Ethernet doesnt turn on

Printable View

12-28-2012, 09:40 AM
bekax5

Ethernet doesnt turn on

Hello all !!

Actualy this is my first post but i come here directly because i am afraid my PS2 Eth. adapter has burn or something.

Two days ago I was trying to revive the PS2 and install OPL.
The thing is, everything runs smoothly, freemcboot, sms, uLE, but somethings wrong with the adapter!

I have set the Settings right, (IP: 192.168.1.20 | Sub: 255.255.255.0 | Gateway: 192.168.1.1)
Router is at 192.168.1.1 obviously.

But the thing is, No activity is registered on the Switch when i try the PS2Net or Host:\ options!
Not even turn the light on in the Switch PS2 port!

Is there anyway to reset the adapter or how can i debug this thing??
12-28-2012, 10:35 AM
SP193

Quote:

Originally Posted by bekax5

Hello all !!

Actualy this is my first post but i come here directly because i am afraid my PS2 Eth. adapter has burn or something.

Two days ago I was trying to revive the PS2 and install OPL.
The thing is, everything runs smoothly, freemcboot, sms, uLE, but somethings wrong with the adapter!

I have set the Settings right, (IP: 192.168.1.20 | Sub: 255.255.255.0 | Gateway: 192.168.1.1)
Router is at 192.168.1.1 obviously.

But the thing is, No activity is registered on the Switch when i try the PS2Net or Host:\ options!
Not even turn the light on in the Switch PS2 port!

Is there anyway to reset the adapter or how can i debug this thing??

What software were you running when you realized that it's not connected to the switch (No valid link)? The Playstation 2 does not have Ethernet support out of the box.

The SMAP (Ethernet) interface only gets initialized when the running program loads the respective drivers. So if you were testing with OPL, I think that you need to start it's Ethernet mode first.

If you are really sure that there should be a valid Link state between your switch and your Playstation 2 console when there really isn't, you may want to check out my new SMAP driver testing program: http://psx-scene.com/forums/f19/new-...totype-108709/

There is actually a problem with the current homebrew driver's ability to auto-negotiate with certain network devices, so it's not an unheard of problem anyway.
12-28-2012, 02:57 PM
bekax5

I tried with OPL, and uLE (Host: and PS2Net)...
I am not sure, but as PS2Net tries to create a FTP Server and connect to the gateway, i guess it should at lease show some activity in the Switch ?

So, that means the best option is to Set is Manualy to 100Mb Full/Duplex ?
All my devices at home are branded DLink at 1Gbit..
12-28-2012, 03:17 PM
bekax5

Oh, and right now i tried to start via OPL, and it gave me a Network Error : 203
12-28-2012, 08:34 PM
SP193

Quote:

Originally Posted by bekax5

I tried with OPL, and uLE (Host: and PS2Net)...
I am not sure, but as PS2Net tries to create a FTP Server and connect to the gateway, i guess it should at lease show some activity in the Switch ?

So, that means the best option is to Set is Manualy to 100Mb Full/Duplex ?
All my devices at home are branded DLink at 1Gbit..

Uh, no. If it can't acquire a valid speed and duplex setting through auto-negotiation because its auto-negotiation doesn't work, it doesn't seem to work right after that. :S
(And since there isn't a valid link state, no network activity is possible anyway).

It should fall back to 100Mbit half duplex and 10Mbit half duplex upon auto-negotiation failure, but it doesn't seem to work most of the time. And the timeout for auto-negotiation is hideously long anyway.

My D-Link DIR-655 router causes auto-negotiation to fail on my SCPH-10000 console (SCPH-10190 network adaptor), although it seems to work right on my SCPH-39006 (SCPH-10281 network adaptor) and SCPH-77006.

When it tries to auto-negotiate (and fails to), the LINK and ACT LEDs on the SCPH-10190 keep going on and off, while the LINK LED on the DIR-655 remains off.

It doesn't hurt for you to try setting the link speed settings to 100Mbit Full Duplex...

Quote:

Originally Posted by bekax5

Oh, and right now i tried to start via OPL, and it gave me a Network Error : 203

From here: http://psx-scene.com/forums/f150/i-n...rsions-105147/
And here: http://psx-scene.com/forums/f150/net...-203-a-105693/

It seems like the SMAP driver can't load. Try reconnecting your Network adaptor. If that doesn't work, you may want to either test the network adaptor on a different console or get another network adaptor to test on your console.
12-28-2012, 09:16 PM
bekax5

I read the links you gave me...

I think the second relates a little more to my problem than the first one.
I am not really sure about how i should proceed to "reset" the network adapter.

I am now going to connect the PS2 alone and then connect the adapter and try again.

For info, I am using:
PS2: SCPH-30004R
Ethernet: SCPH-10350

Edit:
Still happening same error (OPL: network error 203)
Can you explain me how i update the SMAP driver to yours ? Could that solve my issue?
12-29-2012, 12:50 AM
SP193

Quote:

Originally Posted by bekax5

Still happening same error (OPL: network error 203)
Can you explain me how i update the SMAP driver to yours ? Could that solve my issue?

It's not too easy to replace the SMAP driver since I changed the way the driver and network protocol stacks work, to make it easier to maintain. Everything is still beta right now, so using it on an everyday basis... is not recommended.

What I intended to suggest you to do was to just try the IOP SMAP testing platform, to see whether you can access your PS2 with HDLDump/HDLDumb.

(Or if you don't have a HDD unit installed, a PING test while the SMAP testing platform is loaded will surffice)

I won't say that it'll surely solve your problem (Since we do not know for sure what it is right now), but it may solve your problem if it's a problem with auto-negotiation.

EDIT: Error 203 may also be caused by a faulty adaptor or DEV9 expansion interface... so it's best if you can prove that the adaptor is working. I heard that bent/broken pins on the adaptor is a common culprit.