Just got shiny new servers and shiny new Edgeports/416 yesterday. Installed Ubuntu Lucid (10.4 LTS) on the servers
Just plugging in the Edgeports manages to produce 4 of the 16 serial ports as /dev/ttyUSB0-3, which is a start. Unplugging and plugging back in makes all 16 appear. However, after a reboot, there are only 4 again. Since these are going to be installed remotely, without an easy way to unplug after a reboot, this is most annoying.
What are the 50xxxxxx part numbers and revisions of the Edgeport/416 units in question?
How are these Edgeport/416 units connected to the PC? Are they connected directly to the PC or going through a USB hub or some other kind of extender device? Are any of the Edgeport/416 units daisy chained through each other?
Do all 16 ports ever get produced, or does this same problem happen 100% of the time where only 4 ports get produced?
They’re connected directly into the PC (server), no hubs, no daisy chaining - we’ve got 2, one each for each server
I get varying numbers of ports… currently sitting at 10, however I have had all 16, but haven’t consistently managed to get them all
I get firmware upload errors when ports fail - I can post detailed logs if it would be useful. But I’ve tried various different versions of down3.bin to no avail
userid0: using ubuntu kernels - I tried the latest one from Maverick to see if it made any difference (which is what I did the tests with), but I get the same behaviour with the latest Lucid kernel (2.6.32, IIRC).
I’ve downloaded the firmware, removed power and usb and rebooted, but still the same behaviour. Did manage to get 6 ports recognised at one point, but then, I have got that before.
I’ve also tried daisy chaining them via the onboard usb hub, and, I don’t know if this provides any clues but, none of them worked to start with. Then unplugged/plugged at the computer end, and 8 started working. had to unplug/plug at the hub side to get all 16 working.
This is all running off a couple of Dell R200 servers, if that’s important:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 107: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 106: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 105: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 104: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 101: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 100: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 099: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 098: ID 1608:0247 Inside Out Networks [hex]
Bus 003 Device 097: ID 1608:02c7 Inside Out Networks [hex]
Bus 003 Device 096: ID 1608:02c7 Inside Out Networks [hex]
Bus 003 Device 094: ID 1608:0184 Inside Out Networks [hex]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 “TetraHub”
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Just tried it on another random Linux machine here in the office - completely different hardware (AMD processor, nNvidia chipset) and got exactly the same behaviour. Also tried putting a cheap USB hub in between too.
Just for a bit of variety, tried Fedora which also doesn’t work, kernel version 2.6.33.3-85.fc13.x86_64 - not an ubuntu specific problem by the looks of things
The bug which the patch applies to has been fixed in the current kernel tree - I hit that on one of my Ubuntu installs - it was I think 9.10 - the CD install kernel didn’t load the edgeport driver at all and stopped with a Null pointer deference as per: