Red Hat Bugzilla – Bug 72901
Mouse & Keyboard dead after boot - Not 64224
Last modified: 2007-04-18 12:46:08 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux)
Description of problem:
Installed null on IBM Xserver 232, legacy keyboard & mouse. When boot process starts both are dead. Can't change grub or lilo selections (tried both), can't login or move mouse cursor after boot complete. Changed run level to 3, booted to command line. Same behavior. If I boot from the rescue floppy, everything works fine. Unlike 64224 this doesn't seem to be dependent on X. I saw the messages initializing USB mouse/keyboard (which I don't have) so I ssh'ed into the box and commented the USB stuff out of rc.sysinit but that didn't help.
I don't know what comes off the floppy when I boot from the rescue diskette but there's either a difference in the kernel or in the init scripts that makes the difference. On the hard disk booted system it seems to be looking for mouse/keyboard input in the wrong place.
I'll do whatever I can to help track this one down. I looked through the boot.log files and didn't see anything interesting. Would they help? Anything from /proc?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install null on my X232 smp server.
2.Boot from hard disk after install complete.
Actual Results: Mouse and keyboard are dead for GRUB/LILO and stay dead after the boot process completes.
Expected Results: usable system.
XServer 232, 256M ram, 2x8GB SCSI disks, dual PIII 1.266 ghz processors, legacy mouse & keyboard, token ring, no USB devices.
This does not sound like an anaconda issue since the system was installed.
GRUB and LILO are running on the system before Linux boots and use only BIOS
calls. So it isn't a kernel issue.
It seems to be an interaction of your hardware and the bootloader UI.
Created attachment 76264 [details]
Found problem. Please close.