To get you up to speed:
I had bought two RasberryPi's 3 B and set them both up with DreamPi for use with Phantasy Star Online over the last 4 weeks, and they both worked fine to begin with. After 3 weeks one began not to connect to the servers. I used the other backup DreamPi setup for diagnoses, and it worked. I swapped out all the the ancillaries of the unworking setup, and still the backup functioned which suggested the problem was the RasperryPi unit itself.
Batteries on the line voltage inducer were replaced with new ones, even though the old batteries were tested to work on the backup Raspberry Pi setup as stated before.
All lights are on as normal.
I then used my backup for one week, and now it refuses to presumably "answer calls" from DC as the first RPi did. $80 down the drain...
PCwzrd says on the Troubleshooting webpage:
When I try and dial a connection on my Dreamcast, it says "No dial tone" or "No answer".
This means DreamPi isn't answering the call from the Dreamcast for some reason.
This is about as close of a diagnoses I can find, but his solutions have already been ruled out.
If the DreamPi isn't "answering the call", then a different version of DreamPi should work....If that doesn't change anything though...If different versions of DreamPi aren't fixing it, then does that mean the hardware on the RPi is failing after X hours of usage?
How can it possibly answer the calls for 3 weeks and then stop?
Back to present time....
I was last told to establish the ability to view the DreamPi log output....
I haven't yet setup myself to view what the DreamPi is doing in real time yet. I bought a third new Raspberry Pi.
It arrived in the mail, and I unplugged the not-working Raspberry Pi, I plugged in THE VERY SAME ancillaries: all the same line voltage inducer, DELL modem thing, same 9v battery, took the SD card directly out of the non-working RPi, and plugged everything into the brand new RPi.
I fired up XDP and it works like a charm!!! PSO goes online like nothing ever happened
I know I haven't given you view of my RPi command prompt, but is there anything you can think of that would cause an RPi so stop "answering a call" after a few weeks, but it does it RIGHT OUT OF THE BOX?
This is the second instance of this behavior, to the tee.