Fixing DisplayLink Connection Issues on Linux Kernel 6.18

If you recently performed a full system upgrade and found your DisplayLink monitors stopped working, the culprit is likely a compatibility gap between the Linux Kernel and the "evdi" driver.

When the Linux Kernel updates (in this case, from 6.17 to 6.18), the internal rules for how hardware communicates with software often change. If the driver isn't updated to match these new rules, it fails to "build," leaving your external monitors disconnected.

THE PROBLEM: WHY THE BUILD FAILED

The transition to Kernel 6.18 introduced changes to the Direct Rendering Manager (DRM) subsystem. The older evdi version (1.14.9) was written using instructions that the new Kernel no longer recognizes.

Specific technical errors included:

Missing "struct_mutex": A component the driver expected to find in the Kernel is gone.

API Changes: Functions used to create "framebuffers" (the images sent to your screen) now require different technical arguments.

THE SOLUTION: STEP-BY-STEP FIX

To resolve this, we manually upgrade the evdi driver to version 1.14.15, which contains the necessary code fixes for Kernel 6.18.

STEP 1: CONFIRM THE FAILURE

Check your logs to ensure the error matches the DRM API changes:

cat /var/lib/dkms/evdi/1.14.9/build/make.log

STEP 2: DOWNLOAD THE UPDATED SOURCE

We need the source code for v1.14.15 (released Feb 2026).

cd /tmp
curl -sL https://api.github.com/repos/DisplayLink/evdi/tarball/v1.14.15 \
-o evdi-1.14.15.tar.gz
tar xzf evdi-1.14.15.tar.gz

STEP 3: REMOVE THE BROKEN MODULE

Clear the old, incompatible version from the DKMS tree:

dkms remove evdi/1.14.9 --all

STEP 4: INSTALL THE NEW SOURCE

Move the updated files into the system source directory:

mkdir -p /usr/src/evdi-1.14.15

cp -r /tmp/DisplayLink-evdi-/module/ /usr/src/evdi-1.14.15/

STEP 5: UPDATE THE VERSION CONFIG

Tell DKMS that this folder contains version 1.14.15:

sed -i 's/PACKAGE_VERSION=.*/PACKAGE_VERSION="1.14.15"/' /usr/src/evdi-1.14.15/dkms.conf

STEP 6: BUILD AND INSTALL

Compile the driver specifically for your new 6.18 kernel:

dkms add evdi/1.14.15

dkms build evdi/1.14.15

dkms install evdi/1.14.15

RESULTS AND VERIFICATION

After running the installation, verify that the module is correctly loaded:

dkms status evdi

You should see: "evdi/1.14.15, ... installed".

Once you reboot your computer, the new Kernel will load the functional driver, and your DisplayLink displays should activate normally.

SUMMARY NOTES

REBOOT: A full restart is required to switch to the new kernel and driver.

PACKAGING: This was a manual fix. If your Linux distribution (like Fedora or Ubuntu) releases an official updated DisplayLink RPM/DEB package later, it is recommended to install that to stay on the standard update path.

SYSTEM STABILITY: This fix specifically addresses the build errors. If you experience flickering, ensure you haven't disabled any critical power management settings.

Unleashing the Full Potential of Your Logitech MX Master on Linux

If you’ve recently picked up a Logitech MX Master mouse, you already know it’s a phenomenal piece of hardware. However, if you are a Linux user, you’ve probably hit a frustrating roadblock: Logitech doesn't provide an official version of their "Logi Options" software for Linux. Without it, your premium mouse is reduced to just basic point-and-click functionality.

Fortunately, the open-source community has a brilliant solution called Logiops. While the official documentation can sometimes feel a bit scattered, getting it up and running on Fedora is actually quite straightforward. Here is a simplified guide to compiling Logiops and getting all those extra buttons and gestures working on your machine.

(Note: The package names and commands below use dnf specifically for Fedora distributions. If you are on Ubuntu/Debian, you will need to use apt and their equivalent Debian package names.)

Step 1: Install the Required Dependencies

Before we can build the software, your Fedora system needs the right C++ compilers and development libraries. Open up your terminal and run the following command to install everything you need in one go:

sudo dnf install cmake gcc-c++ glib2-devel libevdev-devel systemd-devel libconfig-devel

Troubleshooting Tip: If CMake ever complains about a missing C++ compiler, double-check that gcc-c++ was successfully installed. If you see a "gio-2.0 not found" error during the CMake step, it means glib2-devel is missing.

Step 2: Clone and Build the Project

With the dependencies out of the way, it’s time to pull the source code from GitHub and build it.

First, clone the repository into a directory of your choice:

git clone https://github.com/PixlOne/logiops.git

Next, navigate into the new folder, create a build directory, and compile the code. Run these commands one by one:

cd logiops
mkdir build
cd build
cmake ..
make

Step 3: Create Your Configuration File

Logiops needs to know exactly what you want each button to do. We define this by creating a configuration file.

Create a new file at /etc/logid.cfg (you will need root/sudo privileges to write to the /etc/ directory). Here is an excellent starter configuration for an MX Master 2S (if you have a 3S, simply change the name field to "MX Master 3S"):

devices: (
{
    name: "Wireless Mouse MX Master 2S";
    smartshift:
    {
        on: true;
        threshold: 20;
    };
    hiresscroll:
    {
        hires: false;
        invert: false;
        target: false;
    };
    dpi: 1750;

    buttons: (
    {
        # Thumb button (Gestures)
        cid: 0xc3;
        action =
        {
            type: "Gestures";
            gestures: (
                {
                    direction: "Up";
                    mode: "OnRelease";
                    action = { type: "Keypress"; keys: ["KEY_VOLUMEUP"]; };
                },
                {
                    direction: "Down";
                    mode: "OnRelease";
                    action = { type: "Keypress"; keys: ["KEY_VOLUMEDOWN"]; };
                },
                {
                    direction: "Left";
                    mode: "OnRelease";
                    action = { type: "Keypress"; keys: ["KEY_PREVIOUSSONG"]; };
                },
                {
                    direction: "Right";
                    mode: "OnRelease";
                    action = { type: "Keypress"; keys: ["KEY_NEXTSONG"]; };
                },
                {
                    direction: "None";
                    mode: "OnRelease";
                    action = { type: "Keypress"; keys: ["KEY_PLAYPAUSE"]; };
                }
            );
        };
    },
    {
        # Button behind the scroll wheel
        cid: 0xc4;
        action = { type = "ToggleSmartshift"; };
    },
    {
        # Back button: Previous workspace
        cid: 0x53;
        action = { type: "Keypress"; keys: ["KEY_LEFTMETA", "KEY_PAGEUP"]; };
    },
    {
        # Next button: Next workspace
        cid: 0x56;
        action = { type: "Keypress"; keys: ["KEY_LEFTMETA", "KEY_PAGEDOWN"]; };
    }
    );
});

Feel free to tweak the dpi, customize the keys arrays, or adjust the SmartShift threshold to match your personal workflow!

Step 4: Install and Start the Daemon

You’re almost done. The final step is to install the compiled application to your system and enable the background service (daemon) so it starts automatically.

Run the following commands from inside your build directory:

sudo make install
sudo systemctl enable --now logid

The --now flag is a handy trick that enables the service to start on boot, while simultaneously starting it up right this second.

Final Thoughts

That's it! Your MX Master should now be fully functional on Fedora.

One final tip: If you find that your back and forward buttons aren't registering right away, try completely rebooting your machine. Sometimes the system needs

Changing the Gateway IP in Rocky Linux

 

Step 1: Find the Real Connection Name

Before you change anything, ask NetworkManager what the connection is actually called. Do not guess.

Run this command:

Bash

nmcli connection show

What to look for:

Focus on the NAME column on the far left.

NAME	UUID	TYPE	DEVICE
enp1s0	5fb06bd0...	ethernet	enp1s0
Wired connection 1	2ad18c...	ethernet	enp1s0

• In the first row, the connection name matches the device name (enp1s0).

• In the second row, the connection is named Wired connection 1.

Copy the text from the NAME column exactly.

Step 2: Set the New Gateway

Now that you have the correct name, use nmcli to modify the configuration.

Syntax:

sudo nmcli connection modify "<CONNECTION_NAME>" ipv4.gateway <NEW_IP>

Example (If your name is "enp1s0"):

Bash

sudo nmcli connection modify "enp1s0" ipv4.gateway 192.168.0.70

Example (If your name is "Wired connection 1"):

Bash

sudo nmcli connection modify "Wired connection 1" ipv4.gateway 192.168.0.70

Step 3: Apply the Changes

Modifying the connection only updates the config file on the disk. To make it live, you must reload the interface.

Bash

sudo nmcli connection up "enp1s0"

(Replace enp1s0 with your actual connection name found in Step 1).

Step 4: Verify

Check the kernel routing table to confirm the default route has updated.

Bash

ip route show

You are looking for the line starting with default:

default via 192.168.0.70 dev enp1s0 proto static metric 100

---

Common Gotcha: DHCP Overrides

If you followed the steps above but ip route still shows the old gateway, your server is likely getting its IP via DHCP.

By default, DHCP provides an IP address and a gateway. The DHCP gateway will override your manual setting every time the interface comes up.

The Fix:

You need to tell NetworkManager to keep the DHCP IP address but ignore the DHCP gateway.

Bash

# 1. Ignore the automatic gateway from DHCP
sudo nmcli connection modify "enp1s0" ipv4.ignore-auto-routes yes

# 2. Enforce your manual gateway
sudo nmcli connection modify "enp1s0" ipv4.gateway 192.168.0.70

# 3. Apply changes
sudo nmcli connection up "enp1s0"

---

Summary

• Don't assume the connection name is "System enp1s0".

• Always check nmcli connection show first.

• Remember to reload with nmcli connection up after making changes.