forums.ps2dev.org

[J.F.]

I was using NapLink in Windows, but recently switched to Fedora Core 2 (Linux). Both NapLink and npsh seem to be waiting for a peer (NapLink says this, npsh just sits at the point where it looks for a peer). Any suggestions?

The PS2 side reports the cable and PC to be ready. It seems that the Linux USB is having some trouble trying to send or receive packets.

[pixel]

hasn't pksh a support for naplink ?
_________________
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.

[J.F.]

Yes, that is npsh. As I mentioned above, it doesn't work either, which isn't surprising as it uses the NapLink Linux code for it's base.

[pixel]

True. Actually, I never tried naplink. Can' t help you any further. You should try to debug the PC-side code of naplink somehow. Maybe you simply need to run it as root or something. No better clue, sorry; you have to wait for a better one from somebody else.
_________________
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.

[J.F.]

Looking at the code, the PC is looping around fetching the quick link feature register, waiting for the peer exists bit to become set. It's nothing to do with packets apparently. When I unplug the cable from the PS2, the status goes to Cable: not ready PC: not ready. If I unplug from the PC, it goes to Cable: ready PC: not ready. Running NapLink then changes that to PC: ready. On the PC side, it just sits waiting on that peer exists bit. Swapping the cable ends made no difference to anything (not that I expected it to, just trying to be thorough). I'll try skipping the check for peer exists on the PC side and see what happens.

[blackdroid]

could you try to run npsh first, then boot naplink on the ps2. cable attached and everything.

if this doesnt work, and the kernel do recognize the usblink cable, im not sure what is going on.

out of curiosity, what libusb version did you link npsh with ?
_________________
Kung VU

[J.F.]

[J.F.]

By the way, I have hooked my PS2 up to my enthernet hub, but I'm not sure how to set up the Linux side to allow pksh to work. Any docs somewhere on setting up the Linux side for networking with the PS2? I made a PS2Link disk that I can boot. It says it's setup as 192.168.0.10 and ready to go. It is connected to the hub according to the hub status lights. I have pksh compiled, I just need to get my eth1 setup to communicate to the hub and the PS2. eth0 is already running my cable modem. Any help appreciated.

[mrbrown]

That's easy. Give eth1 an address on the 192.168.0.x network and you're good to go. Your OS docs should explain how to assign an IP address to an interface. Here's example values you could use:

IP: 192.68.0.11
Network: 192.168.0.0
Broadcast: 192.168.0.255
Subnet mask: 255.255.255.0

Typical commands to initialize a network interface to a given address are "ifconfig eth1 ip <ip> ... up" (see it's manpage). But that's usually distribution dependent.

Now, if you want to get the PS2 to be able to access the Internet, you're going to have to setup NAT/IP Masquerading. There's a ton of good FAQs on it (start at linuxdoc.org).

[J.F.]

Yeah, I figured that out and got ps2client working. I'll set it up to access the net later. This is fine for now. Weird about the NapLink though...

Thanks for all the help!

[blackdroid]

im sure my and wiRe's code differs, nonetheless it does work as long as the kernel and libusb plays nice. ive used libusb 0.1.7 and 0.1.8 here and it worked.
_________________
Kung VU

[dnc]