No splash; monitor powers off before login

Bug #1019579 reported by Dave Gilbert
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since my upgrade to the Quantal alpha I'm not seeing a splash (this is mostly Kubuntu setup on this machine); what I see is:

1) BIOS
2) A grey screen (Kubuntu grey startup screen colour?) - for less than a second
3) Display goes into power save - for probably over 10 seconds
4) The login screen appears

(3) was long enough that at first I'd thought it had died.

It's done this for the last couple of weeks of update.

(i7 with Radeon HD4350, Dell S2490W monitor)

Dave

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic x86_64
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
Date: Sat Jun 30 14:35:06 2012
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-2-generic root=UUID=d8314979-8ace-401c-88df-728ad6b89cb5 ro ignore_loglevel netconsole=4444@192.168.66.33/eth0,514@192.168.66.25/00:a0:d1:63:68:a6 nointremap crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-2-generic root=UUID=d8314979-8ace-401c-88df-728ad6b89cb5 ro ignore_loglevel netconsole=4444@192.168.66.33/eth0,514@192.168.66.25/00:a0:d1:63:68:a6 nointremap crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
UpgradeStatus: Upgraded to quantal on 2012-06-17 (12 days ago)
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: P55M Pro
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrew Simpson (andrew-simpson) wrote :

Much the same as Comment #1. New install (with old home directory on separate partition and saved). AMD64 Kubuntu 12.10 on i5 with Radeon HD 6450.

Shutting down with multiple users causes the system to 'hang' and require cntrl-alt-del. I think because the dialog box in Kubuntu for shutting down other users wasn't showing up.

Changing from DVI to VGA cables has no effect. Playing with BIOS for on-board i5 video has no effect.

Added 'plymouth:debug' to kernel boot, and resulting log is attached.

Changed from open source Radeon driver to ATI proprietary (using 'additional drivers') and plymouth works as normal.

Revision history for this message
alopex (alopex) wrote :

I've got the same problem in Linux Mint: for less than three seconds (time between os selection in GRUB and login screen) my display powers off instead off showing the plymouth splash screen.
Weird though, since I got the splash screen the first couple of times I booted. I cannot recall, that I changed anything, that would effect plymouth. Although I'm just remembering that I had to reinstall GRUB2, because it had been installed in the Windows boot sector (I've got a dualboot system) instead of the MBR and Windows wouldn't boot anymore. But I couldn't say if that was the time when the splashscreen had gone...

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.