Re: Possible to force ttyUSB2 for Prolink PH-300?

[Dan Williams <dcbw redhat com>]

On Thu, 2011-05-26 at 12:41 +0800, Ascanio Alba wrote:
> I have a Prolink PH-300 dongle.
> 
> With usbserial.ko, NM/MM probe correctly and use /dev/ttyUSB2
> With option.ko, NM/MM probe incorrectly and use /devttyUSB1.
> The latter is pretty consistent, but once in a while NM/MM will use
> ttyUSB2 correctly.
> See below when it works.

Usually this is done by getting the Windows .INF files from the driver
for the device, which list which ports are which, and encoding that
information into udev rules files.  If you can get the .INF files from a
windows install that would help, otherwise we can try to hack them up.

> I can dial and connect with manually with pppd on ttyUSB2 so that is
> the data port.
> 
> Is there a way to "force" the generic(SimTech?) modem plugin to use
> ttyUSB2
> 
> 1. Prolink PH-300
> ZeroCD: USB id: 0x1e0e / 0xf000
> 
> 2. After eject /dev/sr0
> USB id 0x1e0e / 0x9100

Looks like we've got rules for 0x9200, but not 9100.  We need to know
what the USB interface number for ttyUSB1 and ttyUSB2 are though, can
you provide the output of this?

cd -P /sys/class/tty/ttyUSB1/device
pwd
cd -P /sys/class/tty/ttyUSB2/device
pwd

That will return something like
"/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.2/ttyUSB3" and the
number after the last "." is the USB interface #, in this case "2".
That's what we need.

Dan

