rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu2: rtl8812au kernel module failed to build [/lib/modules/3.13.0-77-generic/build: No such file or directory. Stop.]

Status changed to 'Confirmed' because the bug affects multiple users.

I think line 4 in the dkms.conf file needs to be changed from

MAKE="'make' all"

to

MAKE="'make' all KVER=${kernelver}"

for the package to work correctly as it is building against the old kernel source instead of the new

Thanks for the suggestion, Jeremey, however, I didn't find the need to implement it. With the most recent update to kernel 4.4.0-38, it is working correctly now automatically, with no effort or changes on my part. I can run

    Modinfo 8812au

And inspect the line

    vermagic: 4.4.0-38-generic SMP mod_unload modversions 686

which shows that it was recompiled for the latest kernel when the kernel was installed. On the basis of one kernel update, I'm optimistic.

Jeremey, actually, I'm not sure, but I think the Ubuntu update was compiling the module after downloading the new kernel before the system was rebooted into the new kernel, which is how the module was compiled for the old kernel instead of the new. On rebooting, I was unable to rebuild the module for the new kernel, as it said the module was already installed. Using "modprobe -r <modname>" doesn't work because the module is installed by dmks. I had to issue the command

sudo dkms remove -m 8812au -v 1.0 -k <kernel>

to remove it. Without the kernel specified, I think it will delete module builds for all kernel versions, which means you won't be able to boot into an older kernel and have the wifi work.

Then I was able to rebuild the module from the current (latest) kernel version and install it with dkms, and everything worked fine:

    sudo dkms add -m 8812au -v 1.0
    sudo dkms build -m 8812au -v 1.0
    sudo dkms install -m 8812au -v 1.0

 As I said in my last post however, with the most recent update to kernel 4.4.0-38, the build happened automatically and this wasn't necessary. I'm optimistic the bug could be fixed.