Binary package hint: plymouth
I tried to disable the splash screen on the live system by deleting "quiet splash" and adding vga=711. Then I choosed point 5 for vga. I Didn't know about plymouth because I used lucid the first time and I'm used to Hardy Heron, which is pretty old.
BTW: How can I disable plymouthd on boot to see all messages directly on tty1 in the case that the framebuffer of plymouthd is not functional? That was not the case for my setup, but I ask this because I tried to support someone who left with a black screen and a boot up hang. Therefore I tried to diable the splash. On the black framebuffer screen I tried to change to tty1 but that didn't work no longer. That might happened due to the crash.
This bugreport might be a duplicate of #540237.
ProblemType: Crash
Architecture: amd64
CurrentDmesg:
[ 98.954390] lp0: using parport0 (interrupt-driven).
[ 111.547854] [drm] nouveau 0000:01:00.0: Allocating FIFO number 1
[ 111.548390] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1
[ 168.190027] Clocksource tsc unstable (delta = -245571436 ns)
Date: Sat Mar 20 19:32:04 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /sbin/plymouthd
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 067b:2507 Prolific Technology, Inc. PL2507 Hi-speed USB to IDE bridge controller
Bus 001 Device 002: ID 05da:3008 Microtek International, Inc. Scanner
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System name
Package: plymouth 0.8.0~-17
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz vga=711 -- debian-installer/language=de console-setup/layoutcode?=de
ProcCmdline: /sbin/plymouthd --mode=boot
ProcEnviron: PATH=(custom, no user)
ProcFB:
0 nouveaufb
1 VGA16 VGA
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
Segfault happened at: 0x7f9faf419bdb <memcpy+347>: rep movsq %ds:(%rsi),%es:(%rdi)
PC (0x7f9faf419bdb) ok
source "%ds:(%rsi)" (0x01bf2900) ok
destination "%es:(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
memcpy () from /lib/libc.so.6
?? () from /lib/plymouth/renderers/frame-buffer.so
?? () from /lib/plymouth/renderers/frame-buffer.so
?? () from /lib/libply-splash-core.so.2
?? () from /lib/libply.so.2
Title: plymouthd crashed with SIGSEGV in memcpy()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:
dmi.bios.date: 09/29/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805
dmi.board.name: A8N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System name
dmi.product.version: 1.XX
dmi.sys.vendor: System manufacturer
cat /proc/fb
0 nouveaufb
1 VGA16 VGA
I didn't see any problems with the system now. I guess the bootparam vga=711 <enter> 5 <enter> or/and the few fast tries to switch to text console tty1 was the culprit.
The live system started several times without any problems with plymouth.