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