Closed thmcmahon closed 7 years ago
Thomas,
Your report is very useful. I've been working on trying to better handle the corner case where the pseudo-I2C bus for the laptop's display claims to support DDC when it fact it doesn't.
Please run the following command and send me the output. ddcutil environment --verbose
Are you installing ddcutil from git, the tarball, or one of the rpms or dpkgs? I ask because it might be helpful if you could install a development version of ddcutil.
Thanks, Sanford
On 01/12/2017 12:23 AM, Thomas McMahon wrote:
Hi
I built ddcutil 0.7.0 on Ubuntu 16.10. I have two external displays connected to my Lenovo x260 via a Lenovo Ultra Dock. The displays are Dell U2412Ms.
Here is the output of |ddcutil detect|:
|sudo ddcutil detect Display 1 I2C bus: /dev/i2c-3 Supports DDC: true EDID synopsis: Mfg id: AUO Model: Unspecified Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 VCP version: Detection failed Invalid display I2C bus: /dev/i2c-5 Supports DDC: false EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Display 2 I2C bus: /dev/i2c-6 Supports DDC: true (ddc_open_display) No EDID for device on bus /dev/i2c-6 Error opening display bus /dev/i2c-6, error = -3016 (DDCRC_EDID) (ddc_close_display) close_i2c_bus returned 9 Display 3 I2C bus: /dev/i2c-7 Supports DDC: true (ddc_open_display) No EDID for device on bus /dev/i2c-7 Error opening display bus /dev/i2c-7, error = -3016 (DDCRC_EDID) (ddc_close_display) close_i2c_bus returned 9 |
However when I try and detect monitor capabilities it doesn't work:
|tom@x260:~$ sudo ddcutil capabilities --display 1 Unable to get capabilities for monitor on Display_Handle[i2c: fh=3, busno=3]. Maximum DDC retries exceeded. |
This seems like it may be related to issue number 8 https://github.com/rockowitz/ddcutil/issues/8 - I'm not really all that stressed about not getting this to work, but thought this might be helpful.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbjIoBIVth0RdLJqH19OpfkB_UVYvks5rRbjJgaJpZM4LhYdj.
Sanford
I installed it from the tarball on the website. Happy to try a dev version if that would help.
Here's the output of sudo ddcutil environment --verbose
Output level: Verbose
Reporting DDC data errors: false
Trace groups active: none
The following tests probe the runtime environment using multiple overlapping methods.
System information (uname):
Linux version 4.8.0-32-generic (buildd@lcy01-34) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016
*** Primary Check 1: Identify video card and driver ***
Obtaining card and driver information from /sys...
Determining driver name and possibly version...
Driver name: i915
Unable to determine driver version
Video card identification:
Vendor: 8086 Intel Corporation
Device: 1916 HD Graphics 520
Subvendor/Subdevice: 17aa/504a Lenovo
*** Primary Check 2: Check that /dev/i2c-* exist and writable ***
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-rw---- 1 root i2c 89, 0 Jan 12 15:44 /dev/i2c-0
crw-rw---- 1 root i2c 89, 1 Jan 12 15:44 /dev/i2c-1
crw-rw---- 1 root i2c 89, 2 Jan 12 15:44 /dev/i2c-2
crw-rw---- 1 root i2c 89, 3 Jan 12 15:44 /dev/i2c-3
crw-rw---- 1 root i2c 89, 4 Jan 12 15:44 /dev/i2c-4
crw-rw---- 1 root i2c 89, 5 Jan 12 15:44 /dev/i2c-5
crw-rw---- 1 root i2c 89, 6 Jan 12 15:44 /dev/i2c-6
crw-rw---- 1 root i2c 89, 7 Jan 12 15:44 /dev/i2c-7
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
grep: /etc/udev/rules.d/*rules: No such file or directory
*** Primary Check 3: Check that module i2c_dev is loaded ***
Checking for module i2c_dev...
Module i2c_dev is built into kernel
Remaining i2c_dev detail is purely informational.
Check that kernel module i2c_dev is being loaded by examining files where this would be specified...
/etc/modules:i2c-dev
/etc/modules-load.d/modules.conf:i2c-dev
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...
No driver specific checks apply.
*** Primary Check 5: Installed packages ***
ddcutil requiries package i2c-tools. Use both dpkg and rpm to look for it.
While we're at it, check for package libi2c-dev which is used for building
ddcutil.
Using dpkg to look for package i2c-tools...
Package: i2c-tools
Status: install ok installed
Priority: extra
Section: utils
Installed-Size: 244
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 3.1.1-1
Depends: libc6 (>= 2.7), perl, adduser, udev | makedev
Recommends: read-edid
Suggests: libi2c-dev, python-smbus
Conflicts: lm-sensors (<< 1:3.0.0-1)
Description: heterogeneous set of I2C tools for Linux
This package contains a heterogeneous set of I2C tools for Linux: a bus
probing tool, a chip dumper, register-level access helpers, EEPROM
decoding scripts, and more.
Original-Maintainer: Aurelien Jarno <aurel32@debian.org>
Homepage: http://www.lm-sensors.org
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/i2c-tools
/usr/share/doc/i2c-tools/changelog.Debian.gz
/usr/share/doc/i2c-tools/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/decode-vaio.1.gz
/usr/share/man/man1/decode-dimms.1.gz
/usr/share/man/man8
/usr/share/man/man8/i2cset.8.gz
/usr/share/man/man8/i2cget.8.gz
/usr/share/man/man8/i2cdump.8.gz
/usr/share/man/man8/i2c-stub-from-dump.8.gz
/usr/share/man/man8/i2cdetect.8.gz
/usr/sbin
/usr/sbin/i2cset
/usr/sbin/i2cget
/usr/sbin/i2cdump
/usr/sbin/i2c-stub-from-dump
/usr/sbin/i2cdetect
/usr/bin
/usr/bin/ddcmon
/usr/bin/decode-edid
/usr/bin/decode-vaio
/usr/bin/decode-dimms
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/40-i2c-tools.rules
Using dpkg to look for package libi2c-dev...
dpkg-query: package 'libi2c-dev' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
dpkg-query: package 'libi2c-dev' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
Using rpm to look for package i2c-tools...
rpm command not found
*** 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: i915
Found other loaded module: i2c_algo_bit
Loaded drm module depends on: i915,drm_kms_helper,
Loaded video module depends on: thinkpad_acpi,i915,
Using lspci to examine driver environment...
Video controller: Intel Corporation HD Graphics 520 (rev 07)
Testing if modules are loaded using /sys...
Module amdgpu is NOT loaded
Module fglrx is NOT loaded
Module i915 is loaded
Module nvidia is NOT loaded
Module nouveau is NOT loaded
Module radeon is NOT loaded
Module vboxvideo is NOT loaded
Module i2c_dev is NOT loaded
Module i2c_algo_bit is loaded
Module i2c_piix4 is NOT loaded
Examining /sys/bus/i2c/devices...
/sys/bus/i2c/devices/i2c-3/name: DPDDC-A
/sys/bus/i2c/devices/i2c-1/name: i915 gmbus dpb
/sys/bus/i2c/devices/i2c-6/name: DPMST
/sys/bus/i2c/devices/i2c-4/name: DPDDC-B
/sys/bus/i2c/devices/i2c-2/name: i915 gmbus dpd
/sys/bus/i2c/devices/i2c-0/name: i915 gmbus dpc
/sys/bus/i2c/devices/i2c-7/name: DPMST
/sys/bus/i2c/devices/i2c-5/name: DPDDC-C
Examining i2c buses...
Detected I2C buses:
Bus /dev/i2c-0 found: true
Bus /dev/i2c-0 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-1 found: true
Bus /dev/i2c-1 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-2 found: true
Bus /dev/i2c-2 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-3 found: true
Bus /dev/i2c-3 probed: true
Address 0x37 present: true
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
EDID synopsis:
Mfg id: AUO
Model: Unspecified
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
Product code: 0x226d (8813)
Extra descriptor: B125HAN02.2
White x,y: 0.306, 0.327
Red x,y: 0.587, 0.350
Green x,y: 0.342, 0.585
Blue x,y: 0.154, 0.115
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 06 af 6d 22 00 00 00 00 ..........m"....
+0010 34 19 01 04 a5 1c 10 78 02 6b a7 96 59 57 95 27 4......x.k..YW.'
+0020 1d 4e 53 00 00 00 01 01 01 01 01 01 01 01 01 01 .NS.............
+0030 01 01 01 01 01 01 14 37 80 b8 70 38 24 40 10 10 .......7..p8$@..
+0040 3e 00 14 9b 10 00 00 18 00 00 00 0f 00 00 00 00 >...............
+0050 00 00 00 00 00 00 00 00 00 20 00 00 00 fe 00 41 ......... .....A
+0060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe UO. ....
+0070 00 42 31 32 35 48 41 4e 30 32 2e 32 20 0a 00 a8 .B125HAN02.2 ...
Bus /dev/i2c-4 found: true
Bus /dev/i2c-4 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-5 found: true
Bus /dev/i2c-5 probed: true
Address 0x37 present: false
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
Product code: 0xa07b (41083)
Extra descriptor: Unspecified
White x,y: 0.313, 0.329
Red x,y: 0.640, 0.330
Green x,y: 0.300, 0.600
Blue x,y: 0.150, 0.060
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 10 ac 7b a0 4c 56 4b 30 ..........{.LVK0
+0010 35 19 01 04 a5 34 20 78 2a ee 95 a3 54 4c 99 26 5....4 x*...TL.&
+0020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 .PT....@...@....
+0030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0
+0040 36 00 06 44 21 00 00 1a c8 73 00 a0 f0 b0 23 40 6..D!....s....#@
+0050 30 20 36 00 ff ff 00 00 00 1e 00 00 00 fc 00 44 0 6............D
+0060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 27 4a 00 98 ELL U2412M. 'J..
+0070 a1 00 2a 40 30 70 13 00 ff ff 00 00 00 1e 00 07 ..*@0p..........
Bus /dev/i2c-6 found: true
Bus /dev/i2c-6 probed: true
Address 0x37 present: true
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-7 found: true
Bus /dev/i2c-7 probed: true
Address 0x37 present: true
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
xrandr connection report:
eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 280mm x 160mm
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP2-1 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 520mm x 320mm
DP2-2 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 520mm x 320mm
DP2-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-2 using command "i2cdetect -y 2"
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-3 using command "i2cdetect -y 3"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-4 using command "i2cdetect -y 4"
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-5 using command "i2cdetect -y 5"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-6 using command "i2cdetect -y 6"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-7 using command "i2cdetect -y 7"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
EDIDs reported by X11 for connected xrandr outputs:
xrandr output: eDP1
EDID synopsis:
Mfg id: AUO
Model: Unspecified
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
xrandr output: DP2-1
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: PPNN15CU0KVL
Manufacture year: 2015
EDID version: 1.4
xrandr output: DP2-2
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: 9W5YH3810DES
Manufacture year: 2013
EDID version: 1.3
Probing I2C devices using udev, susbsystem i2c-dev...
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
Device Node Path: /dev/i2c-4
struct udev_device at: 0x55b0725fdff0
devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
sysname: i2c-4
sysnum: 4
devnode: /dev/i2c-4
Properties:
DEVNAME -> /dev/i2c-4
DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
MAJOR -> 89
MINOR -> 4
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:4
device -> (null)
name -> DPDDC-B
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=4
DEVNAME=i2c-4
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
Device Node Path: /dev/i2c-5
struct udev_device at: 0x55b0725fb510
devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
sysname: i2c-5
sysnum: 5
devnode: /dev/i2c-5
Properties:
DEVNAME -> /dev/i2c-5
DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
MAJOR -> 89
MINOR -> 5
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:5
device -> (null)
name -> DPDDC-C
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=5
DEVNAME=i2c-5
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
Device Node Path: /dev/i2c-3
struct udev_device at: 0x55b0726007b0
devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
sysname: i2c-3
sysnum: 3
devnode: /dev/i2c-3
Properties:
DEVNAME -> /dev/i2c-3
DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
MAJOR -> 89
MINOR -> 3
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:3
device -> (null)
name -> DPDDC-A
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=3
DEVNAME=i2c-3
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0
Device Node Path: /dev/i2c-0
struct udev_device at: 0x55b0726014f0
devpath: /devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-0/i2c-dev/i2c-0
MAJOR -> 89
MINOR -> 0
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:0
device -> (null)
name -> i915 gmbus dpc
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=0
DEVNAME=i2c-0
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1
Device Node Path: /dev/i2c-1
struct udev_device at: 0x55b072609280
devpath: /devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-1/i2c-dev/i2c-1
MAJOR -> 89
MINOR -> 1
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:1
device -> (null)
name -> i915 gmbus dpb
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=1
DEVNAME=i2c-1
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
Device Node Path: /dev/i2c-2
struct udev_device at: 0x55b0725f6f80
devpath: /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
sysname: i2c-2
sysnum: 2
devnode: /dev/i2c-2
Properties:
DEVNAME -> /dev/i2c-2
DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
MAJOR -> 89
MINOR -> 2
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:2
device -> (null)
name -> i915 gmbus dpd
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=2
DEVNAME=i2c-2
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
Device Node Path: /dev/i2c-6
struct udev_device at: 0x55b072610e50
devpath: /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
sysname: i2c-6
sysnum: 6
devnode: /dev/i2c-6
Properties:
DEVNAME -> /dev/i2c-6
DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
MAJOR -> 89
MINOR -> 6
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:6
device -> (null)
name -> DPMST
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=6
DEVNAME=i2c-6
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
Device Node Path: /dev/i2c-7
struct udev_device at: 0x55b07261fc70
devpath: /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
sysname: i2c-7
sysnum: 7
devnode: /dev/i2c-7
Properties:
DEVNAME -> /dev/i2c-7
DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
MAJOR -> 89
MINOR -> 7
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:7
device -> (null)
name -> DPMST
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=7
DEVNAME=i2c-7
Thomas,
Well, this is seriously weird.
First off, I'm going to ask you to send me the full, gory, diagnostics, using command "sudo ddcutil interrogate". This will take a while to run.
Before I get into the weeds, a bit of background on how ddcutil (currently) detects monitors on the I2C bus. It scans each of the /dev/i2c-n devices, checking if slave addresses x50 (EDID) and x37 (DDC communication) are active. If both are, it concludes it's found a monitor.
There are 2 things happening on your system. The first is indeed
related to issue #8 https://github.com/rockowitz/ddcutil/issues/8.
The driver is reports that x37 is active on bus /dev/i2c-3, which is the
laptop display. But in fact DDC communication fails (it's a laptop
display), which is why you get the errors on "ddcutil capabilities".
The current development tree performs an additional "sanity" test of DDC
communication before concluding it's found a DDC capable monitor.
The second thing that's going on with the external monitors is truly weird. "ddcutil environment' probes the DDC environment in multiple ways. The system command i2cdetect examines I2C buses, using essentially the same algorithm as ddcutil. Like ddcutil, it finds that /dev/i2c-3, 5, 6, and 7 have both slave address active. So these would appear to be monitors. /dev/i3c-3 is the laptop display, which we know about.
On the other hand, udev combined with xrandr reports displays on i2c-3 (eDP-1), i2c-4 (DP-1) and i2c-5 (DP2). Again, i2c-3 (eDP-1) is the laptop display. So i2cdetect and udev are in disagreement, which hints at the failures you're seeing. I suspect a video driver issue. This will require some thought, and probably additional code to test your environment further.
Are the external monitors connected to the dock individually, or are you using DisplayPort chaining?
What happens if you use the DisplayPort connection on the laptop instead of the dock?
Thanks for your help.
Sanford
On 01/12/2017 06:47 PM, Thomas McMahon wrote:
Sanford
I installed it from the tarball on the website. Happy to try a dev version if that would help.
Here's the output of |sudo ddcutil environment --verbose|
|Output level: Verbose Reporting DDC data errors: false Trace groups active: none The following tests probe the runtime environment using multiple overlapping methods. System information (uname): Linux version 4.8.0-32-generic (buildd@lcy01-34) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016 Primary Check 1: Identify video card and driver Obtaining card and driver information from /sys... Determining driver name and possibly version... Driver name: i915 Unable to determine driver version Video card identification: Vendor: 8086 Intel Corporation Device: 1916 HD Graphics 520 Subvendor/Subdevice: 17aa/504a Lenovo Primary Check 2: Check that /dev/i2c- exist and writable ** 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-rw---- 1 root i2c 89, 0 Jan 12 15:44 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 Jan 12 15:44 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 Jan 12 15:44 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 Jan 12 15:44 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 Jan 12 15:44 /dev/i2c-4 crw-rw---- 1 root i2c 89, 5 Jan 12 15:44 /dev/i2c-5 crw-rw---- 1 root i2c 89, 6 Jan 12 15:44 /dev/i2c-6 crw-rw---- 1 root i2c 89, 7 Jan 12 15:44 /dev/i2c-7 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 grep: /etc/udev/rules.d/rules: No such file or directory Primary Check 3: Check that module i2c_dev is loaded Checking for module i2c_dev... Module i2c_dev is built into kernel Remaining i2c_dev detail is purely informational. Check that kernel module i2c_dev is being loaded by examining files where this would be specified... /etc/modules:i2c-dev /etc/modules-load.d/modules.conf:i2c-dev 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... No driver specific checks apply. Primary Check 5: Installed packages ddcutil requiries package i2c-tools. Use both dpkg and rpm to look for it. While we're at it, check for package libi2c-dev which is used for building ddcutil. Using dpkg to look for package i2c-tools... Package: i2c-tools Status: install ok installed Priority: extra Section: utils Installed-Size: 244 Maintainer: Ubuntu Developers ubuntu-devel-discuss@lists.ubuntu.com Architecture: amd64 Version: 3.1.1-1 Depends: libc6 (>= 2.7), perl, adduser, udev | makedev Recommends: read-edid Suggests: libi2c-dev, python-smbus Conflicts: lm-sensors (<< 1:3.0.0-1) Description: heterogeneous set of I2C tools for Linux This package contains a heterogeneous set of I2C tools for Linux: a bus probing tool, a chip dumper, register-level access helpers, EEPROM decoding scripts, and more. Original-Maintainer: Aurelien Jarno aurel32@debian.org Homepage: http://www.lm-sensors.org /. /usr /usr/share /usr/share/doc /usr/share/doc/i2c-tools /usr/share/doc/i2c-tools/changelog.Debian.gz /usr/share/doc/i2c-tools/copyright /usr/share/man /usr/share/man/man1 /usr/share/man/man1/decode-vaio.1.gz /usr/share/man/man1/decode-dimms.1.gz /usr/share/man/man8 /usr/share/man/man8/i2cset.8.gz /usr/share/man/man8/i2cget.8.gz /usr/share/man/man8/i2cdump.8.gz /usr/share/man/man8/i2c-stub-from-dump.8.gz /usr/share/man/man8/i2cdetect.8.gz /usr/sbin /usr/sbin/i2cset /usr/sbin/i2cget /usr/sbin/i2cdump /usr/sbin/i2c-stub-from-dump /usr/sbin/i2cdetect /usr/bin /usr/bin/ddcmon /usr/bin/decode-edid /usr/bin/decode-vaio /usr/bin/decode-dimms /lib /lib/udev /lib/udev/rules.d /lib/udev/rules.d/40-i2c-tools.rules Using dpkg to look for package libi2c-dev... dpkg-query: package 'libi2c-dev' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libi2c-dev' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Using rpm to look for package i2c-tools... rpm command not found 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: i915 Found other loaded module: i2c_algo_bit Loaded drm module depends on: i915,drm_kms_helper, Loaded video module depends on: thinkpad_acpi,i915, Using lspci to examine driver environment... Video controller: Intel Corporation HD Graphics 520 (rev 07) Testing if modules are loaded using /sys... Module amdgpu is NOT loaded Module fglrx is NOT loaded Module i915 is loaded Module nvidia is NOT loaded Module nouveau is NOT loaded Module radeon is NOT loaded Module vboxvideo is NOT loaded Module i2c_dev is NOT loaded Module i2c_algo_bit is loaded Module i2c_piix4 is NOT loaded Examining /sys/bus/i2c/devices... /sys/bus/i2c/devices/i2c-3/name: DPDDC-A /sys/bus/i2c/devices/i2c-1/name: i915 gmbus dpb /sys/bus/i2c/devices/i2c-6/name: DPMST /sys/bus/i2c/devices/i2c-4/name: DPDDC-B /sys/bus/i2c/devices/i2c-2/name: i915 gmbus dpd /sys/bus/i2c/devices/i2c-0/name: i915 gmbus dpc /sys/bus/i2c/devices/i2c-7/name: DPMST /sys/bus/i2c/devices/i2c-5/name: DPDDC-C Examining i2c buses... Detected I2C buses: Bus /dev/i2c-0 found: true Bus /dev/i2c-0 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-1 found: true Bus /dev/i2c-1 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-2 found: true Bus /dev/i2c-2 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-3 found: true Bus /dev/i2c-3 probed: true Address 0x37 present: true Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK EDID synopsis: Mfg id: AUO Model: Unspecified Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Product code: 0x226d (8813) Extra descriptor: B125HAN02.2 White x,y: 0.306, 0.327 Red x,y: 0.587, 0.350 Green x,y: 0.342, 0.585 Blue x,y: 0.154, 0.115 EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 06 af 6d 22 00 00 00 00 ..........m".... +0010 34 19 01 04 a5 1c 10 78 02 6b a7 96 59 57 95 27 4......x.k..YW.' +0020 1d 4e 53 00 00 00 01 01 01 01 01 01 01 01 01 01 .NS............. +0030 01 01 01 01 01 01 14 37 80 b8 70 38 24 40 10 10 .......7..p8$@.. +0040 3e 00 14 9b 10 00 00 18 00 00 00 0f 00 00 00 00
............... +0050 00 00 00 00 00 00 00 00 00 20 00 00 00 fe 00 41 ......... .....A +0060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe UO. .... +0070 00 42 31 32 35 48 41 4e 30 32 2e 32 20 0a 00 a8 .B125HAN02.2 ... Bus /dev/i2c-4 found: true Bus /dev/i2c-4 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-5 found: true Bus /dev/i2c-5 probed: true Address 0x37 present: false Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Product code: 0xa07b (41083) Extra descriptor: Unspecified White x,y: 0.313, 0.329 Red x,y: 0.640, 0.330 Green x,y: 0.300, 0.600 Blue x,y: 0.150, 0.060 EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 10 ac 7b a0 4c 56 4b 30 ..........{.LVK0 +0010 35 19 01 04 a5 34 20 78 2a ee 95 a3 54 4c 99 26 5....4 x...TL.& +0020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 .PT....@...@.... +0030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0 +0040 36 00 06 44 21 00 00 1a c8 73 00 a0 f0 b0 23 40 6..D!....s....#@ +0050 30 20 36 00 ff ff 00 00 00 1e 00 00 00 fc 00 44 0 6............D +0060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 27 4a 00 98 ELL U2412M. 'J.. +0070 a1 00 2a 40 30 70 13 00 ff ff 00 00 00 1e 00 07 ..@0p.......... Bus /dev/i2c-6 found: true Bus /dev/i2c-6 probed: true Address 0x37 present: true Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-7 found: true Bus /dev/i2c-7 probed: true Address 0x37 present: true Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK xrandr connection report: eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 280mm x 160mm DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP2-1 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 520mm x 320mm DP2-2 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 520mm x 320mm DP2-3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) 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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-2 using command "i2cdetect -y 2" 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-3 using command "i2cdetect -y 3" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-4 using command "i2cdetect -y 4" 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-5 using command "i2cdetect -y 5" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-6 using command "i2cdetect -y 6" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-7 using command "i2cdetect -y 7" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- EDIDs reported by X11 for connected xrandr outputs: xrandr output: eDP1 EDID synopsis: Mfg id: AUO Model: Unspecified Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 xrandr output: DP2-1 EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: PPNN15CU0KVL Manufacture year: 2015 EDID version: 1.4 xrandr output: DP2-2 EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: 9W5YH3810DES Manufacture year: 2013 EDID version: 1.3 Probing I2C devices using udev, susbsystem i2c-dev... One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 Device Node Path: /dev/i2c-4 struct udev_device at: 0x55b0725fdff0 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 sysname: i2c-4 sysnum: 4 devnode: /dev/i2c-4 Properties: DEVNAME -> /dev/i2c-4 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 MAJOR -> 89 MINOR -> 4 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:4 device -> (null) name -> DPDDC-B subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=4 DEVNAME=i2c-4 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 Device Node Path: /dev/i2c-5 struct udev_device at: 0x55b0725fb510 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 sysname: i2c-5 sysnum: 5 devnode: /dev/i2c-5 Properties: DEVNAME -> /dev/i2c-5 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 MAJOR -> 89 MINOR -> 5 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:5 device -> (null) name -> DPDDC-C subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=5 DEVNAME=i2c-5 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 Device Node Path: /dev/i2c-3 struct udev_device at: 0x55b0726007b0 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 sysname: i2c-3 sysnum: 3 devnode: /dev/i2c-3 Properties: DEVNAME -> /dev/i2c-3 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 MAJOR -> 89 MINOR -> 3 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:3 device -> (null) name -> DPDDC-A subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=3 DEVNAME=i2c-3 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0 Device Node Path: /dev/i2c-0 struct udev_device at: 0x55b0726014f0 devpath: /devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-0/i2c-dev/i2c-0 MAJOR -> 89 MINOR -> 0 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:0 device -> (null) name -> i915 gmbus dpc subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=0 DEVNAME=i2c-0 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 Device Node Path: /dev/i2c-1 struct udev_device at: 0x55b072609280 devpath: /devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-1/i2c-dev/i2c-1 MAJOR -> 89 MINOR -> 1 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:1 device -> (null) name -> i915 gmbus dpb subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=1 DEVNAME=i2c-1 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 Device Node Path: /dev/i2c-2 struct udev_device at: 0x55b0725f6f80 devpath: /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 sysname: i2c-2 sysnum: 2 devnode: /dev/i2c-2 Properties: DEVNAME -> /dev/i2c-2 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 MAJOR -> 89 MINOR -> 2 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:2 device -> (null) name -> i915 gmbus dpd subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=2 DEVNAME=i2c-2 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 Device Node Path: /dev/i2c-6 struct udev_device at: 0x55b072610e50 devpath: /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 sysname: i2c-6 sysnum: 6 devnode: /dev/i2c-6 Properties: DEVNAME -> /dev/i2c-6 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 MAJOR -> 89 MINOR -> 6 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:6 device -> (null) name -> DPMST subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=6 DEVNAME=i2c-6 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 Device Node Path: /dev/i2c-7 struct udev_device at: 0x55b07261fc70 devpath: /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 sysname: i2c-7 sysnum: 7 devnode: /dev/i2c-7 Properties: DEVNAME -> /dev/i2c-7 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 MAJOR -> 89 MINOR -> 7 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:7 device -> (null) name -> DPMST subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=7 DEVNAME=i2c-7 |
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-272320390, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsblg5k-x_iHwc-0ZcKBqyeEo1kWFkks5rRruWgaJpZM4LhYdj.
I'll answer the last questions first as this command dump is long.
Here's the dump of sudo ddcutil interrogate
- it segfaulted so let m eknow if you want me to run again.
Setting output level verbose...
Setting maximum retries...
Forcing --stats...
This command will take a while to run...
System information (uname):
Linux version 4.8.0-32-generic (buildd@lcy01-34) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016
*** Primary Check 1: Identify video card and driver ***
Obtaining card and driver information from /sys...
Determining driver name and possibly version...
Driver name: i915
Unable to determine driver version
Video card identification:
Vendor: 8086 Intel Corporation
Device: 1916 HD Graphics 520
Subvendor/Subdevice: 17aa/504a Lenovo
*** Primary Check 2: Check that /dev/i2c-* exist and writable ***
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-rw---- 1 root i2c 89, 0 Jan 12 15:44 /dev/i2c-0
crw-rw---- 1 root i2c 89, 1 Jan 12 15:44 /dev/i2c-1
crw-rw---- 1 root i2c 89, 2 Jan 12 15:44 /dev/i2c-2
crw-rw---- 1 root i2c 89, 3 Jan 12 15:44 /dev/i2c-3
crw-rw---- 1 root i2c 89, 4 Jan 12 15:44 /dev/i2c-4
crw-rw---- 1 root i2c 89, 5 Jan 12 15:44 /dev/i2c-5
crw-rw---- 1 root i2c 89, 6 Jan 17 11:18 /dev/i2c-6
crw-rw---- 1 root i2c 89, 7 Jan 17 11:18 /dev/i2c-7
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
grep: /etc/udev/rules.d/*rules: No such file or directory
*** Primary Check 3: Check that module i2c_dev is loaded ***
Checking for module i2c_dev...
Module i2c_dev is built into kernel
Remaining i2c_dev detail is purely informational.
Check that kernel module i2c_dev is being loaded by examining files where this would be specified...
/etc/modules:i2c-dev
/etc/modules-load.d/modules.conf:i2c-dev
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...
No driver specific checks apply.
*** Primary Check 5: Installed packages ***
ddcutil requiries package i2c-tools. Use both dpkg and rpm to look for it.
While we're at it, check for package libi2c-dev which is used for building
ddcutil.
Using dpkg to look for package i2c-tools...
Package: i2c-tools
Status: install ok installed
Priority: extra
Section: utils
Installed-Size: 244
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 3.1.1-1
Depends: libc6 (>= 2.7), perl, adduser, udev | makedev
Recommends: read-edid
Suggests: libi2c-dev, python-smbus
Conflicts: lm-sensors (<< 1:3.0.0-1)
Description: heterogeneous set of I2C tools for Linux
This package contains a heterogeneous set of I2C tools for Linux: a bus
probing tool, a chip dumper, register-level access helpers, EEPROM
decoding scripts, and more.
Original-Maintainer: Aurelien Jarno <aurel32@debian.org>
Homepage: http://www.lm-sensors.org
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/i2c-tools
/usr/share/doc/i2c-tools/changelog.Debian.gz
/usr/share/doc/i2c-tools/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/decode-vaio.1.gz
/usr/share/man/man1/decode-dimms.1.gz
/usr/share/man/man8
/usr/share/man/man8/i2cset.8.gz
/usr/share/man/man8/i2cget.8.gz
/usr/share/man/man8/i2cdump.8.gz
/usr/share/man/man8/i2c-stub-from-dump.8.gz
/usr/share/man/man8/i2cdetect.8.gz
/usr/sbin
/usr/sbin/i2cset
/usr/sbin/i2cget
/usr/sbin/i2cdump
/usr/sbin/i2c-stub-from-dump
/usr/sbin/i2cdetect
/usr/bin
/usr/bin/ddcmon
/usr/bin/decode-edid
/usr/bin/decode-vaio
/usr/bin/decode-dimms
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/40-i2c-tools.rules
Using dpkg to look for package libi2c-dev...
dpkg-query: package 'libi2c-dev' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
dpkg-query: package 'libi2c-dev' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
Using rpm to look for package i2c-tools...
rpm command not found
*** 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: i915
Found other loaded module: i2c_algo_bit
Loaded drm module depends on: i915,drm_kms_helper,
Loaded video module depends on: thinkpad_acpi,i915,
Using lspci to examine driver environment...
Video controller: Intel Corporation HD Graphics 520 (rev 07)
Testing if modules are loaded using /sys...
Module amdgpu is NOT loaded
Module fglrx is NOT loaded
Module i915 is loaded
Module nvidia is NOT loaded
Module nouveau is NOT loaded
Module radeon is NOT loaded
Module vboxvideo is NOT loaded
Module i2c_dev is NOT loaded
Module i2c_algo_bit is loaded
Module i2c_piix4 is NOT loaded
Examining /sys/bus/i2c/devices...
/sys/bus/i2c/devices/i2c-3/name: DPDDC-A
/sys/bus/i2c/devices/i2c-1/name: i915 gmbus dpb
/sys/bus/i2c/devices/i2c-6/name: DPMST
/sys/bus/i2c/devices/i2c-4/name: DPDDC-B
/sys/bus/i2c/devices/i2c-2/name: i915 gmbus dpd
/sys/bus/i2c/devices/i2c-0/name: i915 gmbus dpc
/sys/bus/i2c/devices/i2c-7/name: DPMST
/sys/bus/i2c/devices/i2c-5/name: DPDDC-C
Examining i2c buses...
Detected I2C buses:
Bus /dev/i2c-0 found: true
Bus /dev/i2c-0 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-1 found: true
Bus /dev/i2c-1 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-2 found: true
Bus /dev/i2c-2 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-3 found: true
Bus /dev/i2c-3 probed: true
Address 0x37 present: true
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
EDID synopsis:
Mfg id: AUO
Model: Unspecified
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
Product code: 0x226d (8813)
Extra descriptor: B125HAN02.2
White x,y: 0.306, 0.327
Red x,y: 0.587, 0.350
Green x,y: 0.342, 0.585
Blue x,y: 0.154, 0.115
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 06 af 6d 22 00 00 00 00 ..........m"....
+0010 34 19 01 04 a5 1c 10 78 02 6b a7 96 59 57 95 27 4......x.k..YW.'
+0020 1d 4e 53 00 00 00 01 01 01 01 01 01 01 01 01 01 .NS.............
+0030 01 01 01 01 01 01 14 37 80 b8 70 38 24 40 10 10 .......7..p8$@..
+0040 3e 00 14 9b 10 00 00 18 00 00 00 0f 00 00 00 00 >...............
+0050 00 00 00 00 00 00 00 00 00 20 00 00 00 fe 00 41 ......... .....A
+0060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe UO. ....
+0070 00 42 31 32 35 48 41 4e 30 32 2e 32 20 0a 00 a8 .B125HAN02.2 ...
Bus /dev/i2c-4 found: true
Bus /dev/i2c-4 probed: true
Address 0x37 present: false
Address 0x50 present: false
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-5 found: true
Bus /dev/i2c-5 probed: true
Address 0x37 present: false
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
Product code: 0xa07b (41083)
Extra descriptor: Unspecified
White x,y: 0.313, 0.329
Red x,y: 0.640, 0.330
Green x,y: 0.300, 0.600
Blue x,y: 0.150, 0.060
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 10 ac 7b a0 4c 56 4b 30 ..........{.LVK0
+0010 35 19 01 04 a5 34 20 78 2a ee 95 a3 54 4c 99 26 5....4 x*...TL.&
+0020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 .PT....@...@....
+0030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0
+0040 36 00 06 44 21 00 00 1a c8 73 00 a0 f0 b0 23 40 6..D!....s....#@
+0050 30 20 36 00 ff ff 00 00 00 1e 00 00 00 fc 00 44 0 6............D
+0060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 27 4a 00 98 ELL U2412M. 'J..
+0070 a1 00 2a 40 30 70 13 00 ff ff 00 00 00 1e 00 07 ..*@0p..........
Bus /dev/i2c-6 found: true
Bus /dev/i2c-6 probed: true
Address 0x37 present: true
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
Bus /dev/i2c-7 found: true
Bus /dev/i2c-7 probed: true
Address 0x37 present: true
Address 0x50 present: true
Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK
xrandr connection report:
eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 280mm x 160mm
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP2-1 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 520mm x 320mm
DP2-2 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 520mm x 320mm
DP2-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-2 using command "i2cdetect -y 2"
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-3 using command "i2cdetect -y 3"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-4 using command "i2cdetect -y 4"
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-5 using command "i2cdetect -y 5"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-6 using command "i2cdetect -y 6"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Probing bus /dev/i2c-7 using command "i2cdetect -y 7"
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
EDIDs reported by X11 for connected xrandr outputs:
xrandr output: eDP1
EDID synopsis:
Mfg id: AUO
Model: Unspecified
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
xrandr output: DP2-1
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: PPNN15CU0KVL
Manufacture year: 2015
EDID version: 1.4
xrandr output: DP2-2
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: 9W5YH3810DES
Manufacture year: 2013
EDID version: 1.3
Probing I2C devices using udev, susbsystem i2c-dev...
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
Device Node Path: /dev/i2c-4
struct udev_device at: 0x55da27a537c0
devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
sysname: i2c-4
sysnum: 4
devnode: /dev/i2c-4
Properties:
DEVNAME -> /dev/i2c-4
DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4
MAJOR -> 89
MINOR -> 4
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:4
device -> (null)
name -> DPDDC-B
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=4
DEVNAME=i2c-4
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
Device Node Path: /dev/i2c-5
struct udev_device at: 0x55da27a500a0
devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
sysname: i2c-5
sysnum: 5
devnode: /dev/i2c-5
Properties:
DEVNAME -> /dev/i2c-5
DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5
MAJOR -> 89
MINOR -> 5
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:5
device -> (null)
name -> DPDDC-C
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=5
DEVNAME=i2c-5
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
Device Node Path: /dev/i2c-3
struct udev_device at: 0x55da27a49da0
devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
sysname: i2c-3
sysnum: 3
devnode: /dev/i2c-3
Properties:
DEVNAME -> /dev/i2c-3
DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3
MAJOR -> 89
MINOR -> 3
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:3
device -> (null)
name -> DPDDC-A
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=3
DEVNAME=i2c-3
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0
Device Node Path: /dev/i2c-0
struct udev_device at: 0x55da27a4baf0
devpath: /devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-0/i2c-dev/i2c-0
MAJOR -> 89
MINOR -> 0
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:0
device -> (null)
name -> i915 gmbus dpc
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=0
DEVNAME=i2c-0
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1
Device Node Path: /dev/i2c-1
struct udev_device at: 0x55da27a5d340
devpath: /devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-1/i2c-dev/i2c-1
MAJOR -> 89
MINOR -> 1
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:1
device -> (null)
name -> i915 gmbus dpb
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=1
DEVNAME=i2c-1
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
Device Node Path: /dev/i2c-2
struct udev_device at: 0x55da27a64f80
devpath: /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
sysname: i2c-2
sysnum: 2
devnode: /dev/i2c-2
Properties:
DEVNAME -> /dev/i2c-2
DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2
MAJOR -> 89
MINOR -> 2
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:2
device -> (null)
name -> i915 gmbus dpd
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=2
DEVNAME=i2c-2
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
Device Node Path: /dev/i2c-6
struct udev_device at: 0x55da27a6cc10
devpath: /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
sysname: i2c-6
sysnum: 6
devnode: /dev/i2c-6
Properties:
DEVNAME -> /dev/i2c-6
DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6
MAJOR -> 89
MINOR -> 6
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:6
device -> (null)
name -> DPMST
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=6
DEVNAME=i2c-6
***One Device ***
path: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
Device Node Path: /dev/i2c-7
struct udev_device at: 0x55da27a6d950
devpath: /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
subsystem: i2c-dev
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
sysname: i2c-7
sysnum: 7
devnode: /dev/i2c-7
Properties:
DEVNAME -> /dev/i2c-7
DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7
MAJOR -> 89
MINOR -> 7
SUBSYSTEM -> i2c-dev
Sysattrs:
dev -> 89:7
device -> (null)
name -> DPMST
subsystem -> i2c-dev
uevent -> MAJOR=89
MINOR=7
DEVNAME=i2c-7
Checking for USB connected monitors...
Using lsusb to summarize USB devices...
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 005: ID 04f2:b52c Chicony Electronics Co., Ltd
Bus 001 Device 024: ID 17ef:1010 Lenovo
Bus 001 Device 025: ID 17ef:100f Lenovo
Bus 001 Device 029: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
Bus 001 Device 030: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 031: ID 04d9:0167 Holtek Semiconductor, Inc.
Bus 001 Device 032: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 17ef:1010 Lenovo
USB device toplogy...
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 4: Dev 24, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 25, If 0, Class=Hub, Driver=hub/3p, 480M
|__ Port 1: Dev 30, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 31, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 31, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 31, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 32, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 32, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 32, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 29, If 2, Class=Vendor Specific Class, Driver=ipheth, 480M
|__ Port 6: Dev 29, If 0, Class=Imaging, Driver=, 480M
|__ Port 6: Dev 29, If 1, Class=Vendor Specific Class, Driver=usbfs, 480M
|__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 8: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 8: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
Listing /dev/usb...
total 0
crw------- 1 root root 180, 0 Jan 17 11:58 hiddev0
crw------- 1 root root 180, 1 Jan 17 11:58 hiddev1
Listing /dev/hiddev*...
ls: cannot access '/dev/hiddev*': No such file or directory
Listing /dev/bus/usb...
total 0
drwxr-xr-x 2 root root 220 Jan 17 11:58 001
drwxr-xr-x 2 root root 80 Jan 17 11:18 002
Listing /dev/hidraw*...
crw------- 1 root root 244, 0 Jan 17 11:58 /dev/hidraw0
crw------- 1 root root 244, 1 Jan 17 11:58 /dev/hidraw1
crw------- 1 root root 244, 2 Jan 17 11:58 /dev/hidraw2
crw------- 1 root root 244, 3 Jan 17 11:58 /dev/hidraw3
crw------- 1 root root 244, 4 Jan 17 11:58 /dev/hidraw4
Probing USB HID devices using udev, susbsystem usbmisc...
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0
Device Node Path: /dev/usb/hiddev0
struct udev_device at: 0x55da27a7c6d0
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0
subsystem: usbmisc
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0
sysname: hiddev0
sysnum: 0
devnode: /dev/usb/hiddev0
Properties:
DEVNAME -> /dev/usb/hiddev0
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0
MAJOR -> 180
MINOR -> 0
SUBSYSTEM -> usbmisc
Sysattrs:
dev -> 180:0
device -> (null)
subsystem -> usbmisc
uevent -> MAJOR=180
MINOR=0
DEVNAME=usb/hiddev0
Parent device:
VID/PID: 04d9 0167
(null)
USB-HID Keyboard
serial: (null)
struct udev_device at: 0x55da27a91e80
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
sysname: 1-4.4.1.3
sysnum: 3
devnode: /dev/bus/usb/001/031
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/031
DEVNUM -> 031
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB-HID_Keyboard
ID_MODEL_ENC -> USB-HID\x20Keyboard
ID_MODEL_ID -> 0167
ID_REVISION -> 1103
ID_SERIAL -> 04d9_USB-HID_Keyboard
ID_USB_INTERFACES -> :030101:030000:
ID_VENDOR -> 04d9
ID_VENDOR_ENC -> 04d9
ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc.
ID_VENDOR_ID -> 04d9
MAJOR -> 189
MINOR -> 30
PRODUCT -> 4d9/167/1103
SUBSYSTEM -> usb
TYPE -> 0/0/0
USEC_INITIALIZED -> 124423894005
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 64
bMaxPower -> 100mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1103
bmAttributes -> a0
busnum -> 1
configuration ->
descriptors ->
dev -> 189:30
devnum -> 31
devpath -> 4.4.1.3
driver -> usb
idProduct -> 0167
idVendor -> 04d9
ltm_capable -> no
maxchild -> 0
port -> (null)
product -> USB-HID Keyboard
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=30
DEVNAME=bus/usb/001/031
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=4d9/167/1103
TYPE=0/0/0
BUSNUM=001
DEVNUM=031
urbnum -> 159
version -> 1.10
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1
Device Node Path: /dev/usb/hiddev1
struct udev_device at: 0x55da27a98590
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1
subsystem: usbmisc
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1
sysname: hiddev1
sysnum: 1
devnode: /dev/usb/hiddev1
Properties:
DEVNAME -> /dev/usb/hiddev1
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1
MAJOR -> 180
MINOR -> 1
SUBSYSTEM -> usbmisc
Sysattrs:
dev -> 180:1
device -> (null)
subsystem -> usbmisc
uevent -> MAJOR=180
MINOR=1
DEVNAME=usb/hiddev1
Parent device:
VID/PID: 046d c52b
Logitech
USB Receiver
serial: (null)
struct udev_device at: 0x55da27a9bb10
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
sysname: 1-4.4.1.4
sysnum: 4
devnode: /dev/bus/usb/001/032
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/032
DEVNUM -> 032
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB_Receiver
ID_MODEL_ENC -> USB\x20Receiver
ID_MODEL_FROM_DATABASE -> Unifying Receiver
ID_MODEL_ID -> c52b
ID_REVISION -> 1203
ID_SERIAL -> Logitech_USB_Receiver
ID_USB_INTERFACES -> :030101:030102:030000:
ID_VENDOR -> Logitech
ID_VENDOR_ENC -> Logitech
ID_VENDOR_FROM_DATABASE -> Logitech, Inc.
ID_VENDOR_ID -> 046d
MAJOR -> 189
MINOR -> 31
PRODUCT -> 46d/c52b/1203
SUBSYSTEM -> usb
TYPE -> 0/0/0
UPOWER_VENDOR -> Logitech, Inc.
USEC_INITIALIZED -> 124424244636
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 8
bMaxPower -> 98mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1203
bmAttributes -> a0
busnum -> 1
configuration -> RQR12.03_B0025
descriptors ->
dev -> 189:31
devnum -> 32
devpath -> 4.4.1.4
driver -> usb
idProduct -> c52b
idVendor -> 046d
ltm_capable -> no
manufacturer -> Logitech
maxchild -> 0
port -> (null)
product -> USB Receiver
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=31
DEVNAME=bus/usb/001/032
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=46d/c52b/1203
TYPE=0/0/0
BUSNUM=001
DEVNUM=032
urbnum -> 2802
version -> 2.00
Probing USB HID devices using udev, susbsystem hidraw...
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0
Device Node Path: /dev/hidraw0
struct udev_device at: 0x55da27a9c0c0
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0
subsystem: hidraw
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0
sysname: hidraw0
sysnum: 0
devnode: /dev/hidraw0
Properties:
DEVNAME -> /dev/hidraw0
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0
MAJOR -> 244
MINOR -> 0
SUBSYSTEM -> hidraw
Sysattrs:
dev -> 244:0
device -> (null)
subsystem -> hidraw
uevent -> MAJOR=244
MINOR=0
DEVNAME=hidraw0
Parent device:
VID/PID: 04d9 0167
(null)
USB-HID Keyboard
serial: (null)
struct udev_device at: 0x55da27af3fe0
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
sysname: 1-4.4.1.3
sysnum: 3
devnode: /dev/bus/usb/001/031
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/031
DEVNUM -> 031
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB-HID_Keyboard
ID_MODEL_ENC -> USB-HID\x20Keyboard
ID_MODEL_ID -> 0167
ID_REVISION -> 1103
ID_SERIAL -> 04d9_USB-HID_Keyboard
ID_USB_INTERFACES -> :030101:030000:
ID_VENDOR -> 04d9
ID_VENDOR_ENC -> 04d9
ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc.
ID_VENDOR_ID -> 04d9
MAJOR -> 189
MINOR -> 30
PRODUCT -> 4d9/167/1103
SUBSYSTEM -> usb
TYPE -> 0/0/0
USEC_INITIALIZED -> 124423894005
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 64
bMaxPower -> 100mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1103
bmAttributes -> a0
busnum -> 1
configuration ->
descriptors ->
dev -> 189:30
devnum -> 31
devpath -> 4.4.1.3
driver -> usb
idProduct -> 0167
idVendor -> 04d9
ltm_capable -> no
maxchild -> 0
port -> (null)
product -> USB-HID Keyboard
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=30
DEVNAME=bus/usb/001/031
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=4d9/167/1103
TYPE=0/0/0
BUSNUM=001
DEVNUM=031
urbnum -> 159
version -> 1.10
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1
Device Node Path: /dev/hidraw1
struct udev_device at: 0x55da27af3b90
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1
subsystem: hidraw
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1
sysname: hidraw1
sysnum: 1
devnode: /dev/hidraw1
Properties:
DEVNAME -> /dev/hidraw1
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1
MAJOR -> 244
MINOR -> 1
SUBSYSTEM -> hidraw
Sysattrs:
dev -> 244:1
device -> (null)
subsystem -> hidraw
uevent -> MAJOR=244
MINOR=1
DEVNAME=hidraw1
Parent device:
VID/PID: 04d9 0167
(null)
USB-HID Keyboard
serial: (null)
struct udev_device at: 0x55da27b5f330
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
sysname: 1-4.4.1.3
sysnum: 3
devnode: /dev/bus/usb/001/031
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/031
DEVNUM -> 031
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB-HID_Keyboard
ID_MODEL_ENC -> USB-HID\x20Keyboard
ID_MODEL_ID -> 0167
ID_REVISION -> 1103
ID_SERIAL -> 04d9_USB-HID_Keyboard
ID_USB_INTERFACES -> :030101:030000:
ID_VENDOR -> 04d9
ID_VENDOR_ENC -> 04d9
ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc.
ID_VENDOR_ID -> 04d9
MAJOR -> 189
MINOR -> 30
PRODUCT -> 4d9/167/1103
SUBSYSTEM -> usb
TYPE -> 0/0/0
USEC_INITIALIZED -> 124423894005
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 64
bMaxPower -> 100mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1103
bmAttributes -> a0
busnum -> 1
configuration ->
descriptors ->
dev -> 189:30
devnum -> 31
devpath -> 4.4.1.3
driver -> usb
idProduct -> 0167
idVendor -> 04d9
ltm_capable -> no
maxchild -> 0
port -> (null)
product -> USB-HID Keyboard
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=30
DEVNAME=bus/usb/001/031
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=4d9/167/1103
TYPE=0/0/0
BUSNUM=001
DEVNUM=031
urbnum -> 159
version -> 1.10
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2
Device Node Path: /dev/hidraw2
struct udev_device at: 0x55da27b5f330
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2
subsystem: hidraw
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2
sysname: hidraw2
sysnum: 2
devnode: /dev/hidraw2
Properties:
DEVNAME -> /dev/hidraw2
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2
MAJOR -> 244
MINOR -> 2
SUBSYSTEM -> hidraw
Sysattrs:
dev -> 244:2
device -> (null)
subsystem -> hidraw
uevent -> MAJOR=244
MINOR=2
DEVNAME=hidraw2
Parent device:
VID/PID: 04d9 0167
(null)
USB-HID Keyboard
serial: (null)
struct udev_device at: 0x55da27bc0620
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
sysname: 1-4.4.1.3
sysnum: 3
devnode: /dev/bus/usb/001/031
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/031
DEVNUM -> 031
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB-HID_Keyboard
ID_MODEL_ENC -> USB-HID\x20Keyboard
ID_MODEL_ID -> 0167
ID_REVISION -> 1103
ID_SERIAL -> 04d9_USB-HID_Keyboard
ID_USB_INTERFACES -> :030101:030000:
ID_VENDOR -> 04d9
ID_VENDOR_ENC -> 04d9
ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc.
ID_VENDOR_ID -> 04d9
MAJOR -> 189
MINOR -> 30
PRODUCT -> 4d9/167/1103
SUBSYSTEM -> usb
TYPE -> 0/0/0
USEC_INITIALIZED -> 124423894005
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 64
bMaxPower -> 100mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1103
bmAttributes -> a0
busnum -> 1
configuration ->
descriptors ->
dev -> 189:30
devnum -> 31
devpath -> 4.4.1.3
driver -> usb
idProduct -> 0167
idVendor -> 04d9
ltm_capable -> no
maxchild -> 0
port -> (null)
product -> USB-HID Keyboard
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=30
DEVNAME=bus/usb/001/031
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=4d9/167/1103
TYPE=0/0/0
BUSNUM=001
DEVNUM=031
urbnum -> 159
version -> 1.10
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4
Device Node Path: /dev/hidraw4
struct udev_device at: 0x55da27bc0620
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4
subsystem: hidraw
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4
sysname: hidraw4
sysnum: 4
devnode: /dev/hidraw4
Properties:
DEVNAME -> /dev/hidraw4
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4
MAJOR -> 244
MINOR -> 4
SUBSYSTEM -> hidraw
Sysattrs:
dev -> 244:4
device -> (null)
subsystem -> hidraw
uevent -> MAJOR=244
MINOR=4
DEVNAME=hidraw4
Parent device:
VID/PID: 046d c52b
Logitech
USB Receiver
serial: (null)
struct udev_device at: 0x55da27c1aa60
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
sysname: 1-4.4.1.4
sysnum: 4
devnode: /dev/bus/usb/001/032
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/032
DEVNUM -> 032
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB_Receiver
ID_MODEL_ENC -> USB\x20Receiver
ID_MODEL_FROM_DATABASE -> Unifying Receiver
ID_MODEL_ID -> c52b
ID_REVISION -> 1203
ID_SERIAL -> Logitech_USB_Receiver
ID_USB_INTERFACES -> :030101:030102:030000:
ID_VENDOR -> Logitech
ID_VENDOR_ENC -> Logitech
ID_VENDOR_FROM_DATABASE -> Logitech, Inc.
ID_VENDOR_ID -> 046d
MAJOR -> 189
MINOR -> 31
PRODUCT -> 46d/c52b/1203
SUBSYSTEM -> usb
TYPE -> 0/0/0
UPOWER_VENDOR -> Logitech, Inc.
USEC_INITIALIZED -> 124424244636
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 8
bMaxPower -> 98mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1203
bmAttributes -> a0
busnum -> 1
configuration -> RQR12.03_B0025
descriptors ->
dev -> 189:31
devnum -> 32
devpath -> 4.4.1.4
driver -> usb
idProduct -> c52b
idVendor -> 046d
ltm_capable -> no
manufacturer -> Logitech
maxchild -> 0
port -> (null)
product -> USB Receiver
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=31
DEVNAME=bus/usb/001/032
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=46d/c52b/1203
TYPE=0/0/0
BUSNUM=001
DEVNUM=032
urbnum -> 2802
version -> 2.00
***One Device ***
path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3
Device Node Path: /dev/hidraw3
struct udev_device at: 0x55da27c1aa60
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3
subsystem: hidraw
devtype: (null)
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3
sysname: hidraw3
sysnum: 3
devnode: /dev/hidraw3
Properties:
DEVNAME -> /dev/hidraw3
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3
MAJOR -> 244
MINOR -> 3
SUBSYSTEM -> hidraw
Sysattrs:
dev -> 244:3
device -> (null)
subsystem -> hidraw
uevent -> MAJOR=244
MINOR=3
DEVNAME=hidraw3
Parent device:
VID/PID: 046d c52b
Logitech
USB Receiver
serial: (null)
struct udev_device at: 0x55da27ccbf80
devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
subsystem: usb
devtype: usb_device
syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
sysname: 1-4.4.1.4
sysnum: 4
devnode: /dev/bus/usb/001/032
Properties:
BUSNUM -> 001
DEVNAME -> /dev/bus/usb/001/032
DEVNUM -> 032
DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4
DEVTYPE -> usb_device
DRIVER -> usb
ID_BUS -> usb
ID_MODEL -> USB_Receiver
ID_MODEL_ENC -> USB\x20Receiver
ID_MODEL_FROM_DATABASE -> Unifying Receiver
ID_MODEL_ID -> c52b
ID_REVISION -> 1203
ID_SERIAL -> Logitech_USB_Receiver
ID_USB_INTERFACES -> :030101:030102:030000:
ID_VENDOR -> Logitech
ID_VENDOR_ENC -> Logitech
ID_VENDOR_FROM_DATABASE -> Logitech, Inc.
ID_VENDOR_ID -> 046d
MAJOR -> 189
MINOR -> 31
PRODUCT -> 46d/c52b/1203
SUBSYSTEM -> usb
TYPE -> 0/0/0
UPOWER_VENDOR -> Logitech, Inc.
USEC_INITIALIZED -> 124424244636
Sysattrs:
authorized -> 1
avoid_reset_quirk -> 0
bConfigurationValue -> 1
bDeviceClass -> 00
bDeviceProtocol -> 00
bDeviceSubClass -> 00
bMaxPacketSize0 -> 8
bMaxPower -> 98mA
bNumConfigurations -> 1
bNumInterfaces -> 3
bcdDevice -> 1203
bmAttributes -> a0
busnum -> 1
configuration -> RQR12.03_B0025
descriptors ->
dev -> 189:31
devnum -> 32
devpath -> 4.4.1.4
driver -> usb
idProduct -> c52b
idVendor -> 046d
ltm_capable -> no
manufacturer -> Logitech
maxchild -> 0
port -> (null)
product -> USB Receiver
quirks -> 0x0
removable -> unknown
speed -> 12
subsystem -> usb
uevent -> MAJOR=189
MINOR=31
DEVNAME=bus/usb/001/032
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=46d/c52b/1203
TYPE=0/0/0
BUSNUM=001
DEVNUM=032
urbnum -> 2802
version -> 2.00
Probing possible HID monitors using libusb...
(possible_monitor_config_descriptor) Examining only interface 0 for device 1:5, vid=0x04f2, pid=0xb52c Chicony Electronics Co., Ltd (null)
(possible_monitor_config_descriptor) Examining only interface 0 for device 1:3, vid=0x8087, pid=0x0a2b Intel Corp. (null)
(possible_monitor_config_descriptor) Examining only interface 0 for device 1:32, vid=0x046d, pid=0xc52b Logitech, Inc. Unifying Receiver
(possible_monitor_config_descriptor) Examining only interface 0 for device 1:31, vid=0x04d9, pid=0x0167 Holtek Semiconductor, Inc. (null)
Checking for USB connected monitors on /dev/hidraw* ...
Found 5 USB HID devices.
Probing device /dev/hidraw0
Raw Name: USB-HID Keyboard
Raw Phys: usb-0000:00:14.0-4.4.1.3/input0
Raw Info:
bustype: 3 (USB)
vendor: 0x04d9
product: 0x0167
Busno:Devno as reported by get_udev_usb_devinfo() for hidraw0: 001:031
Not a USB connected monitor
Probing device /dev/hidraw1
Raw Name: USB-HID Keyboard
Raw Phys: usb-0000:00:14.0-4.4.1.3/input1
Raw Info:
bustype: 3 (USB)
vendor: 0x04d9
product: 0x0167
Busno:Devno as reported by get_udev_usb_devinfo() for hidraw1: 001:031
Not a USB connected monitor
Probing device /dev/hidraw2
Raw Name: USB-HID Keyboard
Raw Phys: usb-0000:00:14.0-4.4.1.3/input2
Raw Info:
bustype: 3 (USB)
vendor: 0x04d9
product: 0x0167
Busno:Devno as reported by get_udev_usb_devinfo() for hidraw2: 001:031
Not a USB connected monitor
Probing device /dev/hidraw3
Raw Name: Logitech USB Receiver
Raw Phys: usb-0000:00:14.0-4.4.1.4/input2
Raw Info:
bustype: 3 (USB)
vendor: 0x046d
product: 0xc52b
Busno:Devno as reported by get_udev_usb_devinfo() for hidraw3: 001:032
Not a USB connected monitor
Probing device /dev/hidraw4
Raw Name: Logitech M560
Raw Phys: usb-0000:00:14.0-4.4.1.4:1
Raw Info:
bustype: 3 (USB)
vendor: 0x046d
product: 0x402d
Busno:Devno as reported by get_udev_usb_devinfo() for hidraw4: 001:032
Not a USB connected monitor
Checking for USB HID devices using hiddev...
Found 2 USB HID devices.
Device /dev/usb/hiddev0, devnum.busnum: 1.31, vid:pid: 04d9:0167 - USB-HID Keyboard
Not a USB HID monitor
Device /dev/usb/hiddev1, devnum.busnum: 1.32, vid:pid: 046d:c52b - Logitech USB Receiver
Not a USB HID monitor
Checking for USB HID Report Descriptors in /sys/kernel/debug/hid...
*** Detected Displays ***
Display 1
I2C bus: /dev/i2c-3
Supports DDC: true
I2C address 0x37 (DDC) present: true
I2C address 0x50 (EDID) present: true
EDID synopsis:
Mfg id: AUO
Model: Unspecified
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
Product code: 0x226d (8813)
Extra descriptor: B125HAN02.2
White x,y: 0.306, 0.327
Red x,y: 0.587, 0.350
Green x,y: 0.342, 0.585
Blue x,y: 0.154, 0.115
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 06 af 6d 22 00 00 00 00 ..........m"....
+0010 34 19 01 04 a5 1c 10 78 02 6b a7 96 59 57 95 27 4......x.k..YW.'
+0020 1d 4e 53 00 00 00 01 01 01 01 01 01 01 01 01 01 .NS.............
+0030 01 01 01 01 01 01 14 37 80 b8 70 38 24 40 10 10 .......7..p8$@..
+0040 3e 00 14 9b 10 00 00 18 00 00 00 0f 00 00 00 00 >...............
+0050 00 00 00 00 00 00 00 00 00 20 00 00 00 fe 00 41 ......... .....A
+0060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe UO. ....
+0070 00 42 31 32 35 48 41 4e 30 32 2e 32 20 0a 00 a8 .B125HAN02.2 ...
VCP version: Detection failed
(ddc_report_active_display) get_nontable_vcp_value(0xc8) returned DDCRC_RETRIES(-3015): maximum retries exceeded
Controller mfg: Unspecified
(ddc_report_active_display) get_vcp_value(0xc9) returned DDCRC_RETRIES(-3015): maximum retries exceeded
Firmware version: Unspecified
Invalid display
I2C bus: /dev/i2c-5
Supports DDC: false
I2C address 0x37 (DDC) present: false
I2C address 0x50 (EDID) present: true
EDID synopsis:
Mfg id: DEL
Model: DELL U2412M
Serial number: Unspecified
Manufacture year: 2015
EDID version: 1.4
Product code: 0xa07b (41083)
Extra descriptor: Unspecified
White x,y: 0.313, 0.329
Red x,y: 0.640, 0.330
Green x,y: 0.300, 0.600
Blue x,y: 0.150, 0.060
EDID hex dump:
+0 +4 +8 +c 0 4 8 c
+0000 00 ff ff ff ff ff ff 00 10 ac 7b a0 4c 56 4b 30 ..........{.LVK0
+0010 35 19 01 04 a5 34 20 78 2a ee 95 a3 54 4c 99 26 5....4 x*...TL.&
+0020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 .PT....@...@....
+0030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0
+0040 36 00 06 44 21 00 00 1a c8 73 00 a0 f0 b0 23 40 6..D!....s....#@
+0050 30 20 36 00 ff ff 00 00 00 1e 00 00 00 fc 00 44 0 6............D
+0060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 27 4a 00 98 ELL U2412M. 'J..
+0070 a1 00 2a 40 30 70 13 00 ff ff 00 00 00 1e 00 07 ..*@0p..........
Display 2
I2C bus: /dev/i2c-6
Supports DDC: true
I2C address 0x37 (DDC) present: true
I2C address 0x50 (EDID) present: true
(ddc_open_display) No EDID for device on bus /dev/i2c-6
Error opening display bus /dev/i2c-6, error = -3016 (DDCRC_EDID)
(ddc_close_display) close_i2c_bus returned 9
Display 3
I2C bus: /dev/i2c-7
Supports DDC: true
I2C address 0x37 (DDC) present: true
I2C address 0x50 (EDID) present: true
(ddc_open_display) No EDID for device on bus /dev/i2c-7
Error opening display bus /dev/i2c-7, error = -3016 (DDCRC_EDID)
(ddc_close_display) close_i2c_bus returned 9
Probing display 1
Capabilities for display Display_Handle[i2c: fh=3, busno=3]
Unable to get capabilities for monitor on Display_Handle[i2c: fh=3, busno=3]. Maximum DDC retries exceeded.
May support table reads: true
Scanning all VCP feature codes for display Display_Handle[i2c: fh=3, busno=3]
Getting data for non-table VCP code 0x00 - Unknown feature:
VCP code 0x00 (Unknown feature ): Maximum retries exceeded
VCP code 0x01 (Degauss ): Write-only feature
Getting data for non-table VCP code 0x02 - New control value:
VCP code 0x02 (New control value ): Maximum retries exceeded
Getting data for non-table VCP code 0x03 - Soft controls:
VCP code 0x03 (Soft controls ): Maximum retries exceeded
VCP code 0x04 (Restore factory defaults ): Write-only feature
VCP code 0x05 (Restore factory brightness/contrast defaults): Write-only feature
VCP code 0x06 (Restore factory geometry defaults): Write-only feature
Getting data for non-table VCP code 0x07 - Unknown feature:
VCP code 0x07 (Unknown feature ): Maximum retries exceeded
VCP code 0x08 (Restore color defaults ): Write-only feature
Getting data for non-table VCP code 0x09 - Unknown feature:
VCP code 0x09 (Unknown feature ): Maximum retries exceeded
VCP code 0x0a (Restore factory TV defaults ): Write-only feature
Getting data for non-table VCP code 0x0b - Color temperature increment:
VCP code 0x0b (Color temperature increment ): Maximum retries exceeded
Getting data for non-table VCP code 0x0c - Color temperature request:
VCP code 0x0c (Color temperature request ): Maximum retries exceeded
Getting data for non-table VCP code 0x0d - Unknown feature:
VCP code 0x0d (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x0e - Clock:
VCP code 0x0e (Clock ): Maximum retries exceeded
Getting data for non-table VCP code 0x0f - Unknown feature:
VCP code 0x0f (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x10 - Brightness:
VCP code 0x10 (Brightness ): Maximum retries exceeded
Getting data for non-table VCP code 0x11 - Flesh tone enhancement:
VCP code 0x11 (Flesh tone enhancement ): Maximum retries exceeded
Getting data for non-table VCP code 0x12 - Contrast:
VCP code 0x12 (Contrast ): Maximum retries exceeded
Getting data for non-table VCP code 0x13 - Backlight control:
VCP code 0x13 (Backlight control ): Maximum retries exceeded
Getting data for non-table VCP code 0x14 - Select color preset:
VCP code 0x14 (Select color preset ): Maximum retries exceeded
Getting data for non-table VCP code 0x15 - Unknown feature:
VCP code 0x15 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x16 - Video gain: Red:
VCP code 0x16 (Video gain: Red ): Maximum retries exceeded
Getting data for non-table VCP code 0x17 - User color vision compensation:
VCP code 0x17 (User color vision compensation): Maximum retries exceeded
Getting data for non-table VCP code 0x18 - Video gain: Green:
VCP code 0x18 (Video gain: Green ): Maximum retries exceeded
Getting data for non-table VCP code 0x19 - Unknown feature:
VCP code 0x19 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x1a - Video gain: Blue:
VCP code 0x1a (Video gain: Blue ): Maximum retries exceeded
Getting data for non-table VCP code 0x1b - Unknown feature:
VCP code 0x1b (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x1c - Focus:
VCP code 0x1c (Focus ): Maximum retries exceeded
Getting data for non-table VCP code 0x1d - Unknown feature:
VCP code 0x1d (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x1e - Auto setup:
VCP code 0x1e (Auto setup ): Maximum retries exceeded
Getting data for non-table VCP code 0x1f - Auto color setup:
VCP code 0x1f (Auto color setup ): Maximum retries exceeded
Getting data for non-table VCP code 0x20 - Horizontal Position:
VCP code 0x20 (Horizontal Position ): Maximum retries exceeded
Getting data for non-table VCP code 0x21 - Unknown feature:
VCP code 0x21 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x22 - Horizontal Size:
VCP code 0x22 (Horizontal Size ): Maximum retries exceeded
Getting data for non-table VCP code 0x23 - Unknown feature:
VCP code 0x23 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x24 - Horizontal Pincushion:
VCP code 0x24 (Horizontal Pincushion ): Maximum retries exceeded
Getting data for non-table VCP code 0x25 - Unknown feature:
VCP code 0x25 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x26 - Horizontal Pincushion Balance:
VCP code 0x26 (Horizontal Pincushion Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x27 - Unknown feature:
VCP code 0x27 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x28 - Horizontal Convergence:
VCP code 0x28 (Horizontal Convergence ): Maximum retries exceeded
Getting data for non-table VCP code 0x29 - Horizontal Convergence M/G:
VCP code 0x29 (Horizontal Convergence M/G ): Maximum retries exceeded
Getting data for non-table VCP code 0x2a - Horizontal Linearity:
VCP code 0x2a (Horizontal Linearity ): Maximum retries exceeded
Getting data for non-table VCP code 0x2b - Unknown feature:
VCP code 0x2b (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x2c - Horizontal Linearity Balance:
VCP code 0x2c (Horizontal Linearity Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x2d - Unknown feature:
VCP code 0x2d (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x2e - Gray scale expansion:
VCP code 0x2e (Gray scale expansion ): Maximum retries exceeded
Getting data for non-table VCP code 0x2f - Unknown feature:
VCP code 0x2f (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x30 - Vertical Position:
VCP code 0x30 (Vertical Position ): Maximum retries exceeded
Getting data for non-table VCP code 0x31 - Unknown feature:
VCP code 0x31 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x32 - Vertical Size:
VCP code 0x32 (Vertical Size ): Maximum retries exceeded
Getting data for non-table VCP code 0x33 - Unknown feature:
VCP code 0x33 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x34 - Vertical Pincushion:
VCP code 0x34 (Vertical Pincushion ): Maximum retries exceeded
Getting data for non-table VCP code 0x35 - Unknown feature:
VCP code 0x35 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x36 - Vertical Pincushion Balance:
VCP code 0x36 (Vertical Pincushion Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x37 - Unknown feature:
VCP code 0x37 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x38 - Vertical Convergence:
VCP code 0x38 (Vertical Convergence ): Maximum retries exceeded
Getting data for non-table VCP code 0x39 - Vertical Convergence M/G:
VCP code 0x39 (Vertical Convergence M/G ): Maximum retries exceeded
Getting data for non-table VCP code 0x3a - Vertical Linearity:
VCP code 0x3a (Vertical Linearity ): Maximum retries exceeded
Getting data for non-table VCP code 0x3b - Unknown feature:
VCP code 0x3b (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x3c - Vertical Linearity Balance:
VCP code 0x3c (Vertical Linearity Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x3d - Unknown feature:
VCP code 0x3d (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x3e - Clock phase:
VCP code 0x3e (Clock phase ): Maximum retries exceeded
Getting data for non-table VCP code 0x3f - Unknown feature:
VCP code 0x3f (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x40 - Key Balance:
VCP code 0x40 (Key Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x41 - Vertical Parallelogram:
VCP code 0x41 (Vertical Parallelogram ): Maximum retries exceeded
Getting data for non-table VCP code 0x42 - Horizontal Trapezoid:
VCP code 0x42 (Horizontal Trapezoid ): Maximum retries exceeded
Getting data for non-table VCP code 0x43 - Vertical Trapezoid:
VCP code 0x43 (Vertical Trapezoid ): Maximum retries exceeded
Getting data for non-table VCP code 0x44 - Tilt (rotation):
VCP code 0x44 (Tilt (rotation) ): Maximum retries exceeded
Getting data for non-table VCP code 0x45 - Unknown feature:
VCP code 0x45 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x46 - Top Corner:
VCP code 0x46 (Top Corner ): Maximum retries exceeded
Getting data for non-table VCP code 0x47 - Unknown feature:
VCP code 0x47 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x48 - Top Corner Balance:
VCP code 0x48 (Top Corner Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x49 - Unknown feature:
VCP code 0x49 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x4a - Bottom Corner:
VCP code 0x4a (Bottom Corner ): Maximum retries exceeded
Getting data for non-table VCP code 0x4b - Unknown feature:
VCP code 0x4b (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x4c - Bottom Corner Balance:
VCP code 0x4c (Bottom Corner Balance ): Maximum retries exceeded
Getting data for non-table VCP code 0x4d - Unknown feature:
VCP code 0x4d (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x4e - Unknown feature:
VCP code 0x4e (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x4f - Unknown feature:
VCP code 0x4f (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x50 - Unknown feature:
VCP code 0x50 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x51 - Unknown feature:
VCP code 0x51 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x52 - Active control:
VCP code 0x52 (Active control ): Maximum retries exceeded
Getting data for non-table VCP code 0x53 - Unknown feature:
VCP code 0x53 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x54 - Performance Preservation:
VCP code 0x54 (Performance Preservation ): Maximum retries exceeded
Getting data for non-table VCP code 0x55 - Unknown feature:
VCP code 0x55 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x56 - Horizontal Moire:
VCP code 0x56 (Horizontal Moire ): Maximum retries exceeded
Getting data for non-table VCP code 0x57 - Unknown feature:
VCP code 0x57 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x58 - Vertical Moire:
VCP code 0x58 (Vertical Moire ): Maximum retries exceeded
Getting data for non-table VCP code 0x59 - 6 axis saturation: Red:
VCP code 0x59 (6 axis saturation: Red ): Maximum retries exceeded
Getting data for non-table VCP code 0x5a - 6 axis saturation: Yellow:
VCP code 0x5a (6 axis saturation: Yellow ): Maximum retries exceeded
Getting data for non-table VCP code 0x5b - 6 axis saturation: Green:
VCP code 0x5b (6 axis saturation: Green ): Maximum retries exceeded
Getting data for non-table VCP code 0x5c - 6 axis saturation: Cyan:
VCP code 0x5c (6 axis saturation: Cyan ): Maximum retries exceeded
Getting data for non-table VCP code 0x5d - 6 axis saturation: Blue:
VCP code 0x5d (6 axis saturation: Blue ): Maximum retries exceeded
Getting data for non-table VCP code 0x5e - 6 axis saturation: Magenta:
VCP code 0x5e (6 axis saturation: Magenta ): Maximum retries exceeded
Getting data for non-table VCP code 0x5f - Unknown feature:
VCP code 0x5f (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x60 - Input Source:
VCP code 0x60 (Input Source ): Maximum retries exceeded
Getting data for non-table VCP code 0x61 - Unknown feature:
VCP code 0x61 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x62 - Audio speaker volume:
VCP code 0x62 (Audio speaker volume ): Maximum retries exceeded
Getting data for non-table VCP code 0x63 - Speaker Select:
VCP code 0x63 (Speaker Select ): Maximum retries exceeded
Getting data for non-table VCP code 0x64 - Audio: Microphone Volume:
VCP code 0x64 (Audio: Microphone Volume ): Maximum retries exceeded
Getting data for non-table VCP code 0x65 - Unknown feature:
VCP code 0x65 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x66 - Ambient light sensor:
VCP code 0x66 (Ambient light sensor ): Maximum retries exceeded
Getting data for non-table VCP code 0x67 - Unknown feature:
VCP code 0x67 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x68 - Unknown feature:
VCP code 0x68 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x69 - Unknown feature:
VCP code 0x69 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x6a - Unknown feature:
VCP code 0x6a (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x6b - Backlight Level: White:
VCP code 0x6b (Backlight Level: White ): Maximum retries exceeded
Getting data for non-table VCP code 0x6c - Video black level: Red:
VCP code 0x6c (Video black level: Red ): Maximum retries exceeded
Getting data for non-table VCP code 0x6d - Backlight Level: Red:
VCP code 0x6d (Backlight Level: Red ): Maximum retries exceeded
Getting data for non-table VCP code 0x6e - Video black level: Green:
VCP code 0x6e (Video black level: Green ): Maximum retries exceeded
Getting data for non-table VCP code 0x6f - Backlight Level: Green:
VCP code 0x6f (Backlight Level: Green ): Maximum retries exceeded
Getting data for non-table VCP code 0x70 - Video black level: Blue:
VCP code 0x70 (Video black level: Blue ): Maximum retries exceeded
Getting data for non-table VCP code 0x71 - Backlight Level: Blue:
VCP code 0x71 (Backlight Level: Blue ): Maximum retries exceeded
Getting data for non-table VCP code 0x72 - Gamma:
VCP code 0x72 (Gamma ): Maximum retries exceeded
Getting data for table VCP code 0x73 - LUT Size:
VCP code 0x73 (LUT Size ): Maximum retries exceeded
Getting data for table VCP code 0x74 - Single point LUT operation:
VCP code 0x74 (Single point LUT operation ): Maximum retries exceeded
Getting data for table VCP code 0x75 - Block LUT operation:
VCP code 0x75 (Block LUT operation ): Maximum retries exceeded
VCP code 0x76 (Remote Procedure Call ): Write-only feature
Getting data for non-table VCP code 0x77 - Unknown feature:
VCP code 0x77 (Unknown feature ): Maximum retries exceeded
Getting data for table VCP code 0x78 - EDID operation:
VCP code 0x78 (EDID operation ): Maximum retries exceeded
Getting data for non-table VCP code 0x79 - Unknown feature:
VCP code 0x79 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x7a - Adjust Focal Plane:
VCP code 0x7a (Adjust Focal Plane ): Maximum retries exceeded
Getting data for non-table VCP code 0x7b - Unknown feature:
VCP code 0x7b (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x7c - Adjust Zoom:
VCP code 0x7c (Adjust Zoom ): Maximum retries exceeded
Getting data for non-table VCP code 0x7d - Unknown feature:
VCP code 0x7d (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x7e - Trapezoid:
VCP code 0x7e (Trapezoid ): Maximum retries exceeded
Getting data for non-table VCP code 0x7f - Unknown feature:
VCP code 0x7f (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x80 - Keystone:
VCP code 0x80 (Keystone ): Maximum retries exceeded
Getting data for non-table VCP code 0x81 - Unknown feature:
VCP code 0x81 (Unknown feature ): Maximum retries exceeded
VCP code 0x82 (HorFlip ): Write-only feature
Getting data for non-table VCP code 0x83 - Unknown feature:
VCP code 0x83 (Unknown feature ): Maximum retries exceeded
VCP code 0x84 (VertFlip ): Write-only feature
Getting data for non-table VCP code 0x85 - Unknown feature:
VCP code 0x85 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x86 - Display Scaling:
VCP code 0x86 (Display Scaling ): Maximum retries exceeded
Getting data for non-table VCP code 0x87 - Sharpness:
VCP code 0x87 (Sharpness ): Maximum retries exceeded
Getting data for non-table VCP code 0x88 - Velocity Scan Modulation:
VCP code 0x88 (Velocity Scan Modulation ): Maximum retries exceeded
Getting data for non-table VCP code 0x89 - Unknown feature:
VCP code 0x89 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0x8a - TV Color Saturation:
VCP code 0x8a (TV Color Saturation ): Maximum retries exceeded
VCP code 0x8b (TV Channel Up/Down ): Write-only feature
Getting data for non-table VCP code 0x8c - TV Sharpness:
VCP code 0x8c (TV Sharpness ): Maximum retries exceeded
Getting data for non-table VCP code 0x8d - Audio Mute:
VCP code 0x8d (Audio Mute ): Maximum retries exceeded
Getting data for non-table VCP code 0x8e - TV Contrast:
VCP code 0x8e (TV Contrast ): Maximum retries exceeded
Getting data for non-table VCP code 0x8f - Audio Treble:
VCP code 0x8f (Audio Treble ): Maximum retries exceeded
Getting data for non-table VCP code 0x90 - Hue:
VCP code 0x90 (Hue ): Maximum retries exceeded
Getting data for non-table VCP code 0x91 - Audio Bass:
VCP code 0x91 (Audio Bass ): Maximum retries exceeded
Getting data for non-table VCP code 0x92 - TV Black level/Brightness:
VCP code 0x92 (TV Black level/Brightness ): Maximum retries exceeded
Getting data for non-table VCP code 0x93 - Audio Balance L/R:
VCP code 0x93 (Audio Balance L/R ): Maximum retries exceeded
Getting data for non-table VCP code 0x94 - Audio Stereo Mode:
VCP code 0x94 (Audio Stereo Mode ): Maximum retries exceeded
Getting data for non-table VCP code 0x95 - Window Position(TL_X):
VCP code 0x95 (Window Position(TL_X) ): Maximum retries exceeded
Getting data for non-table VCP code 0x96 - Window Position(TL_Y):
VCP code 0x96 (Window Position(TL_Y) ): Maximum retries exceeded
Getting data for non-table VCP code 0x97 - Window Position(BR_X):
VCP code 0x97 (Window Position(BR_X) ): Maximum retries exceeded
Getting data for non-table VCP code 0x98 - Window Position(BR_Y):
VCP code 0x98 (Window Position(BR_Y) ): Maximum retries exceeded
Getting data for non-table VCP code 0x99 - Window control on/off:
VCP code 0x99 (Window control on/off ): Maximum retries exceeded
Getting data for non-table VCP code 0x9a - Window background:
VCP code 0x9a (Window background ): Maximum retries exceeded
Getting data for non-table VCP code 0x9b - 6 axis hue control: Red:
VCP code 0x9b (6 axis hue control: Red ): Maximum retries exceeded
Getting data for non-table VCP code 0x9c - 6 axis hue control: Yellow:
VCP code 0x9c (6 axis hue control: Yellow ): Maximum retries exceeded
Getting data for non-table VCP code 0x9d - 6 axis hue control: Green:
VCP code 0x9d (6 axis hue control: Green ): Maximum retries exceeded
Getting data for non-table VCP code 0x9e - 6 axis hue control: Cyan:
VCP code 0x9e (6 axis hue control: Cyan ): Maximum retries exceeded
Getting data for non-table VCP code 0x9f - 6 axis hue control: Blue:
VCP code 0x9f (6 axis hue control: Blue ): Maximum retries exceeded
Getting data for non-table VCP code 0xa0 - 6 axis hue control: Magenta:
VCP code 0xa0 (6 axis hue control: Magenta ): Maximum retries exceeded
Getting data for non-table VCP code 0xa1 - Unknown feature:
VCP code 0xa1 (Unknown feature ): Maximum retries exceeded
VCP code 0xa2 (Auto setup on/off ): Write-only feature
Getting data for non-table VCP code 0xa3 - Unknown feature:
VCP code 0xa3 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xa4 - Turn the selected window operation on/off:
VCP code 0xa4 (Turn the selected window operation on/off): Maximum retries exceeded
Getting data for non-table VCP code 0xa5 - Change the selected window:
VCP code 0xa5 (Change the selected window ): Maximum retries exceeded
Getting data for non-table VCP code 0xa6 - Unknown feature:
VCP code 0xa6 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xa7 - Unknown feature:
VCP code 0xa7 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xa8 - Unknown feature:
VCP code 0xa8 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xa9 - Unknown feature:
VCP code 0xa9 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xaa - Screen Orientation:
VCP code 0xaa (Screen Orientation ): Maximum retries exceeded
Getting data for non-table VCP code 0xab - Unknown feature:
VCP code 0xab (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xac - Horizontal frequency:
VCP code 0xac (Horizontal frequency ): Maximum retries exceeded
Getting data for non-table VCP code 0xad - Unknown feature:
VCP code 0xad (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xae - Vertical frequency:
VCP code 0xae (Vertical frequency ): Maximum retries exceeded
Getting data for non-table VCP code 0xaf - Unknown feature:
VCP code 0xaf (Unknown feature ): Maximum retries exceeded
VCP code 0xb0 (Settings ): Write-only feature
Getting data for non-table VCP code 0xb1 - Unknown feature:
VCP code 0xb1 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xb2 - Flat panel sub-pixel layout:
VCP code 0xb2 (Flat panel sub-pixel layout ): Maximum retries exceeded
Getting data for non-table VCP code 0xb3 - Unknown feature:
VCP code 0xb3 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xb4 - Source Timing Mode:
VCP code 0xb4 (Source Timing Mode ): Maximum retries exceeded
Getting data for non-table VCP code 0xb5 - Unknown feature:
VCP code 0xb5 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xb6 - Display technology type:
VCP code 0xb6 (Display technology type ): Maximum retries exceeded
Getting data for non-table VCP code 0xb7 - Monitor status:
VCP code 0xb7 (Monitor status ): Maximum retries exceeded
Getting data for non-table VCP code 0xb8 - Packet count:
VCP code 0xb8 (Packet count ): Maximum retries exceeded
Getting data for non-table VCP code 0xb9 - Monitor X origin:
VCP code 0xb9 (Monitor X origin ): Maximum retries exceeded
Getting data for non-table VCP code 0xba - Monitor Y origin:
VCP code 0xba (Monitor Y origin ): Maximum retries exceeded
Getting data for non-table VCP code 0xbb - Header error count:
VCP code 0xbb (Header error count ): Maximum retries exceeded
Getting data for non-table VCP code 0xbc - Body CRC error count:
VCP code 0xbc (Body CRC error count ): Maximum retries exceeded
Getting data for non-table VCP code 0xbd - Client ID:
VCP code 0xbd (Client ID ): Maximum retries exceeded
Getting data for non-table VCP code 0xbe - Link control:
VCP code 0xbe (Link control ): Maximum retries exceeded
Getting data for non-table VCP code 0xbf - Unknown feature:
VCP code 0xbf (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xc0 - Display usage time:
VCP code 0xc0 (Display usage time ): Maximum retries exceeded
Getting data for non-table VCP code 0xc1 - Unknown feature:
VCP code 0xc1 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xc2 - Display descriptor length:
VCP code 0xc2 (Display descriptor length ): Maximum retries exceeded
Getting data for table VCP code 0xc3 - Transmit display descriptor:
VCP code 0xc3 (Transmit display descriptor ): Maximum retries exceeded
Getting data for non-table VCP code 0xc4 - Enable display of 'display descriptor':
VCP code 0xc4 (Enable display of 'display descriptor'): Maximum retries exceeded
Getting data for non-table VCP code 0xc5 - Unknown feature:
VCP code 0xc5 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xc6 - Application enable key:
VCP code 0xc6 (Application enable key ): Maximum retries exceeded
Getting data for non-table VCP code 0xc7 - Unknown feature:
VCP code 0xc7 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xc8 - Display controller type:
VCP code 0xc8 (Display controller type ): Maximum retries exceeded
Getting data for non-table VCP code 0xc9 - Display firmware level:
VCP code 0xc9 (Display firmware level ): Maximum retries exceeded
Getting data for non-table VCP code 0xca - OSD:
VCP code 0xca (OSD ): Maximum retries exceeded
Getting data for non-table VCP code 0xcb - Unknown feature:
VCP code 0xcb (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xcc - OSD Language:
VCP code 0xcc (OSD Language ): Maximum retries exceeded
Getting data for non-table VCP code 0xcd - Status Indicators:
VCP code 0xcd (Status Indicators ): Maximum retries exceeded
Getting data for non-table VCP code 0xce - Auxiliary display size:
VCP code 0xce (Auxiliary display size ): Maximum retries exceeded
VCP code 0xcf (Auxiliary display data ): Write-only feature
Getting data for non-table VCP code 0xd0 - Output select:
VCP code 0xd0 (Output select ): Maximum retries exceeded
Getting data for non-table VCP code 0xd1 - Unknown feature:
VCP code 0xd1 (Unknown feature ): Maximum retries exceeded
Getting data for table VCP code 0xd2 - Asset Tag:
VCP code 0xd2 (Asset Tag ): Maximum retries exceeded
Getting data for non-table VCP code 0xd3 - Unknown feature:
VCP code 0xd3 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xd4 - Stereo video mode:
VCP code 0xd4 (Stereo video mode ): Maximum retries exceeded
Getting data for non-table VCP code 0xd5 - Unknown feature:
VCP code 0xd5 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xd6 - Power mode:
VCP code 0xd6 (Power mode ): Maximum retries exceeded
Getting data for non-table VCP code 0xd7 - Auxiliary power output:
VCP code 0xd7 (Auxiliary power output ): Maximum retries exceeded
Getting data for non-table VCP code 0xd8 - Unknown feature:
VCP code 0xd8 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xd9 - Unknown feature:
VCP code 0xd9 (Unknown feature ): Maximum retries exceeded
Getting data for non-table VCP code 0xda - Scan format:
VCP code 0xda (Scan format ): Maximum retries exceeded
Getting data for non-table VCP code 0xdb - Image Mode:
VCP code 0xdb (Image Mode ): Maximum retries exceeded
Getting data for non-table VCP code 0xdc - Display Mode:
VCP code 0xdc (Display Mode ): Maximum retries exceeded
Getting data for non-table VCP code 0xdd - Unknown feature:
VCP code 0xdd (Unknown feature ): Maximum retries exceeded
VCP code 0xde (Operation Mode ): Write-only feature
Getting data for non-table VCP code 0xdf - VCP Version:
VCP code 0xdf (VCP Version ): Maximum retries exceeded
Getting data for non-table VCP code 0xe0 - Manufacturer Specific:
VCP code 0xe0 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe0 - Manufacturer Specific:
VCP code 0xe0 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe1 - Manufacturer Specific:
VCP code 0xe1 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe1 - Manufacturer Specific:
VCP code 0xe1 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe2 - Manufacturer Specific:
VCP code 0xe2 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe2 - Manufacturer Specific:
VCP code 0xe2 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe3 - Manufacturer Specific:
VCP code 0xe3 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe3 - Manufacturer Specific:
VCP code 0xe3 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe4 - Manufacturer Specific:
VCP code 0xe4 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe4 - Manufacturer Specific:
VCP code 0xe4 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe5 - Manufacturer Specific:
VCP code 0xe5 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe5 - Manufacturer Specific:
VCP code 0xe5 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe6 - Manufacturer Specific:
VCP code 0xe6 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe6 - Manufacturer Specific:
VCP code 0xe6 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe7 - Manufacturer Specific:
VCP code 0xe7 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe7 - Manufacturer Specific:
VCP code 0xe7 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe8 - Manufacturer Specific:
VCP code 0xe8 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe8 - Manufacturer Specific:
VCP code 0xe8 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xe9 - Manufacturer Specific:
VCP code 0xe9 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xe9 - Manufacturer Specific:
VCP code 0xe9 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xea - Manufacturer Specific:
VCP code 0xea (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xea - Manufacturer Specific:
VCP code 0xea (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xeb - Manufacturer Specific:
VCP code 0xeb (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xeb - Manufacturer Specific:
VCP code 0xeb (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xec - Manufacturer Specific:
VCP code 0xec (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xec - Manufacturer Specific:
VCP code 0xec (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xed - Manufacturer Specific:
VCP code 0xed (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xed - Manufacturer Specific:
VCP code 0xed (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xee - Manufacturer Specific:
VCP code 0xee (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xee - Manufacturer Specific:
VCP code 0xee (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xef - Manufacturer Specific:
VCP code 0xef (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xef - Manufacturer Specific:
VCP code 0xef (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf0 - Manufacturer Specific:
VCP code 0xf0 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf0 - Manufacturer Specific:
VCP code 0xf0 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf1 - Manufacturer Specific:
VCP code 0xf1 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf1 - Manufacturer Specific:
VCP code 0xf1 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf2 - Manufacturer Specific:
VCP code 0xf2 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf2 - Manufacturer Specific:
VCP code 0xf2 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf3 - Manufacturer Specific:
VCP code 0xf3 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf3 - Manufacturer Specific:
VCP code 0xf3 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf4 - Manufacturer Specific:
VCP code 0xf4 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf4 - Manufacturer Specific:
VCP code 0xf4 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf5 - Manufacturer Specific:
VCP code 0xf5 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf5 - Manufacturer Specific:
VCP code 0xf5 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf6 - Manufacturer Specific:
VCP code 0xf6 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf6 - Manufacturer Specific:
VCP code 0xf6 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf7 - Manufacturer Specific:
VCP code 0xf7 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf7 - Manufacturer Specific:
VCP code 0xf7 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf8 - Manufacturer Specific:
VCP code 0xf8 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf8 - Manufacturer Specific:
VCP code 0xf8 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xf9 - Manufacturer Specific:
VCP code 0xf9 (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xf9 - Manufacturer Specific:
VCP code 0xf9 (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xfa - Manufacturer Specific:
VCP code 0xfa (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xfa - Manufacturer Specific:
VCP code 0xfa (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xfb - Manufacturer Specific:
VCP code 0xfb (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xfb - Manufacturer Specific:
VCP code 0xfb (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xfc - Manufacturer Specific:
VCP code 0xfc (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xfc - Manufacturer Specific:
VCP code 0xfc (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xfd - Manufacturer Specific:
VCP code 0xfd (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xfd - Manufacturer Specific:
VCP code 0xfd (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xfe - Manufacturer Specific:
VCP code 0xfe (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xfe - Manufacturer Specific:
VCP code 0xfe (Manufacturer Specific ): Maximum retries exceeded
Getting data for non-table VCP code 0xff - Manufacturer Specific:
VCP code 0xff (Manufacturer Specific ): Maximum retries exceeded
Getting data for table VCP code 0xff - Manufacturer Specific:
VCP code 0xff (Manufacturer Specific ): Maximum retries exceeded
Unable to read or parse capabilities.
Skipping comparison of declared capabilities to observed features
Unable to calculate color temperature from VCP features x0B and x0C
Probing display 2
(ddc_open_display) No EDID for device on bus /dev/i2c-6
Unable to open display bus /dev/i2c-6, status code -3016 (DDCRC_EDID)
Pr
Hi Thomas,
Thanks for the detailed output. It really does look like something odd is going on with the I2C buses on the dock. I strongly suspect the video driver which creates the I2C buses. It would be interesting to see what happens when a monitor is plugged directly into the laptop, both when it's docked and undocked. Another possibility, though not likely, is the monitor. Some monitors are just ill-behaved. I have a Dell P2411 that fails at DDC communication, and testing a second one showed similar problems. So if you have a different model monitor that you can easily plug in, that would be interesting to check as well.
The following commands would give me most of the information I need, without running the full interrogate:
ddcutil detect --verbose ddcutil environment --verbose
(Please send any extensive output as an attachment. It's easier for me to work with.)
It would be interesting to see how other programs behave. The simplest to try get-edid and parse-edid programs in package read-edid.
for i in {0..7}; do get-edid -b $i | parse-edid; done
If your laptop dual boots into Windows, there's are very helpful Windows program for exercising DDC at http://entechtaiwan.com/lib/softmccs.shtm
I'll try adding some more diagnostics in the next point release, but I suspect to really diagnose the issue I'll need to put my hands on a similar system.
Thanks again for your help. I realize that I'm asking you to plug and unplug equipment, which is inconvenient. Whatever you can do would be useful.
Sanford
On 01/16/2017 09:00 PM, Thomas McMahon wrote:
I'll answer the last questions first as this command dump is long.
- Monitors connected to the dock individually, one with display port the other with DVI.
- Don't know - laptop has mini display port. I think I've got one at home so I'll test that.
Here's the dump of |sudo ddcutil interrogate| - it segfaulted so let m eknow if you want me to run again.
|,,, |
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-273002624, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbqw4s0K5S6N44j4Qa0ittuD8AIzeks5rTCC3gaJpZM4LhYdj.
Thomas
ddcutil version 0.7.1 has been released. There's a new option --force-slave-address, which may address your problems of monitor detection. I say "may" because I don't have a test environment that exhibits the behavior you're seeing.
The segfault should also be fixed.
Please run the following commands and send me the output:
ddcutil detect --verbose --force-slave_address --stats ddcutil environment --verbose --force-slave-address --stats
These commands will produce the subset of "ddcutil interrogate" information that is relevant to monitor detection.
Please lease send the output as attachments. It's easier to work with.
Thanks, Sanford
On 01/16/2017 09:00 PM, Thomas McMahon wrote:
I'll answer the last questions first as this command dump is long.
- Monitors connected to the dock individually, one with display port the other with DVI.
- Don't know - laptop has mini display port. I think I've got one at home so I'll test that.
Here's the dump of |sudo ddcutil interrogate| - it segfaulted so let m eknow if you want me to run again.
|Setting output level verbose... Setting maximum retries... Forcing --stats... This command will take a while to run... System information (uname): Linux version 4.8.0-32-generic (buildd@lcy01-34) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016 Primary Check 1: Identify video card and driver Obtaining card and driver information from /sys... Determining driver name and possibly version... Driver name: i915 Unable to determine driver version Video card identification: Vendor: 8086 Intel Corporation Device: 1916 HD Graphics 520 Subvendor/Subdevice: 17aa/504a Lenovo Primary Check 2: Check that /dev/i2c- exist and writable ** 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-rw---- 1 root i2c 89, 0 Jan 12 15:44 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 Jan 12 15:44 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 Jan 12 15:44 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 Jan 12 15:44 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 Jan 12 15:44 /dev/i2c-4 crw-rw---- 1 root i2c 89, 5 Jan 12 15:44 /dev/i2c-5 crw-rw---- 1 root i2c 89, 6 Jan 17 11:18 /dev/i2c-6 crw-rw---- 1 root i2c 89, 7 Jan 17 11:18 /dev/i2c-7 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 grep: /etc/udev/rules.d/rules: No such file or directory Primary Check 3: Check that module i2c_dev is loaded Checking for module i2c_dev... Module i2c_dev is built into kernel Remaining i2c_dev detail is purely informational. Check that kernel module i2c_dev is being loaded by examining files where this would be specified... /etc/modules:i2c-dev /etc/modules-load.d/modules.conf:i2c-dev 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... No driver specific checks apply. Primary Check 5: Installed packages ddcutil requiries package i2c-tools. Use both dpkg and rpm to look for it. While we're at it, check for package libi2c-dev which is used for building ddcutil. Using dpkg to look for package i2c-tools... Package: i2c-tools Status: install ok installed Priority: extra Section: utils Installed-Size: 244 Maintainer: Ubuntu Developers ubuntu-devel-discuss@lists.ubuntu.com Architecture: amd64 Version: 3.1.1-1 Depends: libc6 (>= 2.7), perl, adduser, udev | makedev Recommends: read-edid Suggests: libi2c-dev, python-smbus Conflicts: lm-sensors (<< 1:3.0.0-1) Description: heterogeneous set of I2C tools for Linux This package contains a heterogeneous set of I2C tools for Linux: a bus probing tool, a chip dumper, register-level access helpers, EEPROM decoding scripts, and more. Original-Maintainer: Aurelien Jarno aurel32@debian.org Homepage: http://www.lm-sensors.org /. /usr /usr/share /usr/share/doc /usr/share/doc/i2c-tools /usr/share/doc/i2c-tools/changelog.Debian.gz /usr/share/doc/i2c-tools/copyright /usr/share/man /usr/share/man/man1 /usr/share/man/man1/decode-vaio.1.gz /usr/share/man/man1/decode-dimms.1.gz /usr/share/man/man8 /usr/share/man/man8/i2cset.8.gz /usr/share/man/man8/i2cget.8.gz /usr/share/man/man8/i2cdump.8.gz /usr/share/man/man8/i2c-stub-from-dump.8.gz /usr/share/man/man8/i2cdetect.8.gz /usr/sbin /usr/sbin/i2cset /usr/sbin/i2cget /usr/sbin/i2cdump /usr/sbin/i2c-stub-from-dump /usr/sbin/i2cdetect /usr/bin /usr/bin/ddcmon /usr/bin/decode-edid /usr/bin/decode-vaio /usr/bin/decode-dimms /lib /lib/udev /lib/udev/rules.d /lib/udev/rules.d/40-i2c-tools.rules Using dpkg to look for package libi2c-dev... dpkg-query: package 'libi2c-dev' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libi2c-dev' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Using rpm to look for package i2c-tools... rpm command not found 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: i915 Found other loaded module: i2c_algo_bit Loaded drm module depends on: i915,drm_kms_helper, Loaded video module depends on: thinkpad_acpi,i915, Using lspci to examine driver environment... Video controller: Intel Corporation HD Graphics 520 (rev 07) Testing if modules are loaded using /sys... Module amdgpu is NOT loaded Module fglrx is NOT loaded Module i915 is loaded Module nvidia is NOT loaded Module nouveau is NOT loaded Module radeon is NOT loaded Module vboxvideo is NOT loaded Module i2c_dev is NOT loaded Module i2c_algo_bit is loaded Module i2c_piix4 is NOT loaded Examining /sys/bus/i2c/devices... /sys/bus/i2c/devices/i2c-3/name: DPDDC-A /sys/bus/i2c/devices/i2c-1/name: i915 gmbus dpb /sys/bus/i2c/devices/i2c-6/name: DPMST /sys/bus/i2c/devices/i2c-4/name: DPDDC-B /sys/bus/i2c/devices/i2c-2/name: i915 gmbus dpd /sys/bus/i2c/devices/i2c-0/name: i915 gmbus dpc /sys/bus/i2c/devices/i2c-7/name: DPMST /sys/bus/i2c/devices/i2c-5/name: DPDDC-C Examining i2c buses... Detected I2C buses: Bus /dev/i2c-0 found: true Bus /dev/i2c-0 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-1 found: true Bus /dev/i2c-1 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-2 found: true Bus /dev/i2c-2 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-3 found: true Bus /dev/i2c-3 probed: true Address 0x37 present: true Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK EDID synopsis: Mfg id: AUO Model: Unspecified Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Product code: 0x226d (8813) Extra descriptor: B125HAN02.2 White x,y: 0.306, 0.327 Red x,y: 0.587, 0.350 Green x,y: 0.342, 0.585 Blue x,y: 0.154, 0.115 EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 06 af 6d 22 00 00 00 00 ..........m".... +0010 34 19 01 04 a5 1c 10 78 02 6b a7 96 59 57 95 27 4......x.k..YW.' +0020 1d 4e 53 00 00 00 01 01 01 01 01 01 01 01 01 01 .NS............. +0030 01 01 01 01 01 01 14 37 80 b8 70 38 24 40 10 10 .......7..p8$@.. +0040 3e 00 14 9b 10 00 00 18 00 00 00 0f 00 00 00 00
............... +0050 00 00 00 00 00 00 00 00 00 20 00 00 00 fe 00 41 ......... .....A +0060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe UO. .... +0070 00 42 31 32 35 48 41 4e 30 32 2e 32 20 0a 00 a8 .B125HAN02.2 ... Bus /dev/i2c-4 found: true Bus /dev/i2c-4 probed: true Address 0x37 present: false Address 0x50 present: false Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-5 found: true Bus /dev/i2c-5 probed: true Address 0x37 present: false Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Product code: 0xa07b (41083) Extra descriptor: Unspecified White x,y: 0.313, 0.329 Red x,y: 0.640, 0.330 Green x,y: 0.300, 0.600 Blue x,y: 0.150, 0.060 EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 10 ac 7b a0 4c 56 4b 30 ..........{.LVK0 +0010 35 19 01 04 a5 34 20 78 2a ee 95 a3 54 4c 99 26 5....4 x...TL.& +0020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 .PT....@...@.... +0030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0 +0040 36 00 06 44 21 00 00 1a c8 73 00 a0 f0 b0 23 40 6..D!....s....#@ +0050 30 20 36 00 ff ff 00 00 00 1e 00 00 00 fc 00 44 0 6............D +0060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 27 4a 00 98 ELL U2412M. 'J.. +0070 a1 00 2a 40 30 70 13 00 ff ff 00 00 00 1e 00 07 ..@0p.......... Bus /dev/i2c-6 found: true Bus /dev/i2c-6 probed: true Address 0x37 present: true Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-7 found: true Bus /dev/i2c-7 probed: true Address 0x37 present: true Address 0x50 present: true Bus functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK xrandr connection report: eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 280mm x 160mm DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP2-1 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 520mm x 320mm DP2-2 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 520mm x 320mm DP2-3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) 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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-2 using command "i2cdetect -y 2" 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-3 using command "i2cdetect -y 3" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-4 using command "i2cdetect -y 4" 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-5 using command "i2cdetect -y 5" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-6 using command "i2cdetect -y 6" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-7 using command "i2cdetect -y 7" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- EDIDs reported by X11 for connected xrandr outputs: xrandr output: eDP1 EDID synopsis: Mfg id: AUO Model: Unspecified Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 xrandr output: DP2-1 EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: PPNN15CU0KVL Manufacture year: 2015 EDID version: 1.4 xrandr output: DP2-2 EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: 9W5YH3810DES Manufacture year: 2013 EDID version: 1.3 Probing I2C devices using udev, susbsystem i2c-dev... One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 Device Node Path: /dev/i2c-4 struct udev_device at: 0x55da27a537c0 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 sysname: i2c-4 sysnum: 4 devnode: /dev/i2c-4 Properties: DEVNAME -> /dev/i2c-4 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-4/i2c-dev/i2c-4 MAJOR -> 89 MINOR -> 4 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:4 device -> (null) name -> DPDDC-B subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=4 DEVNAME=i2c-4 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 Device Node Path: /dev/i2c-5 struct udev_device at: 0x55da27a500a0 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 sysname: i2c-5 sysnum: 5 devnode: /dev/i2c-5 Properties: DEVNAME -> /dev/i2c-5 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-5/i2c-dev/i2c-5 MAJOR -> 89 MINOR -> 5 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:5 device -> (null) name -> DPDDC-C subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=5 DEVNAME=i2c-5 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 Device Node Path: /dev/i2c-3 struct udev_device at: 0x55da27a49da0 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 sysname: i2c-3 sysnum: 3 devnode: /dev/i2c-3 Properties: DEVNAME -> /dev/i2c-3 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3/i2c-dev/i2c-3 MAJOR -> 89 MINOR -> 3 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:3 device -> (null) name -> DPDDC-A subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=3 DEVNAME=i2c-3 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0 Device Node Path: /dev/i2c-0 struct udev_device at: 0x55da27a4baf0 devpath: /devices/pci0000:00/0000:00:02.0/i2c-0/i2c-dev/i2c-0 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-0/i2c-dev/i2c-0 MAJOR -> 89 MINOR -> 0 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:0 device -> (null) name -> i915 gmbus dpc subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=0 DEVNAME=i2c-0 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 Device Node Path: /dev/i2c-1 struct udev_device at: 0x55da27a5d340 devpath: /devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-1/i2c-dev/i2c-1 MAJOR -> 89 MINOR -> 1 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:1 device -> (null) name -> i915 gmbus dpb subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=1 DEVNAME=i2c-1 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 Device Node Path: /dev/i2c-2 struct udev_device at: 0x55da27a64f80 devpath: /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 sysname: i2c-2 sysnum: 2 devnode: /dev/i2c-2 Properties: DEVNAME -> /dev/i2c-2 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 MAJOR -> 89 MINOR -> 2 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:2 device -> (null) name -> i915 gmbus dpd subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=2 DEVNAME=i2c-2 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 Device Node Path: /dev/i2c-6 struct udev_device at: 0x55da27a6cc10 devpath: /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 sysname: i2c-6 sysnum: 6 devnode: /dev/i2c-6 Properties: DEVNAME -> /dev/i2c-6 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-6/i2c-dev/i2c-6 MAJOR -> 89 MINOR -> 6 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:6 device -> (null) name -> DPMST subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=6 DEVNAME=i2c-6 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 Device Node Path: /dev/i2c-7 struct udev_device at: 0x55da27a6d950 devpath: /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 sysname: i2c-7 sysnum: 7 devnode: /dev/i2c-7 Properties: DEVNAME -> /dev/i2c-7 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 MAJOR -> 89 MINOR -> 7 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:7 device -> (null) name -> DPMST subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=7 DEVNAME=i2c-7 Checking for USB connected monitors... Using lsusb to summarize USB devices... Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 005: ID 04f2:b52c Chicony Electronics Co., Ltd Bus 001 Device 024: ID 17ef:1010 Lenovo Bus 001 Device 025: ID 17ef:100f Lenovo Bus 001 Device 029: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6 Bus 001 Device 030: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 031: ID 04d9:0167 Holtek Semiconductor, Inc. Bus 001 Device 032: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 17ef:1010 Lenovo USB device toplogy... /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M | Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M | Port 4: Dev 24, If 0, Class=Hub, Driver=hub/4p, 480M | Port 4: Dev 25, If 0, Class=Hub, Driver=hub/3p, 480M | Port 1: Dev 30, If 0, Class=Hub, Driver=hub/4p, 480M | Port 3: Dev 31, If 2, Class=Human Interface Device, Driver=usbhid, 12M | Port 3: Dev 31, If 0, Class=Human Interface Device, Driver=usbhid, 12M | Port 3: Dev 31, If 1, Class=Human Interface Device, Driver=usbhid, 12M | Port 4: Dev 32, If 2, Class=Human Interface Device, Driver=usbhid, 12M | Port 4: Dev 32, If 0, Class=Human Interface Device, Driver=usbhid, 12M | Port 4: Dev 32, If 1, Class=Human Interface Device, Driver=usbhid, 12M | Port 6: Dev 29, If 2, Class=Vendor Specific Class, Driver=ipheth, 480M | Port 6: Dev 29, If 0, Class=Imaging, Driver=, 480M | Port 6: Dev 29, If 1, Class=Vendor Specific Class, Driver=usbfs, 480M | Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M | Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M | Port 8: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M Listing /dev/usb... total 0 crw------- 1 root root 180, 0 Jan 17 11:58 hiddev0 crw------- 1 root root 180, 1 Jan 17 11:58 hiddev1 Listing /dev/hiddev... ls: cannot access '/dev/hiddev': No such file or directory Listing /dev/bus/usb... total 0 drwxr-xr-x 2 root root 220 Jan 17 11:58 001 drwxr-xr-x 2 root root 80 Jan 17 11:18 002 Listing /dev/hidraw*... crw------- 1 root root 244, 0 Jan 17 11:58 /dev/hidraw0 crw------- 1 root root 244, 1 Jan 17 11:58 /dev/hidraw1 crw------- 1 root root 244, 2 Jan 17 11:58 /dev/hidraw2 crw------- 1 root root 244, 3 Jan 17 11:58 /dev/hidraw3 crw------- 1 root root 244, 4 Jan 17 11:58 /dev/hidraw4 Probing USB HID devices using udev, susbsystem usbmisc... One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0 Device Node Path: /dev/usb/hiddev0 struct udev_device at: 0x55da27a7c6d0 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0 subsystem: usbmisc devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0 sysname: hiddev0 sysnum: 0 devnode: /dev/usb/hiddev0 Properties: DEVNAME -> /dev/usb/hiddev0 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/usbmisc/hiddev0 MAJOR -> 180 MINOR -> 0 SUBSYSTEM -> usbmisc Sysattrs: dev -> 180:0 device -> (null) subsystem -> usbmisc uevent -> MAJOR=180 MINOR=0 DEVNAME=usb/hiddev0 Parent device: VID/PID: 04d9 0167 (null) USB-HID Keyboard serial: (null) struct udev_device at: 0x55da27a91e80 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 sysname: 1-4.4.1.3 sysnum: 3 devnode: /dev/bus/usb/001/031 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/031 DEVNUM -> 031 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB-HID_Keyboard ID_MODEL_ENC -> USB-HID\x20Keyboard ID_MODEL_ID -> 0167 ID_REVISION -> 1103 ID_SERIAL -> 04d9_USB-HID_Keyboard ID_USB_INTERFACES -> :030101:030000: ID_VENDOR -> 04d9 ID_VENDOR_ENC -> 04d9 ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc. ID_VENDOR_ID -> 04d9 MAJOR -> 189 MINOR -> 30 PRODUCT -> 4d9/167/1103 SUBSYSTEM -> usb TYPE -> 0/0/0 USEC_INITIALIZED -> 124423894005 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 64 bMaxPower -> 100mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1103 bmAttributes -> a0 busnum -> 1 configuration -> descriptors -> ���� dev -> 189:30 devnum -> 31 devpath -> 4.4.1.3 driver -> usb idProduct -> 0167 idVendor -> 04d9 ltm_capable -> no maxchild -> 0 port -> (null) product -> USB-HID Keyboard quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=30 DEVNAME=bus/usb/001/031 DEVTYPE=usb_device DRIVER=usb PRODUCT=4d9/167/1103 TYPE=0/0/0 BUSNUM=001 DEVNUM=031 urbnum -> 159 version -> 1.10 One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1 Device Node Path: /dev/usb/hiddev1 struct udev_device at: 0x55da27a98590 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1 subsystem: usbmisc devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1 sysname: hiddev1 sysnum: 1 devnode: /dev/usb/hiddev1 Properties: DEVNAME -> /dev/usb/hiddev1 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/usbmisc/hiddev1 MAJOR -> 180 MINOR -> 1 SUBSYSTEM -> usbmisc Sysattrs: dev -> 180:1 device -> (null) subsystem -> usbmisc uevent -> MAJOR=180 MINOR=1 DEVNAME=usb/hiddev1 Parent device: VID/PID: 046d c52b Logitech USB Receiver serial: (null) struct udev_device at: 0x55da27a9bb10 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 sysname: 1-4.4.1.4 sysnum: 4 devnode: /dev/bus/usb/001/032 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/032 DEVNUM -> 032 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB_Receiver ID_MODEL_ENC -> USB\x20Receiver ID_MODEL_FROM_DATABASE -> Unifying Receiver ID_MODEL_ID -> c52b ID_REVISION -> 1203 ID_SERIAL -> Logitech_USB_Receiver ID_USB_INTERFACES -> :030101:030102:030000: ID_VENDOR -> Logitech ID_VENDOR_ENC -> Logitech ID_VENDOR_FROM_DATABASE -> Logitech, Inc. ID_VENDOR_ID -> 046d MAJOR -> 189 MINOR -> 31 PRODUCT -> 46d/c52b/1203 SUBSYSTEM -> usb TYPE -> 0/0/0 UPOWER_VENDOR -> Logitech, Inc. USEC_INITIALIZED -> 124424244636 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 8 bMaxPower -> 98mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1203 bmAttributes -> a0 busnum -> 1 configuration -> RQR12.03_B0025 descriptors -> �� dev -> 189:31 devnum -> 32 devpath -> 4.4.1.4 driver -> usb idProduct -> c52b idVendor -> 046d ltm_capable -> no manufacturer -> Logitech maxchild -> 0 port -> (null) product -> USB Receiver quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=31 DEVNAME=bus/usb/001/032 DEVTYPE=usb_device DRIVER=usb PRODUCT=46d/c52b/1203 TYPE=0/0/0 BUSNUM=001 DEVNUM=032 urbnum -> 2802 version -> 2.00 Probing USB HID devices using udev, susbsystem hidraw... One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0 Device Node Path: /dev/hidraw0 struct udev_device at: 0x55da27a9c0c0 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0 subsystem: hidraw devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0 sysname: hidraw0 sysnum: 0 devnode: /dev/hidraw0 Properties: DEVNAME -> /dev/hidraw0 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.0/0003:04D9:0167.002B/hidraw/hidraw0 MAJOR -> 244 MINOR -> 0 SUBSYSTEM -> hidraw Sysattrs: dev -> 244:0 device -> (null) subsystem -> hidraw uevent -> MAJOR=244 MINOR=0 DEVNAME=hidraw0 Parent device: VID/PID: 04d9 0167 (null) USB-HID Keyboard serial: (null) struct udev_device at: 0x55da27af3fe0 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 sysname: 1-4.4.1.3 sysnum: 3 devnode: /dev/bus/usb/001/031 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/031 DEVNUM -> 031 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB-HID_Keyboard ID_MODEL_ENC -> USB-HID\x20Keyboard ID_MODEL_ID -> 0167 ID_REVISION -> 1103 ID_SERIAL -> 04d9_USB-HID_Keyboard ID_USB_INTERFACES -> :030101:030000: ID_VENDOR -> 04d9 ID_VENDOR_ENC -> 04d9 ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc. ID_VENDOR_ID -> 04d9 MAJOR -> 189 MINOR -> 30 PRODUCT -> 4d9/167/1103 SUBSYSTEM -> usb TYPE -> 0/0/0 USEC_INITIALIZED -> 124423894005 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 64 bMaxPower -> 100mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1103 bmAttributes -> a0 busnum -> 1 configuration -> descriptors -> ���� dev -> 189:30 devnum -> 31 devpath -> 4.4.1.3 driver -> usb idProduct -> 0167 idVendor -> 04d9 ltm_capable -> no maxchild -> 0 port -> (null) product -> USB-HID Keyboard quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=30 DEVNAME=bus/usb/001/031 DEVTYPE=usb_device DRIVER=usb PRODUCT=4d9/167/1103 TYPE=0/0/0 BUSNUM=001 DEVNUM=031 urbnum -> 159 version -> 1.10 One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1 Device Node Path: /dev/hidraw1 struct udev_device at: 0x55da27af3b90 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1 subsystem: hidraw devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1 sysname: hidraw1 sysnum: 1 devnode: /dev/hidraw1 Properties: DEVNAME -> /dev/hidraw1 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.1/0003:04D9:0167.002C/hidraw/hidraw1 MAJOR -> 244 MINOR -> 1 SUBSYSTEM -> hidraw Sysattrs: dev -> 244:1 device -> (null) subsystem -> hidraw uevent -> MAJOR=244 MINOR=1 DEVNAME=hidraw1 Parent device: VID/PID: 04d9 0167 (null) USB-HID Keyboard serial: (null) struct udev_device at: 0x55da27b5f330 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 sysname: 1-4.4.1.3 sysnum: 3 devnode: /dev/bus/usb/001/031 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/031 DEVNUM -> 031 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB-HID_Keyboard ID_MODEL_ENC -> USB-HID\x20Keyboard ID_MODEL_ID -> 0167 ID_REVISION -> 1103 ID_SERIAL -> 04d9_USB-HID_Keyboard ID_USB_INTERFACES -> :030101:030000: ID_VENDOR -> 04d9 ID_VENDOR_ENC -> 04d9 ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc. ID_VENDOR_ID -> 04d9 MAJOR -> 189 MINOR -> 30 PRODUCT -> 4d9/167/1103 SUBSYSTEM -> usb TYPE -> 0/0/0 USEC_INITIALIZED -> 124423894005 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 64 bMaxPower -> 100mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1103 bmAttributes -> a0 busnum -> 1 configuration -> descriptors -> ���� dev -> 189:30 devnum -> 31 devpath -> 4.4.1.3 driver -> usb idProduct -> 0167 idVendor -> 04d9 ltm_capable -> no maxchild -> 0 port -> (null) product -> USB-HID Keyboard quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=30 DEVNAME=bus/usb/001/031 DEVTYPE=usb_device DRIVER=usb PRODUCT=4d9/167/1103 TYPE=0/0/0 BUSNUM=001 DEVNUM=031 urbnum -> 159 version -> 1.10 One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2 Device Node Path: /dev/hidraw2 struct udev_device at: 0x55da27b5f330 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2 subsystem: hidraw devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2 sysname: hidraw2 sysnum: 2 devnode: /dev/hidraw2 Properties: DEVNAME -> /dev/hidraw2 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3/1-4.4.1.3:1.2/0003:04D9:0167.002D/hidraw/hidraw2 MAJOR -> 244 MINOR -> 2 SUBSYSTEM -> hidraw Sysattrs: dev -> 244:2 device -> (null) subsystem -> hidraw uevent -> MAJOR=244 MINOR=2 DEVNAME=hidraw2 Parent device: VID/PID: 04d9 0167 (null) USB-HID Keyboard serial: (null) struct udev_device at: 0x55da27bc0620 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 sysname: 1-4.4.1.3 sysnum: 3 devnode: /dev/bus/usb/001/031 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/031 DEVNUM -> 031 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.3 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB-HID_Keyboard ID_MODEL_ENC -> USB-HID\x20Keyboard ID_MODEL_ID -> 0167 ID_REVISION -> 1103 ID_SERIAL -> 04d9_USB-HID_Keyboard ID_USB_INTERFACES -> :030101:030000: ID_VENDOR -> 04d9 ID_VENDOR_ENC -> 04d9 ID_VENDOR_FROM_DATABASE -> Holtek Semiconductor, Inc. ID_VENDOR_ID -> 04d9 MAJOR -> 189 MINOR -> 30 PRODUCT -> 4d9/167/1103 SUBSYSTEM -> usb TYPE -> 0/0/0 USEC_INITIALIZED -> 124423894005 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 64 bMaxPower -> 100mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1103 bmAttributes -> a0 busnum -> 1 configuration -> descriptors -> ���� dev -> 189:30 devnum -> 31 devpath -> 4.4.1.3 driver -> usb idProduct -> 0167 idVendor -> 04d9 ltm_capable -> no maxchild -> 0 port -> (null) product -> USB-HID Keyboard quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=30 DEVNAME=bus/usb/001/031 DEVTYPE=usb_device DRIVER=usb PRODUCT=4d9/167/1103 TYPE=0/0/0 BUSNUM=001 DEVNUM=031 urbnum -> 159 version -> 1.10 One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4 Device Node Path: /dev/hidraw4 struct udev_device at: 0x55da27bc0620 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4 subsystem: hidraw devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4 sysname: hidraw4 sysnum: 4 devnode: /dev/hidraw4 Properties: DEVNAME -> /dev/hidraw4 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/0003:046D:402D.0031/hidraw/hidraw4 MAJOR -> 244 MINOR -> 4 SUBSYSTEM -> hidraw Sysattrs: dev -> 244:4 device -> (null) subsystem -> hidraw uevent -> MAJOR=244 MINOR=4 DEVNAME=hidraw4 Parent device: VID/PID: 046d c52b Logitech USB Receiver serial: (null) struct udev_device at: 0x55da27c1aa60 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 sysname: 1-4.4.1.4 sysnum: 4 devnode: /dev/bus/usb/001/032 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/032 DEVNUM -> 032 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB_Receiver ID_MODEL_ENC -> USB\x20Receiver ID_MODEL_FROM_DATABASE -> Unifying Receiver ID_MODEL_ID -> c52b ID_REVISION -> 1203 ID_SERIAL -> Logitech_USB_Receiver ID_USB_INTERFACES -> :030101:030102:030000: ID_VENDOR -> Logitech ID_VENDOR_ENC -> Logitech ID_VENDOR_FROM_DATABASE -> Logitech, Inc. ID_VENDOR_ID -> 046d MAJOR -> 189 MINOR -> 31 PRODUCT -> 46d/c52b/1203 SUBSYSTEM -> usb TYPE -> 0/0/0 UPOWER_VENDOR -> Logitech, Inc. USEC_INITIALIZED -> 124424244636 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 8 bMaxPower -> 98mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1203 bmAttributes -> a0 busnum -> 1 configuration -> RQR12.03_B0025 descriptors -> �� dev -> 189:31 devnum -> 32 devpath -> 4.4.1.4 driver -> usb idProduct -> c52b idVendor -> 046d ltm_capable -> no manufacturer -> Logitech maxchild -> 0 port -> (null) product -> USB Receiver quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=31 DEVNAME=bus/usb/001/032 DEVTYPE=usb_device DRIVER=usb PRODUCT=46d/c52b/1203 TYPE=0/0/0 BUSNUM=001 DEVNUM=032 urbnum -> 2802 version -> 2.00 One Device path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3 Device Node Path: /dev/hidraw3 struct udev_device at: 0x55da27c1aa60 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3 subsystem: hidraw devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3 sysname: hidraw3 sysnum: 3 devnode: /dev/hidraw3 Properties: DEVNAME -> /dev/hidraw3 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4/1-4.4.1.4:1.2/0003:046D:C52B.0030/hidraw/hidraw3 MAJOR -> 244 MINOR -> 3 SUBSYSTEM -> hidraw Sysattrs: dev -> 244:3 device -> (null) subsystem -> hidraw uevent -> MAJOR=244 MINOR=3 DEVNAME=hidraw3 Parent device: VID/PID: 046d c52b Logitech USB Receiver serial: (null) struct udev_device at: 0x55da27ccbf80 devpath: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 subsystem: usb devtype: usb_device syspath: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 sysname: 1-4.4.1.4 sysnum: 4 devnode: /dev/bus/usb/001/032 Properties: BUSNUM -> 001 DEVNAME -> /dev/bus/usb/001/032 DEVNUM -> 032 DEVPATH -> /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1.4 DEVTYPE -> usb_device DRIVER -> usb ID_BUS -> usb ID_MODEL -> USB_Receiver ID_MODEL_ENC -> USB\x20Receiver ID_MODEL_FROM_DATABASE -> Unifying Receiver ID_MODEL_ID -> c52b ID_REVISION -> 1203 ID_SERIAL -> Logitech_USB_Receiver ID_USB_INTERFACES -> :030101:030102:030000: ID_VENDOR -> Logitech ID_VENDOR_ENC -> Logitech ID_VENDOR_FROM_DATABASE -> Logitech, Inc. ID_VENDOR_ID -> 046d MAJOR -> 189 MINOR -> 31 PRODUCT -> 46d/c52b/1203 SUBSYSTEM -> usb TYPE -> 0/0/0 UPOWER_VENDOR -> Logitech, Inc. USEC_INITIALIZED -> 124424244636 Sysattrs: authorized -> 1 avoid_reset_quirk -> 0 bConfigurationValue -> 1 bDeviceClass -> 00 bDeviceProtocol -> 00 bDeviceSubClass -> 00 bMaxPacketSize0 -> 8 bMaxPower -> 98mA bNumConfigurations -> 1 bNumInterfaces -> 3 bcdDevice -> 1203 bmAttributes -> a0 busnum -> 1 configuration -> RQR12.03_B0025 descriptors -> �� dev -> 189:31 devnum -> 32 devpath -> 4.4.1.4 driver -> usb idProduct -> c52b idVendor -> 046d ltm_capable -> no manufacturer -> Logitech maxchild -> 0 port -> (null) product -> USB Receiver quirks -> 0x0 removable -> unknown speed -> 12 subsystem -> usb uevent -> MAJOR=189 MINOR=31 DEVNAME=bus/usb/001/032 DEVTYPE=usb_device DRIVER=usb PRODUCT=46d/c52b/1203 TYPE=0/0/0 BUSNUM=001 DEVNUM=032 urbnum -> 2802 version -> 2.00 Probing possible HID monitors using libusb... (possible_monitor_config_descriptor) Examining only interface 0 for device 1:5, vid=0x04f2, pid=0xb52c Chicony Electronics Co., Ltd (null) (possible_monitor_config_descriptor) Examining only interface 0 for device 1:3, vid=0x8087, pid=0x0a2b Intel Corp. (null) (possible_monitor_config_descriptor) Examining only interface 0 for device 1:32, vid=0x046d, pid=0xc52b Logitech, Inc. Unifying Receiver (possible_monitor_config_descriptor) Examining only interface 0 for device 1:31, vid=0x04d9, pid=0x0167 Holtek Semiconductor, Inc. (null) Checking for USB connected monitors on /dev/hidraw* ... Found 5 USB HID devices. Probing device /dev/hidraw0 Raw Name: USB-HID Keyboard Raw Phys: usb-0000:00:14.0-4.4.1.3/input0 Raw Info: bustype: 3 (USB) vendor: 0x04d9 product: 0x0167 Busno:Devno as reported by get_udev_usb_devinfo() for hidraw0: 001:031 Not a USB connected monitor Probing device /dev/hidraw1 Raw Name: USB-HID Keyboard Raw Phys: usb-0000:00:14.0-4.4.1.3/input1 Raw Info: bustype: 3 (USB) vendor: 0x04d9 product: 0x0167 Busno:Devno as reported by get_udev_usb_devinfo() for hidraw1: 001:031 Not a USB connected monitor Probing device /dev/hidraw2 Raw Name: USB-HID Keyboard Raw Phys: usb-0000:00:14.0-4.4.1.3/input2 Raw Info: bustype: 3 (USB) vendor: 0x04d9 product: 0x0167 Busno:Devno as reported by get_udev_usb_devinfo() for hidraw2: 001:031 Not a USB connected monitor Probing device /dev/hidraw3 Raw Name: Logitech USB Receiver Raw Phys: usb-0000:00:14.0-4.4.1.4/input2 Raw Info: bustype: 3 (USB) vendor: 0x046d product: 0xc52b Busno:Devno as reported by get_udev_usb_devinfo() for hidraw3: 001:032 Not a USB connected monitor Probing device /dev/hidraw4 Raw Name: Logitech M560 Raw Phys: usb-0000:00:14.0-4.4.1.4:1 Raw Info: bustype: 3 (USB) vendor: 0x046d product: 0x402d Busno:Devno as reported by get_udev_usb_devinfo() for hidraw4: 001:032 Not a USB connected monitor Checking for USB HID devices using hiddev... Found 2 USB HID devices. Device /dev/usb/hiddev0, devnum.busnum: 1.31, vid:pid: 04d9:0167 - USB-HID Keyboard Not a USB HID monitor Device /dev/usb/hiddev1, devnum.busnum: 1.32, vid:pid: 046d:c52b - Logitech USB Receiver Not a USB HID monitor Checking for USB HID Report Descriptors in /sys/kernel/debug/hid... Detected Displays Display 1 I2C bus: /dev/i2c-3 Supports DDC: true I2C address 0x37 (DDC) present: true I2C address 0x50 (EDID) present: true EDID synopsis: Mfg id: AUO Model: Unspecified Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Product code: 0x226d (8813) Extra descriptor: B125HAN02.2 White x,y: 0.306, 0.327 Red x,y: 0.587, 0.350 Green x,y: 0.342, 0.585 Blue x,y: 0.154, 0.115 EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 06 af 6d 22 00 00 00 00 ..........m".... +0010 34 19 01 04 a5 1c 10 78 02 6b a7 96 59 57 95 27 4......x.k..YW.' +0020 1d 4e 53 00 00 00 01 01 01 01 01 01 01 01 01 01 .NS............. +0030 01 01 01 01 01 01 14 37 80 b8 70 38 24 40 10 10 .......7..p8$@.. +0040 3e 00 14 9b 10 00 00 18 00 00 00 0f 00 00 00 00 >............... +0050 00 00 00 00 00 00 00 00 00 20 00 00 00 fe 00 41 ......... .....A +0060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe UO. .... +0070 00 42 31 32 35 48 41 4e 30 32 2e 32 20 0a 00 a8 .B125HAN02.2 ... VCP version: Detection failed (ddc_report_active_display) get_nontable_vcp_value(0xc8) returned DDCRC_RETRIES(-3015): maximum retries exceeded Controller mfg: Unspecified (ddc_report_active_display) get_vcp_value(0xc9) returned DDCRC_RETRIES(-3015): maximum retries exceeded Firmware version: Unspecified Invalid display I2C bus: /dev/i2c-5 Supports DDC: false I2C address 0x37 (DDC) present: false I2C address 0x50 (EDID) present: true EDID synopsis: Mfg id: DEL Model: DELL U2412M Serial number: Unspecified Manufacture year: 2015 EDID version: 1.4 Product code: 0xa07b (41083) Extra descriptor: Unspecified White x,y: 0.313, 0.329 Red x,y: 0.640, 0.330 Green x,y: 0.300, 0.600 Blue x,y: 0.150, 0.060 EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 10 ac 7b a0 4c 56 4b 30 ..........{.LVK0 +0010 35 19 01 04 a5 34 20 78 2a ee 95 a3 54 4c 99 26 5....4 x...TL.& +0020 0f 50 54 a1 08 00 81 40 81 80 a9 40 b3 00 d1 c0 .PT....@...@.... +0030 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0 +0040 36 00 06 44 21 00 00 1a c8 73 00 a0 f0 b0 23 40 6..D!....s....#@ +0050 30 20 36 00 ff ff 00 00 00 1e 00 00 00 fc 00 44 0 6............D +0060 45 4c 4c 20 55 32 34 31 32 4d 0a 20 27 4a 00 98 ELL U2412M. 'J.. +0070 a1 00 2a 40 30 70 13 00 ff ff 00 00 00 1e 00 07 ..@0p.......... Display 2 I2C bus: /dev/i2c-6 Supports DDC: true I2C address 0x37 (DDC) present: true I2C address 0x50 (EDID) present: true (ddc_open_display) No EDID for device on bus /dev/i2c-6 Error opening display bus /dev/i2c-6, error = -3016 (DDCRC_EDID) (ddc_close_display) close_i2c_bus returned 9 Display 3 I2C bus: /dev/i2c-7 Supports DDC: true I2C address 0x37 (DDC) present: true I2C address 0x50 (EDID) present: true (ddc_open_display) No EDID for device on bus /dev/i2c-7 Error opening display bus /dev/i2c-7, error = -3016 (DDCRC_EDID) (ddc_close_display) close_i2c_bus returned 9 Probing display 1 Capabilities for display Display_Handle[i2c: fh=3, busno=3] Unable to get capabilities for monitor on Display_Handle[i2c: fh=3, busno=3]. Maximum DDC retries exceeded. May support table reads: true Scanning all VCP feature codes for display Display_Handle[i2c: fh=3, busno=3] Getting data for non-table VCP code 0x00 - Unknown feature: VCP code 0x00 (Unknown feature ): Maximum retries exceeded VCP code 0x01 (Degauss ): Write-only feature Getting data for non-table VCP code 0x02 - New control value: VCP code 0x02 (New control value ): Maximum retries exceeded Getting data for non-table VCP code 0x03 - Soft controls: VCP code 0x03 (Soft controls ): Maximum retries exceeded VCP code 0x04 (Restore factory defaults ): Write-only feature VCP code 0x05 (Restore factory brightness/contrast defaults): Write-only feature VCP code 0x06 (Restore factory geometry defaults): Write-only feature Getting data for non-table VCP code 0x07 - Unknown feature: VCP code 0x07 (Unknown feature ): Maximum retries exceeded VCP code 0x08 (Restore color defaults ): Write-only feature Getting data for non-table VCP code 0x09 - Unknown feature: VCP code 0x09 (Unknown feature ): Maximum retries exceeded VCP code 0x0a (Restore factory TV defaults ): Write-only feature Getting data for non-table VCP code 0x0b - Color temperature increment: VCP code 0x0b (Color temperature increment ): Maximum retries exceeded Getting data for non-table VCP code 0x0c - Color temperature request: VCP code 0x0c (Color temperature request ): Maximum retries exceeded Getting data for non-table VCP code 0x0d - Unknown feature: VCP code 0x0d (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x0e - Clock: VCP code 0x0e (Clock ): Maximum retries exceeded Getting data for non-table VCP code 0x0f - Unknown feature: VCP code 0x0f (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x10 - Brightness: VCP code 0x10 (Brightness ): Maximum retries exceeded Getting data for non-table VCP code 0x11 - Flesh tone enhancement: VCP code 0x11 (Flesh tone enhancement ): Maximum retries exceeded Getting data for non-table VCP code 0x12 - Contrast: VCP code 0x12 (Contrast ): Maximum retries exceeded Getting data for non-table VCP code 0x13 - Backlight control: VCP code 0x13 (Backlight control ): Maximum retries exceeded Getting data for non-table VCP code 0x14 - Select color preset: VCP code 0x14 (Select color preset ): Maximum retries exceeded Getting data for non-table VCP code 0x15 - Unknown feature: VCP code 0x15 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x16 - Video gain: Red: VCP code 0x16 (Video gain: Red ): Maximum retries exceeded Getting data for non-table VCP code 0x17 - User color vision compensation: VCP code 0x17 (User color vision compensation): Maximum retries exceeded Getting data for non-table VCP code 0x18 - Video gain: Green: VCP code 0x18 (Video gain: Green ): Maximum retries exceeded Getting data for non-table VCP code 0x19 - Unknown feature: VCP code 0x19 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x1a - Video gain: Blue: VCP code 0x1a (Video gain: Blue ): Maximum retries exceeded Getting data for non-table VCP code 0x1b - Unknown feature: VCP code 0x1b (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x1c - Focus: VCP code 0x1c (Focus ): Maximum retries exceeded Getting data for non-table VCP code 0x1d - Unknown feature: VCP code 0x1d (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x1e - Auto setup: VCP code 0x1e (Auto setup ): Maximum retries exceeded Getting data for non-table VCP code 0x1f - Auto color setup: VCP code 0x1f (Auto color setup ): Maximum retries exceeded Getting data for non-table VCP code 0x20 - Horizontal Position: VCP code 0x20 (Horizontal Position ): Maximum retries exceeded Getting data for non-table VCP code 0x21 - Unknown feature: VCP code 0x21 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x22 - Horizontal Size: VCP code 0x22 (Horizontal Size ): Maximum retries exceeded Getting data for non-table VCP code 0x23 - Unknown feature: VCP code 0x23 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x24 - Horizontal Pincushion: VCP code 0x24 (Horizontal Pincushion ): Maximum retries exceeded Getting data for non-table VCP code 0x25 - Unknown feature: VCP code 0x25 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x26 - Horizontal Pincushion Balance: VCP code 0x26 (Horizontal Pincushion Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x27 - Unknown feature: VCP code 0x27 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x28 - Horizontal Convergence: VCP code 0x28 (Horizontal Convergence ): Maximum retries exceeded Getting data for non-table VCP code 0x29 - Horizontal Convergence M/G: VCP code 0x29 (Horizontal Convergence M/G ): Maximum retries exceeded Getting data for non-table VCP code 0x2a - Horizontal Linearity: VCP code 0x2a (Horizontal Linearity ): Maximum retries exceeded Getting data for non-table VCP code 0x2b - Unknown feature: VCP code 0x2b (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x2c - Horizontal Linearity Balance: VCP code 0x2c (Horizontal Linearity Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x2d - Unknown feature: VCP code 0x2d (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x2e - Gray scale expansion: VCP code 0x2e (Gray scale expansion ): Maximum retries exceeded Getting data for non-table VCP code 0x2f - Unknown feature: VCP code 0x2f (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x30 - Vertical Position: VCP code 0x30 (Vertical Position ): Maximum retries exceeded Getting data for non-table VCP code 0x31 - Unknown feature: VCP code 0x31 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x32 - Vertical Size: VCP code 0x32 (Vertical Size ): Maximum retries exceeded Getting data for non-table VCP code 0x33 - Unknown feature: VCP code 0x33 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x34 - Vertical Pincushion: VCP code 0x34 (Vertical Pincushion ): Maximum retries exceeded Getting data for non-table VCP code 0x35 - Unknown feature: VCP code 0x35 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x36 - Vertical Pincushion Balance: VCP code 0x36 (Vertical Pincushion Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x37 - Unknown feature: VCP code 0x37 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x38 - Vertical Convergence: VCP code 0x38 (Vertical Convergence ): Maximum retries exceeded Getting data for non-table VCP code 0x39 - Vertical Convergence M/G: VCP code 0x39 (Vertical Convergence M/G ): Maximum retries exceeded Getting data for non-table VCP code 0x3a - Vertical Linearity: VCP code 0x3a (Vertical Linearity ): Maximum retries exceeded Getting data for non-table VCP code 0x3b - Unknown feature: VCP code 0x3b (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x3c - Vertical Linearity Balance: VCP code 0x3c (Vertical Linearity Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x3d - Unknown feature: VCP code 0x3d (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x3e - Clock phase: VCP code 0x3e (Clock phase ): Maximum retries exceeded Getting data for non-table VCP code 0x3f - Unknown feature: VCP code 0x3f (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x40 - Key Balance: VCP code 0x40 (Key Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x41 - Vertical Parallelogram: VCP code 0x41 (Vertical Parallelogram ): Maximum retries exceeded Getting data for non-table VCP code 0x42 - Horizontal Trapezoid: VCP code 0x42 (Horizontal Trapezoid ): Maximum retries exceeded Getting data for non-table VCP code 0x43 - Vertical Trapezoid: VCP code 0x43 (Vertical Trapezoid ): Maximum retries exceeded Getting data for non-table VCP code 0x44 - Tilt (rotation): VCP code 0x44 (Tilt (rotation) ): Maximum retries exceeded Getting data for non-table VCP code 0x45 - Unknown feature: VCP code 0x45 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x46 - Top Corner: VCP code 0x46 (Top Corner ): Maximum retries exceeded Getting data for non-table VCP code 0x47 - Unknown feature: VCP code 0x47 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x48 - Top Corner Balance: VCP code 0x48 (Top Corner Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x49 - Unknown feature: VCP code 0x49 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x4a - Bottom Corner: VCP code 0x4a (Bottom Corner ): Maximum retries exceeded Getting data for non-table VCP code 0x4b - Unknown feature: VCP code 0x4b (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x4c - Bottom Corner Balance: VCP code 0x4c (Bottom Corner Balance ): Maximum retries exceeded Getting data for non-table VCP code 0x4d - Unknown feature: VCP code 0x4d (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x4e - Unknown feature: VCP code 0x4e (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x4f - Unknown feature: VCP code 0x4f (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x50 - Unknown feature: VCP code 0x50 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x51 - Unknown feature: VCP code 0x51 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x52 - Active control: VCP code 0x52 (Active control ): Maximum retries exceeded Getting data for non-table VCP code 0x53 - Unknown feature: VCP code 0x53 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x54 - Performance Preservation: VCP code 0x54 (Performance Preservation ): Maximum retries exceeded Getting data for non-table VCP code 0x55 - Unknown feature: VCP code 0x55 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x56 - Horizontal Moire: VCP code 0x56 (Horizontal Moire ): Maximum retries exceeded Getting data for non-table VCP code 0x57 - Unknown feature: VCP code 0x57 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x58 - Vertical Moire: VCP code 0x58 (Vertical Moire ): Maximum retries exceeded Getting data for non-table VCP code 0x59 - 6 axis saturation: Red: VCP code 0x59 (6 axis saturation: Red ): Maximum retries exceeded Getting data for non-table VCP code 0x5a - 6 axis saturation: Yellow: VCP code 0x5a (6 axis saturation: Yellow ): Maximum retries exceeded Getting data for non-table VCP code 0x5b - 6 axis saturation: Green: VCP code 0x5b (6 axis saturation: Green ): Maximum retries exceeded Getting data for non-table VCP code 0x5c - 6 axis saturation: Cyan: VCP code 0x5c (6 axis saturation: Cyan ): Maximum retries exceeded Getting data for non-table VCP code 0x5d - 6 axis saturation: Blue: VCP code 0x5d (6 axis saturation: Blue ): Maximum retries exceeded Getting data for non-table VCP code 0x5e - 6 axis saturation: Magenta: VCP code 0x5e (6 axis saturation: Magenta ): Maximum retries exceeded Getting data for non-table VCP code 0x5f - Unknown feature: VCP code 0x5f (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x60 - Input Source: VCP code 0x60 (Input Source ): Maximum retries exceeded Getting data for non-table VCP code 0x61 - Unknown feature: VCP code 0x61 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x62 - Audio speaker volume: VCP code 0x62 (Audio speaker volume ): Maximum retries exceeded Getting data for non-table VCP code 0x63 - Speaker Select: VCP code 0x63 (Speaker Select ): Maximum retries exceeded Getting data for non-table VCP code 0x64 - Audio: Microphone Volume: VCP code 0x64 (Audio: Microphone Volume ): Maximum retries exceeded Getting data for non-table VCP code 0x65 - Unknown feature: VCP code 0x65 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x66 - Ambient light sensor: VCP code 0x66 (Ambient light sensor ): Maximum retries exceeded Getting data for non-table VCP code 0x67 - Unknown feature: VCP code 0x67 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x68 - Unknown feature: VCP code 0x68 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x69 - Unknown feature: VCP code 0x69 (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x6a - Unknown feature: VCP code 0x6a (Unknown feature ): Maximum retries exceeded Getting data for non-table VCP code 0x6b - Backlight Level: White: VCP code 0x6b (Backlight Level: White ): Maximum retries exceeded Getting data for non-table VCP code 0x6c - Video black level: Red: VCP code 0x6c (Video black level: Red ): Maximum retries exceeded Getting data for non-table VCP code 0x6d - Backlight Level: Red: VCP code 0x6d (Backlight Level: Red ): Maximum retries exceeded Getting data for non-table VCP code 0x6e - Video black level: Green: VCP code 0x6e (Video black level: Green ): Maximum retries exceeded Getting data for non-table VCP code 0x6f - Backlight Level: Green: VCP code 0x6f (Backlight Level: Green ): Maximum retries exceeded Getting data for non-table VCP code 0x70 - Video black level: Blue: VCP cod
OK I've install 0.7.2
sudo ddcutil detect --verbose --force-slave-address --stats > ddcutil1.txt
sudo ddcutil environment --verbose --force-slave-address --stats > ddcutil2.txt
Thomas,
Thanks for taking the trouble to create the reports.
First, to state the obvious, --force-slave-address has no effect on your situation. If the failure mode addressed by --force-slave-address had occurred, there would have been traces in the logs.
The enhanced environment code in 0.7.2 is consistent with earlier conjectures. The problem is most likely in one of these places:
Interestingly, the (enhanced) environment log shows an errno status code on /dev/i2c-5 never before seen: EREMOTEIO. This appears to be coming from the i2c-over-aux code in the driver. (file gpu/drm/drm_dp_helper.c or gpu/drm/drm_dp_mst_topology.c)
So I'm afraid all I can suggest is testing if hardware changes have any effect:
There's one other peculiarity I see in the logs, though I don't think it's related to your problem. The monitor EDIDs for the U2142Ms read directly by ddcutil over I2c do not quite match those reported by xrandr. In particular, the former do not contain a string serial number, the latter do. I have a few conjectures as to why this might be the case, and have added code to the environment command that will be included in the next point release.
Regards, Sanford
On 02/02/2017 12:21 AM, Thomas McMahon wrote:
OK I've install 0.7.2
|sudo ddcutil detect --verbose --force-slave-address --stats > ddcutil1.txt|
ddcutil1.txt https://github.com/rockowitz/ddcutil/files/746876/ddcutil1.txt
|sudo ddcutil environment --verbose --force-slave-address --stats > ddcutil2.txt|
ddcutil2.txt https://github.com/rockowitz/ddcutil/files/746877/ddcutil2.txt
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-276871183, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbj4mP3EKdPBaol9RPNYy9yTmoxVGks5rYWfcgaJpZM4LhYdj.
I have a new Dell TB16 (thunderbolt) dock that seems to be interfering with DDC to my monitor as well.
I used to use a script with ddccontrol in it to change the brightness on my directly-connected monitor. With the dock in between, it no longer works. Read about ddcutil, then installed it, but it doesn't seem to be able to talk to it either through the dock.
ddcutil environment --verbose > ddc_environment.txt
ddcutil detect --verbose > ddc_detect.txt
Perhaps these can shed some light, however I suspect the problem is with the dock, firmware, or drivers themselves.
Thanks for the report. Yes, it does seem to be another case of I2C passthrough on a dock not working. All the other reports have been for Lenovo Thinkpad docks, so it looks like the problem is more general. Common to all these cases is the i915 Intel video driver.
Looks like you're connecting the monitor to the dock via DisplayPort. Have you tried DVI, HDMI, or (gasp) VGA? One person was able to work around the problem by having both IIRC DisplayPort and VGA connections to the monitor. He sets the monitor input to the DisplayPort connection. Surprisingly, the monitor is nonetheless response to I2C/DDC communication on the VGA connection.
Sanford
On 05/03/2017 08:19 PM, mixmastamyk wrote:
I have a new Dell TB16 (thunderbolt) dock that seems to be interfering with DDC to my monitor as well.
I used to use a script with ddccontrol in it to change the brightness on my directly-connected monitor. With the dock in between, it no longer works. Read about ddcutil, then installed it, but it doesn't seem to be able to talk to it either through the dock.
|ddcutil environment --verbose > ddc_environment.txt|
ddc_environment.txt https://github.com/rockowitz/ddcutil/files/974988/ddc_environment.txt
|ddcutil detect --verbose > ddc_detect.txt| ddc_detect.txt https://github.com/rockowitz/ddcutil/files/974989/ddc_detect.txt
Perhaps these can shed some light, however I suspect the problem is with the dock, firmware, or drivers themselves.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299070791, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsblmIAQLkhnKwP0el097CkpaXRqJyks5r2RmogaJpZM4LhYdj.
I looked a the specs for the dock and it seemed to have all the connections.
Sanford
On 05/04/2017 12:04 PM, mixmastamyk wrote:
Good to know, thanks.
The laptop has an HDMI port so I could use it, but I don't have a cable handy, and not sure it supports 4k @ 60hz. Also, the reason I bought this dock in the first place was to get rid of all these cables crossing my desk, and replacing it with one. Connecting directly defeats 50% of the reason for the purchase, sigh.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299231429, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbkn8UAbZGslgc0ESjLTn9oMJRoY_ks5r2fcHgaJpZM4LhYdj.
As as been discussed, there seems to be a pattern of I2C communication failing with docking stations and the i915 driver. It's not particularly useful for me to file a vague bug report with the i2c folks, but if I can identify a pattern, .e.g. the problem is associated with certain recent processors, that may be more useful. Please run "ddcutil interrogate" as root and send me the output as a file.
Sanford
On 05/04/2017 12:43 PM, mixmastamyk wrote:
Hah, just remembered my daughter's kano computer came with an unused HDMI cable, so plugged it in and it works as an extra channel to communicate! Big, bright yellow Fischer-Price cable sticking out of my "professional" black laptop, haha.
Still curious if a video driver could interfere with I2C/DDC?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299242106, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbv7HZOb_pMDN0gZDQ5BHmi2mGqiOks5r2gA1gaJpZM4LhYdj.
Was that the whole output? The file ends abruptly at line 2338 in the middle of a report. You might try sending it as an attachment.
Also, what is your processor. The video VID/PID is 8086/591B, which appears to be in the Intel graphics range, but isn't in the PID database, and I can't find the number anywhere online. Must be very new.
Sanford
On 05/04/2017 03:02 PM, mixmastamyk wrote:
Ok. ddc_interrogate.txt https://github.com/rockowitz/ddcutil/files/977270/ddc_interrogate.txt
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299278833, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbiA4StojOMr-_CzVIO9Sqvo3Lj5-ks5r2iCqgaJpZM4LhYdj.
I think so. I did run it again and got this:
Job 2, “ddcutil interrogate > ddc_inter…” terminated by signal SIGSEGV (Address boundary error)
Laptop is brand new, but has been around since January I think.
Intel(R) Core(TM) i5-7440HQ CPU @ 2.80GHz
https://ark.intel.com/products/97459/Intel-Core-i5-7440HQ-Processor-6M-Cache-up-to-3_80-GHz
Can you send what was written to ddcinter? Where it ends would narrow down where the fault is.
Even better, can you run it under valgrind? i.e. "valgrind ddcutil interrogate"
Alternatively, "ddcutil interrogate" is essentially a combination of the following commands. Which of the these fail? And where?
ddcutil detect --verbose ddcutil environment --verbose ddcutil usbenvironment --verbose and, for each valid display number N: ddcutil probe --display N probe
Thanks. I regard this as serious. Configuration issues go with the territory for ddcutil. It's in the nature of I2C. But segfaults are my doing.
Sanford
On 05/04/2017 10:54 PM, mixmastamyk wrote:
I think so. I did run it again and got this:
|Job 2, “ddcutil interrogate > ddc_inter…” terminated by signal SIGSEGV (Address boundary error) |
Laptop is brand new, but has been around since January I think.
|Intel(R) Core(TM) i5-7440HQ CPU @ 2.80GHz |
https://ark.intel.com/products/97459/Intel-Core-i5-7440HQ-Processor-6M-Cache-up-to-3_80-GHz
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299358827, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbsEiH7td8471hX69flYHNss7vtkfks5r2o9MgaJpZM4LhYdj.
See bug #21 .
Re the original problem before we got distracted by the segfault, here's a (still incomplete)l exchange today with someone on the i915 team:
https://lists.freedesktop.org/archives/intel-gfx/2017-May/127424.html
Bottom line, the DDC/I2C failures when using a display connected to a recent docking station appear to be in the DisplayPort driver code, which affects the DVI and HDMI connectors, not just the DisplayPort connector. Until that's fixed, there's not much ddcutil can do.
But here's the positive way to think about it. Your bug report helped me see a pattern, which led to identifying a driver bug. So hopefully this will get fixed, though it will be a while before the fix makes its way into released code.
Sanford
On 05/04/2017 12:43 PM, mixmastamyk wrote:
Hah, just remembered my daughter's kano computer came with an unused HDMI cable, so plugged it in and it works as an extra channel to communicate! Big, bright yellow Fischer-Price cable sticking out of my "professional" black laptop, haha.
Still curious if a video driver could interfere with I2C/DDC?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299242106, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbv7HZOb_pMDN0gZDQ5BHmi2mGqiOks5r2gA1gaJpZM4LhYdj.
Closing this issue since it has been determined to be a problem in the DisplayPort Multi-Stream I2C driver code.
For a detailed description of this issue, see this discussion thread.
Updates will be posted on the ddcutil FAQ.
Nice, so it looks like this may be fixed sometime in the future. Tracked down the bug at freedesktop.org:
(Looks like the developer did not get CC'd on the bug as he asked, unless is on the mailing list, which is likely.)
Could not CC him within the bug, unrecognized email address. Sent him email directly.
On 05/08/2017 11:51 AM, mixmastamyk wrote:
Nice, so it looks like this may be fixed sometime in the future. Tracked down the bug at freedesktop.org:
(Looks like the developer did not get CC'd on the bug as he asked, unless he is on the mailing list, which is likely.)
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-299907526, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbtjnRGWAa6HLJziMTqfPTJsXSjmXks5r3zn6gaJpZM4LhYdj.
@rockowitz Can we do something to create more priority on the upstream bugs? Seems anything interesting in the last month.
I suggest you add yourself to the CC list for the following bug: i2c-dev failures with recent chips and docking stations https://bugs.freedesktop.org/show_bug.cgi?id=100954
Sanford
On 12/5/18 1:00 PM, bhack wrote:
@rockowitz https://github.com/rockowitz Can we do something to create more priority on the upstream bugs? Seems anything interesting in the last month.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/11#issuecomment-444582059, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbmqFpM-eMcMIvXqNWnBYxbkNNG5aks5u2AmlgaJpZM4LhYdj.
/cc @libthinkpad
@rockowitz I have the same issue with a lenovo dock. Can I contribute in anyway?
I added myself as a CC to the issue linked above.
I confirm plugging in the HDMI cable directly to the laptop works as expected. The monitor is a Dell P2418D.
(note the abort on that last snippet, maybe that should be tracked as a separate bug)
On 1/7/19 2:31 PM, Antoine Bolvy wrote:
@rockowitz https://github.com/rockowitz I have the same issue with a lenovo dock. Can I contribute in anyway?
I added myself as a CC to the issue linked above
Adding yourself to the CC list for the freedesktop.org bug is the most useful thing to do in my estimation, as it indicates the significance of the problem to the i915 driver developers. If and when they address the problem, then it would be useful to build their latest driver and test if it works.
I confirm plugging in the HDMI cable directly to the laptop works as expected. The monitor is a Dell P2418D.
Connected to DP via dock |Setting output level verbose... Setting maximum retries... Forcing --stats... Forcing --force-slave-address.. This command will take a while to run... Current time (local): 2019-01-07 20:22:29 CET Current time (UTC): 2019-01-07 19:22:29 Seconds since boot: 450431 Basic System Information ddcutil version: 0.9.4 /proc/version: Linux version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) (gcc version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 Architecture: x86_64 Distributor id: Arch Release: rolling Found a known architecture /proc/cmdline: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/MZVLW256HEHP-root rw cryptdevice=UUID=d9b2f01c-1b0f-4059-bb92-308c5c729572:cryptolvm:allow-discards resume=/dev/mapper/MZVLW256HEHP-swap Compiler information: C standard: 201710 gcc compatible compiler: Compiler version: 8.2.1 Processor information as reported by lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Stepping: 9 CPU MHz: 799.267 CPU max MHz: 3500.0000 CPU min MHz: 400.0000 BogoMIPS: 5810.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 4096K NUMA node0 CPU(s): 0-3 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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp DMI Information from /sys/class/dmi/id: Motherboard vendor: LENOVO Motherboard product name: 20HFCTO1WW System vendor: LENOVO System product name: 20HFCTO1WW Chassis vendor: LENOVO Chassis type: 10 - Notebook Byte order checks: Is big endian (local test): false WORDS_BIGENDIAN macro (autoconf): not defined __BYTE_ORDER macro (gcc): ORDER_LITTLE_ENDIAN__ Primary Check 1: Identify video card and driver Obtaining card and driver information from /sys... Primary video controller at PCI address 0000:00:02.0 (boot_vga flag is set) Device class: x030000 VGA compatible controller Vendor: x8086 Intel Corporation Device: x5916 HD Graphics 620 Subvendor/Subdevice: 17aa/224b Lenovo Driver name: i915 Driver version: Unable to determine I2C device: i2c-3 name: i915 gmbus dpd I2C device: i2c-1 name: i915 gmbus dpc I2C device: i2c-2 name: i915 gmbus dpb I2C device: i2c-7 name: DPMST Primary Check 2: Check that /dev/i2c- exist and writable ** Current user: root (0) 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 can 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 Jan 7 17:14 /dev/i2c-0 crw------- 1 root root 89, 1 Jan 7 17:14 /dev/i2c-1 crw------- 1 root root 89, 2 Jan 7 17:14 /dev/i2c-2 crw------- 1 root root 89, 3 Jan 7 17:14 /dev/i2c-3 crw------- 1 root root 89, 4 Jan 7 17:14 /dev/i2c-4 crw------- 1 root root 89, 5 Jan 7 17:14 /dev/i2c-5 crw------- 1 root root 89, 6 Jan 7 17:14 /dev/i2c-6 crw------- 1 root root 89, 7 Jan 7 20:22 /dev/i2c-7 Current user (root) has RW access to all /dev/i2c- devices. Checking for group i2c... Group i2c does not exist Looking for udev rules files that reference i2c: Checking rules directory /lib/udev/rules.d: /lib/udev/rules.d/60-sensor.rules:SUBSYSTEM=="iio", KERNEL=="iio", SUBSYSTEMS=="usb|i2c", \ Checking rules directory /run/udev/rules.d: grep: /run/udev/rules.d/rules: No such file or directory Checking rules directory /etc/udev/rules.d: Primary Check 3: Check that module i2c_dev is loaded Checking for module i2c_dev... Module i2c-dev is NOT built into kernel Loadable i2c-dev module found Module i2c_dev is loaded Check that kernel module i2c_dev is being loaded by examining files where this would be specified... grep: /etc/modules: No such file or directory grep: /etc/modules-load.d/conf: No such file or directory grep: /run/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... No driver specific checks apply. Additional probes Scanning /proc/modules for driver environment... Found other loaded module: i2c_dev Found other loaded module: videobuf2_vmalloc Found other loaded module: videobuf2_memops Found other loaded module: videobuf2_v4l2 Found other loaded module: videobuf2_common Found other loaded module: videodev Found video driver module: i915 Found other loaded module: i2c_algo_bit Found other loaded module: drm_kms_helper Loaded drm module depends on: i915,drm_kms_helper, Found other loaded module: i2c_i801 Testing if modules are loaded using /sys... Module amdgpu is NOT loaded Module fbdev is NOT loaded Module fglrx is NOT loaded Module fturbo is NOT loaded Module i915 is loaded Module mgag200 is NOT loaded Module nvidia is NOT loaded Module nouveau is NOT loaded Module radeon is NOT loaded Module vboxvideo is NOT loaded Module vc4 is NOT loaded Module drm is loaded Module i2c_algo_bit is loaded Module i2c_dev is loaded Module i2c_piix4 is NOT loaded Module ddcci is NOT loaded Examining /sys/bus/i2c/devices... /sys/bus/i2c/devices/i2c-3/name: i915 gmbus dpd /sys/bus/i2c/devices/i2c-1/name: i915 gmbus dpc /sys/bus/i2c/devices/i2c-6/name: DPDDC-C /sys/bus/i2c/devices/i2c-4/name: DPDDC-A /sys/bus/i2c/devices/i2c-2/name: i915 gmbus dpb /sys/bus/i2c/devices/i2c-0/name: SMBus I801 adapter at efa0 /sys/bus/i2c/devices/i2c-7/name: DPMST /sys/bus/i2c/devices/i2c-5/name: DPDDC-B Examining I2C buses, as detected by I2C layer... Current time (local): 2019-01-07 20:22:29 CET Current time (UTC): 2019-01-07 19:22:29 Seconds since boot: 450431 Detected 7 I2C buses: Bus /dev/i2c-1 found: true Bus /dev/i2c-1 probed: true Address 0x50 present: false Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-2 found: true Bus /dev/i2c-2 probed: true Address 0x50 present: false Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-3 found: true Bus /dev/i2c-3 probed: true Address 0x50 present: false Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-4 found: true Bus /dev/i2c-4 probed: true Address 0x50 present: true Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK EDID synopsis: Mfg id: LGD Model: Unspecified Serial number: Unspecified Manufacture year: 2016 EDID version: 1.4 Product code: 1313 Extra descriptor: LP140WF6-SPB6 Video input definition: 0x95 - Digital Input (DisplayPort) Supported features: DPMS standby DPMS suspend DPMS active-off Digital display type: RGB 4:4:4 Standard sRGB color space: False White x,y: 0.313, 0.329 Red x,y: 0.580, 0.360 Green x,y: 0.335, 0.560 Blue x,y: 0.160, 0.120 Extension blocks: 0 EDID source: EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 30 e4 21 05 00 00 00 00 ........0.!..... +0010 00 1a 01 04 95 1f 11 78 ea 9d 35 94 5c 55 8f 29 .......x..5.\U.) +0020 1e 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 .PT............. +0030 01 01 01 01 01 01 2e 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0 +0040 35 00 35 ae 10 00 00 1a 54 2b 80 a0 70 38 1f 40 5.5.....T+..p8.@ +0050 30 20 35 00 35 ae 10 00 00 1a 00 00 00 fe 00 4c 0 5.5..........L +0060 47 20 44 69 73 70 6c 61 79 0a 20 20 00 00 00 fe G Display. .... +0070 00 4c 50 31 34 30 57 46 36 2d 53 50 42 36 00 75 .LP140WF6-SPB6.u Bus /dev/i2c-5 found: true Bus /dev/i2c-5 probed: true Address 0x50 present: false Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-6 found: true Bus /dev/i2c-6 probed: true Address 0x50 present: false Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Bus /dev/i2c-7 found: true Bus /dev/i2c-7 probed: true Address 0x50 present: false Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK xrandr connection report: eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 530mm x 300mm DP2-2 disconnected (normal left inverted right x axis y axis) DP2-3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Checking for possibly conflicting programs... Examining I2C buses using i2cdetect... Current time (local): 2019-01-07 20:22:29 CET Current time (UTC): 2019-01-07 19:22:29 Seconds since boot: 450431 Device /dev/i2c-0 is a SMBus or other ignorable device. Skipping i2cdetect. 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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-2 using command "i2cdetect -y 2" 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-3 using command "i2cdetect -y 3" 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-4 using command "i2cdetect -y 4" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Probing bus /dev/i2c-5 using command "i2cdetect -y 5" 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-6 using command "i2cdetect -y 6" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77 Probing bus /dev/i2c-7 using command "i2cdetect -y 7" 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Performing basic scan of I2C devices using local sysenv functions... Current time (local): 2019-01-07 20:22:46 CET Current time (UTC): 2019-01-07 19:22:46 Seconds since boot: 450448 Examining device /dev/i2c-0... Device /dev/i2c-0 is a SMBus or other ignorable device. Skipping. Examining device /dev/i2c-1... Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Unable to read EDID, psc=ENXIO(-6): No such device or address Trying simple VCP read of feature 0x10... Attempt 1 to read feature returned hard error: ENXIO(-6): No such device or address DDC communication failed. Examining device /dev/i2c-2... Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Unable to read EDID, psc=ENXIO(-6): No such device or address Trying simple VCP read of feature 0x10... Attempt 1 to read feature returned hard error: ENXIO(-6): No such device or address DDC communication failed. Examining device /dev/i2c-3... Functionality: I2C_FUNC_I2C, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Unable to read EDID, psc=ENXIO(-6): No such device or address Trying simple VCP read of feature 0x10... Attempt 1 to read feature returned hard error: ENXIO(-6): No such device or address DDC communication failed. Examining device /dev/i2c-4... Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Unable to read EDID, psc=EREMOTEIO(-121): Remote I/O error Trying simple VCP read of feature 0x10... Attempt 1 to read feature returned hard error: EREMOTEIO(-121): Remote I/O error DDC communication failed. Examining device /dev/i2c-5... Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Unable to read EDID, psc=ETIMEDOUT(-110): Connection timed out Trying simple VCP read of feature 0x10... Attempt 1 to read feature returned hard error: ETIMEDOUT(-110): Connection timed out DDC communication failed. Examining device /dev/i2c-6... Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK Unable to read EDID, psc=EREMOTEIO(-121): Remote I/O error Trying simple VCP read of feature 0x10... Attempt 1 to read feature returned hard error: EREMOTEIO(-121): Remote I/O error DDC communication failed. Examining device /dev/i2c-7... Functionality: I2C_FUNC_I2C, I2C_FUNC_10BIT_ADDR, I2C_FUNC_SMBUS_PEC, I2C_FUNC_SMBUS_BLOCK_PROC_CALL, 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_PROC_CALL, I2C_FUNC_SMBUS_READ_BLOCK_DATA, I2C_FUNC_SMBUS_WRITE_BLOCK_DATA, I2C_FUNC_SMBUS_READ_I2C_BLOCK, I2C_FUNC_SMBUS_WRITE_I2C_BLOCK 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. EDIDs reported by X11 for connected xrandr outputs: xrandr output: eDP1 Raw EDID: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 30 e4 21 05 00 00 00 00 ........0.!..... +0010 00 1a 01 04 95 1f 11 78 ea 9d 35 94 5c 55 8f 29 .......x..5.\U.) +0020 1e 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 .PT............. +0030 01 01 01 01 01 01 2e 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0 +0040 35 00 35 ae 10 00 00 1a 54 2b 80 a0 70 38 1f 40 5.5.....T+..p8.@ +0050 30 20 35 00 35 ae 10 00 00 1a 00 00 00 fe 00 4c 0 5.5..........L +0060 47 20 44 69 73 70 6c 61 79 0a 20 20 00 00 00 fe G Display. .... +0070 00 4c 50 31 34 30 57 46 36 2d 53 50 42 36 00 75 .LP140WF6-SPB6.u EDID synopsis: Mfg id: LGD Model: Unspecified Serial number: Unspecified Manufacture year: 2016 EDID version: 1.4 Product code: 1313 Extra descriptor: LP140WF6-SPB6 Video input definition: 0x95 - Digital Input (DisplayPort) Supported features: DPMS standby DPMS suspend DPMS active-off Digital display type: RGB 4:4:4 Standard sRGB color space: False White x,y: 0.313, 0.329 Red x,y: 0.580, 0.360 Green x,y: 0.335, 0.560 Blue x,y: 0.160, 0.120 Extension blocks: 0 EDID source: xrandr output: DP2-1 Raw EDID: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 10 ac c1 d0 54 32 5a 30 ............T2Z0 +0010 18 1b 01 04 a5 35 1e 78 3a ad 75 a9 54 4d 9d 26 .....5.x:.u.TM.& +0020 0f 50 54 a5 4b 00 81 00 b3 00 d1 00 71 4f a9 40 .PT.K.......qO.@ +0030 81 80 d1 c0 01 01 56 5e 00 a0 a0 a0 29 50 30 20 ......V^....)P0 +0040 35 00 0e 28 21 00 00 1a 00 00 00 ff 00 4d 59 33 5..(!........MY3 +0050 4e 44 37 36 49 30 5a 32 54 0a 00 00 00 fc 00 44 ND76I0Z2T......D +0060 45 4c 4c 20 50 32 34 31 38 44 0a 20 00 00 00 fd ELL P2418D. .... +0070 00 31 56 1d 71 1c 01 0a 20 20 20 20 20 20 01 b2 .1V.q... .. EDID synopsis: Mfg id: DEL Model: DELL P2418D Serial number: MY3ND76I0Z2T Manufacture year: 2017 EDID version: 1.4 Product code: 53441 Extra descriptor: Unspecified Video input definition: 0xa5 - Digital Input (DisplayPort) Supported features: DPMS active-off Digital display type: RGB 4:4:4 + YCrCb 4:2:2 Standard sRGB color space: True White x,y: 0.313, 0.329 Red x,y: 0.662, 0.330 Green x,y: 0.304, 0.614 Blue x,y: 0.149, 0.062 Extension blocks: 1 EDID source: Probing I2C devices using udev, susbsystem i2c-dev... Current time (local): 2019-01-07 20:22:48 CET Current time (UTC): 2019-01-07 19:22:48 Seconds since boot: 450450 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-5/i2c-dev/i2c-5 Device Node Path: /dev/i2c-5 struct udev_device at: 0x557b56c1cfe0 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-5/i2c-dev/i2c-5 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-5/i2c-dev/i2c-5 sysname: i2c-5 sysnum: 5 devnode: /dev/i2c-5 Properties: DEVNAME -> /dev/i2c-5 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-5/i2c-dev/i2c-5 MAJOR -> 89 MINOR -> 5 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:5 device -> (null) name -> DPDDC-B subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=5 DEVNAME=i2c-5 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-6/i2c-dev/i2c-6 Device Node Path: /dev/i2c-6 struct udev_device at: 0x557b56c23520 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-6/i2c-dev/i2c-6 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-6/i2c-dev/i2c-6 sysname: i2c-6 sysnum: 6 devnode: /dev/i2c-6 Properties: DEVNAME -> /dev/i2c-6 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-6/i2c-dev/i2c-6 MAJOR -> 89 MINOR -> 6 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:6 device -> (null) name -> DPDDC-C subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=6 DEVNAME=i2c-6 One Device path: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-4/i2c-dev/i2c-4 Device Node Path: /dev/i2c-4 struct udev_device at: 0x557b56c23520 devpath: /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-4/i2c-dev/i2c-4 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-4/i2c-dev/i2c-4 sysname: i2c-4 sysnum: 4 devnode: /dev/i2c-4 Properties: DEVNAME -> /dev/i2c-4 DEVPATH -> /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-4/i2c-dev/i2c-4 MAJOR -> 89 MINOR -> 4 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:4 device -> (null) name -> DPDDC-A subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=4 DEVNAME=i2c-4 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 Device Node Path: /dev/i2c-1 struct udev_device at: 0x557b56c23210 devpath: /devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.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:02.0/i2c-1/i2c-dev/i2c-1 MAJOR -> 89 MINOR -> 1 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:1 device -> (null) name -> i915 gmbus dpc subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=1 DEVNAME=i2c-1 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 Device Node Path: /dev/i2c-2 struct udev_device at: 0x557b56c23830 devpath: /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 sysname: i2c-2 sysnum: 2 devnode: /dev/i2c-2 Properties: DEVNAME -> /dev/i2c-2 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 MAJOR -> 89 MINOR -> 2 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:2 device -> (null) name -> i915 gmbus dpb subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=2 DEVNAME=i2c-2 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-3/i2c-dev/i2c-3 Device Node Path: /dev/i2c-3 struct udev_device at: 0x557b56c23210 devpath: /devices/pci0000:00/0000:00:02.0/i2c-3/i2c-dev/i2c-3 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-3/i2c-dev/i2c-3 sysname: i2c-3 sysnum: 3 devnode: /dev/i2c-3 Properties: DEVNAME -> /dev/i2c-3 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-3/i2c-dev/i2c-3 MAJOR -> 89 MINOR -> 3 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:3 device -> (null) name -> i915 gmbus dpd subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=3 DEVNAME=i2c-3 One Device path: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 Device Node Path: /dev/i2c-7 struct udev_device at: 0x557b56c23830 devpath: /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 sysname: i2c-7 sysnum: 7 devnode: /dev/i2c-7 Properties: DEVNAME -> /dev/i2c-7 DEVPATH -> /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 MAJOR -> 89 MINOR -> 7 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:7 device -> (null) name -> DPMST subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=7 DEVNAME=i2c-7 One Device path: /sys/devices/pci0000:00/0000:00:1f.4/i2c-0/i2c-dev/i2c-0 Device Node Path: /dev/i2c-0 struct udev_device at: 0x557b56c23830 devpath: /devices/pci0000:00/0000:00:1f.4/i2c-0/i2c-dev/i2c-0 subsystem: i2c-dev devtype: (null) syspath: /sys/devices/pci0000:00/0000:00:1f.4/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:1f.4/i2c-0/i2c-dev/i2c-0 MAJOR -> 89 MINOR -> 0 SUBSYSTEM -> i2c-dev Sysattrs: dev -> 89:0 device -> (null) name -> SMBus I801 adapter at efa0 subsystem -> i2c-dev uevent -> MAJOR=89 MINOR=0 DEVNAME=i2c-0 Summary of udev I2C devices Subsystem Sysname Sysattr Name Devpath i2c-dev i2c-0 SMBus I801 adapter at efa0 /devices/pci0000:00/0000:00:1f.4/i2c-0/i2c-dev/i2c-0 i2c-dev i2c-1 i915 gmbus dpc /devices/pci0000:00/0000:00:02.0/i2c-1/i2c-dev/i2c-1 i2c-dev i2c-2 i915 gmbus dpb /devices/pci0000:00/0000:00:02.0/i2c-2/i2c-dev/i2c-2 i2c-dev i2c-3 i915 gmbus dpd /devices/pci0000:00/0000:00:02.0/i2c-3/i2c-dev/i2c-3 i2c-dev i2c-4 DPDDC-A /devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-4/i2c-dev/i2c-4 i2c-dev i2c-5 DPDDC-B /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-5/i2c-dev/i2c-5 i2c-dev i2c-6 DPDDC-C /devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-6/i2c-dev/i2c-6 i2c-dev i2c-7 DPMST /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 Looking for udev devices with name attribute DPMST... Summary of udev DPMST devices... Subsystem Sysname Sysattr Name Devpath i2c i2c-7 DPMST /devices/pci0000:00/0000:00:02.0/i2c-7 i2c i2c-7 DPMST /devices/pci0000:00/0000:00:02.0/i2c-7 i2c-dev i2c-7 DPMST /devices/pci0000:00/0000:00:02.0/i2c-7/i2c-dev/i2c-7 Examining configuration files... DKMS modules: Kernel I2C configuration settings: grep: /boot/config-4.20.0-arch1-1-ARCH: No such file or directory Kernel AMDGPU configuration settings: grep: /boot/config-4.20.0-arch1-1-ARCH: No such file or directory Examining system logs... Current timestamps: Current time (local): 2019-01-07 20:22:48 CET Current time (UTC): 2019-01-07 19:22:48 Seconds since boot: 450450 Scanning dmesg output for I2C related entries... Executing command: dmesg [91292.007266] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [104333.055168] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [104343.141274] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [104642.028340] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [106353.293987] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [109117.003905] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [119755.590998] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [122358.883869] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [134597.647222] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [134598.182814] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [134631.193116] drm_dp_i2c_do_msg: 2 callbacks suppressed [134694.132608] drm_dp_i2c_do_msg: 2 callbacks suppressed [134704.665076] drm_dp_i2c_do_msg: 2 callbacks suppressed [134712.819451] drm_dp_i2c_do_msg: 2 callbacks suppressed [134885.106197] drm_dp_i2c_do_msg: 2 callbacks suppressed [135124.303862] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [135144.299920] drm_dp_i2c_do_msg: 2 callbacks suppressed [136101.544299] drm_dp_i2c_do_msg: 2 callbacks suppressed [136115.753183] drm_dp_i2c_do_msg: 2 callbacks suppressed [136585.401423] drm_dp_i2c_do_msg: 2 callbacks suppressed [136603.275455] drm_dp_i2c_do_msg: 14 callbacks suppressed [136608.313124] drm_dp_i2c_do_msg: 464 callbacks suppressed [136654.757790] drm_dp_i2c_do_msg: 2 callbacks suppressed [136792.812206] drm_dp_i2c_do_msg: 2 callbacks suppressed [137248.853012] drm_dp_i2c_do_msg: 2 callbacks suppressed [141020.439701] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [141065.091346] drm_dp_i2c_do_msg: 2 callbacks suppressed [143175.799283] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [145281.142366] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [145330.276804] drm_dp_i2c_do_msg: 232 callbacks suppressed Scanning journalctl output for I2C related entries... Executing command: journalctl --no-pager --boot Jan 02 15:41:30 lenovo-LBA042 kernel: ACPI: Added _OSI(Linux-Dell-Video) Jan 02 15:41:30 lenovo-LBA042 kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] Jan 02 15:41:30 lenovo-LBA042 kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver Jan 02 15:41:31 lenovo-LBA042 kernel: i915 0000:00:02.0: enabling device (0006 -> 0007) Jan 02 15:41:31 lenovo-LBA042 kernel: fb0: switching to inteldrmfb from EFI VGA Jan 02 15:41:31 lenovo-LBA042 kernel: [drm] Replacing VGA console driver Jan 02 15:41:31 lenovo-LBA042 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Jan 02 15:41:31 lenovo-LBA042 kernel: [drm] Driver supports precise vblank timestamp query. Jan 02 15:41:31 lenovo-LBA042 kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=mem Jan 02 15:41:31 lenovo-LBA042 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Jan 02 15:41:31 lenovo-LBA042 kernel: [drm] Initialized i915 1.6.0 20180921 for 0000:00:02.0 on minor 0 Jan 02 15:41:31 lenovo-LBA042 kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Jan 02 15:41:31 lenovo-LBA042 kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8 Jan 02 15:41:31 lenovo-LBA042 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jan 02 15:41:31 lenovo-LBA042 kernel: fbcon: inteldrmfb (fb0) is primary device Jan 02 15:41:32 lenovo-LBA042 kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device Jan 02 15:41:32 lenovo-LBA042 kernel: videodev: Linux video capture interface: v2.00 Jan 02 15:41:32 lenovo-LBA042 kernel: uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b5ab) Jan 02 15:41:32 lenovo-LBA042 kernel: uvcvideo 1-8:1.0: Entity type for entity Extension 4 was not initialized! Jan 02 15:41:32 lenovo-LBA042 kernel: uvcvideo 1-8:1.0: Entity type for entity Extension 3 was not initialized! Jan 02 15:41:32 lenovo-LBA042 kernel: uvcvideo 1-8:1.0: Entity type for entity Processing 2 was not initialized! Jan 02 15:41:32 lenovo-LBA042 kernel: uvcvideo 1-8:1.0: Entity type for entity Camera 1 was not initialized! Jan 02 15:41:32 lenovo-LBA042 kernel: usbcore: registered new interface driver uvcvideo Jan 02 15:41:32 lenovo-LBA042 kernel: USB Video Class driver (1.1.1) Jan 02 15:16:34 lenovo-LBA042 keybase[18882]: 2019-01-02T15:16:34.683617+01:00 ▶ [DEBU keybase config.go:310] 22d HelloIAm: 2 - {19108 desktop helper [/opt/keybase/Keybase --type=renderer --no-sandbox --primordial-pipe-token=05E973435C90CC9F91C5BA9F415732AE --lang=en-US --app-path=/opt/keybase/resources/app --node-integration=true --webview-tag=true --no-sandbox --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553 --disable-accelerated-video-decode --service-request-channel-token=05E973435C90CC9F91C5BA9F415732AE --renderer-client-id=4 --shared-files=v8_natives_data:100,v8_snapshot_data:101] Menubar 1.0.36-20171206132529+337e709239} Jan 02 15:16:35 lenovo-LBA042 keybase[18882]: 2019-01-02T15:16:35.305892+01:00 ▶ [DEBU keybase config.go:310] 25c HelloIAm: 3 - {19115 desktop [/opt/keybase/Keybase --type=renderer --no-sandbox --primordial-pipe-token=D8D8BE55DEF7FA8866BDFCD8F2EA5A13 --lang=en-US --app-path=/opt/keybase/resources/app --node-integration=true --webview-tag=true --no-sandbox --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553 --disable-accelerated-video-decode --service-request-channel-token=D8D8BE55DEF7FA8866BDFCD8F2EA5A13 --renderer-client-id=6 --shared-files=v8_natives_data:100,v8_snapshot_data:101] Main Renderer 1.0.36-20171206132529+337e709239} Jan 02 16:02:16 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 02 20:21:12 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 02 20:42:41 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 03 09:38:16 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 03 13:55:54 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 03 19:28:17 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 03 21:49:01 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 08:49:00 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 09:23:44 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 09:38:36 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 11:38:49 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 13:48:00 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 14:05:37 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 15:49:58 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 16:13:36 lenovo-LBA042 root[5641]: ACPI group/action undefined: video/brightnessdown / BRTDN Jan 04 16:13:36 lenovo-LBA042 root[5653]: ACPI group/action undefined: video/brightnessup / BRTUP Jan 04 16:13:37 lenovo-LBA042 root[5660]: ACPI group/action undefined: video/brightnessdown / BRTDN Jan 04 16:13:37 lenovo-LBA042 root[5667]: ACPI group/action undefined: video/brightnessdown / BRTDN Jan 04 16:13:37 lenovo-LBA042 root[5680]: ACPI group/action undefined: video/brightnessup / BRTUP Jan 04 19:27:19 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 04 19:27:29 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 09:04:32 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 09:33:00 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 10:19:04 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 13:16:14 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 13:59:37 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 17:23:36 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 17:23:36 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 17:24:09 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:25:12 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:25:23 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:25:31 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:28:23 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:32:22 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 17:32:42 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:48:40 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:48:54 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:56:44 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 17:57:01 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 14 callbacks suppressed Jan 07 17:57:06 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 464 callbacks suppressed Jan 07 17:57:53 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 18:00:11 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 18:07:47 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 19:10:39 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 19:11:23 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 2 callbacks suppressed Jan 07 19:46:34 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 20:21:39 lenovo-LBA042 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 07 20:22:28 lenovo-LBA042 kernel: drm_dp_i2c_do_msg: 232 callbacks suppressed Scanning file: /var/log/Xorg.0.log Limiting output to first 200 relevant lines... [ 43.250] X.Org Video Driver: 24.0 [ 43.252] (II) xfree86: Adding drm device (/dev/dri/card0) [ 43.774] Module class: X.Org Video Driver [ 43.774] ABI class: X.Org Video Driver, version 24.0 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, [ 43.995] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20180921 [ 44.035] (II) Initializing extension XVideo [ 44.035] (II) Initializing extension XVideo-MotionCompensation [ 44.209] (II) config/udev: Adding input device Video Bus (/dev/input/event6) [ 44.209] () Video Bus: Applying InputClass "libinput keyboard catchall" [ 44.209] () Video Bus: Applying InputClass "system-keyboard" [ 44.209] (II) Using input driver 'libinput' for 'Video Bus' [ 44.209] () Video Bus: always reports core events [ 44.210] (II) event6 - Video Bus: is tagged by udev as: Keyboard [ 44.210] (II) event6 - Video Bus: device is a keyboard [ 44.210] (II) event6 - Video Bus: device removed [ 44.224] () Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8/event6" [ 44.224] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7) [ 44.225] (II) event6 - Video Bus: is tagged by udev as: Keyboard [ 44.225] (II) event6 - Video Bus: device is a keyboard File not found: /var/log/messages File not found: /var/log/kern.log File not found: /var/log/daemon.log File not found: /var/log/syslog Log Summary Log Checked Found === ======= ===== dmesg true true journalctl true false /var/log/daemon.log true false /var/log/kern.log true false /var/log/messages true false /var/log/syslog true false /var/log/Xorg.0.log true true Probing connected monitors using libdrm... Checking libdrm version using pkg-config... 2.4.96 Has a DRM kernel driver been loaded? (drmAvailable()): true Probing device /dev/dri/card0... Open succeeded for device: /dev/dri/card0 DRM driver version information: Version: 1.6.0 Driver: i915 Date: 20180921 Description: Intel Graphics DRM library version: 1.3.0. DRM Busid: pci:0000:00:02.0 Device information: bustype: 0 - pci domain:bus:device.func: 0000:00:02.0 vendor vid:pid: 0x8086:0x5916 subvendor vid:pid: 0x17aa:0x224b revision id: 0x0002 Is a modesetting capable driver attached to bus id: pci:0000:00:02.0? (calling drmCheckModesettingAvailable()) Yes Retrieving DRM resources... Scanning defined properties... Property 1: EDID flags: 0x00000014 - DRM_MODE_PROP_IMMUTABLE, DRM_MODE_PROP_BLOB Property 2: DPMS flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 3: PATH flags: 0x00000014 - DRM_MODE_PROP_IMMUTABLE, DRM_MODE_PROP_BLOB Property 4: TILE flags: 0x00000014 - DRM_MODE_PROP_IMMUTABLE, DRM_MODE_PROP_BLOB Property 5: link-status flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 6: non-desktop flags: 0x00000006 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_IMMUTABLE Property 7: type flags: 0x0000000c - DRM_MODE_PROP_IMMUTABLE, DRM_MODE_PROP_ENUM Property 8: SRC_X flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 9: SRC_Y flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 10: SRC_W flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 11: SRC_H flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 12: CRTC_X flags: 0x80000080 - DRM_MODE_PROP_SIGNED_RANGE, DRM_MODE_PROP_ATOMIC Property 13: CRTC_Y flags: 0x80000080 - DRM_MODE_PROP_SIGNED_RANGE, DRM_MODE_PROP_ATOMIC Property 14: CRTC_W flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 15: CRTC_H flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 16: FB_ID flags: 0x80000040 - DRM_MODE_PROP_OBJECT, DRM_MODE_PROP_ATOMIC Property 17: IN_FENCE_FD flags: 0x80000080 - DRM_MODE_PROP_SIGNED_RANGE, DRM_MODE_PROP_ATOMIC Property 18: OUT_FENCE_PTR flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 19: CRTC_ID flags: 0x80000040 - DRM_MODE_PROP_OBJECT, DRM_MODE_PROP_ATOMIC Property 20: ACTIVE flags: 0x80000002 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_ATOMIC Property 21: MODE_ID flags: 0x80000010 - DRM_MODE_PROP_BLOB, DRM_MODE_PROP_ATOMIC Property 22: DEGAMMA_LUT flags: 0x00000010 - DRM_MODE_PROP_BLOB Property 23: DEGAMMA_LUT_SIZE flags: 0x00000006 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_IMMUTABLE Property 24: CTM flags: 0x00000010 - DRM_MODE_PROP_BLOB Property 25: GAMMA_LUT flags: 0x00000010 - DRM_MODE_PROP_BLOB Property 26: GAMMA_LUT_SIZE flags: 0x00000006 - DRM_MODE_PROP_RANGE, DRM_MODE_PROP_IMMUTABLE Property 27: IN_FORMATS flags: 0x00000014 - DRM_MODE_PROP_IMMUTABLE, DRM_MODE_PROP_BLOB Property 30: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 31: COLOR_ENCODING flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 32: COLOR_RANGE flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 35: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 36: COLOR_ENCODING flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 37: COLOR_RANGE flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 40: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 44: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 45: COLOR_ENCODING flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 46: COLOR_RANGE flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 49: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 50: COLOR_ENCODING flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 51: COLOR_RANGE flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 54: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 58: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 59: COLOR_ENCODING flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 60: COLOR_RANGE flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 63: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 64: COLOR_ENCODING flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 65: COLOR_RANGE flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 68: rotation flags: 0x00000020 - DRM_MODE_PROP_BITMASK Property 76: Broadcast RGB flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 77: scaling mode flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 83: audio flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 84: Content Protection flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 86: aspect ratio flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 87: content type flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 88: Content Protection flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 94: Content Protection flags: 0x00000008 - DRM_MODE_PROP_ENUM Property 96: Content Protection flags: 0x00000008 - DRM_MODE_PROP_ENUM Scanning connectors... connector_id: 71 connector name eDP-1 connector_type: 14
- eDP connector_type_id: 1 connection: 1 - connected encoder: 70 encoder type (signal format): 2 - TDMS EDID property Raw property blob: blob id: 128 +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 30 e4 21 05 00 00 00 00 ........0.!..... +0010 00 1a 01 04 95 1f 11 78 ea 9d 35 94 5c 55 8f 29 .......x..5.\U.) +0020 1e 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 .PT............. +0030 01 01 01 01 01 01 2e 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0 +0040 35 00 35 ae 10 00 00 1a 54 2b 80 a0 70 38 1f 40 5.5.....T+..p8.@ +0050 30 20 35 00 35 ae 10 00 00 1a 00 00 00 fe 00 4c 0 5.5..........L +0060 47 20 44 69 73 70 6c 61 79 0a 20 20 00 00 00 fe G Display. .... +0070 00 4c 50 31 34 30 57 46 36 2d 53 50 42 36 00 75 .LP140WF6-SPB6.u EDID synopsis: Mfg id: LGD Model: Unspecified Serial number: Unspecified Manufacture year: 2016 EDID version: 1.4 Product code: 1313 Extra descriptor: LP140WF6-SPB6 Video input definition: 0x95 - Digital Input (DisplayPort) Supported features: DPMS standby DPMS suspend DPMS active-off Digital display type: RGB 4:4:4 Standard sRGB color space: False White x,y: 0.313, 0.329 Red x,y: 0.580, 0.360 Green x,y: 0.335, 0.560 Blue x,y: 0.160, 0.120 Extension blocks: 0 EDID source: connector_id: 79 connector name DP-1 connector_type: 10 - DP connector_type_id: 1 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found connector_id: 85 connector name HDMI-1 connector_type: 11 - HDMI connector_type_id: 1 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found connector_id: 90 connector name DP-2 connector_type: 10 - DP connector_type_id: 2 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found connector_id: 95 connector name HDMI-2 connector_type: 11 - HDMI connector_type_id: 2 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found connector_id: 100 connector name DP-4 connector_type: 10 - DP connector_type_id: 4 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found connector_id: 113 connector name DP-3 connector_type: 10 - DP connector_type_id: 3 connection: 1 - connected encoder: 92 encoder type (signal format): 7
- (null) EDID property Raw property blob: blob id: 99 +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 10 ac c1 d0 54 32 5a 30 ............T2Z0 +0010 18 1b 01 04 a5 35 1e 78 3a ad 75 a9 54 4d 9d 26 .....5.x:.u.TM.& +0020 0f 50 54 a5 4b 00 81 00 b3 00 d1 00 71 4f a9 40 .PT.K.......qO.@ +0030 81 80 d1 c0 01 01 56 5e 00 a0 a0 a0 29 50 30 20 ......V^....)P0 +0040 35 00 0e 28 21 00 00 1a 00 00 00 ff 00 4d 59 33 5..(!........MY3 +0050 4e 44 37 36 49 30 5a 32 54 0a 00 00 00 fc 00 44 ND76I0Z2T......D +0060 45 4c 4c 20 50 32 34 31 38 44 0a 20 00 00 00 fd ELL P2418D. .... +0070 00 31 56 1d 71 1c 01 0a 20 20 20 20 20 20 01 b2 .1V.q... .. +0080 02 03 15 b1 50 90 05 04 03 02 07 16 01 06 11 12 ....P........... +0090 15 13 14 1f 20 02 3a 80 18 71 38 2d 40 58 2c 45 .... .:..q8-@X,E +00a0 00 0e 28 21 00 00 1e 01 1d 80 18 71 1c 16 20 58 ..(!.......q.. X +00b0 2c 25 00 0e 28 21 00 00 9e bf 16 00 a0 80 38 13 ,%..(!........8. +00c0 40 30 20 3a 00 0e 28 21 00 00 1a 7e 39 00 a0 80 @0 :..(!...~9... +00d0 38 1f 40 30 20 3a 00 0e 28 21 00 00 1a 00 00 00 8.@0 :..(!...... +00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ +00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 62 ...............b EDID synopsis: Mfg id: DEL Model: DELL P2418D Serial number: MY3ND76I0Z2T Manufacture year: 2017 EDID version: 1.4 Product code: 53441 Extra descriptor: Unspecified Video input definition: 0xa5
- Digital Input (DisplayPort) Supported features: DPMS active-off Digital display type: RGB 4:4:4 + YCrCb 4:2:2 Standard sRGB color space: True White x,y: 0.313, 0.329 Red x,y: 0.662, 0.330 Green x,y: 0.304, 0.614 Blue x,y: 0.149, 0.062 Extension blocks: 1 EDID source: connector_id: 121 connector name DP-5 connector_type: 10 - DP connector_type_id: 5 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found connector_id: 125 connector name DP-6 connector_type: 10 - DP connector_type_id: 6 connection: 2 - disconnected encoder: 0 Encoder with id 0 not found EDID property Blob not found Examining /sys/class/drm... Found connector: card0-HDMI-A-1 /sys/class/drm/card0/card0-HDMI-A-1/status: disconnected Found connector: card0-DP-6 /sys/class/drm/card0/card0-DP-6/status: disconnected Found connector: card0-eDP-1 /sys/class/drm/card0/card0-eDP-1/status: connected I2C device: i2c-4 Found connector: card0-DP-2 /sys/class/drm/card0/card0-DP-2/status: disconnected Found connector: card0-HDMI-A-2 /sys/class/drm/card0/card0-HDMI-A-2/status: disconnected Found connector: card0-DP-5 /sys/class/drm/card0/card0-DP-5/status: disconnected Found connector: card0-DP-3 /sys/class/drm/card0/card0-DP-3/status: connected Found connector: card0-DP-1 /sys/class/drm/card0/card0-DP-1/status: disconnected Query file system for i2c nodes under /sys/class/drm/card*... drwxr-xr-x 4 root root 0 Jan 7 19:11 /sys/class/drm/card0/card0-DP-1/i2c-5 drwxr-xr-x 4 root root 0 Jan 7 19:11 /sys/class/drm/card0/card0-DP-2/i2c-6 drwxr-xr-x 4 root root 0 Jan 7 19:11 /sys/class/drm/card0/card0-eDP-1/i2c-4 Device Identifier Cross Reference Report EDID: ...42360075 Mfg: LGD Model: Unspecified SN: Unspecified I2C device: Not found XrandR output: eDP1 DRM connector: eDP-1 UDEV name: (null) UDEV syspath: (null) sysfs drm path: /sys/class/drm/card0/card0-eDP-1 sysfs drm I2C: i2c-4 EDID: ...202001B2 Mfg: DEL Model: DELL P2418D SN: MY3ND76I0Z2T I2C device: Not found XrandR output: DP2-1 DRM connector: DP-3 UDEV name: (null) UDEV syspath: (null) sysfs drm path: /sys/class/drm/card0/card0-DP-3 sysfs drm I2C: (null) Env_Accumulator: architecture: x86_64 distributor_id Arch Drivers detected: i915 /dev/i2c device numbers: 0 1 2 3 4 5 6 7 sysfs_i2c_devices_exist: true /sys/bus/i2c device numbers: 0 1 2 3 4 5 6 7 dev_i2c_devices_required: true module_i2c_dev_needed: true module_i2c_dev_builtin: false loadable_i2c_dev_exists: true i2c_dev_loaded_or_builtin: true group_i2c_checked: true group_i2c_exists: false dev_i2c_common_group_name: root all_dev_i2c_has_group_i2c: false any_dev_i2c_has_group_i2c: false all_dev_i2c_is_group_rw: true any_dev_i2c_is_group_rw: false cur_uname: root cur_uid: 0 cur_user_in_group_i2c: false cur_user_any_devi2c_rw: true cur_user_all_devi2c_rw: true Configuration suggestions: Current user has RW access to all /dev/i2c-N devices. Skipping further group and permission checks. Skipping USB environment exploration. Issue command "ddcutil usbenvironment --verbose" if there are any USB attached monitors. Statistics for environment exploration: Maximum Try Settings: Operation Type Current Default Write only exchange tries: 4 4 Write read exchange tries: 15 10 Multi-part read exchange tries: 15 8 Multi-part write exchange tries: 8 8 Retry statistics for ddc write only No tries attempted Retry statistics for ddc write/read Max tries allowed: 15 Successful attempts by number of tries required: 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 7: 0 8: 0 9: 0 10: 0 11: 0 12: 0 13: 0 14: 0 15: 0 Total: 0 Failed due to max tries exceeded: 1 Failed due to fatal error: 0 Total attempts: 1 Retry statistics for multi-part read exchange No tries attempted Retry statistics for multi-part write exchange No tries attempted DDC Related Errors: Count Status Code Description 15 EREMOTEIO ( -121) Remote I/O error 1 DDCRC_RETRIES (-3007) maximum retries exceeded (derived) Total errors: 16 Errors Wrapped in Retry: Count Status Code Description 15 EREMOTEIO ( -121) Remote I/O error Total errors: 15 Sleep Strategy Stats: Total IO events: 130 IO error count: 16 Total sleep events: 1 Sleep Event type Count SE_WRITE_TO_READ 0 SE_POST_OPEN 1 SE_POST_WRITE 0 SE_POST_READ 0 SE_DDC_NULL 0 SE_POST_SAVE_SETTINGS 0 Call Stats: Type Count Millisec ( Nanosec) write calls (IE_WRITE) 55 826 ( 826610062) read calls (IE_READ) 7 192 ( 192755604) open file calls (IE_OPEN) 16 0 ( 712025) close file calls (IE_CLOSE) 16 0 ( 205127) other I/O calls (IE_OTHER) 36 0 ( 163503) Totals: 130 1020 ( 1020446321) Sleep Call Stats: Total sleep calls: 15 Requested sleep time milliseconds : 750 Actual sleep milliseconds (nanosec): 752 ( 752549529) Total elapsed milliseconds (nanoseconds): 20802 ( 20802920252) Detected Displays Invalid display I2C bus: /dev/i2c-4 I2C address 0x50 (EDID) present: true Is eDP device: true /sys/bus/i2c/devices/i2c-4/name: DPDDC-A EDID synopsis: Mfg id: LGD Model: Unspecified Serial number: Unspecified Manufacture year: 2016 EDID version: 1.4 Product code: 1313 Extra descriptor: LP140WF6-SPB6 Video input definition: 0x95 - Digital Input (DisplayPort) Supported features: DPMS standby DPMS suspend DPMS active-off Digital display type: RGB 4:4:4 Standard sRGB color space: False White x,y: 0.313, 0.329 Red x,y: 0.580, 0.360 Green x,y: 0.335, 0.560 Blue x,y: 0.160, 0.120 Extension blocks: 0 EDID source: EDID hex dump: +0 +4 +8 +c 0 4 8 c +0000 00 ff ff ff ff ff ff 00 30 e4 21 05 00 00 00 00 ........0.!..... +0010
For what it's worth, I have 2 DP Dell U2717D monitors via the lenovo ultra dock, and a x270, and they work great. Unfortunately, ddcutil loses it's ability to control brightness when connected directly to 1 monitor, as per this description.
Seems like the gory thread was useful at the least for pinpointing the actual cause.
Very keen to assist in testing or other such things to solve for the docking peeps. Will at least add myself to their bug cc on issue.
@mattcph I saw your comment on the freedesktop.org bug, you say you filed a bug with lenovo, is it public? Any link to this report?
@mattcph Can you perhaps test if some Windows alternatives to ddcutil work through the Ultra Dock? A quick google gave me https://www.clickmonitorddc.bplaced.net/, I haven't tried it myself (not a Windows user), so no guarantees, but I think it might work.
I have an Dell TB16 connected to a XPS 9560. Monitor is connected via DP to the dock. On Windows I tried multiple DDC utils like clickmonitorddc and they all work just fine. On Linux ddcutils & ddccontrol both work only if monitors are directly connected to the laptop.
So at least for my specific setup I can say that this is a non-issue when using Windows.
Same here, Dell set up, I get around the problem (literally) by having a second cable from my laptop to the monitor. :-/
Kinda defeats the purpose of the docking station but I use it for other things as well.
FWIW, the upstream bug got migrated to https://gitlab.freedesktop.org/drm/intel/-/issues/37 but still no fix :(
This should help, said to be in Linux kernel 5.10, in distros in 2021:
I have checked. The changes are in the just released 5.10 kernel.
@frogmaster has previously (issue #11) reported success having built his own driver with the changes. Further comments should be added to that issue.
I've tested this on 5.10.1 and it works fine, the only interesting thing is, my monitor shows up twice now:
% sudo ddcutil detect
[sudo] password for evgeni:
Invalid display
I2C bus: /dev/i2c-4
EDID synopsis:
Mfg id: BOE
Model:
Serial number:
Manufacture year: 2017
EDID version: 1.4
DDC communication failed
This is an eDP laptop display. Laptop displays do not support DDC/CI.
Invalid display
I2C bus: /dev/i2c-5
EDID synopsis:
Mfg id: AOC
Model: U2790B
Serial number:
Manufacture year: 2020
EDID version: 1.4
DDC communication failed
Display 1
I2C bus: /dev/i2c-7
EDID synopsis:
Mfg id: AOC
Model: U2790B
Serial number:
Manufacture year: 2020
EDID version: 1.4
VCP version: 2.2
Probably not really ddcutil
related, but worth documenting?
First, thank you @thmcmahon for reporting the success with the 5.10 kernel. Many people are interested in this problem.
Multiple /dev/i2c devices for the same monitor is a known problem. See, the FAQ. Clearly a driver problem, and I've been adding more and more code to the environment command to analyse this situation. Can I ask you to run ddcutil environment --verbose as root and submit the output as an attachment?
I've created a new issue, #160, specifically for this problem. Let's continue the discussion there.
A Christmas miracle! I had already stopped hoping that this would work someday.
So, YES, I can confirm it to be working too (kernel v 5.10.4) on a Lenovo ThinkPad Thunderbolt 3 Dock Gen 2.
What a nice surprise! What a relieve!
Hi
I built ddcutil 0.7.0 on Ubuntu 16.10. I have two external displays connected to my Lenovo x260 via a Lenovo Ultra Dock. The displays are Dell U2412Ms.
Here is the output of
ddcutil detect
:However when I try and detect monitor capabilities it doesn't work:
This seems like it may be related to issue number 8 - I'm not really all that stressed about not getting this to work, but thought this might be helpful.