Hi @danbnicholson, Would you be able to verify the fix with the xenial and zesty kernels on -proposed?
Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703430 Title: Set CONFIG_SATA_HIGHBANK=y on armhf Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Released Bug description: SRU Justification Impact: CONFIG_SATA_HIGHBANK was changed from y to m after trusty, with no justification appearing in the git history. This can cause problems booting on some systems. Fix: Change the option back to y. Regression Potential: Minimal, as this only switches a driver from being a module to being built-in, and the driver will only be used if the device appears in a platform's device tree. --- Sometime between trusty and xenial, CONFIG_SATA_HIGHBANK was changed from y to m. I believe the change was in utopic, but it's hard to tell. This makes booting on Calxeda Highbank systems pretty difficult since you can't get to the root filesystem on a SATA disk unless you were smart enough to have initramfs-tools include the sata_highbank module. On a clean install, you'd need to know to drop out of the installer, and rebuild the initramfs appropriately. Any chance that could be changed back to y for armhf? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
