Xorg doesn't properly configure nVidia and WXGA screen in Jaunty alpha 3

[Luca Zorzi]

Binary package hint: xorg

I just downloaded and burned Jaunty Alpha 3, and it doesn't configure my screen properly on my laptop.

The laptop is an Acer Aspire 5633 WLMi with a nVidia GeForce Go 7300 and a WXGA (1280x800) screen.
The screen remains completely black, except 2 groups of 4 pixel each on the top of the screen that are white.

It works in Safe Graphics Mode, but of course the resolution is only 800x600.

I think that this might be due to the nv driver, that used to have some problems with this card/screen.
If I'm not wrong, Intrepid worked well, while Gutsy needed the safe mode too.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
     Subsystem: Acer Incorporated [ALI] Device [1025:0090]
01:00.0 VGA compatible controller [0300]: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] [10de:01d7] (rev a1)
     Subsystem: Acer Incorporated [ALI] Device [1025:0090]

[Jorge Gustavo (jgr)]

Hi,
Have you tried the nvidia driver?
Some users reported success with nvidia legacy driver, with an additional option in /etc/X11/xorg.conf in Jaunty

Section "ServerFlags"
 Option "IgnoreABI" "True"
EndSection

You can install nvidia legacy drivers with apt-get and afterwards running nvidia-xconfig

I hope it helps.

[Bryce Harrington (bryce)]

Hi lucazorzi91,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

[Luca Zorzi (lucazorzi91)]

I tried both -96 and -180 nvidia driver but they conflict with xorg so it gets removed. If I reinstall it then nvidia-glx is removed.
I'll try with the legacy -76 driver.

Attached to this post there is Xorg.0.log when starting with the default nv driver.

[Luca Zorzi (lucazorzi91)]

I can confirm that the nvidia driver (180) works with the IgnoreABI setting in xorg.conf suggested by Jorge Gustavo

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.