Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
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
~ # chroot /target flash-kernel --force 4.8.0-1-marvell
DTB: orion5x-linkstation-lsgl.dtb
Installing /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb into /boot/dtbs/4.8.0-1-marvell/orion5x-linkstation-lsgl.dtb
Taking backup of orion5x-linkstation-lsgl.dtb.
Installing new orion5x-linkstation-lsgl.dtb.
Installing /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb into /boot/dtbs/4.8.0-1-marvell/orion5x-linkstation-lsgl.dtb
Taking backup of orion5x-linkstation-lsgl.dtb.
Installing new orion5x-linkstation-lsgl.dtb.
flash-kernel: installing version 4.8.0-1-marvell
flash-kernel: appending /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb to kernel
Generating kernel u-boot image... done.
Taking backup of uImage.buffalo.
Installing new uImage.buffalo.
Generating initramfs u-boot image... done.
Taking backup of initrd.buffalo.
Installing new initrd.buffalo.
- check the log of above command, it should use
/etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb for building
uImage.buffalo, the kernel image for booting
- reboot and see the result
If the above steps works for you, I can submit the above patch to
kernel upstream, and include it into Stretch release.
So I'm looking forward to your result. Thank you!
It booted! :)
Linux xenon 4.8.0-1-marvell #1 Debian 4.8.5-1 (2016-10-28) armv5tel GNU/Linux
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?
Anyway, the change to nr-ports=2 looks good!
Tested-by: Ryan Tandy <ryan@nardis.ca>
Thanks!
Reply to: