Background first. I'm running Slack 12.2, with the KDE4 that Pat posted in testing. I nave a nVidia card that has both VGA and DVI ports. My monitor also has both VGA and DVI ports. Initially, I was running VGA -> VGA and PS/2 for both mouse and keyboard. I finally got around to upgrading my KVM, which would then allow me to use DVI -> DVI and my USB keyboard/mouse combo.

I shut down, unplugged the VGA and both PS/2s, and plugged in the DVI and USB connector. Booted up, to the command line. I'm still old fashioned like that. All of video, keyboard, and mouse were working perfectly. Yahhh, or so I thought.

Switched to my user account, and tried to start KDE, which promptly failed, because the nVidia drivers couldn't read the EDID information from my monitor. After poking around Google for a while, I found a solution which involved running nvidia-settings, saving the EDID information, and then updating xorg-conf to point to the saved copy.

No problem, I thought. So, shut down again, unplugged the DVI, and reattached the VGA, directly to the video card. Booted up, and started KDE. Came up, as before, or so I thought. The mouse worked fine, but any, and every, key press just caused KDE/X to cycle through the supported resolutions. I couldn't type anything.

OK, so now I shut down, and go back to my original setup, of VGA and PS/2, again attached directly to the system, no KVM. Re-boot, and start KDE. WOW, now KDE is still exhibiting the SAME symptoms. Every key press just cycles through the video resolutions.

My system, hardware wise, is identical to my original setup. I didn't install any additional software, or update any config files, but it's still behaving as it was when I first tried the USB keyboard/mouse.

Just in case, KDE had stored something in $HOME/.kde causing this, I started a 2nd user, that had never started KDE previously. When I started that user, it also had the same issues. So, the problem is "system wide", not user related.

What could have been stored, and where, the time I used the USB keyboard/mouse, that is now causing my PS/2 setup to fail.

Or, how do I go about tracking this down.

Cheers.

any time you change things like that there is two things you can do. One is in run level three as root type xorgsetup and slackware will now load the stock slackware modules and set up the devices. but now your 3d will not work. so as root you type nvidia-xconfig and now it will add acceleration to the xorgconfig by editing it to load the nvidia kernel. now that this is done startx and open nvidia-settings and play with all the stuff you want.

But running those will only set up my xorg.conf. Why would that change this:

I'm running the EXACT same hardware as previously, with EXACTLY the same X configuration files as previously. Something else was changed by switching to the USB keyboard/mouse, that's now haunting me after going back to a PS/2 setup.

Cheers.

OK, after a little more experimentation, this is definitely at a "lower" level than KDE.

If I remove KDE from my system, and just run a "vanilla" X system, with a single xterm, the issue is still present.

So, as a "shell" terminal works normally, I have to assume that it's something at the X level that's controlling this behaviour.

What "settings" could have been changed, when I first used the USB keyboard/mouse that is now affecting a PS/2 keyboard as well.

Cheers.