| 1 |
Luke-Jr wrote: |
| 2 |
> On Friday 29 October 2004 7:57 pm, Robert Zwerus wrote: |
| 3 |
> |
| 4 |
>>Mark Knecht wrote: |
| 5 |
>> |
| 6 |
>>> My crashes are not complete. I am ssh'ed into the machine and can |
| 7 |
>>>actually reboot it cleanly. The crash is apparently only X for me. |
| 8 |
>> |
| 9 |
>>Try entering these commands in the SSH session: |
| 10 |
>>export DISPLAY=:0 |
| 11 |
>>startx |
| 12 |
>> |
| 13 |
>>Maybe your graphics chip just needs to be reset, startx will take care |
| 14 |
>>of that. |
| 15 |
> |
| 16 |
> |
| 17 |
> startx will take care of the DISPLAY variable also. In normal situations, it's |
| 18 |
> fairly rare that you ever need to set it manually. |
| 19 |
> Anyway, if it's the same issue I've encountered (which it seems to be), and |
| 20 |
> IIRC, this won't help anything. |
| 21 |
|
| 22 |
I had another crash this morning. Screen, keyboard and mouse were hung. |
| 23 |
(DRI is still installed - possibly incorrectly) |
| 24 |
|
| 25 |
I was able to log in remotely, su to root, rmmod radeon, modprobe radeon |
| 26 |
and startx as root. The screen came back up. I then killed my new X |
| 27 |
environment and the system came back alive. |
| 28 |
|
| 29 |
This isn't a good solution as I do not always have a remote system to do |
| 30 |
this from, but at least it gets me back in control without a power cycle |
| 31 |
and fsck. |
| 32 |
|
| 33 |
Thanks, |
| 34 |
Mark |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-desktop@g.o mailing list |
Archives