can not emerge xorg-x11 after unmerge

stissing · n00b Joined: 15 Mar 2005 Posts: 2

i tried to get my system up to date doing a emerge -uD world, but this wasn't possible since firefox and xorg-x11 were blocking, so i unmerged both of them. then i tried to reemerge x11 but this made the computer turn off. The same happens now whenever i try to emerge x11.

i can emerge other programs, but just not x11 - this always makes the computer turn off

i am afraid i don't know what else to report, but many thanks in advance, if anyone knows what could cause this trouble

hjnenc · Posted: Tue Mar 15, 2005 5:49 pm Post subject:

Could it be that your CPU gets too hot and the computer turns off because of this? xorg-x11 takes some time to compile and this may distinguish it from other packages.

Gentree · Posted: Tue Mar 15, 2005 9:21 pm Post subject:

yep , that would seem to be the most likely cause of a system just turning off.

You should check your hardware . run some memtest86+ then set up temperature sensors (it seems you dont have this) then , and only then try emerge cpuburn and try some of those tools .

HTH

_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86

stissing · n00b Joined: 15 Mar 2005 Posts: 2

thanks a lot guys,

right now i'm doing a memtest86plus and apparently it has found one error in my memory, not really sure what it means,

does this suggest that i should repair my laptop or is such a single error nothing serious?

about the temperature sensors i'm not really sure what to do,

many thanks in advance

hjnenc · Posted: Wed Mar 16, 2005 4:59 pm Post subject:

Memory errors are always serious. Whenever that memory location is used you will have some kind of error. It depends on the application that uses that memory how this error will show up. This can range from crashes to wrong results.

Gentree · Posted: Wed Mar 16, 2005 7:01 pm Post subject:

If memtest consistantly shows the error at the same localtion it is almost certainly a flakey mem bar.

If you have several , try to determine which one is failing and pull it out.

If it shows at different addresses it may be a bus prob or other component so you'll need to do some further tests.

You could try slowing the system or using some o/c type techniqies such as upping voltages but you need to know what you/re doing in the latter case and it sounds like you would have to read up a bit first.

If you do slow it and it seems to work give it an overnight test but you'd be skating on thin ice .

Best choise is new memory if you can.

HTH

_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86