RPi3 WiFi issues with onboard chip
The onboard wifi seemed to die a while back after I used the rpi-update utility so I stopped using it and just stuck with the reliable Slackware-ARM+cabled ethernet but I'd like to resolve it.
On boot it throws up the following messages that seem to be related to the problem: Code:
[ 4.461534] usbcore: registered new interface driver brcmfmac Network mode on my router is 802.11b/g/n Domain is China Channel is 7 Frequency bandwidth is 20MHz/40MHz I have tried wpa_supplicant with everything I can find to resolve it (including turning off all authentication) and nothing seems to work. I have tried making rc.firewall not start at boot but no luck. Have I fried the onboard wifi or am I just being thick as usual? |
I gather you upgraded. Does it work if you downgrade it?
|
Your issue is wifi is just not working? Searching for "not a ISO3166 code" there's this
Code:
sudo iwconfig wlan0 power off |
Quote:
The RPi3 onboard WNIC is tricky at the best of times. I've stopped using it because it's just cheap and unreliable, in my experience. So without intentionally dancing around your question/problem I'd advise you to get hold of the easiest USB wireless adapter you can lay your hands on and use that instead. It's more than likely going to serve you better. However, if you don't have access to one of these, take a look at alienBOB's pretty comprehensive networking guide which might help to point you in the right direction: http://alien.slackbook.org/dokuwiki/...eless_networks Also, there's the following SARPi page which you might find useful: http://sarpi.fatdog.eu/index.php?p=wireless-nic Hope it helps. :cool: |
Just a shot in the dark: If you have installed some HAT onto the Raspberry Pi there can be interferences. Lately I tried an Sound Hat (DAC) for example, but that one had reportedly a broken design, so that two parts of it are electro-magnetical interfering with the Raspberry's Wifi chip. So if you have installed any additional hardware part please be sure to test Wifi also without it.
|
Quote:
Quote:
Quote:
The most frustrating part is that iwlist scan shows the router with the correct ESSID but the %^&$$ thing just won't associate with it. Quote:
|
I don't know if this is any help for you since I don't have a RPI3, but I have found that installing wicd from extra and letting it handle wireless connections with broadcom cards works best. I never had any luck with networkmanager or manual configs. I also found after an upgrade that the newest drivers from broadcom (even though they are supposed to be compatible) didn't work consistently with my card. I had to download and build an older driver version to regain consistent operation.
|
1. aircrack-ng
2. kismet 3. wireshark and try capture and analyze what Pi "hears" and what it "says" to the AP. I had quite few times "almost" working drivers since 2k5 (PCI-ACX) over a wide variety if chips sometimes it's just the driver (kernel update and maybe even a patch only helps). Not that I solved anything, but a point to an viable direction? |
I'm surprised that you couldn't restore function with a return to what was (I presume) a working system. What have you installed now?
When I have this issue, I try and narrow it down. Booted up & wifi started, post the output of these run one at a time in the given order (presuming wlan0 is your wifi device) Code:
ifconfig wlan0 up |
Thanks for those.
I've just (yesterday) had a cataract operation so it'll be a little while until I get back to trying this. I'll will post back when I start up trying again. Cheers. |
My sympathies. I know about life's limitations. Get well soon.
|
Meh, I am convinced it's broken now or the firmware is simply not compatible with my router.
I put raspian onto a card and then openelec and neither can connect to my WiFi. Even if I fiddle with the router settings to turn off all security my (old) Android phone will happily connect, as will my Mrs' iPhone, an iMac we have in the house, her work laptop which is on Win10, an Android tablet and an ancient SMC EZConnect g wifi dongle. Thanks to all of you that tried to help but I think it is a hardware issue, probably caused by me shorting out something or other while I play around with my breadboard! |
If you run through post #9 we might be able to call it for you.
|
Darn hot out there and allot still to do but came in to cool off and saw this thread and thought I'd throw in my two cents/pence/whatever. This is my drill.
First check if your system sees a wifi something by as root running iwconfig if iwconfig returns with a wlan0 or so your system has loaded a module for your wireless device/chip and a wirless device wlanX has be created. If there is no wlanX then your wireless chip device has not been recognised and a device created. If it has been created then here is what I would do if it was wlan0: iwconfig wlan0 essid myessid # and if the essid is broken by a space put it in quotes Then run iwconfig wlan0 to see what you get. Here's what I have out in the garden shed: Code:
root@bpi9:/home/rick# iwconfig wlan0 Ok you can now configure your wireless network connection using wicd very easily if you are GUI or an ssh X session after installing wicd as long as /etc/rc.d/rc.inet1.conf is clean and /etc/rc.d/rc.networkmanager is chmod -x and /etc/rc.d/rc.wicd is chmod +x Maybe that will help. If you are working in a terminal you can use wicd-curses which is what I do when I can but there is a problem with the packaged wicd/curses/netentry_curses.pi in slackwarearm that will stuff things up. I have one that works but I am in remiss and having not yet submitted a patch and after this post I suppose I better learn how to make a diff! |
Quote:
Code:
[root@darkmoon:~] # iwconfig wlan0 Code:
[root@darkmoon:~] # iwconfig wlan0 Code:
[root@darkmoon:~] # cat /etc/wpa_supplicant.conf Code:
[root@darkmoon:~] # wpa_supplicant -Dnl80211 -i wlan0 -c/etc/wpa_supplicant.conf |
All times are GMT -5. The time now is 06:59 AM. |