Ok, we definitely have that driver included in our kernel config (since a long time). So I was wondering if other people had issues with Linux on this device. But seems like people are happily installing Linux on it despite some video card issues - see here. But no one complaining about network issues.
So I went hunting for those USB messages and read about USB hubs or other faulty USB hardware here and there, e.g.:
It seems the hub in the monitor went bad and was screwing with all other USB ports on the system
Maybe just some faulty hardware? Have you tried different ones. Always getting the exact same error on every try?
Then again I ask you for the third time (and last!), have you tried adding the Kernel Parameter has_usb_nic=1 to the host settings?? If this device is still unregistered and the error happens on registration you might just add the host manually via the web UI, add the parameter and try a capture task to see if that helps.
Just as an FYI, the bzImage and bzImage32 are the kenrels, the inits are (roughly) the virtual hard drives for the FOS (client) image. In your case you need to use the inits for 1.2.0 and then the newer kernels (bzImage). Tom is saying this should work, but the best chance is to just upgrade to the trunk if just copying the bzImages doesn’t work for you.
As you get more clients that will get worse, especially when you get clients that are not active. I suggest you look into disabling the PING unless you have a reason to have it active. (Can’t remember how to do that right now, but I am pretty sure it is something you have to dig into the config files to change). When we were at about 250 clients it got too time consuming. Now that we are at 700+ I can not imagine what it would be like.
I guess my suggestion would be to have a simple on/off on the ping.