Bad refresh rate in text-mode after starting X

[D4rw1nAwdW1nn3r]

I have an odd problem with my framebuffer consoles that only shows up after starting X. (Actually, I suspect that the problem shows up after the first video mode change, whatever that may be, but X is the only thing I can think of that would change the video mode.)

Before X starts, I have a fully functional vesafb-tng (vesafb doesn't seem to work with my card) framebuffer console with splash screen, etc., all working perfectly, at the resolution and refresh rate specified in grub.conf (1280x1024-32@75). If I rc-update del xdm and never start X, then the console continues to work fine. Switching VT's works fine.

When X starts, X works perfectly as well using nvidia-drivers, also at 1280x1024-32@75. But now switching to a VT sets the video mode to 1280x1024@85. That is, the refresh rate is set to 85 Hz. My monitor is only rated for 75 Hz, but apparently it obliges 85 Hz for about a minute and then goes blank. During that minute, I can go into the monitor's menu and view the video mode, which is how I know what is happening. Additionally, now switching between VT's causes the screen to go black for a moment as it switches video modes. Before starting X, switching VT's was instantaneous, as usual. Switching back to X is still fine after this. Stopping X does not stop the problem. Like I said, I believe that the problem starts at the first video mode switch and continues until reboot. Oh yeah, any method of starting X causes this problem, not just xdm.

I'm using nvidia-drivers with a Geforce 4 Ti4200, vesafb-tng, suspend2-sources (but I haven't gotten around to making suspend work yet, so I don't think that's the problem). If there's any other information that might be relevant, I can post it.

Things I will try:
- starting X with vga driver instead of nvidia-drivers
- starting X in a different mode from the VT's
- booting without a framebuffer, just to see what happens.
That's all I can think of right now.

If anyone has any idea what would cause this or how to fix it, I would be grateful.

[Annihil4tor]

I got the same problem here. Everything works fine until I start X.
I tried using vesafb and vesafb-tng and got the same problem with both. I don't know if its a nvidia driver problem(that I use in X) or a vesafb problem. Or none =P

[D4rw1nAwdW1nn3r]

I fixed the problem, sort of. I switched from vesafb-tng to vesafb, which didn't have the problem.