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

Wow, I feel super dumb. I spent too much time creating variables in c++ and nothing online told me the quotes were mandatory, just figured they were a placeholder.

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

you need to shutdown turn you pie off then set your network up with raspi-conf then it works again dont know why just does well for me anyway.

@Bravenstein How did you update without a network connection?

@Otter22 The Wifi is not setup from Emulationstation, but via the RetroPie-Setup. You should have a WiFi menu entry in the RetroPie system in Emulationstation - just like it's described in the Docs.

Not sure what changed, but I went through the WiFi configuration again and it worked this time.

Excellent, thanks! Stewart

Hi, I'm was having trouble with my ps3 controllers and discovered that removing my wifi connection eliminated it. I wanted to install this switch to make this process even easier. However, after installing it it says "Your wifi adapter seems to be blocked or is not available", even though I'm currently connected to wifi and am able to access my retropie over the network. I expected to see the block option, but it shows enable instead. Selecting enable says "sudo: rfkill: command not found" and spits me back to the retropie menu. Wondering if there's something I'm missing... Thanks!

it may be the problem of your router login panel ..you should reboot the router and then try again..