|
09-18-2020, 01:27 AM | #1 |
Junior Member
Join Date: Sep 2020
Posts: 3
|
Ubuntu 20.04 Install error 5.2.14
when running the install script receive
Code:
Verifying archive integrity... 100% All good. Uncompressing DisplayLink Linux Driver 5.2.14 100% DisplayLink Linux Software 5.2.14 install script called: install Distribution discovered: Ubuntu 20.04 LTS Installing Configuring EVDI DKMS module Registering EVDI kernel module with DKMS Building EVDI kernel module with DKMS ERROR (code 3): Failed to build evdi/5.2.14. Consult /var/lib/dkms/evdi/5.2.14/build/make.log for details.. The log file has this at the end... Code:
for m in drivers/net/tun.ko drivers/net/xen-netfront.ko; do echo $m; done; \ cat /dev/null drivers/net/dsa/modules.builtin drivers/net/ethernet/modules.builtin drivers/net/fddi/modules.builtin drivers/net/hamradio/modules.builtin drivers/net/phy/modules.builtin drivers/net/ppp/modules.builtin drivers/net/slip/modules.builtin drivers/net/wan/modules.builtin drivers/net/wireless/modules.builtin) > drivers/net/modules.builtin (for m in ; do echo $m; done; \ cat /dev/null drivers/acpi/modules.builtin drivers/amba/modules.builtin drivers/android/modules.builtin drivers/ata/modules.builtin drivers/auxdisplay/modules.builtin drivers/base/modules.builtin drivers/block/modules.builtin drivers/bus/modules.builtin drivers/cdrom/modules.builtin drivers/char/modules.builtin drivers/char/ipmi/modules.builtin drivers/clk/modules.builtin drivers/clocksource/modules.builtin drivers/connector/modules.builtin drivers/cpufreq/modules.builtin drivers/cpuidle/modules.builtin drivers/crypto/modules.builtin drivers/dax/modules.builtin drivers/devfreq/modules.builtin drivers/dma/modules.builtin drivers/dma-buf/modules.builtin drivers/edac/modules.builtin drivers/eisa/modules.builtin drivers/extcon/modules.builtin drivers/firewire/modules.builtin drivers/firmware/modules.builtin drivers/gpio/modules.builtin drivers/gpu/modules.builtin drivers/hwmon/modules.builtin drivers/hwspinlock/modules.builtin drivers/hwtracing/intel_th/modules.builtin drivers/i2c/modules.builtin drivers/i3c/modules.builtin drivers/idle/modules.builtin drivers/input/modules.builtin drivers/input/serio/modules.builtin drivers/iommu/modules.builtin drivers/irqchip/modules.builtin drivers/isdn/modules.builtin drivers/leds/modules.builtin drivers/lightnvm/modules.builtin drivers/macintosh/modules.builtin drivers/mailbox/modules.builtin drivers/md/modules.builtin drivers/media/modules.builtin drivers/memory/modules.builtin drivers/message/modules.builtin drivers/mfd/modules.builtin drivers/misc/modules.builtin drivers/mmc/modules.builtin drivers/net/modules.builtin drivers/nfc/modules.builtin drivers/nvdimm/modules.builtin drivers/nvme/modules.builtin drivers/nvmem/modules.builtin drivers/opp/modules.builtin drivers/pci/modules.builtin drivers/perf/modules.builtin drivers/phy/modules.builtin drivers/pinctrl/modules.builtin drivers/platform/modules.builtin drivers/pnp/modules.builtin drivers/power/modules.builtin drivers/powercap/modules.builtin drivers/pps/modules.builtin drivers/ptp/modules.builtin drivers/pwm/modules.builtin drivers/rapidio/modules.builtin drivers/ras/modules.builtin drivers/regulator/modules.builtin drivers/remoteproc/modules.builtin drivers/reset/modules.builtin drivers/rtc/modules.builtin drivers/scsi/modules.builtin drivers/sfi/modules.builtin drivers/soc/modules.builtin drivers/spi/modules.builtin drivers/staging/modules.builtin drivers/thermal/modules.builtin drivers/tty/modules.builtin drivers/usb/modules.builtin drivers/vfio/modules.builtin drivers/video/modules.builtin drivers/virt/modules.builtin drivers/virtio/modules.builtin drivers/vme/modules.builtin drivers/watchdog/modules.builtin drivers/xen/modules.builtin) > drivers/modules.builtin make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-29-generic' make: *** [Makefile:22: all] Error 2 |
09-18-2020, 02:56 PM | #2 |
Junior Member
Join Date: Sep 2020
Posts: 4
|
Exact same problem
I just contacted support with this exact issue. Attempting to get Displaylink running on Raspbian OS buster on a Rpi 4. In addition to the listed issue, the Displaylink 3.1.0.34 for Ubuntu cannot be run because it is not UTF-8 valid
|
09-18-2020, 05:12 PM | #3 |
Junior Member
Join Date: Sep 2020
Posts: 3
|
Please let me know what you find out. My plan is to use a virtual machine to drive this given that passing through a traditional video card on ESX has been basically disabled.
|
09-18-2020, 05:57 PM | #4 |
Junior Member
Join Date: Sep 2020
Posts: 4
|
Still waiting
Waiting on support to get back to me, i'll post their reply if i ever get one. Hopefully there will also be some help from the community too, though
|
09-20-2020, 02:09 PM | #5 |
Junior Member
Join Date: Sep 2020
Posts: 4
|
Legacy Buster
I am switching to a legacy version of Raspbian OS, I'll post here if that solves the issue
|
09-20-2020, 03:11 PM | #6 |
Junior Member
Join Date: Sep 2020
Posts: 4
|
solution
download a fresh install of last February's Buster (https://downloads.raspberrypi.org/ra...an-2020-02-14/)
DO NOT UPDATE when you log into Raspbian OS it will now accept the necessary kernels and run Displaylink Ubuntu installer 5.2.14 |
09-21-2020, 05:17 AM | #7 | |
Junior Member
Join Date: Sep 2020
Posts: 8
|
silly question: where and how to contact support?
Quote:
I can't find any link/email/webpage to contact support neither. all i can find is a chat windows. thanks in advance |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|