I think there's a third "debug" parameter for the usbserial module from
looking at the output of "modinfo usbserial".
Try modprobing it with debug=1 to get some logging going.
Other than that, I'm not much help. Although, it sounds like the
usbserial generic driver is having trouble allocating ttyUSB0.
Erik de Castro Lopo wrote:
Hi all,
I've got two devices that connect via USB and set up /dev/ttyUSB*
devices:
- Sierra Wireless Aircard 875
- Custom hardware widget
The custom hardware widget gets automatically detected by udev and
the usbserial and cypress_m8 drivers get loaded and a single
/dev/ttyUSB0 gets created.
To get the Sierra card going I need to do:
modprobe usbserial vendor=0x1199 product=0x6820
which creates /dev/ttyUSB0, ttyUSB1 and ttyUSB2.
These two devices work correctly on their own, but if I have
both plugged in when the machine starts, the Sierra card's
modprobe command does nothing; no ttyUSB devices are created
and there is no dmesg output and nothing in /var/log/messages.
However, if I leave the custom widget unplugged when I reboot,
modprobe the Sierra card, then plug in the widget all works
fine. Unfortunately, this not really a satisfactory solution.
Anybody have any ideas on how to sort this out?
Cheers,
Erik
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
