| |
Activation Codes and Methods, Hardware Details, Sniffing
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 23 Apr 2013, 06:03
Hey guys. I just dropped a Novatel Expedite E371(Dell Wireless 5804, Qualcomm MDM9200 chipset) PCIe Mini Card in my dell latitude E6530. It's working great in windows but acting funky in Linux(Fedora 18). Network Manager is treating it as a wired(ethernet) device. I have no /dev/ttyUSBx devices listed either. I tried poking around with usb_modeswitch but it keeps whining at me. I just wanted to double check and see if this card even has a switch mode needed to operate properly. Here's some data:
Code: Select all Bus 002 Device 003: ID 413c:819b Dell Computer Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x413c Dell Computer Corp.
idProduct 0x819b
bcdDevice 0.00
iManufacturer 4 Novatel Wireless, Inc.
iProduct 3 Novatel Wireless HSPA
iSerial 5 012773000168391
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 254
bNumInterfaces 7
bConfigurationValue 1
iConfiguration 2 Novatel Configuration
bmAttributes 0xe0
Self 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 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 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 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 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 0x83 EP 3 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 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 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
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 32
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 0
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
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
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 0x86 EP 6 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 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 6
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 0
bFunctionProtocol 0
iFunction 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 6
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 0
CDC Header:
bcdCDC 1.10
CDC Ethernet:
iMacAddress 1 00A0C6000000
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1544
wNumberMCFilters 0x0001
bNumberPowerFilters 0
CDC Union:
bMasterInterface 6
bSlaveInterface 7
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 5
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 7
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 7
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 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 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
** UNRECOGNIZED: 2c ff 42 49 53 54 00 01 07 06 40 00 00 00 00 00 01 07 f4 01 02 08 f4 01 03 09 88 13 04 0a 10 27 05 0b 10 27 06 0c f4 01 07 0d f4 01
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Based on the Novatel entries in the device list I tried:
# usb_modeswitch -v 0x413c -p 0x819b -n -I -M "5553424312345678000000000000061b000000020000000000000000000000"
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 003 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using interface number 0
Error: can't use storage command in MessageContent with interface 0;
interface class is 239, should be 8. Aborting.
based on the error I presume this doesn't default to a "storage" mode and that my issue lies elsewhere? Just curious.
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 23 Apr 2013, 09:22
survient wrote:Hey guys. I just dropped a Novatel Expedite E371(Dell Wireless 5804, Qualcomm MDM9200 chipset) PCIe Mini Card in my dell latitude E6530. It's working great in windows but acting funky in Linux(Fedora 18). Network Manager is treating it as a wired(ethernet) device. I have no /dev/ttyUSBx devices listed either. I tried poking around with usb_modeswitch but it keeps whining at me. I just wanted to double check and see if this card even has a switch mode needed to operate properly. Here's some data:
PCIe modules does not have a cd-rom install mode so there is nothing you can do to the device with usb_modeswitch, it is already in a mode where it can be used.
The module is an ethernet device and not a serial modem, Windows does also use it as such.
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 23 Apr 2013, 15:56
I was able to get it working with this article:
http://ubuntuforums.org/showthread.php?t=1969322
I had to run:
# modprobe option
# echo 413c 819b > /sys/bus/usb-serial/drivers/option1/new_id
# systemctl restart NetworkManager.service
Obviously it doesn't work on reboot but since this is a situationally used device that I'd need to turn on anyway, it's not that big of a deal aside from getting things fixed upstream. I believe it's just not being picked up due to an unrecognized product ID.
Thanks for the help LOM
-
bmork
- Posts: 167
- Joined: 15 Mar 2012, 22:47
- Location: Oslo, Norway
Post
by bmork » 23 Apr 2013, 22:24
survient wrote:I was able to get it working with this article:
http://ubuntuforums.org/showthread.php?t=1969322
I had to run:
# modprobe option
# echo 413c 819b > /sys/bus/usb-serial/drivers/option1/new_id
# systemctl restart NetworkManager.service
Obviously it doesn't work on reboot but since this is a situationally used device that I'd need to turn on anyway, it's not that big of a deal aside from getting things fixed upstream. I believe it's just not being picked up due to an unrecognized product ID.
Yes, that's correct. And easily fixable.
But I wonder a bit about the CDC ethernet interface here. Dan W has an E362 (which I believe is pretty much the same card with a MDM9600 chipset), and he has moved support for that from cdc_ether to qmi_wwan to enable using QMI on it. See the following commits:
https://git.kernel.org/cgit/linux/kerne ... 3ea9320755
https://git.kernel.org/cgit/linux/kerne ... 06e19b9d4c
https://git.kernel.org/cgit/linux/kerne ... 5c754b7f95
I expect the E371 also support QMI on that interface. If you feel like playing with it, you could unbind the cdc_ether driver temporarily and replace it with qmi_wwan. Something like this should do:
Find the device name of the USB interface (the part matching the *:1.6):
Code: Select all ls -l /sys/bus/usb/drivers/cdc_ether/*:1.6
Unbind it from cdc_ether (I'm using x-y:1.6 only as example here - you need to use the result from above), and then bind it to qmi_wwan instead:
Code: Select all echo x-y:1.6 > /sys/bus/usb/drivers/cdc_ether/unbind
echo x-y:1.6 > /sys/bus/usb/drivers/qmi_wwan/bind
The resulting wwanX interface should work identical to the cdc_ether one, but you will now also have a /dev/cdc-wdmX device which I assume will accept QMI commands. Use e.g. libqmi to test it.
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 23 Apr 2013, 22:33
I'm fairly new to messing with these devices. Would QMI offer me any benefit over my existing connection?
-
bmork
- Posts: 167
- Joined: 15 Mar 2012, 22:47
- Location: Oslo, Norway
Post
by bmork » 23 Apr 2013, 22:41
survient wrote:I'm fairly new to messing with these devices. Would QMI offer me any benefit over my existing connection?
Maybe. Maybe not. That depends entirely on how well it works using AT commands. I have no first hand experience with Novatel cards.
Using the network device instead of PPP is definitely preferred. Processing PPP packets is inefficient, and the modem is not likely to be able to do that at full LTE speed. QMI will let you configure and manage the connection for the network device. I am guessing that this is what your windows drivers do.
But some vendors also implement vendor specific AT commands for managing the nework device. If Novatel has done this, and it works, then there is little benefit in QMI. Except maybe ModemManager support. I haven't checked, but given the driver patches from Dan W I expect he also has added MM support for these cards using QMI.
And then there is the fun of exploring these things, of course 
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 25 Apr 2013, 03:21
Ok so I decided to take bmork's advice and play around with QMI but I'm still having a few issues.
The good news is I was having issues in Windows land in that I was only getting HSPA+ speeds and not LTE which the card is capable of, but after a long chat with the AT&T rep we were able to get it squared away(The IMEI for the card wasn't being picked up as an LTE device so they just temporarily used another IMEI to trick it into thinking my device is a "supported" LTE device) so now I am definitely getting LTE speeds in windows.
In linux I tried the same thing with just the raw "option" driver but it gave me an error every time I tried "Use only 4G (LTE)" or "Prefer 4G (LTE)". I can connect to HSPA+ just fine though with the option driver.
I followed some of bmork's advice but the raw commands he gave me weren't working; I had to modify them slightly:
modprobe qmi_wwan
echo 2-1.6:1.6 > /sys/bus/usb/drivers/cdc_ether/unbind
echo 413c 819b > /sys/bus/usb/drivers/qmi_wwan/new_id
the output I got was:
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I: If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan
No new modem device was detected by network manager at this point so I tried loading the "option" driver again the same way I usually do:
modprobe option
echo 413c 819b > /sys/bus/usb-serial/drivers/option1/new_id
systemctl restart NetworkManager.service
and I get:
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I: If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan
but the same symptoms as before. I can connect to 3G speeds but not 4G modes(gives an error). Here's /var/log/message chunks, first after a failed connection(4G), and second is a successful connection(3G):
FAILURE
Apr 24 18:53:00 philo NetworkManager[4112]: <info> Activation (ttyUSB0) starting connection 'AT&T LaptopConnect (data cards)'
Apr 24 18:53:00 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 18:53:00 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 24 18:53:00 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Apr 24 18:53:00 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Apr 24 18:53:00 philo NetworkManager[4112]: <warn> GSM connection failed: (32) Invalid allowed mode 0
Apr 24 18:53:00 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Apr 24 18:53:00 philo NetworkManager[4112]: <warn> Activation (ttyUSB0) failed for connection 'AT&T LaptopConnect (data cards)'
Apr 24 18:53:00 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 24 18:53:00 philo NetworkManager[4112]: <info> (ttyUSB0): deactivating device (reason 'none') [0]
Apr 24 18:53:00 philo NetworkManager[4112]: <warn> (ttyUSB0) firewall zone remove failed: (32) UNKNOWN_INTERFACE: ttyUSB0
SUCCESSFUL
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) starting connection 'AT&T LaptopConnect (data cards)'
Apr 24 18:53:21 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Apr 24 18:53:21 philo dbus-daemon[691]: modem-manager[964]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting)
Apr 24 18:53:21 philo modem-manager[964]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting)
Apr 24 18:53:21 philo dbus-daemon[691]: modem-manager[964]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected)
Apr 24 18:53:21 philo modem-manager[964]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected)
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful.
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete.
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 24 18:53:21 philo NetworkManager[4112]: <info> starting PPP connection
Apr 24 18:53:21 philo NetworkManager[4112]: <info> pppd started with pid 4456
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete.
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Apr 24 18:53:21 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Apr 24 18:53:21 philo pppd[4456]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Apr 24 18:53:21 philo NetworkManager[4112]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Apr 24 18:53:21 philo kernel: [ 648.028791] PPP generic driver version 2.4.2
Apr 24 18:53:21 philo pppd[4456]: pppd 2.4.5 started by root, uid 0
Apr 24 18:53:21 philo pppd[4456]: Using interface ppp0
Apr 24 18:53:21 philo pppd[4456]: Connect: ppp0 <--> /dev/ttyUSB0
Apr 24 18:53:21 philo NetworkManager[4112]: Using interface ppp0
Apr 24 18:53:21 philo NetworkManager[4112]: Connect: ppp0 <--> /dev/ttyUSB0
Apr 24 18:53:21 philo NetworkManager[4112]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
Apr 24 18:53:21 philo pppd[4456]: CHAP authentication succeeded
Apr 24 18:53:21 philo pppd[4456]: CHAP authentication succeeded
Apr 24 18:53:21 philo NetworkManager[4112]: CHAP authentication succeeded
Apr 24 18:53:21 philo NetworkManager[4112]: CHAP authentication succeeded
Apr 24 18:53:21 philo kernel: [ 648.059937] PPP BSD Compression module registered
Apr 24 18:53:21 philo kernel: [ 648.067962] PPP Deflate Compression module registered
Apr 24 18:53:22 philo pppd[4456]: Could not determine remote IP address: defaulting to 10.64.64.64
Apr 24 18:53:22 philo pppd[4456]: local IP address 10.150.253.232
Apr 24 18:53:22 philo pppd[4456]: remote IP address 10.64.64.64
Apr 24 18:53:22 philo pppd[4456]: primary DNS address 172.26.38.1
Apr 24 18:53:22 philo pppd[4456]: secondary DNS address 172.26.38.2
Apr 24 18:53:22 philo NetworkManager[4112]: <info> PPP manager(IP Config Get) reply received.
Apr 24 18:53:22 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 24 18:53:22 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 5 of 5 (IPv4 Commit) started...
Apr 24 18:53:22 philo NetworkManager[4112]: Could not determine remote IP address: defaulting to 10.64.64.64
Apr 24 18:53:22 philo NetworkManager[4112]: local IP address 10.150.253.232
Apr 24 18:53:22 philo NetworkManager[4112]: remote IP address 10.64.64.64
Apr 24 18:53:22 philo NetworkManager[4112]: primary DNS address 172.26.38.1
Apr 24 18:53:22 philo NetworkManager[4112]: secondary DNS address 172.26.38.2
Apr 24 18:53:23 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Apr 24 18:53:23 philo NetworkManager[4112]: <info> Activation (ttyUSB0) Stage 5 of 5 (IPv4 Commit) complete.
Apr 24 18:53:23 philo NetworkManager[4112]: <info> (ttyUSB0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 24 18:53:23 philo NetworkManager[4112]: <info> Policy set 'AT&T LaptopConnect (data cards)' (ppp0) as default for IPv4 routing and DNS.
Apr 24 18:53:23 philo NetworkManager[4112]: <info> Activation (ttyUSB0) successful, device activated.
Apr 24 18:53:23 philo dbus-daemon[691]: dbus[691]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 24 18:53:23 philo dbus[691]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 24 18:53:23 philo dbus-daemon[691]: dbus[691]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 24 18:53:23 philo dbus[691]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 24 18:53:23 philo systemd[1]: Starting LSB: Starts and stops login and scanning of iSCSI devices....
Apr 24 18:53:23 philo iscsi[4494]: Starting iscsi: iscsiadm: No records found
Apr 24 18:53:23 philo iscsi[4494]: [ OK ]
Apr 24 18:53:23 philo systemd[1]: Started LSB: Starts and stops login and scanning of iSCSI devices..
Apr 24 18:53:23 philo dbus-daemon[691]: Starting iscsi (via systemctl): [ OK ]
Apr 24 18:53:23 philo systemd[1]: Stopping Sendmail Mail Transport Client...
Apr 24 18:53:23 philo systemd[1]: Stopping Sendmail Mail Transport Agent...
Apr 24 18:53:23 philo systemd[1]: Starting Sendmail Mail Transport Agent...
Apr 24 18:53:24 philo systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Apr 24 18:53:26 philo nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/10-sendmail' took too long; killing it.
Apr 24 18:53:26 philo chronyd[745]: Source 10.6.92.88 online
Apr 24 18:53:26 philo chronyd[745]: Source 10.6.92.89 online
Apr 24 18:53:26 philo chronyd[745]: Source 204.235.61.9 online
Apr 24 18:53:26 philo chronyd[745]: Source 38.101.77.21 online
Apr 24 18:53:26 philo chronyd[745]: Source 199.7.177.206 online
Apr 24 18:53:26 philo chronyd[745]: Source 149.20.68.17 online
Apr 24 18:53:26 philo NetworkManager[4112]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/10-sendmail' timed out.
when I unbind all the drivers and try to load cdc_wdm it doesn't want to stick to any of the devices, just gives me a "device not found" error:
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I: If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan
[root@philo ~]# echo 2-1.6:1.0 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.1 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.2 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.3 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.4 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
Any guidance on this point would be appreciated.
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 25 Apr 2013, 05:06
ok so the idea that cdc_wdm didn't want to bind to anything wasn't entirely true. I unbinded all drivers to each component and then ran:
echo 413c 819b > /sys/bus/usb/drivers/cdc_wdm/new_id
and usb-devices shows
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_wdm
I: If#= 7 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)
so it did latch on to something, and 2 new cdc-wdm devices appeared in /dev:
[root@philo ~]# ls /dev/cdc-wdm*
/dev/cdc-wdm0 /dev/cdc-wdm1
The same result can be seen when I load qmi_wwan, but devices 2-1.6:1.1 through 2-1.6:1.4 are still empty. I tried various combinations of loading drivers and here are the ones that successfully load on which module:
2-1.6:1.0 option qmi_wwan
2-1.6:1.1 option
2-1.6:1.2 option
2-1.6:1.3 option
2-1.6:1.4 option
2-1.6:1.6 option? cdc_ether qmi_wwan cdc_wdm
2-1.6:1.7 option cdc_ether qmi_wwan
each combination has failed to connect to LTE as far as I can tell, I may have missed a certain combination though. I put option? like that on 1.6 because I unbound all the ids and tried to do a mass load of the option driver which caused my whole laptop to crash; I'm not sure what option was trying to do but it obviously wasn't designed to handle that network device, though it acts fine when it is running the 1.7 device combined with cdc_wdm,
Thoughts?
-
bmork
- Posts: 167
- Joined: 15 Mar 2012, 22:47
- Location: Oslo, Norway
Post
by bmork » 25 Apr 2013, 10:46
survient wrote:I followed some of bmork's advice but the raw commands he gave me weren't working; I had to modify them slightly:
modprobe qmi_wwan
Yeah, right. I forgot that....
echo 2-1.6:1.6 > /sys/bus/usb/drivers/cdc_ether/unbind
echo 413c 819b > /sys/bus/usb/drivers/qmi_wwan/new_id
the output I got was:
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
It binds to if #0 because there are enough endpoints there. But this is a serial port, so this won't work. Doesn't matter much as long as you test the other wwanX/cdc-wdmX instance.
You would have avoided this if you had loaded the option driver before doing the unbind/bind of the network drivers.
Apr 24 18:53:00 philo NetworkManager[4112]: <info> Activation (ttyUSB0) starting connection 'AT&T LaptopConnect (data cards)'
Using NetworkManager here means really old software. At least when it comes to QMI support, which has all been written during the last year or so.
You need an extremely new and unreleased ModemManager to get the QMI support there. And because this also changes the API, you need an equally new NetworkManager if you want to have the modem available there.
Or you could just play with the qmicli tool included with libqmi of you don't want to mess with your NM/MM setup. Less work for a simple test.
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I: If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan
[root@philo ~]# echo 2-1.6:1.0 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.1 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.2 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.3 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
[root@philo ~]# echo 2-1.6:1.4 > /sys/bus/usb/drivers/cdc_wdm/bind
-bash: echo: write error: No such device
Any guidance on this point would be appreciated.
cdc_wdm as a standalone driver will not bind to any interface with more (or less) than a single interrupt enpoint. So the only possible one is if#6.
But doing this will be the exact same as letting qmi_wwan bind to that interface, excect that you won't have any wwanX network device. qmi_wwan use the cdc_wdm driver to provide the /dev/cdc-wdmX device. If#6 is really handled by cdc_wdm even if qmi_wwan shows up as the driver for both interfaces.
-
bmork
- Posts: 167
- Joined: 15 Mar 2012, 22:47
- Location: Oslo, Norway
Post
by bmork » 25 Apr 2013, 11:01
survient wrote:C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_wdm
I: If#= 7 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)
so it did latch on to something, and 2 new cdc-wdm devices appeared in /dev:
[root@philo ~]# ls /dev/cdc-wdm*
/dev/cdc-wdm0 /dev/cdc-wdm1
Two? The usb-devices output above shows only one interface handled by cdc_wdm (and as I said, that's the only possible one). Where did the other come from? Did yoy maybe bind qmi_wwan to if#0?
The same result can be seen when I load qmi_wwan, but devices 2-1.6:1.1 through 2-1.6:1.4 are still empty. I tried various combinations of loading drivers and here are the ones that successfully load on which module:
2-1.6:1.0 option qmi_wwan
2-1.6:1.1 option
2-1.6:1.2 option
2-1.6:1.3 option
2-1.6:1.4 option
2-1.6:1.6 option? cdc_ether qmi_wwan cdc_wdm
2-1.6:1.7 option cdc_ether qmi_wwan
Yes. This doesn't really tell you much. The option and qmi_wwan drivers are made for vendor specific functions and will therefore not do much class based filtering. They each contain a long list of supported devices, by ID and interface numbers. When you add dynamic IDs, they will just try to bind to any interface not already bound. The option driver will succeed as long as there are at least two bulk endpoints. The qmi_wwan driver needs an additional interrupt endpoint.
So the option driver can bind to interface #7, but it won't work (that's not a serial function), and the qmi_wwan driver can bind to interface #0, but it won't work (that's not a network function).
The cdc_ether driver will only bind to CDC ECM class interfaces having a number of required CDC functional descriptors. It doesn't need device IDs. And in fact, trying to add one using "new_id" will result in that entry being treated as a blacklist (but I guess that doesn't matter because the built-in entries are evaluated before the dynamic entries).
each combination has failed to connect to LTE as far as I can tell, I may have missed a certain combination though. I put option? like that on 1.6 because I unbound all the ids and tried to do a mass load of the option driver which caused my whole laptop to crash; I'm not sure what option was trying to do but it obviously wasn't designed to handle that network device, though it acts fine when it is running the 1.7 device combined with cdc_wdm,
Thoughts?
The only driver combinations which makes sense to test is either cdc_ether or qmi_wwan handling interfaces 6 and 7, and option handling the rest.
I don't think any of this should affect your ability to attach to a LTE network. That should really work with PPP as well.
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 25 Apr 2013, 14:37
Right, after doing more reading I discovered the lack of QMI support in my current version of NetworkManager; this whole time I've been using that to test this setup but it's just been trying to do a PPP connection but failing when I pushed LTE. I think if I custom compiled NetworkManager I'd start seeing a different result.
I played around with it a bit more last night with qmi_wwan in if 0, 6 , 7 with libqmi commands which seemed to get a bit further. It was able to "connect" to the network but the wwan interface(s) wwan0(fake serial from if 0) and wwan1(the real one from 6, 7) weren't allowing me to bring them up. I'm going to do further testing when I'm in the office with "option" taking ifs 0-4 and qmi_wwan handling 6 & 7. I may still have to custom compile the latest NetworkManager and it's associated pieces to get the wwanX interface to behave.
Thanks for the heads up bmork
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 27 Apr 2013, 00:00
Ok so I poked about a bit more and was able to hit LTE with option on 0-4 and qmi_wwan on 6-7. I had a cdc-wdm0 and a wwan0 device:
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I: If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan
I was able to use qmi-network start and then ifup wwan0 and get a connection just fine. NetworkManager that comes stock with Fedora 18 doesn't understand QMI so this is just from the command line. I'm going to poke a bit more with custom compiling a newer version of NetworkManager to see if I can get it to manage the card.
Thanks for the help bmork
-
bmork
- Posts: 167
- Joined: 15 Mar 2012, 22:47
- Location: Oslo, Norway
Post
by bmork » 27 Apr 2013, 17:18
survient wrote:Ok so I poked about a bit more and was able to hit LTE with option on 0-4 and qmi_wwan on 6-7. I had a cdc-wdm0 and a wwan0 device:
T: Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=819b Rev=00.00
S: Manufacturer=Novatel Wireless, Inc.
S: Product=Novatel Wireless HSPA
S: SerialNumber=012773000168391
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I: If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan
Yes, that looks right.
I was able to use qmi-network start and then ifup wwan0 and get a connection just fine. NetworkManager that comes stock with Fedora 18 doesn't understand QMI so this is just from the command line.
It's been a while since the last ModemManager release. I assume Fedora, and many other distributions, will start shipping MM with QMI support as soon as there is a new release.
I'm going to poke a bit more with custom compiling a newer version of NetworkManager to see if I can get it to manage the card.
Thanks for the help bmork
Thank you for testing this!
I'll submit a patch to change this module from cdc_ether to qmi_wwan, just like the E362. But does anyone know the USB ID of the Novatel branded module? I would prefer to change both at the same time. Anything else would just be confusing.
-
survient
- Posts: 23
- Joined: 23 Apr 2013, 05:56
Post
by survient » 27 Apr 2013, 18:11
I'm not sure what you mean. Would I be able to pull that or are you referring to a different device?
-
bmork
- Posts: 167
- Joined: 15 Mar 2012, 22:47
- Location: Oslo, Norway
Post
by bmork » 27 Apr 2013, 19:58
survient wrote:I'm not sure what you mean. Would I be able to pull that or are you referring to a different device?
A different device. Or really the same device, but with a different USB device ID.
The one you got has a Dell ID. Just like the E362, which also exists as a "Dell 5800", I assume the E371 is sold both with a Novatel device ID and branding as well as the version you've got.
But if I cannot dig up that ID, then I'll just add the one you provided with a comment.
|
|
