|
Bugzilla – Full Text Bug Listing |
| Summary: | Boot splash lost after YOU kernel update | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Kernel | Assignee: | Hannes Reinecke <hare> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2logs
mkinitrd called by rpm - bootsplash lost manual mkinitrd run - bootsplash works mkinitrd |
||
|
Description
Christian Boltz
2005-12-29 09:58:38 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 ;-)
Hannes, any idea why the mkinitrd wasn't called automatically? 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)? The boot splash was lost again after yesterday's kernel update :-( Well, actually it should be called. But as this is YOU doing the update maybe we should ask them? AFAIK YOU doesn't do such thinks, the patch has to care. If you can boot, mkinitrd was most likely called. Could you please confirm this by looking at ls -la /boot/initrd? 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. 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 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 ;-) Created attachment 71630 [details]
mkinitrd called by rpm - bootsplash lost
Created attachment 71631 [details]
manual mkinitrd run - bootsplash works
Created attachment 75874 [details]
mkinitrd
Fixed mkinitrd which reads the current framebuffer settings for selecting bootsplash images.
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. 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! Update approved Maintenance-Tracker-3916 patchinfo please ... Patchinfo submitted. Closing bug. released |