Strange problem with keyboard

**inalto** · 07-07-2005

Hello,

I have just installed the new kernel on my Fedora Core 4.
After I boot, it seems that the keyboard is not responding. The server (dual xeon) is running up fine and I can access it via a ssh.
The only problem is that the keyboard on boot seems dead (when the system goes at login stage, without X11).

To gain access to the server, i run a ssh from another pc on my net, I log into the system and I run kdm& to start x11, and after that the keyboard is working properly!

All has worked perfetcly until I have installed the latest Fedora Kernel smp via rpm.
Now If I boot from the previous kernel the problem still remains.

It seems that the keyboard dont resets at boot. (keyboard used: trust easy scroll silverline)

Anyone has one idea to solve this? It is very annoyng to start x11 from another pc!!

Thank you in advance!

**jamesiniceland** · 07-09-2005

hi,

does the mouse freeze as well?

-James.

**psic** · 07-09-2005

I'm not familiar with the model, is it USB? Kind of strange that the keyboard is not working in the CLI but works in the GUI. It sounds like something is starting in a later runlevel than it should...

**inalto** · 07-10-2005

Hello,

No it is not an usb keyboard.
No the mouse don't freeze.
In dont have tried to change the keyboard for now, but i have made some tests.

If i want to unlock the keyboard i have to login from a remote shell and run the following command:

/usr/sbin/kbdrate

Code:

Typematic Rate set to 10,9 cps &#40;delay = 250 ms&#41;

with this command on the login screen appears this error:

Code:

atkbd.c&#58; Unknown key pressed &#40;translated set 2, code 0x8b on isa0060/serio0&#41;.
atkbd.c&#58; Use 'setkeycodes e00b <keycode>' to make it known.

and I think here is the problem.

This is my keyboard:
http://trust.com/products/product.aspx?artnr=13157

maybe there is an "Unknown key that make my keyboard lookup on boot"

not a big problem because i can unlock the keyboard but is an annonyng problem that i have after I have upgraded to FC4.

now I try to solve the problem with the setkeycodes...

ps. this keyboard has an interesting "easy scroll" feature....

**inalto** · 07-10-2005

Hello,

I have solved the problem!

It was a keycodes problem due to the "easyscroll" feature of the keyboard.

My FC4 locked up the keyboard on boot because the kernel doesn't recognise some keycodes generated by the keyboard.

how I have solved the problem:

I have booted an login from a remote access.

i have unlocked the keyboard on the server with:

Code:

/usr/sbin/kbdrate

i get this error on the server:

Code:

atkbd.c&#58; Unknown key pressed &#40;translated set 2, code 0x8b on isa0060/serio0&#41;.
atkbd.c&#58; Use 'setkeycodes e00b <keycode>' to make it known.

which means that some keycode is not recognised by the kernel.

with the command:

Code:

showkey

i have tried to find the key that generate the e00b keycode (was the easy scroll wheel) and then i find another e016 pressing the weel.

After I have mapped those keys with a "key up" an a "enter"

Code:

setkeycodes e00b 103
setkeycodes e016 28

I have rebooted and now all is working fine.
Now i change the keymaps to make it permanently.
It was the easy scroll feature that locked up all..

**worker201** · 07-10-2005

Slick work! Guess the builders of this keyboard didn't think about Linux. How cool that you figured out how to fix it.

**psic** · 07-10-2005

Great to hear you solved the problem! You should change the subject of your post to reflect this, maybe add a "solved" to the end of it.

Thread Tools

Display

Strange problem with keyboard

keyboard at boot

Posting Permissions