Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- User:
- I want to connect my Raspberry to WiFi but it only says "turn off wireless LAN" and "advanced options".
- Assistant:
- Are you using Raspberry Pi OS desktop environment? If you open the network icon at the top right, you should see available Wi-Fi networks listed. If not, we can try the command line. Could you tell me the exact model of your Raspberry Pi and which OS version you are using?
- User:
- When I type sudo iwlist wlan0 scan, it says "interface doesn't support scanning resource temporarily unavailable".
- Assistant:
- This error can appear if the interface is down or busy. Please try first:
- sudo ip link set wlan0 up
- then
- sudo iwlist wlan0 scan
- and share the output.
- User:
- It shows IEEE 802.11 ESSID: FRITZBOX7490.
- Assistant:
- Great, it found your WiFi SSID "FRITZBOX7490". Next, try to connect by creating a wpa_supplicant config or using nmcli.
- User:
- The line with inet 192... does not show when I type ifconfig wlan0.
- Assistant:
- That means wlan0 does not have an IP address assigned yet, likely because it's not connected. Let's try to connect manually.
- User:
- When I run sudo wpa_cli reconfigure it says "selected interface 'p2p dev wlan0' FAIL".
- Assistant:
- The error shows 'p2p dev wlan0' is selected, which is the peer-to-peer interface, not wlan0. Try:
- sudo wpa_cli -i wlan0 reconfigure
- User:
- When I do sudo wpa_cli reconfigure again it says FAIL.
- Assistant:
- Make sure you specify the interface wlan0 explicitly:
- sudo wpa_cli -i wlan0 reconfigure
- User:
- I typed exactly that but still get FAIL.
- Assistant:
- Are you sure the wpa_supplicant service is running for wlan0? Let's check with:
- ps aux | grep wpa_supplicant
- User:
- When I run sudo wpa_cli -i wlan0 reconfigure it says "failed to connect to non-global ctrl ifname: wlan0 error: no such file or directory".
- Assistant:
- This indicates the control interface file is missing or wpa_supplicant is not running properly for wlan0. We need to restart or start wpa_supplicant manually.
- User:
- On starting wpa_supplicant -B -i wlan0 I get a message about "ctrl iface exists and seems to be in use - cannot override it; delete /var/run/wpa_supplicant/wlan0 manually if not used".
- Assistant:
- This means there is a stale socket file. Run:
- sudo rm /var/run/wpa_supplicant/wlan0
- Then start wpa_supplicant again:
- sudo wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
- User:
- I found the PID and killed the process but the line still remains.
- Assistant:
- Check if the process is actually gone with:
- ps aux | grep wpa_supplicant
- User:
- There is still a wpa_supplicant process running.
- Assistant:
- Kill it properly with:
- sudo kill -9 [PID]
- Replace [PID] with the actual process ID.
- User:
- After restarting wpa_supplicant I get "wpa state = INACTIVE" and the device address.
- Assistant:
- INACTIVE state means it's not connected yet. Check your wpa_supplicant.conf and make sure the network block is correct:
- network={
- ssid="FRITZBOX7490"
- psk="your_password"
- }
- User:
- The file already had that, typed it in manually.
- Assistant:
- Good. Now restart wpa_supplicant and then run:
- sudo wpa_cli -i wlan0 scan
- sudo wpa_cli -i wlan0 scan_results
- User:
- Save config failed, I did not understand what you meant by network ID and the number 0.
- Assistant:
- When you add a network in wpa_cli, it returns an ID, usually 0. You then select that network with "select_network 0" and then enable it with "enable_network 0".
- User:
- I keep getting the same output.
- Assistant:
- What output do you get exactly? Is the interface up? Check with:
- ip link show wlan0
- User:
- The first showed state DOWN, wlan0 scan shows nothing.
- Assistant:
- State DOWN means wlan0 is down. Bring it up:
- sudo ip link set wlan0 up
- User:
- The status does not change with sudo ifconfig wlan0 up.
- Assistant:
- Try with ip instead of ifconfig:
- sudo ip link set wlan0 up
- If it still stays down, check for hardware or driver issues.
- User:
- dmesg shows power save enabled messages.
- Assistant:
- Power save enabled is normal but does not cause interface down. Check with:
- rfkill list
- to see if wifi is soft or hard blocked.
- User:
- The state is still disconnected.
- Assistant:
- Try to uninstall and reinstall firmware packages:
- sudo apt update
- sudo apt install --reinstall raspberrypi-bootloader raspberrypi-kernel raspberrypi-sys-mods
- User:
- Unable to locate package raspberrypi-firmware.
- Assistant:
- Package raspberrypi-firmware is deprecated, replaced by raspberrypi-bootloader and raspberrypi-kernel packages.
- User:
- After update, WiFi networks still don't show.
- Assistant:
- Check kernel messages related to brcmfmac driver to ensure firmware loads correctly.
- User:
- Kernel logs show brcmfmac firmware loaded and power save enabled.
- Assistant:
- Firmware seems to be loading fine. Is the WiFi interface listed by nmcli device?
- User:
- nmcli device shows wlan0 disconnected.
- Assistant:
- Try to restart NetworkManager and scan for WiFi networks again:
- sudo systemctl restart NetworkManager
- nmcli device wifi rescan
- nmcli device wifi list
- User:
- No networks are listed.
- Assistant:
- Is your WiFi adapter SPI or SDIO? You said "I4 is SPI interface".
- User:
- How can I check which version I have?
- Assistant:
- Run:
- cat /proc/cpuinfo | grep Revision
- User:
- It says c03114.
- Assistant:
- Your Pi is a Raspberry Pi 4 Model B.
- User:
- lsmod shows brcmfmac loaded.
- Assistant:
- Driver is loaded but wlan0 is down. Check rfkill and ip link status.
- User:
- rfkill shows no blocks.
- Assistant:
- Run:
- ip link set wlan0 up
- and then
- iwlist wlan0 scan
- User:
- No scan results.
- Assistant:
- Check voltage:
- vcgencmd measure_volts
- User:
- Voltage is 0.8600V.
- Assistant:
- 0.86V is too low for core voltage. Your Pi might have unstable power. Use a proper power supply with 5V and 3A minimum and try again.
- User:
- Please translate the entire conversation to English and provide as a txt file.
- Assistant:
- [Providing the conversation as a .txt file]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement