f1tz,
As long as you have a Realtek codec, SND_HDA_CODEC_REALTEK=y is OK.
As the rest are missing, it won't work if you have some other codec.
HDMI not working
Message
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
Code: Select all
2: [ 0- 0]: digital audio playback
3: [ 0- 0]: digital audio capture
4: [ 0- 1]: digital audio playback
5: [ 0- 3]: digital audio playback
6: [ 0- 7]: digital audio playback
7: [ 0- 8]: digital audio playback
8: [ 0- 9]: digital audio playback
9: [ 0-10]: digital audio playback
10: [ 0- 0]: hardware dependent
11: [ 0- 2]: hardware dependent
12: [ 0] : control
33: : timer- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
f1tz,
is your analogue sound IO.
One ofis your HDMI output.
By default, alsa uses card0 device0. In your case that's analogue sound.
You need to test devices 3, 7, 8, 9 and 10 to see which is your HDMI.
A few media players, like vlc, can direct the output to a device of your choice while they run.
Audio Device is a menu.
You will need to unmute the S/PDIF in alsamixer, will will have the side effect of muting your speakers.
Your sound card is not capable of operating at two different standards at the same time.
Code: Select all
2: [ 0- 0]: digital audio playback
3: [ 0- 0]: digital audio capture One of
Code: Select all
4: [ 0- 1]: digital audio playback
5: [ 0- 3]: digital audio playback
6: [ 0- 7]: digital audio playback
7: [ 0- 8]: digital audio playback
8: [ 0- 9]: digital audio playback
9: [ 0-10]: digital audio playback By default, alsa uses card0 device0. In your case that's analogue sound.
You need to test devices 3, 7, 8, 9 and 10 to see which is your HDMI.
A few media players, like vlc, can direct the output to a device of your choice while they run.
Audio Device is a menu.
You will need to unmute the S/PDIF in alsamixer, will will have the side effect of muting your speakers.
Your sound card is not capable of operating at two different standards at the same time.
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
VLC works and I can see the outputs by selecting from the menu.
This is meant to solve the codec issue from the last post guess?
Still no progress/answer in the Wayland thread. The missing HDMI video signal still remains black-boxed mystery.
No response from Wayland debuggers out there so far. I keep searching. Any recommendations where to look for help?
This is meant to solve the codec issue from the last post guess?
Still no progress/answer in the Wayland thread. The missing HDMI video signal still remains black-boxed mystery.
No response from Wayland debuggers out there so far. I keep searching. Any recommendations where to look for help?
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
Dear Neddy,
I continued looking for helping Wayland to make it across the HDMI port and came across some issues posted on sway (Wayland compositor) github page.
The issue is called "Inconsistent output discovery and enabling" which precisely describes the problem on this machine here.
I followed the devs' guide to create a drm debug log file:
dmesg
HDMI-A-1 is a miniDisplay Port which works, HDMI-A-2 is the one with no output.
The most interesting lines are these ones:
Searching for it brings me to this kernel patch.
Where I realize my personal limits of knowledge on how to proceed. Is this patch already inside the new kernel? These patched files dont exist on my computer: (/etc/src/linux)/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
I also opened an issue on the swaywm/wlroots github page (hope this is the right thing to do?).
Thanks for any support!
I continued looking for helping Wayland to make it across the HDMI port and came across some issues posted on sway (Wayland compositor) github page.
The issue is called "Inconsistent output discovery and enabling" which precisely describes the problem on this machine here.
I followed the devs' guide to create a drm debug log file:
Code: Select all
echo 0xFE | sudo tee /sys/module/drm/parameters/debug # Enable verbose DRM logging
sudo dmesg -C
dmesg -f >dmesg.log & # Continuously write DRM logs to a file
sway -d >sway.log 2>&1 # Run sway and plug in the external monitor, don't move the mouse, exit immediately when sway has started
fg # Kill dmesg with Ctrl+C
echo 0x00 | sudo tee /sys/module/drm/parameters/debug HDMI-A-1 is a miniDisplay Port which works, HDMI-A-2 is the one with no output.
The most interesting lines are these ones:
Code: Select all
[ 2307.280236] i915 0000:00:02.0: [drm:i915_hotplug_work_func] Connector HDMI-A-2 (pin 6) received hotplug event. (retry 0)
...
[ 2307.282577] i915 0000:00:02.0: [drm:intel_hdmi_set_edid] HDMI GMBUS EDID read failed, retry using GPIO bit-banging
Where I realize my personal limits of knowledge on how to proceed. Is this patch already inside the new kernel? These patched files dont exist on my computer: (/etc/src/linux)/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
I also opened an issue on the swaywm/wlroots github page (hope this is the right thing to do?).
Thanks for any support!
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
f1tz,
The patch added the line
Which writes your error message, so I suspect you have the patch.
In your kernel source tree, /usr/src/linux/ the patch changes the file drivers/gpu/drm/i915/intel_hdmi.c
The patch header says
So starting at line, 1573 the old file has 12 lines and the new file has 20 lines.
Knowing that drivers/gpu/drm/i915/intel_hdmi.c is being patched at line 1573, have a look.
Lines starting with a - are removed. lines starting with a + are added.
The text
The patch added the line
Code: Select all
+ DRM_DEBUG_KMS("HDMI GMBUS EDID read failed, retry using GPIO bit-banging\n");Code: Select all
HDMI GMBUS EDID read failed, retry using GPIO bit-banging In your kernel source tree, /usr/src/linux/ the patch changes the file drivers/gpu/drm/i915/intel_hdmi.c
The patch header says
Code: Select all
--- a/drivers/gpu/drm/i915/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/intel_hdmi.c
@@ -1573,12 +1573,20 @@ intel_hdmi_set_edid(struct drm_connector *connector)Knowing that drivers/gpu/drm/i915/intel_hdmi.c is being patched at line 1573, have a look.
Lines starting with a - are removed. lines starting with a + are added.
The text
is interesting. Do you have i2c bit banginig support in your kernel?retry using GPIO bit-banging
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
I trying to find it, but didnt succeed so far. Do you know the exact name of this kernel option?Do you have i2c bit banginig support in your kernel?
https://dpaste.com/4L4GGXLFR
Same heredrivers/gpu/drm/i915/intel_hdmi.c
Does not exist in the directory.https://dpaste.com/4TB65PWFR
Code: Select all
...
intel_device_info.c
intel_device_info.h
intel_device_info.o
intel_dram.c
intel_dram.h
intel_dram.o
intel_gvt.c
intel_gvt.h
intel_memory_region.c
intel_memory_region.h
intel_memory_region.o
intel_pch.c
intel_pch.h
intel_pch.o
intel_pm.c
intel_pm.h
intel_pm.o
intel_region_lmem.c
intel_region_lmem.h
intel_region_lmem.o
intel_runtime_pm.c
intel_runtime_pm.h
intel_runtime_pm.o
intel_sideband.c
intel_sideband.h
intel_sideband.o
intel_uncore.c
intel_uncore.h
intel_uncore.o
intel_wakeref.c
intel_wakeref.h
intel_wakeref.o
intel_wopcm.c
intel_wopcm.h
intel_wopcm.o
...- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
f1tz,
Poke about it those two menus.
We need to see to give any more detail as its chipset dependent and there are lots of chipsets.
Poke about it those two menus.
Code: Select all
# CONFIG_PINCTRL is not set
# CONFIG_GPIOLIB is not setCode: Select all
lspci -nnkRegards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
f1tz,
That's your I2C bus controller. Notice the lack of a kernel driver. It needs
The patch uses i2c and talks about GPIO bit banging, so that may not be enough.
I suspect that CONFIG_GPIOLIB will be required and CONFIG_I2C_GPIO.
You may find the search (/) useful and the toggle hidden options (z) useful in menuconfig.
The driver for that is CONFIG_SPI_INTEL_SPI_PCI but it lets you update the BIOS, so you probably don't want it.
Malicious code could use it too.
Will need CONFIG_THUNDERBOLT if you ever want to use it.
Code: Select all
00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller [8086:02e8]
Subsystem: CLEVO/KAPOK Computer Serial IO I2C Host Controller [1558:1404]Code: Select all
CONFIG_MFD_INTEL_LPSS_PCII suspect that CONFIG_GPIOLIB will be required and CONFIG_I2C_GPIO.
You may find the search (/) useful and the toggle hidden options (z) useful in menuconfig.
Code: Select all
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller [8086:02a4]
Subsystem: CLEVO/KAPOK Computer Comet Lake SPI (flash) Controller [1558:1404]Malicious code could use it too.
Code: Select all
03:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] [8086:15e8] (rev 06)
Subsystem: CLEVO/KAPOK Computer JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] [1558:1404]Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Thanks Neddy.
I enabled both CONFIG_GPIOLIB + CONFIG_I2C_GPIO Kernel options.
CONFIG_THUNDERBOLT is now called CONFIG_USB4, and is enabled now, too.
After that, the missing file from the patch appears, and contains the patched lines.
I recompiled everything and cold booted three times and pastebinned the three dmesg logs, with kernel command line "drm.debug=0x1e log_buf_len=1M" as before.
1. ) with the projector connected with HDMI
2. ) with the projector connected with miniDP
3. ) with the monitor connected with USB-C/DisplayPort
Interestingly, in all three the "GPIO bit-banging" is reserved for the HDMI-A-2 port. All others work.
1.) HDMI
https://paste.c-net.org/UncleanEnforced
Error:
2.) mDP
https://paste.c-net.org/BoneheadEduard
3.) USB-C/Display Port
https://paste.c-net.org/MemoirsKittens
I enabled both CONFIG_GPIOLIB + CONFIG_I2C_GPIO Kernel options.
CONFIG_THUNDERBOLT is now called CONFIG_USB4, and is enabled now, too.
After that, the missing file from the patch appears, and contains the patched lines.
Code: Select all
cd /usr/src/linux-5.11.0-gentoo/drivers/gpu/drm/i915
ls | grep intel
...
intel_hdcp.c
intel_hdcp.h
intel_hdcp.o
intel_hdmi.c
intel_hdmi.h
intel_hdmi.o
...1. ) with the projector connected with HDMI
2. ) with the projector connected with miniDP
3. ) with the monitor connected with USB-C/DisplayPort
Interestingly, in all three the "GPIO bit-banging" is reserved for the HDMI-A-2 port. All others work.
1.) HDMI
https://paste.c-net.org/UncleanEnforced
Error:
Code: Select all
[ 1.833535] i915 0000:00:02.0: [drm:intel_hdmi_set_edid] HDMI GMBUS EDID read failed, retry using GPIO bit-banging
[ 1.833540] i915 0000:00:02.0: [drm:intel_gmbus_force_bit] enabling bit-banging on i915 gmbus dpc. force bit now 1
[ 1.841231] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpc
[ 1.841238] i915 0000:00:02.0: [drm:intel_gmbus_force_bit] disabling bit-banging on i915 gmbus dpc. force bit now 02.) mDP
https://paste.c-net.org/BoneheadEduard
Code: Select all
[ 3.157891] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:103:DP-1] status updated from unknown to disconnected
[ 3.157897] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:103:DP-1] disconnected
[ 3.157903] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:112:HDMI-A-1]
[ 3.157908] i915 0000:00:02.0: [drm:intel_hdmi_detect] [CONNECTOR:112:HDMI-A-1]
[ 3.184663] [drm:drm_add_display_info] Supported Monitor Refresh rate range is 0 Hz - 0 Hz
[ 3.184670] [drm:drm_add_display_info] non_desktop set to 0
[ 3.184674] [drm:drm_add_display_info] HDMI: DVI dual 0, max TMDS clock 150000 kHz
[ 3.185412] usb 1-7: new high-speed USB device number 4 using xhci_hcd
[ 3.187061] [drm:drm_dp_dual_mode_detect] DP dual mode HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
[ 3.188036] [drm:drm_dp_dual_mode_detect] DP dual mode adaptor ID: a0 (err 0)
[ 3.188982] i915 0000:00:02.0: [drm:intel_hdmi_set_edid] DP dual mode adaptor (type 2 HDMI) detected (max TMDS clock: 300000 kHz)
[ 3.188986] [drm:drm_detect_monitor_audio] Monitor has basic audio support
[ 3.188991] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:112:HDMI-A-1] status updated from unknown to connected
[ 3.188997] [drm:drm_add_display_info] Supported Monitor Refresh rate range is 0 Hz - 0 Hz
[ 3.189001] [drm:drm_add_display_info] non_desktop set to 0
[ 3.189005] [drm:drm_add_display_info] HDMI: DVI dual 0, max TMDS clock 150000 kHz
[ 3.189012] [drm:drm_add_edid_modes] ELD monitor LG PROJECTOR
[ 3.189017] [drm:drm_add_edid_modes] HDMI: latency present 0 0, video latency 0 0, audio latency 0 0
[ 3.189022] [drm:drm_add_edid_modes] ELD size 44, SAD count 3
[ 3.189026] [drm:drm_add_display_info] Supported Monitor Refresh rate range is 0 Hz - 0 Hz
[ 3.189030] [drm:drm_add_display_info] non_desktop set to 0
[ 3.189034] [drm:drm_add_display_info] HDMI: DVI dual 0, max TMDS clock 150000 kHz
[ 3.189253] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:112:HDMI-A-1] probed modes :
[ 3.189258] [drm:drm_mode_debug_printmodeline] Modeline "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x48 0x9
https://paste.c-net.org/MemoirsKittens
Code: Select all
[ 12.394096] i915 0000:00:02.0: [drm:intel_dp_detect] [CONNECTOR:103:DP-1]
[ 12.395053] i915 0000:00:02.0: [drm:intel_dp_lttpr_init] LTTPR common capabilities: 14 1e 80 aa 04 00 00 00
[ 12.396581] i915 0000:00:02.0: [drm:intel_dp_lttpr_init] LTTPR 1 PHY capabilities: 03 00 00
[ 12.397770] [drm:drm_dp_read_dpcd_caps] AUX B/DDI B/PHY B: DPCD: 12 14 c4 01 01 00 01 80 02 02 06 00 00 00 00
[ 12.398630] [drm:drm_dp_read_desc] AUX B/DDI B/PHY B: DP sink: OUI 00-00-00 dev-ID HW-rev 0.0 SW-rev 0.0 quirks 0x0000
[ 12.399337] i915 0000:00:02.0: [drm:intel_dp_detect] [ENCODER:102:DDI B/PHY B] MST support: port: yes, sink: no, modparam: yes
[ 12.399345] i915 0000:00:02.0: [drm:intel_dp_print_rates] source rates: 162000, 216000, 270000, 324000, 432000, 540000
[ 12.399349] i915 0000:00:02.0: [drm:intel_dp_print_rates] sink rates: 162000, 270000, 540000
[ 12.399352] i915 0000:00:02.0: [drm:intel_dp_print_rates] common rates: 162000, 270000, 540000
[ 12.411208] [drm:drm_add_display_info] Supported Monitor Refresh rate range is 0 Hz - 0 Hz
[ 12.411214] [drm:drm_add_display_info] non_desktop set to 0
[ 12.411218] [drm:drm_add_display_info] CEA VCDB 0x40
[ 12.411225] i915 0000:00:02.0: [drm:intel_dp_set_edid] [CONNECTOR:103:DP-1] DFP max bpc 0, max dotclock 0, TMDS clock 0-0
[ 12.411230] i915 0000:00:02.0: [drm:intel_dp_set_edid] [CONNECTOR:103:DP-1] YCbCr 4:2:0 allowed? no, YCbCr 4:4:4->4:2:0 conversion? no
[ 12.411234] [drm:drm_detect_monitor_audio] Monitor has basic audio support
[ 12.411933] [drm:drm_dp_get_edid_quirks] DP sink: EDID mfg 38-a3 prod-ID da-2d quirks: 0x0000
[ 12.412628] [drm:drm_add_display_info] Supported Monitor Refresh rate range is 0 Hz - 0 Hz
[ 12.412641] [drm:drm_add_display_info] non_desktop set to 0
[ 12.412689] [drm:drm_add_display_info] CEA VCDB 0x40
[ 12.412695] [drm:drm_add_edid_modes] ELD monitor EA271U
[ 12.412699] [drm:drm_add_edid_modes] ELD size 32, SAD count 1
[ 12.412704] [drm:drm_add_display_info] Supported Monitor Refresh rate range is 0 Hz - 0 Hz
[ 12.412708] [drm:drm_add_display_info] non_desktop set to 0
[ 12.412711] [drm:drm_add_display_info] CEA VCDB 0x40
[ 12.413383] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:103:DP-1] probed modes :
[ 12.413388] [drm:drm_mode_debug_printmodeline] Modeline "3840x2160": 60 533250 3840 3888 3920 4000 2160 2163 2168 2222 0x48 0x9- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
f1tz,
Install x11-misc/read-edid or something similar.
Try which will get you something like ...
The EDID data is binary. It may leave your console in a mess. If that happens, type reset in the console and ignore what appears on the screen.
is probably more user friendly.
Does that read from the HDMI port?
Install x11-misc/read-edid or something similar.
Try
Code: Select all
$ sudo /usr/bin/get-edidCode: Select all
Fhis is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
���������LS90�^5x:�#�UN�'HI�K�����@�����M���p>�0 5�2��V7M4J91S09SL
�DELL P4317Q
�Pc<
Looks like i2c was successful. Have a good day.
:!�N�# �e
�f��p�0 5�2V^���)P0 5�2��Q��p�0 5�2�}9��8@0 :�2��Code: Select all
$ sudo get-edid | parse-edidDoes that read from the HDMI port?
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
This is with external monitor plugged in HDMI:
This is with external monitor plugged in mDP:
Code: Select all
simon@wunderfitz ~ $ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 5
2 potential busses found: 4 6
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one.
256-byte EDID successfully retrieved from i2c bus 4
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier ""
ModelName ""
VendorName "BOE"
# Monitor Manufactured week 18 of 2017
# EDID version 1.4
# Digital Display
DisplaySize 340 190
Gamma 2.20
Option "DPMS" "false"
Modeline "Mode 0" +hsync -vsync
EndSectionCode: Select all
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 5
3 potential busses found: 0 4 6
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one.
256-byte EDID successfully retrieved from i2c bus 0
If this isn't the EDID you were looking for, consider the other potential busses.
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "LG PROJECTOR"
ModelName "LG PROJECTOR"
VendorName "GSM"
# Monitor Manufactured week 1 of 2017
# EDID version 1.3
# Digital Display
DisplaySize 1600 900
Gamma 2.20
Option "DPMS" "false"
Horizsync 30-83
VertRefresh 58-62
# Maximum pixel clock is 160MHz
#Not giving standard mode: 640x480, 60Hz
#Not giving standard mode: 800x600, 60Hz
#Not giving standard mode: 1024x768, 60Hz
#Not giving standard mode: 1152x864, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Extension block found. Parsing...
Modeline "Mode 16" +hsync +vsync
Modeline "Mode 0" +hsync -vsync
Modeline "Mode 1" +hsync +vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 10" 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 12" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 13" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 14" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 15" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 17" +hsync +vsync interlace
Modeline "Mode 18" +hsync +vsync
Option "PreferredMode" "Mode 16"
EndSectionTried a GMBUS script to see if some pins are getting mischanneled from a smiliar issue on gitlab:
Results:
Code tags added to preserve formatting. -- NeddySeageen
Results:
Code: Select all
Probing i2c-0 / i915 gmbus dpb
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 i2c-1 / i915 gmbus dpc
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 i2c-2 / i915 gmbus misc
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 i2c-3 / i915 gmbus dpd
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --- NeddySeagoon
- Administrator
- Posts: 56085
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
f1tz,
Are they the same device?
The first output says
While the second says
so a device was added.
You will need to runwith the different bus numbers to get all the EDID data.
The same device connected to HDMI and DP inThey should be the same. turn would be useful.
They should be identical.
Are they the same device?
The first output says
Code: Select all
2 potential busses found: 4 6
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one. Code: Select all
3 potential busses found: 0 4 6
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one. You will need to run
Code: Select all
$ sudo get-edid | parse-edidThe same device connected to HDMI and DP inThey should be the same. turn would be useful.
They should be identical.
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Both ports are inside the same laptop, but are physically seperated. I dont know if the bridge handels them together, as the mDP is treated as HDMI-A-1 in drm logs, and the HDMI port as HDMI-A-2.
There is a BIOS setting which switches the Displayport from the mDP to the USB-C, but I dont know if this is related to this issue. The HDMI should work in both settings of the BIOS switch as to the manufacturers homepage.
It seems like bus 0 is mDP, bus 4 is eDP, bus 5 is the USB-C DisplayPort.
No idea for 1, 2, 3 and 6, but it seems that both the USB-C and the mDP disappear once they disconnect.
1) monitor in mDP -> bus 0 4 6
2) monitor in HDMI -> bus 4 6
-> *reboots goes to BIOS and switches mDP to TBT*
3) monitor in USB-C DisplayPort -> bus 4 5 6
1) monitor in mDP -> bus 0 4 6
2) monitor in HDMI -> bus 4 6
2) monitor in HDMI -> bus 4 6
3) monitor in USB-C DisplayPort -> bus 4 5 6
Also tried i2cdetect here:
There is a BIOS setting which switches the Displayport from the mDP to the USB-C, but I dont know if this is related to this issue. The HDMI should work in both settings of the BIOS switch as to the manufacturers homepage.
It seems like bus 0 is mDP, bus 4 is eDP, bus 5 is the USB-C DisplayPort.
No idea for 1, 2, 3 and 6, but it seems that both the USB-C and the mDP disappear once they disconnect.
1) monitor in mDP -> bus 0 4 6
2) monitor in HDMI -> bus 4 6
-> *reboots goes to BIOS and switches mDP to TBT*
3) monitor in USB-C DisplayPort -> bus 4 5 6
1) monitor in mDP -> bus 0 4 6
Code: Select all
simon@wunderfitz ~ $ sudo get-edid -b 0 | parse-edid
0
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 0 as per your request.
256-byte EDID successfully retrieved from i2c bus 0
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "LG PROJECTOR"
ModelName "LG PROJECTOR"
VendorName "GSM"
# Monitor Manufactured week 1 of 2017
# EDID version 1.3
# Digital Display
DisplaySize 1600 900
Gamma 2.20
Option "DPMS" "false"
Horizsync 30-83
VertRefresh 58-62
# Maximum pixel clock is 160MHz
#Not giving standard mode: 640x480, 60Hz
#Not giving standard mode: 800x600, 60Hz
#Not giving standard mode: 1024x768, 60Hz
#Not giving standard mode: 1152x864, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Extension block found. Parsing...
Modeline "Mode 16" +hsync +vsync
Modeline "Mode 0" +hsync -vsync
Modeline "Mode 1" +hsync +vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 10" 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 12" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 13" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 14" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 15" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 17" +hsync +vsync interlace
Modeline "Mode 18" +hsync +vsync
Option "PreferredMode" "Mode 16"
EndSectionCode: Select all
sudo get-edid -b 4 | parse-edid
4
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 4 as per your request.
256-byte EDID successfully retrieved from i2c bus 4
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier ""
ModelName ""
VendorName "BOE"
# Monitor Manufactured week 18 of 2017
# EDID version 1.4
# Digital Display
DisplaySize 340 190
Gamma 2.20
Option "DPMS" "false"
Modeline "Mode 0" +hsync -vsync
EndSection
2) monitor in HDMI -> bus 4 6
Code: Select all
sudo get-edid -b 6 | parse-edid
6
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 6 as per your request.
Bus 6 doesn't really have an EDID...
Couldn't find an accessible EDID on this bus.
Attempting to use the classical VBE interface
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function unsupported
Call failed
VBE version 0
VBE string at 0x0 "O"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function unsupported
Call failed
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function unsupported
Call failed
The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again3) monitor in USB-C DisplayPort -> bus 4 5 6
Code: Select all
sudo get-edid -b 5 | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 5 as per your request.
256-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "EA271U"
ModelName "EA271U"
VendorName "NEC"
# Monitor Manufactured week 23 of 2019
# EDID version 1.4
# Digital Display
DisplaySize 600 340
Gamma 2.20
Option "DPMS" "true"
Horizsync 31-140
VertRefresh 30-76
# Maximum pixel clock is 540MHz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1280x800, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1400x1050, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x1200, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1920x1080, 60Hz
#Extension block found. Parsing...
#WARNING: I may have missed a mode (CEA mode 95)
#WARNING: I may have missed a mode (CEA mode 96)
#WARNING: I may have missed a mode (CEA mode 97)
Modeline "Mode 10" -hsync +vsync
Modeline "Mode 0" +hsync -vsync
Modeline "Mode 1" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 2" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 3" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 4" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 5" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 8" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 9" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 11" +hsync +vsync
Modeline "Mode 12" +hsync +vsync
Modeline "Mode 13" +hsync -vsync
Option "PreferredMode" "Mode 10"
EndSectionCode: Select all
simon@wunderfitz ~ $ sudo i2cdetect -l
i2c-3 i2c i915 gmbus dpd I2C adapter
i2c-1 i2c i915 gmbus dpc I2C adapter
i2c-6 smbus SMBus I801 adapter at 6040 SMBus adapter
i2c-4 i2c AUX A/DDI A/PHY A I2C adapter
i2c-2 i2c i915 gmbus misc I2C adapter
i2c-0 i2c i915 gmbus dpb I2C adapter
i2c-5 i2c AUX B/DDI B/PHY B I2C adapter