Re: modem probing takes too long



It exposes 3 ports:
here's a syslog from MM:

Sep 24 21:18:38 walmis-laptop modem-manager: (ttyUSB1) opening serial
device...
Sep 24 21:18:43 walmis-laptop kernel: [22845.632132] usb-storage: device
scan complete
Sep 24 21:18:43 walmis-laptop kernel: [22845.632837] scsi 5:0:0:0:
Direct-Access     ZTE      MMC Storage      2.31 PQ: 0 ANSI: 2
Sep 24 21:18:43 walmis-laptop kernel: [22845.656582] sd 5:0:0:0:
Attached scsi generic sg2 type 0
Sep 24 21:18:43 walmis-laptop kernel: [22845.664841] sd 5:0:0:0: [sdb]
Attached SCSI removable disk
Sep 24 21:18:48 walmis-laptop modem-manager: (ttyUSB1): probe requested
by plugin 'ZTE'
Sep 24 21:18:53 walmis-laptop modem-manager: (ttyUSB0) opening serial
device...
Sep 24 21:19:03 walmis-laptop modem-manager: (ttyUSB0): probe requested
by plugin 'ZTE'
Sep 24 21:19:18 walmis-laptop modem-manager: (ttyUSB2) opening serial
device...
Sep 24 21:19:18 walmis-laptop modem-manager: (ttyUSB2): probe requested
by plugin 'ZTE'
Sep 24 21:19:20 walmis-laptop modem-manager: (ttyUSB1) closing serial
device...
Sep 24 21:19:25 walmis-laptop modem-manager: (ZTE): GSM
modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1 claimed port ttyUSB1
Sep 24 21:19:25 walmis-laptop modem-manager: Added
modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1
Sep 24 21:19:25 walmis-laptop modem-manager: (ttyUSB2) closing serial
device...
Sep 24 21:19:25 walmis-laptop modem-manager: Exported
modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1
as /org/freedesktop/ModemManager/Modems/0
Sep 24 21:19:25 walmis-laptop modem-manager: (ZTE): GSM
modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1 claimed port ttyUSB2
Sep 24 21:19:26 walmis-laptop NetworkManager: <info>  (ttyUSB2): new GSM
device (driver: 'option1') 
Sep 24 21:19:26 walmis-laptop NetworkManager: <info>  (ttyUSB2):
exported as /org/freedesktop/NetworkManager/Devices/2 
Sep 24 21:19:26 walmis-laptop NetworkManager: <info>  (ttyUSB2): now
managed 
Sep 24 21:19:26 walmis-laptop NetworkManager: <info>  (ttyUSB2): device
state change: 1 -> 2 (reason 2) 
Sep 24 21:19:26 walmis-laptop NetworkManager: <info>  (ttyUSB2):
deactivating device (reason: 2). 
Sep 24 21:19:26 walmis-laptop NetworkManager: flush_routes: assertion
`iface_idx >= 0' failed
Sep 24 21:19:26 walmis-laptop NetworkManager: flush_addresses: assertion
`iface_idx >= 0' failed
Sep 24 21:19:26 walmis-laptop NetworkManager: <info>  (ttyUSB2): device
state change: 2 -> 3 (reason 0) 
Sep 24 21:19:33 walmis-laptop modem-manager: (ttyUSB0) closing serial
device...

notice the amount of time ttyUSB1 takes to open.


On Tue, 2009-09-22 at 22:26 -0700, Dan Williams wrote:
> On Sun, 2009-09-13 at 10:17 +0300, Valmantas Palikša wrote:
> > I have ZTE MF633 and it has this "feature", opening or
> > closing /dev/ttyUSB1 blocks the program that is trying to open/close it
> > for about 5 seconds. This in turn slows down modem-manager's probing
> > speed. It takes about 60 seconds from plugging it in an entry appearing
> > in nm-applet's menu. I don't know whether this needs to be addressed in
> > kernel or MM, but it's quite annoying to wait for 1 minute for the modem
> > to be usable. Maybe probing ports in MM in parallel (threaded) makes
> > sense? Currently the PPP data ttyUSB port reports instantly, and I
> > imagine that a threaded solution would speed things considerably.
> 
> MM does probe the ports in parallel...  It might simply be that the
> modem firmware doesn't want to talk to more than one port at a time,
> which means we're out of luck.  How many tty ports does it expose?
> 
> Dan
> 
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]