8086:3582 plymouth splash screen fails for Intel 855GM Chipset

[Martin]

Binary package hint: plymouth

- to not encounter another bug (lockup), I need to boot with i915.modeset=1 enabled
- in either case just a short splash (before lockup) or none at all is visible but blinking cursors
- init tells me in daemon log that plymouth-stop pre-start process terminated with status 1

- might be related to my graphics chipset issue in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/566103

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CurrentDmesg:
 [ 20.760954] ppdev: user-space parallel port driver
 [ 26.532026] eth1: no IPv6 routers present
 [ 26.828028] eth0: no IPv6 routers present
Date: Tue Apr 20 15:32:22 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MTC Montara-GML
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=260f888b-e25c-42e1-b3a6-474579cbee3b ro splash quiet i915.modeset=1
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 06/09/2004
dmi.bios.vendor: Insyde Software Corporation
dmi.bios.version: R1.07
dmi.board.name: Montara-GML
dmi.board.vendor: MTC
dmi.board.version: FAB-2
dmi.chassis.asset.tag: 12345678
dmi.chassis.type: 8
dmi.chassis.vendor: MTC
dmi.chassis.version: A1
dmi.modalias: dmi:bvnInsydeSoftwareCorporation:bvrR1.07:bd06/09/2004:svnMTC:pnMontara-GML:pvrFAB-2:rvnMTC:rnMontara-GML:rvrFAB-2:cvnMTC:ct8:cvrA1:
dmi.product.name: Montara-GML
dmi.product.version: FAB-2
dmi.sys.vendor: MTC

[Steve Langasek (vorlon)]

> I need to boot with i915.modeset=1 enabled

Nothing to do with plymouth; this is an X/kernel bug. Reassigning.

[ubuntlin (fejri-lotfi)]

Hi,

I have the same bug : the plymouth fails in the boot in Ubuntu 10.04. What can i do or wht package i need upgrade or install ?

[Jeremy Foshee (jeremyfoshee)]

Hi Martin,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Martin (wortheld)]

- tested against linux-image-2.6.34-999-generic_2.6.34-999.201004281008_i386.deb
- result is the same regardless of KMS

- however, for all kernels during shutdown and disk examination, there is proper display

[Martin (wortheld)]

- with KMS forcedly off, upstream kernel reliably locks up on X's takeover

[Martin (wortheld)]

Problem can be fixed by giving initramfs-tools the order of setting bootarg FRAMEBUFFER to yes by creating

/etc/initramfs-tools/conf.d/splash with content "FRAMEBUFFER=yes" and updating the initial ramdisk by entering

sudo update-initramfs -u.

--

This will create a ramdisk where plymouth and utilities aren't missing. See attached diff.txt for what is created without this bootarg when building a ramdisk on my box the default way. This shouldn't be the case, I think!

[Sergio Melas (sergiomelas-gmail)]

The workaround of Martin work for me.
By the way I have seen that this:

delete pack files in /var/lib/ureadahead, reboot

Give the same result but with faster boot time.
This force reprofiling readhaed, see: http://ubuntuguide.net/howto-fix-ureadahead-problem-after-upgrading-to-ubuntu-10-04