> Thanks
> 
> ### Successful use of ttyUSB2
> Bus 001 Device 005: ID 1e0e:9100 Qualcomm / Option 
> 
> [90200.852190] usb 1-4: new high speed USB device using ehci_hcd and
> address 4
> [90200.969428] usb 1-4: New USB device found, idVendor=1e0e,
> idProduct=f000
> [90200.969438] usb 1-4: New USB device strings: Mfr=3, Product=2,
> SerialNumber=4
> [90200.969447] usb 1-4: Product: PROLINK 
> [90200.969452] usb 1-4: Manufacturer: PROLINK 
> [90200.969457] usb 1-4: SerialNumber: 1234567890ABCDEF
> [90201.910909] usb 1-4: USB disconnect, address 4
> [90202.224048] usb 1-4: new high speed USB device using ehci_hcd and
> address 5
> [90202.346567] usb 1-4: New USB device found, idVendor=1e0e,
> idProduct=9100
> [90202.346577] usb 1-4: New USB device strings: Mfr=2, Product=1,
> SerialNumber=3
> [90202.346585] usb 1-4: Manufacturer: PROLINK 
> [90202.346590] usb 1-4: SerialNumber: 1234567890ABCDEF
> 
> May 26 12:33:48 tristan kernel: [90366.398155] option 1-4:1.0: GSM
> modem (1-port) converter detected
> May 26 12:33:48 tristan kernel: [90366.405124] usb 1-4: GSM modem
> (1-port) converter now attached to ttyUSB0
> May 26 12:33:48 tristan kernel: [90366.405208] option 1-4:1.1: GSM
> modem (1-port) converter detected
> May 26 12:33:48 tristan kernel: [90366.405424] usb 1-4: GSM modem
> (1-port) converter now attached to ttyUSB1
> May 26 12:33:48 tristan kernel: [90366.405504] option 1-4:1.3: GSM
> modem (1-port) converter detected
> May 26 12:33:48 tristan kernel: [90366.405724] usb 1-4: GSM modem
> (1-port) converter now attached to ttyUSB2
> May 26 12:33:48 tristan modem-manager[1063]: <info>  (ttyUSB1) opening
> serial port...
> May 26 12:34:08 tristan modem-manager[1063]: <info>  (ttyUSB0) opening
> serial port...
> May 26 12:34:28 tristan modem-manager[1063]: <info>  (ttyUSB2) opening
> serial port...
> May 26 12:34:39 tristan modem-manager[1063]: <info>  (ttyUSB2) closing
> serial port...
> May 26 12:34:39 tristan modem-manager[1063]: <info>  (ttyUSB2) serial
> port closed
> May 26 12:34:39 tristan modem-manager[1063]: <info>  (ttyUSB2) opening
> serial port...
> May 26 12:34:39 tristan modem-manager[1063]: <info>  (SimTech): GSM
> modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-4 claimed port
> ttyUSB2
> May 26 12:34:40 tristan modem-manager[1063]: <info>  (ttyUSB2) closing
> serial port...
> May 26 12:34:40 tristan modem-manager[1063]: <info>  (ttyUSB2) serial
> port closed
> May 26 12:34:42 tristan modem-manager[1063]: <info>  (ttyUSB1) closing
> serial port...
> May 26 12:34:47 tristan modem-manager[1063]: <info>  (ttyUSB1) serial
> port closed
> May 26 12:34:47 tristan modem-manager[1063]: <info>  (SimTech): GSM
> modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-4 claimed port
> ttyUSB1
> May 26 12:35:01 tristan modem-manager[1063]: <info>  (ttyUSB0) closing
> serial port...
> May 26 12:35:06 tristan modem-manager[1063]: <info>  (ttyUSB0) serial
> port closed
> May 26 12:35:06 tristan NetworkManager[909]: <warn> (ttyUSB2): failed
> to look up interface index
> May 26 12:35:06 tristan NetworkManager[909]: <info> WWAN now disabled
> by management service
> May 26 12:35:06 tristan NetworkManager[909]: <info> (ttyUSB2): new
> GSM/UMTS device (driver: 'option1' ifindex: -1)
> May 26 12:35:06 tristan NetworkManager[909]: <info> (ttyUSB2):
> exported as /org/freedesktop/NetworkManager/Devices/3
> May 26 12:35:06 tristan NetworkManager[909]: <info> (ttyUSB2): now
> managed
> May 26 12:35:06 tristan NetworkManager[909]: <info> (ttyUSB2): device
> state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
> May 26 12:35:06 tristan NetworkManager[909]: <info> (ttyUSB2):
> deactivating device (reason: 2).
> May 26 12:35:06 tristan NetworkManager[909]: <info> (ttyUSB2): device
> state change: unavailable -> disconnected (reason 'none') [20 30 0]
> 
> May 26 12:39:01 tristan NetworkManager[909]: <info> WWAN now enabled
> by management service
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) starting connection 'SingTel Default'
> May 26 12:39:11 tristan NetworkManager[909]: <info> (ttyUSB2): device
> state change: disconnected -> prepare (reason 'none') [30 40 0]
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
> May 26 12:39:11 tristan modem-manager[1063]: <info>
> Modem /org/freedesktop/ModemManager/Modems/0: state changed
> (registered -> connecting)
> May 26 12:39:11 tristan modem-manager[1063]: <info>
> Modem /org/freedesktop/ModemManager/Modems/0: state changed
> (connecting -> connected)
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 2 of 5 (Device Configure) scheduled...
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 2 of 5 (Device Configure) starting...
> May 26 12:39:11 tristan NetworkManager[909]: <info> (ttyUSB2): device
> state change: prepare -> config (reason 'none') [40 50 0]
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 2 of 5 (Device Configure) successful.
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 3 of 5 (IP Configure Start) scheduled.
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 2 of 5 (Device Configure) complete.
> May 26 12:39:11 tristan NetworkManager[909]: <info> Activation
> (ttyUSB2) Stage 3 of 5 (IP Configure Start) started...
> May 26 12:39:11 tristan NetworkManager[909]: <info> (ttyUSB2): device
> state change: config -> ip-config (reason 'none') [50 70 0]
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list