Urgent:Exit The X server & my monitor goes psycho!

[Weedman]

Exactly what it is in the title.

Every time I exit X to the command line, the monitor goes all weird. I don't know whether it is the refresh rate, but it doesn't look like a resolution issue.

Another thing. When the monitor supposably blanks in commandline mode, it plays up too. But I can then at least press a key to make it go back to normal (to wake it up, kinda).

My first suspicion lies with gensplash, although it has worked fine in the past.

I'm desperate!
~the_weedman

[Weedman]

:bump:

This IS driving me mad. I am wondering whether this could be because of the old version of the drivers the gentoo documentation thingy told me to install.

~the_weedman

[antidrugue]

Could be the ATI drivers... it did gave me "similar" trouble when exiting X in the past (now I have an NVIDIA).

You have an ATI video card right?

[Weedman]

Oops. I forgot to mention it in my first post.

I have a Nvidia TNT2 AGP graphics card. Funnily enough, my radeon mobility gpu in my laptop actually works, considering I used the same method of installing for both of the cards. The driver install was the only difference.

Thanks antidrugue for making me clear that up.

~the_weedman

[ausmusj1]

Exactly what it is in the title.

Every time I exit X to the command line, the monitor goes all weird. I don't know whether it is the refresh rate, but it doesn't look like a resolution issue.

Another thing. When the monitor supposably blanks in commandline mode, it plays up too. But I can then at least press a key to make it go back to normal (to wake it up, kinda).

My first suspicion lies with gensplash, although it has worked fine in the past.

I'm desperate!
~the_weedman

Couple'a guesses about your config:

1. You are using the proprietary NVidia drivers
2. You have framebuffer console enabled
3. The in-kernel framebuffer driver you selected was the NVidia one.

If this is the case (this also seems to affect people using ATI cards and the proprietary ATI X driver), for the kernel framebuffer support, deselect your card-specific driver (NVidia, in your case), and use the VESA framebuffer driver - either vesa-tng (much better than the "regular" vesa driver, but only works on 32 bit gentoo-sources x86 kernels), or just the regular vesa driver (if you aren't using a gentoo-sources kernel, or if you're using a 64 bit kernel).

The actual issue is related to the proprietary X driver not playing well with the in-kernel framebuffer driver - they have sharing issues (specifically video memory sharing issues, if *my* memory is working correctly )


HTH-

James

[Weedman]

1. yes
2. yes
3. no

I think that the sheer fact I am using vesa-tng & old NVIDIA drivers (7174), is causing the problem. I think that if i switched to vesabf only, it might work, but I am very short of time.

Thanks for your response ausmusj1

~weed

[ausmusj1]

1. yes
2. yes
3. no

I think that the sheer fact I am using vesa-tng & old NVIDIA drivers (7174), is causing the problem. I think that if i switched to vesabf only, it might work, but I am very short of time.

Thanks for your response ausmusj1

~weed

I have had good luck with recent NVidia drivers (1.0.81* or higher) and vesafb-tng - what happens if you upgrade nvidia-kernel and nvidia-glx?

-James

[Weedman]

I don't think that the 81*+ drivers work with a TNT2.

I can give it a shot though.

[ausmusj1]

I don't think that the 81*+ drivers work with a TNT2.

I can give it a shot though.

Well, theoretically (just checked NVidia's website), TNT2 is still supported under the latest (1.0.8756)... They might not have updated their documentation however - let me know how it goes.

-James

[Weedman]

Thanks A LOT for That.

I will go and get the latest drivers now (while I'm updating everything).