On 2014-09-30, Ben Hutchings wrote: > On Tue, 2014-09-30 at 08:19 +0100, Ian Campbell wrote: >> On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote: >> > However, at the moment initramfs-tools won't include PHY drivers even in >> > that configuration. >> >> I spent some time last week hunting for a sysfs link between a device >> and the phys which it is using, without success. Do you have any ideas? > > I suspect they're not visible there yet. > > I think you could include all PHY drivers (drivers/phy and > drivers/usb/phy) when MODULES=most, and only the currently loaded > drivers if MODULES=dep. > > USB non-generic PHY drivers don't appear in the device model at all > (ugh!) so in the MODULES=dep case you may have to bodge it by checking > for modules with names beginning with "phy-" (check both /sys/module > and /lib/modules/$(uname -r)/modules.builtin). Would definitely like to see this, with a recent install on a Wandboard Dual with a USB2 sata disk for the rootfs. It installed fine with jessie's debian-installer, but failed on initial boot. I worked around it by adding to /etc/initramfs-tools/modules: ci_hdrc_imx phy_mxs_usb I haven't yet verified if only adding "phy_mxs_usb" instead of both will work. Had a similar problem with an Odroid-XU4 install (which isn't yet supported by debian-installer), and worked around it similarly, although haven't narrowed down exactly which modules are needed, though I suspect one or both of: phy_exynos_usb2 phy_exynos5_usbdrd Something that pulls in all the phy-* modules would likely fix the issue in a generic way, rather than playing whack-a-mole with various phy types. live well, vagrant
Attachment:
signature.asc
Description: PGP signature