Yeah, probably, it's not that common with enterprise networks I guess. Thank you for making that clear though. I actually solved it just now though. For anyone wondering I managed to connect to the network on another machine (Ubuntu) and used Network Manager. I then checked the log (according to this link) with the command: journalctl -u NetworkManager This gave me this config for wpa_supplicant.conf: country=SE ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 ap_scan=1 network={ ssid="Wifi-Name" scan_ssid=1 bgscan="simple:30:-65:300" key_mgmt=WPA-EAP WPA-EAP-SHA256 password="password" eap=PEAP fragment_size=1266 phase2="auth=MSCHAPV2" identity="username" proactive_key_caching=1 } This might not work for everyone else since the configs are always different for every network. So be sure to do the same steps as I did if you can't get it to work. So glad I finally got this, haha.

@MartyH1988 First try to follow all these steps (all of them from the top!): https://retropie.org.uk/docs/Wifi/ Then to transfer roms over the network follow these steps: https://retropie.org.uk/docs/Transferring-Roms/#samba-shares Make sure you place the roms in the right folders! Read the documentation. For example for the SNES: https://retropie.org.uk/docs/Super-Nintendo-Entertainment-System/#roms If you cant find the network share, perhaps try this way of accessing your pi through SFTP. https://retropie.org.uk/docs/Transferring-Roms/#sftp I've been unable to connect to the network share on my pi. For me it turned out I'm having a problem that windows 10 had certain group policies disabled that blocked the share. The fix was explained here. Though, I didnt like the idea of leaving insecure policies open, so I decided to transfer roms with SFTP. Or alternatively, using an old windows 7 laptop, which could access the share.

@BGallagherLA wondering if that is just an automatic thing with NetPlay and is just a computer player or something rather than someone actually joining? I just don't understand how someone can randomly join a game when you need the proper external IP to be able to access the game, and the exact same rom set, emulator and RetroPie version in order for it to work

Hi, thanks, I got it working now. After checking all different settings of my router hardware and the powerline adapters, I resetted the powerline / WiFi adapter to factory defaults an reconfigured it. Strange enough, without changing anything, it works now. I guess that it was a problem with the firmware of the powerline / WiFi adapter since the web interface wasn't available on this specific adapter as well.

Thanks. Change name of ssid was not solution. I'm in Italy . I can connect (with WPA2-PSK) only the first time after install of retropie 4.6 on my rpi4. After a reboot i can't connect. With your hint i can reconnect. Finally. NB: I see a log on startup with "FAILED to start dhcpcp on all interface" and statup is sometime slow than before (for counting time of something), but wifi works fine. Thank you very much, PiUser239043

Hostname works but only with Ethernet Tried without Ethernet just continues trying to connect I usedhostname retropie

