https://bugzilla.novell.com/show_bug.cgi?id=241959 Summary: No keyboard if initrd execs /bin/bash Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: qa@suse.de This is for OpenSuSE 10.2, mkinitrd-1.2-106.25. Hardware is a Dell Optiplex GX-745 with a USB keyboard; same effect is seen in SuSE 10.1 with a Dell Dimension E520 with USB keyboard (and presumably any machine and OS version when a USB keyboard is involved). Suppose something goes seriously wrong in your initrd, for example the root filesystem fails fsck and needs manual attention. /initrd/init execs /bin/bash. Now what? No USB modules are loaded, so the keyboard is inoperative. Workaround #1: run all over the building, find the install disc, and use the rescue system to unscramble your disc or initrd. Assuming the involved compute cluster machine has a CD drive. Workaround #2: to /etc/sysconfig/kernel INITRD_MODULES add the USB modules: usbhid uhci_hcd ehci_hcd. usbcore will be dragged in as a dependency. ohci_hcd may be needed on some non-Dell systems. On the listed systems this workaround would not work until I added ehci_hcd, though I expected that the keyboard would not use USB-2.0. The request is that mkinitrd should detect if a USB keyboard is in use and should add the needed USB modules if so. This is a bug, not a feature request, because the sysadmin can't recover from initrd errors as he could with a PS/2 keyboard. Gotcha: if workaround #2 is used, mkinitrd fails to include the module for the root disc (ata_piix and friends on these systems). Workaround #2A: add ata_piix and ahci by hand, but that should not be necessary. The person making the modifications should be sure that when he adds the needed USB modules this does not prevent detection of the root disc modules. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.