SuSE 9.1 neew install on a C840

Same happened to me today on an inspiron 5150.

Anyone??

Also, if I do this and the keyboard thing is still an issue, can I back this out? If so how?

And you did all updates and also the kernel update? And the keyboard works now?

exactly. I ran the YaST update. it chose a bunch of updates, and i added the rest by checking. My 5150 has an nvidia card so i also added that driver. Basically, i checked everything available to me. Personally, my bet is that it was the nvidia driver or kernel update that fixed it, but my keyboard works great now which is all i care about.

-tsu

So if I have been running SuSE fine for 2 weeks, I just need to log in as root.

do an init 3.

then do an init 5

then run YAST

Then reboot?

UPDATE:

1. start with options:
vga=normal 3

this starts with text only.

2. login with root id and password

3. init 5 to start GUI, which should be ok now.

4. run YaST Update and do update. specifically, i selected to add the nVidia drivers and everything else, kernel update, etc.

5. reboot when done.

now my system works like a charm!

-tsu

ok, thanks very much.

 

your process worked.

if you can back out updates, i've never done it and don't know specifically what you'd need... mostly updates are a good thing.

as for logging in, i can only vouch for the process i outlined. BOOT with 3, login, init 5, YasT update. init 3 should work, but i don't know for sure.

-tsu

Hi all,

I have observed the same problem (no keyboard, but mouse after boot) on a Dell Latitude D800 as well, but in contrast to above posters, running update
didn't fix the problem. It does *sometimes* work that you start with "vga=normal 3" and then "init 5" after logging in as root - sometimes, because
the 'failsafe' boot actually does these settings, and will often leave you with a textscrren, but still no keyboard.

I guess that the keyboard controller in such notebooks is simply broken (and 9.1 triggers the bug for some reason). The following fix was successful for me:

Add 'i8042.dumbkbd=1' to the kernel line of you Linux boot manager. This will attempt not to fiddle with the defective functions in the controller.

Hope this helps

holgios2