On Ubuntu 15.04, running ModemManager 1.4.0-1, I'm unable to establish a connection. mmcli --simple-connect exits right away (with no perceivable timeout) with "MobileEquipment.NetworkTimeout" ≻ mmcli -m 0 --simple-connect="pin=XXXX,apn=internet.t-d1.de" error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NetworkTimeout: Network timeout' with only these three lines in /var/log/syslog : thinkpad ModemManager[924]: <info> Simple connect started... thinkpad ModemManager[924]: <info> Simple connect state (4/8): Wait to get fully enabled thinkpad ModemManager[924]: <info> Simple connect state (5/8): Register However, a 3GPP scan completes successfully: ≻ mmcli -m 0 --3gpp-scan --timeout 60 Found 12 networks: 26207 - o2 - de (unknown, available) 26202 - Vodafone.de (unknown, available) 26202 - Vodafone.de (unknown, available) 26207 - o2 - de (unknown, available) 26202 - Vodafone.de (unknown, available) 26203 - E-Plus (unknown, available) 26203 - E-Plus (unknown, available) 26203 - E-Plus (unknown, available) 26207 - o2 - de (unknown, available) 26201 - Telekom.de (unknown, available) 26201 - Telekom.de (unknown, available) 26201 - Telekom.de (unknown, available) ≻ mmcli -m 0 /org/freedesktop/ModemManager1/Modem/0 (device id 'fa4fd90f4600d86ced16734e58848fbc622d0280') ------------------------- Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:A001]' | revision: 'FIH7160_V1.2_WW_01.1415.07' | supported: 'gsm-umts, lte' | current: 'gsm-umts, lte' | equipment id: '013937005765167' ------------------------- System | device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4' | drivers: 'cdc_acm, cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net), ttyACM0 (at)' ------------------------- Numbers | own : 'unknown' ------------------------- Status | lock: 'none' | unlock retries: 'sim-pin2 (3)' | state: 'enabled' | power state: 'on' | access tech: 'unknown' | signal quality: '51' (recent) ------------------------- Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none' | current: 'allowed: 2g, 3g, 4g; preferred: none' ------------------------- Bands | supported: 'unknown' | current: 'unknown' ------------------------- IP | supported: 'ipv4, ipv6, ipv4v6' ------------------------- 3GPP | imei: '(CORRECT)' | enabled locks: 'sim, fixed-dialing' | operator id: 'unknown' | operator name: 'unknown' | subscription: 'unknown' | registration: 'idle' ------------------------- SIM | path: '/org/freedesktop/ModemManager1/SIM/0' ------------------------- Bearers | paths: 'none' Are there any steps I may follow to better debug this? Thank you very much in advance P
Please follow these instructions to get ModemManager running in debug mode, so that we can get the whole flow of MBIM transactions sent with the device: http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ Once it's running in debug mode, try to get it connected as you normally would.
Created attachment 118586 [details] modem manager debug log
Created attachment 118587 [details] network manager debug log
Thank you very much for the prompt reply! I attached also a network manager log, although i triggered the simple-connect with mmcli
For some reason your modem is not getting registered to any network. And in particular, it's giving a "BadSim" error: >>>>>> Header: >>>>>> length = 96 >>>>>> type = command-done (0x80000003) >>>>>> transaction = 19 >>>>>> Fragment header: >>>>>> total = 1 >>>>>> current = 0 >>>>>> Contents: >>>>>> status error = 'BadSim' (0x00000004) >>>>>> service = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df) >>>>>> cid = 'register-state' (0x00000009) Could you make sure you're trying with a valid SIM card?
Indeed, the SIM card was somehow not activated! After contacting my carrier everything works flawlessly. IMHO bubbling up that 'BadSim' error to the user would be a good idea, as NetworkTimeout seems misleading. Thank you very much for your quick support.
Yeah, proper error reporting is somewhat lacking... Anyway, NOTABUG! :)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.