I am new to this project and spent 3 days learning how to use it. Please forgive me if I ask dumb questions.
The program works fine at the beginning. After putting it in the car and logging some clips (and maybe after some reboots due to the car going to sleep), the Raspberry Pi 4B does not connect to WiFi, nor does it broadcast its AP (with the default auto setting). I might have done something wrong during installation, so I wiped everything and flashed everything all over again. Same problem after using it in the car for 1 day. The Raspberry Pi 4B does not connect to WiFi or broadcast its AP (I set the AP to force-on this time).
I have to take the Raspberry Pi 4B out and connect a monitor and keyboard to it to debug. Running sudo systemctl status NetworkManager shows:
(I take a picture and use OCR, so there might be typos)
Jul 16 08:57:30 pi NetworkManager[572]: <info> [1784206650.4956] device (wlano): supplicant interface state: associating -> disconnected
Jul 16 08:57:30 pi NetworkManager[572]: <info> [1784206650.4956] device (p2p-deu-wlano): supplicant management interface state: associating ->disconnected
Jul 16 08:57:38 pi NetworkManager[572]: <warn>[1784206658.3208] device (wlano): Activation: (wifi) association took too long
Jul 16 08:57:38 pi NetworkManager[572]: <info> [1784206658.3208] device (wlan0): state change: config -> failed (reason "no-secrets', managed-type: 'full')
Jul 16 08:57:38 pi NetuorkManager[572]: <info>[1784206658.3213] manager: NetworkManager state is now DISCONNECTED
Jul 16 08:57:38 pi NetworkManager[572]: <warn> [1784206658.3219] device (wlan0): Actiuation: failed for comnection 'netplan-wlano-OnePlus13_CPH2653'
Jul 16 08:57:38 pi NetworkManager[572]: <info> [1784206658.3222] device (wlan0): state change: failed - >disconnected (reason 'none', managed-type: 'full')
Jul 16 08:57:42 pi NetworkManager[572]: <info>[1784206662.1666] manager: startup complete
Jul 16 08:57:50 pi NetworkManager[572]: <info> [1784206670.5048] device (wlan0): supplicant interface state: disconnected -> inactive
Jul 16 08:57:50 pi NetworkManager[572]: <info> [1784206670.5048] device (p2p-deu-wlan0): supplicant management interface state: disconnected-> inactive
Maybe the WiFi + AP have conflicts, so I deleted the WiFi profile, and hoping at least I can connect with its AP. But after reboot, I still cannot see the AP. Running sudo systemctl status NetworkManager shows:
(I take a picture and use OCR, so there might be typos)
Jul 16 10:48:58 pi NetworkManager[641]: <info>E1784213338.3924] device (wlan0): supplicant interface state: internal-starting -> disconnected
Jul 16 10:48:58 pi NetuorkManagerI6411: <info>E1784213338.3928] Wi-Fi P2P device controlled by interface wlan0 created
Jul 16 10:48:58 pi NetworkManager[6411: <info> [1784213338.3936] manager: (p2p-deu-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Jul 16 10:48:58 pi NetworkManager[641]:<info> [1784213338.39421 device (p2p-deu-wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
[1784213338.3953] device (wlan0): state change: unavailable -> disconnected (reason "supplicant-available', managed-type: 'full')
Jul 16 10:48:58 pi NetworkManager[641): <nfo> Jul 16 10:48:58 pi NetuorkManagerI641]: <info> [178421333B.4013] device (p2p-deu-wlan0): state change: unavailable -> disconnected (reason 'none ', managed-type: 'full')
Jul 16 10:49:04 pi NetuorkManagerI641]: <info> [1784213344.8628] manager: startup complete
Jul 16 10:49:05 pi NetworkManagerI641): < info> [1784213345.4641] device (uapo): driver supports Access Point (AP)mode
Jul 16 10:49:05 pi NetworkManagerI6411: <info> [1784213345.4652] manager: (uapo): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/5)
Jul 16 10:49:05 pi NetworkManager16410: <info> [1784213345.5248] audit: op="device-managed" interface="uapo" ifindex=4 args-"false" pid=1420 uid=0 result="success"
Running ifconfig actually shows uap0 has its IP address 192.168.4.1 correctly. But running systemctl status dnsmasq shows:
Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:dnsmasq(8)
How do we make the service start at boot after this kind of failure?
I am new to this project and spent 3 days learning how to use it. Please forgive me if I ask dumb questions.
The program works fine at the beginning. After putting it in the car and logging some clips (and maybe after some reboots due to the car going to sleep), the Raspberry Pi 4B does not connect to WiFi, nor does it broadcast its AP (with the default
autosetting). I might have done something wrong during installation, so I wiped everything and flashed everything all over again. Same problem after using it in the car for 1 day. The Raspberry Pi 4B does not connect to WiFi or broadcast its AP (I set the AP toforce-onthis time).I have to take the Raspberry Pi 4B out and connect a monitor and keyboard to it to debug. Running
sudo systemctl status NetworkManagershows:(I take a picture and use OCR, so there might be typos)
Maybe the WiFi + AP have conflicts, so I deleted the WiFi profile, and hoping at least I can connect with its AP. But after reboot, I still cannot see the AP. Running
sudo systemctl status NetworkManagershows:(I take a picture and use OCR, so there might be typos)
Running
ifconfigactually showsuap0has its IP address192.168.4.1correctly. But runningsystemctl status dnsmasqshows:How do we make the service start at boot after this kind of failure?