The Max & Parris faulty PS2 Tool tread

This is generally where in a discussion I would bow out and let UJ, Port and many other Linux fiends explain their software wizardry!

However, as this happened during transit what is the chances of the main BOOT HDD having taken a knock?

I only ask, because prior to transit -usr was NOT read only?

<With that naive line of questioning, I now retire until / IF it comes back to hardware>

 

ok, /usr is rw now.

tried:
./dsedb S> reset 2 100

Linux returns nothing and nothing happens on the TV screen.

 

On my TV monitor I got a definate difference in using PAL / NTSC as my old Sony TV only output in PAL and the Network Information screen changed from the coloured Network Information screen to Black & White. Whilst in GAME however, when you loaded retail titles it was the same as my PS2 Test and immediately output in colour, so presumably the native output of the title (i.e. I was using PAL discs).

 

Please ignore the HDDs, I use new HDDs with your image

 

Okay - so scrub that then!

 

Weird that this caused dsedb/linux to not return the error you had last time, while the default settings are that usr is readonly..
Anyway do you get anything after running reset 2 100?

Something like:

dsedb R> reset 2 100
EE DECI2 Manager version 0.06 Oct 31 2003 19:02:01
CPUID=2e14, BoardID=4126, ROMGEN=2003-1031, 128M

And so on..

 

no, I get nothing

 

Just do me a favor, hit the big reset button on the inside, see what happens, it "may" have fixed mine.

 

Also, whilst you are at it, do me the favour of making sure the HDD you dumped the main HDD 1 image onto is DEFINATELY on the BOOT IDE and not the second IDE that terminates under the PSU.

Not the sort of thing I would expect you to have done, but for the settings to have changed it would be the first thing I would check had I been the person presented with this issue :redface:

I know you can boot into Linux with HDD 2 attached as the BOOT HDD, but I never tried the PS2 side.

Try everything once! Including things you think are SO obvious you'd never have been silly enough to have done it!

 

I'm unsure which reset button you mean. There are 2 reset buttons on the PCI board and another one on top of the TOOL.

btw, I changed the PSU, but again that was wasn't the issue.

 

so what does it mean? Are ee and gs processors just deactivated by a simple jumper setting or are both processors broken?

 

I beleive the one on the mainboard, think the PCI part of it, was it, if that dont work, try the other etc!

 

Sorry, but I'm not sure what you mean. Which 'other' should I try?

 

No sorry, I misread the thing, the ee is in normal mode, I should have been sleeping...
I'm going to test all those switch anyway, once I find them...

 

The reset button, my memory is terrible, but iirc there is more than one reset button. Hit one, if it doesnt work (reboot retry etc), try the other reset button(s).

 

I pushed all the reset buttons. Every button seem to work fine because the MultiAV out screen turned black for a few seconds.

But the problem is still not solved:-(

Anyone an idea what I could do next?

 

Maybe...I'll post details later.

 

I am just hoping you have found a solution. Fingers crossed! OH:

 

Parris, what is the latest thing you did with the Tool before unplug it and pack it up?
I've found some messages about the test pattern in the newsgroup logs, I just have to clear them a bit (removing names and emails) before posting.

 

The very last thing I did with the unit was test it with a game. Then I switched it off, removed the base and packaged it up. Nothing unusual, nothing untoward. I certainly didn't try to delete or reset anything.