[Needs noaccel quirk] Screen corruption on startup

Additional info
Adding nomodeset as a boot option allows X to startup and I'm able to test out the beta.

maybe the same bug like mine (take a look at #542639)

Hi D.,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Here are the requested log files. Note that these files were only able to be collected after a successful boot to the desktop. The failed boot did not provide any opportunity to collect the files. I've included both Xorg.0.log and Xorg.0.log.old.

Upstream is suspicious that vga16fb is part of the problem. Could you please re-try the beta, adding “blacklist=vga16fb” as a boot option rather than “nomodeset”? Thank you!

Added blacklist=vga16fb as a boot option. This didn't help. System still behaves the same. Screen becomes corrupted instead of showing the desktop. I am attaching the dmesg and X org log file from the attempt.

And you still can't switch virtual terminals?

I see that the same GPU lockup occurs in your dmesg (although it is much less noisy about it, so vga16fb might be doing *something* there).

It would be nice if the X driver could continue in this case. I'll bring this upstream.

Does booting with blacklist=vga16fb nouveau.noaccel=1 work correctly? You won't get a nice transition from plymouth to X with that but X should work with nouveau and it will help narrow down where the problem is.

Adding blacklist=vga16fb nouveau.noaccel=1 works. Desktop is up and running. I'm using FireFox now to update the comment.

The transition from the splash (plymouth? Ubuntu with the dots underneath) to desktop wasn't an issue. Screen went black for a couple of seconds and then desktop appeared.

Attaching dmesg and X org log again in case they help.

Lucid Beta1 (live CD) / Dell Inspiron 1520 / GeForce 8400M GS

"blacklist=vga16fb nouveau.noaccel=1" params didn't work for me, actually it did not change a thing.

After choosing the 'Try Ubuntu without changes on the system', the keyboard stopped responding (not even the caps lock key worked). First, I got for 1-2 seconds a black screen terminal (only the cursor was visible), after which a weird screen and finally sort of a grey screen. I've attached the last two screen images.

I'm sorry, I did some more testing and the keyboard worked. It switched between terminals, but the display didn't show it. For instance, ctrl+alt+f2, "sudo reboot", enter, enter = reboots the system. I was mislead by the fact that caps lock LED didn't work after switching with ctrl+alt+f2 (num lock & scroll lock LEDs work).

Hi.
Booting with a false parameter like "nouveau.fakeparam=yes" works fine.
System now starts an shows a beautiful lucid desktop.
Yours sincerely
Mike (ZeroBeat)

Confirmed that "noveau.fakeparam=yes" is a valid workaround for same video corruption on Dell Latitude D620 with the following line from an lspci:

"VGA Compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev A1)"

This bug is still apparent in beta 2.

@Marius Vasilescu: Your problem is different - that image is a classic badly-driven display problem - could you please test the most recent 2.6.32-19 kernel, as there have been some fixes for that sort of problem, and then file a new bug? Thanks.

@windexh8er: Your problem is *also* different, but should be fixed in the 2.6.32-20 kernel.

@Chris Halse Rogers: My laptop has been for warranty at Dell for almost 3 weeks, but as soon as it's back I'll test the Beta2.

@Chris Halse Rogers: Problem isn't fixed in the 2.6.32-20 kernel. System doesn't boot (take a look at #561497).

We've had other reports of GeForce 6100 cards failing to boot with the same problem. Given that disabling acceleration works, I think we should quirk off acceleration by default on these cards, too. Then at least you'll be able to boot properly.

We should add a match for PCIID 0242 to the noaccel quirk patch.

Ok, I've pulled in a bunch of Chris' patches to disable acceleration out of the box for these cards. Could those of you affected please test the kernel at the URL below and report back here. The kernels are at the URL below. Thanks:

    http://people.canonical.com/~apw/raof-nv-accel-lucid/

This bug was fixed in the package linux - 2.6.32-21.31

---------------
linux (2.6.32-21.31) lucid; urgency=low

  [ Andy Whitcroft ]

  * allow modules.builtin to be optional
  * d-i: add mpt2sas to the message-modules udeb
    - LP: #530361

  [ Christopher James Halse Rogers ]

  * SAUCE: Nouveau: Add quirk framework to disable acceleration
    - LP: #544088, #546393
  * SAUCE: Nouveau: Disable acceleration on MacBook Pros
    - LP: #546393
  * SAUCE: Nouveau: Disable acceleration on GeForce3 cards
    - LP: #544088
  * SAUCE: Nouveau: Disable acceleration on 6100 cards
    - LP: #542950

  [ Stefan Bader ]

  * SAUCE: dma-mapping: Remove WARN_ON in dma_free_coherent
    - LP: #458201

  [ Surbhi Palande ]

  * SAUCE: sync before umount to reduce time taken by ext4 umount
    - LP: #543617

  [ Upstream Kernel Changes ]

  * tipc: Fix oops on send prior to entering networked mode (v3)
    - CVE-2010-1187
  * KVM: x86 emulator: Add Virtual-8086 mode of emulation
    - LP: #561425
  * KVM: x86 emulator: fix memory access during x86 emulation
    - LP: #561425
  * KVM: x86 emulator: Check IOPL level during io instruction emulation
    - LP: #561425
  * KVM: x86 emulator: Fix popf emulation
    - LP: #561425
  * KVM: Fix segment descriptor loading
    - LP: #561425
  * KVM: VMX: Update instruction length on intercepted BP
    - LP: #561425
  * KVM: VMX: Use macros instead of hex value on cr0 initialization
    - LP: #561425
  * KVM: SVM: Reset cr0 properly on vcpu reset
    - LP: #561425
  * KVM: VMX: Disable unrestricted guest when EPT disabled
    - LP: #561425
  * KVM: x86: disable paravirt mmu reporting
    - LP: #561425
  * AppArmor: Fix put of unassigned ns if aa_unpack fails
  * AppArmor: Fix refcount bug when exec fails
    - LP: #562063
  * AppArmor: Take refcount on cxt->profile to ensure it remains a valid
    reference
    - LP: #367499
  * AppArmor: fix typo in scrubbing environment variable warning
    - LP: #562060
  * AppArmor: fix regression by setting default to mediate deleted files
    - LP: #562056
  * AppArmor: fix refcount order bug that can trigger during replacement
    - LP: #367499
  * AppArmor: Make sure to unmap aliases for vmalloced dfas before they are
    live
    - LP: #529288
  * AppArmor: address performance regression of replaced profile
    - LP: #549428
  * AppArmor: make the global side the correct type
    - LP: #562047
  * AppArmor: use the kernel shared workqueue to free vmalloc'ed dfas
  * sky2: add register definitions for new chips
    - LP: #537168
  * sky2: 88E8059 support
    - LP: #537168
  * net: Fix Yukon-2 Optima TCP offload setup
    - LP: #537168
  * net: Add missing TST_CFG_WRITE bits around sky2_pci_write
    - LP: #537168
  * sky2: print Optima chip name
    - LP: #537168
  * (Upstream) dell-laptop: defer dell_rfkill_update to worker thread
    - LP: #555261
  * drm/nv40: add LVDS table quirk for Dell Latitude D620
    - LP: #539730
 -- Andy Whitcroft <email address hidden> Tue, 13 Apr 2010 18:50:58 +0100