why does it take SO LONG to detect USB dongle?
Hi all,
I'm running ubuntu 10.04 Lucid Lynx netbook edition. Kernel 2.6.32-generic.
Dongle = zte 2736c.
I've got internet working and everything. Only problem is when plug in the dongle, it takes a FULL FIVE (5) MINUTES for it to finally be ready for use!!! FIVE MINUTES!
Can anyone help debug why the delay? i've got the latest usb-modeswitch 1.1.4. modeswitch-data as well. someone suggested doing rmmod usb_storage to remove the storage mode driver to speed up recognition, but that is not helping it.
under /dev/ files for usbtty0-4 are set up rather quickly upon inserting the dongle. so why the delay in dialer recognizing it?
I'm running ubuntu 10.04 Lucid Lynx netbook edition. Kernel 2.6.32-generic.
Dongle = zte 2736c.
I've got internet working and everything. Only problem is when plug in the dongle, it takes a FULL FIVE (5) MINUTES for it to finally be ready for use!!! FIVE MINUTES!
Can anyone help debug why the delay? i've got the latest usb-modeswitch 1.1.4. modeswitch-data as well. someone suggested doing rmmod usb_storage to remove the storage mode driver to speed up recognition, but that is not helping it.
under /dev/ files for usbtty0-4 are set up rather quickly upon inserting the dongle. so why the delay in dialer recognizing it?
You know, windoze actually fires it within seconds.Josh wrote:This is obviously a problem of Gnome's NetworkManager and modem-manager. USB_ModeSwitch can't do anything else apart from providing the ttyUSB ports.
You might try using other dialers, as suggested on the main doc page, paragraph "How to use".
But this brings up interesting point. I read your "other dialers" bit. THank you (clearest explanation yet for shortcomings of NM).
BUT: WHY O WHY does the dongle create FIVE (5!) ttyUSB "dev"-ices under /dev/ ??????
regards.
Well, ask the manufacturer about that.
Usually, only one port is good for connection, the others may provide proprietary control and diagnostic interfaces only usable with the driver for Windoze. As long as manufacturers don't provide Linux drivers or at least documentation about the protocols used, this situation will persist.
Usually, only one port is good for connection, the others may provide proprietary control and diagnostic interfaces only usable with the driver for Windoze. As long as manufacturers don't provide Linux drivers or at least documentation about the protocols used, this situation will persist.
indeed.....i have found (by sending online, live AT modem commands from terminal to each "ttyUSB") that ttyUSB0 is "the one" that responds quickly as a modem. sending standard AT commands to other ttyUSBs only results in terminal prompt "not coming back" forever ie. perhaps like the dreaded delay i encounter when first plugging in the dongle!?Josh wrote:Well, ask the manufacturer about that.
Usually, only one port is good for connection, the others may provide proprietary control and diagnostic interfaces only usable with the driver for Windoze. As long as manufacturers don't provide Linux drivers or at least documentation about the protocols used, this situation will persist.
My manufacturer is in China, mate. U speak mandarin? I already half worry if there aint some hidden keylogger inside this stoopid zerocd "feature" from Qualcomm!!
any help scripting around this or somehting similar would be appreciated. I'm no Linux guru, but CAN follow instruction.
thx.
well.....GUARANTEE it man!
Josh,
what a tip! it worked a charm. i wouldn't have known to look for "ModemManager". I thought it was "NetworkManager" gumming things up.
THANKS mate. windoze RIP.
PS. is there any good reference bible (not for beginners but intermediate onward) on working with these types of Ubuntu OS features that you could reco?
what a tip! it worked a charm. i wouldn't have known to look for "ModemManager". I thought it was "NetworkManager" gumming things up.
THANKS mate. windoze RIP.
PS. is there any good reference bible (not for beginners but intermediate onward) on working with these types of Ubuntu OS features that you could reco?