[solved] vesafb at 1600x1200

vogt · 2006-11-25 02:42:26

I want to have the command line at a 1600x1200 resolution, to avoid making the monitor resync when switching between X

booting with GRUB, up to vga=795 for a 1280x1024 vesafb command line works properly, while higher numbers; vga=798-796 as suggested by this page http://wiki.antlinux.com/pmwiki.php?n=HowTos.VgaModes cause the boot to hang with an error about a bad video mode, elsewhere, I've read that 1600x1200 is 0x375-0x373 which would be vga=885 to 883 for different color depths, which gives the same error.

Running slackware previously, I managed to compile a kernel with a ?radeonfb? that was at default 1600x1200. If thats the only solution, which lines do I change in the conifg in the kernel26 abs directory?

thanks

edit: changed vga numbers to the proper ones which work

Last edited by vogt (2008-02-03 08:13:37)

byte · 2006-11-25 13:12:15

 sed -i -r 's/.*(CONFIG_FB_RADEON).*/1=y/' config

could help, but I'm not sure. Maybe you also need to disable Vesa, no idea.

pauldonnelly · 2006-11-26 04:03:28

I wish I could help, but vga=795 works for me.

Perhaps you could try vga=0x### video=vesafb:mtrr,1600x1200-16@72 or somesuch? I had to use a similar line to get a 1280x800 framebuffer on my laptop.

vogt · 2006-11-27 21:59:48

vga=795 does work here, (must have been a typo) its higher resolutions that elude me.

pauldonnelly · 2006-11-27 22:38:41

No, it's my mistake. I was thinking that I was using 795 to get a 1600x1200 framebuffer. Which is obviously wrong, now that I look closer.

vogt · 2006-11-27 22:52:42

adding the line to my grub menu.lst video=vesafb:mtrr,1600x1200-16@60 is basicaly ignored (I evidently get an even smaller 80x25 console); the only relevant part of my /var/log/kernel.log booting with that line is:

Nov 27 17:24:21 localhost Kernel command line: root=/dev/hda4 video=vesafb:mtrr,1600x1200-16@60 ro
Nov 27 17:24:21 localhost Local APIC disabled by BIOS -- you can enable it with "lapic"
Nov 27 17:24:21 localhost mapped APIC to ffffd000 (0120a000)
Nov 27 17:24:21 localhost Enabling fast FPU save and restore... done.
Nov 27 17:24:21 localhost Enabling unmasked SIMD FPU exception support... done.
Nov 27 17:24:21 localhost Initializing CPU#0
Nov 27 17:24:21 localhost PID hash table entries: 1024 (order: 10, 4096 bytes)
Nov 27 17:24:21 localhost Console: colour VGA+ 80x25

or am I missing something else important?

T-Dawg · 2006-11-28 00:03:08

maybe you could compile the kernel to use vesafb-tng instead and preset that resolution in the kernel?

vogt · 2006-11-29 00:23:32

preset that resolution in the kernel

is there a faster way than reconfiguring the kernel with the vesafb-tng (which may not even work) patch applied (which means changing to the 2.6.19-rc2 kernel?) to try that suggestion? Do any of the kernels precompiled available have vesafb-tng?

Romashka · 2006-11-29 08:34:48

vogt wrote:

Do any of the kernels precompiled available have vesafb-tng?

kernel26beyond

iphitus · 2006-11-29 08:44:19

look in /proc/fb0/modes

if your mode isnt listed there, you won't be able to use it with either vesafb or vesafb-tng

vogt · 2006-11-29 20:58:51

look in /proc/fb0/modes

 #cd /proc/fb0
bash: cd: /proc/fb0: No such file or directory

if that wasn't a typo, could that be fixed or is the hardware detection just crazy?
are any other workarounds possible?
it's not critical, just one more little annoyance.

Romashka · 2006-11-29 22:39:37

vogt wrote:

look in /proc/fb0/modes
 #cd /proc/fb0
bash: cd: /proc/fb0: No such file or directory
if that wasn't a typo, could that be fixed or is the hardware detection just crazy?

I have /proc/fb on my system, but it's a file, not directory (maybe that's because I don't use framebuffer now?).

vogt · 2006-11-30 01:14:14

Romashka wrote:

I have /proc/fb on my system, but it's a file, not directory (maybe that's because I don't use framebuffer now?).

yeah, also got /proc/fb, except that I do have a running vesafb, /proc/fb almost uselessly names the compiled-in fb, in line with the proc manpage

the proc manpage has no mention of /proc/fb(a number)/ where the info about possible modes would be located.

vogt · 2008-02-03 08:13:13

Some time later, the various framebuffer modules got added to kernel26, so I just have to load the radeonfb module (in the modules section of /etc/rc.conf) and disable vesafb by booting the kernel with

kernel /vmlinuz26 root....   video=vesa:off

dab · 2008-05-23 20:29:04

vogt wrote:

Some time later, the various framebuffer modules got added to kernel26, so I just have to load the radeonfb module (in the modules section of /etc/rc.conf) and disable vesafb by booting the kernel with
kernel /vmlinuz26 root....   video=vesa:off

can't get it working - i mean radeonfb from rc.conf and vesa:off.

What should i check/do?

dabski · 2008-05-26 23:51:32

Are you sure your doing it correctly? The

radeonfb

goes in the rc.conf in the modules section and the

video=vesa:off

goes in /boot/grub/grub.conf or whatever its called.

Last edited by dabski (2008-05-26 23:52:05)

Arch Linux

#1 2006-11-25 02:42:26

[solved] vesafb at 1600x1200

#2 2006-11-25 13:12:15

Re: [solved] vesafb at 1600x1200

#3 2006-11-26 04:03:28

Re: [solved] vesafb at 1600x1200

#4 2006-11-27 21:59:48

Re: [solved] vesafb at 1600x1200

#5 2006-11-27 22:38:41

Re: [solved] vesafb at 1600x1200

#6 2006-11-27 22:52:42

Re: [solved] vesafb at 1600x1200

#7 2006-11-28 00:03:08

Re: [solved] vesafb at 1600x1200

#8 2006-11-29 00:23:32

Re: [solved] vesafb at 1600x1200

#9 2006-11-29 08:34:48

Re: [solved] vesafb at 1600x1200

#10 2006-11-29 08:44:19

Re: [solved] vesafb at 1600x1200

#11 2006-11-29 20:58:51

Re: [solved] vesafb at 1600x1200

#12 2006-11-29 22:39:37

Re: [solved] vesafb at 1600x1200

#13 2006-11-30 01:14:14

Re: [solved] vesafb at 1600x1200

#14 2008-02-03 08:13:13

Re: [solved] vesafb at 1600x1200

#15 2008-05-23 20:29:04

Re: [solved] vesafb at 1600x1200

#16 2008-05-26 23:51:32

Re: [solved] vesafb at 1600x1200

Board footer