[ltp] X31 radeon framebuffer 2.6.10 problem

Tino Keitel linux-thinkpad@linux-thinkpad.org
Fri, 21 Jan 2005 14:15:02 +0100


On Fri, Jan 21, 2005 at 14:05:08 +0100, Michal Trzcinski wrote:
> Dnia pi?tek, 21 stycznia 2005 13:52, Brian P. Flaherty napisa?:
> BP> However, what I saw in 2.6.9 during the boot process was
> BP> that the screen went blank for a bit and the boot messages would
> BP> resume at the framebuffer console size.
> 
> It's normal. Boot messages resume after screen went blank at the point of loading framebuffer for any gfx card (vesafb or radeonfb, anyway).
> 
> BP> X windows appears to work just fine.  Any ideas where what I've missed
> BP> or what changed in 2.6.10?  Thanks very much for your time and
> BP> suggestions.
> 
> I have 2.6.10 kernel. My fbset -i looks like yours:
> 
> root@kopernik:~# fbset -i
> 
> mode "1024x768-60"
>     # D: 65.003 MHz, H: 48.365 kHz, V: 60.006 Hz
>     geometry 1024 768 1024 768 8
>     timings 15384 168 16 30 2 136 6
>     hsync high
>     vsync high
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : ATI Radeon LW
>     Address     : 0xe0000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : PSEUDOCOLOR
>     XPanStep    : 8
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 1024
>     MMIO Address: 0xc0100000
>     MMIO Size   : 16384
>     Accelerator : No
> 
> root@kopernik:~# cat /etc/lilo.conf |grep vga
> vga = 773
> 
> I use vga 773 with lilo. Everything works fine with 2.6.10 and all other 2.6.* kernels.
> Do you have lilo with the same vga mode? It seems to be 256 colors.

AFAIK any vga= kernel option doesn't make sense with the Radeon
framebuffer. It will only be used by VESA framebuffer.

Regards,
Tino