Thanks bodhi. Reversing uImage solved the kernel panic and now my Pogoplug mobile boots to Debian as expected. Thank you for your help.by ahmed - Debian
bodhi Wrote: ------------------------------------------------------- > ahmed, > > The reason for the kernel panic is: your rootfs > was created incorrectly. You need to skip step 4, > since you already have U-Boot 2016.05-tld-1 > installed. > > > Quote4. Create uImage with embedded DTB for > booting with older u-boots (2012 or earlier). Skip > thisby ahmed - Debian
I tried with another device (sdcard) from scratch and got to the same exact error. [ 12.470097] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 12.477775] Please append a correct "root=" boot option; here are the available partitions: [ 12.486188] 1f00 2048 mtdblock0 [ 12.486195] (driver?) [ 12.492775] 1f01 3072by ahmed - Debian
Thanks for the prompt response. I re-extracted Debian rootfs and see from the log that it is now loading uInitrd but a kernel panic still occurs. I highlighted below a section where it is unable to open root device "(null)". 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 MMby ahmed - Debian
I don't know if the pogoplug mobile can be recovered at this point. I've a serial port connected to USB and I was able to use screen to monitor the boot progress and/or make setenv changes. I was able to Here is the boot log (printenv is also included before boot): QuoteInitial Boot U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRby ahmed - Debian