10de:0533 [Acer Aspire 5520] Display detection fails

[Arto Jääskeläinen]

Description:
Lucid fails to detect correct display resolution 1280x800 and falls back to 1034x768 which is dizzy / ugly on that panel, fonts turn difficult to read. Trying manually to raise resolution to 1280x800 using "xrandr":
xrandr --newmode "1280x800" 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync
xrandr --addmode default 1280x800
xrandr -s 1280x800
Failed to change the screen configuration!

WORKAROUND: Boot with "nomodeset" results in clean startup with limited resolution. Installing proprietary GeForce drivers succeeds at that point and those closed drivers find correct resolution of lcd panel.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: arto 1668 F.... pulseaudio
CRDA: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xd0880000 irq 21'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250126,00100003 HDA:14f12c06,10250126,00100000'
   Controls : 11
   Simple ctrls : 8
CheckboxSubmission: c360bbb6360601b3aa4064805466b120
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=54e3b2b5-5c3f-481d-909c-4871299dff70
MachineType: Acer Aspire 5520
Package: linux (not installed)
ProcCmdLine: root=UUID=4b82befe-87c6-4ce7-912f-546eccfcc37c ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=fi_FI.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
Tags: lucid kconfig regression-release needs-upstream-testing
Uname: Linux 2.6.32-22-generic x86_64
UserGroups:

WifiSyslog:
 Jun 14 19:56:50 arto-laptop kernel: [ 553.160039] [drm] nouveau 0000:00:12.0: Load detected on output B
 Jun 14 19:58:38 arto-laptop kernel: [ 660.890044] [drm] nouveau 0000:00:12.0: Load detected on output B
 Jun 14 19:59:27 arto-laptop kernel: [ 710.510053] [drm] nouveau 0000:00:12.0: Load detected on output B
 Jun 14 19:59:56 arto-laptop kernel: [ 738.710047] [drm] nouveau 0000:00:12.0: Load detected on output B
 Jun 14 20:01:59 arto-laptop kernel: [ 861.600051] [drm] nouveau 0000:00:12.0: Load detected on output B
WpaSupplicantLog:

dmi.bios.date: 05/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.33
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.33:bd05/06/2008:svnAcer:pnAspire5520:pvrV1.33:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5520
dmi.product.version: V1.33
dmi.sys.vendor: Acer

[Arto Jääskeläinen (ajaaskel)]

Possibly related problem: Virtual terminals Ctrl-Alt-F1...F6 messed, show 3 or 4 times the same text overlayed across each other ---> unreadable. Typo: Acer falls back to resolution 1024x768.

[Arto Jääskeläinen (ajaaskel)]

FYI: Karmic was able to use right resolution. Resolution problem appeared after upgrading to Lucid.

[Arto Jääskeläinen (ajaaskel)]

FYI / possibly related: Attempted to use rt-kernel (Real Time kernel) instead of original Lucid kernel on another computer (Fujitsu Siemens Pi3630 desktop) results in unstable system and wrong display resolution. Those problems do not appear when running rt-kernel on Karmic in that same computer, i.e. problem not kernel-only related but other things in Lucid --- sorry I'm not able to point more exactly.

[Jeremy Foshee (jeremyfoshee)]

Hi Arto,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 575605

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

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

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

apport information

[Arto Jääskeläinen (ajaaskel)]

1) Installed 2.6.35-020635rc1-generic kernel, resulted in severe "screen corruption" (for me it looks like some code running over in screen buffer).

2) Attempted 10.01 alpha-1 from CD, similar results.

Current Lucid with standard kernel (which I use now) will also show upright colored lines (etc. extra mess) in the beginning while starting up.

[penalvch (penalvch)]

Arto Jääskeläinen, 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 kernel 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.12-rc1

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.

[Arto Jääskeläinen (ajaaskel)]

- Downloaded nightly build, made a live stick.

- Problems starting the image, total failure with display, terminal Ctrl-Alt-F1 in mess, too.

- Start with "nomodeset", success.

- Doing apport-collect was not possible, too many problems:

----------------------------------------------------
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

sudo apt-get install python-apport

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

sudo apt-get update

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/saucy-security/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy-updates/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/saucy-security/Release.gpg Could not resolve 'security.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy/Release.gpg Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/saucy-updates/Release.gpg Could not resolve 'archive.ubuntu.com'

W: Some index files failed to download. They have been ignored, or old ones used instead.
-----------------------------------------------------------

Summary: Problem has always been with display driver. Starting with "nomodeset" results in clean startup with limited resolution. Installing proprietary GeForce drivers succeeds at that point and those closed drivers find correct resolution of lcd panel.
Open drivers were last time working with correct resolution when using Ubuntu 9.10 32-bits.

[penalvch (penalvch)]

Arto Jääskeläinen, given the technical issues, please skip the apport-collect in Saucy.

Despite this, did you have to perform nomodeset in Karmic 9.10 for it to boot?

The next step is to bisect between Karmic and Lucid, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Launchpad Janitor (janitor)]

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