Roms won't load
-
I really appreciate all the input. @rbaker, you're right.. I did not specify. My apologies. @dankcushions, I missed that last bit.I am testing Mario Bros. on the NES emulator. The path to the rom is /home/pi/RetroPie/roms/nes. @Shakz , I tried your suggestion, but after applying chmod 777 to the samba share, there was no change. @JFamily , I cleared the read only attribute from the folder on my Windows server and rebooted, still no change in the behavior when attempting to launch the rom. :/
-
@tiberiuskirk
Hmm. That's what fixed it for me when I had that problem. What is your GPU/CPU memory split? It's a little excessive (perhaps) but I set mine to 512.
Just to be certain, you did tell it to apply to "This Folder, All Files and Subfolders" right? Verbiage might be a little off but that's the gist of it. -
@JFamily , I have not configured/modified that setting. I am new to this, and am just following the guides I mentioned above. Where would I configure the GPU/CPU memory split?
-
@tiberiuskirk
sudo raspi-configI sent you there in my guide to tell the Pi to wait for network at boot. I'm at work but I believe the memory split is under "Advanced".
Additionally, are you mounting with fstab or autostart.sh?Can you post the line you added to fstab? Please redact your username/password before posting it here.Btw, 256 is probably plenty for the split.
-
@JFamily , right now the GPU is set to 256. I did indeed tell it to apply to This folder, all files, and subfolders. The fstab line is "//192.168.1.4/RetroPie/roms /home/pi/RetroPie/smb cifs domain=domain,username=username,password=password 0 0 " without quotes. It doesn't mount on it's own. I have to run sudo mount -a once the pi boots up for the share to be visible in the /smb folder. Once I do that, I load emulationstation and I see all the NES roms just fine, just can't launch them. It does work locally though.. but I'd prefer to have it work over the network.
-
@tiberiuskirk If it isn't mounting at boot but works with "sudo mount -a", make sure you turned on "Wait for Network at Boot".
I'm not sure what your Windows system looks like (Win 7, 8, 8.1, 10, Server 2012, w/e) but I'm running Windows 10 Pro 64-bit and I had to add a few more flags than I did with earlier versions of Windows:
//192.168.1.4/RetroPie/roms /home/pi/RetroPie/smb cifs domain=domain,username=Username,password=Password,nounix,noserverino,defaults,users,auto 0 0
Try that line. Not sure if the domain flag is necessary? I may need you to elaborate on your setup beyond the Pi. Are you on a domain or workgroup, what version of windows are you running, etc?
-
@tiberiuskirk
Also, seeing your fstab line, it looks like you followed an older version of the guide. I've since omitted any suggestion of making an smb folder and instead recommend moving the entire RetroPie folder to your server. I don't think that specific step has anything to do with it and it should be just fine they way you're doing it. But, I've made a lot of improvements to the guide in the past couple of days. You may want to read over it again -
@JFamily , I just turned on "Wait for Network at Boot", I can see it fail to load the share during the post process. It succeeds after boot after running sudo mount -a. I'm running Windows 8.1 Pro. It's in the default workgroup "WORKGROUP". I added domain because initially, after following your guide, I was receiving an error when attempting to mount. After tweaking the fstab line, it finally started mounting albeit manually. I initially tried option one from your guide, but it didn't work for me. I just tried it again.. I commented out my fstab line, edited the autostart.sh file located in the /opt/retropie/configs/all directory. Rebooted, and now I don't see any roms at all.. So for some reason option one doesn't work for me. I do have the entire RetroPie contents on the server, but when I add the fstab line instead of through autostart, at the very least it mounts manually...
-
@tiberiuskirk
Strange that adding the domain flag helped, I've never had to use that before...I was replying from work yesterday and now. It was hectic at home last night so I didn't get a chance to tinker. Are you still having problems loading ROMs or have you made some progress?
-
@tiberiuskirk What line did you add to autostart.sh ?
-
Seems I had a problem with permissions, when following the github wiki I was using the mount command with SUDO, and ofcourse the owner/group was root so the user pi couldn't read the mounted dir, the fix was to include the UID and GID for PI in the options during the mount command
sudo mount -t cifs -o domain=workgroup,username=<USERNAME>,password=<PASSWORD>,nounix,noserverino,defaults,users,uid=<LINUX_USERID>,gid=<LINUX_GROUPID> //<HOSTNAME>/ROMSSHARE /home/pi/RetroPie/roms
both LINUX_USERID and LINUX_GROUPID were 1000 in my case.
Hope this helps someone from wasting as much time as I have on this problem.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.