Bug 141098 - Boot splash lost after YOU kernel update
Summary: Boot splash lost after YOU kernel update
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Hannes Reinecke
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-29 09:58 UTC by Christian Boltz
Modified: 2006-05-22 10:10 UTC (History)
1 user (show)

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


Attachments
y2logs (149.04 KB, application/x-gzip)
2005-12-29 10:00 UTC, Christian Boltz
Details
mkinitrd called by rpm - bootsplash lost (127.06 KB, text/plain)
2006-03-07 20:01 UTC, Christian Boltz
Details
manual mkinitrd run - bootsplash works (128.19 KB, text/plain)
2006-03-07 20:02 UTC, Christian Boltz
Details
mkinitrd (76.01 KB, text/plain)
2006-03-31 07:20 UTC, Hannes Reinecke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2005-12-29 09:58:38 UTC
After the YOU update to the latest kernel security update, the bootsplash on tty1 was lost on my system. The console displayed text-only (vga=0x342 = 1400x1050, Acer TravelMate 803 laptop).

A manual call of   mkinitrd   without any parameter fixed the problem - but it should not be necessary to do so after installing a security update :-/
Comment 1 Christian Boltz 2005-12-29 10:00:05 UTC
Created attachment 61807 [details]
y2logs

# rpm -qf --last /boot/vmlinuz
kernel-default-2.6.13-15.7   Do 22 Dez 2005 21:38:12 CET
(just to give you a hint to the relevant timestamp in the log ;-)
Comment 2 Lars Marowsky-Bree 2006-01-17 11:18:56 UTC
Hannes, any idea why the mkinitrd wasn't called automatically?
Comment 3 Christian Boltz 2006-01-17 20:30:07 UTC
I'm not sure if mkinitrd "wasn't called" because I had no boot problems except the missing splash screen. If it was still the old initrd with old kernel modules, shouldn't I have noticed more problems (like modules not loading)?
Comment 4 Christian Boltz 2006-02-12 15:49:12 UTC
The boot splash was lost again after yesterday's kernel update :-(
Comment 5 Hannes Reinecke 2006-02-21 14:49:32 UTC
Well, actually it should be called. But as this is YOU doing the update maybe we should ask them?
Comment 6 Jiří Suchomel 2006-02-24 14:41:38 UTC
AFAIK YOU doesn't do such thinks, the patch has to care.
Comment 7 Chris L Mason 2006-02-24 15:10:46 UTC
If you can boot, mkinitrd was most likely called.   Could you please confirm this by looking at ls -la /boot/initrd?
Comment 8 Lars Marowsky-Bree 2006-02-28 14:42:42 UTC
mkinitrd is called in post.sh from the kernel package itself (except if running in the instsys).

This should do exactly the same as running it manually.
Comment 9 Olaf Kirch 2006-03-06 12:22:43 UTC
This is possibly a problem in mkinitrd itself. The %post script looks good.

I'm handing this back to Hannes for tracking.

Christian, could you please help in pin-pointing the actual problem?
For instance, you could downgrade your kernel, edit mkinitrd and add the
following pseudo patch at the top of the file:

 #
 # $Source: /suse/yast2/cvsroot/mkinitrd/mkinitrd,v $
 # $Revision: 1.210 $
+exec >/tmp/mkinitrd.$$ 2>&1
+echo "Running: $0 $*"
+env
+echo "************"
+set -x

 #
 # Print usage and exit

Then update your kernel, and attach the log file(s) generated by
mkinitrd to this bug report
Comment 10 Christian Boltz 2006-03-07 20:00:40 UTC
I just downgraded my kernel to the one from DVD (rpm -Uhv --oldpackage) - the bootsplash was lost again. Also, a manual "mkinitrd" call without any parameters brought it back.

I'll attach the mkinitrd logs - good luck in finding the problem ;-)
Comment 11 Christian Boltz 2006-03-07 20:01:32 UTC
Created attachment 71630 [details]
mkinitrd called by rpm - bootsplash lost
Comment 12 Christian Boltz 2006-03-07 20:02:21 UTC
Created attachment 71631 [details]
manual mkinitrd run - bootsplash works
Comment 13 Hannes Reinecke 2006-03-31 07:20:00 UTC
Created attachment 75874 [details]
mkinitrd

Fixed mkinitrd which reads the current framebuffer settings for selecting bootsplash images.
Comment 14 Hannes Reinecke 2006-03-31 07:23:09 UTC
Occasionally hwinfo --framebuffer would not return any data (if the BIOS is broken or something). Added to that the 'official' vga modes are only specified up to 1280x1024. So anything beyond that might simply be ignored.

I've fixed up mkinitrd to add the current framebuffer settings when selecting bootsplash images, too.
Still not perfect, as mkinitrd might be run when a different resolution is active, but the best we can do.
Comment 15 Christian Boltz 2006-03-31 22:56:14 UTC
I just did a kernel downgrade after installing the fixed mkinitrd script from comment #13.

This time, I see the bootsplash after the reboot :-)

Thanks for fixing this!
Comment 17 Andreas Jaeger 2006-04-05 14:42:46 UTC
Update approved Maintenance-Tracker-3916
Comment 18 Ruediger Oertel 2006-04-12 23:59:49 UTC
patchinfo please ...
Comment 19 Hannes Reinecke 2006-04-25 14:26:11 UTC
Patchinfo submitted.
Comment 20 Hannes Reinecke 2006-04-25 14:26:44 UTC
Closing bug.
Comment 21 Anja Stock 2006-05-22 10:10:37 UTC
released