| 1 |
On Thu, Jun 19, 2008 at 05:28:50PM +0200, Tonko Mulder wrote: |
| 2 |
> Hello list, |
| 3 |
> |
| 4 |
> I have gentoo installed on my laptop[1] and everything is working fine |
| 5 |
> except for one thing. |
| 6 |
> Every time when I emerge something and even when I don't my laptop |
| 7 |
> first hangs and than the screen goes black. |
| 8 |
> |
| 9 |
> This only happens when I use X, when I'm working with console only it |
| 10 |
> doesn't hang. |
| 11 |
> |
| 12 |
> Does anyone got an idea what's causing this? |
| 13 |
> |
| 14 |
You don't provide a lot of details. The first thing you should confirm |
| 15 |
is whether or not the laptop is actually locking up or just some process |
| 16 |
(like X) is using 100% cpu. To check this you can try a couple of |
| 17 |
things: |
| 18 |
|
| 19 |
1) try to access the laptop from a remote computer. Of course, make sure |
| 20 |
you can access the machine remotely before the machine locks up. I |
| 21 |
normally have ssh running on my machines, but you could use telnet, rsh |
| 22 |
or possibly ftp or http. Just make sure you have the appropriate service |
| 23 |
running on the laptop. |
| 24 |
|
| 25 |
2) Use <CTRL>+<ALT>+<F1> to try and switch from X to a virtual console |
| 26 |
window. |
| 27 |
|
| 28 |
3) If you have ACPI properly setup and responding to the power button, |
| 29 |
you could try pressing the power button < 3 seconds. This should shut |
| 30 |
down the laptop. |
| 31 |
|
| 32 |
If any of these above work when the screen is blank, than the system is |
| 33 |
not locked up. It's likely X or some application is causing X to stop |
| 34 |
responding. If this is the case, you need to figure out what is causing |
| 35 |
the problem. The first thing would be to log in (either through VC or |
| 36 |
ssh) and run the "top" command. This will show what the system is doing |
| 37 |
and how much CPU time each process is using. What to do from here |
| 38 |
depends on whether or not something is using 100% CPU. |
| 39 |
|
| 40 |
If you can not log in or shutdown, then it's possible the machine |
| 41 |
did lock up. Then next steps would be to look in the logs (/var/log) for |
| 42 |
any clues to what may be happening before the system crashes. |
| 43 |
|
| 44 |
|
| 45 |
Is this a new install on new hardware, or was it working fine and just |
| 46 |
started locking up? |
| 47 |
|
| 48 |
It may also be a heat problem. You may want to look in to getting |
| 49 |
lm_sensors or some other tool installed to monitor the system |
| 50 |
temperatures. If could be the CPU or GPU is over heating and either |
| 51 |
stops responding or shuts the system down. |
| 52 |
|
| 53 |
-- |
| 54 |
Brett Johnson |
| 55 |
-- |
| 56 |
gentoo-amd64@l.g.o mailing list |
Archives