[gentoo-user] uvesafb fails to work

[gentoo-user] uvesafb fails to work

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

Hi All,

I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and thought 
of using it on a box of mine.  However, amidst other weird and wonderful 
errors that the new kernel gives me on this box, I have completely failed to 
get uvesafb to work.

When it boots up it comes up with these errors:
=====================================================
* Setting framebuffer console images
Can't open cfg file //etc/splash/emergence/640x480.cfg
No 8bpp silent picture specified in the theme
No 8bpp verbose picture specified in the theme
* Failed to set background image on tty1
=====================================================

Meanwhile the penguins and fonts on the boot console are shown in some 
impossibly large size.  My kernel line is:

kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \ 
video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \ 
splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
initrd /boot/fbsplash-emergence-1280x1024

Any ideas?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Daniel Pielmeier]

Mick schrieb:
> Hi All,
> 
> I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and thought 
> of using it on a box of mine.  However, amidst other weird and wonderful 
> errors that the new kernel gives me on this box, I have completely failed to 
> get uvesafb to work.
> 
> When it boots up it comes up with these errors:
> =====================================================
> * Setting framebuffer console images
> Can't open cfg file //etc/splash/emergence/640x480.cfg
> No 8bpp silent picture specified in the theme
> No 8bpp verbose picture specified in the theme
> * Failed to set background image on tty1
> =====================================================
> 
> Meanwhile the penguins and fonts on the boot console are shown in some 
> impossibly large size.  My kernel line is:
> 
> kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \ 
> video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \ 
> splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
> initrd /boot/fbsplash-emergence-1280x1024
> 
> Any ideas?

Just a shot in the dark are you using any kind of tv-out?

I had this problem with tv-out. I specified a resolution of 1280x1024. 
When I connect my tv to my box the maximal resolution possible is 
1024x768 because the tv-encoder does not offer higher resolutions. So 
instead of switching to the next greatest resolution of 1024x768 the 
uvesafb driver switches to smallest resolution of 640x480. This 
resolution is not available in the emergence theme thus the splash fails!

If you have a problem like this there are existing patches whto the 
kernel which are fixing this issue!

What does "cat /sys/devices/platform/uvesafb.0/vbe_modes" say?

Regards,

Daniel
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] uvesafb fails to work

[Matt Edens]

[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]

I have had problems getting this to work also, but was able to get it
working finally
after being directed to the authors website and following his instructions.
What I
did was get a 2.6.24 kernel working for me fully with no errors then
proceded to follow
spock's instructions to get uvesafb working properly on both my desktop and
laptop.
Hope this gives you what you need to get it working.

Matt

On Sun, Mar 30, 2008 at 2:45 PM, Daniel Pielmeier <
daniel.pielmeier@googlemail.com> wrote:

> Mick schrieb:
> > Hi All,
> >
> > I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and
> thought
> > of using it on a box of mine.  However, amidst other weird and wonderful
> > errors that the new kernel gives me on this box, I have completely
> failed to
> > get uvesafb to work.
> >
> > When it boots up it comes up with these errors:
> > =====================================================
> > * Setting framebuffer console images
> > Can't open cfg file //etc/splash/emergence/640x480.cfg
> > No 8bpp silent picture specified in the theme
> > No 8bpp verbose picture specified in the theme
> > * Failed to set background image on tty1
> > =====================================================
> >
> > Meanwhile the penguins and fonts on the boot console are shown in some
> > impossibly large size.  My kernel line is:
> >
> > kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \
> > video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \
> > splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
> > initrd /boot/fbsplash-emergence-1280x1024
> >
> > Any ideas?
>
> Just a shot in the dark are you using any kind of tv-out?
>
> I had this problem with tv-out. I specified a resolution of 1280x1024.
> When I connect my tv to my box the maximal resolution possible is
> 1024x768 because the tv-encoder does not offer higher resolutions. So
> instead of switching to the next greatest resolution of 1024x768 the
> uvesafb driver switches to smallest resolution of 640x480. This
> resolution is not available in the emergence theme thus the splash fails!
>
> If you have a problem like this there are existing patches whto the
> kernel which are fixing this issue!
>
> What does "cat /sys/devices/platform/uvesafb.0/vbe_modes" say?
>
> Regards,
>
> Daniel
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 2920 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Matt Edens]

