Keyboard not working after boot (suddenly)

fmma · 2009-02-13 18:52:26

Hi,

had a working system, and I rebooted from another virtual terminal when my rc.conf file was still open. Now, after rebooting, keyboard is not working.
Can anybody help me here ?

Thanks

fr

Inxsible · 2009-02-13 19:10:52

fmma wrote:

Hi,
had a working system, and I rebooted from another virtual terminal when my rc.conf file was still open. Now, after rebooting, keyboard is not working.
Can anybody help me here ?
Thanks
fr

Did you update HAL by any chance? If so, you might try disabling input hotplugging and see if your keyboard works when you explicitly configure it in xorg.conf

brisbin33 · 2009-02-13 19:36:04

fmma wrote:

when my rc.conf file was still open...

this catches my eye; if you've got ssh running, then i'd get in there and check your rc.conf; if not, do the same with a LiveCD.

sverzijl · 2009-02-15 11:23:39

I have exactly the same problem and I think its related to one of the latest updates for Archlinux.

The keyboard only stops working when XORG loads, otherwise it works fine up until then. Archlinux fallback seems to still load KDM, is there anyway to get it to just go straight to a console?

Thanks

stuntgp2000 · 2009-02-15 13:30:01

I've the same problem. The only work around I found is using the vesa driver.

Here is the list of packages I updated before I've this problem:

Upgraded compizconfig-python successfully (0.7.8-1 -> 0.7.8-2)
Upgraded digikam successfully (0.9.4-2 -> 0.9.5beta3-1)
Upgraded fusion-icon successfully (20080313-1 -> 20090213-1)
Upgraded libtasn1 successfully (1.7-1 -> 1.8-1)
Upgraded gnutls successfully (2.6.3-1 -> 2.6.4-1)
Upgraded xcb-proto successfully (1.2-2 -> 1.3-1)
Upgraded libxcb successfully (1.1.90.1-1 -> 1.1.93-1)
Upgraded libx11 successfully (1.1.5-2 -> 1.1.99.2-2)
Upgraded inputproto successfully (1.4.4-1 -> 1.5.0-1)
Upgraded xextproto successfully (7.0.4-1 -> 7.0.5-1)
Upgraded libxext successfully (1.0.4-1 -> 1.0.5-1)
Upgraded ghostscript successfully (8.64-1 -> 8.64-2)
Upgraded hdparm successfully (9.6-1 -> 9.10-1)
Upgraded kernel26 successfully (2.6.28.4-1 -> 2.6.28.5-1)
Upgraded libice successfully (1.0.4-1 -> 1.0.5-1)
Upgraded libxi successfully (1.1.4-1 -> 1.2.0-1)
Upgraded pciutils successfully (3.0.3-1 -> 3.1.2-1)
Upgraded pixman successfully (0.12.0-1 -> 0.14.0-1)
Upgraded python-pybluez successfully (0.15-2 -> 0.16-1)
Upgraded sound-theme-freedesktop successfully (0.1-1 -> 0.2-1)
Upgraded xcb-util successfully (0.3.2-1 -> 0.3.3-1)
Upgraded xf86-input-evdev successfully (2.1.0-1 -> 2.1.2-1)
Upgraded xf86-input-keyboard successfully (1.3.1-1 -> 1.3.2-1)
Upgraded xkeyboard-config successfully (1.4-2 -> 1.5-1)
Upgraded xorg-xinit successfully (1.1.0-1 -> 1.1.1-1)
Upgraded xterm successfully (239-1 -> 241-1)
Upgraded xtrans successfully (1.2.2-1 -> 1.2.3-1)

I tried to rollback the previous versions of those packages but no luck.

My graphic card is ATI 9250 and i'm using the open source driver.

Full mouse and keyboard freezing happens after KDM/GDM get loaded completely. And sometime the mouse moves extremely slowly but the keyboard still completely frozen.

I'll try to rollback to the previous version and see what I get one more time.

Last edited by stuntgp2000 (2009-02-15 13:31:58)

brisbin33 · 2009-02-15 19:16:05

sverzijl wrote:

I have exactly the same problem and I think its related to one of the latest updates for Archlinux.
The keyboard only stops working when XORG loads, otherwise it works fine up until then. Archlinux fallback seems to still load KDM, is there anyway to get it to just go straight to a console?
Thanks

edit the grub entry and add a 3 at the end of the line. that'll keep you in init 3 (console). once there:

cat /var/log/Xorg.0.log | grep EE

