Re: modem manager choose incorrect port for onda mt503hsa
- From: Alessandro Bono <alessandro bono gmail com>
- To: Dan Williams <dcbw redhat com>
- Cc: networkmanager-list gnome org
- Subject: Re: modem manager choose incorrect port for onda mt503hsa
- Date: Thu, 03 Dec 2009 19:34:09 +0100
On Wed, 2009-12-02 at 13:52 -0800, Dan Williams wrote:
> On Tue, 2009-12-01 at 09:58 +0100, Alessandro Bono wrote:
> > On Tue, 2009-12-01 at 00:26 -0800, Dan Williams wrote:
> > > On Mon, 2009-11-30 at 09:16 +0100, Alessandro Bono wrote:
> > > > On Sun, 2009-11-29 at 23:50 -0800, Dan Williams wrote:
> > > > > On Fri, 2009-11-27 at 11:56 +0100, Alessandro Bono wrote:
> > > > > > Hi all
> > > > > >
> > > > > > I have an onda mt503hsa that worked without problem with networkmanager
> > > > > > 0.7, after upgrade system to ubuntu karmic and networkmanager 0.8 +
> > > > > > modem-manager I have a problem with correct port selection
> > > > > > Modem manager sometimes choose incorrect port ttyUSB1 instead of ttyUSB2
> > > > > > to open ppp connection, this depends on which port is probed first
> > > > > > below a log with correct and incorrect port selection
> > > > >
> > > > > What is the 'lsusb' output when the modem is plugged in an modeswitched?
> > > > > We need to make sure the device is listed in 77-mm-zte-port-types.rules
> > > > > with the correct port. The port #s there were taken from the ZTE
> > > > > windows drivers, so if this is a newer device we may need to just add
> > > > > it.
> > > > Hi Dan
> > > >
> > > > lsusb -v log below
> > > >
> > > > Bus 002 Device 008: ID 19d2:0037 ONDA Communication S.p.A.
> > >
> > > That's the value I want :) I found the correct port tag for your device
> > > and pushed to modem-manager. Can you also do an experiment for me? I
> > > need to determine the aux port #. I want to find out which ports
> > > respond to AT commands. Most will, one or more won't.
> > >
> > > For each of the ones that *do* (use minicom or screen or whatever and
> > > send "ATI" to the port), please do the following:
> > >
> > > cd -P /sys/class/tty/ttyUSBx (where of course X is the tty number)
> > > pwd
> > >
> > > and the 'pwd' will print out something like this:
> > >
> > > /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.1/tty/ttyACM0
> > >
> > > which is what I'm interested in.
> >
> > port ttyUSB1 and ttyUSB2 respond to ATI
> >
> > /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5:1.1/ttyUSB1/tty/ttyUSB1
> > /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5:1.3/ttyUSB2/tty/ttyUSB2
>
> Thanks; 0.7.x and ModemManager have been updated for your device and a
> few others that I could find .INF files for. Can you give those a shot?
> In your case, grab this file and put it into /lib/udev/rules.d/:
>
> http://cgit.freedesktop.org/ModemManager/ModemManager/plain/plugins/77-mm-zte-port-types.rules
>
> Then unplug and replug the device and lets see where we get to.
Hi Dan
now MM recognize port correctly
Dec 3 19:22:08 champagne modem-manager: (ttyUSB3) opening serial device...
Dec 3 19:22:08 champagne modem-manager: (ttyUSB3): probe requested by plugin 'ZTE'
Dec 3 19:22:08 champagne modem-manager: (ttyUSB0) opening serial device...
Dec 3 19:22:18 champagne modem-manager: (ttyUSB0): probe requested by plugin 'ZTE'
Dec 3 19:22:23 champagne modem-manager: (ttyUSB1) opening serial device...
Dec 3 19:22:33 champagne modem-manager: (ttyUSB1): probe requested by plugin 'ZTE'
Dec 3 19:22:48 champagne modem-manager: (ttyUSB2) opening serial device...
Dec 3 19:22:48 champagne modem-manager: (ttyUSB2): probe requested by plugin 'ZTE'
Dec 3 19:22:50 champagne modem-manager: Got failure code 100: Unknown error
Dec 3 19:22:51 champagne modem-manager: Got failure code 100: Unknown error
Dec 3 19:22:52 champagne modem-manager: Got failure code 100: Unknown error
Dec 3 19:22:53 champagne modem-manager: Got failure code 100: Unknown error
Dec 3 19:22:54 champagne modem-manager: Got failure code 100: Unknown error
Dec 3 19:22:56 champagne modem-manager: Got failure code 100: Unknown error
Dec 3 19:22:57 champagne modem-manager: (ttyUSB1) closing serial device...
Dec 3 19:23:02 champagne modem-manager: (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3 claimed port ttyUSB1
Dec 3 19:23:02 champagne modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3
Dec 3 19:23:02 champagne modem-manager: (ttyUSB2) closing serial device...
Dec 3 19:23:02 champagne modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3 as /org/freedesktop/ModemManager/Modems/0
Dec 3 19:23:02 champagne modem-manager: (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3 claimed port ttyUSB2
Dec 3 19:23:03 champagne NetworkManager: <info> (ttyUSB2): new GSM device (driver: 'option1')
Dec 3 19:23:03 champagne NetworkManager: <info> (ttyUSB2): exported as /org/freedesktop/NetworkManager/Devices/2
Dec 3 19:23:03 champagne NetworkManager: <info> (ttyUSB2): now managed
Dec 3 19:23:03 champagne NetworkManager: <info> (ttyUSB2): device state change: 1 -> 2 (reason 2)
Dec 3 19:23:03 champagne NetworkManager: <info> (ttyUSB2): deactivating device (reason: 2).
Dec 3 19:23:03 champagne NetworkManager: <info> (ttyUSB2): device state change: 2 -> 3 (reason 0)
Dec 3 19:23:06 champagne modem-manager: (ttyUSB3) closing serial device...
Dec 3 19:23:07 champagne modem-manager: (ttyUSB0) closing serial device...
Many thanks for your support
>
> Dan
>
>
--
Cordiali Saluti
Alessandro Bono
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
