Dealing with cdc_acm usb devices

[nswint]

How do I get linuxmce to deal with usb serial devices that register as  ttyACM0 and ttyACM0 instead of ttyUSBx?

[   49.480200] usbcore: registered new interface driver libusual
[   49.480363] usbcore: registered new interface driver usbserial
[   49.480387] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[   49.480446] usbcore: registered new interface driver usbserial_generic
[   49.480448] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   49.480686] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[   49.480700] cdc_acm 1-4.2:1.0: ttyACM0: USB ACM device
[   49.481949] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[   49.481962] cdc_acm 1-4.1.4:1.0: ttyACM1: USB ACM device
[   49.482867] usbcore: registered new interface driver cdc_acm
[   49.482870] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters

[   49.585660] usb 1-4.4: FTDI USB Serial Device converter now attached to ttyUS
B2

[nswint]

The resolution was to ditch the cheap usb serial adapters.  The belkin adapters restore normal functionality.

[hari]

they should work properly (Seluxit Dongle uses the same generic modem device).

br, Hari