On Mon, Feb 6, 2017 at 5:10 AM, Adam Sherman <a...@sherman.ca> wrote: > On 2017-02-05 10:32 PM, matthew stanger wrote: >> First check to make sure you can get GPS location and not just 3gpp >> location, i.e. location from just the cell tower. > > Building on my previous message, I restarted the system to see how it > would come up without my intervention. Once the modem connected, for IP, > I started testing. > > First run: > > $ mmcli -m 0 --location-status > > /org/freedesktop/ModemManager1/Modem/0 > ---------------------------- > Location | capabilities: '3gpp-lac-ci' > | enabled: '3gpp-lac-ci' > | signals: 'yes' > > Also, note the ports listed: > > ------------------------- > System | device: '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4' > | drivers: 'qcserial, qmi_wwan' > | plugin: 'Generic' > | primary port: 'ttyUSB2' > | ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), wwp0s20u4i8 > (net)' > ------------------------- > > The primary port was cdc-wdm0 in my previous message. What is changing? > And I never seem to get the nice data I put in my previous messages. >
Looks like QMI probing failed and MM didn't grab the cdc-wdm port? > Relevant dmesg output: > > [ 29.480835] qcserial 3-4:1.0: Qualcomm USB modem converter detected > [ 29.481694] uvcvideo: Found UVC 1.00 device Integrated Camera (5986:02d2) > [ 29.482312] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB0 > [ 29.483366] qcserial 3-4:1.2: Qualcomm USB modem converter detected > [ 29.483447] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB1 > [ 29.483996] input: Integrated Camera as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input9 > [ 29.484064] usbcore: registered new interface driver uvcvideo > [ 29.484065] USB Video Class driver (1.1.1) > [ 29.484578] qcserial 3-4:1.3: Qualcomm USB modem converter detected > [ 29.484666] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB2 > [ 29.485952] qmi_wwan 3-4:1.8: cdc-wdm0: USB WDM device > [ 29.486078] qmi_wwan 3-4:1.8 wwan0: register 'qmi_wwan' at > usb-0000:00:14.0-4, WWAN/QMI device, 92:d8:61:f9:87:eb > [ 29.486118] usbcore: registered new interface driver qmi_wwan > > So, as an attempt and kicking the card and driver, I suspended the > system, then woke it up. > > Got a similar set of messages: > > [ 563.088465] usb 3-4: new high-speed USB device number 3 using xhci_hcd > [ 563.218244] usb 3-4: config 1 has an invalid interface number: 8 but > max is 3 > [ 563.218250] usb 3-4: config 1 has no interface number 1 > [ 563.219551] usb 3-4: New USB device found, idVendor=0f3d, idProduct=68a2 > [ 563.219556] usb 3-4: New USB device strings: Mfr=3, Product=2, > SerialNumber=0 > [ 563.219559] usb 3-4: Product: MC7700 > [ 563.219562] usb 3-4: Manufacturer: Sierra Wireless, Incorporated > [ 563.222019] qcserial 3-4:1.0: Qualcomm USB modem converter detected > [ 563.222221] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB0 > [ 563.222910] qcserial 3-4:1.2: Qualcomm USB modem converter detected > [ 563.223108] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB1 > [ 563.223953] qcserial 3-4:1.3: Qualcomm USB modem converter detected > [ 563.224119] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB2 > [ 563.225077] qmi_wwan 3-4:1.8: cdc-wdm0: USB WDM device > [ 563.225436] qmi_wwan 3-4:1.8 wwan0: register 'qmi_wwan' at > usb-0000:00:14.0-4, WWAN/QMI device, 92:d8:61:f9:87:eb > [ 563.248712] qmi_wwan 3-4:1.8 wwp0s20u4i8: renamed from wwan0 > > The modem is now index 1, and mmcli says its primary port is back to > cdc-wdm0. In addition, I got the fully loaded location capabilities back: > > $ mmcli -m 1 --location-status > > /org/freedesktop/ModemManager1/Modem/1 > ---------------------------- > Location | capabilities: '3gpp-lac-ci, gps-raw, gps-nmea, agps' > | enabled: '3gpp-lac-ci, gps-raw' > | signals: 'yes' > ---------------------------- > A-GPS | SUPL server: '栭獬瀮浮挳㜰捣㌰㈮灵戮㍧灰湥瑷潲欮潲机㜲㜵' > ---------------------------- > GPS | refresh rate: '30' > > However: > > $ mmcli -m 1 --location-get > > /org/freedesktop/ModemManager1/Modem/1 > ------------------------- > 3GPP location | Mobile country code: '302' > | Mobile network code: '720' > | Location area code: '59100' > | Cell ID: '1547052' > ------------------------- > GPS NMEA traces | Not available > ------------------------- > Raw GPS | Not available > ------------------------- > CDMA BS | Not available > $ mmcli -m 1 --location-enable-gps-nmea > successfully setup location gathering > $ mmcli -m 1 --location-get > > /org/freedesktop/ModemManager1/Modem/1 > ------------------------- > 3GPP location | Mobile country code: '302' > | Mobile network code: '720' > | Location area code: '59100' > | Cell ID: '1547052' > ------------------------- > GPS NMEA traces | $GPGGA,,,,,,0,,,,,,,,*66 > | $GPRMC,,V,,,,,,,,,,N*53 > | $GPGSA,A,1,,,,,,,,,,,,,,,*1E > | $GPGSV,4,1,16,20,,,,10,,,,02,,,,19,,,*72 > | $GPGSV,4,2,16,06,,,,28,,,,16,,,,26,,,*77 > | $GPGSV,4,3,16,13,,,,14,,,,25,,,,08,,,*71 > | $GPGSV,4,4,16,09,,,,21,,,,01,,,,32,,,*74 > | $GPVTG,,T,,M,,N,,K,N*2C > | $PQXFI,,,,,,,,,,*56 > ------------------------- > Raw GPS | Not available > ------------------------- > CDMA BS | Not available > > So I'm quite confused. > The GPS receiver didn't get a position fix yet, so even if you enable GPS raw source, it won't show anything until the fix is reported via NMEA traces ($GPGGA IIRC). -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel