Greetings, After much success with my Pogoplug v4/mobile, I figured I would try to get my larger v3/Oxnas boards working. I seem to have bricked one right out of the gate. I have a sinking suspicion I have misidentified the board and flashed the wrong u-boot. Here's a picture of the board: https://photos.app.goo.gl/kOVyY9wPaZftWUif1 Here's what I've got. The flash went thby maldridge - uBoot
Here's a full bootlog. This is with a muslc implementation, but it is effectively identical to the glibc trace. U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 Pogby maldridge - Debian
Success! I rebuilt the kernel using an updated version of your .config and it now boots happily. I have some cleanup work to do and then I will write-up the process in case someone else wants to get Void running on similar hardware. Needless to say there will be a shoutout to you in there! For completeness, here's the boot log and some commands that give an idea of what the default sby maldridge - Debian
A little bit further this time: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 Pogov4> printenv arcNumber=3960 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargby maldridge - Debian
Hmm, no luck there: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 Pogov4> setenv load_image_addr 0x800000 Pogov4> setenv scan_disk 'echo running scan_disk ...;by maldridge - Debian
Nope, no desktop software, just a lot of modules: https://hastebin.com/zacoveraqe.diff I think I can safely get rid of (at a high level) the following modules: * drm * resume * i18n * terminfo That should slim it down some, and removing kernel modules that shouldn't be loaded will get it the rest of the way. I could probably remove the btrfs modules as well, but since thosby maldridge - Debian
Nope, nothing but kernel modules in there and a handful of binaries to bring the rest of the system up. Now I should mention that for some reason it has every possible module that can be built for armv5, but that's besides the point... I'll sort this out so that it has a more reasonable number of modules and try again.by maldridge - Debian
Ok, it took substantially longer than I expected to get the uInitrd build reliably working but I now have a complete filesystem. U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboby maldridge - Debian
Ah, I should have mentioned that I wrote the new u-boot envs after you mentioned that was an issue. Here is the current state of the environment: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Hit anyby maldridge - Debian
Thanks! I made some progress today (I just didn't check back here until now). Basically what I'm looking at for the moment is that Void's default kernel builds export a zImage. I can alter this to be a uImage containing a zImage, but since your more modern uboot seems to support booting the zImage directly I'd much rather do that. Ultimately I've got the followingby maldridge - Debian
Success! I was able to use your shim values to boot into the flash drive and from there write the correct variables back out to u-boot. Yes, I was referring to booting with an upstream kernel as obtained from kernel.org and cross compiled for armv5. I have such a kernel for 4.13.1, but I could not get it to go further than the "booting the kernel". You mentioned that the upstreaby maldridge - Debian
Yes, I did step 4 in the instructions, though I do not believe it is making it as far as that in booting. Per your request, here is the bootlog: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Hit any key tby maldridge - Debian
Indeed it looks like I was editing as you were typing. I am inclined to believe that these older drives I have may be having problems talking to the USB controller on the board. If that is the case, I believe this may be easier to troubleshoot running from an SD card than a USB key. What do you think? As far as choice of distro, I'm one of the people behind Void Linux, so it was reasby maldridge - Debian
Having flashed the 2016.05-tld-1 uboot without incident I followed the directions from bodhi's excellent thread (Bodhi's Linux Kernel Kirkwood Thread) but my board simply refuses to boot. It seems to load the kernel and initrd from my flash drive fine and the checksums come back OK, but after it reaches the message "booting the kernel." it just stops. I have tried this sevby maldridge - Debian