Your message dated Fri, 19 Jul 2013 18:00:44 +0200 with message-id <[email protected]> and subject line Re: linux-image-2.6.39-2-686-pae: linux >= 2.6.39 and spacefun splash screen don't mix: system fails to come up has caused the Debian Bug report #632824, regarding linux-image-2.6.39-2-686-pae: linux >= 2.6.39 and spacefun splash screen don't mix: system fails to come up to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 632824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632824 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-2.6 Version: 2.6.39-2 Severity: important This is the laptop of a coworker which runs Debian testing, but I have observed this problem on a Linux kvm VM running Debian unstable as well previously. To enable the spacefun splash screen, I had to do the following, according to information in the Debian Wiki, because otherwise, plymouth wouldn’t enter a graphics mode: root@rfisch-nb:~ # sed -n '/^[^#]/p' /etc/initramfs-tools/modules uvesafb mode_option=1400x1050-24 mtrr=3 scroll=ywrap Now, 2.6.38-2-686 boots but 2.6.39-2-686-pae fails to come up at all. On her laptop the screen stays totally black and no disc activity could be observed – it looks as if the system froze. On the Linux kvm VM, the screen gets garbled (like when switching from X back to the console for a short while), and the system also freezes. I have reported a similar bug to plymouth, by suggestion of waldi, but the comments there were not helpful. Stated goal is to have a splash screen (at this time, spacefun) while booting a Debian system. If I’m doing it wrong, please tell me how to do it the right way; reassign if necessary, as long as someone cares. -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh Versions of packages linux-image-2.6.39-2-686-pae depends on: ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy ii initramfs-tools [linux-initra 0.99 tools for generating an initramfs ii linux-base 3.2 Linux image base package ii module-init-tools 3.16-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.39-2-686-pae recommends: ii firmware-linux-free 3 Binary firmware for various driver ii libc6-i686 2.13-7 Embedded GNU C Library: Shared lib Versions of packages linux-image-2.6.39-2-686-pae suggests: ii grub-pc 1.99-6 GRand Unified Bootloader, version pn linux-doc-2.6.39 <none> (no description available) Versions of packages linux-image-2.6.39-2-686-pae is related to: pn firmware-bnx2 <none> (no description available) pn firmware-bnx2x <none> (no description available) pn firmware-ipw2x00 <none> (no description available) pn firmware-ivtv <none> (no description available) ii firmware-iwlwifi 0.30 Binary firmware for Intel Wireless ii firmware-linux 0.30 Binary firmware for various driver ii firmware-linux-nonfree 0.30 Binary firmware for various driver pn firmware-qlogic <none> (no description available) pn firmware-ralink <none> (no description available) pn xen-hypervisor <none> (no description available) -- debconf information: linux-image-2.6.39-2-686-pae/postinst/ignoring-ramdisk: * linux-image-2.6.39-2-686-pae/postinst/missing-firmware-2.6.39-2-686-pae: linux-image-2.6.39-2-686-pae/postinst/depmod-error-initrd-2.6.39-2-686-pae: false linux-image-2.6.39-2-686-pae/prerm/removing-running-kernel-2.6.39-2-686-pae: true
--- End Message ---
--- Begin Message ---On Wed, Jul 06, 2011 at 08:20:01PM +0000, Thorsten Glaser wrote: > Jonathan Nieder dixit: > > >Can you reproduce this with an upstream kernel? Can you bisect? > > Nope, won’t get paid for _that_ much effort. Sorry. Closing the bug, then. Cheers, Moritz
--- End Message ---