[-- Attachment #1: Type: text/plain, Size: 2669 bytes --]

Oops forgot the link to the website.
http://dev.gentoo.org/~spock/projects/uvesafb/<http://dev.gentoo.org/%7Espock/projects/uvesafb/>

On Sun, Mar 30, 2008 at 3:31 PM, Matt Edens <phyrlinux@gmail.com> wrote:

> I have had problems getting this to work also, but was able to get it
> working finally
> after being directed to the authors website and following his
> instructions.  What I
> did was get a 2.6.24 kernel working for me fully with no errors then
> proceded to follow
> spock's instructions to get uvesafb working properly on both my desktop
> and laptop.
> Hope this gives you what you need to get it working.
>
> Matt
>
>
> On Sun, Mar 30, 2008 at 2:45 PM, Daniel Pielmeier <
> daniel.pielmeier@googlemail.com> wrote:
>
> > Mick schrieb:
> > > Hi All,
> > >
> > > I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and
> > thought
> > > of using it on a box of mine.  However, amidst other weird and
> > wonderful
> > > errors that the new kernel gives me on this box, I have completely
> > failed to
> > > get uvesafb to work.
> > >
> > > When it boots up it comes up with these errors:
> > > =====================================================
> > > * Setting framebuffer console images
> > > Can't open cfg file //etc/splash/emergence/640x480.cfg
> > > No 8bpp silent picture specified in the theme
> > > No 8bpp verbose picture specified in the theme
> > > * Failed to set background image on tty1
> > > =====================================================
> > >
> > > Meanwhile the penguins and fonts on the boot console are shown in some
> > > impossibly large size.  My kernel line is:
> > >
> > > kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \
> > > video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \
> > > splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
> > > initrd /boot/fbsplash-emergence-1280x1024
> > >
> > > Any ideas?
> >
> > Just a shot in the dark are you using any kind of tv-out?
> >
> > I had this problem with tv-out. I specified a resolution of 1280x1024.
> > When I connect my tv to my box the maximal resolution possible is
> > 1024x768 because the tv-encoder does not offer higher resolutions. So
> > instead of switching to the next greatest resolution of 1024x768 the
> > uvesafb driver switches to smallest resolution of 640x480. This
> > resolution is not available in the emergence theme thus the splash
> > fails!
> >
> > If you have a problem like this there are existing patches whto the
> > kernel which are fixing this issue!
> >
> > What does "cat /sys/devices/platform/uvesafb.0/vbe_modes" say?
> >
> > Regards,
> >
> > Daniel
> > --
> > gentoo-user@lists.gentoo.org mailing list
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 3472 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Mick]

