Looks really good. I was able to boot with an attached harddrive. Next step may be to update uboot. Christianby ckuetbach - Debian
Hi Bodhi, after changing the envvar, a BAD CRC of the kernel happened. If I understand the change correctly, it was to change some regions in the RAM. May that caused some trouble loading the kernel? Also sometimes some strange things happened, like the command setenv was suddenly not present, or help said help command not find, open help. May be something was wrong with my serial conneby ckuetbach - Debian
Hi, I recreated he USB-Stick, but it still waits for the rootfs to become available. With "root=LABEL=rootfs" it didn't boot. (waited for rootfs) With "root=/dev/sda1" it worked, but as I attached a harddrive, the USB-Stick became /dev/sdb and the box didn't boot. The label is set, I don't know why. Christianby ckuetbach - Debian
Hi, thanks for your fast reply. meanwhile I got some steps further. I added a rootdelay=10 and rootwait to the bootarg options. Now the /dev/sda1 is showing. The label is present, but I created an etx2 partition. My second USB stick was ext3, but wth the same result. I added the current output. Regarding the beeing "root" I always get root with "sudo su",by ckuetbach - Debian
Hello, I tried to give an old NSA 325v2 a new life as, don't know what I want to do with it, ut it should be useful again ;) As a beginner / immediate I tried this tutorial first, because no UART was needed and it should be more or less harmless. Unfortunately, the original kernel and rootfs weren't available anymore, so I used the version from this forum here. Also after pulliby ckuetbach - Debian