RPi 3B+ with WiFi on Red, green on Ethernet - no success

Getting Started with IPFire
1

Was looking for a solution to the problem I have encountered and found your note about WiFi on Red, green on Ethernet. This is exactly the setup I have tried to do, but have not had success. I’m using a RPi 3B+, flashed a fresh ARM version of 159. The setup went smoothy, then upon reboot after doing the full setup including IP addresses, DHCP, etc., the RPi boots but never gives out an IP address, nor is accessible via a fixed IP address from a client. I have tried this 3 times with the same outcome.

Any ideas how to resolve this?

Thanks in advance

2

It is a little hard to figure out without more info.

What errors do you see during boot?

Do you see a login prompt when booting is complete?

Are there any errors in the logs at /var/log/messages?

Including pictures / screen shots would help.

3 Likes
3

Thanks for your reply. Sorry for the lack of info.

I watched the boot messages on the display and didn’t see any glaring, clear errors. The only true error is that it can’t connect to Red, but that’s to be expected since the SSID/password have not yet been set up.

I can’t get screenshots because I have no way to access the RPi with IPFire except with the command line.

Setting my laptop’s LAN to fixed IP on the Green network, I can’t ping the IP of IPFire.

I have attached the bootlog and messages files to this post. Processing: bootlog…
log_files.zip (14.2 KB)

4

Chris - did you get this working?

I am guessing (hoping) you may have seen all of the Undervoltage detected! errors.

from bootlog file:

[   15.287126] hwmon hwmon1: Undervoltage detected!

from messages log:

Aug  9 07:41:46 (none) syslogd 1.5.1: restart (remote reception).
Aug  9 07:41:55 (none) kernel: hwmon hwmon1: Voltage normalised
Aug  9 08:42:12 (none) kernel: hwmon hwmon1: Undervoltage detected!
Aug  9 08:42:16 (none) kernel: hwmon hwmon1: Voltage normalised
Aug  9 08:42:20 (none) kernel: hwmon hwmon1: Undervoltage detected!
Aug  9 08:42:28 (none) kernel: hwmon hwmon1: Voltage normalised
Aug  9 08:43:45 (none) kernel: hwmon hwmon1: Undervoltage detected!
Aug  9 08:43:52 (none) kernel: hwmon hwmon1: Voltage normalised
Aug  9 08:44:24 (none) kernel: smsc95xx 1-1.1:1.0 green0: renamed from eth0
Aug  9 08:44:24 (none) kernel: brcmfmac mmc1:0001:1 red0: renamed from wlan0
Aug  9 08:44:25 (none) kernel: hwmon hwmon1: Undervoltage detected!
Aug  9 08:44:31 (none) kernel: hwmon hwmon1: Voltage normalised
Aug  9 08:44:51 (none) kernel: Kernel logging (proc) stopped.
Aug  9 08:44:51 (none) kernel: Kernel log daemon terminating.
Aug  9 08:44:53 (none) exiting on signal 15
Aug  9 08:45:01 ipfire syslogd 1.5.1: restart (remote reception).
Aug  9 08:45:01 ipfire unbound: [1529:0] notice: init module 0: validator
2 Likes
5

Just now seeing your message. Thank you for the follow-up. I never did get it working on the 3B+. Do you think the undervoltage errors could be the cause?

6

It wouldn’t surprise me.

Undervoltage errors on RPi are said to slow down the RPi speed and result in likely freezes and/or random crashes.

It would make sense to get a power supply that can provide sufficient amps for the RPi and that has good voltage regulation, run the RPi and confirm that the undervoltage messages have disappeared and then check if the same problem with the red interface is still occurring and if so what is then in the logs.

1 Like
7

BTW, wireless devices are not known as power savers. So undervoltage errors show problems with this part of the system also. I think the wifi is going down first, before the CPU.
Without enough power the system is unpredictable.

1 Like
8

If you do buy a new supply I’d suggest buying the Raspberry Pi (official) one:

These have worked very well for me.