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

Newegg Daily Deals

Reply
 
Thread Tools
Old 10-14-10, 04:49 PM   #13
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)

Still no luck with 260.19.12. The new driver seems to recognize the /proc/... EDID (as reported in the changelog), but the screen stays black. Again no relevant errors are found in the Xorg log, even when started with logverbose 6.

I also saw that the 310M is not reported as supported by the driver anymore. Has this anything to do with the black screen?

Cheers,
Alessandro
alexcriss is offline   Reply With Quote
Old 10-16-10, 09:38 AM   #14
taavikko
Registered User
 
Join Date: Oct 2010
Posts: 3
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Have to spend my two cents on this one.

GT 330m also is affected.
Boot freezes with the newer drivers.
No tty's available.
256.53 is last driver working.
Have to use CustomEdid option in Xorg.conf. (funny that with nouveau, I don't have to)

Sony vaio F11 series laptop.
taavikko is offline   Reply With Quote
Old 10-16-10, 10:07 AM   #15
auxbuss
Registered User
 
Join Date: Oct 2010
Posts: 10
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Ditto, taavikko.

Please let us know what test to run and diagnostics to provide.

01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2)
Sony Vaio F-series
Ubuntu 10.10 (worked fine on 10.4)
auxbuss is offline   Reply With Quote
Old 10-16-10, 11:19 AM   #16
XjCook
Registered User
 
Join Date: Oct 2010
Posts: 28
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

I tried generate any log message (for example X -(log)verbose 6 > nvidia.log) but it wasn't succesful, because after startx my laptop is frozen (I see only black screen and "_").

I'm think that problem is in detection of display, for example nouveau recognize my lcd as 2048x1536 instead of 1920x1080. Information about this bug is here.

My laptop is Sony Vaio F11M1E/W with GT330M.
XjCook is offline   Reply With Quote
Old 10-16-10, 10:17 PM   #17
damentz
Registered User
 
Join Date: Jan 2009
Posts: 59
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Quote:
Originally Posted by taavikko View Post
Have to spend my two cents on this one.

GT 330m also is affected.
Boot freezes with the newer drivers.
No tty's available.
256.53 is last driver working.
Have to use CustomEdid option in Xorg.conf. (funny that with nouveau, I don't have to)

Sony vaio F11 series laptop.
Hi taavikko,

Try removing the CustomEDID option with 256.53 - that was fixed some time ago for the GT3XX series with the Sony Vaio laptops.
damentz is offline   Reply With Quote
Old 10-18-10, 06:51 AM   #18
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)

Quote:
Originally Posted by damentz View Post
Hi taavikko,

Try removing the CustomEDID option with 256.53 - that was fixed some time ago for the GT3XX series with the Sony Vaio laptops.
Not working, 256.53 is broken on Vaio S series without the CustomEDID, as reported in this thread.

To generate the required logs connect via ssh to the laptop and get the relevant information, as AaronP suggested in this thread
alexcriss is offline   Reply With Quote
Old 10-18-10, 10:39 AM   #19
taavikko
Registered User
 
Join Date: Oct 2010
Posts: 3
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Quote:
Originally Posted by alexcriss View Post
Not working, 256.53 is broken on Vaio S series without the CustomEDID, as reported in this thread.
Vaio F11S1E is now working without the CustomEDID option.
But the 260.19.12 driver is still a no go.

Quote:
Originally Posted by alexcriss
To generate the required logs connect via ssh to the laptop and get the relevant information, as AaronP suggested in this thread
Will do as soon as I'll get my hands on to a another lappy...
taavikko is offline   Reply With Quote
Old 11-04-10, 08:47 AM   #20
XjCook
Registered User
 
Join Date: Oct 2010
Posts: 28
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Quote:
Originally Posted by AaronP View Post
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.
Hi, I generated bug reports over ssh as you suggested. Also I generated bug report for working driver 256.53.

