AW: AW: AW: h5321gw Problem with --location-get
:00:00:01:02:00:A8:05 ModemManager[2166]: [/dev/cdc-wdm0] Received message (translated)... >>>>>> QMUX: >>>>>> length = 24 >>>>>> flags = 0x80 >>>>>> service = "nas" >>>>>> client = 2 >>>>>> QMI: >>>>>> flags = "response" >>>>>> transaction = 14 >>>>>> tlv_length = 12 >>>>>> message = "Get Signal Strength" (0x0020) >>>>>> TLV: >>>>>> type = "Result" (0x02) >>>>>> length = 4 >>>>>> value = 00:00:00:00 >>>>>> translated = SUCCESS >>>>>> TLV: >>>>>> type = "Signal Strength" (0x01) >>>>>> length = 2 >>>>>> value = A8:05 >>>>>> translated = [ strength = '-88' radio_interface = 'umts' ] ModemManager[2166]: [1491216594.290310] [mm-broadband-modem-qmi.c:2337] signal_strength_get_quality_and_access_tech(): Signal strength (umts): -88 dBm ModemManager[2166]: [1491216594.290357] [mm-broadband-modem-qmi.c:2370] signal_strength_get_quality_and_access_tech(): Signal strength: -88 dBm --> 41% ModemManager[2166]: [1491216594.290508] [mm-iface-modem.c:1165] update_signal_quality(): Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (41) ModemManager[2166]: [1491216624.305711] [mm-broadband-modem-qmi.c:2447] load_signal_quality(): loading signal quality... ModemManager[2166]: [/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 13 <<<<<< data = 01:0C:00:00:03:02:00:0F:00:20:00:00:00 ModemManager[2166]: [/dev/cdc-wdm0] Sent message (translated)... <<<<<< QMUX: <<<<<< length = 12 <<<<<< flags = 0x00 <<<<<< service = "nas" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "none" <<<<<< transaction = 15 <<<<<< tlv_length = 0 <<<<<< message = "Get Signal Strength" (0x0020) ModemManager[2166]: [/dev/cdc-wdm0] Received message... >>>>>> RAW: >>>>>> length = 25 >>>>>> data = >>>>>> 01:18:00:80:03:02:02:0F:00:20:00:0C:00:02:04:00:00:00:00:00:01:02:00:AB:05 ModemManager[2166]: [/dev/cdc-wdm0] Received message (translated)... >>>>>> QMUX: >>>>>> length = 24 >>>>>> flags = 0x80 >>>>>> service = "nas" >>>>>> client = 2 >>>>>> QMI: >>>>>> flags = "response" >>>>>> transaction = 15 >>>>>> tlv_length = 12 >>>>>> message = "Get Signal Strength" (0x0020) >>>>>> TLV: >>>>>> type = "Result" (0x02) >>>>>> length = 4 >>>>>> value = 00:00:00:00 >>>>>> translated = SUCCESS >>>>>> TLV: >>>>>> type = "Signal Strength" (0x01) >>>>>> length = 2 >>>>>> value = AB:05 >>>>>> translated = [ strength = '-85' radio_interface = 'umts' ] ModemManager[2166]: [1491216624.311323] [mm-broadband-modem-qmi.c:2337] signal_strength_get_quality_and_access_tech(): Signal strength (umts): -85 dBm ModemManager[2166]: [1491216624.311906] [mm-broadband-modem-qmi.c:2370] signal_strength_get_quality_and_access_tech(): Signal strength: -85 dBm --> 46% ModemManager[2166]: [1491216624.312588] [mm-iface-modem.c:1165] update_signal_quality(): Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (46) ModemManager[2166]: [1491216654.279275] [mm-broadband-modem-qmi.c:2447] load_signal_quality(): loading signal quality... ModemManager[2166]: [/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 13 <<<<<< data = 01:0C:00:00:03:02:00:10:00:20:00:00:00 ModemManager[2166]: [/dev/cdc-wdm0] Sent message (translated)... <<<<<< QMUX: <<<<<< length = 12 <<<<<< flags = 0x00 <<<<<< service = "nas" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "none" <<<<<< transaction = 16 <<<<<< tlv_length = 0 <
AW: AW: h5321gw Problem with --location-get
I will check this today. I tried a MC 7710 as well same problem --location-status gives that 3g location is enabled when I try --location-get I get not available. Does the MC 7710 have the same problem as the Ericsson one? -Ursprüngliche Nachricht- Von: Aleksander Morgado [mailto:aleksan...@aleksander.es] Gesendet: Donnerstag, 23. März 2017 13:01 An: Thomas Lang ; Dan Williams ; ModemManager (development) Betreff: Re: AW: h5321gw Problem with --location-get On 23/03/17 08:47, Thomas Lang wrote: > Hmm. I tried at+CREG? To get the CellInfo. But I the response is empty. In > the Debug the info is present: > > ModemManager[3184]: [1490255043.880383] > [mm-port-serial.c:1237] mm_port_serial_open(): (cdc-wdm2) device open > count is 2 (open) > ModemManager[3184]: [1490255043.880449] [mm-port-serial-at.c:440] > debug_log(): (cdc-wdm2): --> 'AT+CREG?' > ModemManager[3184]: [1490255043.917955] [mm-port-serial-at.c:440] > debug_log(): (cdc-wdm2): <-- '+CREG: > 2,1,"03B9","0EAD5D18",2OK' > ModemManager[3184]: [1490255043.918155] > [mm-port-serial.c:1294] _close_internal(): (cdc-wdm2) device open > count is 1 (close) > > Can I use the mmcli -m 0 --commnad=+CREG? That is expected, because the response is processed by the unsolicited message handlers, so you just get an empty string as return. Do you see any 3GPP location info reported by mmcli --location-get-3gpp after having sent +CREG with --command? -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: h5321gw Problem with --location-get
Hmm. I tried at+CREG? To get the CellInfo. But I the response is empty. In the Debug the info is present: ModemManager[3184]: [1490255043.880383] [mm-port-serial.c:1237] mm_port_serial_open(): (cdc-wdm2) device open count is 2 (open) ModemManager[3184]: [1490255043.880449] [mm-port-serial-at.c:440] debug_log(): (cdc-wdm2): --> 'AT+CREG?' ModemManager[3184]: [1490255043.917955] [mm-port-serial-at.c:440] debug_log(): (cdc-wdm2): <-- '+CREG: 2,1,"03B9","0EAD5D18",2OK' ModemManager[3184]: [1490255043.918155] [mm-port-serial.c:1294] _close_internal(): (cdc-wdm2) device open count is 1 (close) Can I use the mmcli -m 0 --commnad=+CREG? Thomas On Wed, 2017-03-22 at 22:14 -0500, Dan Williams wrote: > On Wed, 2017-03-22 at 20:34 +, Thomas Lang wrote: > > Hi, > > I'm trying to get the cellId info from an Ericsson module. I'm using > > the modemmanager version 1.6.4. > > What firmware version? > > Is the firmware MBIM-mode or AT-mode? I updated my HS2350 (rebranded h5321gw) to MBIM-enabled firmware R3C11 and tested it out. The MBIM protocol does not give ModemManager the LAC/CI at all, so MM can't actually tell you any of that. And it's a bug in ModemManager that it says MBIM devices actually have 3gpp-lac-ci capability; that should be removed. In the case of the Ericsson devices though, they still present an AT port, so it's possible we could get that information via the AT port while still controlling the modem with MBIM. Unfortunately though, that's not implemented. If you can manage to flash it back to R1D08 or whatever is the pre-MBIM firmware, it'll get used as a normal "MBM" modem and that would allow LAC/CI presentation. Dan > Dan > > > tactilo@VirtualBox001:~$ mmcli -m 0 --location-status > > > > /org/freedesktop/ModemManager1/Modem/0 > > > > Location | capabilities: '3gpp-lac-ci' > > |enabled: '3gpp-lac-ci' > > |signals: 'no' > > tactilo@VirtualBox001:~$ mmcli -m 0 --location-get > > > > /org/freedesktop/ModemManager1/Modem/0 > > - > > 3GPP location | Not available > > - > > GPS NMEA traces | Not available > > - > > Raw GPS | Not available > > - > > CDMA BS | Not available > > > > As you can see from the logs the status says 3gpp-lac-ci is > > supported and enabled but the location-get function response with > > not available. > > How can I get the 3gpp location? > > Kind regards, > > Thomas > > > > ___ > > ModemManager-devel mailing list > > ModemManager-devel@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel > > ___ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: h5321gw Problem with --location-get
Hi Dan, please see: - Hardware | manufacturer: 'Ericsson MBM' | model: 'MBIM [0BDB:1926]' | revision: 'R3C11 (Pro), R4D04 (App)' | supported: 'gsm-umts' |current: 'gsm-umts' | equipment id: '' - System | device: '/sys/devices/pci:00/:00:0b.0/usb1/1-1' |drivers: 'cdc_wdm, cdc_acm, cdc_mbim' | plugin: 'Ericsson MBM' | primary port: 'cdc-wdm2' | ports: 'wwp0s11u1i6 (net), ttyACM0 (at), cdc-wdm2 (mbim), ttyACM1 (at), ttyACM2 (gps)' Thomas -Ursprüngliche Nachricht- Von: Dan Williams [mailto:d...@redhat.com] Gesendet: Donnerstag, 23. März 2017 04:14 An: Thomas Lang ; ModemManager (development) Betreff: Re: h5321gw Problem with --location-get On Wed, 2017-03-22 at 20:34 +, Thomas Lang wrote: > Hi, > I'm trying to get the cellId info from an Ericsson module. I'm using > the modemmanager version 1.6.4. What firmware version? Is the firmware MBIM-mode or AT-mode? Dan > tactilo@VirtualBox001:~$ mmcli -m 0 --location-status > > /org/freedesktop/ModemManager1/Modem/0 > > Location | capabilities: '3gpp-lac-ci' > |enabled: '3gpp-lac-ci' > |signals: 'no' > tactilo@VirtualBox001:~$ mmcli -m 0 --location-get > > /org/freedesktop/ModemManager1/Modem/0 > - > 3GPP location | Not available > - > GPS NMEA traces | Not available > - > Raw GPS | Not available > - > CDMA BS | Not available > > As you can see from the logs the status says 3gpp-lac-ci is supported > and enabled but the location-get function response with not available. > How can I get the 3gpp location? > Kind regards, > Thomas > > ___ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
h5321gw Problem with --location-get
Hi, I'm trying to get the cellId info from an Ericsson module. I'm using the modemmanager version 1.6.4. tactilo@VirtualBox001:~$ mmcli -m 0 --location-status /org/freedesktop/ModemManager1/Modem/0 Location | capabilities: '3gpp-lac-ci' |enabled: '3gpp-lac-ci' |signals: 'no' tactilo@VirtualBox001:~$ mmcli -m 0 --location-get /org/freedesktop/ModemManager1/Modem/0 - 3GPP location | Not available - GPS NMEA traces | Not available - Raw GPS | Not available - CDMA BS | Not available As you can see from the logs the status says 3gpp-lac-ci is supported and enabled but the location-get function response with not available. How can I get the 3gpp location? Kind regards, Thomas ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: AW: MC7455 not listed as usb device any more after reboot
using ehci-pci [ 482.338995] usb 1-1: New USB device found, idVendor=0438, idProduct=7900 [ 482.339004] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 482.340410] hub 1-1:1.0: USB hub found [ 482.340597] hub 1-1:1.0: 4 ports detected [ 482.638000] usb 1-1.3: new high-speed USB device number 3 using ehci-pci [ 482.749626] usb 1-1.3: config 1 has an invalid interface number: 8 but max is 4 [ 482.749649] usb 1-1.3: config 1 has an invalid interface number: 10 but max is 4 [ 482.749658] usb 1-1.3: config 1 has no interface number 1 [ 482.749664] usb 1-1.3: config 1 has no interface number 4 [ 482.757858] usb 1-1.3: New USB device found, idVendor=1199, idProduct=9071 [ 482.757866] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 482.757873] usb 1-1.3: Product: Sierra Wireless MC7455 Qualcomm® Snapdragon™ X7 LTE-A [ 482.757880] usb 1-1.3: Manufacturer: Sierra Wireless, Incorporated [ 482.757886] usb 1-1.3: SerialNumber: LQ61620344021006 [ 482.765172] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected [ 482.765591] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0 [ 482.767049] qcserial 1-1.3:1.2: Qualcomm USB modem converter detected [ 482.767338] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB1 [ 482.768308] qcserial 1-1.3:1.3: Qualcomm USB modem converter detected [ 482.768641] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB2 [ 482.769810] qmi_wwan 1-1.3:1.8: cdc-wdm0: USB WDM device [ 482.771427] qmi_wwan 1-1.3:1.8 wwan0: register 'qmi_wwan' at usb-:00:13.0-1.3, WWAN/QMI device, 52:bb:8a:5e:bc:e4 [ 482.773220] qmi_wwan 1-1.3:1.10: cdc-wdm1: USB WDM device [ 482.774975] qmi_wwan 1-1.3:1.10 wwan1: register 'qmi_wwan' at usb-:00:13.0-1.3, WWAN/QMI device, 52:bb:8a:5e:bc:e4 [ 482.832446] qmi_wwan 1-1.3:1.10 wwp0s19u1u3i10: renamed from wwan1 [ 482.851723] qmi_wwan 1-1.3:1.8 wwp0s19u1u3i8: renamed from wwan0 Everything is fine. After reboot: [ 63.933614] ehci-pci :00:13.0: remove, state 4 [ 63.933678] usb usb3: USB disconnect, device number 1 [ 63.933686] usb 3-1: USB disconnect, device number 2 [ 63.935744] ehci-pci :00:13.0: USB bus 3 deregistered [ 86.540041] ehci-pci: EHCI PCI platform driver [ 86.540551] ehci-pci :00:13.0: EHCI Host Controller [ 86.540577] ehci-pci :00:13.0: new USB bus registered, assigned bus number 3 [ 86.540595] ehci-pci :00:13.0: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [ 86.540613] ehci-pci :00:13.0: debug port 2 [ 86.540698] ehci-pci :00:13.0: irq 18, io mem 0xfeb25400 [ 86.549905] ehci-pci :00:13.0: USB 2.0 started, EHCI 1.00 [ 86.550216] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 86.550225] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 86.550232] usb usb3: Product: EHCI Host Controller [ 86.550238] usb usb3: Manufacturer: Linux 4.6.2-040602-generic ehci_hcd [ 86.550244] usb usb3: SerialNumber: :00:13.0 [ 86.550930] hub 3-0:1.0: USB hub found [ 86.550959] hub 3-0:1.0: 2 ports detected [ 86.861905] usb 3-1: new high-speed USB device number 2 using ehci-pci [ 86.994337] usb 3-1: New USB device found, idVendor=0438, idProduct=7900 [ 86.994346] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 86.995750] hub 3-1:1.0: USB hub found [ 86.995929] hub 3-1:1.0: 4 ports detected Nothing the modem is not detected. I came up with a workaround which currently work but is perhaps not the solution for the problem. I do an at!reset to the modem and do a reboot right after it. In this way the modem is detected and working after reboot. Could it be that the modem is put in LPM mode and is not powered on again? Thomas -Ursprüngliche Nachricht- Von: Dan Williams [mailto:d...@redhat.com] Gesendet: Montag, 20. März 2017 22:16 An: Thomas Lang ; ModemManager (development) Betreff: Re: AW: MC7455 not listed as usb device any more after reboot On Mon, 2017-03-20 at 09:45 +, Thomas Lang wrote: > Hi Dan, > thanks for your comments. > I have included a trace of the working start and the reboot. I > noticed that in the reboot case the usb 3-1.3 device is not detected > anymore. The usb 3-1 is an ehci-pci. Would it help to reset the ehci- > pci? And if so how would I do this. If you rmmod anything related to ehci-hcd and then re-mode probe it and anything else you unloaded, does that make it show up? If so, that would indicate a bug in the ehci driver and/or your platform support. Dan > Thanks a lot for any coment, > Thomas > > Cold Start > PCEngines apu2 > coreboot build 20160311 > 4080 MB ECC DRAM > > SeaBIOS (version ?-20160311_005214-0c3a223c2ee6) > Found mainboard PC Engines PCEngines apu2 > multiboot: eax=0, ebx=0 > boot order: > 1: /pci@i0cf8/usb@10/usb-*@1 > 2: /pci@i0cf8/usb@10/usb-*@2 > 3: /pci@i0cf8/us
AW: MC7455 not listed as usb device any more after reboot
Hi Dan, thanks for your comments. I have included a trace of the working start and the reboot. I noticed that in the reboot case the usb 3-1.3 device is not detected anymore. The usb 3-1 is an ehci-pci. Would it help to reset the ehci-pci? And if so how would I do this. Thanks a lot for any coment, Thomas Cold Start PCEngines apu2 coreboot build 20160311 4080 MB ECC DRAM SeaBIOS (version ?-20160311_005214-0c3a223c2ee6) Found mainboard PC Engines PCEngines apu2 multiboot: eax=0, ebx=0 boot order: 1: /pci@i0cf8/usb@10/usb-*@1 2: /pci@i0cf8/usb@10/usb-*@2 3: /pci@i0cf8/usb@10/usb-*@3 4: /pci@i0cf8/usb@10/usb-*@4 5: /pci@i0cf8/*@14,7 6: /pci@i0cf8/*@11/drive@0/disk@0 7: /pci@i0cf8/*@11/drive@1/disk@0 8: /rom@genroms/pxe.rom 9: pxen0 10: scon1 11: Found 23 PCI devices (max PCI bus is 04) Copying SMBIOS entry point from 0xdffb7000 to 0x000f3110 Copying ACPI RSDP from 0xdffb8000 to 0x000f30e0 Copying MPTABLE from 0xdffdc000/dffdc010 to 0x000f2f30 Copying PIR from 0xdffdd000 to 0x000f2f00 Using pmtimer, ioport 0x818 Scan for VGA option rom Running option rom at c000:0003 Google, Inc. Serial Graphics Adapter 08/22/15 SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (wiv@coreboot-Virtual-Machine) Sat Aug 22 09:25:30 UTC 2015 Term: 80x24 IO4 0 Turning on vga text mode console SeaBIOS (version ?-20160311_005214-0c3a223c2ee6) XHCI init on dev 00:10.0: regs @ 0xfeb22000, 4 ports, 32 slots, 32 byte contexts XHCIextcap 0x1 @ feb22500 XHCIprotocol USB 3.00, 2 ports (offset 1), def 0 XHCIprotocol USB 2.00, 2 ports (offset 3), def 10 XHCIextcap 0xa @ feb22540 Found 2 serial ports ATA controller 1 at 4010/4020/0 (irq 0 dev 88) EHCI init on dev 00:13.0 (regs=0xfeb25420) ATA controller 2 at 4018/4024/0 (irq 0 dev 88) Searching bootorder for: /pci@i0cf8/*@14,7 Searching bootorder for: /rom@img/memtest Searching bootorder for: /rom@img/setup ata0-0: KINGSTON SMS200S3120G ATA-8 Hard-Disk (111 GiBytes) Searching bootorder for: /pci@i0cf8/*@11/drive@0/disk@0 XHCI no devices found Initialized USB HUB (0 ports used) All threads complete. Scan for option roms Running option rom at c100:0003 iPXE (http://ipxe.org) 00:00.0 C100 PCI2.10 PnP PMMpmm call arg1=1 pmm call arg1=0 +DFF49730pmm call arg1=1 pmm call arg1=0 +DFE89730 C100 Searching bootorder for: /rom@genroms/pxe.rom PCengines Press F10 key now for boot menu: Searching bootorder for: HALT drive 0x000f2e90: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=234441648 Space available for UMB: c2000-ef000, f-f2e90 Returned 262144 bytes of ZoneHigh e820 map has 7 items: 0: - 0009f800 = 1 RAM 1: 0009f800 - 000a = 2 RESERVED 2: 000f - 0010 = 2 RESERVED 3: 0010 - dffae000 = 1 RAM 4: dffae000 - e000 = 2 RESERVED 5: f800 - fc00 = 2 RESERVED 6: 0001 - 00011f00 = 1 RAM enter handle_19: NULL Booting from Hard Disk... Booting from :7c00 [0.00] Linux version 4.6.2-040602-generic (kernel@gloin) (gcc version 5.3.1 20160528 (Ubuntu 5.3.1-21ubuntu11) ) #201606100516 SMP Fri Jun 10 09:18:34 UTC 2016 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.6.2-040602-generic root= UUID=474ac08c-0d55-4ac0-ad7e-b922152698e5 ro console=tty0 console=ttyS0,115200n8 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable [0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xdffadfff] usable [0.00] BIOS-e820: [mem 0xdffae000-0xdfff] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00011eff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] e820: last_pfn = 0x11f000 max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xdffae max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000f2f30-0x000f2f3f] mapped at [880f2f30] [0.00] Scanning 1 areas for low m
MC7455 not listed as usb device any more after reboot
Hi all, perhaps you have seen this bug before. I’m using the MC7455 with a linux system after normal power cycle (unplugged power) the mc 7455 can be found with lsusb: go@ubuntu:~$ lsusb Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc. Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub If I do a reboot, the mc7455 is not listed anymore. Any ideas what might be the problem? Kind regards, Thomas ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
MC7455 not listed as usb device anymore after reboot
Hi all, perhaps you have seen this bug before. I’m using the MC7455 with a linux system after normal power cycle (unplugged power) the mc 7455 can be found with lsusb: go@ubuntu:~$ lsusb Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc. Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub If I do a reboot, the mc7455 is not listed anymore. Any ideas what might be the problem? Kind regards, Thomas ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
MC7455 not listed as usb device anymore after reboot
Hi all, perhaps you have seen this bug before. I’m using the MC7455 with a linux system after normal power cycle (unplugged power) the mc 7455 can be found with lsusb: go@ubuntu:~$ lsusb Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc. Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub If I do a reboot, the mc7455 is not listed anymore. Any ideas what might be the problem? Kind regards, Thomas ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: [PATCH v2] bearer-mbim: use the context IP type MM asked to be activated instead of modem response
Hi, perhaps i can bring a good explanation for the long ping. Are you using LTE as a radio access network? If so it could be normal you get a first long ping coz in LTE the power management could put you in a "power save mode" it takes a bit of time to get all the radio resource to use the data connection after you have the radio resources the latency is not an issue any more. If you need a bit more infos let me know. Kind regards, Thomas -Ursprüngliche Nachricht- Von: ModemManager-devel [mailto:modemmanager-devel-boun...@lists.freedesktop.org] Im Auftrag von Thomas Schäfer Gesendet: Dienstag, 21. Juni 2016 21:05 An: modemmanager-devel@lists.freedesktop.org Betreff: Re: [PATCH v2] bearer-mbim: use the context IP type MM asked to be activated instead of modem response Am Dienstag, 21. Juni 2016, 20:30:51 schrieb Thomas Schäfer: > Am Dienstag, 21. Juni 2016, 19:49:25 schrieb Thomas Schäfer: > > Am Dienstag, 21. Juni 2016, 10:02:08 schrieb Dan Williams: > > > Thomas, > > > > > > Could you test this patch out and make sure it works? It should > > > fix the problem you saw before. > Here is the logfile from the dualstack-test with K5150. connect ipv4 works, Ipv6 doesn't work at all (no addresses, no routes) disconnect connect ipv4 works, ping6: connect: Network is unreachable, (the ipv6-default route is missing, one address is there) disconnect IPv4-only works without problems, also after disconnect/connect IPv6-only is untestet, because I have no access to an IPv6-only network anymore. Regards, Thomas PS: Thats all. I have only two mbim devices. ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: MC7455 not working
Hi, I put IPv6 on Ignore, but still same behaviour. I think the problem is somewhere else not IPv6. First what is strange I need to start PC with enabled ModemManger Service otherwise starting ModemManager manualy the Simcard will fail. Second when I start the PC with ModemManager as a service first attempt to connect will fail see log below. What wonders me is that now the nm sees a cdc-wdm1 device. If I restart ModemManager manualy. I can connect but this time nm sees a cdc-wdm0 device. Thomas -Ursprüngliche Nachricht- Von: Bjørn Mork [mailto:bj...@mork.no] Gesendet: Freitag, 17. Juni 2016 19:45 An: Aleksander Morgado Cc: Thomas Lang ; modemmanager-devel@lists.freedesktop.org Betreff: Re: MC7455 not working Aleksander Morgado writes: > On Fri, Jun 17, 2016 at 5:56 PM, Thomas Lang wrote: >> ModemManager[835]: QMI IPv4 Settings: >> ModemManager[835]: Address: 100.76.202.73/30 >> ModemManager[835]: Gateway: 100.76.202.74 >> ModemManager[835]: DNS #1: 139.7.30.126 >> ModemManager[835]: DNS #2: 139.7.30.125 >> ModemManager[835]: MTU: 1500 >> ModemManager[835]: [/dev/cdc-wdm1] Allocating new client ID... >> ModemManager[835]: [/dev/cdc-wdm1] Registered 'wds' (version 1.67) client >> with ID '36' >> ModemManager[835]: error: couldn't start network: QMI protocol error >> (14): 'CallFailed' >> ModemManager[835]: call end reason (1): 'generic-unspecified' >> ModemManager[835]: verbose call end reason (2,210): >> [internal] pdn-ipv6-call-disallowed >> ModemManager[835]: Modem >> /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> >> connected) > > Are you requesting both IPv4 and IPv6 explictly in the NM config? > Looks like IPv6 is failing here. Yes, looks like it is denied by the network. FWIW, I'm currently in exact the same situation - as embarrassing as that might be. But I don't see any failures due to this, only the expected pdn-ipv6-call-disallowed 'CallFailed' message. The IPv4 session still works fine for me. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: MC7455 not working
Hi, Another trace. The last one for today. I personally can't see a difference. Attempt not working: go@ubuntu:~$ sudo ModemManager ModemManager[835]: ModemManager (version 1.5.992) starting in system bus... ModemManager[835]: (ttyUSB2): port attributes not fully set ModemManager[835]: (ttyUSB1): port attributes not fully set ModemManager[835]: (ttyUSB0): port attributes not fully set ModemManager[835]: [/dev/cdc-wdm0] Opening device with flags 'version-info, proxy'... ModemManager[835]: cannot connect to proxy: Could not connect: Connection refused ModemManager[835]: spawning new qmi-proxy (try 1)... ModemManager[835]: [/dev/cdc-wdm1] Opening device with flags 'version-info, proxy'... ModemManager[835]: cannot connect to proxy: Could not connect: Connection refused ModemManager[835]: spawning new qmi-proxy (try 1)... ModemManager[835]: [/dev/cdc-wdm0] Checking version info (10 retries)... ModemManager[835]: [/dev/cdc-wdm1] Checking version info (10 retries)... ModemManager[835]: [/dev/cdc-wdm0] QMI Device supports 32 services: ModemManager[835]: [/dev/cdc-wdm0]ctl (1.5) ModemManager[835]: [/dev/cdc-wdm0]wds (1.67) ModemManager[835]: [/dev/cdc-wdm0]dms (1.14) ModemManager[835]: [/dev/cdc-wdm0]nas (1.25) ModemManager[835]: [/dev/cdc-wdm0]qos (1.6) ModemManager[835]: [/dev/cdc-wdm0]wms (1.10) ModemManager[835]: [/dev/cdc-wdm0]auth (1.3) ModemManager[835]: [/dev/cdc-wdm0]at (1.2) ModemManager[835]: [/dev/cdc-wdm0]voice (2.1) ModemManager[835]: [/dev/cdc-wdm0]cat2 (2.24) ModemManager[835]: [/dev/cdc-wdm0]uim (1.45) ModemManager[835]: [/dev/cdc-wdm0]pbm (1.4) ModemManager[835]: [/dev/cdc-wdm0]test (1.0) ModemManager[835]: [/dev/cdc-wdm0]loc (2.0) ModemManager[835]: [/dev/cdc-wdm0]sar (1.0) ModemManager[835]: [/dev/cdc-wdm0]ts (1.0) ModemManager[835]: [/dev/cdc-wdm0]tmd (1.0) ModemManager[835]: [/dev/cdc-wdm0]wda (1.16) ModemManager[835]: [/dev/cdc-wdm0]csvt (1.1) ModemManager[835]: [/dev/cdc-wdm0]coex (1.0) ModemManager[835]: [/dev/cdc-wdm0]pdc (1.0) ModemManager[835]: [/dev/cdc-wdm0]rfrpe (1.0) ModemManager[835]: [/dev/cdc-wdm0]dsd (1.0) ModemManager[835]: [/dev/cdc-wdm0]ssctl (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0x2e] (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0x30] (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0x31] (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0x36] (1.0) ModemManager[835]: [/dev/cdc-wdm0]rms (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0xf0] (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0xf5] (1.0) ModemManager[835]: [/dev/cdc-wdm0]unknown [0xf6] (1.0) ModemManager[835]: [/dev/cdc-wdm1] QMI Device supports 32 services: ModemManager[835]: [/dev/cdc-wdm1]ctl (1.5) ModemManager[835]: [/dev/cdc-wdm1]wds (1.67) ModemManager[835]: [/dev/cdc-wdm1]dms (1.14) ModemManager[835]: [/dev/cdc-wdm1]nas (1.25) ModemManager[835]: [/dev/cdc-wdm1]qos (1.6) ModemManager[835]: [/dev/cdc-wdm1]wms (1.10) ModemManager[835]: [/dev/cdc-wdm1]auth (1.3) ModemManager[835]: [/dev/cdc-wdm1]at (1.2) ModemManager[835]: [/dev/cdc-wdm1]voice (2.1) ModemManager[835]: [/dev/cdc-wdm1]cat2 (2.24) ModemManager[835]: [/dev/cdc-wdm1]uim (1.45) ModemManager[835]: [/dev/cdc-wdm1]pbm (1.4) ModemManager[835]: [/dev/cdc-wdm1]test (1.0) ModemManager[835]: [/dev/cdc-wdm1]loc (2.0) ModemManager[835]: [/dev/cdc-wdm1]sar (1.0) ModemManager[835]: [/dev/cdc-wdm1]ts (1.0) ModemManager[835]: [/dev/cdc-wdm1]tmd (1.0) ModemManager[835]: [/dev/cdc-wdm1]wda (1.16) ModemManager[835]: [/dev/cdc-wdm1]csvt (1.1) ModemManager[835]: [/dev/cdc-wdm1]coex (1.0) ModemManager[835]: [/dev/cdc-wdm1]pdc (1.0) ModemManager[835]: [/dev/cdc-wdm1]rfrpe (1.0) ModemManager[835]: [/dev/cdc-wdm1]dsd (1.0) ModemManager[835]: [/dev/cdc-wdm1]ssctl (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0x2e] (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0x30] (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0x31] (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0x36] (1.0) ModemManager[835]: [/dev/cdc-wdm1]rms (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0xf0] (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0xf5] (1.0) ModemManager[835]: [/dev/cdc-wdm1]unknown [0xf6] (1.0) ModemManager[835]: Couldn't check support for device at '/sys/devices/pci:00/:00:02.2/:01:00.0': not supported by any plugin ModemManager[835]: Couldn't check support for device at '/sys/devices/pci:00/:00:02.3/:02:00.0': not supported by any plugin ModemManager[835]: Couldn't check support for device at '/sys/devices/pci:00/:00:02.4/:03:00.0':
AW: MC7455 not working
Without restart means I have power-up the device and tried to connect. After this has failed I have restarted nm and mm as service and tried to connect again with the nmcli. -Ursprüngliche Nachricht- Von: Aleksander Morgado [mailto:aleksan...@aleksander.es] Gesendet: Freitag, 17. Juni 2016 15:37 An: Thomas Lang Cc: modemmanager-devel@lists.freedesktop.org; Aleksander Morgado Betreff: Re: MC7455 not working On Fri, Jun 17, 2016 at 2:59 PM, Thomas Lang wrote: > Without restart: > > go@ubuntu:~$ mmcli -b 0 > Bearer '/org/freedesktop/ModemManager1/Bearer/0' > - > Status | connected: 'no' > | suspended: 'no' > | interface: 'unknown' > | IP timeout: '20' > - > Properties | apn: 'web.vodafone.de' > | roaming: 'allowed' > | IP type: 'ipv4v6' > |user: 'none' > |password: 'none' > | number: '*99#' > | Rm protocol: 'unknown' > - > IPv4 configuration | method: 'unknown' > - > IPv6 configuration | method: 'unknown' > - > Stats | Duration: '0' > |Bytes received: 'N/A' > | Bytes transmitted: 'N/A' This info wasn't taken when MM said the bearer was connected; so not useful. It should have said "method DHCP or method static" in IPv4 configuration. > go@ubuntu:~$ sudo service network-manager status ● > NetworkManager.service - Network Manager >Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; > vendor preset: enabled) >Active: active (running) since Fri 2016-06-17 14:48:32 CEST; 4min > 28s ago Main PID: 450 (NetworkManager) >CGroup: /system.slice/NetworkManager.service >└─450 /usr/sbin/NetworkManager --no-daemon > > Jun 17 14:50:11 ubuntu NetworkManager[450]: [1466167811.3502] > dhcp4 (wwp0s19u1u3i8): dhclient started with pid 735 Jun 17 14:50:11 > ubuntu NetworkManager[450]: [1466167811.3506] (cdc-wdm0): IPv6 > configuration disabled Jun 17 14:50:11 ubuntu NetworkManager[450]: > [1466167811.3853] dhcp4 (wwp0s19u1u3i8): client pid 735 exited > with status 1 Jun 17 14:50:11 ubuntu NetworkManager[450]: > [1466167811.3854] dhcp4 (wwp0s19u1u3i8): state changed unknown -> done Jun 17 > 14:50:11 ubuntu NetworkManager[450]: [1466167811.3859] dhcp4 > (wwp0s19u1u3i8): canceled DHCP transaction Jun 17 14:50:11 ubuntu > NetworkManager[450]: [1466167811.3873] device (cdc-wdm0): state > change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Jun > 17 14:50:11 ubuntu NetworkManager[450]: [1466167811.3904] device > (cdc-wdm0): Activation: failed for connection 'Vodafone Default' > Jun 17 14:50:11 ubuntu NetworkManager[450]: [1466167811.3930] > device (cdc-wdm0): state change: failed -> disconnected (reason > 'none') [120 30 0] Jun 17 14:50:11 ubuntu NetworkManager[450]: > [1466167811.4011] (cdc-wdm0): modem state changed, 'connected' --> > 'disconnecting' (reason: user-requested) Jun 17 14:50:11 ubuntu > NetworkManager[450]: [1466167811.4543] (cdc-wdm0): modem state > changed, 'disconnecting' --> 'registered' (reason: user-requested) > > After restart: > What exactly are you restarting? The whole PC, NM, MM? > NetworkManager.service - Network Manager >Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; > vendor preset: enabled) >Active: active (running) since Fri 2016-06-17 14:55:20 CEST; 1min > 51s ago Main PID: 857 (NetworkManager) >CGroup: /system.slice/NetworkManager.service >├─857 /usr/sbin/NetworkManager --no-daemon >└─888 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground > --no-hosts --bind-interfaces > --pid-file=/var/run/NetworkManager/dnsmasq.pid > --listen-address=127.0.1.1 --cache-size=0 --p > > Jun 17 14:55:46 ubuntu dnsmasq[888]: started, version 2.75 cache > disabled Jun 17 14:55:46 ubuntu dnsmasq[888]: compile time options: > IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset > auth DNSSEC loop-detect inotify Jun 17 14:55:46 ubuntu dnsmasq[888]: > DBus support enabled: connected to system bus Jun 17 14:55:46 ubuntu > dnsmasq[888]: warning: no upstream servers configured Jun 1
AW: MC7455 not working
Hmm, so itried dieffrent things out and what I have observed is that if I don’t use NM and MM as sudo systemctl enable NetworkManager ModemManager. The SIM card fails. You could see this in the last mail. When I start the PC after power down. And stop MM with : sudo service ModemManager stop go@ubuntu:~$ mmcli -L No modems were found go@ubuntu:~$ mmcli -m 0 /org/freedesktop/ModemManager1/Modem/0 (device id '7b4cfd7e877aff3cade0b53c88a7b33e7a95c7df') - Hardware | manufacturer: 'Sierra Wireless, Incorporated' | model: 'MC7455' | revision: 'SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53' | supported: 'gsm-umts | lte | gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '359072060132616' - System | device: '/sys/devices/pci:00/:00:13.0/usb1/1-1/1-1.3' |drivers: 'qcserial, qmi_wwan' | plugin: 'Sierra' | primary port: 'cdc-wdm0' | ports: 'ttyUSB2 (at), ttyUSB0 (qcdm), wwp0s19u1u3i10 (net), cdc-wdm0 (qmi), cdc-wdm1 (qmi), wwan0 (net)' - Numbers | own : 'unknown' - Status | lock: 'sim-pin2' | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)' | state: 'registered' |power state: 'on' |access tech: 'lte' | signal quality: '54' (recent) - Modes| supported: 'allowed: 2g, 3g, 4g; preferred: none' |current: 'allowed: 2g, 3g, 4g; preferred: none' - Bands| supported: 'u2100, u1800, u1900, u17iv, u850, u900, eutran-i, eutran-ii, eutran-iii, eutran-iv, eutran-v, eutran-vii, eutran-viii, eutran-xii, eutran-xiii, eutran-xx, eutran-xxv, eutran-xli' |current: 'u2100, u1800, u1900, u17iv, u850, u900, eutran-i, eutran-ii, eutran-iii, eutran-iv, eutran-v, eutran-vii, eutran-viii, eutran-xii, eutran-xiii, eutran-xx, eutran-xxv, eutran-xli' - IP | supported: 'ipv4, ipv6, ipv4v6' - 3GPP | imei: '359072060132616' | enabled locks: 'none' |operator id: '26202' | operator name: 'Vodafone' | subscription: 'unknown' | registration: 'home' - SIM | path: '/org/freedesktop/ModemManager1/SIM/0' - Bearers | paths: 'none' go@ubuntu:~$ sudo nmcli d DEVICETYPE STATE CONNECTION cdc-wdm0 gsm disconnected -- wlp4s0wifi disconnected -- enp1s0ethernet unavailable -- enp3s0ethernet unavailable -- enp2s0ethernet unmanaged -- loloopback unmanaged -- go@ubuntu:~$ sudo nmcli d c cdc-wdm0 Device 'cdc-wdm0' successfully activated with '9264dfab-d648-4497-b851-97bd6a3ad1ce'. It works. Below find the debug trace. But still if NM and MM are enable as service. PC start after powerdown I still need to restart MM once to get it running. My idea would be to restart MM somewhere with a script. Do you see another solution for now? >> tlv_length = 7 >> message = "Set Event Report" (0x0002) >> TLV: >> type = "Result" (0x02) >> length = 4 >> value = 00:00:00:00 >> translated = SUCCESS ModemManager[1157]: [/dev/cdc-wdm0] Sent message... << RAW: << length = 17 << data = 01:10:00:00:03:07:00:07:00:03:00:04:00:13:01:00:01 ModemManager[1157]: [/dev/cdc-wdm0] Sent message (translated)... << QMUX: << length = 16 << flags = 0x00 << service = "nas" << client = 7 << QMI: << flags = "none" << transaction = 7 << tlv_length = 4 << message = "Register Indications" (0x0003) << TLV: << type = "Serving System Events" (0x13) << length = 1 << value = 01 << translated = yes ModemManager[1157]: [/dev/cdc-wdm0] Received message... >> RAW: >> length = 20 >> data = 01:13:00:80:03:07:02:07:00:03:00:07:00:02:04:00:00:00:00:00 ModemManager[1157]: [/dev/cdc-wdm0] Received message (translated)... >> QMUX: >> length = 19 >> flags = 0x80 >> service = "nas" >> client = 7 >> QMI: >> flags = "response" >> transaction = 7 >> tlv_length = 7 >> message = "Register Indications" (0x0003) >> TLV: >> type = "Result" (0x02) >> length = 4 >> value = 00:00:00:00 >> translated = SUCCESS ModemManager[1157]: [1466176578.472516] [mm-broadband-modem.c:9238] enabling_step(): Modem has location capabil
AW: MC7455 not working
x27;
|user: 'none'
|password: 'none'
| number: '*99#'
| Rm protocol: 'unknown'
-
IPv4 configuration | method: 'static'
| address: '100.78.46.127'
| prefix: '24'
| gateway: '100.78.46.128'
| DNS: '139.7.30.126', '139.7.30.125'
| MTU: '1500'
-
IPv6 configuration | method: 'unknown'
-----
Stats | Duration: '90'
|Bytes received: '49718'
| Bytes transmitted: '107326'
-Ursprüngliche Nachricht-
Von: Aleksander Morgado [mailto:aleksan...@aleksander.es]
Gesendet: Freitag, 17. Juni 2016 14:45
An: Thomas Lang
Cc: modemmanager-devel@lists.freedesktop.org; Aleksander Morgado
Betreff: Re: MC7455 not working
On Fri, Jun 17, 2016 at 2:16 PM, Thomas Lang wrote:
> I have been following the discussion on the mail-list. I’m trying to
> get network-manager working with a MC7455. I upgraded the kernel to
> 4.6.2. I updated the libqmi (1.14.2), MomdemManager (1.5.992) and
> NetworkManager
> (1.2.0) to the latest versions. The modemmanager can use the qmi interface.
> I can connect with the mmcli to the network. I can receive an ip
> address with udhcpc -I command. The problem I still have I can’t get
> the Network-Manager to start the connection. I have read the mail
> below that states the NetworkManager will config the connection for
> you. It seems that the dhcp set-up from the NetworkManager fails, see
> trace below. Now my question what can I do to get the network-manager to
> set-up the connection.
That is strange; for the MC7455, when using raw-ip, we are defaulting to static
IP setup, not DHCP, so NM shouldn't even try DHCP. Can you get us the output of
the bearer info generated during the connection request? (something like "mmcli
-b 0", or some other index).
Anyway, it would also be good to get MM/NM debug logs, see:
https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: MC7455 not working
Dear Aleksander, perhaps an interesting observation. I could connect through the Network-manager. I restarted the Modem-Manager and the Network-Manager service. After this I could connect with the nm-applet gui. Also I could connect with the nmcli d c cdc-wdm0, but only after I restarted both mm and nm. Kind regards, Thomas ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor p Active: active (running) since Fri 2016-06-17 12:42:06 CEST; 5min ago Main PID: 1209 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─1209 /usr/sbin/NetworkManager --no-daemon └─1242 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts Jun 17 12:42:33 ubuntu dnsmasq[1242]: started, version 2.75 cache disabled Jun 17 12:42:33 ubuntu dnsmasq[1242]: compile time options: IPv6 GNU-getopt DBus Jun 17 12:42:33 ubuntu dnsmasq[1242]: DBus support enabled: connected to system Jun 17 12:42:33 ubuntu dnsmasq[1242]: warning: no upstream servers configured Jun 17 12:42:33 ubuntu NetworkManager[1209]: [1466160153.7774] device (c Jun 17 12:42:33 ubuntu NetworkManager[1209]: [1466160153.7885] dnsmasq[0 Jun 17 12:42:33 ubuntu NetworkManager[1209]: [1466160153.7893] dns-mgr: Jun 17 12:42:33 ubuntu dnsmasq[1242]: setting upstream servers from DBus Jun 17 12:42:33 ubuntu dnsmasq[1242]: using nameserver 139.7.30.126#53 Jun 17 12:42:33 ubuntu dnsmasq[1242]: using nameserver 139.7.30.125#53 Von: Thomas Lang Gesendet: Freitag, 17. Juni 2016 14:17 An: 'modemmanager-devel@lists.freedesktop.org' Cc: Aleksander Morgado Betreff: AW: MC7455 not working Dear Aleksander, I have been following the discussion on the mail-list. I’m trying to get network-manager working with a MC7455. I upgraded the kernel to 4.6.2. I updated the libqmi (1.14.2), MomdemManager (1.5.992) and NetworkManager (1.2.0) to the latest versions. The modemmanager can use the qmi interface. I can connect with the mmcli to the network. I can receive an ip address with udhcpc -I command. The problem I still have I can’t get the Network-Manager to start the connection. I have read the mail below that states the NetworkManager will config the connection for you. It seems that the dhcp set-up from the NetworkManager fails, see trace below. Now my question what can I do to get the network-manager to set-up the connection. I’m looking forward for an answer. Kind regards, Thomas ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-06-17 11:19:39 CEST; 57min ago Main PID: 1300 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─1062 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --proxy-dnssec └─1300 /usr/sbin/NetworkManager --no-daemon Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.3799] (cdc-wdm0): IPv6 configuration disabled Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4154] dhcp4 (wwp0s19u1u3i10): client pid 1691 exited with status 1 Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4154] dhcp4 (wwp0s19u1u3i10): state changed unknown -> done Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4159] dhcp4 (wwp0s19u1u3i10): canceled DHCP transaction Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4171] device (cdc-wdm0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4205] policy: disabling autoconnect for connection 'Vodafone Default'. Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4218] device (cdc-wdm0): Activation: failed for connection 'Vodafone Default' Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4243] device (cdc-wdm0): state change: failed -> disconnected (reason 'none') [120 30 0] Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4337] (cdc-wdm0): modem state changed, 'connected' --> 'disconnecting' (reason: user-requested) Jun 17 12:16:40 ubuntu NetworkManager[1300]: [1466158600.4405] (cdc-wdm0): modem state changed, 'disconnecting' --> 'registered' (reason: user-requested) MC7455 not working Aleksander Morgado aleksander at aleksander.es <mailto:modemmanager-devel%40lists.freedesktop.org?Subject=Re%3A%20MC7455%20not%20working&In-Reply-To=%3CCAAP7ucLn%2BoBZUvwagg30k2r%2Bdt68GLb1mN1GiuTvucjCZ6PcYw%40mail.gmail.com%3E> Wed Mar 23 10:47:57 UTC 2016 * Previous message: MC7455 not working <https://lists.freedesktop.org/archives/modemmanager-devel/2016-March/002817.html> * Next message: MC7455 not working <https://lists.freedesktop.org/ar
