On Sun, Nov 27, 2016 at 7:50 AM, Ryan Tandy <r...@nardis.ca> wrote: > Control: tag -1 patch > > On Sat, Nov 26, 2016 at 12:59:21PM -0800, Ryan Tandy wrote: >> >> Unfortunately dmesg and kern.log are flooded with messages like: >> >> [ 161.781360] Bad eraseblock 32764 at 0x0001fff00000 >> [ 161.786261] Bad eraseblock 32765 at 0x0001fff40000 >> [ 161.791159] Bad eraseblock 32766 at 0x0001fff80000 >> [ 161.796058] Bad eraseblock 32767 at 0x0001fffc0000 >> >> and boot takes a very long time due to logging all these messages. I >> suppose that's a side-effect of using the kurobox-pro dtb - guessing it has >> a different flash layout?
Glad to hear it works for you. Actually there's less flash on Linkstation GL or Pro/Live than on KuroBox Pro. So using kurobox-pro dtb is just a tentative solution for test purpose. > On Sun, Nov 27, 2016 at 01:20:10AM +0900, Roger Shimizu wrote: >> >> - start your device by kernel 4.3 first. >> - confirm your have flash-kernel and linux-image-4.8.0-1-marvell >> installed. >> - cp /usr/lib/linux-image-4.8.0-1-marvell/orion5x-kuroboxpro.dtb >> /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb >> - flash-kernel --force 4.8.0-1-marvell Sorry, I forgot to mention after steps above, when you want to switch to another kernel version, and run like - flash-kernel --force <debian-kernel-version> The flash-kernel will treat the device as Kurobox Pro. So you need the following command to tell flash-kernel that your device is Linkstation Pro/Live: # echo -n "Buffalo Linkstation Pro/Live" > /etc/flash-kernel/machine After that, you can switch back to kernel 4.3 or 4.4, which use the device file instead of device tree, if you still installed on your system: # flash-kernel --force 4.3.0-1-orion5x - or - # flash-kernel --force 4.4.0-1-marvell Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1