ps2client does not echo printf from PS2 anymore

[cosmito]

Hi,

Suddenly, I've just got this problem. My faithful ps2client build under cygwin is not gettting output from PS2 printf's anymore. I've checked it and is the same executable I've been using (its date is from 2007) so it's not the result of any recent build I did recently...

I remember also one time after a fresh build of the toolchain (a more recent revision that I had that time) the built ps2client.exe also was showing this "muteness"...

What am I missing?

[SP193]

So you're saying that your PS2client CAN communicate with PS2link on your console, but won't display any messages that were to be displayed by printf()?

How are you launching your PS2client? Is it any different from the say you used to launch it when it still worked?

Somehow I've found that launching it directly from FMCB will cause it to have different results, compared to when it's launched by SwapMagic.

Your console was never changed *before* PS2CLIENT ceased functioning properly, right?

[cosmito]

So you're saying that your PS2client CAN communicate with PS2link on your console, but won't display any messages that were to be displayed by printf()?

That's right.

How are you launching your PS2client? Is it any different from the say you used to launch it when it still worked?

Nothing changed. I just type ps2client (followed by the arguments -h for host address, execee, etc) at a cygwin shell under Windows XP. This used to work until now. I haven't also installed any cygwin based application recently, as far I remember.

Somehow I've found that launching it directly from FMCB will cause it to have different results, compared to when it's launched by SwapMagic.

I think my problem is with ps2client running at the PC, not ps2link running at the PS2. I also tried other versions of ps2link that also never gave me any problems and the same happens.

Your console was never changed *before* PS2CLIENT ceased functioning properly, right?

I tried some weeks ago a ps2link I compiled. But I'm not using it anymore.
ps2link doesn't have any config setting that could justify this, right? My settings only defines the PS2 IP address and gateway and that's it. The extraparam setting is disabled, also.

[SP193]

I tried some weeks ago a ps2link I compiled. But I'm not using it anymore.
ps2link doesn't have any config setting that could justify this, right? My settings only defines the PS2 IP address and gateway and that's it. The extraparam setting is disabled, also.

You're correct, unless your copy was compiled with "extraconfig" enabled (It's disabled by default).

You haven't mentioned this: How is your PS2 connected to your PC? Via a crossover-cable, via a switch, or through hub (or a more complicated network configuration)?

Could you please post your settings here (In your PS2's IPCONFIG.dat file, and your PC's IP address configuration)?

Nothing changed. I just type ps2client (followed by the arguments -h for host address, execee, etc) at a cygwin shell under Windows XP. This used to work until now. I haven't also installed any cygwin based application recently, as far I remember.

Wait... but does your homebrew/whatever program you're working on load it's own network TTY drivers if it resets the IOP (And initilizing the SIF RPC)?

The PS2 doesn't channel printf() messages to anywhere by default.

Have you tried running ps2client without the "-h" parameter? Or used the broadcast address "255.255.255.255" as the option for the "-h" parameter instead?

If you have a firewall, then it's best to disable it first.

[cosmito]

You're correct, unless your copy was compiled with "extraconfig" enabled (It's disabled by default).

You haven't mentioned this: How is your PS2 connected to your PC? Via a crossover-cable, via a switch, or through hub (or a more complicated network configuration)?

Could you please post your settings here (In your PS2's IPCONFIG.dat file, and your PC's IP address configuration)?

The PS2 connects to a Thomson TG784 (router? it is described as a triple-play Service Gateway) by a regular network cable, just like the PC. The IP gets the IP 192.168.1.60 specified by ps2link and the PC get a 192.168.1.70. The router gateway is located at 192.168.1.254.

The contents of IPCONFIG.dat are:

192.168.1.60 255.255.255.0 192.168.1.254
# EXTRACNF = mc0:extracnf

Wait... but does your homebrew/whatever program you're working on load it's own network TTY drivers if it resets the IOP (And initilizing the SIF RPC)?

The PS2 doesn't channel printf() messages to anywhere by default.

Are you sure? ps2ip.irx and ps2smap.irx are loaded by ps2link. For example, if you run a sample from the ps2sdk (debug/callstacktest) I remember it to give back to the PC some printf output... And it doesn't load any irx nor resets the IOP.

Have you tried running ps2client without the "-h" parameter? Or used the broadcast address "255.255.255.255" as the option for the "-h" parameter instead?

I do need to specify the PS2 IP address or to compile the sources targeting my 192.168.1.60. The default 192.168.0. 10 falls outside my router IP range. My router is a bit complicated to use and besides I should not be configuring it since it's part of my TV/Net provider. it assumes some IP for the set top boxes and last time I tried to change the IP ranges, I lost connectivity with those.