@ParadoxGBB said in Why the hell doesn't RetroPie come with an On-Screen Keyboard?: @BenMcLean If you want someone to test, I can help. I agree that an OSK would be very useful --- now that a lot of us are sticking retropie on mobile form factors, I thought a cool scenario would be: Hop onto a plane, play some retro games. Check into a hotel, plug into the TV's HDMI, stream your home library from Kodi / Plex. I get that RetroPie may not consider itself a similar class device to a FireTV stick or something like that, but IMHO it's there as a real compelling scenario. This would make this close to the ultimate device IMHO. To keep things light, I don't want to travel with a keyboard or a ton of controllers. Controlling Kodi is pretty straightfoward with the mobile remote control scenarios they already support (Kore). But you still have to configure WiFi. A while ago I tried to follow some steps that would allow you to pair your phone to a service running on the Pi to emulate a bluetooth keyboard, but I could never get that working. So instead I ended up scripting a pretty horribile solution here (https://retropie.org.uk/forum/topic/20308/waveshare-game-hat-thoughts/21?_=1588610080231), basically running bash scripts from my phone to copy updated network settings to the Pi, falling back to the credentials to my phone's hotspot if need be and we're isolated. Turns out to you really need to shake your phone pretty hard to get these scripts running and not everyone with a smartphone is willing to root it. Anyway, apologies for diverting the topic too much here, but yes, this is a great idea. Read this and whilst I'm not saying I wouldn't like an on screen keyboard... I'm not sure the problem matches the solution. I've given some thoughts beloe If you don't want to bring controllers cables etc, why not look at a portable device. I.e. gpi. Even if you had an on-screen keyboard, you'd still need an HDMI controllers etc... maybe even a keyboard depending on the system. Does Plex work. Is that dual boot and if so how would you control it? It's not a fire TV stick, while it's great you can add things like some home media (Kodi, Spotify) to retropie. . that's not its purpose.... Everyone here does such a great job with that. You say it would make it close to the ultimate device... But the firestick you can add loads of apps (iPlayer, itv hub etc in the UK) For it to be ultimate, surely you'd want to add those, have access to sports apps like bt, sky and ESPN.. watch box office, wwe, netflix, prime, kids shows.... I think adding all those things is a hell of a lot more complex. I think if retropie incorporated all those... It's not retropie imo. I don't want to sound dismissive... And I'm sure there are many things in my post that aren't correct... I just love the work the retropie guys do and to be honest... I love the focus they make on improving performance and how they incorporate changes into it.

thank a lot for you help problem solved

@mitu The Bluetooth is down. I could not get my controllers to connect. They would with the usb cable, but not Bluetooth. I think the module might be done.

@SolemnSpirit Thanks that helped!, the moment i remove the key_mgmt, i was able to connect to the wireless! :D i appreciate you posting this!

A Raspberry Pi Zero doesn't have a WiFi NIC, so not being able to connect to WiFi is the expected result. Only Pi Zero W and Pi Zero WH have WiFi NICs.

sorry my bad just new to forrums etc and the retro thing :)

@granderjoree We don't support 3rd party images - https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu Thanks sudo /usr/sbin/sshd -d to debug helped a lot. It was the very first line /etc/ssh/sshd_config that had been uncommented, I noticed it wasn't in yours but it kind of blends in and I kept ignoring it for some reason.

@mitu You forgot to ask me an important question, "Is there a copy of that image?" The answer is yes!!! I am now back in business. This time I will pay close attention to what the heck I am changing. This was a great learning opportunity, however, so thank you very much for your support. =) I have two cards for the sake of clustering, in case you were wondering.

Alright, I've tried Ubuntu MATE 18.04 beta 1 extensively and the problem does not occur on Ubuntu at all. Must be a Raspbian issue. Definitely not my hardware. I hate to dig up a month old topic, but it is what it is. A Raspbian issue.

@mitu said in Speeding up retropie boot up on a Pi zero and turning off BT & WiFi..: @MachLid One thing you can do to speed up the boot is to disable file shares (Samba services). From what I've noticed, this is one of the services that takes up a lot of time (proportional to the total boot time) to start up. I've looked up in the RetroPie-Setup script and you only have the options to remove Samba completely (not disable it), so you'd have to use the command line to disable the services manually. sudo systemctl disable smbd sudo systemctl disable nmbd More ideas and help!! thank you very much, and I'm also going to try this as well. I have no problem killing anything unnecessary on it in order to speed up booting into the game selection menu. What I'm hoping to do with this Pi Zero is simply and only use it for mostly Atari 2600 stuff and maybe some popular arcade games from pre 1990's or earlier (if it'll handle it). I grew up with a Atari 2600 and lots of this stuff thru out the 1980s,, and thought it'd be neat to have something very little and compact (and even battery powered) and be able to quickly power on, and play some of the true classics. Not sure what I'm doing yet for a compact and portable housing or anything like that yet,, I just wanted to square away the working parts first. Thanks again.

You can transfer ROMs via a usb stick https://github.com/retropie/retropie-setup/wiki/Transferring-Roms