3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient
Dan Williams
dcbw at redhat.com
Tue Oct 27 08:29:09 PDT 2015
On Tue, 2015-10-27 at 09:56 -0500, Dan Williams wrote:
> On Tue, 2015-10-27 at 15:32 +0100, Benoît wrote:
> > modemmanager :
> > ModemManager
> > ModemManager[655]: <info> ModemManager (version 1.4.12) starting in
> > system bus...
>
> Benoit, could you run ModemManager with "--debug" so we can get a bit
> more information here?
The debug logs you sent show that /dev/cdc-wdm0 isn't responding to the
QMI "Get Version Info" request. I wonder if the modem is actually
expecting MBIM at this point?
Dan
> Dan
>
> > ModemManager[655]: <warn> (ttyUSB0): port attributes not fully set
> > ModemManager[655]: <warn> (ttyUSB1): port attributes not fully set
> > ModemManager[655]: <warn> (ttyUSB2): port attributes not fully set
> > ModemManager[655]: [/dev/cdc-wdm0] Opening device with flags
> > 'version-info, proxy'...
> > ModemManager[655]: cannot connect to proxy: Could not connect:
> > Connection refused
> > ModemManager[655]: spawning new qmi-proxy (try 1)...
> > ModemManager[655]: [/dev/cdc-wdm0] Checking version info (10 retries)...
> > ModemManager[655]: <info> Couldn't find support for device at
> > '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
> > ModemManager[655]: <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[655]: <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[655]: <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[655]: <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[655]: <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[655]: <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[655]: <info> Creating modem with plugin 'Gobi' and '5' ports
> > ModemManager[655]: <warn> Could not grab port (usbmisc/cdc-wdm0):
> > 'Cannot add port 'usbmisc/cdc-wdm0', unsupported'
> > ModemManager[655]: <warn> Could not grab port (tty/ttyUSB1): 'Cannot
> > add port 'tty/ttyUSB1', unhandled serial type'
> > ModemManager[655]: <warn> (ttyUSB2): port attributes not fully set
> > ModemManager[655]: <info> Modem for device at
> > '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7' successfully created
> > ModemManager[655]: <info> Creating modem with plugin 'Generic' and '1'
> > ports
> > ModemManager[655]: <warn> Could not grab port (tty/ttyS3): 'Cannot add
> > port 'tty/ttyS3', unhandled serial type'
> > ModemManager[655]: <warn> Couldn't create modem for device at
> > '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
> > ModemManager[655]: <info> Modem: state changed (unknown -> disabled)
> >
> > :( excuse me to bother you with this problem and I appreciate a lot your
> > help to troubleshoot the problem ...
> >
> >
> > On 10/27/15 15:14, Bjørn Mork wrote:
> > > "Benoît" <benoitne at gmail.com> writes:
> > >
> > >> 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[725]: <warn> Could not grab port (usbmisc/cdc-wdm0):
> > >> 'Cannot add port 'usbmisc/cdc-wdm0', unsupported'
> > > This doesn't look good. Is there something else holding the device
> > > open? "lsof /dev/cdc-wdm0" will tell. Was the configuration switch too
> > > late? "dmesg" will tell. If it shows cdc_mbim probing before the
> > > switch, then you will have to prevent that somehow. Blacklisting
> > > cdc_mbim maybe.
> > >
> > >
> > > Bjørn
> >
> > _______________________________________________
> > libqmi-devel mailing list
> > libqmi-devel at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>
>
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
More information about the libqmi-devel
mailing list