Make error Bad return status for module build on kernel #975
Comments
|
I should note that I ran In either case, this is the output when I log in to an x11 session: |
|
Also -- not sure how relevant this is, but when I try to install, the message says: However, on my system there is no
It says: I could be barking up the wrong tree with this, but it seems like it could be related to the issue here? |
|
Update: I was able to work around this by hard-coding the Here's the quick and dirty change to # Get latest versions
versions=$(wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep "<p>Release: " | head -n 2 | perl -pe '($_)=/([0-9]+([.][0-9]+)+(\ Beta)*)/; exit if $. > 1;')
# if versions contains "Beta", try to download previous version
if [[ $versions =~ Beta ]]; then
- version=$(wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep "<p>Release: " | head -n 2 | perl -pe '($_)=/([0-9]+([.][0-9]+)+(?!\ Beta))/; exit if $. > 1;')
+ # version=$(wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep "<p>Release: " | head -n 2 | perl -pe '($_)=/([0-9]+([.][0-9]+)+(?!\ Beta))/; exit if $. > 1;')
+ version="6.0"
dlurl="https://www.synaptics.com/$(wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep -B 2 $version'-Release' | perl -pe '($_)=/<a href="\/([^"]+)"[^>]+class="download-link"/')"
driver_url="https://www.synaptics.com/$(wget -q -O - ${dlurl} | grep '<a class="no-link"' | head -n 1 | perl -pe '($_)=/href="\/([^"]+)"/')"
else
- version=`wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep "<p>Release: " | head -n 1 | perl -pe '($_)=/([0-9]+([.][0-9]+)+)/; exit if $. > 1;'`
+ # version=`wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep "<p>Release: " | head -n 1 | perl -pe '($_)=/([0-9]+([.][0-9]+)+)/; exit if $. > 1;'`
+ version="6.0"
dlurl="https://www.synaptics.com/$(wget -q -O - https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu | grep -B 2 $version'-Release' | perl -pe '($_)=/<a href="\/([^"]+)"[^>]+class="download-link"/')"
driver_url="https://www.synaptics.com/$(wget -q -O - ${dlurl} | grep '<a class="no-link"' | head -n 1 | perl -pe '($_)=/href="\/([^"]+)"/')"
fiIf you're going to try this yourself, copy the version number the script reports when it tries to install the display link driver, and then check the Legacy Drivers section of the release page to find the next-to-most-recent release, and use that when you modify the shell script. It's worth noting that for me, with driver version However, when I switched to Wayland, everything works again as it used to, except the dock now also works correctly. I'm leaving this issue open (if that's okay) because I'd still like to understand why using version At the very least, I think it would be worth letting the user manually select the version if they so choose, either via a prompt or a command line option, and then add a note in the Common issues page to try a previous version if you encounter the |
|
This is the first workaround that works for me. And it also explains why a few of my users who installed a few months ago, don't have any issues. They're simply still on 6.0. |
|
Hotfix fork with somewhat reasonable usability: |
|
The workaround worked under LMDE (same kernel), and I finally got it to install evdi ok (see debug info below), BUT ... seems to be sending a signal to the monitor, cycles periodically and monitor responds with "no signal detected" then apparently gets a signal, but never detected under display settings. Any ideas? I had an HDMI monitor plugged in while running the debug param of the modified displaylink-debian.sh script. Worth mentioning I have Secure Boot on and enabled, but no run of mokutil happened, as it did reliably with Ubuntu and derivatives (actually got Pop!Os to load the DD driver and even boot under Secure Boot!) I do wish there was a way to get evdi 1.14.7 to install independently of the displaylink package, but I guess it's "their" package, even though it's open source and distributed by Debian. |
|
The 6.0 version of displaylink and Secure Boot evidently don't get along, even if |
|
Yeah, and I'm encountering visual glitches using driver version 6.0 on my debian system, both on the software and hardware level, that did not occur before installing these drivers. They work well enough but for anyone reading this just know that this is an imperfect solution. I'm just a web developer so there's a limit what I can understand about what's going wrong here, but again if anyone reading this has more experience with doing that kind of work, it would be great if we could at least identify the underlying issues here. It's dismaying (though completely understandable) that modern linux desktops still have to deal with basic compatibility issues like this. |
|
We tested Displaylink versions 6.0 and 6.1 on Secureboot without any issue; however we may have hooked dkms module signing with our platform key in a way that Synaptics accidentally doesn't choke on. After a brief affair with my forked repository (above) and Displaylink 6.0, we started to use Adnan's installer with Displaylink 6.1 as-is, with the Debian Backport Kernel 6.11, which is completely beyond the Linux 6.1/6.2 situation with evdi. |
I am getting the same error listed on the common errors page.
However, running the suggested solution does not resolve the issue. Running the install script results in the same error.
Debug info:
The text was updated successfully, but these errors were encountered: