Missing rtwn0 device

[danish gypsy]

I'm installing fbsd 13.3 on a new asus box. It has a realtek 8821a wlan device. After boot there is no device, either rtwn0 or wlan0 or any other flavors of this interface. The *.ko are present on /boot/kernel: rtwn.ko, if _rtwn_pci.ko, if_rtw88.ko.

So I can't create rtwn0 or wlan0 or any others when I try

ifconfig wlan0 create wlandev rtwn0
--> device not configured

/etc/rc.conf:

wlans_rtwn0="wlan0"
ifconfig_wlan0="WPA DHCP"
ifconfig_rtwn0="DHCP"

/etc/loader.conf:

if_rtwn_pci_load="YES"

What's missing?

Thanks, in advance, Chris

 

[Makoto]

Verify the file /etc/wpa_supplicant.conf . Also, I think you only need only the 2 first lines in /etc/rc.conf

 

[SirDice]

a new asus box

Entire desktop, mainboard or laptop? Asus makes a lot of different things. What's the model number?

Is the card itself detected at all? What does pciconf -lv | grep -A1 -B3 network output?

 

[danish gypsy]

Thanks for the thoughtful replies. I've gotten some more
information:

ASUS motherboard with gigabit and wlan from realtek

The output of pciconf -lv is interesting
it recognizes the 8821 chip and the Realtek vendor.
But it's called none2 because it can't match a device driver
for the device/resource.

none2@pci0:3:0:0 class=0x028000 rev=0x00 hdr=0x00 vendor=0x10ec
device=0x8821

/boot/loader.conf:

rtwn_load="YES"
if_rtwn_pci_load="YES"

The kldstat produces:

3 1 0x206b000 e3d8 if_rtwn_pci.ko
4 2 0x207a000 21b80 rtwn.ko

It seems the kos were loaded, but neither of them created
/dev/rtwn0, which is needed to create an interface:

ifconfig wlan0 create wlandev rtwn0

 

[SirDice]

The output of pciconf -lv is interesting
it recognizes the 8821 chip and the Realtek vendor.

pciconf(8) just enumerates devices through ACPI. In other words it just lists each device that happens to be on the PCI(e) bus. What's important here are the vendor and device IDs. Those are used to look for a driver that matches that vendor/device ID. Because it can't find those it cannot attach a driver to it (hence the none). Which basically means this is probably a variant of the chipset that's not recognized by the rtwn(4) driver. Sometimes it's just a matter of adding those IDs to the driver, but sometimes it requires a bit more.