---------- Forwarded message ----------
From: Schmirr Wurst <[email protected]>
Date: 2015-05-17 16:07 GMT+02:00
Subject: Re: lspci not working
To: Hauke Mehrtens <[email protected]>
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 16:08, Schmirr Wurst wrote:
> ---------- Forwarded message ----------
> From: Schmirr Wurst <[email protected]>
> Date: 2015-05-17 16:07 GMT+02:00
> Subject: Re: lspci not working
> To: Hauke Mehrtens <[email protected]>
>
>
> 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...
I guess your system in jinxed because of the hostname you setup :-p
Ok, more seriously now. This is the nvram data I mentioned earlier. This
system may have that info stored in efi variable. You should be able to
find it in /sys/firmware/efi/efivars/nvram-*.
It may be necessary to run the following commands:
# modprobe efivarfs
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Regards,
Arend
> 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
>