27 May
2018
27 May
'18
5:03 a.m.
With a basic build of OpenADK for the Raspberry Pi 3, I'm getting the
following error when I try to bring up wlan0.
# ifup wlan0
ip: SIOCGIFFLAGS: No such device
command failed: No such device (-19)
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect
commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
ip: SIOCGIFFLAGS: No such device
In /etc/network/interface, I have the following configured:
auto wlan0
iface wlan0 inet dhcp
wireless-ssid HomeWiFi
wireless-mode sta
wireless-security wpa2
wireless-passphrase XXXXXXXXXXXX
I presume there is an additional configuration for OpenADK required to
enable wlan0 on the Raspberry Pi 3, but I don't see anything obvious. I
have the 'iw' and 'wpa_supplicant' packages enabled, but that doesn't
seem
to be the issue.
Any tips on what I might be missing?
Thanks,
Mike Thompson
27 May
27 May
4:03 p.m.
Hi Mike,
Mike Thompson wrote,
With a basic build of OpenADK for the Raspberry Pi 3,
I'm getting the following
error when I try to bring up wlan0.
# ifup wlan0
ip: SIOCGIFFLAGS: No such device
command failed: No such device (-19)
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
ip: SIOCGIFFLAGS: No such device
In /etc/network/interface, I have the following configured:
auto wlan0
iface wlan0 inet dhcp
wireless-ssid HomeWiFi
wireless-mode sta
wireless-security wpa2
wireless-passphrase XXXXXXXXXXXX
I presume there is an additional configuration for OpenADK required to enable
wlan0 on the Raspberry Pi 3, but I don't see anything obvious. I have the
'iw'
and 'wpa_supplicant' packages enabled, but that doesn't seem to be the
issue.
Any tips on what I might be missing?
I do not think you missed anything, it is just a Bug.
I once started to try to make it work, but got distracted.
I look into it again. Strange thing, I installed Libreelec for
Testing on my RPI3 and even this did not recognized the Wifi device.
I am starting now with Raspbian to see what I am missing.
Hard to find an detailed information, which Linux kernel config
symbols are required and what firmware files need to be installed.
best regards
Waldemar
4:24 p.m.
Hi
While I haven't tried to use wifi in ADK, I do remember it worked for me
in libreelec on my Pi 3 model B+
At least it showed the available wifi networks. I did not connect to one
since I am using the wired connection.
If there's anything I can do to help, i.e. test on the B+, let me know!
Cheers
Oliver
On 27.05.2018 18:03, Waldemar Brodkorb wrote:
Hi Mike,
Mike Thompson wrote,
With a basic build of OpenADK for the Raspberry
Pi 3, I'm getting the following
error when I try to bring up wlan0.
# ifup wlan0
ip: SIOCGIFFLAGS: No such device
command failed: No such device (-19)
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
ip: SIOCGIFFLAGS: No such device
In /etc/network/interface, I have the following configured:
auto wlan0
iface wlan0 inet dhcp
wireless-ssid HomeWiFi
wireless-mode sta
wireless-security wpa2
wireless-passphrase XXXXXXXXXXXX
I presume there is an additional configuration for OpenADK required to enable
wlan0 on the Raspberry Pi 3, but I don't see anything obvious. I have the
'iw'
and 'wpa_supplicant' packages enabled, but that doesn't seem to be the
issue.
Any tips on what I might be missing?
I do not think you missed anything, it is
just a Bug.
I once started to try to make it work, but got distracted.
I look into it again. Strange thing, I installed Libreelec for
Testing on my RPI3 and even this did not recognized the Wifi device.
I am starting now with Raspbian to see what I am missing.
Hard to find an detailed information, which Linux kernel config
symbols are required and what firmware files need to be installed.
best regards
Waldemar
_______________________________________________
dev mailing list
dev(a)openadk.org
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev 
5:26 p.m.
It could also very well be that you just need to wail for wlan0 interface at startup
because it is not yet ready when trying to configure it?
I added this in my /etc/init.d/network scripts’ start-function:
echo "Waiting for wlan0 ... "
waittime=30
while [ ! -d /sys/class/net/wlan0 ] && [ $waittime -gt 0 ]; do
sleep 1
let waittime=$waittime-1
done
if [ ! -d /sys/class/net/wlan0 ]; then
echo "ERROR: Did not find wlan0 interface after 30 seconds"
fi
ifup -a > /dev/null
On 27 May 2018, at 18:03, Waldemar Brodkorb
<wbx(a)openadk.org> wrote:
Hi Mike,
Mike Thompson wrote,
With a basic build of OpenADK for the Raspberry
Pi 3, I'm getting the following
error when I try to bring up wlan0.
# ifup wlan0
ip: SIOCGIFFLAGS: No such device
command failed: No such device (-19)
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
ip: SIOCGIFFLAGS: No such device
In /etc/network/interface, I have the following configured:
auto wlan0
iface wlan0 inet dhcp
wireless-ssid HomeWiFi
wireless-mode sta
wireless-security wpa2
wireless-passphrase XXXXXXXXXXXX
I presume there is an additional configuration for OpenADK required to enable
wlan0 on the Raspberry Pi 3, but I don't see anything obvious. I have the
'iw'
and 'wpa_supplicant' packages enabled, but that doesn't seem to be the
issue.
Any tips on what I might be missing?
I do not think you missed anything, it is just a Bug.
I once started to try to make it work, but got distracted.
I look into it again. Strange thing, I installed Libreelec for
Testing on my RPI3 and even this did not recognized the Wifi device.
I am starting now with Raspbian to see what I am missing.
Hard to find an detailed information, which Linux kernel config
symbols are required and what firmware files need to be installed.
best regards
Waldemar
_______________________________________________
dev mailing list
dev(a)openadk.org <mailto:dev@openadk.org>
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev
<https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev>
28 May
28 May
6:32 a.m.
OK, thanks.
I'll see if I can get time to understand what the issue might be.
During some initial research I did come across a brief description of a
hardware problem with the Raspberry Pi 3 Wifi that may be related.
https://benjaminknofe.com/blog/2017/12/19/fix-broken-onboard-wifi-on-a-rasp…
Getting Wifi isn't terribly important to me, but it would be nice to see it
working.
Mike
On Sun, May 27, 2018 at 9:03 AM, Waldemar Brodkorb <wbx(a)openadk.org> wrote:
Hi Mike,
Mike Thompson wrote,
With a basic build of OpenADK for the Raspberry
Pi 3, I'm getting the
following
error when I try to bring up wlan0.
# ifup wlan0
ip: SIOCGIFFLAGS: No such device
command failed: No such device (-19)
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect
commands
nl80211: deinit ifname=wlan0
disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
ip: SIOCGIFFLAGS: No such device
In /etc/network/interface, I have the following configured:
auto wlan0
iface wlan0 inet dhcp
wireless-ssid HomeWiFi
wireless-mode sta
wireless-security wpa2
wireless-passphrase XXXXXXXXXXXX
I presume there is an additional configuration for OpenADK required to
enable
wlan0 on the Raspberry Pi 3, but I don't see
anything obvious. I have
the 'iw'
and 'wpa_supplicant' packages enabled,
but that doesn't seem to be the
issue.
Any tips on what I might be missing?
I do not think you missed anything, it is just a Bug.
I once started to try to make it work, but got distracted.
I look into it again. Strange thing, I installed Libreelec for
Testing on my RPI3 and even this did not recognized the Wifi device.
I am starting now with Raspbian to see what I am missing.
Hard to find an detailed information, which Linux kernel config
symbols are required and what firmware files need to be installed.
best regards
Waldemar
9:39 p.m.
Hi Mike,
Mike Thompson wrote,
OK, thanks.
I'll see if I can get time to understand what the issue might be.
During some initial research I did come across a brief description of a
hardware problem with the Raspberry Pi 3 Wifi that may be related.
https://benjaminknofe.com/blog/2017/12/19/
fix-broken-onboard-wifi-on-a-raspberry-pi-3-and-arch-linux-and-systemd/
Getting Wifi isn't terribly important to me, but it would be nice to see it
working.
What does dmesg say on your device?
My device shows -110 errors now.
Mike, Oliver, can you retest with latest master?
I updated firmware, kernel and wireless firmware and still get mmc1
-110 errors, which looks like a hardware issue with my rpi3 if I
interpret the discussions on the net correctly.
best regards
Waldemar
29 May
29 May
6:38 p.m.
Hi
I get error -2
$ iw dev
is empty.
dmesg and .config attached
Best,
Oliver
On 28.05.2018 23:39, Waldemar Brodkorb wrote:
Hi Mike,
Mike Thompson wrote,
OK, thanks.
I'll see if I can get time to understand what the issue might be.
During some initial research I did come across a brief description of a
hardware problem with the Raspberry Pi 3 Wifi that may be related.
https://benjaminknofe.com/blog/2017/12/19/
fix-broken-onboard-wifi-on-a-raspberry-pi-3-and-arch-linux-and-systemd/
Getting Wifi isn't terribly important to me, but it would be nice to see it
working.
What does dmesg say on your device?
My device shows -110 errors now.
Mike, Oliver, can you retest with latest master?
I updated firmware, kernel and wireless firmware and still get mmc1
-110 errors, which looks like a hardware issue with my rpi3 if I
interpret the discussions on the net correctly.
best regards
Waldemar
_______________________________________________
dev mailing list
dev(a)openadk.org
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev
10:04 p.m.
Hi,
lich000king wrote,
Hi
I get error -2
But the difference is, the driver is loading, it tries to open and
load the binary firmware blob and then fails with error -2.
My system fails when the wifi chip is detected on the SDIO bus early
not even trying to load any wifi driver at all.
[ 2.015329] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 2.022389] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for
chip 0x004345(17221) rev 0x000006
[ 2.037341] mmc0: host does not support reading read-only switch, assuming write-enable
[ 2.049293] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin
failed with error -2
So either simply the file does not exist in /lib/firmware/brcm/brcmfmac43455-sdio.bin
or we have the wrong one like discussed here:
https://patchwork.codeaurora.org/patch/248789/
See include/uapi/asm-generic/errno-base.h
#define ENOENT 2 /* No such file or directory */
You have latest files in package/brcmfmac-firmware/src
file brcmfmac43455-sdio.bin
brcmfmac43455-sdio.bin: data
best regards
Waldemar
30 May
30 May
1:57 p.m.
Hi
Not quite sure if I'm following, but/lib/firmware/brcm/brcmfmac43455-sdio.binexists
and is identical topackage/brcmfmac-firmware/src/brcmfmac43455-sdio.binfrom the latest adk
revision.This would mean it's not the problem described in the link?
Oliver
Am Mittwoch, 30. Mai 2018, 00:04:54 MESZ hat Waldemar Brodkorb <wbx(a)openadk.org>
Folgendes geschrieben:
Hi,
lich000king wrote,
Hi
I get error -2
But the difference is, the driver is loading, it tries to open and
load the binary firmware blob and then fails with error -2.
My system fails when the wifi chip is detected on the SDIO bus early
not even trying to load any wifi driver at all.
[ 2.015329] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 2.022389] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for
chip 0x004345(17221) rev 0x000006
[ 2.037341] mmc0: host does not support reading read-only switch, assuming
write-enable
[ 2.049293] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin
failed with error -2
So either simply the file does not exist in /lib/firmware/brcm/brcmfmac43455-sdio.bin
or we have the wrong one like discussed here:
https://patchwork.codeaurora.org/patch/248789/
See include/uapi/asm-generic/errno-base.h
#define ENOENT 2 /* No such file or directory */
You have latest files in package/brcmfmac-firmware/src
file brcmfmac43455-sdio.bin
brcmfmac43455-sdio.bin: data
best regards
Waldemar
11:24 p.m.
Hi Oliver,
Oliver Schib wrote,
Hi
Not quite sure if I'm following, but
/lib/firmware/brcm/brcmfmac43455-sdio.bin
exists and is identical to
package/brcmfmac-firmware/src/brcmfmac43455-sdio.bin
from the latest adk revision.
This would mean it's not the problem described in the link?
No, it would mean that it is the problem!
But, can you just install latest raspbian lite and check if the
wireless is working for you?
In OpenADK master I added all the firmware blobs from a fresh
Raspbian installation. But as long as my rpi3 seems to have broken
WLAN I am unable to test.
best regards
Waldemar
31 May
31 May
6:48 p.m.
Hi
Oops, installed full raspbian, not lite.
but yes, it works. I had to set the wifi country first, though. Don't
know if that's relevant.
Best
Oliver
On 31.05.2018 01:24, Waldemar Brodkorb wrote:
Hi Oliver,
Oliver Schib wrote,
Hi
Not quite sure if I'm following, but
/lib/firmware/brcm/brcmfmac43455-sdio.bin
exists and is identical to
package/brcmfmac-firmware/src/brcmfmac43455-sdio.bin
from the latest adk revision.
This would mean it's not the problem described in the link?
No, it would mean
that it is the problem!
But, can you just install latest raspbian lite and check if the
wireless is working for you?
In OpenADK master I added all the firmware blobs from a fresh
Raspbian installation. But as long as my rpi3 seems to have broken
WLAN I am unable to test.
best regards
Waldemar
2169
days inactive
2173
days old
10 comments
6 participants
participants (6)
-
lich000king -
Mike Thompson -
Oliver Schib
-
Tom Deblauwe -
Waldemar Brodkorb -
Waldemar Brodkorb