I have a new install of PVE 6.17.4
I am running on a Dell Optiplex 790, with an i7-2600k CPU (4 cores/8 threads), 32 GB of RAM, and 1TB of disk, so a very capable host, ancient as it may be.
I would like to bring up a USB WiFi network interface.
Before anyone begins screaming about how Proxmox doesn't like it or that it's unstable, I'd like to point out that a very specific driver set has been included in the distro which is for exactly the hardware I have.
I can't imagine them doing that if it didn't work.
The hardware in question is a RealTek RTL8822BU Wireless LAN 802.11ac USB NIC (vendor 0BFA/device B82C), and it works plug-and-play in Windows 10, so Linux shouldn't have issues with it.
When I plug it into Windows 10, it comes up immediately, its indicator light blinks, and all is well.
I have tried using a keyboard in all 10 of the host's USB ports, and they all work.
The WiFi device shows up in "ip a" no matter which USB port I use.
The indicator light does not turn on, but regular NIC port lights don't either until you issue an "ip link set ... up" either.
Proxmox shows with "lsmod" that a number of drivers are loaded, including "rtw88_8822bu" (exact match), "rtw88_usb", "rtw88_8822b" and "rtw88_core".
It certainly appears that Proxmox has recognized the device and loaded its own built-in support.
The problem is that after I issue an "ip link set ... up" command, "ip a" still shows the interface as down, and as would be expected, the indicator light remains dark.
There is no error message on the console; after the command the prompt just returns.
I have found a good handful of repos which offer drivers for the rtl8822bu, but each one recommends using the built-in driver instead.
One thing I did notice is a mention of firmware, and the fact that those files should be in the /lib/firmware directory, and while there is an rtw88 subdirectory, and many of the variants do have firmware, the specific "rtl8822bu" version is not among them.
Where should I look next for diagnostic information which can offer a clue, or firmware that can help fix the problem ?
I am running on a Dell Optiplex 790, with an i7-2600k CPU (4 cores/8 threads), 32 GB of RAM, and 1TB of disk, so a very capable host, ancient as it may be.
I would like to bring up a USB WiFi network interface.
Before anyone begins screaming about how Proxmox doesn't like it or that it's unstable, I'd like to point out that a very specific driver set has been included in the distro which is for exactly the hardware I have.
I can't imagine them doing that if it didn't work.
The hardware in question is a RealTek RTL8822BU Wireless LAN 802.11ac USB NIC (vendor 0BFA/device B82C), and it works plug-and-play in Windows 10, so Linux shouldn't have issues with it.
When I plug it into Windows 10, it comes up immediately, its indicator light blinks, and all is well.
I have tried using a keyboard in all 10 of the host's USB ports, and they all work.
The WiFi device shows up in "ip a" no matter which USB port I use.
The indicator light does not turn on, but regular NIC port lights don't either until you issue an "ip link set ... up" either.
Proxmox shows with "lsmod" that a number of drivers are loaded, including "rtw88_8822bu" (exact match), "rtw88_usb", "rtw88_8822b" and "rtw88_core".
It certainly appears that Proxmox has recognized the device and loaded its own built-in support.
The problem is that after I issue an "ip link set ... up" command, "ip a" still shows the interface as down, and as would be expected, the indicator light remains dark.
There is no error message on the console; after the command the prompt just returns.
I have found a good handful of repos which offer drivers for the rtl8822bu, but each one recommends using the built-in driver instead.
One thing I did notice is a mention of firmware, and the fact that those files should be in the /lib/firmware directory, and while there is an rtw88 subdirectory, and many of the variants do have firmware, the specific "rtl8822bu" version is not among them.
Where should I look next for diagnostic information which can offer a clue, or firmware that can help fix the problem ?