On 1/10/2012 8:38 PM, Felix Miata wrote:
On 2012/01/10 19:48 (GMT-0800) Marc Chamberlin composed:
Rajko M. wrote:
Try to remove BlueDevil if keyboard works in a text mode. Carl explained how to get there.
zypper search bluedevil will list all related.
zypper remove bluedevil
After that I would reboot, to make sure that something related is not active tough early-xdm.
Hmmm, well attempting to go to runlevel 3 took me down a different rabbit hole.... I reach the login prompt, but the keyboard remains unresponsive. So am unable to log in or do anything... A new "feature"
Even when you choose the "failsafe" Grub menuitem, with or without "3" on the Grub line?
also surfaced, right after getting the login prompt, I am getting a repetition of some sort of instrumented error (about every 10 second) -
[ nnn.nnnnnnnn] [drm] nouveau 0000:01:00.0: No native mode, forcing panel scaling
The nnn.nnnnnnn is a number which keeps increasing on each line as it is printed out to the screen. This number increments by about 10 to 12 in value, climbs up to 600.9150863 then everything freezes up.... Only option is to reset the computer at this point..... So no joy with the keyboard in the runlevel 3 state...
I suspect the nomodeset component of failsafe should avoid this (not use nouveau/drm) and let you do your updates and get rid of bluedevil, after which try again the default grub entry. Oh, I am sorry Felix, I didn't make myself very clear... No, I am unable to use the keyboard, regardless of whether I boot to runlevel 3 (text mode) or runlevel 5 (graphics mode), when booting to either the desktop or the failsafe version of 12.1. I have tried all 4 variations, no joy, and was reporting the one unusual anomaly I saw.
But, while I didn't feel this was out of the ordinary, I will report that when I tried to boot the failsafe version, to runlevel 3, I get the login prompt, but further output messages are reported to the screen until it starts phase 2 of the SuSE firewall. That is the last thing reported, quite awhile after the login prompt occurred. I don't have the network configured yet either, so there are some failures being reported in conjunction with network startup, but I figure that as soon as I can get to YaST, I can fix those issues as well. However, that remains a moot point because at this point when output messages stop, I cannot input anything via the keyboard. This discussion has given me an idea however, and I think I have an old PS2 keyboard out in my garage, that I will try and use tomorrow. Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org