Driver for DWA-182 rev. C

[michaing]

Driver for DWA-182 rev. C

[Fourdee]

Hi Luke,

Yep, from the download like you provided, looks like i'll need to compile the driver. I'll attempt this in the next few days and keep you updated.

Have you tried using this device on the official Raspbian. Same issue?

[lukecyca]

Thanks for the reply, Dan.

I have not tried with Raspbian. I suspect the drivers are not built-in, but it would be fairly easy to install linux-headers-rpi and then build the drivers as per the manufacturer's instructions.

[lukecyca]

Anything I can do to help you with this?

If I could get the kernel headers installed, then I could try compiling the vendor's drivers to ensure they work.

[Fourdee]

Hi Luke,

Apologies for the delay, extremely busy at the moment with v100.
Yes, if you could try compiling and testing, seems the most logical as I dont own DWA-182.

You can search Apt for a list of packages:
apt-cache search linux-headers
As for which one you need, not sure, but i'd assume linux-headers-rpi.

[lukecyca]

I managed to get this build for my 4.1.10+ kernel (DietPi Jessie, updated). It wasn't straightforward so I'll post my instructions here.

1. apt-get install gcc-4.8 g++-4.8
2. Used rpi-source to download the correct kernel sources and set things up for compiling a kernel module. This utility is awesome! It automates the frustrating process of getting the correct headers since the typical linux-headers-* packages don't exist for most rasbian kernels.
3. I had no luck with the manufacturer's driver source. Instead I used rtl8812AU_8821AU_linux.
4. After building and installing as per the README in that driver, modprobe cfg80211 8812au worked and the wireless device shows up in ifconfig -a.

I'm set for now, but it would be great to include this in future versions of DietPi!

[Fourdee]

Hi Luke,

Thanks for the info 👍 , and great to hear the issue is resolved.

If the DWA-182 works on the official raspbian, i'll add support for it in DietPi also. If it does not, you will need to manually compile the driver as required.
The amount of time required to support all DietPi images with a user specific/unsupported driver would be a nightmare.

You could also compile the driver to a .deb file (eg: checkinstall). This would allow you to dpkg -i driver.deb each time you need the driver.