pfranz wrote:Adding RaspberryPI3 solved the problem.
Mouse description is correct:"PCPlay...".
Excellent, that confirms that you have network functionality.
I'm mindful of expanding the troubleshooting in multiple directions at once because it gets very easy to lose track of the details of the conversation.
For the moment let's focus primarily on the mouse diagnostics and we can follow up further on any additional issues once that is mostly dealt with.
I will just add the following brief thoughts about the other items which might assist.
pfranz wrote:I enabled syslog, sent a test message with LoggingOutput which doesn't appear.
I'm making the assumption that you put this at the start of the example, you might need to allow a little bit of time for the network to initialize (a second or two) otherwise a syslog message can go missing or more correctly simply be discarded because there is no network available to deliver it.
pfranz wrote:I see messages that network is configured, and many "Failed interrupt interrupt request" from the 95xx driver.
The interrupt endpoint in the SMSC95XX device is used for ethernet management functionality like link up/down, negotiation complete etc so a failed interrupt request can result from a number of reasons.
The most interesting initial information would be your definition of "many", is that 3 to 5, 30 to 50, 300 to 500 or more? And what is the status value reported with the failure?
pfranz wrote:The net uses DHCP even though I set a static address in cmdline.txt.
Assuming that you put all of the configuration parameters on one line in the cmdline.txt file then could you post the file you used so we can see if there is anything unusual about it.
pfranz wrote:No mouse messages at all.
Looking at the experimental USBPS2Converter driver there is no code path in the HIDMouseReportWorker function that would not produce at least some message so one possibility is that the driver is failing on the first receipt (and possibly before logging is ready).
Could you try starting the Pi with the PS/2 to USB converter not plugged in, then wait several seconds for the network to be ready and logging messages started before plugging in the PS/2 to USB converter (with mouse attached) and recording the log messages that are generated.
I'm sure that we are only missing some very small detail to get this working for you, if you can supply as much detail as possible that will make it much quicker and easier to resolve.