Install the MS9133 USB HDMI Driver on AlmaLinux 10 with DKMS

Those inexpensive USB 3.0 to HDMI adapters sold on Amazon under dozens of different brand names very often have the same chip inside: the MacroSilicon MS9133. The box usually says a driver is required and only mentions Windows and macOS. On Linux, nothing in the mainline kernel drives it. The free, open-source ms91xx-linux-drm driver fills that gap, and with release 3.1.9 it now ships as a kernel-independent DKMS RPM for the Enterprise Linux 10 family: AlmaLinux 10, Rocky Linux 10, Oracle Linux 10 and CentOS Stream 10.

Project on GitHub: azwieg103/ms91xx-linux-drm

This post covers the packaged install. If you want the background on the chip, the fixes over the vendor code and a manual build-and-load walkthrough, read the earlier write-up, MacroSilicon MS9133 USB Display Driver for Linux (Free, Open Source).

Is your adapter an MS9133? Check with lsusb

The brand name on the box tells you very little, so check the USB ID instead. Plug the adapter in and run:

lsusb -d 345f:9133

An MS9133 shows up with vendor:product ID 345f:9133 and the name MS USB Video. If the command prints nothing, run plain lsusb and look for a 345f: or 534d: MacroSilicon entry.

The driver’s USB ID table also lists 345f:9132, 345f:9135 and 534d:6021. The last one is the ID an MS912C USB-to-VGA dongle switches to after it first enumerates as 345f:9132. The repository documents that VGA setup separately (more on that below). The hardware-verified device for this release is the MS9133, so treat the other IDs as “may work” rather than tested.

What the 3.1.9 package gives you

  • Two kernel modules: usbdisp_drm.ko (the DRM/platform driver) and usbdisp_usb.ko (the USB interface and display transport).
  • A DKMS source package installed under /usr/src/msdisp-3.1.9. DKMS builds the modules against every installed kernel that has a matching kernel-devel package, so new kernels get rebuilt modules automatically.
  • /usr/lib/modules-load.d/msdisp.conf, which loads usbdisp_drm before usbdisp_usb at boot.
  • Safer upgrades: older DKMS versions are only removed after the new version has built successfully for all installed kernel-devel packages. A failed build keeps the previous driver in place.
  • Matching version metadata: both modules report 3.1.9, and CI checks that the module versions match the RPM version on every build target.
  • GPL-3.0 licensed source.

How the packages are built and tested

Every code change pushed to the project’s main or dev branch triggers a GitHub Actions pipeline. For each of AlmaLinux 10, Rocky Linux 10, Oracle Linux 10 and CentOS Stream 10, CI installs the build dependencies, builds the binary DKMS RPM and source RPM, installs the RPM in a container, runs DKMS, verifies that both modules build, and checks that their versions match the package. A GitHub Release is published only when all four jobs pass on the latest main commit.

Release files use a ZWIEGNET.N.el10 release field, where N counts successful rebuilds of the same driver version. For example: ms91xx-linux-drm-dkms-3.1.9-ZWIEGNET.3.el10.noarch.rpm.

Install the MS9133 driver on AlmaLinux 10 (or Rocky, Oracle Linux, CentOS Stream 10)

1. Install EPEL, DKMS and the build tools

sudo dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm
sudo dnf install -y dkms gcc make elfutils-libelf-devel kernel-devel

DKMS can only build for kernels whose development files are installed. Make sure the running kernel has them:

KVER="$(uname -r)"
test -e "/lib/modules/$KVER/build/Makefile" || {
    echo "Missing kernel-devel for $KVER"
    exit 1
}

If that fails, the installed kernel-devel is usually newer than the running kernel. Update, reboot into the newest kernel and check again.

2. Download and install the RPM

Grab the latest noarch.rpm from the GitHub Releases page and install it with dnf. Use the exact filename shown on the release:

sudo dnf install ./ms91xx-linux-drm-dkms-3.1.9-ZWIEGNET.N.el10.noarch.rpm

3. Verify the install

rpm -q ms91xx-linux-drm-dkms
dkms status -m msdisp
modinfo -F version usbdisp_drm
modinfo -F version usbdisp_usb
modinfo -n usbdisp_drm
modinfo -n usbdisp_usb
cat /usr/lib/modules-load.d/msdisp.conf

Both modinfo -F version commands should print 3.1.9, and the modinfo -n paths should point at the DKMS-built modules for your kernel. Then reboot so the modules load cleanly. Don’t force-unload the display modules while a graphical session is using them.

Secure Boot

If Secure Boot is enabled, a successful DKMS build is not enough. You need to set up and enroll a DKMS signing key before the kernel will load the modules. The DKMS build does not do that for you.

Tested hardware

The project is clear that this is one verified system, not a compatibility guarantee:

ItemTested configuration
HostHP MP9 G4 Retail System
DistributionAlmaLinux 10.2
Kernel6.12.0-211.69.1.el10_2.x86_64
Architecturex86_64
USB adapterMacroSilicon MS9133 (345f:9133)
DesktopKDE Plasma on Wayland
Verified mode1920×1080 at 60 Hz

On that system the adapter initialized, registered its DRM framebuffer and started video output.

Building from source instead

The RPM is the recommended method on EL10. For other distributions, or for development, the source builds with a plain make against the running kernel, or against another installed kernel by setting KVER:

sudo dnf install -y gcc make elfutils-libelf-devel kernel-devel
git clone https://github.com/azwieg103/ms91xx-linux-drm.git
cd ms91xx-linux-drm
make clean
make -j"$(nproc)" KVER="$(uname -r)"

That leaves drm/usbdisp_drm.ko and drm/usbdisp_usb.ko. The earlier post walks through loading them by hand with insmod and checking /sys/class/drm/.

MS912C USB-to-VGA dongles

The repository includes docs/MS912C-VGA.md, a community write-up of getting an MS912C VGA dongle working as the text console on Debian 13. That hardware needs two module options in /etc/modprobe.d/usbdisp.conf:

options usbdisp_usb port_type=2 custom_mode=1_640x480@60,4_1280x720@60

port_type=2 forces the VGA output, because the chip reports the wrong video port and the VGA DAC is otherwise never powered on. custom_mode= supplies a mode list, because a basic VGA monitor provides no EDID. The doc explains each failure mode in detail. Read it before you try a VGA dongle.

Known limitations

On the tested system the kernel logged a warning from a high-order DMA allocation during USB HAL setup. The HAL fell back to a vmalloc buffer and video still started, but the project lists this as an area for further investigation. These scenarios have not yet been fully validated:

  • Repeated USB unplug/replug and disconnect recovery
  • Suspend and resume
  • Long-running use and memory pressure
  • More than one MS9133 adapter at a time
  • Other chipsets, kernels and desktop environments

Treat it as experimental kernel software and keep a recovery path, such as SSH from another machine.

Troubleshooting

Confirm the adapter, the running kernel and its development files, then read the kernel log:

lsusb -d 345f:9133
uname -r
rpm -q "kernel-devel-$(uname -r)"
ls -ld "/lib/modules/$(uname -r)/build"
journalctl -k -b | grep -E -i 'msdisp|usbdisp|345f:9133|drm|dma'
  • dkms status shows nothing built for your kernel: install the matching kernel-devel and reinstall or rebuild the package.
  • Modules built but won’t load with Secure Boot on: enroll a DKMS signing key (see above).
  • Display stays black after an upgrade: reboot. The old modules may still be in use by the session.

When you report an issue on GitHub, include the adapter’s USB ID, your distribution release, kernel version, build output and the relevant kernel log lines.

Removing the driver

sudo dnf remove ms91xx-linux-drm-dkms

This unregisters the driver from DKMS. If the module is in use by your display session, reboot before you expect it to be fully unloaded.

FAQ

Do I need the vendor’s driver CD? No. The adapter’s driver CD is aimed at Windows and macOS. On Linux this driver replaces it.

Will it survive kernel updates? Yes, as long as each new kernel’s kernel-devel package is installed. DKMS rebuilds the modules for it.

Which brand should I buy? The project doesn’t certify any brand. Check the listing or the device itself for an MS9133 and the 345f:9133 ID.

How do I contribute? Open pull requests against the dev branch, not main, and report security issues privately as described in the repository’s SECURITY.md.

Get the driver

Source, issues and release downloads are on GitHub: github.com/azwieg103/ms91xx-linux-drm. The latest RPM is always on the releases page.

Leave a Reply

Your email address will not be published. Required fields are marked *