On 05/16/2015 04:12 AM, Schmirr Wurst wrote:
> I've already posted the message once, but as it was my first, I'm not
> sure, if it worked...
>
> Actually I'm trying to get read of a t100af from asus, that has a nice
> broadcom wifi chipset, but I'm wondering that I don't see anything
> with lspci, do that mean, that the chipset is broken ?
> (I though lspci is one level deeper than driver, and I should see
> something, even if I have driver problems) ?
>
> Could just somebody tell me if I'm right or wrong ?
On Intel Bay Trail tablets, the wifi device is frequently attached using an SDIO
bus, not a PCI connection. Accordingly, lspci will probably not show the device.
I am not familiar with any Broadcom devices that use SDIO, but I have Cc'd the
linux-wireless mailing list. Perhaps someone there will be able to help.
I am currently working with a Winbook TW100, which is another Bay Trail device.
It uses a Realtek RTL8723BS, which also has an SDIO interface.
Larry
On 05/17/15 02:21, Schmirr Wurst wrote:
> Thank you all, for your answers...
>
> In fact I'm trying to help a friend with that, and I must say I never
> hard such a complicated device...
Well, it depends what aspect you find complicated. It is pretty
straightforward device that just needs a driver to work.
> I tried as suggested to had a look at
> /sys/bus/sdio/devices, but the only devices around there a 3
> mmc1:0001:1 to :3, I guess it is something else...
>
> I already try to install brcmfmac_sdio , with some tutorial from the
> internet, but it didn't work...
> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>
> In that directory, I see a directory mmc1:0001:2
> under device I have 0xa94d
>
> I completly lost, maybe you understand that information, sorry..
I do. The fact that you see a subdirectory mmc1:0001:2 in
/sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
this device. Now would be a good time to share your (friends') kernel
log, but my guess is you are either missing firmware or nvram data or
both for this device.
And could you try to answer inline instead of top-posting.
Regards,
Arend
> 2015-05-16 23:16 GMT+02:00 Arend van Spriel<[email protected]>:
>>
>>
>> On 16-05-15 16:58, Rafał Miłecki wrote:
>>>
>>> On 16 May 2015 at 16:34, Larry Finger<[email protected]> wrote:
>>>>
>>>> On 05/16/2015 04:12 AM, Schmirr Wurst wrote:
>>>>>
>>>>>
>>>>> I've already posted the message once, but as it was my first, I'm not
>>>>> sure, if it worked...
>>>>>
>>>>> Actually I'm trying to get read of a t100af from asus, that has a nice
>>>>> broadcom wifi chipset, but I'm wondering that I don't see anything
>>>>> with lspci, do that mean, that the chipset is broken ?
>>>>> (I though lspci is one level deeper than driver, and I should see
>>>>> something, even if I have driver problems) ?
>>>>>
>>>>> Could just somebody tell me if I'm right or wrong ?
>>>>
>>>>
>>>>
>>>> On Intel Bay Trail tablets, the wifi device is frequently attached using
>>>> an
>>>> SDIO bus, not a PCI connection. Accordingly, lspci will probably not show
>>>> the device.
>>>
>>>
>>> But you should be able to browse /sys/bus/sdio/devices/ I guess
>>> (assuming bus host driver is working).
>>
>>
>> Indeed. The broadcom device would have a modalias starting 'sdio:c00v02D0d'.
>> The Asus T100 series use 43241 if I am not mistaken. It should be supported
>> by the brcmfmac driver.
>>
>> Regards,
>> Arend
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
On 16 May 2015 at 16:34, Larry Finger <[email protected]> wrote:
> On 05/16/2015 04:12 AM, Schmirr Wurst wrote:
>>
>> I've already posted the message once, but as it was my first, I'm not
>> sure, if it worked...
>>
>> Actually I'm trying to get read of a t100af from asus, that has a nice
>> broadcom wifi chipset, but I'm wondering that I don't see anything
>> with lspci, do that mean, that the chipset is broken ?
>> (I though lspci is one level deeper than driver, and I should see
>> something, even if I have driver problems) ?
>>
>> Could just somebody tell me if I'm right or wrong ?
>
>
> On Intel Bay Trail tablets, the wifi device is frequently attached using an
> SDIO bus, not a PCI connection. Accordingly, lspci will probably not show
> the device.
But you should be able to browse /sys/bus/sdio/devices/ I guess
(assuming bus host driver is working).
On 17 May 2015 at 12:23, Arend van Spriel <[email protected]> wrote:
> On 05/17/15 02:21, Schmirr Wurst wrote:
>> I tried as suggested to had a look at
>> /sys/bus/sdio/devices, but the only devices around there a 3
>> mmc1:0001:1 to :3, I guess it is something else...
>>
>> I already try to install brcmfmac_sdio , with some tutorial from the
>> internet, but it didn't work...
>> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>>
>> In that directory, I see a directory mmc1:0001:2
>> under device I have 0xa94d
>>
>> I completly lost, maybe you understand that information, sorry..
>
>
> I do. The fact that you see a subdirectory mmc1:0001:2 in
> /sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
> this device. Now would be a good time to share your (friends') kernel log,
> but my guess is you are either missing firmware or nvram data or both for
> this device.
It could also mean driver was loaded manually. So please also make
sure the friend uses kernel 4.0 or newer.
> And could you try to answer inline instead of top-posting.
Ack
--
Rafał
I'm not familiar with inline answers and mailing list, tried to put
some order in my answer + log file
2015-05-17 13:18 GMT+02:00 Rafał Miłecki <[email protected]>:
> On 17 May 2015 at 12:23, Arend van Spriel <[email protected]> wrote:
>> On 05/17/15 02:21, Schmirr Wurst wrote:
>>> I tried as suggested to had a look at
>>> /sys/bus/sdio/devices, but the only devices around there a 3
>>> mmc1:0001:1 to :3, I guess it is something else...
>>>
>>> I already try to install brcmfmac_sdio , with some tutorial from the
>>> internet, but it didn't work...
>>> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>>>
>>> In that directory, I see a directory mmc1:0001:2
>>> under device I have 0xa94d
>>>
>>> I completly lost, maybe you understand that information, sorry..
>>
>>
>> I do. The fact that you see a subdirectory mmc1:0001:2 in
>> /sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
>> this device. Now would be a good time to share your (friends') kernel log,
>> but my guess is you are either missing firmware or nvram data or both for
>> this device.
I ve attatched the kernel.log
In dmsg I see following linked with the brc driver :
dmesg | grep brc
[ 7.987661] brcmf_sdio_drivestrengthinit: No SDIO Drive strength
init done for chip 43340 rev 2 pmurev 20
[ 7.993487] usbcore: registered new interface driver brcmfmac
[ 7.996318] brcmfmac_sdio mmc1:0001:1: Direct firmware load for
brcm/brcmfmac43340-sdio.bin failed with error -2
[ 9.011572] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 10.037365] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>
> It could also mean driver was loaded manually. So please also make
> sure the friend uses kernel 4.0 or newer.
Kernel : 4.0.0 #3 SMP PREEMPT Wed Apr 22 17:52:53 MSK 2015
Distro:
Distributor ID: T100 Ubuntu 15.04
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
I ve installed it from the magic stick here
https://plus.google.com/communities/117853703024346186936
On 17 May 2015 at 02:21, Schmirr Wurst <[email protected]> wrote:
> I tried as suggested to had a look at
> /sys/bus/sdio/devices, but the only devices around there a 3
> mmc1:0001:1 to :3, I guess it is something else...
Why do you guess so? You didn't provide us any details about entries there.
> In that directory, I see a directory mmc1:0001:2
> under device I have 0xa94d
>
> I completly lost, maybe you understand that information, sorry..
You provided only one single device id, without even vendor id. Give
us at least a list of devices, e.g. by their modalias, like
cat /sys/bus/sdio/devices/*/modalias
Thank you all, for your answers...
In fact I'm trying to help a friend with that, and I must say I never
hard such a complicated device...
I tried as suggested to had a look at
/sys/bus/sdio/devices, but the only devices around there a 3
mmc1:0001:1 to :3, I guess it is something else...
I already try to install brcmfmac_sdio , with some tutorial from the
internet, but it didn't work...
actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
In that directory, I see a directory mmc1:0001:2
under device I have 0xa94d
I completly lost, maybe you understand that information, sorry..
2015-05-16 23:16 GMT+02:00 Arend van Spriel <[email protected]>:
>
>
> On 16-05-15 16:58, Rafał Miłecki wrote:
>>
>> On 16 May 2015 at 16:34, Larry Finger <[email protected]> wrote:
>>>
>>> On 05/16/2015 04:12 AM, Schmirr Wurst wrote:
>>>>
>>>>
>>>> I've already posted the message once, but as it was my first, I'm not
>>>> sure, if it worked...
>>>>
>>>> Actually I'm trying to get read of a t100af from asus, that has a nice
>>>> broadcom wifi chipset, but I'm wondering that I don't see anything
>>>> with lspci, do that mean, that the chipset is broken ?
>>>> (I though lspci is one level deeper than driver, and I should see
>>>> something, even if I have driver problems) ?
>>>>
>>>> Could just somebody tell me if I'm right or wrong ?
>>>
>>>
>>>
>>> On Intel Bay Trail tablets, the wifi device is frequently attached using
>>> an
>>> SDIO bus, not a PCI connection. Accordingly, lspci will probably not show
>>> the device.
>>
>>
>> But you should be able to browse /sys/bus/sdio/devices/ I guess
>> (assuming bus host driver is working).
>
>
> Indeed. The broadcom device would have a modalias starting 'sdio:c00v02D0d'.
> The Asus T100 series use 43241 if I am not mistaken. It should be supported
> by the brcmfmac driver.
>
> Regards,
> Arend
Thank you all, for your answers...
>
> In fact I'm trying to help a friend with that, and I must say I never
> hard such a complicated device...
>
> I tried as suggested to had a look at
> /sys/bus/sdio/devices, but the only devices around there a 3
> mmc1:0001:1 to :3, I guess it is something else...
>
> I already try to install brcmfmac_sdio , with some tutorial from the
> internet, but it didn't work...
> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>
> In that directory, I see a directory mmc1:0001:2
> under device I have 0xa94d
>
> I completly lost, maybe you understand that information, sorry..
>
>
> 2015-05-16 23:16 GMT+02:00 Arend van Spriel <[email protected]>:
>>
>>
>> On 16-05-15 16:58, Rafał Miłecki wrote:
>>>
>>> On 16 May 2015 at 16:34, Larry Finger <[email protected]> wrote:
>>>>
>>>> On 05/16/2015 04:12 AM, Schmirr Wurst wrote:
>>>>>
>>>>>
>>>>> I've already posted the message once, but as it was my first, I'm not
>>>>> sure, if it worked...
>>>>>
>>>>> Actually I'm trying to get read of a t100af from asus, that has a nice
>>>>> broadcom wifi chipset, but I'm wondering that I don't see anything
>>>>> with lspci, do that mean, that the chipset is broken ?
>>>>> (I though lspci is one level deeper than driver, and I should see
>>>>> something, even if I have driver problems) ?
>>>>>
>>>>> Could just somebody tell me if I'm right or wrong ?
>>>>
>>>>
>>>>
>>>> On Intel Bay Trail tablets, the wifi device is frequently attached using
>>>> an
>>>> SDIO bus, not a PCI connection. Accordingly, lspci will probably not show
>>>> the device.
>>>
>>>
>>> But you should be able to browse /sys/bus/sdio/devices/ I guess
>>> (assuming bus host driver is working).
>>
>>
>> Indeed. The broadcom device would have a modalias starting 'sdio:c00v02D0d'.
>> The Asus T100 series use 43241 if I am not mistaken. It should be supported
>> by the brcmfmac driver.
>>
>> Regards,
>> Arend
On 16-05-15 16:58, Rafał Miłecki wrote:
> On 16 May 2015 at 16:34, Larry Finger <[email protected]> wrote:
>> On 05/16/2015 04:12 AM, Schmirr Wurst wrote:
>>>
>>> I've already posted the message once, but as it was my first, I'm not
>>> sure, if it worked...
>>>
>>> Actually I'm trying to get read of a t100af from asus, that has a nice
>>> broadcom wifi chipset, but I'm wondering that I don't see anything
>>> with lspci, do that mean, that the chipset is broken ?
>>> (I though lspci is one level deeper than driver, and I should see
>>> something, even if I have driver problems) ?
>>>
>>> Could just somebody tell me if I'm right or wrong ?
>>
>>
>> On Intel Bay Trail tablets, the wifi device is frequently attached using an
>> SDIO bus, not a PCI connection. Accordingly, lspci will probably not show
>> the device.
>
> But you should be able to browse /sys/bus/sdio/devices/ I guess
> (assuming bus host driver is working).
Indeed. The broadcom device would have a modalias starting
'sdio:c00v02D0d'. The Asus T100 series use 43241 if I am not mistaken.
It should be supported by the brcmfmac driver.
Regards,
Arend
2015-05-17 14:57 GMT+02:00 Schmirr Wurst <[email protected]>:
> I'm not familiar with inline answers and mailing list, tried to put
> some order in my answer + log file
>
> 2015-05-17 13:18 GMT+02:00 Rafał Miłecki <[email protected]>:
>> On 17 May 2015 at 12:23, Arend van Spriel <[email protected]> wrote:
>>> On 05/17/15 02:21, Schmirr Wurst wrote:
>>>> I tried as suggested to had a look at
>>>> /sys/bus/sdio/devices, but the only devices around there a 3
>>>> mmc1:0001:1 to :3, I guess it is something else...
>>>>
>>>> I already try to install brcmfmac_sdio , with some tutorial from the
>>>> internet, but it didn't work...
>>>> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>>>>
>>>> In that directory, I see a directory mmc1:0001:2
>>>> under device I have 0xa94d
>>>>
>>>> I completly lost, maybe you understand that information, sorry..
>>>
>>>
>>> I do. The fact that you see a subdirectory mmc1:0001:2 in
>>> /sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
>>> this device. Now would be a good time to share your (friends') kernel log,
>>> but my guess is you are either missing firmware or nvram data or both for
>>> this device.
> I ve attatched the kernel.log here https://drive.google.com/file/d/0B8gm4mLCCQAgMmNlVVFSYmNjOGs/view?usp=sharing
> In dmsg I see following linked with the brc driver :
> dmesg | grep brc
> [ 7.987661] brcmf_sdio_drivestrengthinit: No SDIO Drive strength
> init done for chip 43340 rev 2 pmurev 20
> [ 7.993487] usbcore: registered new interface driver brcmfmac
> [ 7.996318] brcmfmac_sdio mmc1:0001:1: Direct firmware load for
> brcm/brcmfmac43340-sdio.bin failed with error -2
> [ 9.011572] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
> [ 10.037365] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>>
>> It could also mean driver was loaded manually. So please also make
>> sure the friend uses kernel 4.0 or newer.
> Kernel : 4.0.0 #3 SMP PREEMPT Wed Apr 22 17:52:53 MSK 2015
> Distro:
> Distributor ID: T100 Ubuntu 15.04
> Description: Ubuntu 15.04
> Release: 15.04
> Codename: vivid
> I ve installed it from the magic stick here
> https://plus.google.com/communities/117853703024346186936
2015-05-17 15:17 GMT+02:00 Hauke Mehrtens <[email protected]>:
> On 05/17/2015 03:00 PM, Schmirr Wurst wrote:
>> 2015-05-17 14:57 GMT+02:00 Schmirr Wurst <[email protected]>:
>>> I'm not familiar with inline answers and mailing list, tried to put
>>> some order in my answer + log file
>>>
>>> 2015-05-17 13:18 GMT+02:00 Rafał Miłecki <[email protected]>:
>>>> On 17 May 2015 at 12:23, Arend van Spriel <[email protected]> wrote:
>>>>> On 05/17/15 02:21, Schmirr Wurst wrote:
>>>>>> I tried as suggested to had a look at
>>>>>> /sys/bus/sdio/devices, but the only devices around there a 3
>>>>>> mmc1:0001:1 to :3, I guess it is something else...
>>>>>>
>>>>>> I already try to install brcmfmac_sdio , with some tutorial from the
>>>>>> internet, but it didn't work...
>>>>>> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>>>>>>
>>>>>> In that directory, I see a directory mmc1:0001:2
>>>>>> under device I have 0xa94d
>>>>>>
>>>>>> I completly lost, maybe you understand that information, sorry..
>>>>>
>>>>>
>>>>> I do. The fact that you see a subdirectory mmc1:0001:2 in
>>>>> /sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
>>>>> this device. Now would be a good time to share your (friends') kernel log,
>>>>> but my guess is you are either missing firmware or nvram data or both for
>>>>> this device.
>>> I ve attatched the kernel.log here https://drive.google.com/file/d/0B8gm4mLCCQAgMmNlVVFSYmNjOGs/view?usp=sharing
>>> In dmsg I see following linked with the brc driver :
>>> dmesg | grep brc
>>> [ 7.987661] brcmf_sdio_drivestrengthinit: No SDIO Drive strength
>>> init done for chip 43340 rev 2 pmurev 20
>>> [ 7.993487] usbcore: registered new interface driver brcmfmac
>>> [ 7.996318] brcmfmac_sdio mmc1:0001:1: Direct firmware load for
>>> brcm/brcmfmac43340-sdio.bin failed with error -2
>>> [ 9.011572] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>>> [ 10.037365] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>>>>
>>>> It could also mean driver was loaded manually. So please also make
>>>> sure the friend uses kernel 4.0 or newer.
>>> Kernel : 4.0.0 #3 SMP PREEMPT Wed Apr 22 17:52:53 MSK 2015
>>> Distro:
>>> Distributor ID: T100 Ubuntu 15.04
>>> Description: Ubuntu 15.04
>>> Release: 15.04
>>> Codename: vivid
>>> I ve installed it from the magic stick here
>>> https://plus.google.com/communities/117853703024346186936
>
> The driver complains about missing firmware and Ubuntu 15.04 does not
> contain it.
>
> Please place this file
> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/brcmfmac43340-sdio.bin
>
> to /lib/firmware/brcm/brcmfmac43340-sdio.bin
>
> Hauke
Before that, the system was complaining about
brcm/brcmfmac43340-sdio.bin, and now about brcm/brcmfmac43340-sdio.txt
but errors are similar...
43340 rev 2 pmurev 20
May 17 15:53:48 scheissasus kernel: [ 7.372974] usbcore: registered
new interface driver brcmfmac
May 17 15:53:48 scheissasus kernel: [ 7.374344] brcmfmac_sdio
mmc1:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.bin
failed with error -2
May 17 15:53:48 scheissasus kernel: [ 8.383270] brcmf_sdio_htclk:
HT Avail timeout (1000000): clkctl 0x50
May 17 15:53:50 scheissasus kernel: [ 11.401582] brcmf_sdio_htclk:
HT Avail timeout (1000000): clkctl 0x50
May 17 15:59:23 scheissasus kernel: [ 7.496560]
brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for
chip 43340 rev 2 pmurev 20
May 17 15:59:23 scheissasus kernel: [ 7.500086] usbcore: registered
new interface driver brcmfmac
May 17 15:59:23 scheissasus kernel: [ 7.506911] brcmfmac_sdio
mmc1:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.txt
failed with error -2
May 17 15:59:23 scheissasus kernel: [ 8.514107] brcmf_sdio_htclk:
HT Avail timeout (1000000): clkctl 0x50
May 17 15:59:23 scheissasus kernel: [ 9.531340] brcmf_sdio_htclk:
HT Avail timeout (1000000): clkctl 0x50
On 17-05-15 10:47, Rafał Miłecki wrote:
> On 17 May 2015 at 02:21, Schmirr Wurst <[email protected]> wrote:
>> I tried as suggested to had a look at
>> /sys/bus/sdio/devices, but the only devices around there a 3
>> mmc1:0001:1 to :3, I guess it is something else...
>
> Why do you guess so? You didn't provide us any details about entries there.
Indeed a wrong guess. The sdio specification allows a physical sdio
device to provide multiple sdio functions, which are instantiated as
devices in the linux driver model. So they will have the same modalias.
>> In that directory, I see a directory mmc1:0001:2
>> under device I have 0xa94d
>>
>> I completly lost, maybe you understand that information, sorry..
>
> You provided only one single device id, without even vendor id. Give
> us at least a list of devices, e.g. by their modalias, like
> cat /sys/bus/sdio/devices/*/modalias
>
Converting 0xa94d gives 43341, which does not look like a coincidence to
me. So this Asus device comes with a newer chip, but it is supported by
brcmfmac (provided vendor id is indeed 0x02d0!).
Regards,
Arend
On 05/17/2015 03:00 PM, Schmirr Wurst wrote:
> 2015-05-17 14:57 GMT+02:00 Schmirr Wurst <[email protected]>:
>> I'm not familiar with inline answers and mailing list, tried to put
>> some order in my answer + log file
>>
>> 2015-05-17 13:18 GMT+02:00 Rafał Miłecki <[email protected]>:
>>> On 17 May 2015 at 12:23, Arend van Spriel <[email protected]> wrote:
>>>> On 05/17/15 02:21, Schmirr Wurst wrote:
>>>>> I tried as suggested to had a look at
>>>>> /sys/bus/sdio/devices, but the only devices around there a 3
>>>>> mmc1:0001:1 to :3, I guess it is something else...
>>>>>
>>>>> I already try to install brcmfmac_sdio , with some tutorial from the
>>>>> internet, but it didn't work...
>>>>> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>>>>>
>>>>> In that directory, I see a directory mmc1:0001:2
>>>>> under device I have 0xa94d
>>>>>
>>>>> I completly lost, maybe you understand that information, sorry..
>>>>
>>>>
>>>> I do. The fact that you see a subdirectory mmc1:0001:2 in
>>>> /sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
>>>> this device. Now would be a good time to share your (friends') kernel log,
>>>> but my guess is you are either missing firmware or nvram data or both for
>>>> this device.
>> I ve attatched the kernel.log here https://drive.google.com/file/d/0B8gm4mLCCQAgMmNlVVFSYmNjOGs/view?usp=sharing
>> In dmsg I see following linked with the brc driver :
>> dmesg | grep brc
>> [ 7.987661] brcmf_sdio_drivestrengthinit: No SDIO Drive strength
>> init done for chip 43340 rev 2 pmurev 20
>> [ 7.993487] usbcore: registered new interface driver brcmfmac
>> [ 7.996318] brcmfmac_sdio mmc1:0001:1: Direct firmware load for
>> brcm/brcmfmac43340-sdio.bin failed with error -2
>> [ 9.011572] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>> [ 10.037365] brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>>>
>>> It could also mean driver was loaded manually. So please also make
>>> sure the friend uses kernel 4.0 or newer.
>> Kernel : 4.0.0 #3 SMP PREEMPT Wed Apr 22 17:52:53 MSK 2015
>> Distro:
>> Distributor ID: T100 Ubuntu 15.04
>> Description: Ubuntu 15.04
>> Release: 15.04
>> Codename: vivid
>> I ve installed it from the magic stick here
>> https://plus.google.com/communities/117853703024346186936
The driver complains about missing firmware and Ubuntu 15.04 does not
contain it.
Please place this file
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/brcmfmac43340-sdio.bin
to /lib/firmware/brcm/brcmfmac43340-sdio.bin
Hauke
On 17 May 2015 at 11:27, Arend van Spriel <[email protected]> wrote:
> On 17-05-15 10:47, Rafał Miłecki wrote:
>> On 17 May 2015 at 02:21, Schmirr Wurst <[email protected]> wrote:
>>> In that directory, I see a directory mmc1:0001:2
>>> under device I have 0xa94d
>>>
>>> I completly lost, maybe you understand that information, sorry..
>>
>>
>> You provided only one single device id, without even vendor id. Give
>> us at least a list of devices, e.g. by their modalias, like
>> cat /sys/bus/sdio/devices/*/modalias
>>
>
> Converting 0xa94d gives 43341, which does not look like a coincidence to me.
> So this Asus device comes with a newer chip, but it is supported by brcmfmac
> (provided vendor id is indeed 0x02d0!).
I had no idea its supported, it would be nice if you could keep wiki
page up to date. I've just added entries for BCM4334[01]:
https://wireless.wiki.kernel.org/en/users/drivers/brcm80211#brcmfmac
--
Rafał