Raspberry Pi Forums

callmesteve wrote:Yeah, I get none of that. I vaguely remember getting it to work once, but for some reason it has never worked again. When it did work, it was just as you described. Ever since that, though, it has caused all kinds of problems. I even tried a different Wi-Fi adapter (same model), and it still will not work.

Some problems I have gotten since reflashing with the new image, which I presume are related (they do not all happen at once, or sometimes at all):

Flashing panel, which also locks out all input devices. (This seems to be related to panel icons, like the temperature monitor or clock, that are not functioning properly. This has only happened with the weather indicator or DHCPDUI.)

Wi-Fi adapter recognized by the Pi (in lsusb), but not activated (is not assigned a wlan#), so no Wi-Fi connection apps can detect an adapter to use.

I think something also messes up the Ethernet, too.


I have tried installing the new image, NOOBS with the new image, and the newest version of OctoPi, which is based on this image. Upgrading the packages on an old image will also result in these problem(s). I cannot understand what it is, since I have not changed anything. Could it be a hardware problem?

uname -a
lsusb
lsmod
cat /etc/network/interfaces
sudo cat /etc/wpa-supplicant/wpa_supplicant.conf

callmesteve wrote:Here are the command outputs I said I would post: (I had to write these down and type them manually, since I can't do anything without the network)

Trying a different cable and power supply did not work. I will note older images still work fine, with the original power supply.
Note: I am using a custom image for 3D printer control. It behaves exactly the same way, network-wise, as the raspbian image.
WPA-supplicant posts a message on boot that it is ignoring wlan0 and wlan1. This may help you.

uname -a:
Linux octopi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux

lsusb: (I also tried connecting to the network without the USB hub, Bluetooth, etc connected, but that didn't work either)
Bus 001 Device 002 ID 0424:9514 Standard Microsystems Corp
Bus 001 Device 001 ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003 ID 0424:ec00 Standard Microsystems Corp
Bus 001 Device 004 ID 7392:7811 Edimax Technology co., LTD EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 005 ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 006 ID 0a52:2198 Broadcom Corp
Bus 001 Device 007 ID 046d:c534 Logitech Inc

lsmod:
module list (I skipped the filesize; if that is needed too I will go add that)
cfg80211
snd_bcm 2835
snd_pcm
snd_seq
snd_seqdevice
snd_timer
snd
btusb
bluetooth
rfkill
8192cu
evdev
joydev
uio
uio_pdrv_genirq

cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
allow-hotplug-eth0
iface eth0 inet manual

auto wlan0
allow hotplug wlan0
#iface wlan0 inet manual
#wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

auto wlan1
allow hotplug wlan1
#iface wlan1 inet manual
#wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

source /boot/octopi-network.txt

The command sudo cat /etc/wpa-supplicant/wpa_supplicant.conf fails to find the file.
I suspect a typo.
Running the command sudo cat /etc/wpa_supplicant/wpa_supplicant.conf, however, returns:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

Does that help?

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
	ssid="your-network-name"
	psk="your-network-password"
}

callmesteve wrote:As far as I can tell, I have not edited the files. They must have been edited by the creator of the image. I will uncomment them now.
I will go install a vanilla raspbian image and see if they are commented out there too, as the issue still happens in the regular image. Odd.

The seemingly identical commands actually differ by an underscore in the first wpa_supplicant. It is not a typo.

callmesteve wrote:Yeah, I just found that out too.

I edited the file to remove the comments. How odd that it had them, but it works now.

It seems that no lines needed to be added to the wpa_supplicant file, as that part is added automatically once you connect to a network with the desktop panel icon (or perhaps wpa_gui?).

I know for a fact that I was using a regular raspbian image before I switched to octopi for 3d printing purposes, and the network didn't work on that, either. The problem I was having was the exact same one. However, I downloaded the raspbian image again today and it connected to the network first try. Very odd! I had been trying for a few weeks to get it to connect to the Wi-Fi, on a brand-new image with no changes made, and it acted this way, but now it works once I ask about it. Sometimes it seems that is all I need to do!

Perhaps it was some kind of weird bug to do with accidentally unplugging the Pi before I configured raspi-config on first boot?
That was the only thing I can think of that might have caused this. That would be some pretty precise SD card corruption, though.

InsideJob wrote:
Quite frankly, the new networking stuff stinks though, I'm going back to the 2-17 Raspbian image anyways.