monitor blanks when switching from X to vt with framebuffer

zaiyon

Hi, I'm using the vesafb-tng framebuffer, and it all works allright.

But if I startx and then switch back to a vt, the monitor looses signal and never gains it again until the computer is shut down.

I have an nvidia card (tried both "nv" and "nvidia" as a driver, with the same results), am using a fresh gentoo 2005.1 stage3 installation and gcc 3.4.4 with gentoo kernel sources 2.6.15-r5. Any ideas on how to get rid of this?
_________________
What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast

rodoke · Posted: Fri Feb 17, 2006 6:08 am Post subject:

Just curious, what happens if you try to change back to X?

I just had a similar problem after switching my x.org resolution to 1600x1200. My monitor would complain about out-of-spec refresh rates and go to sleep. The thing that fixed mine was by changing the resolution lines in grub.conf to start at 1600x1200-32@75 as well.

HTH.
_________________

zaiyon · Posted: Fri Feb 17, 2006 12:02 pm Post subject:

that's what I mean with "never gains it again", even if I switch back to X, the monitor is blank.

I have a sony multiscan s72 (or something similair

) and he doesn't show up _what_ the problem is.

My framebuffer runs with 1024x768-32@75, while my X is configured to have 1280x960-24 (don't know the hertz)

But it always worked set up like this - some kernel changes perhaps? I'll try a 2.6.12 if I find one (that was the last kernel I used before 2.6.15)
_________________
What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast

gerard27 · Posted: Fri Feb 17, 2006 12:40 pm Post subject:

As far as I know from this forums you should not use framebuffers with nvidia.

Drunkula · Posted: Fri Feb 17, 2006 1:40 pm Post subject:

I can't confirm it but I hear that adding Load "int10" to the modules section of your xorg.conf file will help with this situation. Couldn't hurt to try!
_________________
Go away or I will replace you with a very small shell script.

zaiyon · Posted: Sat Feb 18, 2006 11:12 am Post subject:

tboloo · Posted: Sat Feb 18, 2006 11:18 am Post subject:

Make sure that you have your agp module loaded, eg

zaiyon · Posted: Sat Feb 18, 2006 12:09 pm Post subject:

Switching from vesafb to vesafb-tng did the trick for me, though I don't really understand why.
Is my kernel line for vesafb-tng perhaps wrong?

My graphics card shouldn't be too old ... I mean, it's a Nvidia GeForce Ti 4200, quite antique for gamers, but notice the fact that the nvidia "TNT" chipset is listed as new in the current kernel.

Here go my kernel lines: