2013/3/26 John Talbut <jt@xxxxxxxxxxx>: > On 26/03/13 12:01, Arend van Spriel wrote: >> On 03/26/2013 12:43 PM, John Talbut wrote: >>> On 26/03/13 11:29, Arend van Spriel wrote: >>>> On 03/26/2013 12:13 PM, John Talbut wrote: >>>>> >>>>> On 26/03/13 10:53, Arend van Spriel wrote: >>>>>> On 03/26/2013 11:34 AM, John Talbut wrote: >>>>>>> Kernel log attached. >>>>>>> >>>>>> >>>>>> Now this is weird. I do not see any BCMA log messages. Can you give >>>>>> output of following command: >>>>>> >>>>>> $ lspci -n -s 1:0.0 >>>>> >>>>> 01:00.0 0280: 14e4:4357 (rev 01) >>>> >>>> Ok, no problem there. >>>> >>>> digging further in sysfs. Can you execute the following commands: >>>> >>>> if it exists: >>>> $ ls /sys/bus/bcma >>>> $ ls /sys/bus/bcma/devices >>>> $ ls /sys/bus/bcma/drivers >>>> >>>> if it exists also following: >>>> $ ls -l /sys/bus/bcma/drivers/brcmsmac >>> >>> root@johnwtnc110:/usr/src/linux-source-3.8# ls /sys/bus/bcma >>> devices drivers drivers_autoprobe drivers_probe uevent >>> root@johnwtnc110:/usr/src/linux-source-3.8# ls /sys/bus/bcma/devices >> >> The fact that there are no devices detected under bcma is suspicious. >> Adding bcma developer to the list. Maybe he knows about issues when >> having bcma compiled in kernel image. >> >> Regards, >> Arend > > I have just noticed that with a previous version of the kernel which I > had compiled with > # CONFIG_BCMA is not set > > there are references to brcmsmac in the kernel log. It complains about > failing to find the firmware, though. In earlier kernels brcmsmac was re-implementing "bcma" on it's own. It was changed, so now brcmsmac operates just on the bcma 80211 core. You need both: bcma and brcmsmac loaded. -- Rafał -- 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
