You are not logged in.

#1 2009-01-21 10:44:52

esters
Member
Registered: 2006-11-04
Posts: 173

Native framebuffer resolution

I know that many of laptop users struggle with this kind of problem, so before writing this post I went through the old posts and stumbled upon some suggestions but none of them helped. The laptop is Samsung R20+ with ATi X1250. I'm trying to set 1280x800 resolution.

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Xpress 1250 [1002:7942]

At first I tried the vbetest tool, but unsuccesfuly none of the resolutions were 1280x800. After that I set up Uvesafb following the wiki entry, again it didn't work. I haven't tried radeonfb yet, because I'm not sure how to set it up. Thanks.

Offline

#2 2009-01-21 16:36:36

msh
Member
From: Latvia
Registered: 2009-01-16
Posts: 17

Re: Native framebuffer resolution

After that I set up Uvesafb following the wiki entry, again it didn't work.

Did you check your /sys/class/graphics/fb0/modes to see if 1280x800 resolution is available for you?

(Sveicieni no Latvijas! smile)

Offline

#3 2009-01-21 16:37:38

esters
Member
Registered: 2006-11-04
Posts: 173

Re: Native framebuffer resolution

Yes, I checked that file smile And for my surprise it was empty :>

( \o/ )

Offline

#4 2009-01-21 20:17:03

msh
Member
From: Latvia
Registered: 2009-01-16
Posts: 17

Re: Native framebuffer resolution

Are you certain it was modes, plural. Because mode, single, exists in the same directory too and it is empty.

Also, did you regenerate your initramfs after you configured /etc/modprobe.d/uvesafb? I recently set up uvesafb for myself and I found that after I made changes in /etc/modprobe.d/uvesafb I had to regenerate my initramfs every time before they took effect.

Offline

#5 2009-01-21 22:07:25

esters
Member
Registered: 2006-11-04
Posts: 173

Re: Native framebuffer resolution

I checked the modes file and the only resolution was the one I had already passed in menu.lst. uvesafb didn't work anyway

Getting VBE info block failed (eax=0x4f00, err=-2) vbe_init() failed with -22 probe of uvesafb.0 failed with error -22

Great, I just found out that the VGA isn't supported by the radeonfb driver.

Last edited by esters (2009-01-21 22:14:45)

Offline

#6 2009-01-22 06:26:14

msh
Member
From: Latvia
Registered: 2009-01-16
Posts: 17

Re: Native framebuffer resolution

Well, I'm fresh out of bright troubleshooting suggestions. Maybe someone else with more clue then me will come along. Best of luck to you! smile

esters wrote:

Great, I just found out that the VGA isn't supported by the radeonfb driver.

Sorry to hear that. sad

Offline

#7 2009-01-22 07:17:16

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: Native framebuffer resolution

esters wrote:

Great, I just found out that the VGA isn't supported by the radeonfb driver.

Not sure what you mean there, but my Radeon XPRESS 200M works perfectly with radeonfb.

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE)

Offline

#8 2009-01-22 11:14:04

esters
Member
Registered: 2006-11-04
Posts: 173

Re: Native framebuffer resolution

tomk - http://kerneltrap.org/node/14417

also second attempt to set uvesafb failed, In that case I will stick with the vesafb with vga=791 option

Offline

#9 2009-01-22 12:19:59

Ranguvar
Member
Registered: 2008-08-12
Posts: 2,549

Re: Native framebuffer resolution

Offline

#10 2009-01-22 14:09:51

esters
Member
Registered: 2006-11-04
Posts: 173

Re: Native framebuffer resolution

I'll take a look Ranguvar, thanks smile

Offline

Board footer

Powered by FluxBB