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

Bug#366168: debian-installer: usbhid NOT loaded by udev at initrd stage = no keyboard on USB-only system



Package: debian-installer
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As suggested by Kamion, I'm filing the bug I discussed on #debian-boot.

My particular situation is an installation on a Geode (i586 compatible 
single-chip PC) with a Compact Flash attached to the Geode's IDE bus. 

I'm using the hd-media kernels, following a recipe similar to the USB 
stick installation.

I bootstrap d-i kernels using LILO from the Geode's CF (to compensate 
for the Geode's lack of a complete BIOS), while the businesscard ISO 
resides on a USB stick to avoid file locks during the drive formating 
stage (the CF is my root drive).

The problem is that udev doesn't load usbhid during the initrd stage, 
which later makes it impossible for me to run through the installation 
because the keyboard is not accessible without usbhid.

I have tried the daily hd-media kernels and initrds (both 2.4 and 2.6).

2.4 kernels waste time trying to find an AT keyboard that isn't there,
then forget to load usbhid.

2.6 kernels don't try finding any AT keyboard and forget usbhid too.

The funny thing in both cases is that usbcore and usb-storage are both
found, which means that the USB stick on which the ISO resides and the 
keyboard's built-in hub are accessible; the only missing part is usbhid
to actually be able to type something.

The LILO config I use to bootstrap d-i kernels from the CF:

lba32
disk=/dev/sda
        bios=0x80
boot=/dev/sda
install=/boot/boot.b
image=/vmlinuz
  append="initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw"
  initrd=/initrd.gz
  root=/dev/ram0

I'd appreciate any help on getting the udev in initrd to successfully
detect the hardware and systematically load usbhid.

Thanks!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEW6lfeXr56x4Muc0RAswmAJ9avqQ+Be+4ldb896lgFoLkhXLDvQCfYCij
pK5NUTwprWzIvjQJxbGu1YA=
=LLIw
-----END PGP SIGNATURE-----



Reply to: