I haven't encountered this but since all this developed after the re-install then there is a need to look at what could have happened at this stage.

You will remember that the Linux kernel depends on the BIOS to be in control of the hardware so did anything happen in the BIOS before you re-installed?

The other thing, did you reformat the partition before re-installing? I always re-read the partition information and then always format the linux partition (I dual boot at the moment) before re-installing. This ensures that there is no crud sitting around.

There were no BIOS changes made between the first install and the re-install. The upgrade path was like this. 1. I had a working AMD2000+ on a Gigabyte MB with 1GB of ram and the nVidia6600GT. I installed 10.1 (32bit mode with a regular kernel) on this hardware. Other than the known wobbly bits with Zen/Rug, 10.1 was working fine. 2. I bought a new CPU (AMD X2 3800+), new MB (ASRock S939 - chosen because I can reuse a lot of my older hardware with this board and still get a dual core CPU) and 1 more GB of ram. 3. I swapped the hardware around, and set things back up again - installed Windows in a small partition that was reformatted, and then re-installed 10.1 after formatting /. I did not reformat my /home partition... just reused it (which was reused from 10.0 etc). I chose to re-install 10.1 vs just changing to an SMP kernel because I wanted to start with a clean slate again. 4. Booted up and things worked fine. I started tinkering and playing to see what new things I could do with the dual core CPU. In the process of doing this, I tend to break a few things, remove apps, add apps etc. Basically experimenting. All along the OS performed nicely. 5. I decide I want to re-install just to give me a clean start since I was done playing about in the OS and needed to bring it all back to a useable state after all my tinkering. I reformat / and install (do not reformat /home) and do all the updated as needed on the install. 6. I boot up, and the OS is effectively unusable. I get the insane keyboard repeat thing, random hibernate/sleeps etc. 7. I figure I've done something silly during the install. I backup my /home, and do a complete clean install including reformatting the /home and / partitions. The install is the preselected base install with the addition of gcc and the kernel sources (so I can install the nVidia driver). 8. Boot up... keyboard is still on it's insane repeat, and I get random hibernates/sleeps. After a little troubleshooting I do get things into a useable state. First I discover that it's only as $USER in KDE that the keyboard is on hyper-repeat. If I am running as root on tty1, everything works fine (ie no keyboard repeats). I still get the odd hibernate happen - and there is an entry in my messages log that says that "the computer is going to sleep now" for each instance. If it gets into the hibernate mode, the only way to wake it up is a hard reset. I can "interrupt" the sleep mode by moving the mouse. Using the keyboard has no impact on cancelling the hibernate. The only thing I can think of that really changed between the first install and the second is the kernel. There was a kernel update that happened between the first install and the second. I have not yet rolled back the kernel. I figured that if it was the kernel then there would be a bit of a ruckus on the mailing list :-) and it's been quiet. Anyway, after a while - couple hours - things settle down and the OS behaves more or less normally. No more random hibernates... and the keyboard seems to settle into a manageable state - although... if I turn the KDE keyboard repeat back on I still do occasionally get 50 or 60 letters in a row when I try to type something. This got em to thinking maybe it was Beagle... so I disable it as a service, kill Kerry, and make sure there are no more Beagle processes running... and it makes no difference to the system behavior. Nothing in /var/log/messages looks out of place. Nothing looks out of place in the kernel log either. I've watched "top" to see what processes are using up CPU time... and X sits at about 5%, and there are a few others that use up another 5 or 10% CPU time... that's it.. nothing in wait, nothing chewing up 100% of either CPU ... So in the end.. I've still got a problem with the computer... a couple hours after booting it settles into a semi useable state. C. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Are you sure your keyboard hasn't gone bad? Does it also maybe have a sleep button that could also cause the hibernate problem?

Good suggestion, but I checked that... If I am logged in as root (in tty1 for example or even in a terminal window within the KDE UI) the keyboard repeat does not happen, only happens as $USER (including with a newly created user)... I've also checked in my Windows partition, and everything is fine there. The keyboard is a Cherry Linux keyboard, but I do not have the keyboard drivers installed in Linux at the moment... so none of the extra (Linux centric) keys are functioning. As far as I know there is no hibernate or sleep button, or a combination of buttons on this keyboard that can initiate a hibernate... especially without the Keytouch drivers installed. C. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com