* Karsten Merker [Thu Sep 25, 2014 at 08:15:48AM +0200]: > On Tue, Sep 23, 2014 at 11:42:08PM +0200, Michael Prokop wrote: > > Does this look like it would provide what you're asking for? > > http://anonscm.debian.org/cgit/kernel/initramfs-tools.git/commit/?h=mika/bug_762634&id=3b835665015c0a9287284c2548b12ab7c8cabc78 > outside d-i and for the "MODULES=most" configuration, this works > fine: [...] > Inside the /target chroot created by d-i, update-initramfs is by default > configured to run with "MODULES=dep" and gives only the following > modules on my armhf/sunxi test system: Hmpf, I so much am not a fan of this default "MODULES=dep" behaviour of d-i... [...] > The phy-sun4i-usb module is missing there, although it is loaded > by the running kernel: > # lsmod |grep phy_sun4i_usb > phy_sun4i_usb 4260 4 > Without phy_sun4i_usb, USB support does not work at all on this > platform, so this module would always have to be included. > The missing ohci-hcd and ohci-platform modules would be explained > by the fact that this particular device technically has both EHCI > and OHCI controllers, but the platform-dependent OHCI glue code > is not yet implemented in the kernel, so the OHCI part is > currently invisible to the kernel. Ok > When manually running update-initramfs with MODULES=most inside > the d-i /target chroot, all three modules (ohci-platform, > ehci-platform and phy-sun4i-usb) are there, but by default the > user is not presented with a choice regarding MODULES=dep vs. > MODULES=most in d-i. The relevant debconf prompt is only > presented at debconf priority "medium", i.e. when running d-i in > "expert" mode, so I would appreciate very much if you could > include the missing phy-sun4i-usb module also when building the > initramfs with MODULES=dep. Is there a /sys/... entry which would make it obvious for i-t that phy-sun4i-usb exists/should be loaded? regards, -mika-
Attachment:
signature.asc
Description: Digital signature