Bug 102913

Summary: Nouveau on >4.12.12 not loading EDID
Product: xorg Reporter: andrewb03
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: high CC: fdsfgs, jan.public
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Arch 4.12.13 dmesg none

Description andrewb03 2017-09-21 00:48:24 UTC
Created attachment 134394 [details]
Arch 4.12.13 dmesg

System: Arch Linux
CPU: AMD Ryzen 1700
Motherboard: Gigabyte AX370 Gaming K7
After an upgrade from Arch Linux kernel 4.12.10 to 4.12.12 (or 4.12.13) the system will hang just before initializing nouveaufb.  The system doesn't respond to keyboard or mouse but can be reset with the Ctrl+Alt+Del or accessible via ssh.

If I turn off KMS via nomodeset nouveau.modeset=0, I am able to boot normally but without graphics acceleration.c

The following showed in dmesg from kernel 4.12.13:

[   12.945435] nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-1
[   13.087167] gnome-shell[901]: segfault at 28 ip 00007ffab9d672f5 sp 00007fff5771ba20 error 4 in libmutter-0.so.0.0.0[7ffab9d1d000+139000]
[   16.264988] nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-1
[   16.286324] nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-1

As a result of this I have to either use the nvidia proprietary drivers or not upgrade.

This seems to be the exact opposite of a 4.12 regression reported where EDID would not load on 4.12 kernels with DP.

I have two PCIe GPUs: GK104 and GP102.  Neither are detected on those kernel versions.  I tested 4.13 as well and it can't find the EDID either on that kernel version.
Comment 1 andrewb03 2017-10-01 15:26:45 UTC
Issue still occurs on 4.13.3 (Arch Linux default kernel).
Comment 2 caguduzexi 2018-01-29 13:59:21 UTC
Problem still there with GK104 and latest kernel? Also on other linux OS? You could try out for example some ubuntu daily testing iso.

I wont recommend using/keeping the GP102. It cant ever run with free software: https://www.theregister.co.uk/2015/04/15/nvidia_gtx_900_linux_driver_roadbloack/
https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-XDC2017
https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-XDC2016-NVIDIA

Sell this crappy GP102 card away and go away from nvidia. Nvidia died with the 780ti card. Its the last end-user card that can be used normaly. Everything else is in some countries even a legal problem. Because the manufacturer (nvidia) blocks the users from beeing able to boot the software they want on THEIR hardware - happyly illegal in some countries. Hopefully some layer would sue the heck out of nvidia so that they would have to release the private signing key or close their doors.
Blocking the freedom of the users on such way should not be accepted by anyone.
Comment 3 Martin Peres 2018-01-29 17:35:47 UTC
(In reply to caguduzexi from comment #2)
> Problem still there with GK104 and latest kernel? Also on other linux OS?
> You could try out for example some ubuntu daily testing iso.
> 
> I wont recommend using/keeping the GP102. It cant ever run with free
> software:
> https://www.theregister.co.uk/2015/04/15/
> nvidia_gtx_900_linux_driver_roadbloack/
> https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-XDC2017
> https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-XDC2016-NVIDIA
> 
> Sell this crappy GP102 card away and go away from nvidia. Nvidia died with
> the 780ti card. Its the last end-user card that can be used normaly.
> Everything else is in some countries even a legal problem. Because the
> manufacturer (nvidia) blocks the users from beeing able to boot the software
> they want on THEIR hardware - happyly illegal in some countries. Hopefully
> some layer would sue the heck out of nvidia so that they would have to
> release the private signing key or close their doors.
> Blocking the freedom of the users on such way should not be accepted by
> anyone.

User banned
Comment 4 Martin Peres 2019-12-04 09:31:29 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/372.

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.