Hello,
if I boot the Precise installation on the PC this report has been sent from (using Nouveau drivers on a Geforce 2 MX card), the screen stays blank ("No Signal") during the boot process:
- The grub menu is displayed as usual (allthough in low resolution of 1024x768, while the display's native resolution is 1280x1024)
- Then a few seconds after the text of the grub menu disappeared, the screen goes blank (and turns of a few seconds later due to lack of input signal). In this phase usually the Plymouth boot logo should appear.
- When the display manager is loaded, the screen finally turns back on again/receives input again.
This happens regardless if the system is upgraded or freshly installed.
It is also a regression from Lucid, where the boot process worked without such problems on this machine (also with Nouveau drivers).
If I set GRUB_GFXPAYLOAD_LINUX=text in /etc/default/grub, I get the text-only boot logo with correct screen resolution on startup and monitor doesn't power off in this case.
If I boot using "nomodeset", the graphical boot logo is displayed correctly but the screen resolution on the desktop is limited to 1024x768 (which is not acceptable).
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu30
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
Uname: Linux 3.2.0-30-generic-pae i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Sun Sep 9 16:34:19 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
MachineType: ECS K7S5A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic-pae root=UUID=979d6337-c3a8-4daa-9a97-4cd021dcb572 ro quiet splash vt.handoff=7
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic-pae root=UUID=979d6337-c3a8-4daa-9a97-4cd021dcb572 ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to precise on 2012-09-09 (0 days ago)
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: K7S5A
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr07.00T:bd04/02/01:svnECS:pnK7S5A:pvr1.0:rvnECS:rnK7S5A:rvr1.0:cvnECS:ct3:cvrVersion1.00:
dmi.product.name: K7S5A
dmi.product.version: 1.0
dmi.sys.vendor: ECS
> If I set GRUB_GFXPAYLOAD
> I get the text-only boot logo with correct screen resolution on
> startup and monitor doesn't power off in this case.
Given that you have a drm framebuffer listed in /proc/fb, this shouldn't happen. Could you boot this way and attach the /var/log/dmesg that results?
In the first dmesg log, I see the following:
[ 4.990494] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0)
[ 4.990503] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on TV encoder (output 1)
[ 5.152352] [drm] nouveau 0000:01:00.0: allocated 1280x1024 fb: 0x48000, bo eecfc800
I'm not sure what dpms mode 3 is. Do you have both a vga display and a TV out connected to this machine?
Later, we see:
[ 51.160214] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on TV encoder (output 1)
[ 51.170591] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0)
[ 51.170603] [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output A
[ 51.172240] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on TV encoder (output 1)
[ 60.039444] init: plymouth-stop pre-start process (1240) terminated with status 1
This suggests that 'dpms mode 3' is off, and 'dpms mode 0' is on, and the monitor is being turned on only towards the end of boot (the plymouth-stop error message shows that plymouth has died before it can be stopped normally).