Comment 16 for bug 700176

The "Unknown symbol in module" I got when trying to compile bcmwl with the headers from linux-headers-2.6.37-11-generic instead of the linux-headers-2.6.37-12-generic that would have matched my kernel. Another time I got this message was when after installing a new kernel I tried to compile the module for the new one --- and the Makefile compiled it for the old one, instead. Seems like the tracking which kernel to compile the module for is somehow critical. Don't know if that can help you; The missing MODULE_LICENSE does AFAIK just indicate that the module does claim not to be GPL (which is a choice made by the creator: It hinders the module from being debugged and thus from being reverse-engineered) but does not tell which license it conforms to, instead. So this message should be therefore just a administrative matter.