Blank screen during system startup with Precise/Nouveau

Bug #1048261 reported by Jan Rathmann
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

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

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

> 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.

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).

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :

@Steve

Here is the dmesg output of such a boot.

The graphics board seems to have a TV out indeed, but it has never been used. Only the TFT flatscreen is connected via VGA out.

If the monitor is turned on only at the end of the boot, it would explain of course the observed behaviour that the monitor receives no input signal during boot.

Kind regards,
Jan

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Ok, so there seems to be a problem with plymouth managing to open the drm framebuffer; it falls back to the text splash screen which, in the vt_handoff case, is not visible.

Can you boot with plymouth:debug=file:/var/log/plymouth-debug.log added to the boot options, and attach the resulting file? (Either value of GRUB_GFXPAYLOAD_LINUX is fine)

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :

@Steve
I have attached the plymouth-debug.log from a boot without GRUB_GFXPAYLOAD_LINUX being set explicitly (=the default setting).

Revision history for this message
Steve Langasek (vorlon) wrote :

Ok, the key bit of the log is this:

[./plugin.c] query_device:Visual was FB_VISUAL_PSEUDOCOLOR, trying to find usable mode.

[./plugin.c] query_device:Visual is FB_VISUAL_PSEUDOCOLOR; not using graphics

This means your kernel is only presenting a 16-bit framebuffer for use, not a 32-bit framebuffer; plymouth doesn't support properly displaying on a 16-bit fb, so avoids using the fb at all to not present you with horrible wrong color palettes.

If this worked for you in lucid with a full-color splash screen, then there seems to be a bug in the nouveau kernel driver for no longer exposing the expected 32-bit framebuffer. Reassigning to the kernel.

If this can't be fixed in the kernel, we should blacklist this card in grub-gfxpayload-lists.

affects: plymouth (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc5-quantal/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-da-key needs-upstream-testing
Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :

@Joseph

I tested the upstream kernel, but I'm not sure which tag would be appropriate for the result.

When I boot with the upstream kernel, the "text splash" is shown, as if I would have booted with GRUB_GFXPAYLOAD_LINUX=text. But I had commented out this line before to see what the default behaviour is, and it seems that it falls back automatically to the text splash with kernel 3.6 as the default behaviour.

So using kernel 3.6 fixes it sort of in the way that the monitor shows something during boot and doesn't power off, but it is not fixed in the way that it still doesn't show the usual graphical boot logo (which worked in Lucid). That's why I'm unsure which is the appropriate tag.

I have also attached dmesg and plymouth-debug.log files from a startup with kernel 3.6, if those may be useful.

Kind regards,
Jan

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :
Revision history for this message
Christian Assig (chrassig) wrote :

I also have a computer with a GeForce2 MX/400 NV11 chip.

Booting with linux-image-3.5.0-16-generic (from the official quantal repository) also causes my screen to go to standby mode. It turns on again when the login screen is displayed. As suggested here, I tried two mainline kernels from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.5-quantal/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/

Both mainline kernels keep the screen on. I can see the boot animation (of lubuntu in my case. unity is too slow for me to work with since quantal and the removal of unity-2d). However, the colors of the boot screen seem to be wrong (white text "lubuntu", surrounded by a bright red "shadow"). I don't know if this color issue has to do with this bug, though.

Is there anything I can do to contribute to a solution for this bug?

Revision history for this message
Mat (matthewb-e) wrote :

I have seen this bug intermittently, perhaps one in twelve boots which makes it really difficult to debug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The v3.7-rc8 kernel is now available. It would be good to know if this bug exists in this mainline kernel as well. It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc8-raring/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :

I have tested the v3.7-rc8 kernel, the behaviour is exactly the same as with the 3.6 kernel: A text only splash is shown (without GRUB_GFX_PAYLOAD being explicitly set, so this is a small improvement), but I still don't get the normal, graphical splash as it used to work in Lucid.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
tags: removed: needs-upstream-testing
Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Jan Rathmann, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-07.00t needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
importance: Medium → Low
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers