I am looking for any information on updated Linux drivers for the Edgeport 416. For the past few years we have been functioning just fine by modifying the kernel to force the 416 to be seen as 8 two-port Serial to USB devices. Apparently the hardware has changed recently and the 416 is now functioning as 2 8-port devices. Although the 2.6.18-53 and 2.6.18-128 kernels both natively recognize the PID/VID…the device doesn’t work correctly. The Serial devices are added, but they do not function (even the USB hub lights stay on constantly).
Are there any updated Linux patches or any ideas to make this function under Linux (especially CentOS 5)?
The hardware has been verified to work correctly under Windows.
Please give me some sample 50xxxxxx part numbers (and revisions) of older Edgeport/416 hardware that has been “working” compared to the newer ones that are not “working”.
What exactly is the color and activity of the two System Status LEDs on older Edgeport/416 hardware compared to the newer ones? Specifically, what is the behavior in the following states:
When the Edgeport/416 is idle, i.e. when no software applications are interfacing with any of the serial ports / device nodes.
When the Edgeport/416 is in use, i.e. when a software application is interfacing with one or more serial ports / device nodes.
We have 4 that are of the “new style.” (or at least new to us) They were purchased in the last few months from CDW. We have almost 30 of the “old style” 416s that are happily running under Linux,
FYI, the units you are having trouble with are based on an older “930” chipset (specifically, an uncommon variant of that older chipset).
The units that have been working are based on the newer/current “TI” chipset.
The easiest way to resolve this is to get you the hardware that works for you and swap those 4 out. I’ve asked someone from our sales group to contact you about this, via e-mail. Also, they will let you know how to specifically order the TI-based units in the future from CDW, in the chance that you need to order more in the future, so you don’t run into this issue again.