Created attachment 59271 [details] Part of system log When started kernel with kms-nouveau compiled in, the kernel logi is spammed every 10 seconds with unknown EDID messages:
Created attachment 59272 [details] EDID binary file Edid data file for eDP-1 output
Apart from the annoying messages are you experiencing any issues with nouveau ? A few thing to help out meanwhile Try with output polling turned off $echo 0 > /sys/module/drm_kms_helper/parameters/poll or provide a customer EDID - see linux/Documentation/EDID/HOWTO.txt and $modinfo drm_kms_helper
Emil thank you for the tip, it acts good as workaround. Now I just compiled new kernel with support of nouveau. And except of above described log spamming it works perfectly. But I don't understand one thing. Why the driver is mentioning different EDID data in the logs, and different in /sys/class/drm/card0/card0-eDP-1 While status of other video outputs is disabled
You're welcome, can you let me know are you loading the edid from file/firmware? And here is a bit of background about edid(s) The edid has header (block 0) and extensions (block 1-...), each 128 bytes in size drm core tries to retrieve the whole edid, thus in your case is failing to fetch extension #1 (block 1). Can you do the following * attach the edid retrieved from both the blob and nouveau * clearly indicate which one is which I assume the file attached was fetched with the blob running
Created attachment 69635 [details] Edid File retreived using nvidia settings from blob driver
Created attachment 69636 [details] Edid file from nouveau retreived from /sys/class/drm/card0-DVI-I-1
OK. Now I understand. Attached file was from nouveau. Now I attached both: from blob, and from nouveau with right description. If necessary, I could retreive and send bios from the video card, but I need to know how to find it. Right now I switched off polling, and the system works well. I tried to make it with external edid file, but system don't use it. I put file 1920x1080.bin in /lib/firmware, but without success. Thanks Mirek
This seems identical to the issue in the other bug, feel free to undup it if you think I'm wrong. Unfortunately I can't tell the linux kernel version you used from your logs... but please try out linux 3.5 or 3.6 -- it should work fine there, and also try with the latest kernel (e.g. 3.11-rc7) and report back on whether things work again now (all without setting poll=0). *** This bug has been marked as a duplicate of bug 64858 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.