Arduino and another FT232 device randomly don't appear after boot OpenSUSE 10.3

Development Tools IDE 1.x
1

I posted this hear in case any linux Arduino users had experienced this problem.

I have a embedded computer running OpenSUSE 10.3 (stuck with that version) that has USB device issues.

In reality, it has two USB devices attached, both FTDI FT232 USB to Serial Uart driven hardware, one is an arduino. Both usually are at /dev/ttyUSB0 and 1 when everything goes right. The latest FTDI driver is already in the kernel.

Randomly however, when it boots one or both will be missing in dev.

If we only leave one physically attached before booting, sometimes it comes up ok, the other times there's no listing in /dev/ or lsusb. But when we do run lsusb once and watch the system log, suddenly the device is found and 'attached'. Then it works fine.

I've repeated this with another test USB device (and old cell phone that gets installed as a ceullar modem) and the same thing can happen. It will randomly be missing from lsusb listing till lsusb is run once. IE, run it once, no listing, run it again, then it shows up and the system log saya it was just attached.

If we leave both, sometimes one device (Call this one A) is ready to go, but device B is missing. If we unplug B, A dissapears from /dev/ and the system log says A was unpluged. The when we reattach B, both show up in /dev/ and the system log reports two USB devices were attached. running lsusb doesn't fix one or both missing when they are both physically attached.

This is an embedded system and we need both to be discovered at boot 100% of the time. Any ideas what might be going on?

2

Oops, I do mean version 11.3

3

Does running 'udevadm trigger' help ?

4

I only know enough linux to be dangerous, another team member is good at linux but hadn't heard of the command. I googled it quickly and it looks pretty useful in this regard so we are going to give it a try.

Any suggestions for what we should be lookign for?

5

Well, either the device shows up or it doesn't.

The 'trigger' should make the udev daemon re-evaluate what devices are connected and make them usable if that's not already the case.

6

Ok, thanks.

We gave it a try when the computer booted up and saw the arduino but not the other FTDI device. It did not fix the problem: :confused:

7

Please post /var/log/boot.msg and the end of (all the lines with the current date) /var/log/messages. Make sure to remove anything that is personal (IP addresses, system name...).