Mick schrieb:
> # dmesg | grep uvesafb
> Kernel command line: root=/dev/sda3 video=uvesafb:1024x768-32@64,ywrap,mtrr:4 
> splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
> uvesafb: ATI Technologies Inc., V380, 01.00, OEM: ATI RV380, VBE v2.0
> uvesafb: protected mode interface info at c000:5884
> uvesafb: pmi: set display start = c00c5918, set palette = c00c5964
> uvesafb: pmi: ports = b010 b016 b054 b038 b03c b05c b000 b004 b0b0 b0b2 b0b4 
> uvesafb: no monitor limits have been set, default refresh rate will be used
> uvesafb: VBE state buffer size cannot be determined (eax=0x0, err=0)
> uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
> uvesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 6144k, total 
> 16384k

Looks okay, but i don't know much about ATI cards!

> fbset gives me bash: command not found.  Should have I emerged something here?  
> Can't remember seeing this in the wiki article, as in it wasn't a must for fb 
> splash to work (I think).

It just gives some info about the framebuffer, i think it is not 
necessary. If you want it just do an "emerge fbset". It is a small utility.

I am not an expert here, but what are the other strange errors the new 
kernel is giving you, which you have mentioned before.

Can you post the output of
"cat /sys/devices/platform/uvesafb.0/vbe_modes"

> although the quality of the image is poor (it looks sort of pixelated)

What do you mean by this? I will attach a grab of a 1024x768 framebuffer 
image with the livecd-2007.0 theme, which looks okay here!

What about trying a higher frequency, i have 75Hz here! Or is your 
monitor not capable of this frequency?

Regards,

Daniel