@mitu Thanks

@StuMcBill

So, I've updated the bootloader to "NVME/USB Boot" (got the green screen and rapidly flashing green light), removed the SD card, placed a USB stick (flashed with Raspbian Lite) into one of the USB3 slots, and it won't boot.

I get the message below:

"Raspberry Pi 5 - 4GB

bootloader: 6fe0b091 2024/06/05

update-ts: 1718268387

board: c04170 ce7cb976 d8:3a:dd:a6:ef:65

boot: mode USB-MSD 4 order f14 retry 0/128 restart 1/-1

SD: card not detected

part: 0 mbr [0x00:00000000 0x00:00000000 0x00:00000000 0x00:00 power: supply: RPi USB-PD 5000 mA CC1 PMIC: reset normal 0x0 us net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0

tftp: 0.0.0.0 00:00:00:00:00:00

display: DISPO: HDMI HPD=1 EDID=ok #2 DISP1: HPD=0 EDID=none #0

Boot mode: USB-MSD (04) order f1

USB2[1] 000206e1 connected

USB2[1] 0020003 connected enabled

USB2 root HUB port 1 init

USB2[1] 000206e1 connected

USB2[1] 00200e03 connected

enabled

USB2 root HUB port 1 init

USB MSD stopped. Timeout: 25

Boot mode: SD (01) order f

seconds

Failed to open device: 'scard'

Failed to

(cmd 371a0010 status 1fff0001)

Boot mode: RESTART (0f) order 0

open device: 'scard (cmd 371a0010 status 1fff0001)

Boot mode: USB-MSD (04) order f1

USB2\1) 000206e1 connected

USB2(1) 00200e03 connected enabled

USB2 root HUB port 1 init"

Any ideas?

@mituthe only things changed or added have been when I have started the desktop(via cli and startx) but nothing has touched Network etc... And like I have stated the addon Scaper works fine as does any and all network features once in Desktop.

Oddly just notice I nolonger can see an IP address shown but like I said I can access by SSh to the same IP it always uses

and booting to desktop and this shows IP address... something is clearly wrong with retropie side

@rasp_renegade What are you using for an image ?

Other Pi is now back to faster wireless speeds as well.

Awesome! :D

@erv93 said in Hi,Pi3B, Can’t set Country from Raspi-config:

Hardware issue ?

Loos like it.

@Andlau
Have you tried using a wpa_supplicant.conf file? In retropie docs, see “Connecting to WiFi Without a Keyboard”. Works great on my Gpi. You shld probably remove your existing WiFi config before trying it.

https://retropie.org.uk/docs/Wifi/

@hawkes_84 I'd like them to do an M30 Pro with dual analogues, hard to fit on the 6 button layout though. There's a cheapo Chinese one that sort of does it, they've tilted the buttons the other way to make room for the right analogue. From what I could work out though it's not a proper 6 button layout, one of them is for turning on autofire.

Got a 2.4G M30 on the way for my real Mega Drive, can't wait!

This fix did not survive a reboot, so I added modules-load=brcmfmac roamoff=1 feature_disable=0x82000 into /boot/cmdline.txt and it seems to work.

@Joltron Cool. Thanks for digging this adapter up. Should be a safe bet, as the advertised chipset ASM1153E is a ASMedia. It has also a more compact form factor than the CSL I own and an USB-C adapter.

Hi,
unfortunately, I do not know how to help with your actual issue; just for anyone reading, according to the specifications, the Raspberry Pi 3 B+ actually does have 5 GHz Wifi: "2.4GHz and 5GHz IEEE 802.11.b/g/n/ac wireless LAN"

@philcomm First off, I'm sorry that your OSK as originally engineered looks like it won't be accepted --- but I wanted to thank you for really moving the ball forward on this, because it looks like the python-based one will make it through as per recent comments on the PR. This is going to save a lot of people time and frustration and you should get a large chunk of the credit.

