1 |
meino.cramer@×××.de wrote: |
2 |
> Dale<rdalek1967@×××××.com> [10-04-10 06:16]: |
3 |
> |
4 |
>> meino.cramer@×××.de wrote: |
5 |
>> |
6 |
>>> Dale<rdalek1967@×××××.com> [10-04-10 05:48]: |
7 |
>>> |
8 |
>>> |
9 |
>>>> meino.cramer@×××.de wrote: |
10 |
>>>> |
11 |
>>>> |
12 |
>>>>> Hi Dale, |
13 |
>>>>> |
14 |
>>>>> Somne shots into the dark: |
15 |
>>>>> I am running a non-kde and non-gnome Gentoo here (Openbox is my |
16 |
>>>>> friend) and after upgrading X nothing works. |
17 |
>>>>> |
18 |
>>>>> I rtecompiled openbox, lxpanel and the X11-drivers like |
19 |
>>>>> xf86-input-keyboard, xf86-input-mouse. nvidia-drivers and |
20 |
>>>>> everything was ok. |
21 |
>>>>> |
22 |
>>>>> Try to recompile the x11-drivers and the kde equivalent of the |
23 |
>>>>> window manager (I dont know much about kde/gnome...sorry ;) ) |
24 |
>>>>> and may be X11 will be you friend again... |
25 |
>>>>> |
26 |
>>>>> HTH! |
27 |
>>>>> |
28 |
>>>>> Keep hacking! and have a nice weekend! |
29 |
>>>>> mcc |
30 |
>>>>> |
31 |
>>>>> |
32 |
>>>>> |
33 |
>>>>> |
34 |
>>>> That makes sense now that you mention it. I'll give that a try. |
35 |
>>>> Heck, |
36 |
>>>> nothing to lose. I know how to use the sysreq keys pretty good now. |
37 |
>>>> lol |
38 |
>>>> |
39 |
>>>> Thanks. |
40 |
>>>> |
41 |
>>>> Dale |
42 |
>>>> |
43 |
>>>> :-) :-) |
44 |
>>>> |
45 |
>>>> |
46 |
>>>> |
47 |
>>> Hi Dale, |
48 |
>>> |
49 |
>>> to get out of X (or not-so-X in your case :O) ) you dont need the |
50 |
>>> sysreqs every time. since they are somehow a 'very hard hrmmm |
51 |
>>> "feature"' ;). |
52 |
>>> |
53 |
>>> Look into your Xorg.conf file under /etc/X11 and look for "dont zap" |
54 |
>>> or something like that (I removed this from my xorg.conf ;) ) and |
55 |
>>> remove that (or better comment it out). |
56 |
>>> |
57 |
>>> After that you kann kill X without disturbing the kernel (and risk |
58 |
>>> your data) with ALT-Backspace. You will get back a console. Log in |
59 |
>>> as root and do a "telinit 2" since the setuo still think of running |
60 |
>>> runlevel 5 "without X" and this is not a sane setup: Runlevel 5 is |
61 |
>>> "with X" and runlevel 2 is "without X". |
62 |
>>> To restart X the clean way do "teleinit 5" as root. |
63 |
>>> |
64 |
>>> HTH |
65 |
>>> |
66 |
>>> Keep hacking! |
67 |
>>> mcc |
68 |
>>> |
69 |
>>> |
70 |
>>> |
71 |
>> Well when it locks up hard, nothing works not even sysreq. That was |
72 |
>> the first time it failed me. I'm not sure what made it lock up tho. |
73 |
>> |
74 |
>> Oh, ctrl alt backspace doesn't do anything either. |
75 |
>> |
76 |
>> Dale |
77 |
>> |
78 |
>> :-) :-) |
79 |
>> |
80 |
>> |
81 |
> Hi Dale, |
82 |
> |
83 |
> you have to remove this "Dont Zap"-Option from your xorg.conf first. |
84 |
> Should work then. |
85 |
> But of course: If a busmaster (in this case your GraphicsCard) doesnot |
86 |
> release the bus...no way for little folks little some tiny keys |
87 |
> on the keyboard... ;) |
88 |
> |
89 |
> Keep hacking! |
90 |
> mcc |
91 |
> |
92 |
|
93 |
I got rid of that a long time ago. I like to be able to switch when |
94 |
needed. I'm the only one on this rig so its not a security issue for me. |
95 |
|
96 |
I got the original issue solved. I emerged everything installed in |
97 |
x11-drivers/* and it works fine. I guess I missed something in the list |
98 |
earlier. |
99 |
|
100 |
I now have a new problem to solve. I mentioned this before but now it |
101 |
is a system killer. I boot the system, log into KDE as usual then log |
102 |
out. Instead of going back to kdm, the screen goes black and sits |
103 |
there. I thought maybe it was busy or something so I let it sit for |
104 |
about 10 minutes. It never did anything. The monitor stays on so it is |
105 |
getting some sort of a signal. |
106 |
|
107 |
Also, ctrl alt F* keys do nothing. They work elsewhere but not when it |
108 |
locks up. The only way to do anything is to go through the whole sysreq |
109 |
set until the system reboots. Then the process repeats. I can boot up, |
110 |
the services start fine, I can even log in but once I log out, it locks |
111 |
up with nothing on the screen. |
112 |
|
113 |
Anybody have a clue what could cause this? |
114 |
|
115 |
I searched the logs in /var/log and found this: |
116 |
|
117 |
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X |
118 |
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X |
119 |
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX |
120 |
module. If |
121 |
(EE) NVIDIA(0): you continue to encounter problems, Please try |
122 |
(EE) NVIDIA(0): reinstalling the NVIDIA driver. |
123 |
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 (NV34) at PCI:2:0:0 (GPU-0) |
124 |
(--) NVIDIA(0): Memory: 131072 kBytes |
125 |
(--) NVIDIA(0): VideoBIOS: 04.34.20.23.00 |
126 |
(II) NVIDIA(0): Detected AGP rate: 8X |
127 |
(--) NVIDIA(0): Interlaced video modes are supported on this GPU |
128 |
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:2:0:0: |
129 |
(--) NVIDIA(0): Gateway EV910 (CRT-0) |
130 |
(--) NVIDIA(0): Gateway EV910 (CRT-0): 350.0 MHz maximum pixel clock |
131 |
(WW) NVIDIA(0): The EDID for Gateway EV910 (CRT-0) contradicts itself: mode |
132 |
(WW) NVIDIA(0): "720x405" is specified in the EDID; however, the EDID's |
133 |
(WW) NVIDIA(0): valid HorizSync range (30.000-95.000 kHz) would exclude |
134 |
(WW) NVIDIA(0): this mode's HorizSync (29.5 kHz); ignoring HorizSync |
135 |
check |
136 |
(WW) NVIDIA(0): for mode "720x405". |
137 |
(II) NVIDIA(0): Assigned Display Device: CRT-0 |
138 |
|
139 |
|
140 |
I searched the forums and it appears this is a known issue. Going back |
141 |
to the older xorg is one solution according to what I read. If anyone |
142 |
has a sure fire fix, I'd be willing to fix but otherwise, I'm back |
143 |
tracking. |
144 |
|
145 |
Dale |
146 |
|
147 |
:-) :-) |