From 0a251a68f581a8f015aa0f513158a499c5ece85d Mon Sep 17 00:00:00 2001
From: Tamas Hudak <tamas@thudak.com>
Date: Thu, 19 Feb 2026 12:35:03 +0100
Subject: [PATCH 1/3] Update README: add OSMC kernel to tested list, fix
 firmware typo

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index db6b6b1..7dbd068 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,8 @@ $ sudo make install
 ```
 $ sudo make uninstall
 ```
-Note: Firmware for MT7621 will not be uninstalled.
+Note: Firmware for MT7921 will not be uninstalled.
 # Tested kernels
 1. Kernel 5.15.0-56-generic (Linux Mint 20.3 Una)
 2. Kernel 5.16.17-sun50iw6 (Orange Pi 3.0.8 Orangepi3-lts Ubuntu 22.04)
+3. Kernel 5.15.92-1-osmc (OSMC on Raspberry Pi 4, aarch64 kernel / armhf userland)

From 02fe83a6b2a483840dd061ac96d88c811c2aa7ea Mon Sep 17 00:00:00 2001
From: Tamas Hudak <tamas@thudak.com>
Date: Thu, 19 Feb 2026 12:46:32 +0100
Subject: [PATCH 2/3] Add OSMC Raspberry Pi 4 cross-compilation setup guide

---
 OSMC-RPi4-GUIDE.md | 222 +++++++++++++++++++++++++++++++++++++++++++++
 README.md          |   2 +-
 2 files changed, 223 insertions(+), 1 deletion(-)
 create mode 100644 OSMC-RPi4-GUIDE.md

diff --git a/OSMC-RPi4-GUIDE.md b/OSMC-RPi4-GUIDE.md
new file mode 100644
index 0000000..52be2a4
--- /dev/null
+++ b/OSMC-RPi4-GUIDE.md
@@ -0,0 +1,222 @@
+# Fenvi FU-AX1800 (MT7921au) on OSMC — Setup Guide
+
+## Environment
+
+- **Device**: Raspberry Pi 4 running OSMC
+- **Kernel**: 5.15.92-1-osmc (aarch64 kernel, armhf userland)
+- **USB Adapter**: Fenvi FU-AX1800 (MediaTek MT7921au, USB ID `0e8d:7961`)
+- **Problem**: The `mt7921u` driver was added in kernel 5.18, so it must be compiled as an out-of-tree module for kernel 5.15.
+
+---
+
+## Step 1: Install build dependencies
+
+```bash
+sudo apt update
+sudo apt install -y build-essential git libssl-dev bc file
+```
+
+If `libssl-dev` fails with a 404, download manually:
+
+```bash
+wget http://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.1w-0+deb11u4_armhf.deb -O /tmp/libssl1.1.deb
+wget http://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl-dev_1.1.1w-0+deb11u4_armhf.deb -O /tmp/libssl-dev.deb
+sudo dpkg -i /tmp/libssl1.1.deb /tmp/libssl-dev.deb
+```
+
+## Step 2: Install kernel headers and source
+
+```bash
+sudo apt install -y rbp464-headers-sanitised-5.15.92-1-osmc rbp464-source-5.15.92-1-osmc
+```
+
+> **Note**: Use `apt-cache search rbp464` if the exact version has changed.
+
+## Step 3: Create the kernel build symlink
+
+```bash
+sudo ln -sf /usr/src/rbp464-source-5.15.92-1-osmc /lib/modules/5.15.92-1-osmc/build
+```
+
+## Step 4: Install the cross-compiler
+
+The kernel is arm64 but userland is armhf, so a cross-compiler is needed:
+
+```bash
+sudo apt install -y aarch64-toolchain-osmc
+```
+
+This installs a chroot-based toolchain at `/opt/osmc-tc/aarch64-toolchain-osmc/`.
+
+## Step 5: Set up cross-compiler wrapper scripts
+
+The toolchain binaries are aarch64 ELF executables inside a chroot. They can run on the aarch64 kernel but need the correct dynamic linker and library paths. Create wrapper scripts for every tool:
+
+```bash
+# Create the dynamic linker symlink
+sudo ln -sf /opt/osmc-tc/aarch64-toolchain-osmc/lib/ld-linux-aarch64.so.1 /lib/ld-linux-aarch64.so.1
+
+# Create wrapper scripts
+sudo mkdir -p /usr/local/aarch64-cross
+for tool in $(ls /opt/osmc-tc/aarch64-toolchain-osmc/usr/bin/aarch64-linux-gnu-* | xargs -n1 basename); do
+  sudo tee /usr/local/aarch64-cross/$tool > /dev/null <<SCRIPT
+#!/bin/sh
+export LD_LIBRARY_PATH=/opt/osmc-tc/aarch64-toolchain-osmc/lib/aarch64-linux-gnu:/opt/osmc-tc/aarch64-toolchain-osmc/usr/lib/aarch64-linux-gnu
+export PATH=/usr/local/aarch64-cross:\$PATH
+exec /opt/osmc-tc/aarch64-toolchain-osmc/usr/bin/$tool "\$@"
+SCRIPT
+  sudo chmod +x /usr/local/aarch64-cross/$tool
+done
+```
+
+## Step 6: Create assembler symlinks for GCC
+
+GCC looks for `as`, `ld`, etc. (without the `aarch64-linux-gnu-` prefix) in a specific directory relative to itself. That directory doesn't exist by default:
+
+```bash
+sudo mkdir -p /opt/osmc-tc/aarch64-toolchain-osmc/usr/aarch64-linux-gnu/bin
+for tool in as ar ld ld.bfd ld.gold nm objcopy objdump ranlib readelf strip; do
+  sudo ln -sf /opt/osmc-tc/aarch64-toolchain-osmc/usr/bin/aarch64-linux-gnu-$tool \
+    /opt/osmc-tc/aarch64-toolchain-osmc/usr/aarch64-linux-gnu/bin/$tool
+done
+```
+
+## Step 7: Copy kernel config and prepare for module building
+
+```bash
+sudo cp /boot/config-5.15.92-1-osmc /usr/src/rbp464-source-5.15.92-1-osmc/.config
+
+export LD_LIBRARY_PATH=/opt/osmc-tc/aarch64-toolchain-osmc/lib/aarch64-linux-gnu:/opt/osmc-tc/aarch64-toolchain-osmc/usr/lib/aarch64-linux-gnu
+
+sudo -E make -C /usr/src/rbp464-source-5.15.92-1-osmc \
+  ARCH=arm64 \
+  CROSS_COMPILE=/usr/local/aarch64-cross/aarch64-linux-gnu- \
+  modules_prepare
+```
+
+> **Note**: Ignore the `libarmmem.so` preload warnings — they are harmless (32-bit library being skipped by 64-bit processes).
+
+## Step 8: Install firmware files
+
+```bash
+sudo mkdir -p /lib/firmware/mediatek
+
+sudo wget -O /lib/firmware/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \
+  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin
+
+sudo wget -O /lib/firmware/mediatek/WIFI_RAM_CODE_MT7961_1.bin \
+  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/WIFI_RAM_CODE_MT7961_1.bin
+```
+
+## Step 9: Clone and build the mt7921 driver
+
+```bash
+cd ~
+git clone https://github.com/tomhudak/mt7921.git
+cd mt7921
+
+export LD_LIBRARY_PATH=/opt/osmc-tc/aarch64-toolchain-osmc/lib/aarch64-linux-gnu:/opt/osmc-tc/aarch64-toolchain-osmc/usr/lib/aarch64-linux-gnu
+
+make ARCH=arm64 \
+  CROSS_COMPILE=/usr/local/aarch64-cross/aarch64-linux-gnu- \
+  CONFIG_MT76_CONNAC_LIB=m \
+  CONFIG_MT7921_COMMON=m \
+  CONFIG_MT7921U=m
+```
+
+> **Critical**: You must pass `CONFIG_MT76_CONNAC_LIB=m` on the make command line. The kernel .config doesn't include this option, and without it the `mt76-connac-lib.ko` module won't be built, causing "Unknown symbol" errors when loading.
+
+## Step 10: Install the modules
+
+```bash
+sudo -E make ARCH=arm64 \
+  CROSS_COMPILE=/usr/local/aarch64-cross/aarch64-linux-gnu- \
+  CONFIG_MT76_CONNAC_LIB=m \
+  CONFIG_MT7921_COMMON=m \
+  CONFIG_MT7921U=m \
+  modules_install
+```
+
+> The `cp: -r not specified` errors at the end are harmless (firmware directory copy issue in the install script). The `.ko` modules are installed correctly.
+
+Run depmod manually (it gets skipped due to missing `System.map`):
+
+```bash
+sudo /sbin/depmod -a
+```
+
+## Step 11: Load the driver
+
+```bash
+sudo /sbin/modprobe mt7921u
+```
+
+Verify the adapter appears:
+
+```bash
+ip link show
+# You should see wlan1 (or similar)
+
+dmesg | grep mt7921
+# Should show: "mt7921u 1-1.3:1.0: HW/SW Version: ..."
+# And: "WM Firmware Version: ..."
+```
+
+## Step 12: Configure autoload on boot
+
+```bash
+echo 'mt7921u' | sudo tee /etc/modules-load.d/mt7921u.conf
+```
+
+## Step 13: Connect to WiFi
+
+Create a connman provisioning file:
+
+```bash
+sudo tee /var/lib/connman/your-wifi.config > /dev/null <<'EOF'
+[service_your_wifi]
+Type=wifi
+Name=YOUR_SSID
+Security=psk
+Passphrase=YOUR_PASSWORD
+AutoConnect=true
+IPv4=dhcp
+EOF
+```
+
+Then restart connman and connect:
+
+```bash
+sudo systemctl restart connman
+connmanctl scan wifi
+connmanctl services
+# Find your network's service ID for wlan1 (identified by the MAC address)
+connmanctl connect wifi_XXXX_YYYY_managed_psk
+```
+
+---
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| `/lib/modules/.../build` not found | Redo step 3 (symlink) |
+| `unknown assembler invoked` during modules_prepare | Redo step 6 (assembler symlinks for GCC) |
+| `__uint128_t` error | Make sure you're using `ARCH=arm64` with the aarch64 cross-compiler |
+| `bc: not found` during modules_prepare | `sudo apt install bc` |
+| `Unknown symbol mt76_connac_*` when loading | Rebuild with `CONFIG_MT76_CONNAC_LIB=m` (step 9) |
+| `Not registered` when connecting via connmanctl | Create a provisioning file (step 13) or restart connman |
+| `libarmmem.so` preload warnings | Harmless — 32-bit library being skipped by 64-bit processes |
+| Module doesn't load after reboot | Check `/etc/modules-load.d/mt7921u.conf` exists (step 12) |
+
+## Built modules reference
+
+The following kernel modules are installed in `/lib/modules/5.15.92-1-osmc/updates/`:
+
+| Module | Purpose |
+|--------|---------|
+| `mt76/mt76.ko` | Core mt76 driver |
+| `mt76/mt76-usb.ko` | mt76 USB transport |
+| `mt76/mt76-connac-lib.ko` | mt76 connectivity library (MCU/MAC) |
+| `mt76/mt7921/mt7921-common.ko` | MT7921 common driver |
+| `mt76/mt7921/mt7921u.ko` | MT7921 USB driver (loads all deps) |
diff --git a/README.md b/README.md
index 7dbd068..7ff9d6a 100644
--- a/README.md
+++ b/README.md
@@ -14,4 +14,4 @@ Note: Firmware for MT7921 will not be uninstalled.
 # Tested kernels
 1. Kernel 5.15.0-56-generic (Linux Mint 20.3 Una)
 2. Kernel 5.16.17-sun50iw6 (Orange Pi 3.0.8 Orangepi3-lts Ubuntu 22.04)
-3. Kernel 5.15.92-1-osmc (OSMC on Raspberry Pi 4, aarch64 kernel / armhf userland)
+3. Kernel 5.15.92-1-osmc (OSMC on Raspberry Pi 4, aarch64 kernel / armhf userland) — [setup guide](OSMC-RPi4-GUIDE.md)

From 1788aab5e4b09072a05f5f084626155c1e1dcb0a Mon Sep 17 00:00:00 2001
From: Tamas Hudak <tamas@thudak.com>
Date: Thu, 19 Feb 2026 12:55:28 +0100
Subject: [PATCH 3/3] Add explanations for why each setup step is needed

---
 OSMC-RPi4-GUIDE.md | 27 +++++++++++++++++++++++----
 1 file changed, 23 insertions(+), 4 deletions(-)

diff --git a/OSMC-RPi4-GUIDE.md b/OSMC-RPi4-GUIDE.md
index 52be2a4..2833efc 100644
--- a/OSMC-RPi4-GUIDE.md
+++ b/OSMC-RPi4-GUIDE.md
@@ -5,7 +5,16 @@
 - **Device**: Raspberry Pi 4 running OSMC
 - **Kernel**: 5.15.92-1-osmc (aarch64 kernel, armhf userland)
 - **USB Adapter**: Fenvi FU-AX1800 (MediaTek MT7921au, USB ID `0e8d:7961`)
-- **Problem**: The `mt7921u` driver was added in kernel 5.18, so it must be compiled as an out-of-tree module for kernel 5.15.
+
+## Why is this guide needed?
+
+The MT7921 WiFi chipset (used in the Fenvi FU-AX1800 and other USB adapters) is supported by the `mt7921u` kernel driver — but that driver was only added in **kernel 5.18**. OSMC ships with **kernel 5.15**, so the driver simply isn't there. This repo backports the driver from 5.18.19, but building it on OSMC is not a straightforward `make && make install` for two reasons:
+
+1. **OSMC uses a mixed-architecture setup.** The Raspberry Pi 4 runs a **64-bit (aarch64) kernel** but OSMC's userland is **32-bit (armhf)**. All system tools — including `gcc` from `apt` — are 32-bit and cannot compile 64-bit kernel modules. You need an aarch64 cross-compiler, and OSMC's cross-compiler package ships inside a chroot that requires wrapper scripts to use.
+
+2. **The kernel source tree needs manual preparation.** OSMC doesn't set up the `/lib/modules/<version>/build` symlink or copy the kernel `.config` by default, so the out-of-tree module build will fail unless you wire these up yourself and run `modules_prepare` first.
+
+The steps below walk through the full process — from installing the toolchain to connecting to WiFi.
 
 ---
 
@@ -26,6 +35,8 @@ sudo dpkg -i /tmp/libssl1.1.deb /tmp/libssl-dev.deb
 
 ## Step 2: Install kernel headers and source
 
+Out-of-tree module builds need the kernel headers and source to compile against. OSMC packages these separately.
+
 ```bash
 sudo apt install -y rbp464-headers-sanitised-5.15.92-1-osmc rbp464-source-5.15.92-1-osmc
 ```
@@ -34,6 +45,8 @@ sudo apt install -y rbp464-headers-sanitised-5.15.92-1-osmc rbp464-source-5.15.9
 
 ## Step 3: Create the kernel build symlink
 
+The kernel build system expects the source tree at `/lib/modules/<version>/build`, but OSMC doesn't create this symlink automatically.
+
 ```bash
 sudo ln -sf /usr/src/rbp464-source-5.15.92-1-osmc /lib/modules/5.15.92-1-osmc/build
 ```
@@ -50,7 +63,7 @@ This installs a chroot-based toolchain at `/opt/osmc-tc/aarch64-toolchain-osmc/`
 
 ## Step 5: Set up cross-compiler wrapper scripts
 
-The toolchain binaries are aarch64 ELF executables inside a chroot. They can run on the aarch64 kernel but need the correct dynamic linker and library paths. Create wrapper scripts for every tool:
+The OSMC toolchain is packaged inside a chroot, so the binaries can't find their dynamic linker and shared libraries when called directly from the host. Wrapper scripts set the correct `LD_LIBRARY_PATH` so the 64-bit compiler tools work outside the chroot.
 
 ```bash
 # Create the dynamic linker symlink
@@ -71,7 +84,7 @@ done
 
 ## Step 6: Create assembler symlinks for GCC
 
-GCC looks for `as`, `ld`, etc. (without the `aarch64-linux-gnu-` prefix) in a specific directory relative to itself. That directory doesn't exist by default:
+When GCC invokes the assembler or linker internally, it looks for unprefixed tool names (`as`, `ld`, etc.) in `<sysroot>/usr/aarch64-linux-gnu/bin/`. The OSMC toolchain doesn't populate this directory, so GCC fails with "unknown assembler invoked". These symlinks fix that.
 
 ```bash
 sudo mkdir -p /opt/osmc-tc/aarch64-toolchain-osmc/usr/aarch64-linux-gnu/bin
@@ -83,6 +96,8 @@ done
 
 ## Step 7: Copy kernel config and prepare for module building
 
+The kernel source tree needs the running kernel's `.config` and a `modules_prepare` pass to generate the headers and scripts that out-of-tree builds depend on (e.g. `Module.symvers`, generated headers).
+
 ```bash
 sudo cp /boot/config-5.15.92-1-osmc /usr/src/rbp464-source-5.15.92-1-osmc/.config
 
@@ -98,6 +113,8 @@ sudo -E make -C /usr/src/rbp464-source-5.15.92-1-osmc \
 
 ## Step 8: Install firmware files
 
+The MT7921 chipset requires firmware blobs that the driver uploads to the device at load time. OSMC's kernel 5.15 doesn't ship these since it has no built-in MT7921 support. Download them from the upstream linux-firmware repository.
+
 ```bash
 sudo mkdir -p /lib/firmware/mediatek
 
@@ -164,13 +181,15 @@ dmesg | grep mt7921
 
 ## Step 12: Configure autoload on boot
 
+Without this, you'd have to manually `modprobe mt7921u` after every reboot.
+
 ```bash
 echo 'mt7921u' | sudo tee /etc/modules-load.d/mt7921u.conf
 ```
 
 ## Step 13: Connect to WiFi
 
-Create a connman provisioning file:
+OSMC uses connman (not NetworkManager) for network management. A provisioning file tells connman how to connect to your network automatically.
 
 ```bash
 sudo tee /var/lib/connman/your-wifi.config > /dev/null <<'EOF'