View previous topic :: View next topic |
Author |
Message |
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
Posted: Thu Feb 16, 2006 11:48 pm Post subject: monitor blanks when switching from X to vt with framebuffer |
|
|
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 |
|
Back to top |
|
|
rodoke Tux's lil' helper
Joined: 01 Jan 2005 Posts: 87 Location: So. Ill.
|
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. _________________
Bill Watterson wrote: | If we wanted more leisure, we'd invent machines that do things less efficiently. |
|
|
Back to top |
|
|
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
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 |
|
Back to top |
|
|
gerard27 Advocate
Joined: 04 Jan 2004 Posts: 2377 Location: Netherlands
|
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. |
|
Back to top |
|
|
Drunkula Apprentice
Joined: 28 Jul 2003 Posts: 257 Location: Denton, TX - USA
|
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. |
|
Back to top |
|
|
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
Posted: Sat Feb 18, 2006 11:12 am Post subject: |
|
|
Gerard van Vuuren wrote: | As far as I know from this forums you should not use framebuffers with nvidia. |
It has always been working. I think I'll try the nv framebuffer driver instead of vesafb-tng today.
Drunkula wrote: | I hear that adding Load "int10" to the modules section of your xorg.conf file will help with this situation. |
Thanks for help, but it behaves the same for me. _________________ What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast |
|
Back to top |
|
|
tboloo Guru
Joined: 20 Jan 2006 Posts: 403 Location: Grodzisq, Poland
|
Posted: Sat Feb 18, 2006 11:18 am Post subject: |
|
|
Make sure that you have your agp module loaded, eg
Code: |
/etc/modules.autoload.d/kernel-2.6
agpgart
intel-agp
fglrx
|
it worked for me. |
|
Back to top |
|
|
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
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:
Code: |
kernel /boot/kernel-2.6.15-gentoo-r5 root=/dev/hda7 vga=792 splash=silent,theme:livecd-2005.1 CONSOLE=/dev/tty1
|
Code: |
kernel /boot/kernel-2.6.15-gentoo-r5-vesafbtng root=/dev/hda7 video=vesafb:mtrr,ywrap,1024x768-32@75 splash=silent,theme:livecd-2005.1 CONSOLE=/dev/tty1
|
But I'm happy now, I can see no difference between vesafb-tng and vesafb. _________________ What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast |
|
Back to top |
|
|
|