-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pi Zero 2W compatibility and sudo command #82
Comments
Bumping this. Experiencing the same issue with Sudo on a Pi4 |
I can somewhat help you with it. I researched more and turns out its a pi update thing because of which they had to change the script. Unfortunately there's conflicting stuff so it doesn't work. You can look up earlier versions of this script and try running that by simply copying and making your own .sh files. However, I faced an issue where the stuff that the .sh files were no longer downloading, maybe the servers were down I don't know and you can try that. You can always look up the BDM network thing it's just that you have to set up a server everytime you try playing and not something that you can just put together and forget about it. I can't do BDM because mine is a Pi Zero. However, the best option that I found was a bitbuilt link which you can use to set up a proper SMBshare yourself without all this pizzazz. It works well and what I'm presently using. Only caveat is I don't know of it'll work for PS3 and stuff. Here's the link for the guide: https://bitbuilt.net/forums/index.php?threads/ps2-smb-with-a-raspberry-pi-or-how-to-load-games-at-near-full-speed.1780/. BIG UPDATE that's not there in the bitbuilt link. You have to update something in the global setting in smb.conf : client min protocol = NT1 |
The setup.sh file has a line that says 'do not run this script as sudo or root' which directly conflicts with when I type in sudo ./setup.sh on my pi zero 2w. When I try using ./setup.sh without, it loads some parts of the script and then starts failing and stops after 30 seconds and OPL gives the 300 error.
The text was updated successfully, but these errors were encountered: