Comments (11)
If you are still facing issues try this : http://www.ddcutil.com/nvidia/
This worked for me.
from ddcutil.
from ddcutil.
Thank you. Will do and reply back, but within 1-2 weeks.
Currently everything works with latest nvidia drivers, and HDMI cable. (So my best guess that problem was in bad nvidia update plus the whole system not working with displayport for some reason, because I remember I switched to displayport, and only then started to try different drivers.)
So what I am going to try is to switch back to displayport, and provide the log in case it stops working again.
(I presume brightness control (DDC communication?) should work regardless of cable I connect monitor with.)
from ddcutil.
from ddcutil.
(i2c-tools package installed)
just in case, I attach output of "ddcutil environment --verbose" for the current setup (HDMI cable, nvidia-387, where currently everything is working fine)
sudo ddcutil environment --verbose
Output level: Verbose
Reporting DDC data errors: false
Trace groups active: none
Force I2C slave address: false
The following tests probe the runtime environment using multiple overlapping methods.
*** Basic System Information ***
ddcutil version: 0.8.4
/proc/version:
Linux version 4.4.0-96-generic (buildd@lgw01-10) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017
/etc/os-release...
PRETTY_NAME="Ubuntu 16.04.3 LTS"
/proc/cmdline:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=UUID=890c5053-2fab-497d-b889-c60e496b7562 ro quiet splash vt.handoff=7
Processor information as reported by lscpu:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 26
Model name: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
Stepping: 5
CPU MHz: 1862.000
CPU max MHz: 2793,0000
CPU min MHz: 1596,0000
BogoMIPS: 5397.20
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 8192K
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm ida
DMI Information from /sys/class/dmi/id:
Motherboard vendor: Gigabyte Technology Co., Ltd.
Motherboard product name: EX58-UD5
System vendor: Gigabyte Technology Co., Ltd.
System product name: EX58-UD5
Chassis vendor: Gigabyte Technology Co., Ltd.
Chassis type: 3 - Desktop
*** Primary Check 1: Identify video card and driver ***
Obtaining card and driver information from /sys...
Determining driver name and possibly version...
Driver name: nvidia
Driver version: 387.12
Video card identification:
Vendor: 10de NVIDIA Corporation
Device: 1d01 unknown device
*** Primary Check 2: Check that /dev/i2c-* exist and writable ***
(identify_i2c_devices) Identified 2 I2C devices
Checking /dev/i2c-* devices...
Unless the system is using the AMD proprietary driver fglrx, devices /dev/i2c-*
must exist and the logged on user must have read/write permission for those
devices (or at least those devices associated with monitors).
Typically, this access is enabled by:
- setting the group for /dev/i2c-* to i2c
- setting group RW permissions for /dev/i2c-*
- making the current user a member of group i2c
Alternatively, this could be enabled by just giving everyone RW permission
The following tests probe for these conditions.
Checking for /dev/i2c-* devices...
crw------- 1 root root 89, 0 окт 4 02:12 /dev/i2c-0
crw------- 1 root root 89, 1 окт 4 02:12 /dev/i2c-1
Current user: root (0)
Current user (root) has RW access to all /dev/i2c-* devices.
Checking for group i2c...
Group i2c exists
WARNING: Current user root is NOT a member of group i2c
Looking for udev nodes files that reference i2c:
grep: /etc/udev/makedev.d/*: No such file or directory
Looking for udev rules files that reference i2c:
/lib/udev/rules.d/40-i2c-tools.rules:KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
grep: /run/udev/rules.d/*rules: No such file or directory
*** Primary Check 3: Check that module i2c_dev is loaded ***
Checking for module i2c_dev...
Using only proprietary nvidia or fglrx driver. Module i2c_dev not required.
Remaining i2c_dev detail is purely informational.
Module i2c_dev is built into kernel
Check that kernel module i2c_dev is being loaded by examining files where this would be specified...
grep: /run/modules-load.d/*conf: No such file or directory
grep: /usr/lib/modules-load.d/*conf: No such file or directory
Check for any references to i2c_dev in /etc/modprobe.d ...
grep: /run/modprobe.d/*conf: No such file or directory
*** Primary Check 4: Driver specific checks ***
Performing driver specific checks...
Checking for special settings for proprietary Nvidia driver
(needed for some newer Nvidia cards).
grep: /etc/X11/xorg.conf: No such file or directory
grep: /etc/X11/xorg.conf.d/*: No such file or directory
*** Additional probes ***
Scanning /proc/modules for driver environment...
Found other loaded module: videobuf2_vmalloc
Found other loaded module: videobuf2_memops
Found other loaded module: videobuf2_v4l2
Found other loaded module: videobuf2_core
Found other loaded module: videodev
Found video driver module: nvidia
Found other loaded module: drm_kms_helper
Loaded drm module depends on: nvidia_drm,drm_kms_helper,
Using lspci to examine driver environment...
Video controller: NVIDIA Corporation Device 1d01 (rev a1)
Testing if modules are loaded using /sys...
Module amdgpu is NOT loaded
Module fglrx is NOT loaded
Module i915 is NOT loaded
Module nvidia is loaded
Module nouveau is NOT loaded
Module radeon is NOT loaded
Module vboxvideo is NOT loaded
Module drm is loaded
Module eeprom is NOT loaded
Module i2c_algo_bit is NOT loaded
Module i2c_dev is NOT loaded
Module i2c_piix4 is NOT loaded
Examining /sys/bus/i2c/devices...
/sys/bus/i2c/devices/i2c-0/name: NVIDIA i2c adapter 4 at 4:00.0
/sys/bus/i2c/devices/i2c-1/name: NVIDIA i2c adapter 5 at 4:00.0
Examining /proc/driver/nvidia:
/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 387.12 Thu Sep 28 20:18:48 PDT 2017
GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
/proc/driver/nvidia/registry:
Binary: ""
/proc/driver/nvidia/params:
Mobile: 4294967295
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
UpdateMemoryTypes: 4294967295
InitializeSystemMemoryAllocations: 1
UsePageAttributeTable: 4294967295
EnableMSI: 1
MapRegistersEarly: 0
RegisterForACPIEvents: 1
CheckPCIConfigSpace: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
TCEBypassMode: 0
UseThreadedInterrupts: 1
EnableStreamMemOPs: 0
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
AssignGpus: ""
PCI bus id: 0000:04:00.0
/proc/driver/nvidia/gpus/0000:04:00.0/information:
Model: GeForce GT 1030
IRQ: 30
GPU UUID: GPU-eec473f3-aebd-0018-64ff-fb37f9d2fc9f
Video BIOS: 86.08.0c.00.0b
Bus Type: PCIe
DMA Size: 47 bits
DMA Mask: 0x7fffffffffff
Bus Location: 0000:04:00.0
Device Minor: 0
/proc/driver/nvidia/gpus/0000:04:00.0/registry:
Binary: ""
Examining I2C buses, as detected by I2C layer...
Detected I2C buses:
Bus /dev/i2c-0 found: true
Bus /dev/i2c-0 probed: true
Address 0x30 present: false
Address 0x37 present: false
Address 0x50 present: false
Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_QUICK, I2C_FUNC_SMBUS_READ_BYTE,
I2C_FUNC_SMBUS_WRITE_BYTE, I2C_FUNC_SMBUS_READ_BYTE_DATA,
I2C_FUNC_SMBUS_WRITE_BYTE_DATA, I2C_FUNC_SMBUS_READ_WORD_DATA,
I2C_FUNC_SMBUS_WRITE_WORD_DATA, I2C_FUNC_SMBUS_READ_BLOCK_DATA,
I2C_FUNC_SMBUS_WRITE_BLOCK_DATA
Bus /dev/i2c-1 found: true
Bus /dev/i2c-1 probed: true
Address 0x30 present: false
Address 0x37 present: true
Address 0x50 present: true
Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_QUICK, I2C_FUNC_SMBUS_READ_BYTE,
I2C_FUNC_SMBUS_WRITE_BYTE, I2C_FUNC_SMBUS_READ_BYTE_DATA,
I2C_FUNC_SMBUS_WRITE_BYTE_DATA, I2C_FUNC_SMBUS_READ_WORD_DATA,
I2C_FUNC_SMBUS_WRITE_WORD_DATA, I2C_FUNC_SMBUS_READ_BLOCK_DATA,
I2C_FUNC_SMBUS_WRITE_BLOCK_DATA
EDID synopsis:
Mfg id: PHL
Model: PHL BDM4037U
Serial number: Unspecified
Manufacture year: 2017
EDID version: 1.3
Product code: 0xc142 (49474)
Extra descriptor: Unspecified
Video input definition: 0x80 - Digital Input
White x,y: 0.312, 0.329
Red x,y: 0.676, 0.313
Green x,y: 0.278, 0.653
Blue x,y: 0.149, 0.073
Extension blocks: 1
EDID source:
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 41 0c 42 c1 61 11 00 00 ........A.B.a...
+0010 17 1b 01 03 80 59 32 78 2a 15 71 ad 50 47 a7 26 .....Y2x*.q.PG.&
+0020 12 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40 .PT............@
+0030 81 c0 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20 ......M....p>.0
+0040 35 00 75 f2 31 00 00 1a a3 66 00 a0 f0 70 1f 80 5.u.1....f...p..
+0050 30 20 35 00 75 f2 31 00 00 1a 00 00 00 fd 00 17 0 5.u.1.........
+0060 50 1e a0 3c 00 0a 20 20 20 20 20 20 00 00 00 fc P..<.. ....
+0070 00 50 48 4c 20 42 44 4d 34 30 33 37 55 0a 01 6c .PHL BDM4037U..l
xrandr connection report:
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 885mm x 498mm
Checking for possibly conflicting programs...
Examining I2C buses using i2cdetect...
Probing bus /dev/i2c-0 using command "i2cdetect -y 0"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-1 using command "i2cdetect -y 1"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- --
50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Performing basic scan of I2C devices using local sysenv functions...
Examining device /dev/i2c-0...
Device name (/sys/bus/i2c/devices/i2c-0/name): NVIDIA i2c adapter 4 at 4:00.0
Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_QUICK, I2C_FUNC_SMBUS_READ_BYTE,
I2C_FUNC_SMBUS_WRITE_BYTE, I2C_FUNC_SMBUS_READ_BYTE_DATA,
I2C_FUNC_SMBUS_WRITE_BYTE_DATA, I2C_FUNC_SMBUS_READ_WORD_DATA,
I2C_FUNC_SMBUS_WRITE_WORD_DATA, I2C_FUNC_SMBUS_READ_BLOCK_DATA,
I2C_FUNC_SMBUS_WRITE_BLOCK_DATA
Unable to read EDID, psc=EIO(-5): Input/output error
Trying simple VCP read of feature 0x10...
Attempt 1 to read feature returned hard error: EIO(-5): Input/output error
DDC communication failed.
Examining device /dev/i2c-1...
Device name (/sys/bus/i2c/devices/i2c-1/name): NVIDIA i2c adapter 5 at 4:00.0
Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_QUICK, I2C_FUNC_SMBUS_READ_BYTE,
I2C_FUNC_SMBUS_WRITE_BYTE, I2C_FUNC_SMBUS_READ_BYTE_DATA,
I2C_FUNC_SMBUS_WRITE_BYTE_DATA, I2C_FUNC_SMBUS_READ_WORD_DATA,
I2C_FUNC_SMBUS_WRITE_WORD_DATA, I2C_FUNC_SMBUS_READ_BLOCK_DATA,
I2C_FUNC_SMBUS_WRITE_BLOCK_DATA
Raw EDID:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 41 0c 42 c1 61 11 00 00 ........A.B.a...
+0010 17 1b 01 03 80 59 32 78 2a 15 71 ad 50 47 a7 26 .....Y2x*.q.PG.&
+0020 12 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40 .PT............@
+0030 81 c0 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20 ......M....p>.0
+0040 35 00 75 f2 31 00 00 1a a3 66 00 a0 f0 70 1f 80 5.u.1....f...p..
+0050 30 20 35 00 75 f2 31 00 00 1a 00 00 00 fd 00 17 0 5.u.1.........
+0060 50 1e a0 3c 00 0a 20 20 20 20 20 20 00 00 00 fc P..<.. ....
+0070 00 50 48 4c 20 42 44 4d 34 30 33 37 55 0a 01 6c .PHL BDM4037U..l
EDID synopsis:
Mfg id: PHL
Model: PHL BDM4037U
Serial number: Unspecified
Manufacture year: 2017
EDID version: 1.3
Product code: 0xc142 (49474)
Extra descriptor: Unspecified
Video input definition: 0x80 - Digital Input
White x,y: 0.312, 0.329
Red x,y: 0.676, 0.313
Green x,y: 0.278, 0.653
Blue x,y: 0.149, 0.073
Extension blocks: 1
EDID source:
Trying simple VCP read of feature 0x10...
read() returned 6e 88 02 00 10 00 00 64 00 00 c0
Attempt 1 to read feature succeeded.
DDC communication succeeded
EDIDs reported by X11 for connected xrandr outputs:
xrandr output: HDMI-0
Raw EDID:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 41 0c 42 c1 61 11 00 00 ........A.B.a...
+0010 17 1b 01 03 80 59 32 78 2a 15 71 ad 50 47 a7 26 .....Y2x*.q.PG.&
+0020 12 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40 .PT............@
+0030 81 c0 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20 ......M....p>.0
+0040 35 00 75 f2 31 00 00 1a a3 66 00 a0 f0 70 1f 80 5.u.1....f...p..
+0050 30 20 35 00 75 f2 31 00 00 1a 00 00 00 fd 00 17 0 5.u.1.........
+0060 50 1e a0 3c 00 0a 20 20 20 20 20 20 00 00 00 fc P..<.. ....
+0070 00 50 48 4c 20 42 44 4d 34 30 33 37 55 0a 01 6c .PHL BDM4037U..l
EDID synopsis:
Mfg id: PHL
Model: PHL BDM4037U
Serial number: Unspecified
Manufacture year: 2017
EDID version: 1.3
Product code: 0xc142 (49474)
Extra descriptor: Unspecified
Video input definition: 0x80 - Digital Input
White x,y: 0.312, 0.329
Red x,y: 0.676, 0.313
Green x,y: 0.278, 0.653
Blue x,y: 0.149, 0.073
Extension blocks: 1
EDID source:
Probing I2C devices using udev, susbsystem i2c-dev...
***One Device ***
path: /sys/devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-0/i2c-dev/i2c-0
Device Node Path: /dev/i2c-0
struct udev_device at: 0x564ab547d5b0
devpath: /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-0/i2c-dev/i2c-0
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-0/i2c-dev/i2c-0
sysname: i2c-0
sysnum: 0
devnode: /dev/i2c-0
Properties:
DEVNAME -> /dev/i2c-0
DEVPATH -> /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-0/i2c-dev/i2c-0
MAJOR -> 89
MINOR -> 0
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:0
device -> (null)
name -> NVIDIA i2c adapter 4 at 4:00.0
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=0
DEVNAME=i2c-0
***One Device ***
path: /sys/devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-1/i2c-dev/i2c-1
Device Node Path: /dev/i2c-1
struct udev_device at: 0x564ab547bd70
devpath: /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-1/i2c-dev/i2c-1
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-1/i2c-dev/i2c-1
sysname: i2c-1
sysnum: 1
devnode: /dev/i2c-1
Properties:
DEVNAME -> /dev/i2c-1
DEVPATH -> /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-1/i2c-dev/i2c-1
MAJOR -> 89
MINOR -> 1
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:1
device -> (null)
name -> NVIDIA i2c adapter 5 at 4:00.0
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=1
DEVNAME=i2c-1
Summary of udev I2C devices
Subsystem Sysname Sysattr Name Devpath
i2c-dev i2c-0 NVIDIA i2c adapter 4 at 4:00.0 /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-0/i2c-dev/i2c-0
i2c-dev i2c-1 NVIDIA i2c adapter 5 at 4:00.0 /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-1/i2c-dev/i2c-1
Looking for udev devices with name attribute DPMST...
Summary of udev DPMST devices...
No devices detected
Examining system logs...
Checking dmesg for video and I2C related lines...
Checking journalctl for video and I2C related lines...
Limiting output to 200 lines...
Checking Xorg.0.log for video and I2C related lines...
[ 6.145] X.Org Video Driver: 20.0
[ 6.146] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6.273] (II) Module glx: vendor="NVIDIA Corporation"
[ 6.273] (II) NVIDIA GLX Module 387.12 Thu Sep 28 19:24:49 PDT 2017
[ 6.273] (II) LoadModule: "nvidia"
[ 6.273] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
[ 6.285] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 6.285] Module class: X.Org Video Driver
[ 6.286] (II) NVIDIA dlloader X Driver 387.12 Thu Sep 28 18:57:27 PDT 2017
[ 6.286] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 6.295] (II) NVIDIA(0): Creating default Display subsection in Screen section
[ 6.295] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 6.295] (==) NVIDIA(0): RGB weight 888
[ 6.295] (==) NVIDIA(0): Default visual is TrueColor
[ 6.295] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 6.297] (**) NVIDIA(0): Option "RegistryDwords" "RMUseSwI2c=0x01; RMI2cSpeed=100"
[ 6.297] (**) NVIDIA(0): Enabling 2D acceleration
[ 6.957] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:4:0:0
[ 6.957] (--) NVIDIA(0): DFP-0
[ 6.957] (--) NVIDIA(0): DFP-1
[ 6.957] (--) NVIDIA(0): DFP-2 (boot)
[ 6.959] (II) NVIDIA(0): NVIDIA GPU GeForce GT 1030 (GP108-A) at PCI:4:0:0 (GPU-0)
[ 6.959] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 6.959] (--) NVIDIA(0): VideoBIOS: 86.08.0c.00.0b
[ 6.959] (II) NVIDIA(0): Detected PCI Express Link width: 4X
[ 6.959] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 6.959] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 6.959] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[ 6.959] (--) NVIDIA(GPU-0):
[ 6.959] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 6.959] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 6.959] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 6.959] (--) NVIDIA(GPU-0):
[ 7.006] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 7.006] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 7.006] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 7.006] (--) NVIDIA(GPU-0):
[ 7.010] (==) NVIDIA(0):
[ 7.010] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 7.010] (==) NVIDIA(0): will be used as the requested mode.
[ 7.010] (==) NVIDIA(0):
[ 7.011] (II) NVIDIA(0): Validated MetaModes:
[ 7.011] (II) NVIDIA(0): "DFP-2:nvidia-auto-select"
[ 7.011] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160
[ 7.025] (--) NVIDIA(0): DPI set to (109, 109); computed from "UseEdidDpi" X config
[ 7.025] (--) NVIDIA(0): option
[ 7.026] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[ 7.026] (II) NVIDIA: access.
[ 7.055] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
[ 7.107] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 7.107] (==) NVIDIA(0): Backing store enabled
[ 7.107] (==) NVIDIA(0): Silken mouse enabled
[ 7.109] (==) NVIDIA(0): DPMS enabled
[ 7.109] (II) NVIDIA(0): [DRI2] Setup complete
[ 7.109] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 7.171] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[ 7.172] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 11.258] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 11.258] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 11.258] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[ 11.258] (--) NVIDIA(GPU-0):
[ 11.258] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 11.258] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 11.258] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 11.258] (--) NVIDIA(GPU-0):
[ 11.310] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 11.310] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 11.310] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 11.310] (--) NVIDIA(GPU-0):
[ 11.700] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 11.700] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 11.700] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[ 11.700] (--) NVIDIA(GPU-0):
[ 11.701] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 11.701] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 11.701] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 11.701] (--) NVIDIA(GPU-0):
[ 11.752] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 11.752] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 11.752] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 11.752] (--) NVIDIA(GPU-0):
[ 17.481] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 17.481] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 17.481] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[ 17.481] (--) NVIDIA(GPU-0):
[ 17.481] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 17.481] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 17.481] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 17.481] (--) NVIDIA(GPU-0):
[ 17.535] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 17.535] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 17.535] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 17.535] (--) NVIDIA(GPU-0):
[ 1030.813] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 1030.813] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 1030.813] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 1030.813] (--) NVIDIA(GPU-0):
[ 1030.861] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 1030.861] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 1030.861] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 1030.861] (--) NVIDIA(GPU-0):
[ 82975.784] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 82975.784] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 82975.784] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 82975.784] (--) NVIDIA(GPU-0):
[ 82975.832] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[ 82975.832] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[ 82975.832] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[ 82975.832] (--) NVIDIA(GPU-0):
[120238.937] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[120238.939] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[120238.939] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[120238.939] (--) NVIDIA(GPU-0):
[120238.986] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[120238.986] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[120238.986] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[120238.986] (--) NVIDIA(GPU-0):
[120338.911] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[120338.911] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[120338.911] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[120338.911] (--) NVIDIA(GPU-0):
[120338.959] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[120338.959] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[120338.959] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[120338.959] (--) NVIDIA(GPU-0):
[167647.192] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[167647.192] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[167647.192] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[167647.192] (--) NVIDIA(GPU-0):
[167647.240] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[167647.240] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[167647.240] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[167647.240] (--) NVIDIA(GPU-0):
[208782.137] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[208782.137] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[208782.138] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[208782.138] (--) NVIDIA(GPU-0):
[208782.189] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[208782.189] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[208782.189] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[208782.189] (--) NVIDIA(GPU-0):
[209959.353] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[209959.353] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[209959.353] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[209959.353] (--) NVIDIA(GPU-0):
[209959.405] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[209959.405] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[209959.405] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[209959.405] (--) NVIDIA(GPU-0):
[213359.908] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[213359.908] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[213359.908] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[213359.908] (--) NVIDIA(GPU-0):
[213359.959] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[213359.959] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[213359.959] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[213359.959] (--) NVIDIA(GPU-0):
[217797.874] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[217797.874] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[217797.874] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[217797.874] (--) NVIDIA(GPU-0):
[217797.957] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[217797.957] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[217797.957] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[217797.957] (--) NVIDIA(GPU-0):
[218324.766] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[218324.766] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[218324.766] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[218324.766] (--) NVIDIA(GPU-0):
[218324.818] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[218324.818] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[218324.818] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[218324.818] (--) NVIDIA(GPU-0):
[219924.631] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[219924.631] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[219924.631] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[219924.631] (--) NVIDIA(GPU-0):
[219924.682] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[219924.682] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[219924.682] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[219924.682] (--) NVIDIA(GPU-0):
[223624.903] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[223624.903] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[223624.903] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[223624.903] (--) NVIDIA(GPU-0):
[223624.955] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[223624.955] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[223624.955] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[223624.955] (--) NVIDIA(GPU-0):
[223770.351] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[223770.351] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[223770.351] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[223770.351] (--) NVIDIA(GPU-0):
[223770.402] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[223770.402] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[223770.402] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
[223770.402] (--) NVIDIA(GPU-0):
[238067.162] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): connected
[238067.162] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): Internal TMDS
[238067.162] (--) NVIDIA(GPU-0): Philips PHL BDM4037U (DFP-2): 600.0 MHz maximum pixel clock
Not built with libdrm support. Skipping DRM related checks
Device Identifier Cross Reference Report
EDID: ...550A016C Mfg: PHL Model: PHL BDM4037U SN: Unspecified
Bus: /dev/i2c-1
XrandR output: HDMI-0
DRM connector: (null)
UDEV name: NVIDIA i2c adapter 5 at 4:00.0
UDEV syspath: /devices/pci0000:00/0000:00:07.0/0000:04:00.0/i2c-1/i2c-dev/i2c-1
from ddcutil.
❯ sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- --
50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
~ 10s
❯ sudo i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
from ddcutil.
(Will attach same output of all the commands when I switch back to displayport and thus probably reproduce the issue.)
from ddcutil.
ok, I restarted computer today since then, and the issue came back.
I copied a file to /etc/udev/rules.d, one binary to read usb light sensor to /usr/sbin and a systemd service wrapper, then restarted system again - and ddcutil was still working fine.
I did one more (third) restart, doing nothing other than opening the browser - now it says again Failure getting EDID for /dev/i2c-1: status code=DDCRC_EDID(-3016): invalid EDID
output of sudo i2cdetect 1
and sudo i2cdetect
is the very same as in the comment above - 1 month ago (did diff comparison with vim)
@rockowitz, can you please offer an advice in further debugging?
From a blackbox point of view, I can only guess that my system has something non-deterministic in the load order such that sometimes ddcutil works, and sometimes doesn't - because copying files and running this tiny systemd service (and also deleting /dev/floppy0 from my /etc/fstab) was literally the only change between these three restarts, and there was no changes other than running google chrome between second restart (ddcutil worked with no errors) and the third one (ddcutil gives an error).
from ddcutil.
edit: actually, I do not see I have posted original error message of ddcutil in this ticket, which is not good, so I cannot compare current error message of ddcutil to something above.
Redoing steps from man on nvidia drivers now, and modprobe commands from above, because it looks like #30 and not like something that was in this ticket. Sorry for confusion
from ddcutil.
I just did one more restart, doing no changes whatsoever, and it works again. The workaround for nvidia in xorg.conf.d was there all the time, of course.
So it's something to do with the load order or something else. (Something something dark side.)
from ddcutil.
from ddcutil.
Related Issues (20)
- Ubuntu 24.04 LTS prebuild package HOT 2
- Unable to set input source on Gigabyte M27Q HOT 2
- Failed assertion in check_video_adapters_list_implements_drm HOT 1
- Small suggestion for ddcutil documentation on the website HOT 1
- Dell UltraSharp 2209WAf: DDC communication failed HOT 8
- Ubuntu and Debian packages in OBS are missing libddcutil.so.x.x.x HOT 2
- Enhancement - consider packaging module loading HOT 2
- "Keeping adjust sleep multiplier" warning shown many times HOT 1
- Monitor resets many times on boot after new udev rule installed HOT 26
- System cannot enter S0ix sleep after running ddcutil detect HOT 7
- No (DisplayLink) displays found on 2.1.4, but works on 2.0.0 HOT 6
- ddcutil 2.1.4-1: DDC communication failed HOT 3
- [debian] updating linux-image pkg fails due to ddcutil dkms module failure HOT 2
- Cannot get capabilities: Maximum DDC retries exceeded. HOT 8
- Add an option to return the capabilities for a specific feature. HOT 4
- DDC communication failed (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(15)]) HOT 1
- Ddcutil crashes when some usb devices are connected HOT 1
- `ddcutil` ignores the final entry in `XDG_DATA_DIRS` when looking for an `mccs` file HOT 1
- Cannot update beyond 1.2.2-1 HOT 2
- Samsung C24F390 - DDC communication failed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ddcutil.