3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

[Benoît]

Many thanks

I did it (writing udev rules) and now I can see ttyUSB0 ttyUSB1 ttyUSB2
When I try to speak to the modem I always got a Transaction Timed out.

It is like I am unable to unlock it? (qmicli -d /dev/cdc-wdm0 
--dms-set-fcc-authentication
error: couldn't create client for the 'dms' service: CID allocation 
failed in the CTL client: Transaction timed out)

all commands I try to pass are Timed out

for ModemManager I tried to see:
ModemManager /dev/cdc-wdm0
ModemManager[725]: <info>  ModemManager (version 1.4.12) starting in 
system bus...
ModemManager[725]: <warn>  (ttyUSB0): port attributes not fully set
ModemManager[725]: <warn>  (ttyUSB1): port attributes not fully set
ModemManager[725]: <warn>  (ttyUSB2): port attributes not fully set
ModemManager[725]: [/dev/cdc-wdm0] Opening device with flags 
'version-info, proxy'...
ModemManager[725]: cannot connect to proxy: Could not connect: 
Connection refused
ModemManager[725]: spawning new qmi-proxy (try 1)...
ModemManager[725]: [/dev/cdc-wdm0] Checking version info (10 retries)...
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0': not supported by 
any plugin
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0': not supported by 
any plugin
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0': not supported by 
any plugin
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0': not supported by 
any plugin
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:1c.4/0000:05:00.0/0000:06:01.0/0000:07:00.0': 
not supported by any plugin
ModemManager[725]: <info>  Couldn't find support for device at 
'/sys/devices/pci0000:00/0000:00:1c.5/0000:09:00.0': not supported by 
any plugin
ModemManager[725]: <info>  Creating modem with plugin 'Gobi' and '5' ports
ModemManager[725]: <warn>  Could not grab port (usbmisc/cdc-wdm0): 
'Cannot add port 'usbmisc/cdc-wdm0', unsupported'
ModemManager[725]: <warn>  Could not grab port (tty/ttyUSB1): 'Cannot 
add port 'tty/ttyUSB1', unhandled serial type'
ModemManager[725]: <warn>  (ttyUSB2): port attributes not fully set
ModemManager[725]: <info>  Modem for device at 
'/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7' successfully created
ModemManager[725]: <info>  Creating modem with plugin 'Generic' and '1' 
ports
ModemManager[725]: <warn>  Could not grab port (tty/ttyS3): 'Cannot add 
port 'tty/ttyS3', unhandled serial type'
ModemManager[725]: <warn>  Couldn't create modem for device at 
'/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
ModemManager[725]: <info>  Modem: state changed (unknown -> disabled)



On 10/27/15 14:41, Bjørn Mork wrote:
> "Benoît" <benoitne at gmail.com> writes:
>
>> I didn't configure it and didn't make anything to switch to QMI
>> I tried MBIM but I don't have any reply so I guess it is set to QMI.
>> when I do a journalctl | grep cdc ;
>>
>> Oct 27 10:58:44  kernel: usbcore: registered new interface driver cdc_ncm
>> Oct 27 10:58:44  kernel: usbcore: registered new interface driver cdc_wdm
>> Oct 27 10:58:44  kernel: cdc_mbim 1-7:2.12: cdc-wdm0: USB WDM device
>> Oct 27 10:58:44  kernel: cdc_mbim 1-7:2.12 wwan0: register 'cdc_mbim'
>> at usb-0000:00:14.0-7, CDC MBIM, d2:cc:f3:56:10:30
>> Oct 27 10:58:44  kernel: usbcore: registered new interface driver cdc_mbim
>> Oct 27 10:58:44  kernel: cdc_mbim 1-7:2.12 wwp0s20u7c2i12: renamed
>> from wwan0
> Right.  I suspected this. The Linux kernel will select the MBIM
> configuration.
>
> cdc_mbim != qmi_wwan.  Both drivers use /dev/cdc-wdmX devices to carry
> their management protocols, but the protocols are very different.
>
> Unfortunately, as I mentioned, a firmware bug makes the device appear to
> support whaever protocol you *first* use of QMI and MBIM, regardless of
> USB configuration. This is not a feature.  The network device framing is
> incompatible, so the cdc_mbim driver is incapable of supporting QMI
> network devices.
>
> Using qmicli with the cdc_mbim driver is not going to work.  Forget
> about libqmi and use libmbim instead.  Or use an udev rule to switch the
> modem to QMI if you prefer to stay with qmicli. It goes something like
> this (I'm too lazy to google):
>
> SUBSYSTEM=="usb",ATTR{idVendor}=="413c",ATTR{idProduct}=="81a3",ATTR{bConfigurationValue}=="2" ATTR{bConfigurationValue}="1"
>
>
> Note: You must use udev to make sure this happens immediately on device
> discovery. I do not recommend "late" switching of these modems.  Another
> firmware bug is likely to hit if the configuration is changed after
> cdc_mbim has probed it.
>
> Even easier than all this:  Use ModemManager.  It will automagically
> "Do The Right Thing"
>
>
> Bjørn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20151027/504f092e/attachment-0001.html>