LiveCD 2005.1 locks up my system

Message

eivinn · Post by **eivinn** » Thu Oct 13, 2005 12:40 pm

Hi,

I've got a brand new Fic Condor-SB65G2 barebone system with a 3GHz prescott, Geil 1GB PC3200 Dual Channel ram and a serial ata harddrive. After successfully booting the LiveCD my computer starts spewing out

Code: Select all

atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.

I know that this error has something to do with my "Microsoft Wireless Desktop Elite Keyboard", but the difference is that my computer locks up after this. Sometimes it will not even start the monitor afterwards. I feel this is really strange.
Running memtest86 does not return any problems at all and the computer does not stop to respond.

Have you got any suggestions on what to do? Is it the keyboard, overheating, or maybe booth?

To make sure everything is hell the Intel mainboard in the Fic barebone does not show any temperatures or anything. Although overheating should not be a problem as Intel CPU's should have temperature throttling, right?

Hoping to get some help so thanks in advance!

quickshiftin · Post by **quickshiftin** » Thu Oct 13, 2005 1:01 pm

i dont know what the problem is, but if you suspect the wireless keyboard is causing problems why dont you try booting the machine with a ps/2 keyboard instead. if it works then you know that was the problem, if the problem still occurs then you know its not the keyboard.
i doubt overheating has anything to do with it, otherwise i think the machine would shut down
EDIT:
also, have you tried an earlier live cd, like 2005.0?

eivinn · Post by **eivinn** » Thu Oct 13, 2005 2:01 pm

I have now tried installing Windows 2000 and have run CPU burn-in for a 15 minutes without any lock-ups. Had to run to instances to get it to use 100% cpu time. Looks like the cpu is ok.

I'm buying a new keyboard tomorrow so I can have a real go at installing Gentoo. Hopefully that's it

I'll get back to you tomorrow afternoon (Australia time).

eivinn · Post by **eivinn** » Fri Oct 14, 2005 12:40 am

Another development

The Windows 2000 installation spontaneously reboots after a couple of minutes of idle time. When I use it though it works like a charm...

Any suggestions what can cause this?

eivinn · Post by **eivinn** » Fri Oct 14, 2005 8:11 am

Well, after buying an "old" PS/2 keyboard that problem seems to be gone.

But the reboot problems were still there. After some fiddling around I noticed that the Fic cooling to be screwed too tight. At least this is what I think (an uneven motherboard) because it now compiles emerge -e world.

Only problem left is that while it detects both cpu cores it does only compile on one of them even though I have inserted MAKEOPTS="-j3" in make.conf. Strange...

quickshiftin · Post by **quickshiftin** » Fri Oct 14, 2005 2:49 pm

eivinn wrote:Well, after buying an "old" PS/2 keyboard that problem seems to be gone.

But the reboot problems were still there. After some fiddling around I noticed that the Fic cooling to be screwed too tight. At least this is what I think (an uneven motherboard) because it now compiles emerge -e world.

Only problem left is that while it detects both cpu cores it does only compile on one of them even though I have inserted MAKEOPTS="-j3" in make.conf. Strange...

MAKEOPTS="-j3" is a gcc compiler optimization, read the manpage on gcc for details ($man gcc)
to get multiprocessor support you need to enable symetric multiprocessing in the kernel
in the kernel configuration
Processor type and features --->
[*] Symetric multi-processing support