[-- Attachment #1: Type: text/plain, Size: 281 bytes --]

On Sunday 30 March 2008, Matt Edens wrote:
> Oops forgot the link to the website.
> http://dev.gentoo.org/~spock/projects/uvesafb/<http://dev.gentoo.org/%7Espo
>ck/projects/uvesafb/>

Thanks Matt, I have followed spock's instructions in the first place.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Ricardo Saffi Marques]

[-- Attachment #1: Type: text/plain, Size: 541 bytes --]

On Sun, Mar 30, 2008 at 5:32 PM, Matt Edens <phyrlinux@gmail.com> wrote:

> Oops forgot the link to the website.
> http://dev.gentoo.org/~spock/projects/uvesafb/<http://dev.gentoo.org/%7Espock/projects/uvesafb/>


Yay! This works beautifully! :o)
Thanks a lot! Finally, framebuffer console again!

Best Regards,

Saffi

-- 
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.com

[-- Attachment #2: Type: text/html, Size: 878 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]

On Sunday 30 March 2008, Daniel Pielmeier wrote:
> Mick schrieb:
> > Hi All,
> >
> > I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and
> > thought of using it on a box of mine.  However, amidst other weird and
> > wonderful errors that the new kernel gives me on this box, I have
> > completely failed to get uvesafb to work.
> >
> > When it boots up it comes up with these errors:
> > =====================================================
> > * Setting framebuffer console images
> > Can't open cfg file //etc/splash/emergence/640x480.cfg
> > No 8bpp silent picture specified in the theme
> > No 8bpp verbose picture specified in the theme
> > * Failed to set background image on tty1
> > =====================================================
> >
> > Meanwhile the penguins and fonts on the boot console are shown in some
> > impossibly large size.  My kernel line is:
> >
> > kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \
> > video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \
> > splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
> > initrd /boot/fbsplash-emergence-1280x1024
> >
> > Any ideas?
>
> Just a shot in the dark are you using any kind of tv-out?
>
> I had this problem with tv-out. I specified a resolution of 1280x1024.
> When I connect my tv to my box the maximal resolution possible is
> 1024x768 because the tv-encoder does not offer higher resolutions. So
> instead of switching to the next greatest resolution of 1024x768 the
> uvesafb driver switches to smallest resolution of 640x480. This
> resolution is not available in the emergence theme thus the splash fails!
>
> If you have a problem like this there are existing patches whto the
> kernel which are fixing this issue!
>
> What does "cat /sys/devices/platform/uvesafb.0/vbe_modes" say?

Thanks Daniel, I am not using tvout, just a LCD monitor.  You're right, 
there's no 1280x1024 in the above file!  Changed it to 1024x768 and it works, 
although the quality of the image is poor (it looks sort of pixelated).

What controls what resolutions exist in that file?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Daniel Pielmeier]

Mick schrieb:
> On Sunday 30 March 2008, Daniel Pielmeier wrote:
>> Mick schrieb:
>>> Hi All,
>>>
>>> I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and
>>> thought of using it on a box of mine.  However, amidst other weird and
>>> wonderful errors that the new kernel gives me on this box, I have
>>> completely failed to get uvesafb to work.
>>>
>>> When it boots up it comes up with these errors:
>>> =====================================================
>>> * Setting framebuffer console images
>>> Can't open cfg file //etc/splash/emergence/640x480.cfg
>>> No 8bpp silent picture specified in the theme
>>> No 8bpp verbose picture specified in the theme
>>> * Failed to set background image on tty1
>>> =====================================================
>>>
>>> Meanwhile the penguins and fonts on the boot console are shown in some
>>> impossibly large size.  My kernel line is:
>>>
>>> kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \
>>> video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \
>>> splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1
>>> initrd /boot/fbsplash-emergence-1280x1024
>>>
>>> Any ideas?
>> Just a shot in the dark are you using any kind of tv-out?
>>
>> I had this problem with tv-out. I specified a resolution of 1280x1024.
>> When I connect my tv to my box the maximal resolution possible is
>> 1024x768 because the tv-encoder does not offer higher resolutions. So
>> instead of switching to the next greatest resolution of 1024x768 the
>> uvesafb driver switches to smallest resolution of 640x480. This
>> resolution is not available in the emergence theme thus the splash fails!
>>
>> If you have a problem like this there are existing patches whto the
>> kernel which are fixing this issue!
>>
>> What does "cat /sys/devices/platform/uvesafb.0/vbe_modes" say?
> 
> Thanks Daniel, I am not using tvout, just a LCD monitor.  You're right, 
> there's no 1280x1024 in the above file!  Changed it to 1024x768 and it works, 
> although the quality of the image is poor (it looks sort of pixelated).
> 
> What controls what resolutions exist in that file?

Output of /usr/src/linux/Documentation/fb/uvesafb.txt

... snip ....

2. Caveats and limitations
--------------------------

uvesafb is a _generic_ driver which supports a wide variety of video
cards, but which is ultimately limited by the Video BIOS interface.
The most important limitations are:

- Lack of any type of acceleration.
- A strict and limited set of supported video modes.  Often the native
   or most optimal resolution/refresh rate for your setup will not work
   with uvesafb, simply because the Video BIOS doesn't support the
   video mode you want to use.  This can be especially painful with
   widescreen panels, where native video modes don't have the 4:3 aspect
   ratio, which is what most BIOS-es are limited to.
- Adjusting the refresh rate is only possible with a VBE 3.0 compliant
   Video BIOS.  Note that many nVidia Video BIOS-es claim to be VBE 3.0
   compliant, while they simply ignore any refresh rate settings.

..... snip .....

4. The sysfs interface
----------------------

uvesafb provides several sysfs nodes for configurable parameters and
additional information.

Driver attributes:

/sys/bus/platform/drivers/uvesafb
   - v86d (default: /sbin/v86d)
     Path to the v86d executable. v86d is started by uvesafb
     if an instance of the daemon isn't already running.

Device attributes:

/sys/bus/platform/drivers/uvesafb/uvesafb.0
   - nocrtc
     Use the default refresh rate (60 Hz) if set to 1.

   - oem_product_name
   - oem_product_rev
   - oem_string
   - oem_vendor
     Information about the card and its maker.

   - vbe_modes
     A list of video modes supported by the Video BIOS along with their
     VBE mode numbers in hex.

   - vbe_version
     A BCD value indicating the implemented VBE standard.

..... snip .....


So this depend on the Video Bios of your card and you maybe can't do 
anything about it!

Although 1280x1024 should normally work and i guess you use this 
resolution for your Desktop. How do you generate your initrd? Which card 
do you have?

"dmesg | grep uvesafb" and "fbset --info -v"?

Regards,

Daniel

-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] uvesafb fails to work

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]

On Sunday 30 March 2008, Daniel Pielmeier wrote:

> So this depend on the Video Bios of your card and you maybe can't do
> anything about it!
>
> Although 1280x1024 should normally work and i guess you use this
> resolution for your Desktop. How do you generate your initrd? Which card
> do you have?
>
> "dmesg | grep uvesafb" and "fbset --info -v"?

