FreeBSD doesn't detect my D-Link DWA-172 Wi-Fi adapter!

[T-Daemon]

I plugged adapter with USB Virtualbox USB

I've tested this in a VirtualBox VM with a USB wifi adapter I use on the host system. The adapter is recognized, the firmware loaded, but it does not associate with the access point, but only when WPA/WPA2 authentication is enabled.

Without authentication, a "open" configured access point associates with no problems. I wasn't able to determine the cause, perhaps others can use this to track the issue, I'm out of ideas.

The VM configuration: Settings -> USB -> Add USB filter <wifi adapter name>. Or insert the adapter in running system: VM window Statusbar, USB icon right click, wifi adapter.

"wlan0" is created but ifconfig(8) interface status shows "no carrier". A manually configured wlan0 (IP, ssid, interface up) has no effect, the interface still has "no carrier".

/etc/wpa_supplicant.conf in VM is configured as the same as on the host system.

It make no difference when the VMs network adapter is configured "Attached to: Bridged Adapter" "Name: wlan0".

Somthing else I noticed: when trying to configure the wifi adapter by bsdconfig(8) (bsdconfig -> Network Management -> Wireless Networks ), this error message pop's up:

 

[astyle]

I've tested this in a VirtualBox VM with a USB wifi adapter I use on the host system. The adapter is recognized, the firmware loaded, but it does not associate with the access point, but only when WPA/WPA2 authentication is enabled.

Without authentication, a "open" configured access point associates with no problems. I wasn't able to determine the cause, perhaps others can use this to track the issue, I'm out of ideas.

The VM configuration: Settings -> USB -> Add USB filter <wifi adapter name>. Or insert the adapter in running system: VM window Statusbar, USB icon right click, wifi adapter.

"wlan0" is created but ifconfig(8) interface status shows "no carrier". A manually configured wlan0 (IP, ssid, interface up) has no effect, the interface still has "no carrier".

/etc/wpa_supplicant.conf in VM is configured as the same as on the host system.

It make no difference when the VMs network adapter is configured "Attached to: Bridged Adapter" "Name: wlan0".

Somthing else I noticed: when trying to configure the wifi adapter by bsdconfig(8) (bsdconfig -> Network Management -> Wireless Networks ), this error message pop's up:

View attachment 21995

My very first time seeing this error. If the card has a driver, and shows up like iwn0 or something, then even bsdconfig works OK. For me, the problem is underneath the wpa_supplicant...

 

[Leviwryi]

I don't see anything wrong in the screenshot. I think it may be the hardware driver. What's the output of pciconf -lv | grep -B4 network? The network device listed in that manner will be detected by ifconfig.

Sorry for my inactivity FreeBSD only found the Virtual Box virtual adapter(no the DWA-172)

 

[Leviwryi]

I've tested this in a VirtualBox VM with a USB wifi adapter I use on the host system. The adapter is recognized, the firmware loaded, but it does not associate with the access point, but only when WPA/WPA2 authentication is enabled.

Without authentication, a "open" configured access point associates with no problems. I wasn't able to determine the cause, perhaps others can use this to track the issue, I'm out of ideas.

The VM configuration: Settings -> USB -> Add USB filter <wifi adapter name>. Or insert the adapter in running system: VM window Statusbar, USB icon right click, wifi adapter.

"wlan0" is created but ifconfig(8) interface status shows "no carrier". A manually configured wlan0 (IP, ssid, interface up) has no effect, the interface still has "no carrier".

/etc/wpa_supplicant.conf in VM is configured as the same as on the host system.

It make no difference when the VMs network adapter is configured "Attached to: Bridged Adapter" "Name: wlan0".

Somthing else I noticed: when trying to configure the wifi adapter by bsdconfig(8) (bsdconfig -> Network Management -> Wireless Networks ), this error message pop's up:

View attachment 21995

on my case, Virtual Box and host system both doesn't detect the adapter

 

[T-Daemon]

on my case, Virtual Box and host system both doesn't detect the adapter

Perhaps the adapter is missing an explicit device description for the driver to attach to the device.

If this is the case, then some files in the FreeBSD source code needs to be modified, and a new kernel build.

But lets see first what the situation is by examining the system information.

With the DWA-172 adapter plugged in (on the host system, not VBox), please provide full output of:

1. usbconfig
2. usbconfig -d <unit.addr of the wifi adapter> dump_device_desc
3. dmesg Full dmesg output, not a screenshot of a terminal window or similar like last time with VBox, which is pretty much useless.

 

[astyle]

on my case, Virtual Box and host system both doesn't detect the adapter

Maybe you just need to turn on UBS 2.0 in VirtualBox settings? This may be a per-VM setting.

 

[Leviwryi]

Perhaps the adapter is missing an explicit device description for the driver to attach to the device.

If this is the case, then some files in the FreeBSD source code needs to be modified, and a new kernel build.

But lets see first what the situation is by examining the system information.

With the DWA-172 adapter plugged in (on the host system, not VBox), please provide full output of:

1. usbconfig
2. usbconfig -d <unit.addr of the wifi adapter> dump_device_desc
3. dmesg Full dmesg output, not a screenshot of a terminal window or similar like last time with VBox, which is pretty much useless.

 

[Leviwryi]

Dmesg

 

[astyle]

Dmesg

Please don't go mixing VirtualBox with metal when asking for help.

BTW, there's a good way to get a copy of your dmesg out if you don't have a Samba/NFS fileshare set up on your machine (but machine has Internet access):

% dmesg > dmesg.txt
% cat dmesg.txt | nc termbin.com 9999

 

[T-Daemon]

Dmesg

Patching a dmesg together from monitor image outputs is not ideal. If the machine has a internet connection, proceed as astyle suggested.

If the machine has no internet, redirect dmesg into a file (dmesg > dmesg.txt), transfer file on a USB device, transfer the device to a machine with internet, post here.