Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Quoting Dan Williams : On Sat, 2013-08-17 at 18:05 -0400, Peter Hyman wrote: snip Maybe this will move the ball. We'll see. Thank you. Yes, I was given that document by Sierra a couple years ago. No, it doesn't help, because it only covers basic CDMA/EVDO stuff and does not cover anything related GSM/UMTS/LTE or other basic modem operations like mode switching. So yes, it documents HIP and CnS, but we'd still need to reverse engineer the mode switch packets that Peter is looking for. Dan Diminishing returns. For a three year old product which is not actively supported by the vendor (linux drivers are old), I recommend we just adopt the workaround I wrote and leave it there. Obviously proprietary things are done in the proprietary Windows software. Thanks all for taking a look. -- Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On Sat, 2013-08-17 at 18:05 -0400, Peter Hyman wrote: > On 08/17/2013 04:58 PM, Forest Bond wrote: > > snip... > > > > Okay, I published it here: > > > > > http://www.alittletooquiet.net/media/2131024%20CDMA%20EVDO%20CnS%20Reference.pdf > > > > For the record, the document states its license as follows: > > > > http://creativecommons.org/licenses/by-nd/3.0/us/ > > > > You are free: > > > > to Share — to copy, distribute,display, and perform the work > > > > Under the following conditions: > > > > Attribution. You must attribute the work in the manner specified by > the author > > or licensor (but not in any way that suggests that they endorse you > or your > > use of the work). > > > > No Derivative Works. You may not alter, transform, or build upon > this work. > > > > Thanks, > > Forest > > Maybe this will move the ball. We'll see. Thank you. Yes, I was given that document by Sierra a couple years ago. No, it doesn't help, because it only covers basic CDMA/EVDO stuff and does not cover anything related GSM/UMTS/LTE or other basic modem operations like mode switching. So yes, it documents HIP and CnS, but we'd still need to reverse engineer the mode switch packets that Peter is looking for. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/17/2013 04:58 PM, Forest Bond wrote: snip... > Okay, I published it here: > > http://www.alittletooquiet.net/media/2131024%20CDMA%20EVDO%20CnS%20Reference.pdf > > For the record, the document states its license as follows: > > http://creativecommons.org/licenses/by-nd/3.0/us/ > > You are free: > > to Share — to copy, distribute,display, and perform the work > > Under the following conditions: > > Attribution. You must attribute the work in the manner specified by the author > or licensor (but not in any way that suggests that they endorse you or your > use of the work). > > No Derivative Works. You may not alter, transform, or build upon this work. > > Thanks, > Forest Maybe this will move the ball. We'll see. Thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Hi, On Sat, Aug 17, 2013 at 03:47:48PM +0200, Oleksij Rempel wrote: > Am 17.08.2013 14:53, schrieb Forest Bond: > >Hi, > > > >On Thu, Aug 15, 2013 at 03:31:40PM -0500, Dan Williams wrote: > >>On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote: > >>>On 08/15/2013 09:47 AM, Dan Williams wrote: > On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote: > >Peter Hyman writes: > > > >>On 08/14/2013 01:42 PM, Bjørn Mork wrote: > >>snip... > >> > >>>Great! And if you can snoop on Windows trying to figure out how to > >>>switch the modes, then that would also help. I believe Wireshark with > >>>usbpcap is the current state-of-the-art USB sniffer for Windows: > >>>http://desowin.org/usbpcap/ > >>> > >>> > >>>Bjørn > >>Detailed files attached. > Anyone mind sending those files over to me? > > Dan > >>>snip... > >>> > >>>Please download AC250U_lsusb_pcap.tar.bz2 from: > >>>https://app.box.com/s/6sln7t1na4pz6ij7ggpc > >> > >>The modem is speaking Sierra's proprietary CnS protocol. This is a > >>proprietary protocol for which no public documentation has been > >>released, and so we'd have to reverse-engineer the specific commands > >>being used to switch the modem between 3G and 4G mode. > > > >This is actually not true. Sierra released a document titled "CDMA 1xEV-DO > >CnS > >Reference" under a Creative Commons license. It has since disappeared from > >the > >Internet, but private copies exist. ;) There are a large number of specifics > >not covered by this document, but it does cover the basics of speaking CnS. > > > >Actually, I recall you mentioning this document here: > > > >http://blogs.gnome.org/dcbw/2010/04/15/mobile-broadband-and-qualcomm-proprietary-protocols/ > > > >I can post the document somewhere if it would be helpful. It's only 279KB. > > i would like to have this document if possible :) Okay, I published it here: http://www.alittletooquiet.net/media/2131024%20CDMA%20EVDO%20CnS%20Reference.pdf For the record, the document states its license as follows: http://creativecommons.org/licenses/by-nd/3.0/us/ You are free: to Share — to copy, distribute,display, and perform the work Under the following conditions: Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). No Derivative Works. You may not alter, transform, or build upon this work. Thanks, Forest -- Forest Bond http://www.alittletooquiet.net http://www.rapidrollout.com signature.asc Description: Digital signature
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Hi, On Thu, Aug 15, 2013 at 03:31:40PM -0500, Dan Williams wrote: > On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote: > > On 08/15/2013 09:47 AM, Dan Williams wrote: > > > On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote: > > >> Peter Hyman writes: > > >> > > >>> On 08/14/2013 01:42 PM, Bjørn Mork wrote: > > >>> snip... > > >>> > > Great! And if you can snoop on Windows trying to figure out how to > > switch the modes, then that would also help. I believe Wireshark with > > usbpcap is the current state-of-the-art USB sniffer for Windows: > > http://desowin.org/usbpcap/ > > > > > > Bjørn > > >>> Detailed files attached. > > > Anyone mind sending those files over to me? > > > > > > Dan > > snip... > > > > Please download AC250U_lsusb_pcap.tar.bz2 from: > > https://app.box.com/s/6sln7t1na4pz6ij7ggpc > > The modem is speaking Sierra's proprietary CnS protocol. This is a > proprietary protocol for which no public documentation has been > released, and so we'd have to reverse-engineer the specific commands > being used to switch the modem between 3G and 4G mode. This is actually not true. Sierra released a document titled "CDMA 1xEV-DO CnS Reference" under a Creative Commons license. It has since disappeared from the Internet, but private copies exist. ;) There are a large number of specifics not covered by this document, but it does cover the basics of speaking CnS. Actually, I recall you mentioning this document here: http://blogs.gnome.org/dcbw/2010/04/15/mobile-broadband-and-qualcomm-proprietary-protocols/ I can post the document somewhere if it would be helpful. It's only 279KB. Thanks, Forest -- Forest Bond http://www.alittletooquiet.net http://www.rapidrollout.com -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/15/2013 03:31 PM, Dan Williams wrote: snip... > On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote: >> snip... >> >> Please download AC250U_lsusb_pcap.tar.bz2 from: >> https://app.box.com/s/6sln7t1na4pz6ij7ggpc > The modem is speaking Sierra's proprietary CnS protocol. This is a > proprietary protocol for which no public documentation has been > released, and so we'd have to reverse-engineer the specific commands > being used to switch the modem between 3G and 4G mode. > > Dan > Why does this not surprise me? Anyway, I think we're done. It's Netgear now and I am sure this old product won't get any support. I wrote up some doc on this to use or not to identify and work around the issue. Thanks for the deep dive. Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote: > On 08/15/2013 09:47 AM, Dan Williams wrote: > > On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote: > >> Peter Hyman writes: > >> > >>> On 08/14/2013 01:42 PM, Bjørn Mork wrote: > >>> snip... > >>> > Great! And if you can snoop on Windows trying to figure out how to > switch the modes, then that would also help. I believe Wireshark with > usbpcap is the current state-of-the-art USB sniffer for Windows: > http://desowin.org/usbpcap/ > > > Bjørn > >>> Detailed files attached. > > Anyone mind sending those files over to me? > > > > Dan > snip... > > Please download AC250U_lsusb_pcap.tar.bz2 from: > https://app.box.com/s/6sln7t1na4pz6ij7ggpc The modem is speaking Sierra's proprietary CnS protocol. This is a proprietary protocol for which no public documentation has been released, and so we'd have to reverse-engineer the specific commands being used to switch the modem between 3G and 4G mode. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/15/2013 09:47 AM, Dan Williams wrote: > On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote: >> Peter Hyman writes: >> >>> On 08/14/2013 01:42 PM, Bjørn Mork wrote: >>> snip... >>> Great! And if you can snoop on Windows trying to figure out how to switch the modes, then that would also help. I believe Wireshark with usbpcap is the current state-of-the-art USB sniffer for Windows: http://desowin.org/usbpcap/ Bjørn >>> Detailed files attached. > Anyone mind sending those files over to me? > > Dan snip... Please download AC250U_lsusb_pcap.tar.bz2 from: https://app.box.com/s/6sln7t1na4pz6ij7ggpc File was too large for gmane. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On Thu, 2013-08-15 at 03:47 -0500, Peter Hyman wrote: > On 08/14/2013 06:03 PM, Dan Williams wrote: > snip... > > It's almost certainly not the domain of the driver to switch this mode, > > it's the responsibility of userland. Kernel drivers must only talk to > > the device, they are not supposed to do any kind of policy or switching. > > Also, it would have to be a choice to switch, since some users may > > already be using the out-of-tree Beceem WiMAX stack and drivers and we > > can't screw it up for them. > > > > It's possible that we could determine the current mode via the > > proprietary QCDM using the "modepref" tool from ModemManager sources: > > > > http://cgit.freedesktop.org/ModemManager/ModemManager/tree/libqcdm/tests > > > > but QCDM has no "WIMAX" option that I'm aware of, so I'd be quite > > curious to see what modepref reports when the device is in 4G-only mode. > > I've attached an x86_64 build of modepref, give it a shot on ttyUSB1, > > ttyUSB2, or ttyUSB3 and see what comes out: > > > > modepref /dev/ttyUSB1 --debug > > > > Thanks, > > Dan > I ran modepref in both 3G and 4G modes. Output attached. They look > identical to me. Anything stand out? Nothing, except that QCDM doesn't appear to know anything about the mode here. There must be some other mechanism that controls the 3G/4G mode stuff, can you send me the traces you sent Bjorn so I can see if anything there looks interesting? Dan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote: > Peter Hyman writes: > > > On 08/14/2013 01:42 PM, Bjørn Mork wrote: > > snip... > > > >> Great! And if you can snoop on Windows trying to figure out how to > >> switch the modes, then that would also help. I believe Wireshark with > >> usbpcap is the current state-of-the-art USB sniffer for Windows: > >> http://desowin.org/usbpcap/ > >> > >> > >> Bjørn > > > > Detailed files attached. Anyone mind sending those files over to me? Dan > > Archive: AC250U_lsusb_pcap.zip > > Length MethodSize CmprDateTime CRC-32 Name > > -- --- -- - > > 6162648 Defl:N 2029329 67% 08-14-2013 15:22 14f8de80 3g.pcap > > 7015710 Defl:N 2190669 69% 08-14-2013 15:07 55ce8a54 4g.pcap > > 1565 Defl:N 478 70% 08-14-2013 15:30 9b150f7f > > sierra_driver_output_w4g_set.rpt > > 4589 Defl:N 636 86% 08-14-2013 13:59 7908a3b4 > > lsusb_1199_0301_3g.rpt > > 4589 Defl:N 636 86% 08-14-2013 15:30 7908a3b4 > > lsusb_1199_0301_4g.rpt > > 385 Defl:N 210 46% 08-14-2013 15:36 a7016844 > > lsusb_198f_0220.diff > > 6231 Defl:N 711 89% 08-14-2013 14:15 cf018349 > > lsusb_198f_0220_3g.rpt > > 6231 Defl:N 711 89% 08-14-2013 15:31 376b38d0 > > lsusb_198f_0220_4g.rpt > > > > > > 3g.pcap = sniff from when unit STARTS in 3G. Sprint Software > > automatically switched to 4G and that is the last event > > Thanks. The lsusb outputs show that there are no descriptor differences > between the two modes. The diff you see is only the device address, > which is a dynamic property and expected to change every time you plug > in a device. > > Unfortunately there is a large number of vendor specific control > requests addressed to endpoint 0x00 and 0x80, which is odd by itself > IMHO. These give a number of different values for wValue and wIndes, > and the meaning is not obvious (too me at least). Some of this is > obviously switching mode, but it looks like it does so as part of a more > complex device setup and configuration. So there is no easy way out > here. We could try replaying the sequence blindly, but I fear that is > pointless without more understanding. > > The data following the control requests looks mostly like a HDLC like > protocol over bulk endpoints 0x04 and 0x84 on device 3-3 (the above is > sent to device 3-4). The bulk data has a 5 byte prefix, 0x7e before and > after the frame data, and a 16 bit checksum. > > Given that only the 1199:0301 device has a 0x84 endpoint, we know that > device 3-3 is the Sierra serial device (which also makes sense wrt the > serial protocol observed). So the magic control requests are sent to > the 198f:0220 device, as expected. > > Sorry, I don't know if any of this helped at all. The device mode > switching is not as simple and obvious the common usb-storage type > switching, and trying to guess the more complex vendor specific control > protocol is going to take a lot of trial and error. > > > 4g.pcap = sniff from when unit STARTS in 4G. Changed to 3G using Sprint > > Software and that was the last event > > sierra_driver_output_w4g_set.rpt = sierra and usbserial driver output > > from /var/log/messages when unit inserted in 4G mode > > lsusb*.rpt = lsusb -vd for 1199 and 198f devices > > lsusb_198f_0220.diff shows one line difference when WiMAX device is 6 > > when loaded in 4G and 4 when loaded in 3G > > > > Not so familiar with Wireshark or how to detect the switchover though. I > > hope this helps. ITMT, I will download Beceem driver from git and see if > > that makes a difference. > > Yes, I recommend trying to get that driver going. Googling for it will > point you to a number of howtos. > > > One final note. When device is set to 4G and inserted into Linux box, > > the 3G LED lights and blinks several times before going off. It tries to > > load it, but the device firmware still knows it is 4G so it fails. > > Yes, or it just indicates traffic on the AT serial port until the PPP > connection fails. > > > Bjørn > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Quoting Bjørn Mork : snip... > > Thanks. The lsusb outputs show that there are no descriptor differences > between the two modes. The diff you see is only the device address, > which is a dynamic property and expected to change every time you plug > in a device. > > Unfortunately there is a large number of vendor specific control > requests addressed to endpoint 0x00 and 0x80, which is odd by itself > IMHO. These give a number of different values for wValue and wIndes, > and the meaning is not obvious (too me at least). Some of this is > obviously switching mode, but it looks like it does so as part of a more > complex device setup and configuration. So there is no easy way out > here. We could try replaying the sequence blindly, but I fear that is > pointless without more understanding. > snip... Well, as I initially posted, this is just a FAQ and workaround for those who experience this issue. I am not surprised there is a lot of proprietary stuff going on and it is not a worthwhile reverse engineering exercise. I do believe a Documentation entry would be worthwhile so that others who experience this can fix it. A lot of ppl use M$ for work and this device will get messed up every time. I will also download the Beceem WiMAX driver and see if it works. I believe we've spend enough time on this :-) I've attached a small document for review by maintainers, sierra.txt, that describes the issue and resolution as of today. I only list the AC250U device, but hopefully others can add to it as new devices with this issue are uncovered. It should be filed under Documentation/usb if accepted. Thank you for your time! Peter August 2013 Driver: sierra Issue: Devices recognized, but no connection to internet Root Cause: Device likely set to 4G mode which is unsupported Resolution: Reset device to use 3G mode using vendor software Description of Issue: Users who have a Sierra Wireless (now Netgear) device that operates in 3G and 4G mode may experience connectivity issues if the device was placed in 4G mode via vendor software in other Operating Systems. Currently, the Sierra driver only supports 3G mode. If the device is in 4G mode, it won't use PPP protocol, but attempt to use WiMAX which is not currently supported under Linux. As a result, no connection will be possible. If using a Sierra (Netgear) device and you experience connectivity problems, set your device back to 3G mode using vendor sofwtare. Then reconnect in Linux. dmesg output will indicate if the Serial device (3G) and/or the WiMAX device (4G) are detected. If the 4G device is detected, it's an indication your device is set to 4G mode. *** Please add to this list *** Devices currently impacted (see /var/log/messages): AC250U: 3G Mode Vendor ID: 1199, Product ID: 0301 4G Mode Vendor ID: 198f, Product ID: 0220 Submitted by Peter Hyman
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Peter Hyman writes: > On 08/14/2013 01:42 PM, Bjørn Mork wrote: > snip... > >> Great! And if you can snoop on Windows trying to figure out how to >> switch the modes, then that would also help. I believe Wireshark with >> usbpcap is the current state-of-the-art USB sniffer for Windows: >> http://desowin.org/usbpcap/ >> >> >> Bjørn > > Detailed files attached. > > Archive: AC250U_lsusb_pcap.zip > Length MethodSize CmprDateTime CRC-32 Name > -- --- -- - > 6162648 Defl:N 2029329 67% 08-14-2013 15:22 14f8de80 3g.pcap > 7015710 Defl:N 2190669 69% 08-14-2013 15:07 55ce8a54 4g.pcap > 1565 Defl:N 478 70% 08-14-2013 15:30 9b150f7f > sierra_driver_output_w4g_set.rpt > 4589 Defl:N 636 86% 08-14-2013 13:59 7908a3b4 > lsusb_1199_0301_3g.rpt > 4589 Defl:N 636 86% 08-14-2013 15:30 7908a3b4 > lsusb_1199_0301_4g.rpt > 385 Defl:N 210 46% 08-14-2013 15:36 a7016844 > lsusb_198f_0220.diff > 6231 Defl:N 711 89% 08-14-2013 14:15 cf018349 > lsusb_198f_0220_3g.rpt > 6231 Defl:N 711 89% 08-14-2013 15:31 376b38d0 > lsusb_198f_0220_4g.rpt > > > 3g.pcap = sniff from when unit STARTS in 3G. Sprint Software > automatically switched to 4G and that is the last event Thanks. The lsusb outputs show that there are no descriptor differences between the two modes. The diff you see is only the device address, which is a dynamic property and expected to change every time you plug in a device. Unfortunately there is a large number of vendor specific control requests addressed to endpoint 0x00 and 0x80, which is odd by itself IMHO. These give a number of different values for wValue and wIndes, and the meaning is not obvious (too me at least). Some of this is obviously switching mode, but it looks like it does so as part of a more complex device setup and configuration. So there is no easy way out here. We could try replaying the sequence blindly, but I fear that is pointless without more understanding. The data following the control requests looks mostly like a HDLC like protocol over bulk endpoints 0x04 and 0x84 on device 3-3 (the above is sent to device 3-4). The bulk data has a 5 byte prefix, 0x7e before and after the frame data, and a 16 bit checksum. Given that only the 1199:0301 device has a 0x84 endpoint, we know that device 3-3 is the Sierra serial device (which also makes sense wrt the serial protocol observed). So the magic control requests are sent to the 198f:0220 device, as expected. Sorry, I don't know if any of this helped at all. The device mode switching is not as simple and obvious the common usb-storage type switching, and trying to guess the more complex vendor specific control protocol is going to take a lot of trial and error. > 4g.pcap = sniff from when unit STARTS in 4G. Changed to 3G using Sprint > Software and that was the last event > sierra_driver_output_w4g_set.rpt = sierra and usbserial driver output > from /var/log/messages when unit inserted in 4G mode > lsusb*.rpt = lsusb -vd for 1199 and 198f devices > lsusb_198f_0220.diff shows one line difference when WiMAX device is 6 > when loaded in 4G and 4 when loaded in 3G > > Not so familiar with Wireshark or how to detect the switchover though. I > hope this helps. ITMT, I will download Beceem driver from git and see if > that makes a difference. Yes, I recommend trying to get that driver going. Googling for it will point you to a number of howtos. > One final note. When device is set to 4G and inserted into Linux box, > the 3G LED lights and blinks several times before going off. It tries to > load it, but the device firmware still knows it is 4G so it fails. Yes, or it just indicates traffic on the AT serial port until the PPP connection fails. Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/14/2013 01:58 PM, Dan Williams wrote: snip > The 4G part of the 250U is a Beceem WiMAX chip, for which there are no > drivers on Linux at this time. The 4G parts are used with a > pseudo-ethernet interface, but since there aren't any kernel drivers, > that's not going to work. The 4G parts do not use PPP. The 3G part, > however, *does* use PPP over the serial ports. So with this > information, it's not surprising that when you choose "4G Only" in > Windows, the 3G part (eg, PPP over serial ports) isn't going to work > on Linux. Dan Yes, but if we knew 1) to Identify that 4G has been set, and 2) the command to toggle the device from 4G-3G, then this problem could be identified by the driver and the unit switched back to 3G and a log message printed. Then, the issue would be avoided, right? -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On Wed, 2013-08-14 at 11:43 -0500, Peter Hyman wrote: > Linux Kernel: 3.9.10 > Device Driver: usb/serial/sierra.c > Device Driver version: not known > > Apparently Sierra has sold the AirCard 250U product to Netgear, so I am > sure driver development on drivers/usb/serial/sierra.c will be in limbo > for a period. While I am copying li...@sierrawireless.com, they will not > do anything since they don't own the product anymore. > > Nonetheless, I uncovered a problem when using the AC250U Aircard device > Vendor 0x1199, Product 0x0301. If the device is used in Windows and set > to 4G mode, using the device in Linux will fail to create the ppp0 > network interface. I could find no workaround. Even though the device > can be reached and modem commands sent, ppp0 won't be created. I > regression tested this all the way back to kernel 3.2.29, and I also > tried the unpublished sierra driver 1.7.40 which works up to kernel > 3.4.x iirc. The issue is the same. The 4G part of the 250U is a Beceem WiMAX chip, for which there are no drivers on Linux at this time. The 4G parts are used with a pseudo-ethernet interface, but since there aren't any kernel drivers, that's not going to work. The 4G parts do not use PPP. The 3G part, however, *does* use PPP over the serial ports. So with this information, it's not surprising that when you choose "4G Only" in Windows, the 3G part (eg, PPP over serial ports) isn't going to work on Linux. Dan > The workaround is to set the device to 3G mode and then use in Linux. I > wrote this FAQ in case it is of interest. > = > FAQ: ppp0 Network Interface does not get created after plugging AirCard > 250U device when using Linux. No internet access is possible without the > ppp0 network interface. > > Answer: If the AC250U device is used in Windows, and is set to 4G mode > by the Sprint SmartView software, it MUST be set back to 3G mode prior > to use in Linux. The Linux Sierra driver does not support 4G and the > device won't be able to be initialized properly. It will be recognized > and you can send modem commands, but the ppp0 device won't be created. > Reset device to 3G under Windows and it will work fine in Linux. > = > > Maybe a nice feature request would be to check the 3G/4G status of the > device and reset to 3G since that is what is supported for now. If you > need additional information, please reach out. Happy to help. > > usb 4-1.2.2: New USB device found, idVendor=1199, idProduct=0301 > usb 4-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=4 > usb 4-1.2.2: Product: Sierra Wireless Device > usb 4-1.2.2: Manufacturer: Sierra Wireless, Incorporated > usb 4-1.2.2: SerialNumber: 4Vx«Ãïÿÿÿÿ > usbcore: registered new interface driver usbserial > usbcore: registered new interface driver usbserial_generic > usbserial: USB Serial support registered for generic > usbcore: registered new interface driver sierra > usbserial: USB Serial support registered for Sierra USB modem > sierra 4-1.2.2:1.0: Sierra USB modem converter detected > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB0 > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB1 > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB2 > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB3 > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/14/2013 01:42 PM, Bjørn Mork wrote: > snip... > Great! And if you can snoop on Windows trying to figure out how to > switch the modes, then that would also help. I believe Wireshark with > usbpcap is the current state-of-the-art USB sniffer for Windows: > http://desowin.org/usbpcap/ > > > Bjørn ITMT, here is some output for the Beceem vendor and product ID. It does not show in the syslog while the driver loads, but the hardware is recognized. Bus 004 Device 004: ID 198f:0220 Beceem Communications Inc. BCSM250 WiMAX Adapter Bus 004 Device 005: ID 1199:0301 Sierra Wireless, Inc. It could be that when 4G is set, the Linux system looks at the WiMax first. Then usbserial does not know what to do? bash-4.2$ lsusb -vd 198f:0220 Bus 004 Device 004: ID 198f:0220 Beceem Communications Inc. BCSM250 WiMAX Adapter Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0x198f Beceem Communications Inc. idProduct 0x0220 BCSM250 WiMAX Adapter bcdDevice0.01 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 111 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 6 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 6 bInterfac
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Peter Hyman writes: > On 08/14/2013 01:02 PM, Bjørn Mork wrote: >> Peter Hyman writes: >> >>> Linux Kernel: 3.9.10 >>> Device Driver: usb/serial/sierra.c >>> Device Driver version: not known >>> >>> Apparently Sierra has sold the AirCard 250U product to Netgear, so I am >>> sure driver development on drivers/usb/serial/sierra.c will be in limbo >>> for a period. While I am copying li...@sierrawireless.com, they will not >>> do anything since they don't own the product anymore. >>> >>> Nonetheless, I uncovered a problem when using the AC250U Aircard device >>> Vendor 0x1199, Product 0x0301. If the device is used in Windows and set >>> to 4G mode, using the device in Linux will fail to create the ppp0 >>> network interface. I could find no workaround. Even though the device >>> can be reached and modem commands sent, ppp0 won't be created. >> What exactly do you mean by "ppp0 won't be created"? The ppp interface >> is a virtual network device running on top of a serial port. Does this >> mean that there is one serial port missing? Or are all of them missing >> in this mode? Does this device support DirectIP, using the sierra_net >> driver? If so, does that still work in 4G mode? >> >> Exactly what action does the Windows driver/application do to trigger >> this? > > When the device is set in 3G mode, and is plugged in to a Linux box, a > network interface ppp0 (in my case) is created and permits interface to > the web. When using kppp or similar, you get a Connect ack from the > modem and everything performs as normal. > > When the device is set in 4G mode, and is plugged in to a Linux box, no > network interface is created and no access to web is permitted. When > using kppp or similar, you get a NO CARRIER ack from the modem and there > is no way to advance. That pretty much answers my questions. You get the same serial ports, and you can configure the device using AT commands, but it cannot emulate PPP in 4G mode. That's most likely a firmware limitation, and we should focus on 1) getting it to work in 4G mode using the network device like Windows does (bcm-wimax driver?) 2) switch the device to 3G mode from Linux so that we don't depend on Windows for this >>> I >>> regression tested this all the way back to kernel 3.2.29, and I also >>> tried the unpublished sierra driver 1.7.40 which works up to kernel >>> 3.4.x iirc. The issue is the same. >>> >>> The workaround is to set the device to 3G mode and then use in Linux. I >>> wrote this FAQ in case it is of interest. >> Nice. Thanks. Documenting the problem is important. >> >> But I believe we can do better. Making this device work regardless of >> mode and Windows settings should not be too difficult. We just need to >> research a bit what's going on, and then try to do the same as Windows >> to make it work. > I BELIEVE it may be related to the inherent limitation of the driver > module, sierra.c, and it's documented inability to work with 4G. It may > have something to do with Wimax as well since a Wimax device shows up as > well. >> >> Could you start with sending the output of "lsusb -vd 1199:0301" for >> both the working (3G mode) and non-working (4G mode) cases? This will >> help understanding how the device appearance changes between these >> modes, if it does? > Here is the 3G output. I will need to log off and come back for the 4G. > I will save for a diff run when I do the 4G version. I DO know the > driver output is different for 3G and 4G. There is a stanza for WiMax > and a Beceem device with a different Vendor and Product ID than below. > Recall, one can access the device with AT commands regardless of 3G or > 4G mode. > usb 4-1.2.1: new high-speed USB device number 18 using ehci-pci > usb 4-1.2.1: New USB device found, idVendor=198f, idProduct=0220 > usb 4-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > usb 4-1.2.1: Product: Mobile WiMax SS > usb 4-1.2.1: Manufacturer: Beceem Communications Inc. > usb 4-1.2.1: SerialNumber: MSB220 Oh.. Right. I was probably too optimistic here. Didn't know this device was based on a Beceem chip. That's going to be difficult to support... Did you try the driver in staging? bjorn@nemi:/usr/local/src/git/linux$ less drivers/staging/bcm/Kconfig config BCM_WIMAX tristate "Beceem BCS200/BCS220-3 and BCSM250 wimax support" depends on USB && NET default N help This is an experimental driver for the Beceem WIMAX chipset used by Sprint 4G. I don't know how to use that driver, but I believe it ought to be possible to get the device running in 4G mode using it. > bash-4.2$ lsusb -vd 1199:0301 > > Bus 004 Device 005: ID 1199:0301 Sierra Wireless, Inc. > Couldn't open device, some information will be missing > Device Descriptor: > bLength18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProt
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/14/2013 01:05 PM, Greg KH wrote: > On Wed, Aug 14, 2013 at 11:43:37AM -0500, Peter Hyman wrote: >> Linux Kernel: 3.9.10 >> Device Driver: usb/serial/sierra.c >> Device Driver version: not known >> >> Apparently Sierra has sold the AirCard 250U product to Netgear, so I am >> sure driver development on drivers/usb/serial/sierra.c will be in limbo >> for a period. While I am copying li...@sierrawireless.com, they will not >> do anything since they don't own the product anymore. >> >> Nonetheless, I uncovered a problem when using the AC250U Aircard device >> Vendor 0x1199, Product 0x0301. If the device is used in Windows and set >> to 4G mode, using the device in Linux will fail to create the ppp0 >> network interface. I could find no workaround. Even though the device >> can be reached and modem commands sent, ppp0 won't be created. I >> regression tested this all the way back to kernel 3.2.29, and I also >> tried the unpublished sierra driver 1.7.40 which works up to kernel >> 3.4.x iirc. The issue is the same. >> >> The workaround is to set the device to 3G mode and then use in Linux. I >> wrote this FAQ in case it is of interest. > How do you set the device to 3G mode? Can this be done in Linux using > the latest version of modemmanager and networkmanager? > > thanks, > > greg k-h I do not know if there is an AT command for this. Worth investigating though. I have zero documentation on the device and the driver, sierra.c, ignores 4G altogether. -- Peter Hyman C: +1(609)598-0262 http://www.peterhyman.com http://www.linkedin.com/in/peterh -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On 08/14/2013 01:02 PM, Bjørn Mork wrote: > Peter Hyman writes: > >> Linux Kernel: 3.9.10 >> Device Driver: usb/serial/sierra.c >> Device Driver version: not known >> >> Apparently Sierra has sold the AirCard 250U product to Netgear, so I am >> sure driver development on drivers/usb/serial/sierra.c will be in limbo >> for a period. While I am copying li...@sierrawireless.com, they will not >> do anything since they don't own the product anymore. >> >> Nonetheless, I uncovered a problem when using the AC250U Aircard device >> Vendor 0x1199, Product 0x0301. If the device is used in Windows and set >> to 4G mode, using the device in Linux will fail to create the ppp0 >> network interface. I could find no workaround. Even though the device >> can be reached and modem commands sent, ppp0 won't be created. > What exactly do you mean by "ppp0 won't be created"? The ppp interface > is a virtual network device running on top of a serial port. Does this > mean that there is one serial port missing? Or are all of them missing > in this mode? Does this device support DirectIP, using the sierra_net > driver? If so, does that still work in 4G mode? > > Exactly what action does the Windows driver/application do to trigger > this? When the device is set in 3G mode, and is plugged in to a Linux box, a network interface ppp0 (in my case) is created and permits interface to the web. When using kppp or similar, you get a Connect ack from the modem and everything performs as normal. When the device is set in 4G mode, and is plugged in to a Linux box, no network interface is created and no access to web is permitted. When using kppp or similar, you get a NO CARRIER ack from the modem and there is no way to advance. >> I >> regression tested this all the way back to kernel 3.2.29, and I also >> tried the unpublished sierra driver 1.7.40 which works up to kernel >> 3.4.x iirc. The issue is the same. >> >> The workaround is to set the device to 3G mode and then use in Linux. I >> wrote this FAQ in case it is of interest. > Nice. Thanks. Documenting the problem is important. > > But I believe we can do better. Making this device work regardless of > mode and Windows settings should not be too difficult. We just need to > research a bit what's going on, and then try to do the same as Windows > to make it work. I BELIEVE it may be related to the inherent limitation of the driver module, sierra.c, and it's documented inability to work with 4G. It may have something to do with Wimax as well since a Wimax device shows up as well. > Could you start with sending the output of "lsusb -vd 1199:0301" for > both the working (3G mode) and non-working (4G mode) cases? This will > help understanding how the device appearance changes between these > modes, if it does? Here is the 3G output. I will need to log off and come back for the 4G. I will save for a diff run when I do the 4G version. I DO know the driver output is different for 3G and 4G. There is a stanza for WiMax and a Beceem device with a different Vendor and Product ID than below. Recall, one can access the device with AT commands regardless of 3G or 4G mode. usb 4-1.2.1: new high-speed USB device number 18 using ehci-pci usb 4-1.2.1: New USB device found, idVendor=198f, idProduct=0220 usb 4-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-1.2.1: Product: Mobile WiMax SS usb 4-1.2.1: Manufacturer: Beceem Communications Inc. usb 4-1.2.1: SerialNumber: MSB220 bash-4.2$ lsusb -vd 1199:0301 Bus 004 Device 005: ID 1199:0301 Sierra Wireless, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1199 Sierra Wireless, Inc. idProduct 0x0301 bcdDevice0.03 iManufacturer 1 iProduct2 iSerial 4 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 81 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 9 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 3 Endpoint Descriptor: bLength
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
Peter Hyman writes: > Linux Kernel: 3.9.10 > Device Driver: usb/serial/sierra.c > Device Driver version: not known > > Apparently Sierra has sold the AirCard 250U product to Netgear, so I am > sure driver development on drivers/usb/serial/sierra.c will be in limbo > for a period. While I am copying li...@sierrawireless.com, they will not > do anything since they don't own the product anymore. > > Nonetheless, I uncovered a problem when using the AC250U Aircard device > Vendor 0x1199, Product 0x0301. If the device is used in Windows and set > to 4G mode, using the device in Linux will fail to create the ppp0 > network interface. I could find no workaround. Even though the device > can be reached and modem commands sent, ppp0 won't be created. What exactly do you mean by "ppp0 won't be created"? The ppp interface is a virtual network device running on top of a serial port. Does this mean that there is one serial port missing? Or are all of them missing in this mode? Does this device support DirectIP, using the sierra_net driver? If so, does that still work in 4G mode? Exactly what action does the Windows driver/application do to trigger this? > I > regression tested this all the way back to kernel 3.2.29, and I also > tried the unpublished sierra driver 1.7.40 which works up to kernel > 3.4.x iirc. The issue is the same. > > The workaround is to set the device to 3G mode and then use in Linux. I > wrote this FAQ in case it is of interest. Nice. Thanks. Documenting the problem is important. But I believe we can do better. Making this device work regardless of mode and Windows settings should not be too difficult. We just need to research a bit what's going on, and then try to do the same as Windows to make it work. Could you start with sending the output of "lsusb -vd 1199:0301" for both the working (3G mode) and non-working (4G mode) cases? This will help understanding how the device appearance changes between these modes, if it does? If the device appears identical, then we have to know more details about how the ppp connection fails. Maybe the firmware just doesn't support PPP at all when it is in 4G mode? The lsusb output should still tell us whether to expect DirectIP, as Sierra use fixed interface numbers to indicate these things. Bjørn > = > FAQ: ppp0 Network Interface does not get created after plugging AirCard > 250U device when using Linux. No internet access is possible without the > ppp0 network interface. > > Answer: If the AC250U device is used in Windows, and is set to 4G mode > by the Sprint SmartView software, it MUST be set back to 3G mode prior > to use in Linux. The Linux Sierra driver does not support 4G and the > device won't be able to be initialized properly. It will be recognized > and you can send modem commands, but the ppp0 device won't be created. > Reset device to 3G under Windows and it will work fine in Linux. > = > > Maybe a nice feature request would be to check the 3G/4G status of the > device and reset to 3G since that is what is supported for now. If you > need additional information, please reach out. Happy to help. > > usb 4-1.2.2: New USB device found, idVendor=1199, idProduct=0301 > usb 4-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=4 > usb 4-1.2.2: Product: Sierra Wireless Device > usb 4-1.2.2: Manufacturer: Sierra Wireless, Incorporated > usb 4-1.2.2: SerialNumber: 4Vx«Ãïÿÿÿÿ > usbcore: registered new interface driver usbserial > usbcore: registered new interface driver usbserial_generic > usbserial: USB Serial support registered for generic > usbcore: registered new interface driver sierra > usbserial: USB Serial support registered for Sierra USB modem > sierra 4-1.2.2:1.0: Sierra USB modem converter detected > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB0 > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB1 > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB2 > usb 4-1.2.2: Sierra USB modem converter now attached to ttyUSB3 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I: Sierra.c USB Serial Driver FAQ/Feature Request
On Wed, Aug 14, 2013 at 11:43:37AM -0500, Peter Hyman wrote: > Linux Kernel: 3.9.10 > Device Driver: usb/serial/sierra.c > Device Driver version: not known > > Apparently Sierra has sold the AirCard 250U product to Netgear, so I am > sure driver development on drivers/usb/serial/sierra.c will be in limbo > for a period. While I am copying li...@sierrawireless.com, they will not > do anything since they don't own the product anymore. > > Nonetheless, I uncovered a problem when using the AC250U Aircard device > Vendor 0x1199, Product 0x0301. If the device is used in Windows and set > to 4G mode, using the device in Linux will fail to create the ppp0 > network interface. I could find no workaround. Even though the device > can be reached and modem commands sent, ppp0 won't be created. I > regression tested this all the way back to kernel 3.2.29, and I also > tried the unpublished sierra driver 1.7.40 which works up to kernel > 3.4.x iirc. The issue is the same. > > The workaround is to set the device to 3G mode and then use in Linux. I > wrote this FAQ in case it is of interest. How do you set the device to 3G mode? Can this be done in Linux using the latest version of modemmanager and networkmanager? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