# 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

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).
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Daniel Pielmeier]

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

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

[-- Attachment #2: 1024x768.png --]
[-- Type: image/png, Size: 52047 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2671 bytes --]

On Wednesday 02 April 2008, Daniel Pielmeier wrote:
> 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!

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

This is what I get, there's no 1280x1024 available:
==========================================
320x200-8, 0x0182
320x200-15, 0x010d
320x200-16, 0x010e
320x200-24, 0x010f
320x200-32, 0x0120
320x240-8, 0x0192
320x240-15, 0x0193
320x240-16, 0x0194
320x240-24, 0x0195
320x240-32, 0x0196
400x300-8, 0x01a2
400x300-15, 0x01a3
400x300-16, 0x01a4
400x300-24, 0x01a5
400x300-32, 0x01a6
512x384-8, 0x01b2
512x384-15, 0x01b3
512x384-16, 0x01b4
512x384-24, 0x01b5
512x384-32, 0x01b6
640x350-8, 0x01c2
640x350-15, 0x01c3
640x350-16, 0x01c4
640x350-24, 0x01c5
640x350-32, 0x01c6
640x400-8, 0x0100
640x400-15, 0x0183
640x400-16, 0x0184
640x400-24, 0x0185
640x400-32, 0x0186
640x480-8, 0x0101
640x480-15, 0x0110
640x480-16, 0x0111
640x480-24, 0x0112
640x480-32, 0x0121
800x600-8, 0x0103
800x600-15, 0x0113
800x600-16, 0x0114
800x600-24, 0x0115
800x600-32, 0x0122
1024x768-8, 0x0105
1024x768-15, 0x0116
1024x768-16, 0x0117
1024x768-24, 0x0118
1024x768-32, 0x0123
==========================================

> > 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?

What I mean is that when if fades in it creates artifacts on the screen (is 
this a matter of uvesafb not having acceleration?).  Also the background 
image when I press F2 is not clear.  It looks as if it is a smaller 
resolution stretched over a larger screen.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] uvesafb fails to work

[Daniel Pielmeier]

Mick schrieb:
> On Wednesday 02 April 2008, Daniel Pielmeier wrote:
>> 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!
> 
>> Can you post the output of
>> "cat /sys/devices/platform/uvesafb.0/vbe_modes"
> 
> This is what I get, there's no 1280x1024 available:
> ==========================================
> 320x200-8, 0x0182
> 320x200-15, 0x010d
> 320x200-16, 0x010e
> 320x200-24, 0x010f
> 320x200-32, 0x0120
> 320x240-8, 0x0192
> 320x240-15, 0x0193
> 320x240-16, 0x0194
> 320x240-24, 0x0195
> 320x240-32, 0x0196
> 400x300-8, 0x01a2
> 400x300-15, 0x01a3
> 400x300-16, 0x01a4
> 400x300-24, 0x01a5
> 400x300-32, 0x01a6
> 512x384-8, 0x01b2
> 512x384-15, 0x01b3
> 512x384-16, 0x01b4
> 512x384-24, 0x01b5
> 512x384-32, 0x01b6
> 640x350-8, 0x01c2
> 640x350-15, 0x01c3
> 640x350-16, 0x01c4
> 640x350-24, 0x01c5
> 640x350-32, 0x01c6
> 640x400-8, 0x0100
> 640x400-15, 0x0183
> 640x400-16, 0x0184
> 640x400-24, 0x0185
> 640x400-32, 0x0186
> 640x480-8, 0x0101
> 640x480-15, 0x0110
> 640x480-16, 0x0111
> 640x480-24, 0x0112
> 640x480-32, 0x0121
> 800x600-8, 0x0103
> 800x600-15, 0x0113
> 800x600-16, 0x0114
> 800x600-24, 0x0115
> 800x600-32, 0x0122
> 1024x768-8, 0x0105
> 1024x768-15, 0x0116
> 1024x768-16, 0x0117
> 1024x768-24, 0x0118
> 1024x768-32, 0x0123
> ==========================================
> 
>>> 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?
> 
> What I mean is that when if fades in it creates artifacts on the screen (is 
> this a matter of uvesafb not having acceleration?).  Also the background 
> image when I press F2 is not clear.  It looks as if it is a smaller 
> resolution stretched over a larger screen.

What about the silent screen does it also look unclear or just the 
verbose screen.

I don't have any artifacts here and the picture is clear, even with the 
connected TV where i only get 1024x768.

I think I can't help you any further here. Maybe you could contact the 
maintainer of uvesafb, splashutils (spock@gentoo.org). Probably he could 
help you, although he seems busy with other things at the moment.

Regards,

Daniel
-- 
gentoo-user@lists.gentoo.org mailing list