Hi bodhi, I did several tests: * Provided initrd (note that I extract all the libs in the initrd - /lib/modules - and placed them on my /dev/sda2) with current config => no boot * Provided initrd with ramdisk_addr= 0x02100000 => no boot * Empty initrd (from http://tyche.pu-toyama.ac.jp/~a-urasim/lsxhl/data/initrd.buffalo) with current config => boot but no ethernet * Empty initby benoqkuke - Debian
Hi bodhi, Thanks for your quick answer. As long as u-boot can start, I can set the NAS in rescue mode (pressing a button at boot time) and acces u-boot with a netconsole. So I could try to update the parameter. But where exactly is this value coming from ? Benby benoqkuke - Debian
Hi bodhi, I tried to boot with stock u-boot and with 2013.01.01 (from https://github.com/mwalle/u-boot/issues/1 ). In both cases I have the same result. I don't have a console so here's everything from Debian: > cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0x70000 0x10000 0x10000 >fw_prinby benoqkuke - Debian
Hi, I'm trying to use 4.14.1-kirkwood-tld-1 on my Buffalo LS-XHL. The Kernel boots perfectly but I don't have any network connection. From dmesg I can see: ... [ 6.891645] libphy: orion_mdio_bus: probed [ 6.896060] orion-mdio f1072004.mdio-bus: Cannot register MDIO bus (-19) [ 6.903029] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 6.911011] ehby benoqkuke - Debian