I’m top-editing this as I have worked around it, and though interesting it is no longer blocking me.
I manually backed off to kernel 570.55, then reinstalled displaylink.
That brought my 2 screens back.
Though I’m confused because I thought the compilation errors were related to the altered kernel headers which came with 611.11 and I had understood they were updated permanently now.
So I have a working system again, though I don’t understand how.
I would still like to move to the current kernel - so knowing how long I will be blocked from doing that would still be useful.
————————
I allowed a kernel upgrade, and now I’ve lost my displaylink screens.
$uname -r
5.14.0-611.11.1.el9_7.x86_64
$cat /etc/rocky-release
Rocky Linux release 9.7 (Blue Onyx)
On booting with the new kernel the 2 displaylink screens are blank.
I see this is because displaylink-driver.service is not running.
Tracking back I see
modprobe evdi
failed during its startup.
I see the evdi module is stored by-kernel-version - which I guess means I have to remove and re-install the displaylink rpm, which will recompile evdi into the correct directory for the new kernel ?
But when I try that it barfs rebuilding evdi.
I eventually tracked that to this bug report…
So… clearly someone has patched the fault, and somewhere in the multiverse is code which will allow me to create a usable evdi, and then, presumably, I will get my 2 screens back.
As a dumb user I assume that would mean me waiting for someone to update and reissue the displaylink rpm in the ‘standard repo’, to include the patch.
How long can I expect such a process to take?
If more than a few days, can anyone tell me how I can pull the patched evdi build stuff and do it for myself?