Fedora 41 on aarch64

[< XML Suplex >]

After running the 5.8 install script I was

• informed that the install was successful
• prompted to reboot

Rebooting did not lead to a signal. The same thing happened with 6.1

Now these scripts return the following warnings.

sudo sh displaylink-driver-5.8.0-63.33.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 5.8.0-63.33  100%  
Distribution discovered: "Fedora Linux Asahi Remix 41 (KDE Plasma)"
WARNING: Version 1.14.7 of EVDI kernel module is already running.
Please uninstall all other versions of DisplayLink Linux Software before attempting to install.
Installation terminated.

sudo sh displaylink-driver-6.1.0-17.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 6.1.0  100%  
Distribution discovered: "Fedora Linux Asahi Remix 41 (KDE Plasma)"
WARNING: This is not an officially supported distribution.
Please use DisplayLink Forum for getting help if you find issues.
WARNING: Version 1.14.7 of EVDI kernel module is already running.
Please uninstall all other versions of DisplayLink Linux Software before attempting to install.
Installation terminated.

[< XML Suplex >]

$ sudo sh displaylink-driver-6.1.0-17.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 6.1.0  100%
Distribution discovered: "Fedora Linux Asahi Remix 41 (KDE Plasma)"
WARNING: This is not an officially supported distribution.
Please use DisplayLink Forum for getting help if you find issues.
WARNING: Version 1.14.7 of EVDI kernel module is already running.
Please uninstall all other versions of DisplayLink Linux Software before attempting to install.
Installation terminated.

$ sudo sh displaylink-driver-6.1.0-17.run uninstall
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 6.1.0  100%
Distribution discovered: "Fedora Linux Asahi Remix 41 (KDE Plasma)"
WARNING: This is not an officially supported distribution.
Please use DisplayLink Forum for getting help if you find issues.

Uninstalling

[ Removing EVDI from kernel tree, DKMS, and removing sources. ]
make: Entering directory '/tmp/tmp.9sEB2YqP0x/module'
dkms remove evdi/1.14.7 --all

Module evdi-1.14.7 for kernel 6.11.6-401.asahi.fc41.aarch64+16k (aarch64):
Before uninstall, this module version was ACTIVE on this kernel.
Deleting /lib/modules/6.11.6-401.asahi.fc41.aarch64+16k/extra/evdi.ko.xz
Running depmod.... done.

Deleting module evdi-1.14.7 completely from the DKMS tree.
rm -f -rf /usr/src/evdi-1.14.7
make: Leaving directory '/tmp/tmp.9sEB2YqP0x/module'
Stopping displaylink-driver systemd service
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
* A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
* A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
* A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
* In case of template units, the unit is meant to be enabled with some
  instance name specified.
[ Removing suspend-resume hooks ]
[ Removing udev rule ]
[ Removing Core folder ]

Uninstallation steps complete.
Please note that the evdi kernel module is still in the memory.
A reboot is required to fully complete the uninstallation process.

$ sudo sh displaylink-driver-6.1.0-17.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 6.1.0  100%
Distribution discovered: "Fedora Linux Asahi Remix 41 (KDE Plasma)"
WARNING: This is not an officially supported distribution.
Please use DisplayLink Forum for getting help if you find issues.

Installing
[ Installing EVDI ]
[[ Installing EVDI DKMS module ]]

Sign command: /lib/modules/6.11.6-401.asahi.fc41.aarch64+16k/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Creating symlink /var/lib/dkms/evdi/1.14.7/source -> /usr/src/evdi-1.14.7

Cleaning build area... done.
Building module(s)... done.
Signing module /var/lib/dkms/evdi/1.14.7/build/evdi.ko
Cleaning build area... done.

Installing /lib/modules/6.11.6-401.asahi.fc41.aarch64+16k/extra/evdi.ko.xz
Running depmod.... done.
[[ Installing EVDI library ]]
make: Entering directory '/tmp/tmp.qg7q5ZQM9K/evdi/library'
cc -I../module -std=gnu99 -fPIC -D_FILE_OFFSET_BITS=64  $(pkg-config --cflags-only-I libdrm)   -c -o evdi_lib.o evdi_lib.c
cc -I../module -std=gnu99 -fPIC -D_FILE_OFFSET_BITS=64  $(pkg-config --cflags-only-I libdrm)   -c -o evdi_procfs.o evdi_procfs.c
cc evdi_lib.o evdi_procfs.o -shared -Wl,-soname,libevdi.so.1 -o libevdi.so.1.14.7 -lc -lgcc
cp libevdi.so.1.14.7 libevdi.so
ln -sf libevdi.so.1.14.7 libevdi.so.1
make: Leaving directory '/tmp/tmp.qg7q5ZQM9K/evdi/library'
[ Installing aarch64-linux-gnu/DisplayLinkManager ]
[ Installing libraries ]
[ Installing firmware packages ]
[ Installing licence file ]
[ Adding udev rule for DisplayLink DL-3xxx/4xxx/5xxx/6xxx devices ]
[ Adding upstart and powermanager sctripts ]

Please read the FAQ
http://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu

DisplayLink evdi module installed successfully.

 Reboot required!
 Detected user session type is: tty.
 Please, reboot your computer to ensure proper functioning of the software.

DisplayLink driver installed successfully.

Do you want to reboot now? (Y/n)

$ sudo systemctl start displaylink-driver.service

$ sudo systemctl status displaylink-driver.service
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/usr/lib/systemd/system/displaylink-driver.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2024-11-15 16:45:00 CST; 1min 9s ago
 Invocation: 07be8d06f5344e289a507f573b6254f6
    Process: 24373 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  |>
   Main PID: 24375 (DisplayLinkMana)
      Tasks: 14 (limit: 4494)
     Memory: 9.7M (peak: 15.6M)
        CPU: 32ms
     CGroup: /system.slice/displaylink-driver.service
             └─24375 /opt/displaylink/DisplayLinkManager

Nov 15 16:45:00 asahi-kde systemd[1]: Starting displaylink-driver.service - DisplayLink Driver Service...
Nov 15 16:45:00 asahi-kde systemd[1]: Started displaylink-driver.service - DisplayLink Driver Service.

$ sudo systemctl enable displaylink-driver.service
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

[< XML Suplex >]