garbled graphics with 2.6.32-15 kernel

Bug #530976 reported by Andreas Schildbach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

On an Geforce 8800GTS system connected to a Dell 2405FPW:

2.6.32-14 detected my monitor reasonably well and had no trouble displaying GDM and the desktop.
2.6.32-15 does not even get the resolutions right and displays only garbage instead of the desktop.

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aschildbach 1401 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 22'
   Mixer name : 'Analog Devices AD1986A'
   Components : 'HDA:11d41986,104381b3,00100500'
   Controls : 37
   Simple ctrls : 21
Date: Tue Mar 2 22:09:55 2010
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=678f2ef6-04b0-4c21-8d7f-31f0692733f9
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
MachineType: System manufacturer System Product Name
Package: linux-image-2.6.32-14-generic 2.6.32-14.20
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=c01604a7-6990-432a-b63c-f91e7400872d ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.31
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-14-generic i686
dmi.bios.date: 02/05/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1301
dmi.board.name: M2NPV-VM
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1301:bd02/05/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Andreas Schildbach (schildbach) wrote :
Revision history for this message
Andreas Schildbach (schildbach) wrote :

Ok, on a second try:

1. plymouth does not show up. Instead, a text-mode progress bar is displayed.
2. GDM comes up, but low resolution
3. on first login, X seemed to crash, GDM comes up again. This time low resolution again but quite strange 1920x1024 aspect ratio
4. booted into desktop with this strange resolution (no garbage this time)

Revision history for this message
Andreas Schildbach (schildbach) wrote :

Note that all of the bug infos were collected with the -14 kernel that worked ok - an attempt to update the bug info with "ubuntu-bug -u 530976" because it insisted to create a new bug report.

Revision history for this message
Andreas Schildbach (schildbach) wrote :

Kernel 2.6.32-15-generic #21~drm33v1-Ubuntu from https://edge.launchpad.net/~apw/+archive/red/+packages gets the graphics right again, but GDM still crashes on the first login attempt. Or maybe it doesn't crash, but it asks for login credentials twice in a row.

Revision history for this message
Chase Douglas (chasedouglas) wrote :

@Andy:

This is a bug that was found in the -15 kernel you just released, but your red ppa kernel has doesn't have the issue. Win for .33 drm I guess?

Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
rasos (rasos) wrote :

Same situation here on motherboard ASUS M3N78-VM with Mythbuntu 10.04 kernel 2.6.32-22-generic. dmesg says at boot:
[ 17.309719] i2c i2c-0: nForce2 SMBus adapter at 0x600
[ 17.309726] ACPI: resource nForce2_smbus [0x700-0x73f] conflicts with ACPI region SM00 [0x700-0x73f]
[ 17.309729] ACPI: This conflict may cause random problems and system instability
[ 17.309731] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 17.309751] i2c i2c-1: nForce2 SMBus adapter at 0x700
[ 17.334792] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141

Additionally, I can not get the Nvidia nouveau working, various Xorg.confs tested.
Always get a: "Failed to initialize the NVIDIA gaphics device"
Can run only low graphics VESA mode, Xorg log file submitted at https://bugs.launchpad.net/ubuntu/+bug/561738

tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Andreas Schildbach, 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 run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11

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.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Andreas Schildbach (schildbach) wrote :

I do not have access to the machine any more.

Revision history for this message
penalvch (penalvch) wrote :

Andreas Schildbach, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/530976/comments/8 regarding you no longer have access to the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.