I updated a SuSE 9.3 to 11.1. Although the install went seemingly well, I have no keyboard under X. The keyboard does work on text console. X -probeonly complains about the use of udevinfo instead of udevadm info, but apart from that it apears to work. sax2 does hav the issue as well, independantly from any keyboard settings.
If keyboard works under konsole, you could try running “yast” (no quotes - with root permissions) and then navigate to the menu item to tune your keyboard.
Regarding the Update from 9.3 to 11.1: Probably this is a classical case of “To boldly step where no man went before.”
Indeed I just tried it, and was “almost” successful. I got a few complains during the installation, but from irrelevant packages. And besides the keyboard issue the machine does not look too bad, it boots up to the graphical login with apropriate graphics mode, it has a working network, the mouse works fine…
And although I’m by no means an expert on newer SuSEs I’m doing this for some time. Since kernel 0.96something I think. Probably I’m just a (too) optimistic dinosaur >:)
Yes, I tried that. However, the text-console related keyboard settings do change nothing (at the console the keyboard works fine anyhow). And for tuning xorg.conf yast just fires sax2. Which I did as well (mentioned above). And alas, the test input in sax2 does not work.
if no one comes in with a bingo solution, maybe you can try with a
11.1 install DVD (not Live CD) boot from it and make all the right
decisions until you come to this page in the install process http://en.opensuse.org/INSTALL_Local#Step_3:_Installation_Mode and
click on “Repair Installed System”, spin and close the cylinder, put
the muzzle to your temple and pull the trigger…
you might win that roulette…you might not…i’m confident you have
all your data backed up…so. . . . .
hmmmmmm…before you do that…have you yet tried at the very first
boot green screen to type 3 and then enter…that will take you to run
level three where you should be able to fire up your favorite editor
(mine is mc) and have a look at /etc/X11/xorg.conf
well…going back now i see you have told us nothing about your
keyboard…is it USB, maybe wireless or what? heck, maybe it is
laptop…well…make a backup of that config file and then get
creative with the keyboard entries in it…
do you happen to have a backup of that file as it existed in 9.3???,
if so, i’d just make sure the new file’s KEYBOARD entries makes sense
compared to the old file…
well…i suspect you are far ahead of me in diddling creative magic
chants into config files…
maybe my previously mentioned Russian Roulette with a DVD is the best
guess i come up with…
–
brassy
CAVEAT: The author of this posting does not warrant the accuracy,
completeness, legality, or usefulness of its content and is not
responsible for consequences resulting from its use.
Yes indeed, I didn’t supply too much information. The keyboard is a normal PS/2. In fact one of these heavy original IBM PS/2 keyboards from last millenium
It’s connected via a console switch, but this setup works for years. I did check the xorg.conf, it’s keyboard definition is identical to the one used by SuSE 9.3 (and those made sense). And for the magic chant part: Yes, I do remeber the old times where man were real men and created their mode lines in the XF86CONFIG with a slide rule
Funnilly I was able to use X (& kde) if I started it from a textconsole logged in under root. This includes keyboard usage. Thus I suspect either an issue with access rights (but didn’t found anything obvious) or a damaged X module due to the update installation. Btw. even the ATI driver worked after the update
As much as I like the occasional puzzle, I didn’t feel it right to invest more time into this. So I bit the bullet and did a clean reinstall. And now even the keyboard works lol!
For anybody worried about my data: Yes, I do have a good backup, and additionally can leave the home and data partitions out of the update game. Was sysadmin in a former life…
My conclusion of the whole story: No, an update from 9.3 to 11.1 does not work. This will probably surprise nobody.
I still do own two slides, one aluminium and one plastic. And no, I was never cool enough to dangle one from my belt. That would have been too much with the girls >:)
How do you know that your 9->11 update caused the strange keyboard malfunction as a user under X?
I have the same problem out of the blue sky (opensuse 11.1 X86_64 kde) after trying to get my audio to work and installing pulse audio a few days ago.
**PS/2 keyboard works at runlevel 3 and stops working after user login startx.
It continues to work under root login startx. **
The /var/log/warn complained about pulse audio so I uninstalled pulseaudio.
Now /var/log/warn says:
Aug 18 13:21:32 Tokamac SuSEfirewall2: SuSEfirewall2 not active
Aug 18 13:21:32 Tokamac rpcbind: cannot create socket for udp6
Aug 18 13:21:32 Tokamac rpcbind: cannot create socket for tcp6
Aug 18 13:21:33 Tokamac kdm_config[2954]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Aug 18 13:21:35 Tokamac kernel: Clocksource tsc unstable (delta = -62540101 ns)
Aug 18 13:21:57 Tokamac pulseaudio[3983]: pid.c: Stale PID file, overwriting.
Aug 18 13:21:57 Tokamac pulseaudio[3983]: alsa-util.c: Cannot find fallback mixer control "Mic".
Aug 18 13:21:57 Tokamac pulseaudio[3983]: alsa-util.c: Cannot find fallback mixer control "Mic".
Aug 18 13:21:58 Tokamac python: hp-systray(init)[3977]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Aug 18 13:24:36 Tokamac auditd[2916]: Error sending signal_info request (Operation not supported)
Aug 18 13:24:37 Tokamac rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Aug 18 14:01:58 Tokamac SuSEfirewall2: SuSEfirewall2 not active
Aug 18 14:01:59 Tokamac rpcbind: cannot create socket for udp6
Aug 18 14:01:59 Tokamac rpcbind: cannot create socket for tcp6
Aug 18 14:02:02 Tokamac kernel: Clocksource tsc unstable (delta = -189335474 ns)
Aug 18 14:50:18 Tokamac python: hp-systray(init)[5898]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Aug 18 14:53:26 Tokamac python: hp-systray(init)[6237]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Aug 18 14:55:36 Tokamac auditd[2885]: Error sending signal_info request (Operation not supported)
Aug 18 14:55:38 Tokamac rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Aug 18 14:56:42 Tokamac SuSEfirewall2: SuSEfirewall2 not active
Aug 18 14:56:43 Tokamac rpcbind: cannot create socket for udp6
Aug 18 14:56:43 Tokamac rpcbind: cannot create socket for tcp6
Aug 18 14:56:45 Tokamac kernel: Clocksource tsc unstable (delta = -101408539 ns)
Aug 18 14:57:16 Tokamac auditd[2947]: Error sending signal_info request (Operation not supported)
Aug 18 14:57:17 Tokamac rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Aug 18 15:12:23 Tokamac SuSEfirewall2: SuSEfirewall2 not active
Aug 18 15:12:24 Tokamac rpcbind: cannot create socket for udp6
Aug 18 15:12:24 Tokamac rpcbind: cannot create socket for tcp6
Aug 18 15:12:27 Tokamac kernel: Clocksource tsc unstable (delta = -223900588 ns)
I will try to do make a new user now - but any somewhat wise ideas would be well appreciated.