-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Am Donnerstag, 6. Mai 2004 21:27 schrieb Moe:
> Hi
>
> I am windows user. I had no problem (or so I thought) installing the new
> 4.40 Xfree. After I restarted x I could not login as the keyboard no longer
> works when x starts. The mouse still works.
>
> The video card is a FX5200 and the motherboard is A7V8X-X
>
> Maurice Windham
Possibility 1:
I know of a similar problem which appears with the latest SuSE Linux
distributions in combination with some strange bios versions and hardware
combinations, esp. graphics / video card. The keyboard is locked when X is
started, probably because of a socalled race condition between the keyboard
access of the X process, the BIOS and tool named hwinfo / hwscan, which is
quite useful to detect new hardware or certain hardware settings but
sometimes causes strange behaviour like keyboard locks on X. hwinfo / hwscan
aren't really bad, in 99% of all cases they are nice little helpers for Linux
newbies working as busy bees in the background helping them with hardware
detection and configuration.
You should try to restart X or xdm by remotely logging into your system and
killing X or restarting xdm.
To remotely login, use the command:
ssh root@addressOfFirstMachine
To kill X, use
ps ax | grep X
then note it's pid number (the number in the left most column) and kill it
using
kill pidNumber
If you don't see the screen flashing (the login window now should disappear
and reappear again), use
kill -9 pidNumber
instead. With
ps ax | grep X
you can check the results. You should see no X process now or a new one with a
pid different from the one you saw before.
To restart xdm, use one of the following commands:
rcxdm restart
/etc/init.d/xdm restart
/etc/rc.d/xdm restart
If you can use the keyboard now, you might find a file named kbd and a file
named hwscan or hwinfo in your /etc/init.d/ or /etc/rc.d directory.
If this is the case, the directory /etc/init.d/rc5.d/ or /etc/rc.d/rc5.d/
contains symbolic links to these scripts named Snnkbd, Knnkbd, Snnhwscan /
Snnhwinfo and Knnhwscan / Knnhwinfo, where nn is some number usually ranging
between 01 and 20. These symbolic links can safely be deleted, deleting them
will only disable your localized keyboard settings, if any, on the virtual
terminals, but it should have no further negative impact on your system.
So do a
rm /etc/init.d/rc5.d/[KS]??{hwinfo,hwscan,kbd}
The system now should never again lockup the keyboard in X after booting.
If this doesn't help, try the next one:
Possibility 2:
The keyboard section of your X-Server configuration might be jammed by the ati
driver installation, which is not very likely but maybe happened (just a
theory, this shall in no way be a blame against ati, so don't misunderstand
this, please).
The configuration file is named XF86Config and usually lives in /etc/X11.
The installation tool should have left a backup copy of your previous X
configuration in some file named XF86Config and some ending appended on its
name.
Again, remotely login to your machine using ssh.
You can list all variants using the command
ls -l /etc/X11/XF86Config*
Hopefully you see more than one file now. The one not named only XF86Config
with the latest date will probably be the backup copy generated by the ati
driver installation. Make a backup copy of the current configuration now,
e.g. using
cp /etc/X11/XF86Config /etc/X11/XF86Config.`date +%Y%m%d`.mycopy
or just
cp /etc/X11/XF86Config /etc/X11/XF86Config.mycopy
then open the used and the detected latest version of the file both in an
editor and overwrite the section Keyboard with that of the backup copy using
your favorite text editor, which hopefully already is vi / vim because then
you may use vimdiff or vi -d to simultaneously open both files and let vim
having marked up the differences between the files.
After editing the XF86Config file, you can now restart X using the same
procedure as described for Possibility 1.
If X doesn't start again, there's some error in your config file. Try fixing
it. In emergency, restore the backup you made before. The
files /var/log/X*log might give you some hint what error X detected in the
config file.
I hope this helps.
Bye
- --
ITCQIS GmbH
Christian Wolfgang Hujer
E-Mail: Christian.Hujer@xxxxxxxxxx
WWW: http://www.itcqis.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQFAmqlbMgwgpCF2K9sRAq+QAKCYCaeW8jMrALDrUjRWOqqLpIPJeQCeIqn0
wW0IeuIMgGic4JpHQusMkaA=
=D0OC
-----END PGP SIGNATURE-----
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86
