Hey all,
From Paul's email, the port type hints for the TTYs exposed by the
MC74xx could help make the probing much faster. I haven't tested them
myself, but we could definitely add them in the release.
# MC74XX: Add port hints
# if 03: primary port
# if 02: raw NMEA port
# if 00: diag/qcdm port
ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
ENV{.MM_USBIFNUM}=="03", ENV{ID_MM_PORT_TYPE_AT_PRIMARY}="1"
ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
ENV{.MM_USBIFNUM}=="02", ENV{ID_MM_PORT_TYPE_GPS}="1"
ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
ENV{.MM_USBIFNUM}=="00", ENV{ID_MM_PORT_TYPE_QCDM}="1"
This rule is not required because (FOR NOW) ID_MM_DEVICE_IGNORE
applies exclusively to TTYs, which is something I'd like to change in
the next release (there's an open MR to do that):
# MC74XX: Ignore "wwan0" net interface
ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
ENV{.MM_USBIFNUM}=="08", ENV{ID_MM_DEVICE_IGNORE}="1"
And this one should also not be required, as there are other generic
built-in rules to ignore the device in QDL mode:
# MC74XX: ignore QDL port
ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9070", ENV{ID_MM_DEVICE_IGNORE}="1"
On Wed, Aug 21, 2019 at 9:20 PM Paul Bartell wrote:
>
> Amol,
>
> Try this 77-mm-sierra.rules udev rules file with port type hints for
> Sierra MDM9x30 chipset modems.
>
> Thanks,
> Paul
>
> On Wed, Aug 21, 2019 at 5:23 AM Amol Lad wrote:
> >
> > Please help with this. What could be the cause of significant MM startup
> > delay?
> >
> >
> >
> > From: ModemManager-devel
> > On Behalf Of Amol Lad
> > Sent: Monday, 19 August 2019 4:05 PM
> > To: modemmanager-devel@lists.freedesktop.org
> > Subject: Modemmanager significant startup delay
> >
> >
> >
> > Hi,
> >
> >
> >
> > I’m using Solidrun’s clearfog-base plarform with Sierra Wireless EM7430 LTE
> > chipset. I’m running OpenWRT 18.06 with ModemManager feed from
> > https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt
> >
> >
> >
> > It is taking around 20 seconds for modemanager to bring up the LTE IP
> > interface (i.e. after around 20 seconds ‘wwan1’ interface is up and I can
> > ping external world). With uqmi the interface comes up instantly. Please
> > refer to below logs (captured in –debug mode). It seems most of this delay
> > is because of “serial command timeout”. As you can see from the last time
> > “[plugin manager] task 0: finished in '17.149826' seconds
> >
> > “
> >
> >
> >
> > Please advise what is going wrong.
> >
> >
> >
> > …
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.535657]
> > (ttyUSB2): <-- ''
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.535956]
> > (ttyUSB2): <-- 'OK'
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536110]
> > (tty/ttyUSB2) port is AT-capable
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536188]
> > [plugin manager] task 0,ttyUSB2: found best plugin for port (Sierra)
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536269]
> > [plugin manager] task 0,ttyUSB2: finished in '1.604063' seconds
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536348]
> > [plugin manager] task 0,ttyUSB2: best plugin matches device reported one:
> > Sierra
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536433]
> > [plugin Manager] task 0: still 2 running probes (2 active): ttyUSB1, ttyUSB0
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536565]
> > (ttyUSB2) device open count is 0 (close)
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.536702]
> > (ttyUSB2) closing
> >
> > port...
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.537143]
> > (ttyUSB2) serial port closed
> >
> > Mon Aug 19 10:11:05 2019 daemon.debug [2086]: [1566209465.537304]
> > (ttyUSB2) forced to close port
> >
> > Mon Aug 19 10:11:06 2019 daemon.debug [2086]: [1566209466.220126]
> > [plugin manager] task 0: min probing time elapsed
> >
> > Mon Aug 19 10:11:06 2019 daemon.debug [2086]: [1566209466.220187]
> > [plugin Manager] task 0: still 2 running probes (2 active): ttyUSB1, ttyUSB0
> >
> > Mon Aug 19 10:11:08 2019 daemon.debug [2086]: [1566209468.868113]
> > Parsing AT got: 'Serial command timed out'
> >
> > Mon Aug 19 10:11:08 2019 daemon.debug [2086]: [1566209468.868197]
> > Parsing AT got: 'Serial command timed out'
> >
> > Mon Aug 19 10:11:08 2019 daemon.debug [2086]: [1566209468.868282]
> > (ttyUSB1): --> 'AT'
> >
> > Mon Aug 19 10:11:08 2019 daemon.debug [2086]: [1566209468.868351]
> > (ttyUSB0): --> 'AT'
> >
> > Mon Aug 19 10:11:11 2019 daemon.debug [2086]: [1566209471.869749]
> > Parsing AT got: 'Serial command timed out'
> >
> > Mon Aug 19 10:11:11 2019 daemon.debug [2086]: [1566209471.869831]
> > Parsing AT got: 'Serial command timed out'
> >
> > Mon Aug 19 10:11:11 2019 daemon.debug [2086]: [1566209471.869917]
> > (ttyUSB1): --> 'AT'
> >
> >