Search Linux Wireless

Re: brcmsmac in kernel driver on a Samsung NC110

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 27/03/13 11:22, Arend van Spriel wrote:
> On 03/27/2013 11:45 AM, John Talbut wrote:
>>
>>
>> On 27/03/13 10:33, Rafał Miłecki wrote:
>>> 2013/3/27 John Talbut <jt@xxxxxxxxxxx>:
>>>> On 27/03/13 07:46, Rafał Miłecki wrote:
>>>>> 2013/3/26 Arend van Spriel <arend@xxxxxxxxxxxx>:
>>>>>> On 03/26/2013 08:48 PM, John Talbut wrote:
>>>>>>> echo "14e4 4357" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
>>>>>>> bash: /sys/bus/pci/drivers/bcma-pci-bridge/new_id: No such file or directory
>>>>>>
>>>>>> This could mean you do not have CONFIG_BCMA_HOST_PCI=y in your .config
>>>>>
>>>>> Exactly. Make sure you have CONFIG_BCMA_HOST_PCI=y and that your
>>>>> host_pci.c is not modified/hacked/whatever.
>>>>>
>>>>> You can compare it with
>>>>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/bcma/host_pci.c
>>>>> bcma_pci_bridge_tbl.
>>>>>
>>>> OK, thanks, I have recompiled the kernel with CONFIG_BCMA_HOST_PCI=y and
>>>> we have some progress.
>>>>
>>>> ls /sys/bus/bcma/devices
>>>> bcma0:0
>>>>
>>>> lspci -d 14e4: -v
>>>> now has a line:
>>>> Kernel driver in use: bcma-pci-bridge
>>>>
>>>> host_pci.c is the same as torvalds.
>>>>
>>>> However, kernel log includes:
>>>> brcmsmac bcma0:0: firmware: agent aborted loading brcm/bcm43xx-0.fw (not
>>>> found?)
>>>> ieee80211 phy0: brcmsmac: Failed to find firmware usually in
>>>> /lib/firmware/brcm
>>>> brcmsmac: brcms_bcma_probe: brcms_attach failed!
>>>
>>> "Failed to find firmware". You didn't tell us if you have firmware installed.
>>> ls /lib/firmware/brcm/
>>> http://wireless.kernel.org/en/users/Drivers/brcm80211#Firmware_installation
>>>
>> Sorry, meant to do that:
>> ls /lib/firmware/brcm/
>> bcm43xx-0.fw bcm43xx_hdr-0.fw
>>
> 
> Do you have a ramdisk during boot? I suspect brcmsmac does request the
> firmware before the root filesystem is mounted.
> 
> Gr. AvS
> 

Yes.  Everything apart from the boot partition is encrypted, so,
presumably, if it tries to fetch the firmware before the root filesystem
is decripted and mounted it will not find it.  How do I prove that this
is what is happening and get round it?

Regards

John
--
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




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux