10de:0429 plymouth boot screen corrupted with nouveau Quadro NVS 140M

I have near-identical (right down to the corruption pattern looking nearly the same) results on a GeForce 9800gt. It also works fine with the proprietary driver (As well as the proprietary driver works during bootup, anyhow)

I have the same issue on a Dell Optiplex 980.

The shutdown splash is working fine so it looks like an initialization issue.

Same problem on MSI M670 (GeForce Go 6100).

Same problem with Dell Latitude e6410 with nvidia GT218 [NVS 3100M]

Same for GeForce 8400M GS, 2.6.28-8-generic kernel.

EN9800GT (Asus)... init is borked.. shutdown works..

Same problem on a Sony Vaio VPCCW2S1E with Nvidia 330M.

I have to switch tty to enter my passphrase for encrypted root (luks) otherwise the screen stay corrupted.

Same here for GeForce 8400M GS with 3.0.0-11-generic-pae on Oneric i386 beta2 plus recent updates.

I have the same problem on a Dell XPS m1330 with GeFOrce 8400gs and Ubuntu 11.10 64 bit fully updated...

Same here on a Dell Precision M6400 on 10.11 64bit.

01:00.0 VGA compatible controller: nVidia Corporation G94M [Quadro FX 2700M] (rev a1)

Is upstream aware of this?

Hi!!!

Do you think we can fix with

echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash

sudo update-initramfs -u

?

http://www.worldofnubcraft.com/1621/make-plymouth-start-earlier-in-the-boot-process/

I tried this one but it did not work for me.

Disabling vt.handoff in /etc/grub.d/10_linux fixes this for me.

How did you disable it (it's not long time I'm using Ubuntu... :-) )?

sudo gedit /etc/grub.d/10_linux

# vt.handoff

and saving the file?

unoup11, I believe you have to run:
================
sudo update-grub2
================
to apply your modification to grub.

I see... and do you think the modification to apply is from

vt.handoff

to

# vt.handoff

?

No, no. You can't just hash comment mid-quote. Do something like this:

 68 for word in $GRUB_CMDLINE_LINUX_DEFAULT; do
 69 if [ "$word" = splash ]; then
 70 # GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT vt.handoff=7"
 71 GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT"
 72 fi
 73 done

Worked for me :) Thanx Jonathan.

Now plymouth starts late in the boot process, maybe we can fix by:

http://www.worldofnubcraft.com/1621/make-plymouth-start-earlier-in-the-boot-process/

what do you think Jonathan?

Other solution there:

https://help.ubuntu.com/community/Asus_U36JC

so we can try

1) put file splash inside /etc/initramfs-tools/conf.d/ with the content:

FRAMEBUFFER=y

and then

echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash

sudo update-initramfs -u

or

2) try with no splash file:

sudo echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash

sudo update-initramfs -u

It worked for me too. Thank you Jonathan!

Removing vt.handoff=7 from kernel parameters worked for me too.

Tried the fix in post #20

Corruption during boot still - though it does quickly disappear to show the throbber (if that's what it's called) for the remainder of the boot till desktop shows - set to autologin here so no login screen.

Xubuntu 12.04

GeForce 8500 GT

Same as forestpiskie, I tried the fix and the ugly screen still appears for half a second or so.

Ubuntu 12.04
GeForce 8600M GT

Works fine with the Nvidia drivers

Hi.

How to disable vt.handoff in /etc/grub.d/10_linux of Ubuntu 12.04?

just comment line 160?

68 for word in $GRUB_CMDLINE_LINUX_DEFAULT; do
69 if [ "$word" = splash ]; then
70 GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT \$vt_handoff"
71 fi
72 done

156 cat << 'EOF'
157 function gfxmode {
158 set gfxpayload="${1}"
159 if [ "${1}" = "keep" ]; then
160 set vt_handoff=vt.handoff=7
161 else
162 set vt_handoff=
163 fi
164 }
165 EOF

In ubuntu 12.04 with noveau driver I modified only

70 GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT"

and fixed for me

I'm seeing the same problem as Elfy. I modified line 70 but I still see corruption and then plymouth behaves normally.

Changing the title of this bug because it's not related to Thinkpads at all; it's an nVidia issue.

I can't find any mention of this issue outside of this bug report (and its duplicates). This may be an Ubuntu bug. Can anyone confirm this with the upstream kernel and/or upstream plymouth?

I use the vanilla 3.4 kernel and get this issue.

I observed the same behaviour as #29 on my Latitude E6400 with Nvidia Quadro NVS 160M graphics. Did the line 70 trick and the splash screen gets corrupted for a couple of seconds before plymouth shows up correctly.

Editing /etc/grub.d/10_linux sort of worked for me. Now, the corrupted image flashes briefly on the screen before displaying the uncorrupted splash. It's definitely an improvement, but something still isn't quite right.

Also, don't forget to run update-grub after editing the file.

Still issue in Quantal. Reproducible for me on many different laptops and nVidia GPU's.

RussianNeuroMancer, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

> could you please file a new report
I need to fill new report for every GeForce I tested for this bug (I remember at least 7300 GT, 7300 Go, 7400 Go, 8600M GT, ION, 240M, etc.) or one? If one, which one I should choose for bug report?

I pretty sure this issue reproducible not only on 8400M (10de:0429) but on wide rage or GeForce GPU's, that why I rename this bugreport. If it's same issue anyway, isn't it better to track this issue in one bugreport instead of few?

Won't Fix as Natty is EOL October 2012 as per https://wiki.ubuntu.com/Releases .

Marc Deslauriers, regarding your Bug Description:
"When using the nouveau driver, the boot screen is corrupted..."

Does the splash screen disappear and then you see the log in screen well enough to login, or does it hang at the splash and does not continue to the log in screen, or is the login screen also corrupted?

As well, changing package to linux as per sidebar E-Mail communication:
"It's probably a kernel bug. It's probably telling userspace that it supports graphics modes the hardware doesn't actually support."

is it still an issue ? as there is no recent comment, that report is closed.

Yes, this is still an issue. Please stop closing my bugs.

This is still an issue for me. On Ubuntu 12.04.

But I found out if I press F1 at boot up I'll see the normal boot screen. Is it possible to trigger this automatically ex. with a grub boot parameter?

Louis, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Christopher, why should I create a new bug report?

I know that Natty is EOL, but this bug is still an issue on newer Ubuntu releases with Nvidia GPUs and the nouveau driver and I have the exact same problem that this is described in this bug report.

HARDWARE:
Thinkpad T61p
GPU: nVidia Quadro FX 570M
Ubuntu 12.04 with kernel 3.2.0-32-generic, libdrm-nouveau2 2.4.43-0ubuntu0.0.2, xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3, mesa 8.0.4-0ubuntu0.6

This bug was nominated against a series that is no longer supported, ie raring. The bug task representing the raring nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

This bug was nominated against a series that is no longer supported, ie quantal. The bug task representing the quantal nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release