Use usb wireless fail

question: why is no wireless extensions

steps:

1.insmod 8812au.ko

image

2.iwconfig

For “1.insmod 8812au.ko” the tainting is irrelevant and not an issue. This is a statement of not having a GPL license for that driver (e.g., the manufacturer provided the source or the precompiled binary with a different license). The practical side is that the kernel.org people won’t debug that.

I’m not sure about “2.iwconfig”. Technically this would be from no driver for that function, but no driver might simply be a load failure. Wireless devices have different regulations around the world, and so various aspects are not built into the hardware. As a result one needs to set up the hardware for a specific region of the world, and this is usually done with a firmware upload to the device. Such firmware uploads are usually agnostic to the o/s which loads it since it goes into the device and not into the host. Many manufacturers have both a driver and a firmware download for wireless devices, and you might be missing the firmware or the driver (or both). What would be a more interesting bit of information (pun intended, I’m terrible!) is to boot without the USB device, then monitor “dmesg --follow” (use sudo if needed), and then watch what log lines appear as a result of plugging in the USB device. Copy and paste that bit of log from the plug-in event; this should offer information about detecting the device, with USB working, and if any driver is assigned. I saw the renaming part, which means likely the USB end works (the renaming is part of the udev system, and this triggers upon detecting and identifying relevant USB hardware plug-in).

The last image tends to say the driver is loaded, without error, and the system knows about the network device, but the device never achieved setup. This latter could be for other reasons, but given what’s showing up it tends to mean you need the firmware for that device (often the manufacturer’s web site has this, and it won’t matter which o/s you use if it is installed correctly; any variants would be for region of the world or for some sort of install wrapper, but the payload will be the same regardless of o/s).

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