Arch Linux

Piotrek M

Member

From: Poland

Registered: 2008-07-22

Posts: 5

framebuffer resution 1440x900 at bootup

I have an old graphic card, Riva TNT2, and when booting the kernel with vga=ask i don't get 1440x900 as a possible resolution.
However, when i set it with fbset later, everything works just fine. Is there any possibility to have this resolution set from the start?

Maybe someone has already made any kernel patch with a workaround? What I heard is that vesafb gets the list of resolutions from the vga bios, so maybe just an ommision of this check would do the trick, though it wouldn't be very safe.

I got the modeline for fbset from gtf:

$ gtf 1440 900 60 -f

mode "1440x900 60.00Hz 32bit (GTF)"
    # PCLK: 106.47 MHz, H: 55.92 kHz, V: 60.00 Hz
    geometry 1440 900 1440 900 32
    timings 9392 232 80 28 1 152 3
    hsync low
    vsync high
endmode

Gen2ly

Member

From: Sevierville, TN

Registered: 2009-03-06

Posts: 1,529

Website

Re: framebuffer resution 1440x900 at bootup

Try the, hex line, from hwinfo:

http://wiki.archlinux.org/index.php/GRU … Resolution

---

Setting Up a Scripting Environment | Proud donor to wikipedia - link

Piotrek M

Member

From: Poland

Registered: 2008-07-22

Posts: 5

Re: framebuffer resution 1440x900 at bootup

Unfortunately, vbetest shows more or less the same list as the kernel prompt. The biggest resolution there is 1600x1200, but no panoramic ones.

EDIT: And trying the one from wiki also doesn't help, kernel says it's incorrect

Last edited by Piotrek M (2009-06-25 21:13:35)

arkham

Member

From: Stockholm

Registered: 2008-10-26

Posts: 516

Website

Re: framebuffer resution 1440x900 at bootup

Did you follow thoroughly these instructions -> http://wiki.archlinux.org/index.php/GRU … ant_to_use ?

---

"I'm Winston Wolfe. I solve problems."

~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~

Piotrek M

Member

From: Poland

Registered: 2008-07-22

Posts: 5

Re: framebuffer resution 1440x900 at bootup

Thoroughly, and testing worked only on the listed values. I tried vbetest -m 357 with no success. And I remembered to add 512 before typing the value in the command line.

I consider it strange, because, fbset makes it just work, but a bit late, and in effect during the bootup the screen first changes resolution to 1024x768, then, after running fbset, to 1440x900