boot splash screen

[sktsee]

On Thu, 19 Jul 2007 09:05:30 +0200, Luca Ferrari wrote:

> On Wednesday 18 July 2007 sktsee's cat, walking on the keyboard, wrote:
> 
>> What framebuffer driver are you using? Can you post the results from
>> the "sudo hwinfo --framebuffer" command?
> 
> 
> Here it is:
> 
> 02: None 00.0: 11001 VESA Framebuffer
>   [Created at bios.440]
>   Unique ID: rdCR.w9EuYHvR0MC
>   Hardware Class: framebuffer
>   Model: "ATI ATOMBIOS M56P    "
>   Vendor: "(C) 1988-2005, ATI Technologies Inc. " Device: "M56P    "
>   SubVendor: "ATI ATOMBIOS"
>   SubDevice:
>   Revision: "01.00"
>   Memory Size: 16 MB
>   Memory Range: 0xe0000000-0xe0ffffff (rw) Mode 0x0300: 640x400 (+640),
>   8 bits
>   Mode 0x0301: 640x480 (+640), 8 bits
>   Mode 0x0303: 800x600 (+832), 8 bits

[snip]

Well, it looks like you are using the vesafb driver, so there goes my
initial suspicion that your machine was erroneously loading one of the ATI
framebuffer drivers. I believe the vga= parameter only works with vga text
and vesafb graphic modes. But you're using vesafb, so obviously the
problem lies elsewhere.

One possible cause of the black screen could be related to the module fbcon
not loading correctly, or causing a sync problem after it's loaded. I saw
some reported issues in a google search which affected some older 2.6
kernel versions with fbcon and vesafb, including some with ATI cards. To
test for improper module loading do a fresh boot, open a terminal, and do
an "lsmod |grep fb" and see if fbcon is one of the modules loaded. If it
doesn't show up, then try "sudo modprobe -v fbcon". If that is successful,
then do "sudo /etc/init.d/console-setup reload" and then press ALT+CTRL+F1
to see if you have a visible console (login prompt).

If fbcon was already loaded, then it may be sync problem, or some totally
unrelated issue with the hardware. In that case, you probably need to file
a bug report.

good luck,

-- 
sktsee