That’s mighty strange, could you whack a photo of them up on here?
The very occasional one having hardware issues is likely, but the chances of you coming across two are slim.
This is with a brand new Jessie/Jessie Lite image from https://www.raspberrypi.org/downloads ?
And no rpi-update (curse its very existence!) tomfoolery?
If you run sudo dmesg | grep 80211 on either, do you see anything?
I’m at work at the moment. But yes. Done all that. I’ve got a bad 2. Typical. Luck of the draw. Had to happen to someone. And they Are both v1.1 W’s
I have reloaded them both with each of the last 3 releases.
Same issues. Boot up fine. Just no wifi. Ssh’d in no problem. Just no wifi.
I am confused, how are you getting in via ssh? perhaps if you have an ethernet adapter it is somehow messing things up… or have you configured them for otg?
Hi there,
Hate to add to your woes, but same thing. Here’s what I’ve done:
Currently:
So I’m now stuck. One thing I didn’t try from elsewhere is moving the ssid and password into interfaces file.
Shall I return it? Best regards Hugh
Can you run vcgencmd otp_dump and post the output?
Cheers!
Here we go:
08:00000000
09:00000000
10:00000000
11:00000000
12:00000000
13:00000000
14:00000000
15:00000000
16:24280000
17:1020000a
18:1020000a
19:ffffffff
20:ffffffff
21:ffffffff
22:ffffffff
23:ffffffff
24:ffffffff
25:ffffffff
26:ffffffff
27:00005050
28:1401e905
29:ebfe16fa
30:009000c1
31:00000000
32:00000000
33:00000000
34:00000000
35:00000000
36:00000000
37:00000000
38:00000000
39:00000000
40:00000000
41:00000000
42:00000000
43:00000000
44:00000000
45:00000000
46:00000000
47:00000000
48:00000000
49:00000000
50:00000000
51:00000000
52:00000000
53:00000000
54:00000000
55:00000000
56:00000000
57:00000000
58:00000000
59:00000000
60:00000000
61:00000000
62:00000000
63:00000000
64:00000000
65:00000000
66:00000000
Looks like the revision ID is correct, I suspect there might be a board-level (hardware) fault with your Pi at play here.
You should never use rpi-update by the way, it’s not an update tool, but instead installs pre-release kernel, modules and firmware on your Pi.
It’s possible, also, that there’s something up with your wpa_supplicant.con but I’m not quite sure how to test for that. What happens if you do:
sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
That gives me:
Successfully initialized wpa_supplicant
and then it blocks until I control-C
Thanks for the tip about rpi-update, that should be a little more prominent.
Aha (for others too), just found:
sudo iwlist wlan0 scan | grep <part of my ssid>
This turns up my complete ssid, so you are right there’s probably something else wrong with wpa_supplicant.conf or the config somewhere else.
So, thanks, I’ll carry on for a bit, but it looks as though this is not hardware.
Thar’s interesting. I wonder if it’s a rogue character or something making its way into wpa_supplicant.conf. Did you create the wpa_suppliant.conf on a Windows PC and drop it into /boot?
Ok, nearly there, I removed the proto and pairwise entries in my wpa_supplicant.conf to make the whole thing more liberal and now:
brings the network up, then blocks. I can ping, be ping-ed etc. So, a few things to clear up, such as network doesn’t seem to come up automatically on boot, but, if necessary I can work around that. Next stop ssh, but that should be simple?! Thanks again for your help.
With the right wpa_supplicant.conf in place, network should come up automagically on boot. You could try sudo ifdown wlan0 and then sudo ifup wlan0 to give it a kick.
All good now, thanks, ssh and (because I’m lazy) sshfs too. Last problem was interfaces file, now reverted to default and collect IP address from dhcp on the router. Not quite what I want but it’ll do for the moment.