Well, now it works again.

@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

@mitu i'm on 4.7.14 retropie image now. everything is working. if the drivers dont work again when a new upgrade is released, i'll just have to install an older driver again. not a big deal. just glad its working.

@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!

@mitu Thanks, the backup method worked. Strangely, my psx games were missing in the .img file, but otherwise it worked and it is easy to dump those with RetroArch anyway.

@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.

@mitu thank you for the response, wanted to double check there wasn't anything that could be done retropie side first. I'll reach out to utility board manufacturer.

@soren , that's great that it works! Your post made me think of another post where someone said that they have spent more time installing the Raspberry pi than actually playing on it. It was quite the hassle to make it work but well I guess that's life, what is good usually takes some effort. Again, I am glad it now works for you =)

@hairdyeguy said in Speeding up boot time and the necessary commands:

Tried it along side to disabeling bluetooth and rainbow splash screen + inserting the quiet flag to kernel. Booting time is now 28 seconds!
Are there more things you'd recommend?

The EmulationStation settings I mentioned in my first post - they should speed up dramatically the front-end startup.

Other services that are not strictly needed - raspi-config(?), hciuart (which you don't need if you disabled Bluetooth), rpi-eeprom-update (the Pi zero doesn't have an EEPROM).
You can also disable the swap service (dphys-swapfile) and test, but the Pi 0 has limited memory and swap may be useful if you want to install from source or run other things.

I'm not sure why the dev-mmcblk0p2.device takes so long, maybe the sdcard is not so fast (?).

There may be other - more radical - options

@konrad_ziom Make sure you set-up your Wi-Fi country first before attempting to connect to your AP. Do you see your Wi-Fi in the list of when you try connecting ?

@jet how are you configuring your wifi? are you using wpa_supplicant.conf? if so please show the contents (censoring password etc)

again, please also fill out https://retropie.org.uk/forum/topic/3/read-this-first

@mitu said in Wifi & Samba Share:

@gigo said in Wifi & Samba Share:

I have WebDAV enabled on my NAS, so I assuming it would be a case of just pointing it at the synology.me address I have setup?

Webdav is not the same as CIFS, so the answer would be no. I'd advise against opening your local ROM folder to the internet. If you want to take your Pi on the go, then copy some ROMs locally and use that.

Thanks for the heads up, really appreciate the help. Now for some retro gaming :D