nothing is visible on screen during boot sequence with fbcon disabled -- really annoying when the system decided to run a periodic fsck

Bug #593408 reported by Joshua
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

I must disable fbcon due to bad driver. fbcon-nouveau requires X-nouveau (fbcon-nouveau and X-vesa is bad), which is unstable on this machine. fbcon-vesa doesn't work right.

This leaves me with must hard-disable fbcon (alias fbcon off).

Something got broke in an update since the lucid release where this now misbehaves. On release, this displayed a green screen with information on it, now that screen does not display.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Sun Jun 13 12:48:27 2010
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=ee79c471-4414-4d4f-8b4b-1460e1fa6be1 ro vga=normal nofb nomodeset noplymouth
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VGA16 VGA
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 04/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1009
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1009:bd04/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Joshua (joshudson) wrote :
Revision history for this message
Joshua (joshudson) wrote :

set invalid

local copy of /bin/plymouth was damaged

Steve Langasek (vorlon)
Changed in plymouth (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.