Re: New USB 3G modem
- From: "Andrew Bird (Sphere Systems)" <ajb spheresystems co uk>
- To: networkmanager-list gnome org
- Subject: Re: New USB 3G modem
- Date: Sun, 11 Sep 2011 13:17:21 +0100
Hi Perazim,
See below.
On Sunday 11 September 2011, perazim portugalmail pt wrote:
> Here are the results:
>
> On Thu, 2011-09-08 at 21:40 +0100, Andrew Bird (Sphere Systems) wrote:
> Hi Perazim,
>
> > There's a few things you can do to get started:
> > try doing:
> > lsusb -v -d 0685:7000 # paste the log here
>
> -->
> [yossi@server ~]$ lsusb -v -d 0685:7000
>
> Bus 005 Device 005: ID 0685:7000
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x0685
> idProduct 0x7000
> bcdDevice 0.00
> iManufacturer 1
> iProduct 2
> iSerial 3
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 131
> bNumInterfaces 5
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xa0
> (Bus Powered)
> Remote Wakeup
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 3
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0010 1x 16 bytes
> bInterval 128
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> 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 3
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x84 EP 4 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x04 EP 4 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 2
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 3
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x85 EP 5 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x03 EP 3 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 3
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 3
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x87 EP 7 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x07 EP 7 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 4
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 8 Mass Storage
> bInterfaceSubClass 6 SCSI
> bInterfaceProtocol 80 Bulk (Zip)
> iInterface 3
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x05 EP 5 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> cannot read device status, Operation not permitted (1)
> [yossi@server ~]$
Looks promising. With the 'option' driver this should produce four tty ports
of /dev/ttyUSB0 .. /dev/ttyUSB3, with the modem(data) port on /dev/ttyUSB0
>
> > sudo su - # to become root, then
> > modprobe -a option
> > echo "0685 7000" > /sys/bus/usb-serial/drivers/option1/new_id
> > ls -l /dev/ttyUSB* # see if you have tty devices
>
> -->
> [root@server yossi]# modprobe -a option
> [root@server yossi]# echo "0685 700" >
> /sys/bus/usb-serial/drivers/option1/new_id
> [root@server yossi]# ls -l /dev/ttyUSB*
> ls: cannot access /dev/ttyUSB*: No such file or directory
> [root@server yossi]#
This should have worked, but it appears you are a zero short on the echo line.
I'd try again with the full product ID.
>
> > if you have then try using 'screen' to talk to them in turn
> > (you might have to install it)
> > screen /dev/ttyUSB0
> > ATI3
> > Ctrl-A k y
> >
> > screen /dev/ttyUSB1
> > ATI3
> > Ctrl-A k y
> >
> > and repeat until finished, note which ports respond to ATI3, and which
> > don't
> >
> >
> > Hope that helps,
> >
> >
> > Andrew
> >
> > On Thursday 08 September 2011, perazim portugalmail pt wrote:
> > > Dan, I am also working with the openWRT router project to get this
> > > modem working.
> > >
> > > > After posting to that forum, someone came forward regarding this
> > > > modem.
> > >
> > > They stated that usb_modeswitch was NOT used for this device and the
> > > modem was to be found on /dev/ttyUSB0. I have noticed that on windows
> > > that the drivers are installed everytime this device is plugged and
> > > this seems to confirm the non-use of usb_modeswitch. Also the is no
> > > evidence of usb_modeswitch in the syslog.
> > >
> > > > On openWRT I was able to get this to connect once and pass traffic
> > > > but
> > >
> > > it seems that I messed something up later.
> > >
> > > > Shall I make a copy of the fake driver CD for you now?
> > > > Thanks,
> > > > Perazim
> > > > On Fri, 2011-09-02 at 15:53 +0100, perazim portugalmail pt wrote:
> > > > I have a "generic" USB modem labeled "HSDPA 3.5G Wireless Modem"
> > > > bought from Deal Extreme in Hong Kong.
> > > >
> > > > > > It works on Windows XP and installs its own drivers when plugged
> > > > > > the
> > > >
> > > > first time.
> > > >
> > > > > > When plugged to Fedora 14, I see a CDROM detected and a USB
> > > > > > storage
> > > >
> > > > device if a microSDHC is plugged into the slot on the modem. I do not
> > > > see usb_modeswitch run and NetworkManager does not see this modem.
> > > > usb_modeswitch needs the right logic to flip the device to modem
> > > > mode,
> > >
> > > without that there's no change ModemManager can detect the modem,
> > > because it's not a modem yet. After that, we may need to implement
> > > support for this device's specific quirks. I usually ask users to
> > > zip/gzip up the contents of the "fake" driver CD and email it to me so
> > > that I can inspect the drivers and the connection manager and determine
> > > what AT commands (and thus what firmware variant) the device uses.
> > > Then we can implement more than basic support for the device.
> > >
> > > > > Using lsusb I see: ID 0685:7000 with no description whatever. There
> > > > > is
> > > >
> > > > no file by this name in /etc/usb_modeswitch.d/
> > > >
> > > > > > How do I add this modem to the appropriate tables so that it is
> > > >
> > > > detected?
> > > > If there is no entry for that device in usb_modeswitch's /etc
> > > > directory,
> > >
> > > then you'll need to communicate first with the usb_modeswitch project
> > > and determine the sequence to flip the device to modem mode. That
> > > might include installing a USB sniffer in Windows and sniffing the
> > > command sequences that the driver uses to tell the device to enter
> > > modem mode. The usb_modeswitch project is pretty good about helping
> > > people through that process. Once that's done, we can proceed with
> > > inspecting the actual modem and determining what we need to do to get
> > > it connecting to the network.
> > >
> > > > Dan
> > > > _______________________________________________
> > >
> > > networkmanager-list mailing list
> > > networkmanager-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> > _______________________________________________
> > networkmanager-list mailing list
> > networkmanager-list gnome org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
