Hi bodhi, I believe doing the first test is enough already, since the problem seems to be in the bootloader command line being ignored (according to dmesg): Booting U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) OXNAS OX820 gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 10 0 OX820> setenv mtdparts 'mtdpartby chessplayer - Rescue System
daviddyer Wrote: ------------------------------------------------------- > > Well, it looks complicated. Anyway, if the flash > drive doesn't work in u-boot, add a usb hub and it > might change. Ah, that seems like a way to go, if need be - thanks for that. Anyway, the GoflexNet is now booting from HDD again with the latest uBoot and I have a USB drive which seems toby chessplayer - uBoot
bodhi Wrote: ------------------------------------------------------- [...snip] > > That's what I try to find out (after chessplayer > done the 2 tests). The sysupgrade will show > whether the envs are touched during the upgrade, > and in what way. We know the kernel and ubi > partitions are updated. Perhaps if you have the > box running, you can verify it, too.by chessplayer - Rescue System
bodhi Wrote: ------------------------------------------------------- > > Has anybody else seen the > > GFN be so picky about booting from USB? > > A lot of the USB thumb drives suffer the same > fate. Sandisk brand is most reliable in booting. > > In anycase, my released u-boot for 2017 should > help in booting USB thumb drives of many brands. As I saby chessplayer - uBoot
bodhi Wrote: ------------------------------------------------------- > chessplayer, > > > root@OpenWrt:~# cat /proc/cmdline > earlyprintk console=ttyS0,115200 > > > That's the problem. The mtdparts is not in the > boot args. And this cmdline is a default one, not > what we need, which should be many more > parameters. > > In serial/netby chessplayer - Rescue System
daviddyer, does this survive a sysupgrade from OpenWrt? (Just out of curiosity - the use case for that is probably not too obvious ...). My guess is it wouldn't, would it? Cheers, chessplayerby chessplayer - Rescue System
Hi, I followed the instructions in the 2017 uBoot thread for the Kirkwoods for my GoFlexNet (which still had a uBoot from 2011 ...). Everything worked fine (or so it seemed - see below) except for the setting of the ethaddr: root@gfn ~ $ fw_setenv ethaddr '00:10:75:XX:YY:ZZ' Can't overwrite "ethaddr" This could be remedied from the OpenWrt Rescue system. Howeveby chessplayer - uBoot
1st test OX820> setenv mtdparts 'mtdparts=41000000.nand:0x100000@0x0(u-boot),0x20000@0x100000(u-boot-env-main),0x80000@0x3c0000(u-boot-env),0x440000@0x9C0000(kernel),-(ubi)' setenv mtdparts 'mtdparts=41000000.nand:0x100000@0x0(u-boot),0x20000@0x100000(u-boot-env-main),0x80000@0x3c0000(u-boot-env),0x440000@0x9C0000(kernel),-(ubi)' OX820> run bootcmd_owrt run bootby chessplayer - Rescue System
Actually, here is some additional info: even if I boot the latest kernel / rootfs combi of bodhi's, I end up with a randomly assigned MAC-address. During the boot process, I can observe that nc connects and uses the ethaddr specified in the uBoot-env (shows up briefly in my FritzBox), but after booting Debian, it has a random MAC-address, so it is not picked up from the uBoot-env. So, herby chessplayer - Rescue System
How to install OpenWrt on OXNAS boxes This thread is based on my tutorial HowTo: OpenWrt on Kirkwood boxes (Attention: if it is one of the Kirkwood Pogoplugs you have, it is that tutorial you want to follow!). The basic approach is the same for the OXNAS', but some modifications are required (and, as we will see, not everything is perfect as of the original writeup of this tutorial on Auby chessplayer - Rescue System
daviddyer Wrote: ------------------------------------------------------- > @chessplayer > > A Maybe you need to add "nand erase.part ubi" > in 3 or 4. Don't know about that, since I went through this process on 2 Dockstars, 3 Pogo E02 and a GoFlex Net (I know, I overdid it a bit with these boxes way back when ...) and did not need this. > B It'sby chessplayer - Rescue System
bodhi Wrote: ------------------------------------------------------- > Yes what joerg said is absolutely correct, the > modified bootcmd_exec is required to boot with > Debian on USB and fall back to OpenWrt, when the > USB rootfs is either corrupted or absent. Without > this change, the rescue system will not work as > intended. > > > setenv bootcmd_execby chessplayer - Rescue System
daviddyer Wrote: ------------------------------------------------------- > Just found a typo in > > echo '/dev/mtd0 0xc0000 0x20000 0x20000' > > /etc/fw_envs.config > > should be > > echo '/dev/mtd0 0xc0000 0x20000 0x20000' > > /etc/fw_env.config Thanks for pointing this out. I corrected it in the original post. Cheers, cby chessplayer - Rescue System
joerg_999, I tried that and it did not work. Maybe I did something wrong somewhere. Anyway, the method I am describing did work on Dockstar, PogoE02 and also GoFlex Net, in the latter case even with an older uBoot and customised uBoot environment. Thus, I thought I would share. I does seem to me that being able to find the environment variables by having the correct /etc/fw_env.config is neby chessplayer - Rescue System
bodhi, thanks for the clarification. I updated my original post to make it quite clear that this is essential. Cheers, chesspalyerby chessplayer - Rescue System
bodhi Wrote: ------------------------------------------------------- > chessplayer, > > > The latter is a small wonder, since the uBoot environment variables do not correspond to bodhi's anymore. Also, I get: > > > > cat /proc/mtd > > dev: size erasesize name > > mtd0: 00100000 00020000 "u-boot" > > mtd1: 0ff00000 00020000by chessplayer - Rescue System
Hi, I posted a general HowTo here. Cheers, chessplayerby chessplayer - Rescue System
So, I got everything working and since I believe that the process can be improved and generalized, I opened a new thread for Kirkwood boxes in general. The procedure described therein was tested on Dockstar, GoFlex Net and PogoE02 with OpenWrt 18.06.2 (and LEDE 17.01.6) and worked well in all cases, even with older uBoots and kernel+rootfs. Cheers, chessplayerby chessplayer - Rescue System
bodhi's edit: this is a very good tutorial! If you're looking to install OpenWrt for the Pogo V4, very important to also see this post. I also made some improvement (in blue) in the installation instruction below. chessplayer's edit (Aug 14th, 2022): Since there is obviously renewed interest in the subject starting, apparently, in June this year and there is now also a siblinby chessplayer - Rescue System
Hi guys, the following might help others, so I thought I'd share. Here is my report: --- So I tried this with my Dockstar, but managed to semi-brick it ... Status is that I can still connect via netconsole and I can boot the LEDE image (also the newer 18.2 image), but the sysupgrade seems to have messed things up (obviously, I did replace the 'pogo_e02' part with 'by chessplayer - Rescue System
bodhi Wrote: ------------------------------------------------------- > Chessplayer, > > https://packages.debian.org/search?keywords=Dvb&searchon=names&suite=stable§ion=all > > https://packages.debian.org/search?keywords=Firmware&searchon=names&suite=stable§ion=all > > And then you can look at the files in the > packages. bodhiby chessplayer - Debian
bodhi Wrote: ------------------------------------------------------- > To answer habibie question. > > To find a firmware package for your device, you'd > do a package search at Debian site. > > https://www.debian.org/distrib/packages#search_packages > > Enter something specific such as DVB, realtek, > .... in the search box, you will find the rightby chessplayer - Debian
habibie Wrote: ------------------------------------------------------- > Where did you obtain the > dvb-usb-dib0700-1.20.fw firmware file, i.e. > from your windows os? I copied it over from my laptop, which, of course, runs linux (not the other stuff ...). : and the demod-firmware I obtained from Armbian Firmware in GutHub But I will go through the process once more trying oby chessplayer - Debian
Hi bodhi, this explains it, I guess: Laptop: dmesg | tail [14529.873599] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware [14529.873723] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [14529.942585] dib0700: firmware started successfully. [14530.450769] dvb-usb: found a 'Microsoft Xbox Oneby chessplayer - Debian
Hi bodhi, thanks for the info. So, after plugging in the tuner, on my laptop I get: lsmod | grep dvb dvb_usb_dib0700 159744 0 dib7000m 24576 1 dvb_usb_dib0700 dib0090 36864 1 dvb_usb_dib0700 dib0070 20480 1 dvb_usb_dib0700 dib3000mc 20480 1 dvb_usb_dib0700 dibx000_common 16384 3 dib7000m,dib3000mc,dvb_usb_dby chessplayer - Debian
Hi everyone (and bodhi in particular), after a few years I am currently trying to see what my old Kirkwood machines can still do and first of all I would like to say thank you very much to bodhi for keeping this alive. Anyway, way back when I used the boxes as a headless VDR, which worked quite well. The problem was that I needed USB receivers which were installed in user space and cost a lby chessplayer - Debian
bodhi Wrote: ------------------------------------------------------- > > What I am trying to say is after you flashed the > default u-boot envs image, the MAC address is a > valid local MAC address. So there is no > need to specificy the MAC address in > /etc/network/interfaces to get it booting. You can > use the MAC address in the default envs. And then > seby chessplayer - uBoot
Partial success So, inelegant as it may be, my idea of hex-editing the uBoot environment image actually did work, and I now have my OXNAS boxes with the correct value for ethaddr, allowing me to use the same USB drive for both. However, there are two points to consider: a) Obviously, the total size of the image has to be exactly 128kb (i.e. 131072 b) b) The first four bytes are CRC byteby chessplayer - uBoot
bodhi, we are not really understanding each other. Here is my situation in the OXNAS boxes: a) I can boot debian without a problem using a line like hwaddress ether 192.0.xxx.yyy in /etc/network interfaces. b) I cannot see the boot process, since netconsole is not working c) In my router, I have defined the IP address and hostname (oxdefault) to assign to a machine with the randomlby chessplayer - uBoot
bodhi Wrote: ------------------------------------------------------- > @chessplayer, > > The correct command is > > nc -lup 6666 192.168.0.xxx 6666 > > if the 192.168.0.xxx is your pogoplug u-boot env > ipaddr. > > If you have with netconsole while u-boot is > booting, then pls post your u-boot envs, and > describe how you test netconsole (whatby chessplayer - uBoot