this will return any errors (lines starting with EE) during the last loading of the xserver

once, when my keyboard wasn't loading that at least pointed me to the error (mixmatch in xorg-server and kbd_driver.so).

ro0x · 2009-02-15 23:37:03

anyone can post a link for the old packages replaced by the update??? // I need a fix for this

ro0x · 2009-02-15 23:45:28

[2009-02-15 15:38] upgraded xkeyboard-config (1.4-2 -> 1.5-1)
[2009-02-15 15:38] upgraded xorg-xinit (1.1.0-1 -> 1.1.1-1)
[2009-02-15 15:38] upgraded xf86-input-keyboard (1.3.1-1 -> 1.3.2-1)
[2009-02-15 15:38] upgraded xcb-util (0.3.2-1 -> 0.3.3-1)
[2009-02-15 15:38] upgraded libdrm (2.3.1-2 -> 2.3.1-3)
[2009-02-15 15:38] upgraded libice (1.0.4-1 -> 1.0.5-1)
[2009-02-15 15:38] upgraded xcb-proto (1.2-2 -> 1.3-1)
[2009-02-15 15:38] upgraded libxcb (1.1.90.1-1 -> 1.1.93-1)
[2009-02-15 15:38] upgraded libx11 (1.1.5-2 -> 1.1.99.2-2)
[2009-02-15 15:38] upgraded xextproto (7.0.4-1 -> 7.0.5-1)
[2009-02-15 15:38] upgraded libxext (1.0.4-1 -> 1.0.5-1)
[2009-02-15 15:38] upgraded libxi (1.1.4-1 -> 1.2.0-1)
[2009-02-15 15:38] upgraded inputproto (1.4.4-1 -> 1.5.0-1)

Last edited by ro0x (2009-02-15 23:46:14)

stuntgp2000 · 2009-02-16 21:01:06

Tried to roll back the previous version of the packages mentioned in my fist post but no luck.

I did some extensive search and I think we hit a nasty bug. The combination of kernel 2.6.28 and Xorg 7.4 and some "non supported" ATI cards leads to what we got. This affects Ubuntu too.

I tried almost all tweaks and options but no result. the only thing that worked for me is vesa driver with limited res (800x600) which is unbearable.

Hopefully I still have Ubuntu 7.04 LiveCD which I tried and I confirm it works. Ubuntu 7.10 and 8.04 failed.

This problem may stay with us till the end June/July when Xorg 7.5 will be released.

Actually, there are two options either you buy a new graphic card from a different vendor, or use a distro which uses an older version of Xorg.

Too bad.

brisbin33 · 2009-02-17 15:13:13

FWIW, there's another thread here on how to use this site: http://arm.nrk.cc/ via a wget+pacman script to "roll back" your system to a particular date. i tried, but can't find the thread.

i've been using it extensively (but manually) to keep my xorg-related packages back at 1.4.2. if someone knows the thread please post, if not feel free to browse that site for date specific packages; keeping xorg at 1.4.2 and if86-input-keyboard at 1.3.1 fixed all my problems.

i think i'll be skipping 1.5 entirely so this site is a godsend for me. enjoy

stuntgp2000 · 2009-02-18 00:48:58

@brisbin33: Big thanks, you're the man!

I can confirm that using xorg-server-1.4.2-2 and xf86-input-keyboard-1.3.1-1 fixed the problem.

You can find them at http://arm.nrk.cc/extra/os/

Thanks again @brisbin33

Arch Linux

#1 2009-02-13 18:52:26

Keyboard not working after boot (suddenly)

#2 2009-02-13 19:10:52

Re: Keyboard not working after boot (suddenly)

#3 2009-02-13 19:36:04

Re: Keyboard not working after boot (suddenly)

#4 2009-02-15 11:23:39

Re: Keyboard not working after boot (suddenly)

#5 2009-02-15 13:30:01

Re: Keyboard not working after boot (suddenly)

#6 2009-02-15 19:16:05

Re: Keyboard not working after boot (suddenly)

#7 2009-02-15 23:37:03

Re: Keyboard not working after boot (suddenly)

#8 2009-02-15 23:45:28

Re: Keyboard not working after boot (suddenly)

#9 2009-02-16 21:01:06

Re: Keyboard not working after boot (suddenly)

#10 2009-02-17 15:13:13

Re: Keyboard not working after boot (suddenly)

#11 2009-02-18 00:48:58

Re: Keyboard not working after boot (suddenly)

Board footer