Does anyone know the best value of the vga parameter in grub for an LCD monitor? I've tried the value of 0x031a (1280x1024, 16 bits), but it causes the monitor to produce an "out of range" message on the screen. My guess is that the same value will work for all LCD monitors. I can get it to work with "vga=normal" but I would like to get higher resolution, particularly when I'm working with text consoles. I discovered by looking in the code for /sbin/mkinitrd that you can get a list of available values with the command "/usr/sbin/hwinfo --framebuffer", but seeing the available values doesn't tell you which ones will work, particularly since the values are given with bit counts, not scan frequencies. Paul
* Paul W. Abrahams <abrahams@acm.org> [03-24-05 23:36]:
Does anyone know the best value of the vga parameter in grub for an LCD monitor? I've tried the value of 0x031a (1280x1024, 16 bits), but it causes the monitor to produce an "out of range" message on the screen.
That value, 0x031a, works on my nec lcd1912. I would guess that you have an incorrect vertical or horizontal scan rate Start with vga=normal and boot to 'init 3', run sax2 and correct the settings to your monitor's specs. Or edit /etc/X11/XF86Config by hand and provide the correct values. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery
On Thursday 24 March 2005 11:55 pm, Patrick Shanahan wrote:
* Paul W. Abrahams <abrahams@acm.org> [03-24-05 23:36]:
Does anyone know the best value of the vga parameter in grub for an LCD monitor? I've tried the value of 0x031a (1280x1024, 16 bits), but it causes the monitor to produce an "out of range" message on the screen.
That value, 0x031a, works on my nec lcd1912. I would guess that you have an incorrect vertical or horizontal scan rate
Start with vga=normal and boot to 'init 3', run sax2 and correct the settings to your monitor's specs. Or edit /etc/X11/XF86Config by hand and provide the correct values.
I'm confused. The vga setting for grub affects only text display, and would be meaningful even if X is never invoked. So how could XF86Config get involved? Setting "vga=normal" for grub is the fallback and it works for me, but it displays the text at the lowest resolution. For a text console I'd like to do better if it's possible, since then I can see more lines on the screen. Paul
On Fri, 2005-03-25 at 10:52 -0500, Paul W. Abrahams wrote:
On Thursday 24 March 2005 11:55 pm, Patrick Shanahan wrote: I'm confused. The vga setting for grub affects only text display, and would be meaningful even if X is never invoked. So how could XF86Config get involved?
Setting "vga=normal" for grub is the fallback and it works for me, but it displays the text at the lowest resolution. For a text console I'd like to do better if it's possible, since then I can see more lines on the screen.
Then change it to your liking and run mk_initrd to set it in the initrd at boot. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Friday 25 March 2005 11:26 am, Ken Schneider wrote:
Setting "vga=normal" for grub is the fallback and it works for me, but it displays the text at the lowest resolution. For a text console I'd like
to
do better if it's possible, since then I can see more lines on the screen.
Then change it to your liking and run mk_initrd to set it in the initrd at boot.
So far I haven't found a vga value that (a) doesn't drive the monitor out of range and (b) gives me the smaller text size I want. Fortunately the monitor protects itself from sync values it doesn't like. By the way, it doesn't seem necessary to run mk_initrd to put the changes into effect on the next boot. I've tried just editing /boot/grub/menu.lst and rebooting, and my changes do have an effect (though not necessarily a favorable one). Paul
* Paul W. Abrahams <abrahams@acm.org> [03-25-05 13:06]:
So far I haven't found a vga value that (a) doesn't drive the monitor out of range and (b) gives me the smaller text size I want. Fortunately the monitor protects itself from sync values it doesn't like.
the video modes are listed: /usr/src/linux/Documentation/fb/vesafb.txt If you do not have the file, I have made a copy available: http://wahoo.no-ip.org/~pat/vesafb.txt -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery
Paul W. Abrahams wrote:
On Friday 25 March 2005 11:26 am, Ken Schneider wrote:
Setting "vga=normal" for grub is the fallback and it works for me, but it displays the text at the lowest resolution. For a text console I'd like
vga=792
It's what I have, the monitor is not out of range, and I get the right fonts. mo2cts fx
On Fri, 2005-03-25 at 13:01 -0500, Paul W. Abrahams wrote:
On Friday 25 March 2005 11:26 am, Ken Schneider wrote: So far I haven't found a vga value that (a) doesn't drive the monitor out of range and (b) gives me the smaller text size I want. Fortunately the monitor protects itself from sync values it doesn't like.
By the way, it doesn't seem necessary to run mk_initrd to put the changes into effect on the next boot. I've tried just editing /boot/grub/menu.lst and rebooting, and my changes do have an effect (though not necessarily a favorable one).
run hwinfo --framebuffer That will show what the graphics card supports. I found that mk_initrd changes something in the initrd file that gets loaded at boot time which is why I recommended it. On my laptop I founf that 0x317 or 0x318 worked well (1024x768 resolution). -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Fri, 2005-03-25 at 22:13 -0500, Paul W. Abrahams wrote:
On Friday 25 March 2005 7:27 pm, Ken Schneider wrote:
On my laptop I founf that 0x317 or 0x318 worked well (1024x768 resolution).
One is 15-bit and the other is 16-bit, I know, but what effect does the difference have?
One is 16 bit the other is 24 bit, just the number of bit-planes (more colors). -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
participants (4)
-
FX Fraipont -
Ken Schneider -
Patrick Shanahan -
Paul W. Abrahams