Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 09-17-10, 03:52 AM   #1
alexcriss
Registered User
 
Join Date: Sep 2010
Posts: 18
Default [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Hi everybody,

I tried using the nvidia beta driver on a Arch Linux system, however I am unable to get the display recognized.

Before this release I was using the 256.53 driver and I had to set
Code:
Option "CustomEDID" "DFP-0: /proc/acpi/video/IGPU/LCD0/EDID"
for recognizing the monitor (I know that from 256.44 EDID should be fixed, but it still does not work on my monitor as per http://www.nvnews.net/vbulletin/showthread.php?t=153720)

I tried switching to the beta driver and I have got a blank screen. The resulting Xorg log contains:
Code:
[   213.176] (**) NVIDIA(0): Option "NoLogo" "True"
[   213.176] (**) NVIDIA(0): Option "ConnectedMonitor" "DFP-0,DFP-1,CRT-0"
[   213.176] (**) NVIDIA(0): Option "TwinView" "1"
[   213.176] (**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select, DFP-1: NULL; DFP-1: nvidia-auto-select, DFP-0: NULL"
[   213.176] (**) NVIDIA(0): Option "CustomEDID" "DFP-0: /proc/acpi/video/IGPU/LCD0/EDID"
[   213.176] (**) NVIDIA(0): Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"
[   213.176] (**) NVIDIA(0): Option "TripleBuffer" "True"
[   213.176] (**) NVIDIA(0): Option "OnDemandVBlankInterrupts" "True"
[   213.176] (**) NVIDIA(0): OpenGL flipping disabled
[   213.176] (**) NVIDIA(0): Enabling RENDER acceleration
[   213.176] (**) NVIDIA(0): ConnectedMonitor string: "DFP-0,DFP-1,CRT-0"
[   213.176] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[   213.176] (II) NVIDIA(0):     enabled.
[   214.398] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
[   214.399] (WW) NVIDIA(GPU-0): Unable to use EDID file '/proc/acpi/video/IGPU/LCD0/EDID':
[   214.399] (WW) NVIDIA(GPU-0):     unable to map file
[   214.399] (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-0
[   214.402] (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-1
Code:
[   215.500] (WW) NVIDIA(0): Unable to get display device DFP-0's EDID; cannot compute DPI
[   215.500] (WW) NVIDIA(0):     from DFP-0's EDID.
Same results are obtained using possible combinations of 260.19.04, 260.19.06 and Xorg 1.8.1, Xorg 1.9.0.

If I do not specify the CustomEDID options (and all following settings like ConnectedMonitors and metamodes) the driver fails to recognize my display with:
Code:
[    16.944] (**) NVIDIA(0): Option "NoFlip" "True"
[    16.944] (**) NVIDIA(0): Option "NoLogo" "True"
[    16.944] (**) NVIDIA(0): Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"
[    16.944] (**) NVIDIA(0): Option "TripleBuffer" "True"
[    16.944] (**) NVIDIA(0): Option "OnDemandVBlankInterrupts" "True"
[    16.951] (**) NVIDIA(0): OpenGL flipping disabled
[    16.951] (**) NVIDIA(0): Enabling RENDER acceleration
[    16.951] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[    16.951] (II) NVIDIA(0):     enabled.
[    18.246] (II) NVIDIA(0): NVIDIA GPU GeForce 310M (GT218) at PCI:1:0:0 (GPU-0)
[    18.246] (--) NVIDIA(0): Memory: 524288 kBytes
[    18.246] (--) NVIDIA(0): VideoBIOS: 70.18.30.00.0e
[    18.246] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    18.246] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[    18.246] (--) NVIDIA(0): Connected display device(s) on GeForce 310M at PCI:1:0:0
[    18.246] (--) NVIDIA(0):     none
[    18.248] (EE) NVIDIA(0): No display devices found for this X screen.
[    19.498] (II) UnloadModule: "nvidia"
[    19.499] (II) UnloadModule: "wfb"
[    19.499] (II) UnloadModule: "fb"
[    19.499] (EE) Screen(s) found, but none have a usable configuration.
which is what I also get with previous driver's versions.

Furthermore, I noticed that as soon as udev starts loading modules my screen goes black (hence I cannot login even in console mode). This is solved by a nomodeset option when booting, which was not necessary before.

Hope this might be useful, feel free to ask further details if needed and sorry for my English!

Cheers,
Alessandro

Last edited by alexcriss; 09-27-10 at 11:31 AM. Reason: Typos
alexcriss is offline   Reply With Quote
Old 09-17-10, 09:37 AM   #2
65kid
Registered User
 
Join Date: Sep 2010
Posts: 3
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

I have exactly the same problem, already mentioned it here: http://www.nvnews.net/vbulletin/show...6&postcount=39

the external display works fine and is recognized as DFP-1, but the internal display simply turns off and I can't see it in the NVIDIA Settings.
Unfortunately, I can't do any more testing, as I already reverted back to 256.53... performance sucks, but at least it works...

btw, I didn't know you could just use /proc/acpi/video/IGPU/LCD0/EDID as the CustomEDID, I extracted the EDID under Windows and use it as a file. I'm gonna try this out, thanks...
65kid is offline   Reply With Quote
Old 09-27-10, 10:54 AM   #3
sPOiDar
Registered User
 
Join Date: Nov 2008
Posts: 15
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

CustomEDID confirmed broken here with 260.19.xx - actually hangs my display completely for me though - Geforce 9300M GS.
sPOiDar is offline   Reply With Quote
Old 09-27-10, 02:47 PM   #4
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

alexcriss,
The driver changed from using read() to using mmap() on the specified CustomEDID file, and apparently that fails for the special files in /proc, which is arguably a kernel bug. Please try copying the contents of /proc/acpi/video/IGPU/LCD0/EDID to a normal file on the filesystem and then pointing CustomEDID at that.
AaronP is offline   Reply With Quote
Old 09-27-10, 08:29 PM   #5
sPOiDar
Registered User
 
Join Date: Nov 2008
Posts: 15
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Quote:
Originally Posted by AaronP View Post
alexcriss,
The driver changed from using read() to using mmap() on the specified CustomEDID file, and apparently that fails for the special files in /proc, which is arguably a kernel bug. Please try copying the contents of /proc/acpi/video/IGPU/LCD0/EDID to a normal file on the filesystem and then pointing CustomEDID at that.
Both myself and 65kid have always been using files dumped from Windows. And rather than breaking user configurations, why not revert that change?
sPOiDar is offline   Reply With Quote
Old 09-28-10, 02:25 AM   #6
alexcriss
Registered User
 
Join Date: Sep 2010
Posts: 18
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Hi AaronP,

I've tried your suggestion, using both the bin file dumped from windows provided in the topic linked in my first post and a cp /proc/acpi/video/IGPU/LCD0/EDID /etc/X11/edid.bin.

The Xorg log does not report the previous error message for either solution, however the screen stays black and GDM does not come up. Furhter, I do not see any other error in Xorg.0.log.

This is unfortunate since the new driver kills my laptop LCD in whatever way I try to use it

Last edited by alexcriss; 09-28-10 at 04:49 AM. Reason: typos
alexcriss is offline   Reply With Quote
Old 09-28-10, 07:48 AM   #7
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

That sounds like a different issue, then. Can you SSH into the computer? If so, please try running X over SSH with "startx -- -logverbose 6" both with your custom configuration, and with the ConnectedMonitor and CustomEDID options removed, generating an nvidia-bug-report.log.gz for each scenario, and then attach both of them to your reply.

I filed a bug about CustomEDID using mmap(), and we'll change it back to read() in a future release.
AaronP is offline   Reply With Quote
Old 09-28-10, 02:24 PM   #8
alexcriss
Registered User
 
Join Date: Sep 2010
Posts: 18
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Hi AaronP,

please find attached the requested information.

The files containing noedid in the name refer to X started without the CustomEDID option, while the files with edid are for the configuration specified in the first post, using a edid stored by copying the one under /proc.

Please note that when the CustomEDID is not set the X server fails to recognize the display and dies. In this case I've generated the nvidia-report after the crash. However, when setting CustomEDID = /etc/X11/edid.bin the X server appears to be working (but the screen stays black) and the nvidia-report script hangs. I waited 20 min and then got the log.gz while the routine was still running.

I hope the provided information is useful, if I made some mistakes collecting data please tell me and I'll go through the process again!

Alessandro
Attached Files
File Type: gz nvidia-bug-report-edid.log.gz (41.2 KB, 152 views)
File Type: gz nvidia-bug-report-noedid.log.gz (47.6 KB, 144 views)
File Type: txt Xorg-log-edid.txt (7.1 KB, 163 views)
File Type: txt Xorg-log-noedid.txt (9.9 KB, 157 views)
alexcriss is offline   Reply With Quote

Old 09-28-10, 03:41 PM   #9
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Hmm, you're right that the driver isn't detecting the laptop's internal panel. 260.19.06 has fixes for panel detection on a number of quirky laptops, but apparently it's not working for yours.

Your log is missing the verbose messages that I requested, so I can't tell which mode it's setting or how it got validated in the CustomEDID case.
AaronP is offline   Reply With Quote
Old 09-28-10, 04:02 PM   #10
alexcriss
Registered User
 
Join Date: Sep 2010
Posts: 18
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Hmm that's strange, I started X with -- -logverbose 6 and skimmed through the logs which say verbosity level 6 (or something similar). Am I missing something?

I will try to post new logs tomorrow evening, but sure this Vaio display is a major source of pain!

Before the usual cheers, I would really like to thank you AaronP for the kind help. Providing logs is nicer when people care and answer!

Cheers,
Alessandro
alexcriss is offline   Reply With Quote
Old 09-28-10, 05:27 PM   #11
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

You're right, it sure does say "log verbosity: 6". I wonder if they got truncated somehow. Some of the lines that normally show up in the log file seem to be missing.

There's a bug filed on panel detection problems on some VAIO laptops, so hopefully that's the same issue and it'll be fixed in a future release. For future reference, the bug number is #681330.
AaronP is offline   Reply With Quote
Old 09-29-10, 09:36 AM   #12
alexcriss
Registered User
 
Join Date: Sep 2010
Posts: 18
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Thanks again!

I'll try to get new logs then, however I'm leaving tomorrow for Germany and I don't think I'll be able to find some bug-squashing time before Monday.

Just a few more questions.
1) You mentioned a bug report, is it visible by users (I couldn't find a bug reporting place for nvidia apart from this forum)
2) Should I refrain to update to 260.19.xx when it becomes stable or the stable release may have further fixes (e.g. panel fixes or read() again).

Cheers,
Alessandro
alexcriss is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 11:13 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.