HI Aydan What i found is that a module was loading for the usb-to-serial (pl2303) that affected the 3G modems module (usbserial). I unloaded the usb-to-serials module and loaded the 3g'd module and hey presto the 3g modem worked. I then loaded the usb-to-serials modem and all was right again. I foun...

HI Aydan I thought so too. I have run this before and it always comes back "Nothing to do" /usr/sbin/usb_modeswitch -V 0x2001 -P 0x7600 -v 0x2001 -p 0x7600 -u 2 root@blunap:/home/pi# /usr/sbin/usb_modeswitch -V 0x2001 -P 0x7600 -v 0x2001 -p 0x7600 -u 2 Looking for target devices ... found matching p...

Hi Aydan Herewith as requested. Both devices plugged in at boot. dmesg | grep usb root@blunap:/home/pi# dmesg | grep usb [ 0.820419] usbcore: registered new interface driver usbfs [ 0.826031] usbcore: registered new interface driver hub [ 0.831518] usbcore: registered new device driver usb [ 1.23386...

If you leave both devices plugged in and reboot only the serial-to-usb is added to the system. If you want everything to work you have to boot with the modem then manually plug in the serial-to-usb after boot. Any idea what's the issue?

Hi Ayden Thanks for the reply. I also thought that the usb-to-serial adapter was being matched by the dlink script but i could not see how as the Dlink script has both vendor and device ids to match. Please see the outputs as requested: dmesg -c after plugging in the usb-to-serial root@blunap:/home/...

Been struggling with this for 2 days and cant seem to get around it. I have 2 devices 1) Dlink DWM-157 3g modem and 2) Trendnet TU-S9 usb to serial. The dlink modem came with a udev script which works fine when the usb-to-serial is NOT plugged in from boot. So if the modem is on its own from boot, i...