[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



Michael Prokop <mika@debian.org> (2014-09-25):
> * 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...

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
|                         db_get base-installer/kernel/linux/initramfs-tools/driver-policy
|                         db_set base-installer/initramfs-tools/driver-policy "$RET"
|                 fi
|                 db_settitle debian-installer/bootstrap-base/title
|                 db_input medium base-installer/initramfs-tools/driver-policy || true
|                 if ! db_go; then
|                         db_progress stop
|                         exit 10
|                 fi
| 
|                 db_get base-installer/initramfs-tools/driver-policy
|                 if [ "$RET" != most ]; then
|                         cat > $IT_CONFDIR/driver-policy <<EOF
| # Driver inclusion policy selected during installation
| # Note: this setting overrides the value set in the file
| # /etc/initramfs-tools/initramfs.conf
| MODULES=$RET
| EOF
|                 fi

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).

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.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: