| View previous topic :: View next topic |
| Author |
Message |
rimian
n00b
Joined: 31 Dec 2005
Posts: 42
Location: Australia
|
 Posted: Sat Jan 07, 2006 8:35 am Post subject: vesafb & vesafb-tng not working |
 |
|
Hi,
I've been trying to get my kernel to boot in a higher res that 640x480. if i use the vesafb driver and one of the vga options in my grub.conf i get a blank screen [have to boot from the CD to change it back]. i have read through numerous forum posts and have checked the syntax over and over. i am currently using vesafb-tng but no matter what i change in the resolution settings i get no change in my resolution. i'm also using an nVidia card but i don't know if this is relevant.
when i use vesafb-tng and, in my grub.conf place:
video=vesafb:ywrap,mtrr,1024x768-32@70
i get the following for dmesg | grep vesa
vesafb: unrecognised option mtrr
vesafb: NVIDIA Corporation, NV17 Board, Chip Rev A5 (OEM: NVIDIA)
vesafb: VBE version 3.0
vesafb: protected mode interface info at c000:f8f0
vesafb: pmi: set display start = c00cf935, set palette = c00cf9ba
vesafb: pmi: ports = [a big long string]
vesafb: VBIOS/hardware supports DDC2 transfers
vesafb: monitor limits: vf = 76Hz, hf = 81 Khz, clk = 140 Mhz
vesafb: scrolling ywrap using protected mode interface, yres_virtual=6144
vesafb: cannot reserve video memory at 0xd8000000
vesafb: framebuffer at 0xd8000000, mapped to 0xe5980000, using 24576k, total 65536k
can anyone tell me what this means? i have tried other refresh frequencies and bit depths. nuthin changes.
thanks for any help!
rim
PS i had to hand type all that. |
|
| Back to top |
|
 |
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Sat Jan 07, 2006 10:28 am Post subject: |
|
|
errors look like it is actually working
maybe you shold start with a lower colordepth and/or refresh-rate - or let the driver decide about these for a start
you could use a line like:
video=vesafb:1024x768
and start from there
this should work
and the error-message - you tried to tell the driver to use mtrr and it failed to do so
make a second entry in your boot-loaders config - so you will have one configuration, that _will_ boot - and change only one thing at a time in the other |
|
| Back to top |
|
|
rimian
n00b
Joined: 31 Dec 2005
Posts: 42
Location: Australia
|
| Posted: Sat Jan 07, 2006 10:38 am Post subject: |
|
|
yes it looks like something is happening. i'll try the base bit depth and resolution and see what frequency my suse machine likes to run that monitor on. there is hope!
that extra boot is a bloody good idea! i didn't know you could do that.
thanks heaps. |
|
| Back to top |
|
|
sirdilznik
l33t
Joined: 28 Apr 2005
Posts: 731
|
| Posted: Sat Jan 07, 2006 6:36 pm Post subject: Re: vesafb & vesafb-tng not working |
|
|
| rimian wrote: | video=vesafb:ywrap,mtrr,1024x768-32@70
|
try: | Code: | | video=vesafb:ywrap,mtrr vga=0x318 |
Here are some more video modes. |
|
| Back to top |
|
|
rimian
n00b
Joined: 31 Dec 2005
Posts: 42
Location: Australia
|
| Posted: Mon Jan 09, 2006 10:45 am Post subject: |
|
|
| i tried various vga= options and got a blank screen. |
|
| Back to top |
|
|
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Mon Jan 09, 2006 11:06 am Post subject: vesafb & vesafb-tng not working |
|
|
from explanations - available under "help" option in kernel-config (if you are using "make menuconfig or make xconfig)
section: Graphics - framebuffer-support - VESA-VGA graphics-support - vesa-driver-type - vesafb
| Code: | CONFIG_FB_VESA_STD: x
x x
x This is the frame buffer device driver for generic VESA 2.0 x
x compliant graphic cards. The older VESA 1.2 cards are not supported. x
x You will get a boot time penguin logo at no additional cost. Please x
x read <file:Documentation/fb/vesafb.txt>. Choose this driver if you x
x are experiencing problems with vesafb-tng or if you own a 64-bit system. x
x x
x Note that this driver cannot be compiled as a module.
|
So maybe you should try the "normal" vesafb instead of vesafb-tng...
There is also explicit support for a special fb-driver for nVidia-cards - maybe you should try this one instead...
for how to configure it (command-line at boot-time...) see the files in this directory - maybe things get more clear then...
| Code: | | /usr/src/linux/Documentation/fb |
from vesafb.txt (one of the files there):
| Code: | So the table for the Kernel mode numbers are:
| 640x480 800x600 1024x768 1280x1024
----+-------------------------------------
256 | 0x301 0x303 0x305 0x307
32k | 0x310 0x313 0x316 0x319
64k | 0x311 0x314 0x317 0x31A
16M | 0x312 0x315 0x318 0x31B
To enable one of those modes you have to specify "vga=ask" in the lilo.conf
file and rerun LILO. Then you can type in the desired mode at the "vga=ask"
prompt. For example if you like to use 1024x768x256 colors you have to say
"305" at this prompt.
|
...or put these right in the vga=... option at boot - as far as I know - you can specify eighter vga=... or video=vesafb:ywrap... not both of them together, but I'm not sure there - its easier to find a source of error if you start with one or the other - an then try to combine them if needed (and at all possible) |
|
| Back to top |
|
|
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Mon Jan 09, 2006 12:04 pm Post subject: |
|
|
a little more:
here is a line from my grub.conf, that I actually used (not any more, because I currently run radeonfb...)
| Code: | title=Gentoo-vesafb
kernel /kernel-2.6.14-gentoo-r5 root=/dev/hda3 video=vesafb:ywrap,pmipal |
there is an option in kernel-config where you can specify the default resolution, when there is none given at boot (i.e. grub.conf) - so you don'teven need to bother with how to give the commands in grub.conf
in:
Device Drivers - Graphics Support - right below Vesa VGA graphics support
I put 1024x768@60 in there - @60 because I have Laptop and the LCD has just this frequency available...
the grub.conf-line above - possibly first without the "ywrap,pmipal" parameters should work perfectly
you need to compile "Support for frame buffer devices" and the framebuffer you want to use in the kernel - not as a module - or it will of course not be there at boot-time, when you want to have it |
|
| Back to top |
|
|
nickeh
Tux's lil' helper
Joined: 15 Feb 2004
Posts: 137
|
| Posted: Wed Jan 11, 2006 11:52 am Post subject: |
|
|
If you use vesafb-tng some things are different
mtrr syntax is changed:
| Code: |
mtrr:n Setup memory type range registers for the vesafb framebuffer
where n:
0 - disabled (equivalent to nomtrr) (default)
1 - uncachable
2 - write-back
3 - write-combining
4 - write-through
|
Also vga= is not used by vesafb-tng it uses video=vesafb:1024x768-16@70 instead
h[/code][/quote]ttp://dev.gentoo.org/~spock/projects/vesafb-tng/ |
|
| Back to top |
|
|
|
Kernel & Hardware
