It works, log snip below, thanks! Can you just tell me how do you calculate the addresses and do I need to recalculate for each new kernel or those just go straight to uEnv.txt/setenv? ==== >8 ==== Now the above I've wrote between your edits, so now I assume my questions answered ^_^J ==== >8 ==== importing envs ...by Dźwiedziu - Debian
`file` says yes: file /media/root/rootfs/boot/initrd.img-5.17.4-kirkwood-tld-1 /media/root/rootfs/boot/initrd.img-5.17.4-kirkwood-tld-1: gzip compressed data, was "mkinitramfs-MAIN_ZBkgNW", last modified: Sun May 15 13:12:59 2022, from Unix, original size modulo 2^32 31927296by Dźwiedziu - Debian
I'm having trouble with installing newer, > 5.14.9 (still I've also managed to break it in another way) kernels. 5.15.5 and 5.17.4 at least. And I don't have an idea what to do about it. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In:by Dźwiedziu - Debian
After downgrading the kernel it boots properly (as a bare board, no network attached) without changing anything else. Also the 5.14 kernel worked for at least half a year.by Dźwiedziu - Debian
Took the thing apart and the serial console now works. But it kernel panics as doesn't seem to see the USB drive (yes the same drive the kernels boots from). Also the console doesn't react to any keys, so I can't stop the autoboot. [ 8.598956][ T1] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 8.607254]by Dźwiedziu - Debian
After multiple restarts yesterday* I've tried to boot with my last working kernel (5.14.9) for the final time to get back to a working hardware state. Unfortunately all I've got was the output below. The autoboot timeout just skips. Tried a few times, with and without USB storage and nothing changed. * Was trying to work around that the 5.17.4 and 5.15.5 kernels installation did notby Dźwiedziu - Debian
Last things first: 5.14.9 with included dts works, eth0 also. Still have no idea what's up with the envs. In the mtd1 dump the dtb_file was set wrongly, but it didn't boot with correct dtb_file in uEnv.txt. Still didn't work when I've fw_setenv dtb_file correctly. And still I don't have idea why it didn't flash the U-Boot defaults (see end of post). ==== >8by Dźwiedziu - Debian
bodhi Wrote: ------------------------------------------------------- Quote As I mentioned above, QuoteYes, do the same thinng cratsil did. Repopulate the envs with uEnv.txt. Yes, this is why I've mentioned Quote (I've reset the uBoot envs in NAND before my earlier post, just not sure if I did it right) Quote I'm a bit confused. Is this the old listing Quoterby Dźwiedziu - Debian
U-Boot 2014.07-tld-4 (Aug 02 2015 - 00:40:12) ZyXEL NSA325 2-Bay Power Media Server Yeeeeeeah...... Maybe I'll update first...... Edit: unfortunately this did not help (I've reset the uBoot envs in NAND before my earlier post, just not sure if I did it right): U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282by Dźwiedziu - Debian
Could this be the same problem? Apart from that I've reset the uBoot envs to default (no change), upgraded the kernel from 5.13.6 a few times (it does not see eth0; I'm beginning to think that my eth0 is gone due to a hard poweroff event). SoC: Kirkwood 88F6282_?? DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egby Dźwiedziu - Debian
IT'S ALIVE! I'm contractually obligated to say this, when a first issue is solved, right? ;)by Dźwiedziu - Debian
First of all I'm new to this and have a second-hand NAS, so I'm pretty sure I've missed something. I'm booting from USB, with the 5.2.9 kernel. The boot looks like this: NSA325> reset resetting ...by Dźwiedziu - Debian