Bug 104596 - No boot splash after update to 10.0 beta1
Summary: No boot splash after update to 10.0 beta1
Status: VERIFIED DUPLICATE of bug 113573
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Hannes Reinecke
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-14 14:02 UTC by Christian Boltz
Modified: 2007-06-11 22:01 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2005-08-14 14:02:57 UTC 
After updating to 10.0 beta1, I don't have a boot splash. Instead I see a 
message "bootsplash: no good signature found". 
 
I had a similar issue after a 9.3 kernel update already - I had to run 
mkinitrd -s 1400x1050  and I expect this will work on 10.0 also (didn't test 
yet). 
 
Is there a way to have a working bootsplash automatically? ;-)
Comment 1 Dr. Werner Fink 2005-08-16 09:21:45 UTC 
IMHO this is an enhancment
Comment 2 Michael Schröder 2005-08-16 10:08:09 UTC 
I don't understand this. Isn't mkinitrd automatically run after the kernel 
update? Maybe the automatic resolution detection does not work, do you really 
need the "-s 1400x1050"? Anyway, as this is a mkinitrd problem I'm reassigning 
this to the mkinitrd maintainer. Maybe he has some more ideas...
Comment 3 Andreas Gruenbacher 2005-08-16 13:56:18 UTC 
We would need the trace (serial console) of booting with the "linuxrc=trace" 
boot loader option, please.
Comment 4 Christian Boltz 2005-08-16 22:35:13 UTC 
Could you please explain what you need a bit more detailed? 
 
I shall use the boot option   linuxrc=trace   - no problem so far. 
 
In the installed system? 
Or shall I boot the installation DVD? 
 
Is the trace written to boot.msg? 
Or is there another way to capture it? 
 
 
However, I think the problem is mkinitrd which seems not to be able to 
determinate the screen size on my system (Acer TravelMate 803 laptop 
(1400x1050) + external screen (1280x1024)). 
 
At least in 9.3, I needed "-s 1400x1050". I didn't have the time to test it in 
10.0 beta yet.
Comment 5 Christoph Thiel 2005-08-27 23:13:07 UTC 

*** This bug has been marked as a duplicate of 113573 ***