Re: [gentoo-user] xorg-server 1.7.

[Dale <rdalek1967@gmail.com>]

meino.cramer@gmx.de wrote:
> Dale<rdalek1967@gmail.com>  [10-04-10 06:16]:
>    
>> meino.cramer@gmx.de wrote:
>>      
>>> Dale<rdalek1967@gmail.com>   [10-04-10 05:48]:
>>>
>>>        
>>>> meino.cramer@gmx.de wrote:
>>>>
>>>>          
>>>>> Hi Dale,
>>>>>
>>>>> Somne shots into the dark:
>>>>> I am running a non-kde and non-gnome Gentoo here (Openbox is my
>>>>> friend) and after upgrading X nothing works.
>>>>>
>>>>> I rtecompiled openbox, lxpanel and the X11-drivers like
>>>>> xf86-input-keyboard, xf86-input-mouse. nvidia-drivers and
>>>>> everything was ok.
>>>>>
>>>>> Try to recompile the x11-drivers and the kde equivalent of the
>>>>> window manager (I dont know much about kde/gnome...sorry ;) )
>>>>> and may be X11 will be you friend again...
>>>>>
>>>>> HTH!
>>>>>
>>>>> Keep hacking! and have a nice weekend!
>>>>> mcc
>>>>>
>>>>>
>>>>>
>>>>>            
>>>> That makes sense now that you mention it.  I'll give that a try.
>>>> Heck,
>>>> nothing to lose.  I know how to use the sysreq keys pretty good now.
>>>> lol
>>>>
>>>> Thanks.
>>>>
>>>> Dale
>>>>
>>>> :-)  :-)
>>>>
>>>>
>>>>          
>>> Hi Dale,
>>>
>>> to get out of X (or not-so-X in your case :O) ) you dont need the
>>> sysreqs every time. since they are somehow a 'very hard hrmmm
>>> "feature"' ;).
>>>
>>> Look into your Xorg.conf file under /etc/X11 and look for "dont zap"
>>> or something like that (I removed this from my xorg.conf ;) ) and
>>> remove that (or better comment it out).
>>>
>>> After that you kann kill X without disturbing the kernel (and risk
>>> your data) with ALT-Backspace. You will get back a console. Log in
>>> as root and do a "telinit 2" since the setuo still think of running
>>> runlevel 5 "without X" and this is not a sane setup: Runlevel 5 is
>>> "with X" and runlevel 2 is "without X".
>>> To restart X the clean way do "teleinit 5" as root.
>>>
>>> HTH
>>>
>>> Keep hacking!
>>> mcc
>>>
>>>
>>>        
>> Well when it locks up hard, nothing works not even sysreq.  That was
>> the first time it failed me.  I'm not sure what made it lock up tho.
>>
>> Oh, ctrl alt backspace doesn't do anything either.
>>
>> Dale
>>
>> :-)  :-)
>>
>>      
> Hi Dale,
>
> you have to remove this "Dont Zap"-Option from your xorg.conf first.
> Should work then.
> But of course: If a busmaster (in this case your GraphicsCard) doesnot
> release the bus...no way for little folks little some tiny keys
> on the keyboard... ;)
>
> Keep hacking!
> mcc
>    

I got rid of that a long time ago.  I like to be able to switch when 
needed.  I'm the only one on this rig so its not a security issue for me.

I got the original issue solved.  I emerged everything installed in 
x11-drivers/* and it works fine.  I guess I missed something in the list 
earlier.

I now have a new problem to solve.  I mentioned this before but now it 
is a system killer.  I boot the system, log into KDE as usual then log 
out.  Instead of going back to kdm, the screen goes black and sits 
there.  I thought maybe it was busy or something so I let it sit for 
about 10 minutes.  It never did anything.  The monitor stays on so it is 
getting some sort of a signal.

Also, ctrl alt F* keys do nothing.  They work elsewhere but not when it 
locks up.  The only way to do anything is to go through the whole sysreq 
set until the system reboots.  Then the process repeats.  I can boot up, 
the services start fine, I can even log in but once I log out, it locks 
up with nothing on the screen.

Anybody have a clue what could cause this?

I searched the logs in /var/log and found this:

(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
(EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX 
module.  If
(EE) NVIDIA(0):     you continue to encounter problems, Please try
(EE) NVIDIA(0):     reinstalling the NVIDIA driver.
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 (NV34) at PCI:2:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 04.34.20.23.00
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:2:0:0:
(--) NVIDIA(0):     Gateway EV910 (CRT-0)
(--) NVIDIA(0): Gateway EV910 (CRT-0): 350.0 MHz maximum pixel clock
(WW) NVIDIA(0): The EDID for Gateway EV910 (CRT-0) contradicts itself: mode
(WW) NVIDIA(0):     "720x405" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0):     valid HorizSync range (30.000-95.000 kHz) would exclude
(WW) NVIDIA(0):     this mode's HorizSync (29.5 kHz); ignoring HorizSync 
check
(WW) NVIDIA(0):     for mode "720x405".
(II) NVIDIA(0): Assigned Display Device: CRT-0


I searched the forums and it appears this is a known issue.  Going back 
to the older xorg is one solution according to what I read.  If anyone 
has a sure fire fix, I'd be willing to fix but otherwise, I'm back 
tracking.

Dale

:-)  :-)