You are not logged in.

Pages: 1

#1 2023-02-06 09:02:34

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Dell Latitude 3420 - DisplayPort MST not working anymore

I have a Dell Latitude 3420 (https://wiki.archlinux.org/title/Dell_Latitude_3420). I'm using a USB type-C hub with 2 displays (HDMI) linked to the laptop via USB type-C (DisplayPort capable port). I was working great in the past but now it is not working anymore. I still have the built-in monitor + an external one directly wired in HDMI.

I think this error is clearly related to the issue:

kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful

This is happening with both linux kernel 6.1.9.arch1-1 and 5.15.91-1-lts. I searched a bit for this error but didn't see much about it.

I have not install xf86-video-intel, xf86-video-vesa nor xf86-video-fbdev so I should be relying on Kernel mode setting (KMS).

Offline

#2 2023-02-06 10:34:29

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

journalctl -b | grep drm

févr. 06 09:37:36 norarch systemd[1]: Starting Load Kernel Module drm...
févr. 06 09:37:36 norarch systemd[1]: modprobe@drm.service: Deactivated successfully.
févr. 06 09:37:36 norarch systemd[1]: Finished Load Kernel Module drm.
févr. 06 09:37:36 norarch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 09:37:36 norarch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 09:37:36 norarch kernel: audit: type=1130 audit(1675672656.649:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 09:37:36 norarch kernel: audit: type=1131 audit(1675672656.649:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 09:37:38 norarch kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
févr. 06 09:37:38 norarch kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
févr. 06 09:37:38 norarch kernel: fbcon: i915drmfb (fb0) is primary device
févr. 06 09:37:39 norarch kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
févr. 06 09:37:42 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:42 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:42 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:43 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:43 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:54 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:55 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:55 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 09:37:58 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful

Offline

#3 2023-02-06 11:52:53

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Could be some kind of timing issue, are you using early KMS start  ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#4 2023-02-06 12:45:27

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

I'm not using early start. Where should I insert i915? In https://wiki.archlinux.org/title/Kernel … mkinitcpio the text says HOOKS and the code examples says MODULES.

MODULES=()
HOOKS=(base udev autodetect keyboard keymap consolefont modconf block encrypt lvm2 resume filesystems fsck)

Offline

#5 2023-02-06 13:00:45

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

If you want the easy way (and don't mind having all in-tree kms modules added to the initramfs)  add kms to the HOOKS array.

Incase you prefer only adding necessary things, add i915 to the MODULES array.
(Choose either one, doing both adds nothing)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#6 2023-02-06 14:46:16

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

I have added `i915` to the `MODULES` array and rebuilt all initramfs with `sudo mkinitcpio --allpresets`. But nothing seems to have changed.

$ lsmod | grep -i i915
i915                 3481600  85
drm_buddy              20480  1 i915
intel_gtt              28672  1 i915
video                  65536  3 dell_wmi,dell_laptop,i915
drm_display_helper    212992  1 i915
cec                    81920  2 drm_display_helper,i915
ttm                    94208  1 i915

$ journalctl -b | grep drm                                                           
févr. 06 15:42:38 norarch kernel: ACPI: bus type drm_connector registered
févr. 06 15:42:38 norarch kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
févr. 06 15:42:38 norarch kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
févr. 06 15:42:38 norarch kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
févr. 06 15:42:38 norarch kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
févr. 06 15:42:38 norarch kernel: fbcon: i915drmfb (fb0) is primary device
févr. 06 15:42:38 norarch kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
févr. 06 15:42:38 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 15:42:38 norarch systemd[1]: Starting Load Kernel Module drm...
févr. 06 15:42:38 norarch systemd[1]: modprobe@drm.service: Deactivated successfully.
févr. 06 15:42:38 norarch systemd[1]: Finished Load Kernel Module drm.
févr. 06 15:42:38 norarch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 15:42:38 norarch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 15:42:38 norarch kernel: audit: type=1130 audit(1675694558.750:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 15:42:38 norarch kernel: audit: type=1131 audit(1675694558.750:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 06 15:42:41 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 15:42:41 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 15:42:52 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 15:42:53 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 15:42:53 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
févr. 06 15:42:56 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful

Offline

#7 2023-02-07 08:36:50

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Even before entering my LUKS passphrase I see the following errors on my TTY:

usb 3-2: device descriptor read/64, error -71                                                                                                                                      
i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful                                                                                                                        
i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful                                                                                                                        
i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful

I wonder if it's a compatibility issue with some new updates or a USB type-C hub defect. However power delivery and ethernet still working through the hub, only display stopped.
Instead of the two displays connected to the hub I see "Doble Engineering Company VMM2300 ROM".

Offline

#8 2023-02-07 11:50:27

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Does the behaviour change if you boot up with the extra monitors disconnected / switched off and only switch them on until after startup has finished ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#9 2023-02-08 14:38:40

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Lone_Wolf wrote:

Does the behaviour change if you boot up with the extra monitors disconnected / switched off and only switch them on until after startup has finished ?

I'll have to test that but for now I can tell it's specific to the hub because I tested with another model of hub and I don't have the issue.

Offline

#10 2023-02-10 08:10:17

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Branching the bugging hub after boot make the laptop hanging 30sec but finally works without kernel error.

Offline

#11 2023-02-11 12:12:46

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

That does suggest timing plays a role in this but there's more going on.

What is the exact brand & model of the hub ?

Please post dmesg &  journal (run both as root) from such a boot ( where it works when connected after booting) .

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#12 2023-02-13 08:37:12

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Unfortunately, it seems the hub nearly died and must have a hardware issue.

Boot A (the other day): I just plugged the hub after boot and it worked.

Boot B (the other day): I just plugged the hub after boot and nothing happens, not working.

Boot C (today): I just plugged the hub after boot and it worked while there was only one display attached to it and made the OS freeze after branching the second display.

Boot D (today): I just plugged the hub after boot and nothing happens, not working.

I'm not able to reproduce a working case.

Last edited by noraj2 (2023-02-13 08:53:34)

Offline

#13 2023-02-13 08:48:32

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

Ok I was able to isolate a reproducible scenario.

Always after boot, if I plug the hub to the laptop while two displays are plugged on it, it won't work and nothing will happen. But if I plug the hub to the laptop while only one display is plugged to the hub it will work but a freeze will occurs as soon as I'll plug the second display to the hub. Note: plugging only one display will work but only during 10 seconds then the hub will disappear (screen, network, power).

I lauched `journalctl -b -f` while branching the second display to the hub and was able to see this before the freeze:

févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper: RRNotify_OutputChange
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Timestamp:  573176
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Output:  2054
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         CRTC:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Mode:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Connection:  "Connected"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Subpixel Order:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandROutput 2054 update 
                                                                    m_connected: 1 
                                                                    m_crtc QObject(0x0) 
                                                                    CRTC: 0 
                                                                    MODE: 0 
                                                                    Connection: 0 
                                                                    Primary: false
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Output 2054 : connected = true , enabled = false
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper: RRScreenChangeNotify
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Timestamp:  573176
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Config_timestamp:  628351
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Window: 44040197
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Root: 1974
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Size ID: 65535
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Size:  5760 1080
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         SizeMM:  1520 285
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper: RRNotify_OutputChange
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Timestamp:  573176
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Output:  2054
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         CRTC:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Mode:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Connection:  "Connected"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Subpixel Order:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandROutput 2054 update 
                                                                    m_connected: 0 
                                                                    m_crtc QObject(0x0) 
                                                                    CRTC: 0 
                                                                    MODE: 0 
                                                                    Connection: 0 
                                                                    Primary: false
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Output 2054 : connected = true , enabled = false

After rebooting I'm able the access the full trace since the second display was plugged with sudo journalctl -b -1:

févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper: RRNotify_OutputChange
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Timestamp:  573176
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Output:  2054
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         CRTC:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Mode:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Connection:  "Connected"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Subpixel Order:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandROutput 2054 update
                                                                    m_connected: 1
                                                                    m_crtc QObject(0x0)
                                                                    CRTC: 0
                                                                    MODE: 0
                                                                    Connection: 0
                                                                    Primary: false
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Output 2054 : connected = true , enabled = false
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper: RRScreenChangeNotify
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Timestamp:  573176
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Config_timestamp:  628351
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Window: 44040197
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Root: 1974
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Size ID: 65535
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Size:  5760 1080
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         SizeMM:  1520 285
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper: RRNotify_OutputChange
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Timestamp:  573176
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Output:  2054
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         CRTC:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Mode:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Connection:  "Connected"
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xcb.helper:         Subpixel Order:  0
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandROutput 2054 update
                                                                    m_connected: 0
                                                                    m_crtc QObject(0x0)
                                                                    CRTC: 0
                                                                    MODE: 0
                                                                    Connection: 0
                                                                    Primary: false
févr. 13 09:38:23 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Output 2054 : connected = true , enabled = false
févr. 13 09:38:24 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Emitting configChanged()
févr. 13 09:38:24 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandR::setConfig
févr. 13 09:38:24 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Requested screen size is QSize(5760, 2160)
févr. 13 09:38:24 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Needed CRTCs:  4
févr. 13 09:38:24 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Actions to perform:
                                                                    Primary Output: false
févr. 13 09:38:24 norarch kscreen_backend_launcher[1159]: kscreen.xrandr:         Change Screen Size: true
...skipping...
                                                                    Free: true
                                                                    Mode: 0
                                                                    Possible outputs: QVector(66, 67, 68, 69, 2054, 2055, 2056)
                                                                    Connected outputs: QVector()
                                                                    Geometry: QRect(0,0 0x0)
févr. 13 09:38:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: RRSetCrtcConfig (enable output)
                                                                    Output: 2054 ( "DP-1-1" )
                                                                    New CRTC: 63
                                                                    Pos: QPoint(0,0)
                                                                    Mode: KScreen::Mode(Id: "153" , Size: QSize(1920, 1080) @ 60 ) Preferred: "153"
                                                                    Rotation: KScreen::Output::None
févr. 13 09:38:25 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for ACT sent
févr. 13 09:38:25 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:38:28 norarch plasma_waitforname[4628]: org.kde.knotifications: WaitForName: Service was not registered within timeout
févr. 13 09:38:28 norarch dbus-daemon[937]: [session uid=1000 pid=937] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
févr. 13 09:38:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] flip_done timed out
févr. 13 09:38:44 norarch kernel: ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
févr. 13 09:38:45 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:38:45 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] commit wait timed out
févr. 13 09:38:45 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:38:55 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] flip_done timed out
févr. 13 09:39:05 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:39:05 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] commit wait timed out
févr. 13 09:39:15 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:39:15 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:346:DP-3] commit wait timed out
févr. 13 09:39:15 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandRCrtc  63  m_timestamp update  572677  =>  630092
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr:         Result:  0  timestamp:  630092
févr. 13 09:39:25 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] flip_done timed out
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandROutput 2054 update
                                                                    m_connected: 0
                                                                    m_crtc QObject(0x0)
                                                                    CRTC: 63
                                                                    MODE: 153
                                                                    Connection: 0
                                                                    Primary: false
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Connected output 2054 to CRTC 63
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: RRSetScreenSize
                                                                    DPI: 96.2526
                                                                    Size: QSize(5760, 2160)
                                                                    SizeMM: QSize(1520, 570)
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Output 66 has no CRTC, falling back to enableOutput()
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: QMap((62, XRandRCrtc(0x559cafea10a0))(63, XRandRCrtc(0x559cafea0a70))(64, XRandRCrtc(0x559cafea12d0))(65, XRandRCrtc(0x559cafea39b0)))
févr. 13 09:39:28 norarch systemd-resolved[669]: wlp0s20f3: Bus client set DNS server list to: 192.168.1.254, 1.1.1.1, 1.0.0.1
févr. 13 09:39:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:39:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] commit wait timed out
févr. 13 09:39:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:39:52 norarch systemd-logind[695]: Power key pressed short.
...skipping...
                                                                    Free: true
                                                                    Mode: 0
                                                                    Possible outputs: QVector(66, 67, 68, 69, 2054, 2055, 2056)
                                                                    Connected outputs: QVector()
                                                                    Geometry: QRect(0,0 0x0)
févr. 13 09:38:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: RRSetCrtcConfig (enable output)
                                                                    Output: 2054 ( "DP-1-1" )
                                                                    New CRTC: 63
                                                                    Pos: QPoint(0,0)
                                                                    Mode: KScreen::Mode(Id: "153" , Size: QSize(1920, 1080) @ 60 ) Preferred: "153"
                                                                    Rotation: KScreen::Output::None
févr. 13 09:38:25 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for ACT sent
févr. 13 09:38:25 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:38:28 norarch plasma_waitforname[4628]: org.kde.knotifications: WaitForName: Service was not registered within timeout
févr. 13 09:38:28 norarch dbus-daemon[937]: [session uid=1000 pid=937] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
févr. 13 09:38:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] flip_done timed out
févr. 13 09:38:44 norarch kernel: ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
févr. 13 09:38:45 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:38:45 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] commit wait timed out
févr. 13 09:38:45 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:38:55 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] flip_done timed out
févr. 13 09:39:05 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:39:05 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] commit wait timed out
févr. 13 09:39:15 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:39:15 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:346:DP-3] commit wait timed out
févr. 13 09:39:15 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandRCrtc  63  m_timestamp update  572677  =>  630092
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr:         Result:  0  timestamp:  630092
févr. 13 09:39:25 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] flip_done timed out
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: XRandROutput 2054 update
                                                                    m_connected: 0
                                                                    m_crtc QObject(0x0)
                                                                    CRTC: 63
                                                                    MODE: 153
                                                                    Connection: 0
                                                                    Primary: false
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Connected output 2054 to CRTC 63
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: RRSetScreenSize
                                                                    DPI: 96.2526
                                                                    Size: QSize(5760, 2160)
                                                                    SizeMM: QSize(1520, 570)
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: Output 66 has no CRTC, falling back to enableOutput()
févr. 13 09:39:25 norarch kscreen_backend_launcher[1159]: kscreen.xrandr: QMap((62, XRandRCrtc(0x559cafea10a0))(63, XRandRCrtc(0x559cafea0a70))(64, XRandRCrtc(0x559cafea12d0))(65, XRandRCrtc(0x559cafea39b0)))
févr. 13 09:39:28 norarch systemd-resolved[669]: wlp0s20f3: Bus client set DNS server list to: 192.168.1.254, 1.1.1.1, 1.0.0.1
févr. 13 09:39:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
févr. 13 09:39:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:167:pipe B] commit wait timed out
févr. 13 09:39:35 norarch kernel: i915 0000:00:02.0: [drm] *ERROR* Potential atomic update failure on pipe B
févr. 13 09:39:52 norarch systemd-logind[695]: Power key pressed short.

Last edited by noraj2 (2023-02-13 08:54:32)

Offline

#14 2023-02-13 09:03:34

noraj2
Member
From: France, Europe
Registered: 2022-02-09
Posts: 19

Re: Dell Latitude 3420 - DisplayPort MST not working anymore

The hub is a Novoo (brand) NVHUBGY11PDNS (model). There is more info on Amazon than on the brand website and I found no spec sheet online.

Offline

Pages: 1

Board footer

Powered by FluxBB