1 |
On Fri, Jun 22, 2012 at 2:04 PM, Willie <matthews.willie@×××××.com> wrote: |
2 |
> On Fri, Jun 22, 2012 at 11:46 AM, Paul Hartman |
3 |
> <paul.hartman+gentoo@×××××.com> wrote: |
4 |
>> |
5 |
>> On Fri, Jun 22, 2012 at 11:20 AM, Willie <matthews.willie@×××××.com> |
6 |
>> wrote: |
7 |
>> > Hi All, |
8 |
>> > |
9 |
>> > I have been running a gentoo box for quite some time without a desktop |
10 |
>> > manager. Did a lot of upgrading in between time also. The problem I am |
11 |
>> > having is when I login I can't open any Windows. The only one that has |
12 |
>> > open |
13 |
>> > without crashing the entire computer that I know of is VLC. |
14 |
>> > |
15 |
>> > Any help is greatly appreciated. |
16 |
>> |
17 |
>> Be sure to "emerge --oneshot @x11-module-rebuild" after upgrading xorg |
18 |
>> stuff. Drivers might be out of sync and maybe that's causing your |
19 |
>> pain. |
20 |
>> |
21 |
>> Try to delete/rename your /etc/X11/xorg.conf and see if that makes a |
22 |
>> difference. Modern Xorg can start a basic environment without it. |
23 |
>> |
24 |
>> Try to run "startx" as a user instead of using xdm and see if you get |
25 |
>> any better errors/logs. |
26 |
>> |
27 |
>> If you have another computer/device SSH into your problematic computer |
28 |
>> before starting X so you can see if it's still alive, just |
29 |
>> unresponsive at the local terminal. Maybe then you can see logs and |
30 |
>> stuff. |
31 |
>> |
32 |
>> revdep-rebuild just to ensure everything is consistent on your system. |
33 |
>> |
34 |
> |
35 |
> I rebuild all of my x11-drivers it rebuild the nvidia driver along with a |
36 |
> couple of others. |
37 |
> |
38 |
> I used startx and got the errors below. I have a feeling it has something to |
39 |
> do with my nVidia card (Geforce 8400GS) |
40 |
> |
41 |
> SSH is not active anymore. It is also the computer that shares the internet |
42 |
> and no one can access the internet either. |
43 |
> |
44 |
> Okay now I think we are getting somewhere. Didn't think to leave XDM out but |
45 |
> I did do it. It still froze but I got some useful information soon as it did |
46 |
> freeze. This is from /var/log/messages |
47 |
> |
48 |
> Jun 22 11:52:52 beast kernel: NVRM: Xid (0000:02:00): 6, PE0001 |
49 |
> Jun 22 11:52:54 beast kernel: NVRM: os_schedule: Attempted to yield the CPU |
50 |
> while in atomic or interrupt context |
51 |
> Jun 22 11:52:54 beast kernel: NVRM: Xid (0000:02:00): 3, C 00000002 SC |
52 |
> 00000003 M 00000100 Data 00000000 |
53 |
> Jun 22 11:53:03 beast kernel: NVRM: os_schedule: Attempted to yield the CPU |
54 |
> while in atomic or interrupt context |
55 |
> Jun 22 11:53:05 beast kernel: NVRM: os_schedule: Attempted to yield the CPU |
56 |
> while in atomic or interrupt context |
57 |
> Jun 22 11:53:08 beast kernel: NVRM: os_schedule: Attempted to yield the CPU |
58 |
> while in atomic or interrupt context |
59 |
> |
60 |
> That was printed as soon as XFCE froze. |
61 |
|
62 |
Okay, now I googled those errors and it seems to be a fairly common |
63 |
problem. The workaround I saw is to add "nolapic_timer" to your kernel |
64 |
commandline. Try that, reboot and cross your fingers. ;) |