Blizzrdball
Forum Noob
Hey there!
I'm making an account here originally to post a comment to the PSBBN thread for help, but I can't do that due to site restrictions so I'm making a separate thread here hopefully to get some help.
Here's the cursory hardware info I'm working with:
Console: PS2 Phat - SCPH-50001/N
Network Adapter: SCPH-12801 (Original/Official)
SATA Adapter: BFX_PNA_SATA V3.0 (Came from Gamestar Network "Adaptor", SSPH-10350, swapped IDE board in SCPH-12801 with this board)
SSD: Kingston A400 960GB (SA400S73/960G)
OS: EndeavourOS/Linux Mint (Both fresh installs)
I'm having issues where on my PS2 with CosmicScales PSBBN image, I can't get the drive image to boot properly.
The PS2 will boot normally, start up as if it's booting an image or game (no disc in console), and then sit at a black screen. The orange drive activity light will be on for ~1-2 minutes, flashing as though it's doing normal activity, and then it will turn off. The PS2 will be stuck at a black screen again for ~3 more minutes before kicking me back to browser.
I've written the image via. EndeavourOS using a cloned repo from the github. I ran the script in the order of 01>02>03>04 as intended and installed the PSBBL accordingly. Despite this, the image won't boot on my console.
I also used a FMCB memory card to boot uLaunchELF and confirmed the drive was readable and formatted properly, and from here I tried to launch the PSBBL/N .ELF directly, but got the same black screen/drive activity happens before it just hung at a black screen forever.
The first time I wrote the image, I used an Inland 512GB SSD. I ran into the issue and tried again without writing any games to the drive to test and ran into the same issue. From here assuming drive compatibility was an issue, I picked up a WD Blue 500GB SSD from Micro Center since they had no Kingston A400's. Using the same process of troubleshooting as the Inland drive, I had the same outcome on all attempts. At this point, I bit the bullet and assumed a second strike-out on drive compatibility and picked up the Kingston A400 drive. Wrote the image again, same problems.
At this point I was getting desperate and thought maybe it's the Arch version of the script that's having issues. I make a Linux Mint live image, boot into that, git clone the repo and run the scripts in order again, and still run into the same issue.
At no point have I received any errors during the drive write process in either Linux environment, the PS2 does seem to be able to see and read the drive successfully, and it most certainly attempts to boot some sort of .ELF on startup; but whatever it's trying to do is failing and I can't for the life of me figure out why.
I've done a lot of digging and can't find anyone else having the same issue. I don't have another working phat PS2 to test on, and I'd like to avoid buying another third party drive adapter to salvage the board from if I can help it after having gone through and bought two drives and returned one solely for this project now.
If anyone has any ideas on what's going on here or what I can even do anymore short of buying a new SATA adapter, I'd really appreciate any considerations people might have to help.
Thanks for reading!
I'm making an account here originally to post a comment to the PSBBN thread for help, but I can't do that due to site restrictions so I'm making a separate thread here hopefully to get some help.
Here's the cursory hardware info I'm working with:
Console: PS2 Phat - SCPH-50001/N
Network Adapter: SCPH-12801 (Original/Official)
SATA Adapter: BFX_PNA_SATA V3.0 (Came from Gamestar Network "Adaptor", SSPH-10350, swapped IDE board in SCPH-12801 with this board)
SSD: Kingston A400 960GB (SA400S73/960G)
OS: EndeavourOS/Linux Mint (Both fresh installs)
I'm having issues where on my PS2 with CosmicScales PSBBN image, I can't get the drive image to boot properly.
The PS2 will boot normally, start up as if it's booting an image or game (no disc in console), and then sit at a black screen. The orange drive activity light will be on for ~1-2 minutes, flashing as though it's doing normal activity, and then it will turn off. The PS2 will be stuck at a black screen again for ~3 more minutes before kicking me back to browser.
I've written the image via. EndeavourOS using a cloned repo from the github. I ran the script in the order of 01>02>03>04 as intended and installed the PSBBL accordingly. Despite this, the image won't boot on my console.
I also used a FMCB memory card to boot uLaunchELF and confirmed the drive was readable and formatted properly, and from here I tried to launch the PSBBL/N .ELF directly, but got the same black screen/drive activity happens before it just hung at a black screen forever.
The first time I wrote the image, I used an Inland 512GB SSD. I ran into the issue and tried again without writing any games to the drive to test and ran into the same issue. From here assuming drive compatibility was an issue, I picked up a WD Blue 500GB SSD from Micro Center since they had no Kingston A400's. Using the same process of troubleshooting as the Inland drive, I had the same outcome on all attempts. At this point, I bit the bullet and assumed a second strike-out on drive compatibility and picked up the Kingston A400 drive. Wrote the image again, same problems.
At this point I was getting desperate and thought maybe it's the Arch version of the script that's having issues. I make a Linux Mint live image, boot into that, git clone the repo and run the scripts in order again, and still run into the same issue.
At no point have I received any errors during the drive write process in either Linux environment, the PS2 does seem to be able to see and read the drive successfully, and it most certainly attempts to boot some sort of .ELF on startup; but whatever it's trying to do is failing and I can't for the life of me figure out why.
I've done a lot of digging and can't find anyone else having the same issue. I don't have another working phat PS2 to test on, and I'd like to avoid buying another third party drive adapter to salvage the board from if I can help it after having gone through and bought two drives and returned one solely for this project now.
If anyone has any ideas on what's going on here or what I can even do anymore short of buying a new SATA adapter, I'd really appreciate any considerations people might have to help.
Thanks for reading!