Hide Forgot
Description of problem: During installation the keyboard is unavailable as soon as the installation process starts X11 The mouse works. Version-Release number of selected component (if applicable): phobe-i386-disc1.iso How reproducible: I have 15 computers with Board K7 Triton 400/GA-7VA Athlon 2200+. At every computer the keyboard is not available as soon as the installation process sarts X11. BTW: It IS availabel on psyche-8.0! Steps to Reproduce: 1. insert CD-ROM with "phoebe-i386-disc1.iso" 2. proceed installation process till X11 is started 3. Press any key --> nothing happens Actual results: The Red Hat users have to learn to use the computer without keyboard. Expected results: If I press a key on keyboard (for instance 192.168.10.1 for network konfiguration) the appropriate signs should appear at screen. Additional info:
If you hit cntl-alt-f2 does it switch to a text command screen?
This should be fixed in current trees.
I can hit hit cntl-alt-f2: nothing happens. Even if I press cntl-alt-backspace: nothing happens. An nothing happens if I press cntl-alt-del. BTW: I've forgotten: I use PS2 keyboard and USB mouse. I hope the last answer is authoritative!
If you boot with 'linux text' you will see a text based install interface. Does you keyboard work then?
It dosn't work if I use: linux text The installation proceeds and the keyboard works till a screen appears "Wilcome to RedHat Linux..." And I shall choose "OK" or "Back". But I can't do anything because the keyboard has no effect. I can press <Return> or <Tab> even crtl+alt+del --> nothing happens! Again: I have 15 computers with Board K7 Triton 400/GA-7VA and Athlon 2200+. I can choose any of these computers randomly. The keyboard has no effect. But note! All works with psyche-8.0. (???) Perhaps I can give a hint. There are some related news: http://www.cs.helsinki.fi/linux/linux-kernel/2002-50/0226.html http://www.cs.helsinki.fi/linux/linux-kernel/2002-50/0255.html http://www.uwsg.iu.edu/hypermail/linux/kernel/0212.1/0891.html Perhaps this helps!
Apparently this is a kernel issue.
it's not.