And this is very interesting (from kernel dmesg):
Code:
ioremap error for 0x9e000-0x9f000, requested 0x10, got 0x0
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<(null)>] (null)
PGD 122c2b067 PUD 120a72067 PMD 0 
Oops: 0010 [#1] PREEMPT SMP 
last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video Driver/uevent
CPU 0 
Modules linked in: ipv6 nvidia(P) uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 snd_hda_codec_nvhdmi snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device arc4 snd_pcm_oss snd_mixer_oss ecb snd_hda_codec_realtek sony_laptop video output snd_hda_intel ac snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc button battery thermal fuse iwlagn vboxdrv iwlcore mac80211 sdhci_pci sdhci mmc_core led_class cfg80211 rfkill psmouse firewire_ohci firewire_core crc_itu_t pcspkr serio_raw ehci_hcd usbcore evdev cpufreq_powersave i2c_i801 i2c_core sr_mod cdrom sky2 cpufreq_ondemand intel_agp iTCO_wdt iTCO_vendor_support sg acpi_cpufreq freq_table processor mperf rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 fpu aesni_intel cryptd aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod uvesafb cn sd_mod ahci libahci libata scsi_mod

Pid: 5851, comm: X Tainted: P            2.6.35-ARCH #1 VAIO/VPCF11M1E
RIP: 0010:[<0000000000000000>]  [<(null)>] (null)
RSP: 0018:ffff8801209759c0  EFLAGS: 00010292
RAX: 0000000000000161 RBX: ffff8801245b2000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffff8801245b2000 RDI: ffff88012495c000
RBP: ffff880122c45ef0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88012495c000
R13: ffff88012495c000 R14: 0000000000000000 R15: 0000000000000000
FS:  00007f1f70d19840(0000) GS:ffff880001800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001209c9000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process X (pid: 5851, threadinfo ffff880120974000, task ffff88012519d340)
Stack:
 ffffffffa07a57b9 ffff8801245b2000 ffff8801245b2000 0000000000000000
<0> ffffffffa07b6050 0000000000000000 ffff8801245b2000 ffff88012495c000
<0> ffff8801245b2000 0000000000000000 ffffffffa07b3f09 ffff880122c24000
Call Trace:
 [<ffffffffa07a57b9>] ? _nv021430rm+0x13/0x26 [nvidia]
 [<ffffffffa07b6050>] ? _nv021329rm+0xf5/0x1b9 [nvidia]
 [<ffffffffa07b3f09>] ? _nv021186rm+0x268/0x4c6 [nvidia]
 [<ffffffffa07f8e07>] ? _nv009131rm+0x86/0x1b3 [nvidia]
 [<ffffffffa07f12fa>] ? _nv009646rm+0x1a0/0x237 [nvidia]
 [<ffffffffa090711f>] ? _nv014469rm+0x27b/0x4c9 [nvidia]
 [<ffffffffa0906043>] ? _nv014749rm+0xea/0x167 [nvidia]
 [<ffffffffa05f8912>] ? _nv014928rm+0xd/0x12 [nvidia]
 [<ffffffffa0acda3e>] ? _nv002152rm+0x160/0x26f [nvidia]
 [<ffffffffa0ace862>] ? _nv002146rm+0x492/0x65a [nvidia]
 [<ffffffffa0ad4279>] ? rm_init_adapter+0x89/0xfd [nvidia]
 [<ffffffffa0af00c4>] ? nv_kern_open+0x5c4/0x790 [nvidia]
 [<ffffffff81127d77>] ? chrdev_open+0x127/0x270
 [<ffffffff81127c50>] ? chrdev_open+0x0/0x270
 [<ffffffff8112229b>] ? __dentry_open+0x11b/0x3c0
 [<ffffffff811a2c5a>] ? security_inode_permission+0x1a/0x20
 [<ffffffff811234d4>] ? nameidata_to_filp+0x54/0x70
 [<ffffffff81131800>] ? do_last+0x480/0x740
 [<ffffffff81131cad>] ? do_filp_open+0x1ed/0x680
 [<ffffffff8113be0b>] ? generic_setattr+0xab/0x140
 [<ffffffff8113d284>] ? alloc_fd+0xf4/0x150
 [<ffffffff81123554>] ? do_sys_open+0x64/0x130
 [<ffffffff81123248>] ? sys_chown+0x68/0xa0
 [<ffffffff8112363b>] ? sys_open+0x1b/0x20
 [<ffffffff81009e82>] ? system_call_fastpath+0x16/0x1b
Code:  Bad RIP value.
RIP  [<(null)>] (null)
 RSP <ffff8801209759c0>
CR2: 0000000000000000
---[ end trace eb7fed3a7ff9de6b ]---
Attached Files
File Type: gz nvidia-bug-report-default.log.gz (25.1 KB, 106 views)
File Type: gz nvidia-bug-report-custom.log.gz (30.5 KB, 91 views)
File Type: gz nvidia-bug-report-256.53.log.gz (36.3 KB, 110 views)
XjCook is offline   Reply With Quote

Old 11-10-10, 12:28 PM   #21
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Thanks, XjCook. I debugged and fixed the bug that caused the kernel Oops you're seeing today. The next (after the 260.19.21) 260.xx NVIDIA Linux graphics driver release should work on your system.
zander is offline   Reply With Quote
Old 11-10-10, 12:49 PM   #22
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)

Quote:
Originally Posted by zander View Post
The next (after the 260.19.21) 260.xx NVIDIA Linux graphics driver release should work on your system.
Does it mean that the EDID will be correctly decoded for the Vaio VPCS or only that the kernel error is gone? Besides, thanks very much for the support

Cheers,
Alessandro
alexcriss is offline   Reply With Quote
Old 11-10-10, 02:11 PM   #23
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

X came up at the panel's native resolution on the Sony notebook I briefly had access to, and I believe it correctly read the EDID via ACPI. Unfortunately, I no longer have the notebook.
zander is offline   Reply With Quote
Old 11-10-10, 02:45 PM   #24
XjCook
Registered User
 
Join Date: Oct 2010
Posts: 28
Default Re: [260.19.0x Geforce 310M] Cannot read VAIO EDID (both with and without CustomEDID)

Quote:
Originally Posted by zander View Post
Thanks, XjCook. I debugged and fixed the bug that caused the kernel Oops you're seeing today. The next (after the 260.19.21) 260.xx NVIDIA Linux graphics driver release should work on your system.
Thanks for your support too. I'm very happy that this frustrated bug will be fixed
XjCook 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 05:22 AM.


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