Skip to content
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

Raspberry pi 4B Won’t connect to OPL though the ethernet port? #72

Open
TheRealRetroTonic opened this issue Jun 7, 2023 · 1 comment

Comments

@TheRealRetroTonic
Copy link

So when I first tried running the code it worked fine without any issues, but then I updated Opl using the ethernet. After it did that I turned off my console and Pi so I could use it the next day, but when I booted them up OPL wouldn’t load in? And my Pi had a different static IP address which was really weird.. so I thought it must be a glitch so I wiped the original SD Card, then put a new version of the Raspberry pi OS the legacy version.
I set it up the same way but the IP address wasn’t correct? I was so confused until I realised it was cause I had set the settings for my country so I just set it to default then put the OS on it fixed the IP address but now it gives an error on OPL saying 303. I’m confused could someone help?

@Profeces
Copy link

I had the same issue with my Pi where the IP address apparently changed after a reboot. What I noticed, is that if I did an ifconfig it would show the 192.168.2.1 address, but when the system started, it showed a completely different IP right before the login prompt. It was that IP address that I needed to use, not the one from ifconfig. Once I switched to that, everything else was flawless. Leave the PS2 network settings how they are in the readme, but just use that other IP it's showing you instead.

For the 303, another thing I've noticed is that if you have your media in the Pi when you boot it, it sometimes shows that 303 when connecting. Boot the Pi without your drive attached, boot the PS2 and get it into OPL as well. Once you're there, then connect the drive, and go to the network settings and connect.

Doing that every time, seems to work for me. I'm not sure why it's different than almost everyone else, but I had your exact problem and this is how I resolved it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants