[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs



[ Context: MODULES=dep in d-i on arm* ]

Karsten Merker <merker@debian.org> (2014-09-25):
> > > Can you please clarify? I see this in base-installer:
> > > |                 if db_get base-installer/initramfs-tools/driver-policy && \
> > > |                    [ -z "$RET" ]; then
> > > |                         # Get default for architecture
>                                             ^^^^^^^^^^^^^^^^
> [snip] 
> 
> > > Granted, no coffee yet. But I seem to recall that people having issues
> > > with MODULES="dep" are those who actually selected it manually (e.g.
> > > through expert install).
> > 
> > I'm just not a friend of "MODULES=dep" as a default behaviour, good
> > to know that d-i uses a sane default here. :) Thanks for verifying!
> > 
> > > My local test confirms that a basic installation (netboot-gtk image on
> > > amd64 using udebs from sid) leads to MODULES="most" in /target. I didn't
> > > go further than the popcon prompt though.
> 
> Hello,
> 
> I have just run another test on armhf with today's daily d-i
> build (dated 25-Sep-2014 05:17) and default debconf priority
> (at which no debconf prompt regarding initramfs-tools gets
> displayed). This results in:
> 
>   ~ # cat /target/etc/initramfs-tools/conf.d/driver-policy
>   # Driver inclusion policy selected during installation
>   # Note: this setting overrides the value set in the file
>   # /etc/initramfs-tools/initramfs.conf
>   MODULES=dep
> 
> and the short module list in the initramfs confirms that it was
> really built with MODULES=dep. The comment marked above suggests
> that this is an architecture-dependent default, so we could
> possibly both be right ;-). If yes, we will have to find a
> solution regarding the inclusion of the phy-sun4i-usb module
> when building the initramfs with MODULES=dep, though.

Spot-on.

Sorry, I'm frequently entering and leaving that sid chroot on that
wheezy host and failing to remember passing ack-grep the -a flag when
I'm with the wheezy version of it, so I missed the file responsible for
the behaviour you're reporting: debian/templates-arch (base-installer).

Browse online:
  http://anonscm.debian.org/cgit/d-i/base-installer.git/tree/debian/templates-arch

Adding -arm@ and -boot@ for possible comments/insight.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: