Kernel module for D-Link N300 WiFi 4 USB Adapter (AN3U) rev. A1

Hello all,

for an old desktop I bought an D-Link N300 WiFi 4 USB Adapter. It is being recognised when inserted into a USB Port:

[Sun Feb  8 11:56:29 2026] usb 5-6.2: new high-speed USB device number 7 using xhci_hcd
[Sun Feb  8 11:56:29 2026] usb 5-6.2: New USB device found, idVendor=2001, idProduct=3328, bcdDevice= 2.00
[Sun Feb  8 11:56:29 2026] usb 5-6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sun Feb  8 11:56:29 2026] usb 5-6.2: Product: 802.11n  WLAN Adapter
[Sun Feb  8 11:56:29 2026] usb 5-6.2: Manufacturer: Realtek
[Sun Feb  8 11:56:29 2026] usb 5-6.2: SerialNumber: 00e04c000001

however it is not recognised by any of the modules. Searching on the net I found
https://marc.info/?l=linux-wireless&m=175921892830898 and https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=a8e32d208ae192299bf32457924170255aaad6f7
which indicate that the chipset of the device 2001:3328 is an rtl8192fu and it should be handled by the rtl8xxxu module. In fact it has been incorporated into kernel 6.18 . Is there any chance of backporting to Leap 16.0 kernel 6.12? If needed I can provide the windows driver files.

Best regards,

George

Should be done with:

modprobe -c | grep -i "2001.\+3328"
alias usb:v2001p3328d*dc*dsc*dp*icFFiscFFipFFin* rtl8xxxu

So post it.

kernel-firmware-realtek is installed?

LANG=C zypper se -si kernel-firmware-realtek
Loading repository data...
Reading installed packages...

S  | Name                    | Type    | Version            | Arch   | Repository
---+-------------------------+---------+--------------------+--------+----------------
i+ | kernel-firmware-realtek | package | 20260130-lp160.1.1 | noarch | kernel-firmware

    Note: For an extended search including not yet activated remote resources please use 'zypper
    search-packages'.

both modprobe and zypper return the shown output. The problem was blacklisting
rtl8xxxu as the D-Link DW-131 rev A1 device used before (failing wpa3) needed to blacklist rtl8xxxu so that r8712u could take over. reverting it solved the issue.

Thank you and best regards

George

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.