| View previous topic :: View next topic |
| Author |
Message |
deadeyes
Tux's lil' helper
Joined: 25 May 2007
Posts: 83
|
 Posted: Sat Feb 27, 2010 3:17 pm Post subject: nvidia-drivers and framebuffer in decent resolution |
 |
|
Hi all,
Sorry for creating another thread on this forum about framebuffers.
I am trying to get a decent resolution on my laptop.
I am having a Dell M4300. The graphics card is this:
01:00.0 VGA compatible controller: nVidia Corporation Quadro FX 360M (rev a1)
I am using nvidia-drivers for X.
Now I want to get instead of the giant characters on the console some smaller ones.
If I am correct I need a framebuffer for that.
After alot of searching I decided to go with the vesafb (I don't want v68d with klibc) and I read uvesafb does not work together with nvidia-drivers.
Now I have vesafb support compiled into the kernel and still am not able to get a decent resolution.
When I do vga=ask I can select a mode and that changes the size.
But after a few services are booted, I get the old size again.
Do note that the size is still sh***y.
I tried something like this in menu.lst:
kernel /boot/vmlinuz video=vesafb:ywrap,mtrr:3 vga=ask
I tried different things.
Can someone tell me what is best to use? I dont want to go away from nvidia-drivers.
Also what kind of grub kernel line should I use?
Is it possible to get 1680x1050 in any way?
I can't understand why after a few years this is still such a mess to get working.
Thanks in advance for your help! |
|
| Back to top |
|
 |
loftwyr
l33t
Joined: 29 Dec 2004
Posts: 970
Location: 43°38'23.62"N 79°27'8.60"W
|
| Posted: Sat Feb 27, 2010 3:29 pm Post subject: |
|
|
uvesafb is what you want.
you can find full instructions in the forums.
_________________
My emerge --info
Have you run revdep-rebuild lately? It's in gentoolkit and it's worth a shot if things don't work well.
Celebrating 5 years of Gentoo-ing. |
|
| Back to top |
|
|
geki
Advocate
Joined: 13 May 2004
Posts: 2387
Location: Germania
|
| Posted: Sat Feb 27, 2010 3:37 pm Post subject: |
|
|
deadeyes
you can find information at various websites. but I had to search quite some time, too.
I have this kernel config in grub.conf for vesafb. 1280er or 1024er resolution, I do not remember. ^^
| Quote: | | video=vesafb:mtrr:3,ywrap vga=0x317 |
and a 8x9 consolefont to get the text tiny. 
| Quote: | $ grep ^consolefont /etc/conf.d/consolefont
consolefont="default8x9" |
with this the text is very small on my 1600x1200 resolution.
_________________
hear hear
Last edited by geki on Sun Feb 28, 2010 12:09 am; edited 1 time in total |
|
| Back to top |
|
|
deadeyes
Tux's lil' helper
Joined: 25 May 2007
Posts: 83
|
| Posted: Sat Feb 27, 2010 10:01 pm Post subject: |
|
|
| loftwyr wrote: | uvesafb is what you want.
you can find full instructions in the forums. |
I have read this is more flexible but also does not work well with nvidia-drivers (proprietary)
Thanks geki, I will try that. |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Sun Feb 28, 2010 12:01 am Post subject: |
|
|
vesafb is usually fine to get native resolution. You just need to find a code for it, and for non-standard modes it depends on manufacturer and a card.
Download something like vbespy to find what framebuffer modes your card supports and convert the code you see into vesafb code
by adding 512 and converting to hex.
For example, my NVIDIA card supports 1680x1050 in 8x8x8 true color under the code 361 according to vbetest (part of vbespy).
My kernel line reads
video=vesafb:ypan,vga=0x369
where 369 is obtained as 361+512=873 converted into hex (873 = 0x369)
on my laptop, the same mode means completely different thing ! |
|
| Back to top |
|
|
loftwyr
l33t
Joined: 29 Dec 2004
Posts: 970
Location: 43°38'23.62"N 79°27'8.60"W
|
| Posted: Sun Feb 28, 2010 3:20 pm Post subject: |
|
|
| deadeyes wrote: | | loftwyr wrote: | uvesafb is what you want.
you can find full instructions in the forums. |
I have read this is more flexible but also does not work well with nvidia-drivers (proprietary)
Thanks geki, I will try that. |
I've been using uvesafb for a long time wiht nvidia-drivers and have had no problem. My kernel line is: video=uvesafb:1920x1200-32,mtrr:3,ywrap
_________________
My emerge --info
Have you run revdep-rebuild lately? It's in gentoolkit and it's worth a shot if things don't work well.
Celebrating 5 years of Gentoo-ing. |
|
| Back to top |
|
|
deadeyes
Tux's lil' helper
Joined: 25 May 2007
Posts: 83
|
| Posted: Tue Mar 02, 2010 10:39 am Post subject: |
|
|
| dmpogo wrote: | vesafb is usually fine to get native resolution. You just need to find a code for it, and for non-standard modes it depends on manufacturer and a card.
Download something like vbespy to find what framebuffer modes your card supports and convert the code you see into vesafb code
by adding 512 and converting to hex.
For example, my NVIDIA card supports 1680x1050 in 8x8x8 true color under the code 361 according to vbetest (part of vbespy).
My kernel line reads
video=vesafb:ypan,vga=0x369
where 369 is obtained as 361+512=873 converted into hex (873 = 0x369)
on my laptop, the same mode means completely different thing ! |
This does not seem to work for me  did tried the vbetest and stuff without luck.
I got really weird image on the screen.
So seems I will have to go with emerging some more packages :S |
|
| Back to top |
|
|
xaviermiller
Bodhisattva
Joined: 23 Jul 2004
Posts: 8708
Location: ~Brussels - Belgique
|
| Posted: Tue Mar 02, 2010 10:56 am Post subject: |
|
|
Hello,
I used uvesafb until kernel 2.6.32.
Now, I take a chance to nv and nouveau.
_________________
Kind regards,
Xavier Miller |
|
| Back to top |
|
|
i92guboj
Bodhisattva
Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)
|
| Posted: Tue Mar 02, 2010 11:23 am Post subject: |
|
|
| uvesafb is better for most purposes. Besides that, you have no option if you are not using x86 because the regular vesa fb driver doesn't support any other architecture (that sorts out amd64 as well). uvesafb used to work well with nvidia-drivers. I haven't used those for some time, though. |
|
| Back to top |
|
|
geki
Advocate
Joined: 13 May 2004
Posts: 2387
Location: Germania
|
| Posted: Tue Mar 02, 2010 12:45 pm Post subject: |
|
|
interesting, my amd64 box runs fine with vesafb. 
_________________
hear hear |
|
| Back to top |
|
|
xaviermiller
Bodhisattva
Joined: 23 Jul 2004
Posts: 8708
Location: ~Brussels - Belgique
|
| Posted: Tue Mar 02, 2010 12:47 pm Post subject: |
|
|
uvesafb works fine in AMD64, using a v86d initrd.
_________________
Kind regards,
Xavier Miller |
|
| Back to top |
|
|
i92guboj
Bodhisattva
Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)
|
| Posted: Tue Mar 02, 2010 1:43 pm Post subject: |
|
|
| geki wrote: | | interesting, my amd64 box runs fine with vesafb. |
An x64-able cpu doesn't imply an x86_64 OS. You are probably running a 32 bits kernel. I don't think that vesafb works on a 64 bit kernel at all. Just look at the kernel info:
| Code: | Symbol: FB_VESA [=n]
Prompt: VESA VGA graphics support
Defined at drivers/video/Kconfig:708
Depends on: HAS_IOMEM [=y] && FB [=y]=y [=y] && X86 [=y]
Location:
-> Device Drivers
-> Graphics support
-> Support for frame buffer devices (FB [=y])
Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGEBLIT [=y] && FB_BOOT_VESA_SUPPORT [=n]
|
And see that one of the requisites for this option to be available (Depends on) is "X86". In fact, one of the reasons why uvesafb was created was the fact that there wasn't a viable option to do framebuffer on x86_64 installations. |
|
| Back to top |
|
|
xaviermiller
Bodhisattva
Joined: 23 Jul 2004
Posts: 8708
Location: ~Brussels - Belgique
|
| Posted: Tue Mar 02, 2010 1:50 pm Post subject: |
|
|
My kernel is 64 bits, and I run uvesafb 
I only need v86d and it rocks !
_________________
Kind regards,
Xavier Miller |
|
| Back to top |
|
|
geki
Advocate
Joined: 13 May 2004
Posts: 2387
Location: Germania
|
| Posted: Tue Mar 02, 2010 3:23 pm Post subject: |
|
|
| i92guboj wrote: | | geki wrote: | | interesting, my amd64 box runs fine with vesafb. |
An x64-able cpu doesn't imply an x86_64 OS. You are probably running a 32 bits kernel. I don't think that vesafb works on a 64 bit kernel at all. Just look at the kernel info:
| Code: | Symbol: FB_VESA [=n]
Prompt: VESA VGA graphics support
Defined at drivers/video/Kconfig:708
Depends on: HAS_IOMEM [=y] && FB [=y]=y [=y] && X86 [=y]
Location:
-> Device Drivers
-> Graphics support
-> Support for frame buffer devices (FB [=y])
Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGEBLIT [=y] && FB_BOOT_VESA_SUPPORT [=n]
|
And see that one of the requisites for this option to be available (Depends on) is "X86". In fact, one of the reasons why uvesafb was created was the fact that there wasn't a viable option to do framebuffer on x86_64 installations. |
wrong. this is a clean amd64 system. and that X86 mark is just fine with an amd64 box. do not mix amd64 with ia64.
amd64 is just a 32bit system with an invasive extension, yes, but still 32bit deep inside somewhere hidden.
_________________
hear hear |
|
| Back to top |
|
|
deadeyes
Tux's lil' helper
Joined: 25 May 2007
Posts: 83
|
| Posted: Tue Mar 02, 2010 7:31 pm Post subject: |
|
|
I used v86d and uvesafb. Now I do have my normal resolution at the framebuffer  (although I had liked it to be easier instead of emerging stuff, compiling kernel and an initramfs).
A few seconds at boot I still have the big letters but that is normal IIRC? |
|
| Back to top |
|
|
-Vortex-
n00b
Joined: 28 Feb 2005
Posts: 13
Location: Modena, Italy
|
| Posted: Wed Mar 03, 2010 1:43 pm Post subject: |
|
|
Hi,
I have this video card:
| Code: | | 01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GTS 512] (rev a2) |
I ran vbetest and it gave me the following modes:
| Code: |
[256] 640x400 (256 color palette)
[257] 640x480 (256 color palette)
[259] 800x600 (256 color palette)
[261] 1024x768 (256 color palette)
[263] 1280x1024 (256 color palette)
[270] 320x200 (5:6:5)
[271] 320x200 (8:8:8)
[273] 640x480 (5:6:5)
[274] 640x480 (8:8:8)
[276] 800x600 (5:6:5)
[277] 800x600 (8:8:8)
[279] 1024x768 (5:6:5)
[280] 1024x768 (8:8:8)
[282] 1280x1024 (5:6:5)
[283] 1280x1024 (8:8:8)
[304] 320x200 (256 color palette)
[305] 320x400 (256 color palette)
[306] 320x400 (5:6:5)
[307] 320x400 (8:8:8)
[308] 320x240 (256 color palette)
[309] 320x240 (5:6:5)
[310] 320x240 (8:8:8)
[317] 640x400 (5:6:5)
[318] 640x400 (8:8:8)
[325] 1600x1200 (256 color palette)
[326] 1600x1200 (5:6:5)
[327] 1400x1050 (256 color palette)
[328] 1400x1050 (5:6:5)
[329] 1400x1050 (8:8:8)
[330] 1600x1200 (8:8:8)
[338] 2048x1536 (8:8:8)
[352] 1280x800 (256 color palette)
[353] 1280x800 (8:8:8)
[354] 768x480 (256 color palette)
[356] 1440x900 (256 color palette)
[357] 1440x900 (8:8:8)
[360] 1680x1050 (256 color palette)
[361] 1680x1050 (8:8:8)
[380] 1920x1200 (256 color palette)
[381] 1920x1200 (8:8:8)
|
Now i don't understand why the max resolution i can set is 1280x1024 with vesafb and 1440x900 with uvesafb.
I'd like to have a 1680x1050 resolution.
Another strange thing is that if i run vbetest -m with any mode my screen turns black and the monitor says me "No signal" and i have to reboot.
Someone had this problems / knows a solution?
Thanks
_________________
Vortex
Gentoo user since oct 2004
Gentoo Linux - ASUS P5N32-E SLi - Intel Core2 Quad Q6600 - 4GB Super Talent DDR2 800 - nVidia GeForce GTX 470 - WesternDigital VelociRaptor 150GB |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Thu Mar 04, 2010 3:12 am Post subject: |
|
|
| i92guboj wrote: | | geki wrote: | | interesting, my amd64 box runs fine with vesafb. |
An x64-able cpu doesn't imply an x86_64 OS. You are probably running a 32 bits kernel. I don't think that vesafb works on a 64 bit kernel at all. Just look at the kernel info:
| Code: | Symbol: FB_VESA [=n]
Prompt: VESA VGA graphics support
Defined at drivers/video/Kconfig:708
Depends on: HAS_IOMEM [=y] && FB [=y]=y [=y] && X86 [=y]
Location:
-> Device Drivers
-> Graphics support
-> Support for frame buffer devices (FB [=y])
Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGEBLIT [=y] && FB_BOOT_VESA_SUPPORT [=n]
|
And see that one of the requisites for this option to be available (Depends on) is "X86". In fact, one of the reasons why uvesafb was created was the fact that there wasn't a viable option to do framebuffer on x86_64 installations. |
Surely it does, at least on kernels <= 2.6.31.
I have 64-bit kernels on three computers, two with NVIDIA cards and one laptop with intel, and vesafb works fine on all of them.
BTW my kernel config says
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
so CONFIG_X86 is something else than 32 bit |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Thu Mar 04, 2010 3:36 am Post subject: |
|
|
| -Vortex- wrote: | Hi,
I have this video card:
| Code: | | 01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GTS 512] (rev a2) |
I ran vbetest and it gave me the following modes:
| Code: |
[256] 640x400 (256 color palette)
[257] 640x480 (256 color palette)
[259] 800x600 (256 color palette)
[261] 1024x768 (256 color palette)
[263] 1280x1024 (256 color palette)
[270] 320x200 (5:6:5)
[271] 320x200 (8:8:8)
[273] 640x480 (5:6:5)
[274] 640x480 (8:8:8)
[276] 800x600 (5:6:5)
[277] 800x600 (8:8:8)
[279] 1024x768 (5:6:5)
[280] 1024x768 (8:8:8)
[282] 1280x1024 (5:6:5)
[283] 1280x1024 (8:8:8)
[304] 320x200 (256 color palette)
[305] 320x400 (256 color palette)
[306] 320x400 (5:6:5)
[307] 320x400 (8:8:8)
[308] 320x240 (256 color palette)
[309] 320x240 (5:6:5)
[310] 320x240 (8:8:8)
[317] 640x400 (5:6:5)
[318] 640x400 (8:8:8)
[325] 1600x1200 (256 color palette)
[326] 1600x1200 (5:6:5)
[327] 1400x1050 (256 color palette)
[328] 1400x1050 (5:6:5)
[329] 1400x1050 (8:8:8)
[330] 1600x1200 (8:8:8)
[338] 2048x1536 (8:8:8)
[352] 1280x800 (256 color palette)
[353] 1280x800 (8:8:8)
[354] 768x480 (256 color palette)
[356] 1440x900 (256 color palette)
[357] 1440x900 (8:8:8)
[360] 1680x1050 (256 color palette)
[361] 1680x1050 (8:8:8)
[380] 1920x1200 (256 color palette)
[381] 1920x1200 (8:8:8)
|
Now i don't understand why the max resolution i can set is 1280x1024 with vesafb and 1440x900 with uvesafb.
I'd like to have a 1680x1050 resolution.
Another strange thing is that if i run vbetest -m with any mode my screen turns black and the monitor says me "No signal" and i have to reboot.
Someone had this problems / knows a solution?
Thanks |
so you want mode 361 I believe ?
And you put vesafb:vga=0x369 in your kernel line ?
If this did not work, can you try 0x368 ?
don't try to use vbetest for anything but listing modes - vbetest is using pretty low-level BIOS calls, and who knows what happens |
|
| Back to top |
|
|
-Vortex-
n00b
Joined: 28 Feb 2005
Posts: 13
Location: Modena, Italy
|
| Posted: Thu Mar 04, 2010 9:33 am Post subject: |
|
|
Yes i want mode 361.
I tried 0x369, 0x368, 0x365, 0x364 and many others but those that work are only from 640x480 to 1280x1024 and the 1600x1200.
I also ran hwinfo --framebuffer and it gave me the same resolutions as vbetest...
Edit:
I found this thread that says such modes are available on dvi but not on analog. I have an analog monitor, could it be because of this?
_________________
Vortex
Gentoo user since oct 2004
Gentoo Linux - ASUS P5N32-E SLi - Intel Core2 Quad Q6600 - 4GB Super Talent DDR2 800 - nVidia GeForce GTX 470 - WesternDigital VelociRaptor 150GB |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Thu Mar 04, 2010 2:39 pm Post subject: |
|
|
| -Vortex- wrote: | Yes i want mode 361.
I tried 0x369, 0x368, 0x365, 0x364 and many others but those that work are only from 640x480 to 1280x1024 and the 1600x1200.
I also ran hwinfo --framebuffer and it gave me the same resolutions as vbetest...
Edit:
I found this thread that says such modes are available on dvi but not on analog. I have an analog monitor, could it be because of this? |
Oh, that is possible. It seems that what you are able to set are only 'VESA standard' modes, support of which is required by VESA standard. They do not include widescreen modes, as far as I know. The rest of the modes are up to the manufacturer to implement, and perhaps they do it only for DVI.
All machines I use vesafb are with DVI |
|
| Back to top |
|
|
|
Other Things Gentoo
