 | | | Keyboard detect failure | Keyboard detect failure 2004-10-15 - By James B. Byrne
Back
I pulled the system disk out of an ES3 server and placed in a
new chassis with a different chip set, memory size, processor,
NIC and device controllers. The only other items that were
brought across to the new chassis were the PS2 mouse and
keyboard.
The new configuration boots, but the keyboard is not functions.
However, if I boot in rescue mode from the CD-ROM and chroot to
/mnt/sysimage/ then everything is fine. I ran kudzu which
detected all of the changed hardware but was silent on the mouse
and keyboard. However, when I had kudzu delete the
configuration information for devices specific to the old
chassis the NIC no longer retained its network address
configuration. This can be entered manually when running in
rescue mode but I cannot seem to find a way to make it stick.
Are there any suggestions on how to proceed from here? The RH
support people suggest re-installing ES3 and re-applying the
patches, which seems a little excessive just to get a standard
keyboard back online.
--
*** e-mail is not a secure channel ***
mailto:byrnejb. <token >@(protected)
James B. Byrne Harte & Lyne Limited
vox: +1 905 561 1241 9 Brockley Drive
fax: +1 905 561 0757 Hamilton, Ontario
<token > = rhn Canada L8E 3C3
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
|
|
|