If you have a firewall, then it's best to disable it first

I disabled it now for a test and the same happens. I enabled it again.

I tried the 255.255.255.255 broadcast setting you mentioned. I also tried XLink, the GUI app for windows and although it sends ELF and files are read from host: device, I still get no printf output from the PS2...

[dlanor]

@cosmito:
I guess you have not restarted your computer recently, nor checked the process list in the task manager...

What you describe is typical for what happens when a ps2client instance is launched while another HOST protocol program is already hooked up to PS2Link.

The new instance has then no problems sending its commands to PS2Link on the console, but all replies that are sent back are 'eaten' by the older HOST client on the PC. (older launch-wise I mean)

This frequently happens to me When I've been using PS2ClientLoader to work with HOST in the uLE FileBrowser, and then a bit later I decide to test something in PS2Link without remembering to terminate PS2ClientLoader and/or the ps2client instance it opens.

But it can sometimes happen with simple uses of ps2client.exe itself, that a previous instance of it has failed to terminate properly, and then keeps 'eating' the feedback strings sent by PS2Link in response to commands of a newer ps2client instance.


Check the process list of the task manager, to see if there is more than one instance of ps2client.exe, or some other HOST client you have used (such as RadHostClient etc)

Best regards: dlanor

[SP193]

Are you sure? ps2ip.irx and ps2smap.irx are loaded by ps2link. For example, if you run a sample from the ps2sdk (debug/callstacktest) I remember it to give back to the PC some printf output... And it doesn't load any irx nor resets the IOP.

You're right about PS2LINK loading the necessary modules for printf() redirection, but I was talking about the PS2's regular behavior (Before any software attempts to redirect printf() outputs).

True... but it doesn't initialize the RPC. printf()s are channeled over the SIF RPC, to the IOP, and through the Network Adaptor to the PC.

If the RPC isn't initilized (With a call to SifInitRpc(0)), printf() messages may not go through (Although it somehow usually does).

I do need to specify the PS2 IP address or to compile the sources targeting my 192.168.1.60. The default 192.168.0. 10 falls outside my router IP range. My router is a bit complicated to use and besides I should not be configuring it since it's part of my TV/Net provider. it assumes some IP for the set top boxes and last time I tried to change the IP ranges, I lost connectivity with those.

It's the same for me (Default IP address out of range).

I forgot to ask: Is your current build of PS2LINK the "high-loading" type (Somewhere around 0x01700000+), or the "normal" kind that loads itself into low user memory (Somewhere around 0x000A0000)?

Your homebrew software may not launch if overwrites PS2LINK (Before PS2LINK completes loading it).

Somehow, your problem seems like a case of blocked/chewed-up (Or lost) packets.

If you can, you should try a cross-over cable.
This is to test whether there are problems with your PC or PS2's configurations (If there are no problems, then it might be your router).

[cosmito]

@cosmito:
I guess you have not restarted your computer recently, nor checked the process list in the task manager...

What you describe is typical for what happens when a ps2client instance is launched while another HOST protocol program is already hooked up to PS2Link

Bingo
Actually, no ps2client process is on the TM list, but one of the several svhosts processes might belong to a dead ps2client.

Still, I have the oddity to get the same problem when running a virtual machine on vmware player with a recent toolchain. This happens for both linux and windows virtual machines. Also, the syslinux virtual machine for compiling OPL featured on the forums also behaves the same way and this time it's running on virtualbox...

[cosmito]

I forgot to ask: Is your current build of PS2LINK the "high-loading" type (Somewhere around 0x01700000+), or the "normal" kind that loads itself into low user memory (Somewhere around 0x000A0000)?

Yes, it's the high-loading version.

Your homebrew software may not launch if overwrites PS2LINK (Before PS2LINK completes loading it).

Yes that may happen but in this case, it's not the case. The homebrew I'm running gave no problems previously giving always the nice printf output.

Somehow, your problem seems like a case of blocked/chewed-up (Or lost) packets.

Yep, dlanor pointed me to the solution. It should have been a zombie ps2client that were eating the PS2 outgoing packets. Delicious packets for zombies

Still, I have the odd behaviour when running the ps2client at virtual machines... The same happens (and this time I rebooted my (real) PC and started the vmachine).

[dlanor]

Still, I have the odd behaviour when running the ps2client at virtual machines... The same happens (and this time I rebooted my (real) PC and started the vmachine).

I have never used virtual machines of any kind for running ps2client, but I suspect that it is the software linking the virtual network interface of the virtual machine to the physical LAN that somehow fails to cope with the custom protocols used between ps2client and PS2Link.

Is there any strong reason why the ps2client session needs to reside in the virtual machine ?

Best regards: dlanor