Try the commands in post #9. Maybe they will show the device. Also try after FN+F3 to see if it makes any difference.
Try the commands in post #9. Maybe they will show the device. Also try after FN+F3 to see if it makes any difference.
Here:
Code:$ cat /sys/bus/sdio/devices/* cat: '/sys/bus/sdio/devices/mmc1:0001:1': Is a directory cat: '/sys/bus/sdio/devices/mmc1:0001:2': Is a directory $ cat /sys/bus/sdio/devices/*/uevent SDIO_CLASS=00 SDIO_ID=02D0:A9A6 MODALIAS=sdio:c00v02D0dA9A6 SDIO_CLASS=00 SDIO_ID=02D0:A9A6 MODALIAS=sdio:c00v02D0dA9A6
There doesn't seem to be any change after Fn+F3, but dmesg did spit out something connected to mmc1 (which is on the sdio bus):
[ 1427.470534] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1427.472083] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1427.473614] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1427.476387] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1427.479756] mmc1: queuing unknown CIS tuple 0x81 (9 bytes)
givesCode:modprobe -c | grep -i "02d0.*a9a6"
So lets seeCode:alias sdio:c*v02D0dA9A6* brcmfmac
Code:sudo modprobe -v brcmfmac dmesg | grep brcm
Here:
$ sudo modprobe -v brcmfmac
[sudo] password for dbclin:
insmod /lib/modules/5.3.0-40-generic/kernel/drivers/net/wireless/broadcom/brcm80211/brcmutil/brcmutil.ko
insmod /lib/modules/5.3.0-40-generic/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko
$ dmesg | grep brcm
[ 9.411132] bluetooth hci0: Direct firmware load for brcm/BCM4343A0.hcd failed with error -2
[ 9.411141] Bluetooth: hci0: BCM: Patch brcm/BCM4343A0.hcd not found
[ 2033.627030] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430a0-sdio for chip BCM43430/0
[ 2033.627265] usbcore: registered new interface driver brcmfmac
[ 2033.662422] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.Acer-One S1003.txt failed with error -2
[ 2033.663081] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.txt failed with error -2
[ 2034.673518] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
Now we're getting somewhere. It looks like a failed firmware loading. I think that it will be easy for the experts to come up with a solution.
Very interesting.
How did dmesg know that we're looking for a file called "brcmfmac43430a0-sdio.Acer-One S1003.txt"? Where did the "Acer-One" come from?
Do you think I should rename brcmfmac43430a0-sdio.txt to fit that expectation?
Thanks!
Please post results forCode:ls /sys/firmware/efi/efivars/ | grep nvram
The efivars/ directory is empty (not even hidden files).
I'm in!!!
I got a copy of the brcmfmac43430a0-sdio.txt file from GitHub and saved it to /lib/firmware/brcm/
Then, remembering how dmesg had complained about brcm/brcmfmac43430a0-sdio.Acer-One S1003.txt failing with error -2, I made copies of the brcmfmac43430a0-sdio.txt file named brcmfmac43430a0-sdio.Acer-One-S1003.txt and brcmfmac43430a0-sdio.Acer-One\ S1003.txt (because I wasn't sure which one dmesg wanted).
I then ran modprobe -v brcmfmac once again, and my new interface showed up.
Everything's perfect now.
I've lost count of how many of you forum guys were a part of this, but I'm very grateful to all of you. I plan to write this whole thing up to make it available to the community.
Thanks
David
Bookmarks