Re: Alcatel x060s - incorrect port
- From: Dan Williams <dcbw redhat com>
- To: Andrey Alakozov <aa29ww gmail com>
- Cc: networkmanager-list gnome org
- Subject: Re: Alcatel x060s - incorrect port
- Date: Thu, 06 May 2010 15:30:28 -0700
On Fri, 2010-04-30 at 15:45 +0400, Andrey Alakozov wrote:
> 29.04.2010 22:22, Dan Williams пишет:
>
> > Is there any chance I can get the Windows .INF files from you off the
> > device's fake driver CD? In a pinch, feel free to just mail me the
> > entire contents of the fake driver CD or post it somewhere I can grab
> > it. This will clear up the issue 100%.
>
> Yes, these are Windows 7 drivers provided by modem distributor:
> http://www.svyaznoy.ru/upload/Window_7(32&64)_Patch.zip
Thanks; that confirms that the rules in 77-longcheer.rules are correct
and that USB interface #3 is the correct interface to use for the
modem/ppp stuff. So the ports should get tagged correctly.
I just found your bug too; the problem was that the Longcheer plugin
also contains a vendor ID check, and since your Alcatel x060s has a
different vendor ID, it wasn't getting grabbed by the Longcheer plugin.
The generic plugin doesn't handle port tags because most generic modems
don't need them.
I've committed that fix upstream as:
425c28dfc1d24126feab432609f2c525069d577e
this is a very safe commit for Ubuntu to backport. At this point, I'd
suggest filing a bug in Launchpad requesting a backport for this
specific commit and follow up the actual Ubuntu packages there.
Thanks for reporting this!
Dan
> >
> > I have the driver for the X020s, but not the X060s.
> >
> >> While playing with it I found that NM fails to find modem if Ethernet
> >> connection is active:
> >>
> >> # tail -f /var/log/syslog
> >>
> >> ...
> >> Apr 29 13:18:07 andrey-laptop NetworkManager: Could not get modem
> >> driver: Did not receive a reply. Possible causes include: the remote
> >> application did not send a reply, the message bus security policy
> >> blocked the reply, the reply timeout expired, or the network connection
> >> was broken.
> >
> > Quite interesting; that indicates a problem with ModemManager. Any
> > chance you can grab some modem-manager debugging for me?
> >
> > http://live.gnome.org/NetworkManager/Debugging
> >
> > under the "Debugging NetworkManager 0.8.x 3G connections" section. And
> > lets see what's going on there.
>
> After doing some more experiments I found that it is not Ethernet that
> causes problem. NM fails if I detach and attach modem back. If I attach
> it quickly and to the same USB port, NM alway fails. If I attach it
> after a minute and to the different USB port it is more probable to get
> it working. modem-manager log looks the same in all cases. I've also
> noticed, that after Ethernet is connected, NM starts using ttyUSB1 for
> modem, though udevadm DB is not changed.
>
> So. the best way to make it work is a fresh boot without Ethernet cable
> connected.
>
> Thanks again!
>
> Debag info:
>
> Kubuntu Lucid Beta 2
> kernel 2.6.32-21-generic
> Aclatel x060s
>
> # lsusb -v
> ...
> Bus 001 Device 020: ID 1bbb:0000 T & A Mobile Phones
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x1bbb T & A Mobile Phones
> idProduct 0x0000
> bcdDevice 0.00
> iManufacturer 2 USBModem
> iProduct 1 USBModem Configuration
> iSerial 3 1234567890ABCDEF
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 108
> bNumInterfaces 4
> bConfigurationValue 1
> iConfiguration 1 USBModem Configuration
> bmAttributes 0xa0
> (Bus Powered)
> Remote Wakeup
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 32
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01 EP 1 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 32
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 1
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 32
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 32
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 2
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 8 Mass Storage
> bInterfaceSubClass 6 SCSI
> bInterfaceProtocol 80 Bulk (Zip)
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x03 EP 3 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 3
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x84 EP 4 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 5
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x85 EP 5 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 32
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x04 EP 4 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 32
> Device Qualifier (for other device speed):
> bLength 10
> bDescriptorType 6
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> bNumConfigurations 1
> Device Status: 0x0001
> Self Powered
> ...
>
> # dmesg
>
> ...
> [90548.981128] usb 1-1: new high speed USB device using ehci_hcd and
> address 21
> [90549.116217] usb 1-1: configuration #1 chosen from 1 choice
> [90549.118356] scsi23 : SCSI emulation for USB Mass Storage devices
> [90549.118550] usb-storage: device found at 21
> [90549.118556] usb-storage: waiting for device to settle before scanning
> [90552.611416] usb 1-1: USB disconnect, address 21
> [90552.976067] usb 1-1: new high speed USB device using ehci_hcd and
> address 22
> [90553.116250] usb 1-1: configuration #1 chosen from 1 choice
> [90553.118555] option 1-1:1.0: GSM modem (1-port) converter detected
> [90553.118662] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
> [90553.118765] option 1-1:1.1: GSM modem (1-port) converter detected
> [90553.118843] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
> [90553.143835] scsi24 : SCSI emulation for USB Mass Storage devices
> [90553.145108] option 1-1:1.3: GSM modem (1-port) converter detected
> [90553.145262] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
> [90553.148444] usb-storage: device found at 22
> [90553.148448] usb-storage: waiting for device to settle before scanning
> [90558.185533] usb-storage: device scan complete
> [90558.186564] scsi 24:0:0:0: Direct-Access USBModem MMC Storage
> 2.31 PQ: 0 ANSI: 2
> [90558.187622] sd 24:0:0:0: Attached scsi generic sg2 type 0
> [90558.198730] sd 24:0:0:0: [sdb] Attached SCSI removable disk
>
> # tail /var/log/daemon.log
>
> Apr 30 14:14:50 andrey-laptop modem-manager: (ttyUSB1) opening serial
> device...
> Apr 30 14:15:05 andrey-laptop modem-manager: (ttyUSB1): probe requested
> by plugin 'Generic'
> Apr 30 14:15:10 andrey-laptop modem-manager: (ttyUSB2) opening serial
> device...
> Apr 30 14:15:10 andrey-laptop modem-manager: (ttyUSB2): probe requested
> by plugin 'Generic'
> Apr 30 14:15:10 andrey-laptop modem-manager: (ttyUSB0) opening serial
> device...
> Apr 30 14:15:25 andrey-laptop modem-manager: (ttyUSB0): probe requested
> by plugin 'Generic'
> Apr 30 14:15:47 andrey-laptop modem-manager: (ttyUSB1) closing serial
> device...
> Apr 30 14:15:52 andrey-laptop modem-manager: (ttyUSB2) closing serial
> device...
> Apr 30 14:15:52 andrey-laptop modem-manager: (Generic): GSM modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1 claimed port ttyUSB1
> Apr 30 14:15:52 andrey-laptop modem-manager: Added modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1
> Apr 30 14:15:52 andrey-laptop modem-manager: Exported modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1 as
> /org/freedesktop/ModemManager/Modems/12
> Apr 30 14:15:52 andrey-laptop modem-manager: (Generic): GSM modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1 claimed port ttyUSB2
> Apr 30 14:16:05 andrey-laptop modem-manager: (ttyUSB0) closing serial
> device...
> Apr 30 14:16:20 andrey-laptop NetworkManager: Could not get modem
> driver: Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network connection
> was broken.
>
> modem-manager detailed log
>
> ** Message: (ttyUSB1) opening serial device...
> ** (modem-manager:16681): DEBUG: (ttyUSB1): probe requested by plugin
> 'Generic'
> ** Message: (ttyUSB2) opening serial device...
> ** (modem-manager:16681): DEBUG: (ttyUSB2): probe requested by plugin
> 'Generic'
> ** Message: (ttyUSB0) opening serial device...
> ** (modem-manager:16681): DEBUG: (ttyUSB0): probe requested by plugin
> 'Generic'
> ** (modem-manager:16681): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
> ** (modem-manager:16681): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
> ** (modem-manager:16681): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
> ** (modem-manager:16681): DEBUG: (ttyUSB1): <--
> 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+FCLASS,+DS<CR><LF><CR><LF>OK<CR><LF>'
> ** (modem-manager:16681): DEBUG: (ttyUSB2): <--
> 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+FCLASS,+DS<CR><LF><CR><LF>OK<CR><LF>'
> ** (modem-manager:16681): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
> ** Message: (ttyUSB1) closing serial device...
> ** Message: (ttyUSB2) closing serial device...
> ** Message: (Generic): GSM modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1 claimed port ttyUSB1
> ** (modem-manager:16681): DEBUG: Added modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1
> ** (modem-manager:16681): DEBUG: Exported modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1 as
> /org/freedesktop/ModemManager/Modems/1
> ** Message: (Generic): GSM modem
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1 claimed port ttyUSB2
> ** (modem-manager:16681): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
> ** (modem-manager:16681): DEBUG: (ttyUSB0): --> 'ATI<CR>'
> ** (modem-manager:16681): DEBUG: (ttyUSB0): --> 'AT+CPIN?<CR>'
> ** (modem-manager:16681): DEBUG: (ttyUSB0): --> 'AT+CGMM<CR>'
> ** Message: (ttyUSB0) closing serial device...
>
> Network Manager detailed log
>
> NetworkManager: Could not get modem driver: Did not receive a reply.
> Possible causes include: the remote application did not send a reply,
> the message bus security policy blocked the reply, the reply timeout
> expired, or the network connection was broken.
>
> --
> Andrey
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
