<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" content="1" /><style type="text/css"> p, li { white-space: pre-wrap; } </style></head><body style=" font-family:'Bitstream Vera Sans Mono'; font-size:9pt; font-weight:400; font-style:normal;"> Dear Bjørn, On Donnerstag, 13. Oktober 2016 12:46:49 Bjørn Mork wrote: > On October 13, 2016 12:10:07 PM CEST, Hans-Peter Jansen <hpj@urpla.net> wrote: > >T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 > >D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > >P: Vendor=1199 ProdID=9079 Rev=00.06 > >S: Manufacturer=Sierra Wireless, Incorporated > >S: Product=Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A > >S: SerialNumber=LF62830495041014 > >C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA > >I: If#=12 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=qmi_wwan > >I: If#=13 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=qmi_wwan > > That's the wrong driver. Nothing is ever going to work that way. > > This is NOT the result of a default configuration. You need to start from > scratch. Remove ever change affecting the modem and install a clean > environment with defaults for everything. Oops, sorry, forgot a hunk in udev.rules.d, removed it, rebooted, and: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1199 ProdID=9079 Rev=00.06 S: Manufacturer=Sierra Wireless, Incorporated S: Product=Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A S: SerialNumber=LF62830495041014 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=12 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#=13 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim Be assured, that I'm very careful (minus this fault pas :() in system modifications, e.g. I never build system apps from tarballs. I'm pretty sure, that I can reproduce this effect on another X1 Carbon Gen4 (type FB20), just by installing openSUSE Leap and adding my repo, given the same modem model is assembled. > >I'm not that deep into the usb protocol but obviously, the kernel > >doesn't > >accept the interface numbers 12 and 13. Kernel shows now: 2016-10-13T15:36:14.178364+02:00 x1carbon kernel: [ 712.814653] usb 1-2: new high-speed USB device number 7 using xhci_hcd 2016-10-13T15:36:14.318373+02:00 x1carbon kernel: [ 712.955373] usb 1-2: config 1 has an invalid interface number: 12 but max is 1 2016-10-13T15:36:14.318402+02:00 x1carbon kernel: [ 712.955374] usb 1-2: config 1 has an invalid interface number: 13 but max is 1 2016-10-13T15:36:14.318403+02:00 x1carbon kernel: [ 712.955375] usb 1-2: config 1 has an invalid interface number: 13 but max is 1 2016-10-13T15:36:14.318404+02:00 x1carbon kernel: [ 712.955376] usb 1-2: config 1 has no interface number 0 2016-10-13T15:36:14.318405+02:00 x1carbon kernel: [ 712.955376] usb 1-2: config 1 has no interface number 1 2016-10-13T15:36:14.318406+02:00 x1carbon kernel: [ 712.955884] usb 1-2: New USB device found, idVendor=1199, idProduct=9079 2016-10-13T15:36:14.318407+02:00 x1carbon kernel: [ 712.955885] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2016-10-13T15:36:14.318408+02:00 x1carbon kernel: [ 712.955886] usb 1-2: Product: Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A 2016-10-13T15:36:14.318409+02:00 x1carbon kernel: [ 712.955886] usb 1-2: Manufacturer: Sierra Wireless, Incorporated 2016-10-13T15:36:14.318428+02:00 x1carbon kernel: [ 712.955887] usb 1-2: SerialNumber: LF62830495041014 2016-10-13T15:36:14.338381+02:00 x1carbon kernel: [ 712.978072] cdc_mbim 1-2:1.12: cdc-wdm0: USB WDM device 2016-10-13T15:36:14.338392+02:00 x1carbon kernel: [ 712.978295] cdc_mbim 1-2:1.12 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-2, CDC MBIM, 72:55:f7:xx:yy:zz > It does accept them. It's just a warning. Bo need to worry about that. It's > normal. > > Yes, the warning is obviously misleading although formally correct. But I've > not been successful getting it removed or demoted. Understood, thanks. Unfortunately, the issue persists: ~# rcModemManager status ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Thu 2016-10-13 14:22:54 CEST; 2h 28min ago Main PID: 869 (ModemManager) CGroup: /system.slice/ModemManager.service |- 869 /usr/sbin/ModemManager `-1385 /usr/lib/mbim-proxy Oct 13 14:23:25 x1carbon.infovision ModemManager[869]: <warn> Could not grab port (usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0', unsupported' Oct 13 14:23:25 x1carbon.infovision ModemManager[869]: <warn> Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2': Failed to find primary AT port Oct 13 15:36:07 x1carbon.infovision ModemManager[869]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0': not supported by any plugin Oct 13 15:36:07 x1carbon.infovision ModemManager[869]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin Oct 13 15:36:15 x1carbon.infovision ModemManager[869]: opening device... Oct 13 15:36:15 x1carbon.infovision ModemManager[869]: [/dev/cdc-wdm0] Read max control message size from descriptors file: 4096 Oct 13 15:36:45 x1carbon.infovision ModemManager[869]: proxy configuration failed: closed Oct 13 15:36:45 x1carbon.infovision ModemManager[869]: <info> Creating modem with plugin 'Sierra' and '2' ports Oct 13 15:36:45 x1carbon.infovision ModemManager[869]: <warn> Could not grab port (usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0', unsupported' Oct 13 15:36:45 x1carbon.infovision ModemManager[869]: <warn> Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2': Failed to find primary AT port mbim-proxy is spinning: [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 [pid 1385] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0 and mbimcli is still missing the device: ~# mbimcli -p -d /dev/cdc-wdm0 --query-device-caps error: couldn't open the MbimDevice: Transaction timed out although it exists: ~# l /dev/cdc-wdm0 crw------- 1 root root 180, 176 13. Okt 15:36 /dev/cdc-wdm0 The ModemManager doesn't stop properly until mbim-proxy is killed with SIGKILL. Surprise: after that procedure, I was able to query the devices capabilities: ~# mbimcli -p -d /dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' Sim class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '014582001815001' Firmware info: 'SWI9X30C_02.08.02.00' Hardware info: 'EM7455' and guess what, it worked! And kept working after reboot. Hmm. Let's see, how stable this is in the next couple of days. Will call back then. Thanks everyone, Pete</body></html>