For fun last week as I was setting up my Zero2W I connected via SSH to it and attempted to enter Wifi via my phone using the existing infrastructure by executing RetroPie-Setup directly. Although in theory this seemed like a good idea, the WiFi won't drop and reconnect to a new network when you're using that connection for the terminal session, turns out. So, still very clunky.

Will check out your music suggestion, and also the new OSK coming down the pike. Thanks so much.

I think I might have found some quirks around the safe shutdown script with the Zero2W around pin allocation and interaction with WiFi but I want to do some more testing this week before making further topics or inquiries about it here. I also will share some additional script suggestions / observations too.

For more information on supported chipsets:
https://wiki.debian.org/WiFi

For more information about supported brands and models (linked also from above site):
http://linux-wless.passys.nl/query_hostif.php?hostif=USB

TL;DR chipsets Ralink, Atheros, Atmel, Prism are mostly well supported. Realtek: depends on model, to be avoided: Broadcom. But do search the internet about Linux compliance before buying a specific model.

I use a Netgear A6210 (USB ID 0846:9053) which depends on firmware mediatek/mt7662u.bin. Listed here as mt76 flavor: https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers (this is also the most accurate list to my knowledge)
Depending on which model you pick, you will have to install the package firmware-linux-nonfree, see also first link above.

HTH

I see this topic is quite old but I had this problem as well. Perhaps adding it here will help others find it more easily. My hubpiwi stopped working when I upgraded my raspberry pi zero (no W) with the hubwipi to raspbian bulleye. The thing I finally stumbled on to was to add wext to the wpa_supplicant options. Here are the details with thanks to those who wrote this up:

https://www.linuxbabe.com/debian/connect-to-wi-fi-from-terminal-on-debian-wpa-supplicant

The following is needed for hubwipi using rtl8188EUS
lsusb ->
ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

You can get the wifi working from the command line using this:

sudo wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf

Unfortunately, it will be gone after a reboot. To get it to start at boot time see (with my thanks here as well)

https://superuser.com/questions/1434621/set-wpa-supplicant-default-driver-on-startup

Here is what worked for me: To the end of the file /etc/dhcpcd.conf. add:

interface wlan0 env ifwireless=1 env wpa_supplicant_driver=wext

Your interface name may be different from wlan0. Running the command

ip addr

will tell you the name.

I have tried this on other raspberry pi zero w's and adding the "wext" did not seem to bother them. I did not do too much testing here so I only add the wext when I need it.

One of the notes I saw warned that the network speed of the rtl8188eus was low and I experienced this as well but it was sufficient for my purpose and let me update the OS on the rpi zero with the hubwipi.

I hope this helps someone searching for how to get the hubwifi to work again with a newer Raspian OS release.

@jamrom2 So, I'm not sure how to wipe static IPs from the system. It keeps saying the IP is unknown, as it can't connect.

@seannyboy08 said in No Wlan0 interface detected:

answer to the f4 command prompts -
iw get reg
global
country 00: DFS-UNSET

You haven't set the WiFi country, as indicated in one of the first replies to your post. Please do so before configuring WiFi - https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md.

After some tries clearing my head i erased the interfaces file (auto lo iface etc...), rebooted and i got connected though ethernet.

Then i installed all the latest versions of everything.

I tried to connect to my WIFI and it dint, BUT it connected to my 5G WIFI!

Now i have internet through WIFI. Its working im not touching anything else!

Thank you!

@themazingness
Hi!
Just for log information, I had this same problem today and I solved using this:

make a copy of /etc/network/interfaces
sudo cp /etc/network/interfaces /etc/network/interfaces.old

append to the file /etc/network/interfaces
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

enable the wpa_supplicant service and restart
sudo systemctl enable wpa_supplicant.service
sudo systemctl restart wpa_supplicant

*restart the system
sudo reboot now

@hairdyeguy said in Is it possible to save multiple wifi networks on retropie?:

Just to be clear, when you said boot partition, you meant the extra "drive" that appears on windows and can be accessed on windows, not the folder inside retropie, right?

Yes, that one.