[Hardy] Screen detection problems with xorg, nvidia and an Acer AL2216W

[Creak]

It makes now almost 6 years that I'm on Linux, and I can say that I never had such problems with nvidia/xorg and my screen until now. Even though I had some really hard one back on my old Debian and all the kernel recompilation stuff. That was just to say that, even if I'm not an expert, I know few stuff about how to get my screen recognized by the xserver.

But this time, it feels like the whole xorg/nvidia/acer combo is broken. This bug appears one week ago (after an update which included the xorg and linux kernel packages) and each day nights until then I tried to solve the problem, which I didn't have. So it's really my last chance here...

To be sure it wasn't a complete mess in my configuration files that was the cause of this problem, I've just reinstalled a whole new Ubuntu 8.04 beta, freshly downloaded and burned. The result is the same: can't get my screen detected with nvidia driver enabled.
It wouldn't be a real problem if the nv driver was capable of detecting wide resolution screens. I could wait until the next nvidia or xorg release. But here I'm writing on a 22" screen with a 1280x1024 resolution. Might as well say that I'm even considering to switch back to Windows (and I really don't want to!), but I need to work on my computer...

Here is what I tried for now:
The biggest resolution I can have with the nv driver is 1280x1024.
The biggest resolution I can have with the nvidia driver is less than 640x480. Each time I tried a resolution above, the screen was displaying a completely wrong resolution (like taller than wider) and the screen was like vertically shifted down.

I tried nvidia-settings to configure my xorg config file.
I tried writing my own config file, with the appropriate modelines gathered from google searches.
I tried configuring with the gnome-system-monitor app. Using preset generic screens (LCD Panel 1680x1050, LCD Panel 1920x1080, Monitor 1600x1200, and all with or without wide screen checked).
I tried also adding a configured screen using the .inf file of my LCD (Acer AL2216W).
I tried with generic or 386 version of the 2.6.24-11 and 2.6.24-12 kernels.
I also tried to install the driver with the envyng app.
I'm sure I tried other stuff, but I can't remember. At least I can say that I tried! :)

It feels like the last nvidia driver or the last xorg release (or both) can't detect my screen anymore.

Here is the packages installed:
* linux-images-2.6.24-12-generic (v2.6.24-12.22)
* xorg (v1:7.3+10ubuntu7)
* nvidia-glx-new (v169.12+2.6.24.11-12.31)
(I repeat, this is a freshly new installation from this morning, so I don't have 10 different configs that could be in conflict anymore, but the result is the same)

I'll attach my xorg.conf, and the other I tried and the xorg log.

[Creak (romain-failliot)]

For the previous xorg.conf file, I also tried the same one, but with nvidia driver... It didn't work either.

Here is another one I tried, I found it on Internet, it's from a guy that had the same hardware configuration. Didn't work... as you see...

[Creak (romain-failliot)]

Here is the xserver log, with the very first xorg.conf (i.e. nv driver and 1280x1024 res)

[Creak (romain-failliot)]

I've just rebooted with the nvidia driver activated in the xorg.conf. My resolution is 640x480, compiz is working and here is the xorg log.

[Creak (romain-failliot)]

I tried installing manually the 169.04, 169.07, 169.09 and 171.06 versions. The problem is still the same: it just can't read EDID and then falls back to the ugly 640x480 resolution.

I also tried forcing the resolution with a modeline as recommended here:
http://gentoo-wiki.com/HARDWARE_AL2216W
But it was even worst, the refresh rates are completely messing up the display (the resolution is still something like 640x480, but it's also horizontally shifted).

It seems like it's not the nvidia driver, but more the last xorg update that has broken the EDID module.

(Maybe it's my monitor or my graphic card that is broken, but I hardly believe that only the EDID module would crash if there was a hardware problem, in any case, if someone has an Acer AL2216W monitor running on the last Ubuntu 8.04 beta, please say it here!)

[Creak (romain-failliot)]

Another guy has exactly the same problem. He has the same monitor, but a different graphic card (8600GT).
And it happened when he updated his ubuntu.

ubuntu-fr post: http://forum.ubuntu-fr.org/viewtopic.php?pid=1626823#p1626823

[Creak (romain-failliot)]

Just to say it still doesn't work :(
Here is the nv thread: http://www.nvnews.net/vbulletin/showthread.php?t=110329

I can't understand the read-edid part... If someone have an idea?

[lameire (alexisis-pristontale)]

i have the same error with my nvidia fx 5200
i am welcom to the group

[maicolpiton (maicolpiton)]

Hi, same problem here with Hardy Heron and the AL2216W (actually recognized as a "plug n play monitor" ) on a Geforce 8600 GT

[clay.osi (clay.osi)]

I'm experiencing the same problem with hardy 8.04 beta, using acer AL1916W and Nvidia 8500 GT running the proprietary nvidia driver. Any news on a fix?

[clay.osi (clay.osi)]

OK, i fixed my problem, others may consider using the same fix go here http://ubuntuforums.org/showthread.php?t=745508&page=5 and look at the post by biasedopiniondrummer. thats what worked for me

YES!!! Success! ok, this is what i did to get it to work. ran this command

Code:

sudo apt-get install nvidia-glx-new && sudo dpkg-reconfigure xserver-xorg

(originally posted here by jlacroix

Then I used envyng to install the new nvidia drivers and it was a success!!! I used the GUI but you could use the command line by typing
Code:

envyng -t

in the terminal or as root in recovery and choosing the install nvidia choice.

I'll post this multiple places, hopefully it will help someone! Thanks to everyone who helped!

[maicolpiton (maicolpiton)]

thank you very much clay.osi!

[Creak (romain-failliot)]

Still doesn't work for me. I tried with your solution and it gave me exactly the same result.
And I tried with the version 173.08 of the nvidia driver and I had a bad resolution, but for an reason I don't understand, the X log was full of "VESA" lines instead of "NVIDIA". As if the last beta driver wasn't even recognized.

[M Pietila (pietila-meghan)]

I also had the same problem using the nvidia driver through the Restricted Drivers Manager - I could get 800x600 resolution through nv (hardly great, but that's a different issue), but once I loaded the nvidia driver through the Manager, I could only get 640x480.

Did these three steps this weekend:

1. Turned off the Restricted driver through the interface (i.e. uncheck the checkbox) and restarted Linux
2. Renamed the xorg.conf file I had been using (so I'd start from a clean slate with no xorg.conf file)
3. Installed envyng from the Hardy repository, then used the gui to install the latest nvidia driver

That fixed my problem, I'm finally getting great resolution (to anyone who tries it--remember, you need a full reboot not just an xserver restart). I'm also finally able to get both my monitor and my projector running as clones, I'd spent the past couple of weeks struggling with that (to get the dual monitors running, I used the Nvidia settings gui from the System menu).

Would be great if whatever is wrong with the Restricted Drivers Manager install gets fixed, though, new people trying out Ubuntu aren't going to figure out to use envyng instead, and even if they do they'll probably be frustrated at having to download and install something "extra" just to get the machine up and running to play with it. Even if people are used to installing extra drivers with Windows, they seem to set higher standards for Linux.

[Matthieu Yiptong (ergosteur)]

I have the same problem with an Acer AL1916. It worked with gutsy, and it works on my laptop's Intel GMA950. I'm going to try envy and see if that helps.

[Creak (romain-failliot)]

I've just tried your technique M Pietila but it stills doesn't work.
It seems that globally, the idea of removing then reinstalling everything doesn't work for my problem. I think I tried quite everything now.

BTW, I retried the 173.08 so that there wasn't the "VESA" lines. I succeeded (i.e. I had "NVIDIA" lines instead), but the problem is still here... :(

I'll try another complete reinstallation of Ubuntu when I'll have the time...

[besson3c (joe-netmusician)]

I finally got my resolution back after a lot of work by uninstalling the Restricted Driver, the Envy driver, rebooting, and installing the beta NVidia driver by hand.

[besson3c (joe-netmusician)]

The solution of installing the beta driver is temporary at best, since some apps such as Wine don't recognize the presence of OpenGL acceleration this way. Please do post a workaround to this if you know of one, and if not too complex and outside of the scope of this bug.

[Creak (romain-failliot)]

I found a workaround: use the VGA plug for the screen. (I also reinstalled the whole ubuntu because all the changes had ruined my xorg config file, but even before the reinstallation, the VGA cable was showing some improvements).

[besson3c (joe-netmusician)]

This error message may be new, this occurred after the latest restricted-driver package upgrade recently made available:

May 3 21:59:05 mycomputer kernel: [ 58.066676] NVRM: API mismatch: the client has the version 173.08, but
May 3 21:59:05 mycomputer kernel: [ 58.066679] NVRM: this kernel module has the version 96.43.05. Please
May 3 21:59:05 mycomputer kernel: [ 58.066680] NVRM: make sure that this kernel module and all NVIDIA driver
May 3 21:59:05 mycomputer kernel: [ 58.066681] NVRM: components have the same version.
May 3 21:59:10 mycomputer kernel: [ 60.488021] NVRM: API mismatch: the client has the version 173.08, but
May 3 21:59:10 mycomputer kernel: [ 60.488023] NVRM: this kernel module has the version 96.43.05. Please
May 3 21:59:10 mycomputer kernel: [ 60.488024] NVRM: make sure that this kernel module and all NVIDIA driver
May 3 21:59:10 mycomputer kernel: [ 60.488026] NVRM: components have the same version.

My card should be using nvidia-glx-new, not nvidia-glx

[besson3c (joe-netmusician)]

I forgot to add above that what I wrote about 3D acceleration not working in WINE can be disregarded, as I had forgot to install the 32 bit compatibility libs.

[Creak (romain-failliot)]

Just to say I tried with a 7800 (or 7600?) and the same bug happened again. But on this card there is only DVI output, so I had to go back to the "old" 6600.

[maicolpiton (maicolpiton)]

Hi,
This morning i casually found this interesting link

http://myy.helia.fi/~karte/acer_al2216w_-_22_inch_monitor_with_linux.html

It seems that the problem actually resides in the dvi/vga adapter which makes the monitor unrecognizable by the displayconfig-gtk package

https://bugs.launchpad.net/ubuntu/+source/displayconfig-gtk/+bug/137517

Anyway manually fixing the xorg.conf as the first link suggests works really well for me.

Hope can help

[Creak (romain-failliot)]

At last? a solution? It's the most beautiful saturday I ever had ! :D
Well I try it right away!
Keep in touch

2008/9/20 Simone Perelli <email address hidden>

> Hi,
> This morning i casually found this interesting link
>
> http://myy.helia.fi/~karte/acer_al2216w_-_22_inch_monitor_with_linux.html<http://myy.helia.fi/%7Ekarte/acer_al2216w_-_22_inch_monitor_with_linux.html>
>
> It seems that the problem actually resides in the dvi/vga adapter which
> makes the monitor unrecognizable by the displayconfig-gtk package
>
> https://bugs.launchpad.net/ubuntu/+source/displayconfig-gtk/+bug/137517
>
> Anyway manually fixing the xorg.conf as the first link suggests works
> really well for me.
>
> Hope can help
>
> --
> [Hardy] Screen detection problems with xorg, nvidia and an Acer AL2216W
> https://bugs.launchpad.net/bugs/205093
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Creak (romain-failliot)]

Well, sorry... I know this page :(
Actually I remembered I couldn't answer the questions of "sudo
dpkg-reconfigure xserver-xorg" even if it should be "obvious".

I'll retry late and mark the questions I don't know how to answer.

[maicolpiton (maicolpiton)]

Hi,
sudo dpkg-reconfigure xserver-xorg does not work for me too.

Instead open your xorg.conf with gedit (or whatever you like) as:

sudo gedit /etc/X11/xorg.conf

and replace the Section "Monitor" with this one taken from the Gentoo Wiki

Section "Monitor"
       # Block type: 2:0 3:fd
       # Block type: 2:0 3:fc
       Identifier "Acer AL2216W"
       VendorName "ACR"
       ModelName "Acer AL2216W"
       # Block type: 2:0 3:fd
       HorizSync 30-82
       VertRefresh 56-76
       # Max dot clock (video bandwidth) 210 MHz
       # Block type: 2:0 3:fc
       # Block type: 2:0 3:ff
       # DPMS capabilities: Active off:yes Suspend:no Standby:no
       Mode "1680x1050" # vfreq 59.954Hz, hfreq 65.290kHz
               DotClock 146.250000
               HTimings 1680 1784 1960 2240
               VTimings 1050 1053 1059 1089
               Flags "+HSync" "-VSync"
       EndMode
       # Block type: 2:0 3:fd
       # Block type: 2:0 3:fc
       # Block type: 2:0 3:ff
EndSection

Then replace the Section "Screen" with this one

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Acer AL2216W"
    DefaultDepth 24
    SubSection "Display"
      Depth 24
      Modes "1680x1050"
   EndSubSection

having a nvidia card I first launched sudo nvidia-xconfig and then replaced the two sections as explained above

Hope can help

[leo (leodicarpacio)]

Hello everybody,

I had the exactly same problem with my screen IIYAMA E2607WS and my laptop equipped with a NVIDIA GeForce 5200FX under kubuntu 8.10. I begun to be really fed up about this.
After a lot of tests It appears effectively that there is a bug inside xorg server which is unable to read EDID data from external screen.
To solve my problem and make my screen works on VGA port with a 1920x1200 resolution, I did this
 - I install read-edid with "sudo apt-get install read-edid"
 - I launch the related command and redirect output : "sudo get-edid > tmp.txt"
 - I parse the resulted file : "parse-edid < tmp.txt"
 - It gives you everything already correctly printed for your xorg.conf file. Just include it in. (in fact it will overwrite incorrect default values by real and adapted values from and for your monitor)
 - restart you xserver and configure as you want with nvidia-settings tool.

I hope it will help you

Bye

[bugbot (bugbot)]

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.