Slackware - ARMThis forum is for the discussion of Slackware ARM.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've tried many google tips about setting the reg domain etc, tried messing with rc.inetd and a host of other things.
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?
Have I fried the onboard wifi or am I just being thick as usual?
Most probably "No", and certainly "No".
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:
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.
I gather you upgraded. Does it work if you downgrade it?
Nope, still no joy
Originally Posted by glorsplitz
Your issue is wifi is just not working? Searching for "not a ISO3166 code" there's this
sudo iwconfig wlan0 power off
I've been through the Raspi forums and nothing suggested there works for me
Originally Posted by Penthux
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.
I've been through aliensBOB's excellent guide several times and I think I've got everything in the right place but the thing still won't connect. I've got an old wifi dongle and that will connect fine but it's slow so I think I'll just stick with wired and give up for now. It seems that somehow broadcom and my router just can't get along.
The most frustrating part is that iwlist scan shows the router with the correct ESSID but the %^&$$ thing just won't associate with it.
Originally Posted by titopoquito
Just a shot in the dark: <snip>
Thanks for that, an intriguing idea. I don't have a HAT on it, just a ribbon cable to a T-cobbler. I disconnected it and it didn't make any difference unfortunately.
Distribution: Slackware 14.1 32bit on laptop 14.2 64bit on desktop
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.
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)
ifconfig wlan0 up
ping -c3 -I wlan0 <IP of your router, e.g. 192.168.1.1>
iwlist wlan0 scan
If these read ok, you're down to dhcp & wpa_supplicant. If they don't, it's probably the driver.
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!
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:
Now I would run ifconfig wlan0 up there should be nothing returned in the terminal and if so try to see what's about with iwlist wlan0 scan. If you see something returned indicating there is life out there, ie. your lan and anything else within range.
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!
Last edited by justwantin; 02-08-2017 at 12:53 AM.