![]() From the log sfiles, it became clear to me that the kernel was bugging the compatibility with the EVDI drivers. This made me vigurously looking what was going on. When re-installing the Pop!_OS 22.04_14 ISO, sporting the 5.19.0-76051900-generic kernel again No problem! Linux kernel 6.x - DisplayLink, internal laptop display only!Īs a new version, Pop!_OS 22.04_15, running the 6.0.2-7606002-generic kernel, was released no additional monitors! Linux kernel 5.x - DisplayLink working as expected. After diggin around I discovered that the EVDI version isn’t working anymore after the kernel updates. That real culprit has to do with the kernel being updated from 5.19.0-x to 6.0.2-x and the display part of the drive. I noticed, during experimenting with the different 22.04 releases of Pop!_OS, the DisplayLink device wasn’t displaying to the external monitors anymore althought the other functionality (USB, Ethernet and audio) was working as expected. ![]() Again no dice… re-applying the procedure, as noted below, fixed the issue again. Pop!_OS updated the kernel again, this time to version 6.0.6-76060006-generic. Possible solution, suggested by Daniel C., is using kernelstub to assign the 6.0.2 kernel to you system again Kernel 6.2 broke the EVDI again: awaiting for a fix to be implemented. Updates, having the most recent on top, on the current status of the EVDI trouble. It took me a little while to realize what the actual problem is. ![]() This happened by an upgrade package overnight (around 25th of October 2022). This is really annoying as all of a ‘sudden’ my workstations which sport Pop!_OS 22.04 LTS wouldn’t work with external monitors, connected using a DisplayLink device, anymore. Ubuntu 14.04.1, 3.19.0-9-generic kernel, Intel i7-4770R, Iris Pro 5200, Mimo USB screen.Kernel 6.x broke the support for the EVDI which is shipped with current release (5.6.1) of the DisplayLink drivers for Ubuntu. The Monitor section can be omitted if your monitor has a proper EDID. However, I wanted a working nf so I could tweak / use with Mali (ARM) on an Odroid, which requires a nfīusID and kmsdev will need tweaking for your particular setup, see lspci and /sys/class/drm/. Provider 1: id: 0xe8 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting Provider 0: id: 0x48 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 5 associated providers: 1 name:Intel Out of the box, if plugged in before boot, my screen works with no nf xrandr -listproviders fbdev doesn't give you hardware acceleration. The new DisplayLink driver (udldrmfb) piggy backs off your graphics card, in my case, I wish to use the Intel DRI/OpenGL, yet use USB for display. So my question is: how can I enable the output on my second (displaylink) card? Or alternatively, where can I find further info (since web-searches lead me nowhere because the "modesetting" keyword ends up matching lots of irrelevant threads about other drivers)? Gbm: Last dlopen error: /usr/lib/dri/udl_dri.so: cannot open shared object file: No such file or directory Gbm: failed to open any driver (search paths /usr/lib/i386-linux-gnu/dri:$/dri:/usr/lib/dri) The only other hint of possible problem I see is when I start "xinit" I get: pci id for fd 10: 8086:8108, driver (null) The Xorg.0.log file doesn't have any special (WW) or (EE), except for the expected glamor/aiglx failures. Provider 1: id: 0x41 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting Provider 0: id: 0x77 cap: 0x0 crtcs: 2 outputs: 1 associated providers: 0 name:modesetting Screen 0: minimum 320 x 200, current 1200 x 1600, maximum 4096 x 4096ĭVI-0 connected 1200x1600+0+0 left (normal left inverted right x axis y axis) 432mm x 324mm The other card is detected (as evidenced by "xrandr -list-providers" output), but "not enough" (as evidenced by the fact that only one output shows up in "xrandr"): % xrandr The X server starts up OK but only the main (i.e. So I'm using a trivial nf with just: Section "Device" The primary graphics card is the dreaded Poulsbo, so there's no hardware acceleration to worry about (makes no difference in Emacs anyway -). I have a USB2 displaylink adapter connected to my machine so as to make use of that nice second monitor I have here.
0 Comments
Leave a Reply. |