@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

@entozoon please don't. You can edit your first post and make it clear it's a Raspbian issue preferably leaving original text in place for reference) (please don't blank your post as it will mess the thread up). You can't delete the entire topic anyway.

@xxalphawolf420xx From the 2nd screenshot, I see that the WLAN Country hasn't been set. It shows as DFS-UNSET, while on a working system it should show:

root@pie4:/home/pi# iw reg get global country UK: DFS-ETSI (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A)

The other command screenshot looks like the command's been miss-typed (wlan instead of wlan0).
Check again your wpa_supplicant.conf and make sure it's correct - no extraneous characters, proper newlines, no funny quotes, un-balanced parantheses {/}. Post it here to take a look.

I had issues with Pi4 wifi too. In my case I was noticing it when sending files over Samba from W10 or using FTP, and also scraping problems. I'd get constant disconnects and transfer speeds of around 200kb/s even when it would stay working.

I found mentions online of known issues where noise from the HDMI output can disrupt the wifi signal. Every instance I saw talked about said it was only over a certain resolution (1440 I think), but I decided to try disconnecting my 5" screen anyway, which runs 800x480, and as soon as I did that the speeds went up to around 3-5MB/s and the connection stays stable.

@Donkbot said in USB wifi dongle and retropie:

Am I going to have to build the project first?

There are installation instructions (using dkms) on the project page - there's no need for a 'release'.

We don't support 3rd party images - image your sd card with the image from retropie.org.uk/download. We don't know how the sdcard you purchased was configured or pre-installed with RetroPie.

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.

@piuser239043 thanks this corrected my problem!