Arend van Spriel <arend@...> writes: > > > CONFIG_BRCM_TRACING is another way to get debug output, but I guess that > is not enabled either. > Just found this via google to enable wlan: 1. the nvram file under /sys/firmware/efi/efivars/ has a wrong MAC address. I changed it to the correct one. However, I am not sure if this is really necassary. 2. Found the following on the web: >rmmod brcmfmac >rmmod brcmutil >echo on > /sys/bus/platform/drivers/sdhci-acpi/INT33BB\:00/power/control >modprobe brcmfmac After this, I can connect to wlan! Does this give you enough information to find out, what the problem is? Or do you still need DBG output from the driver? if so, just tell me and I will try to compile and install the kernel with DBG turnded on. Its not a big deal but I stopped working on it as I found this workaround. At the momment I am trying to put these commands to rc,local. With limited success until now, But this may be caused by the fact, that they are executed too early. Will add some sleep. Another thing I found out is, that the system sometimes comes up without wlan0. It seems I have it only on every second boot. However, this could be just by incident and it is not exactly every second boot but about 50 % of all boots. Juergen -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
