RE: libmbim 1.24.0 slowing down MM startup
Hi Aleksander, I followed your steps and mbim-proxy seg faults when MM tries to enable QMI indications over MBIM. This is just a heads-up just in case something clicks in your mind. I will try to get you a crash dump. Amol -Original Message- From: Aleksander Morgado Sent: Tuesday, 7 July 2020 6:32 PM To: Amol Lad Cc: ModemManager (development) Subject: Re: libmbim 1.24.0 slowing down MM startup Hey, > > I'm testing 1.14.0 and finding that libmbim has significantly slowed down MM > startup. I'm using EM7565 in MBIM mode. Please see below snippets from log > which highlight the delay. As you can see "couldn't load carrier config; > couldn't load SUPL; assistance data" are causing this slowness. > This looks like QMI over MBIM indications not working properly, how strange. Could you retry debug logging but also including mbim-proxy logs? E.g.: // stop ModemManager and make sure mbim-proxy is not running $ sudo /usr/libexec/mbim-proxy --verbose --no-exit // in another terminal, start ModemManager in debug mode -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Quectel BG96: band selection does not take effect
On Tue, Jul 07, 2020 at 03:16:09PM +0200, Reinhard Speyerer wrote: > On Tue, Jul 07, 2020 at 01:56:34PM +0200, Fredrik Flornes Ellertsen wrote: > [...] > > << TLV: > > << type = 0x25 > > << length = 8 > > << value = 9F:18:0E:0A:40:00:00:00 > > << TLV: > > << type = 0x26 > > << length = 8 > > << value = 9F:18:0E:0A:00:00:00:00 > > << TLV: > > << type = 0x27 > > << length = 17 > > << value = 04:08:00:00:00:0A:00:00:00:0B:00:00:00:04:00:00:00 > > > > Resetting the modem doesn't help either. I am not sure whether this mailing > > list is the correct forum for this question or if I should ask Quectel > > about this. Any help is very much appreciated. > > > > Hi Fredrik, > > when looking at TLVs 0x24 and 0x25 one can see that their values when > interpreted as a LTE bandmask seem to match the values supported by the > BG96 for Cat-M1 and CAT-NB1. > Sorry, that should read TLVs 0x25 and 0x26. Regards, Reinhard > My guess is that there would also be two additional extended LTE band > preference TLVs for MDM9205-based devices like Quectel BG95 and > Telit ME910G1 since they may support LTE bands > 64: > > Regards, > Reinhard > ___ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Quectel BG96: band selection does not take effect
On Tue, Jul 07, 2020 at 01:56:34PM +0200, Fredrik Flornes Ellertsen wrote:
> Hi,
>
> We are having trouble with band selection on the Quectel BG96. It seems the
> band selection command executes successfully, but the modem always stays on
> LTE band 20 regardless of the band selection preference. We are using
> ModemManager version 1.10.0 patched with commit f2c878e7 to allow setting
> the band preference without SIGSEGV.
>
> Here we try to configure the modem to avoid band 20.
>
> $ mmcli -m 0 --set-current-bands='eutran-8'
> successfully set current bands in the modem
>
> [...]
>
> Relevant part of the ModemManager log:
>
> [...]
> << message = "Get System Selection Preference" (0x0034)
> ModemManager[6395]: [/dev/cdc-wdm0] received message...
> << RAW:
> << length = 151
> << data =
> 01:96:00:80:03:01:02:4B:00:34:00:8A:00:02:04:00:00:00:00:00:10:01:00:00:11:02:00:10:00:12:08:00:00:00:00:00:00:00:00:00:15:08:00:80:00:00:00:00:00:00:00:16:01:00:00:18:04:00:02:00:00:00:19:04:00:01:00:00:00:1C:05:00:04:08:00:00:04:1D:04:00:00:00:00:00:1F:04:00:02:00:00:00:20:04:00:01:00:00:00:24:08:00:02:00:00:00:00:00:00:00:25:08:00:9F:18:0E:0A:40:00:00:00:26:08:00:9F:18:0E:0A:00:00:00:00:27:11:00:04:08:00:00:00:0A:00:00:00:0B:00:00:00:04:00:00:00
> ModemManager[6395]: [/dev/cdc-wdm0] received generic response
> (translated)...
> << QMUX:
> << length = 150
> << flags = 0x80
> << service = "nas"
> << client = 1
> << QMI:
> << flags = "response"
> << transaction = 75
> << tlv_length = 138
> << message = "Get System Selection Preference" (0x0034)
> << TLV:
> << type = "Result" (0x02)
> << length = 4
> << value = 00:00:00:00
> << translated = SUCCESS
> << TLV:
> << type = "Emergency mode" (0x10)
> << length = 1
> << value = 00
> << translated = no
> << TLV:
> << type = "Mode Preference" (0x11)
> << length = 2
> << value = 10:00
> << translated = lte
> << TLV:
> << type = "Band Preference" (0x12)
> << length = 8
> << value = 00:00:00:00:00:00:00:00
> << translated = (null)
> << TLV:
> << type = "LTE Band Preference" (0x15)
> << length = 8
> << value = 80:00:00:00:00:00:00:00
> << translated = 8
> << TLV:
> << type = "Network Selection Preference" (0x16)
> << length = 1
> << value = 00
> << translated = automatic
> << TLV:
> << type = "Service Domain Preference" (0x18)
> << length = 4
> << value = 02:00:00:00
> << translated = cs-ps
> << TLV:
> << type = "GSM WCDMA Acquisition Order Preference" (0x19)
> << length = 4
> << value = 01:00:00:00
> << translated = gsm
> << TLV:
> << type = "Acquisition Order Preference" (0x1c)
> << length = 5
> << value = 04:08:00:00:04
> << translated = { [0] = 'lte ' [1] = 'none ' [2] = 'none ' [3] = 'gsm
> '}
> << TLV:
> << type = 0x1d
> << length = 4
> << value = 00:00:00:00
> << TLV:
> << type = 0x1f
> << length = 4
> << value = 02:00:00:00
> << TLV:
> << type = 0x20
> << length = 4
> << value = 01:00:00:00
> << TLV:
> << type = 0x24
> << length = 8
> << value = 02:00:00:00:00:00:00:00
> << TLV:
> << type = 0x25
> << length = 8
> << value = 9F:18:0E:0A:40:00:00:00
> << TLV:
> << type = 0x26
> << length = 8
> << value = 9F:18:0E:0A:00:00:00:00
> << TLV:
> << type = 0x27
> << length = 17
> << value = 04:08:00:00:00:0A:00:00:00:0B:00:00:00:04:00:00:00
>
> Resetting the modem doesn't help either. I am not sure whether this mailing
> list is the correct forum for this question or if I should ask Quectel
> about this. Any help is very much appreciated.
>
Hi Fredrik,
when looking at TLVs 0x24 and 0x25 one can see that their values when
interpreted as a LTE bandmask seem to match the values supported by the
BG96 for Cat-M1 and CAT-NB1.
My guess is that there would also be two additional extended LTE band
preference TLVs for MDM9205-based devices like Quectel BG95 and
Telit ME910G1 since they may support LTE bands > 64:
Regards,
Reinhard
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: libmbim 1.24.0 slowing down MM startup
Hey, > > I'm testing 1.14.0 and finding that libmbim has significantly slowed down MM > startup. I'm using EM7565 in MBIM mode. Please see below snippets from log > which highlight the delay. As you can see "couldn't load carrier config; > couldn't load SUPL; assistance data" are causing this slowness. > This looks like QMI over MBIM indications not working properly, how strange. Could you retry debug logging but also including mbim-proxy logs? E.g.: // stop ModemManager and make sure mbim-proxy is not running $ sudo /usr/libexec/mbim-proxy --verbose --no-exit // in another terminal, start ModemManager in debug mode -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Quectel BG96: band selection does not take effect
Hey! > We are having trouble with band selection on the Quectel BG96. It seems the > band selection command executes successfully, but the modem always stays on > LTE band 20 regardless of the band selection preference. We are using > ModemManager version 1.10.0 patched with commit f2c878e7 to allow setting the > band preference without SIGSEGV. > > Here we try to configure the modem to avoid band 20. > > $ mmcli -m 0 --set-current-bands='eutran-8' > successfully set current bands in the modem > $ mmcli -m 0 > > General |dbus path: /org/freedesktop/ModemManager1/Modem/0 >|device id: 6efb0cb14e9698c55a05a847f5c774f135ac7011 > > Hardware | manufacturer: Quectel >|model: 0 >| revision: BG96MAR02A10M1G >| h/w revision: 1 >|supported: gsm-umts, lte >| current: gsm-umts, lte >| equipment id: 860536043902982 > > System | device: > /sys/devices/platform/soc/3080.aips-bus/30b2.usb/ci_hdrc.1/usb2/2-1 >| drivers: option1, qmi_wwan >| plugin: Quectel >| primary port: cdc-wdm0 >|ports: ttyUSB0 (qcdm), ttyUSB1 (gps), ttyUSB2 > (at), >| cdc-wdm0 (qmi), wwan0 (net), ttyUSB3 (at) > > Status | lock: sim-pin2 >| unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), > sim-puk2 (10) >|state: connected >| power state: on >| access tech: lte >| signal quality: 100% (recent) > > Modes|supported: allowed: 2g; preferred: none >| allowed: 4g; preferred: none >| allowed: 2g, 4g; preferred: 4g >| allowed: 2g, 4g; preferred: 2g >| current: allowed: 4g; preferred: none > > Bands|supported: egsm, dcs, pcs, g850, eutran-1, eutran-2, > eutran-3, >| eutran-4, eutran-5, eutran-8, eutran-12, > eutran-13, eutran-17, >| eutran-18, eutran-19, eutran-20, eutran-39 >| current: eutran-8 > > IP |supported: ipv4, ipv6, ipv4v6 > > 3GPP | imei: >| operator id: 24201 >|operator name: TELENOR >| registration: home > > 3GPP EPS | ue mode of operation: csps-2 > > SIM |dbus path: /org/freedesktop/ModemManager1/SIM/0 > > Bearer |dbus path: /org/freedesktop/ModemManager1/Bearer/0 > $ qmicli -d /dev/cdc-wdm0 -p --nas-get-rf-band-info > [/dev/cdc-wdm0] Successfully got RF band info > Radio Interface: 'lte' > Active Band Class: 'eutran-20' > Active Channel:'6400' > $ mmcli -m 0 --command="AT+QENG=\"servingcell\"" > response: '+QENG: > "servingcell","NOCONN","CAT-M","FDD",242,01,105ED03,496,6400,20,3,3,78BF,-51,-6,-28,24,76 > > Relevant part of the ModemManager log: > > ModemManager[6395]: [1594121691.792737] Setting new list of bands: > 'eutran-8' > ModemManager[6395]: [/dev/cdc-wdm0] sent message... > << RAW: > << length = 39 > << data = > 01:26:00:00:03:01:00:4A:00:33:00:1A:00:17:01:00:01:15:08:00:80:00:00:00:00:00:00:00:12:08:00:00:00:00:00:00:00:00:00 > ModemManager[6395]: [/dev/cdc-wdm0] sent generic request (translated)... > << QMUX: > << length = 38 > << flags = 0x00 > << service = "nas" > << client = 1 > << QMI: > << flags = "none" > << transaction = 74 > << tlv_length = 26 > << message = "Set System Selection Preference" (0x0033) > << TLV: > << type = "Change Duration" (0x17) > << length = 1 > << value = 01 > << translated = permanent > << TLV: > << type = "LTE Band Preference" (0x15) > << length = 8 > << value = 80:00:00:00:00:00:00:00 > << translated = 8 > << TLV: > << type = "Band Preference" (0x12) > << length = 8 > << value = 00:00:00:00:00:00:00:00 > << translated = (null) > ModemManager[6395]: [/dev/cdc-wdm0] received message... > << RAW: > << length = 20 > << data = 01:13:00:80:03:01:02:4A:00:33:00:07:00:02:04:00:00:00:00:00 > ModemManager[6395]: [/dev/cd
RE: libmbim 1.24.0 slowing down MM startup
Sorry, logs got mingled in previous post. Please find it attached -Original Message- From: Amol Lad Sent: Tuesday, 7 July 2020 5:37 PM To: ModemManager (development) Subject: libmbim 1.24.0 slowing down MM startup Hi Aleksander, I'm testing 1.14.0 and finding that libmbim has significantly slowed down MM startup. I'm using EM7565 in MBIM mode. Please see below snippets from log which highlight the delay. As you can see "couldn't load carrier config; couldn't load SUPL; assistance data" are causing this slowness. MM 1.12.6 or MM 1.14.0 + libmbim 1.24.0 Jul 7 11:42:59 [6570]: [modem0] QMI-based capability and mode switching support enabled Jul 7 11:43:04 [6570]: [modem0] couldn't load carrier config: Operation timed out Jul 7 11:43:05 [6570]: [modem0/sim0] couldn't load list of emergency numbers: Failed to parse CRSM query result '+CRSM: 148,8,""' Jul 7 11:43:15 [6570]: [modem0] couldn't load SUPL server: Failed to receive indication with the current server settings Jul 7 11:43:25 [6570]: [modem0] couldn't load supported assistance data types: Failed to receive indication with the predicted orbits data source Jul 7 11:43:25 [6570]: [modem0] state changed (unknown -> disabled) MM 1.12.6 + libmbim 1.22.0 Jul 7 11:38:45 [6529]: QMI-based capability and mode switching support enabled Jul 7 11:38:46 [6529]: couldn't load list of Emergency Numbers: 'Failed to parse CRSM query result '+CRSM: 148,8,""'' Jul 7 11:38:46 [6529]: Modem: state changed (unknown -> disabled) Bearer connection is also slow with libmbim 1.24.0. If I switch to 1.22.0 in below then delay between registered and connect is not seen MM 1.12.6 + libmbim 1.24.0 Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> registered) Jul 7 12:00:47 [6548]: Simple connect state (6/8): Bearer Jul 7 12:00:47 [6548]: Simple connect state (7/8): Connect Jul 7 12:00:47 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Jul 7 12:00:51 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) MM 1.12.6 or MM 1.14.0 + LIBMBIM 1.24.0 Jul 7 11:42:59 [6570]: [modem0] QMI-based capability and mode switching support enabled Jul 7 11:43:04 [6570]: [modem0] couldn't load carrier config: Operation timed out Jul 7 11:43:05 [6570]: [modem0/sim0] couldn't load list of emergency numbers: Failed to parse CRSM query result '+CRSM: 148,8,""' Jul 7 11:43:15 [6570]: [modem0] couldn't load SUPL server: Failed to receive indication with the current server settings Jul 7 11:43:25 [6570]: [modem0] couldn't load supported assistance data types: Failed to receive indication with the predicted orbits data source Jul 7 11:43:25 [6570]: [modem0] state changed (unknown -> disabled) MM 1.12.6 + LIBMBIM 1.22.0 Jul 7 11:38:45 [6529]: QMI-based capability and mode switching support enabled Jul 7 11:38:46 [6529]: couldn't load list of Emergency Numbers: 'Failed to parse CRSM query result '+CRSM: 148,8,""'' Jul 7 11:38:46 [6529]: Modem: state changed (unknown -> disabled) MM 1.12.6 + LIBMBIM 1.24.0 (delay between registered and connect) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> registered) Jul 7 12:00:47 [6548]: Simple connect state (6/8): Bearer Jul 7 12:00:47 [6548]: Simple connect state (7/8): Connect Jul 7 12:00:47 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Jul 7 12:00:51 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
libmbim 1.24.0 slowing down MM startup
Hi Aleksander, I'm testing 1.14.0 and finding that libmbim has significantly slowed down MM startup. I'm using EM7565 in MBIM mode. Please see below snippets from log which highlight the delay. As you can see "couldn't load carrier config; couldn't load SUPL; assistance data" are causing this slowness. MM 1.12.6 or MM 1.14.0 + libmbim 1.24.0 Jul 7 11:42:59 [6570]: [modem0] QMI-based capability and mode switching support enabled Jul 7 11:43:04 [6570]: [modem0] couldn't load carrier config: Operation timed out Jul 7 11:43:05 [6570]: [modem0/sim0] couldn't load list of emergency numbers: Failed to parse CRSM query result '+CRSM: 148,8,""' Jul 7 11:43:15 [6570]: [modem0] couldn't load SUPL server: Failed to receive indication with the current server settings Jul 7 11:43:25 [6570]: [modem0] couldn't load supported assistance data types: Failed to receive indication with the predicted orbits data source Jul 7 11:43:25 [6570]: [modem0] state changed (unknown -> disabled) MM 1.12.6 + libmbim 1.22.0 Jul 7 11:38:45 [6529]: QMI-based capability and mode switching support enabled Jul 7 11:38:46 [6529]: couldn't load list of Emergency Numbers: 'Failed to parse CRSM query result '+CRSM: 148,8,""'' Jul 7 11:38:46 [6529]: Modem: state changed (unknown -> disabled) Bearer connection is also slow with libmbim 1.24.0. If I switch to 1.22.0 in below then delay between registered and connect is not seen MM 1.12.6 + libmbim 1.24.0 Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) Jul 7 12:00:21 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> registered) Jul 7 12:00:47 [6548]: Simple connect state (6/8): Bearer Jul 7 12:00:47 [6548]: Simple connect state (7/8): Connect Jul 7 12:00:47 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Jul 7 12:00:51 [6548]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Quectel BG96: band selection does not take effect
Hi, We are having trouble with band selection on the Quectel BG96. It seems the band selection command executes successfully, but the modem always stays on LTE band 20 regardless of the band selection preference. We are using ModemManager version 1.10.0 patched with commit f2c878e7 to allow setting the band preference without SIGSEGV. Here we try to configure the modem to avoid band 20. $ mmcli -m 0 --set-current-bands='eutran-8' successfully set current bands in the modem $ mmcli -m 0 General |dbus path: /org/freedesktop/ModemManager1/Modem/0 |device id: 6efb0cb14e9698c55a05a847f5c774f135ac7011 Hardware | manufacturer: Quectel |model: 0 | revision: BG96MAR02A10M1G | h/w revision: 1 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 860536043902982 System | device: /sys/devices/platform/soc/3080.aips-bus/30b2.usb/ci_hdrc.1/usb2/2-1 | drivers: option1, qmi_wwan | plugin: Quectel | primary port: cdc-wdm0 |ports: ttyUSB0 (qcdm), ttyUSB1 (gps), ttyUSB2 (at), | cdc-wdm0 (qmi), wwan0 (net), ttyUSB3 (at) Status | lock: sim-pin2 | unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10) |state: connected | power state: on | access tech: lte | signal quality: 100% (recent) Modes|supported: allowed: 2g; preferred: none | allowed: 4g; preferred: none | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | current: allowed: 4g; preferred: none Bands|supported: egsm, dcs, pcs, g850, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-8, eutran-12, eutran-13, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-39 | current: eutran-8 IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: | operator id: 24201 |operator name: TELENOR | registration: home 3GPP EPS | ue mode of operation: csps-2 SIM |dbus path: /org/freedesktop/ModemManager1/SIM/0 Bearer |dbus path: /org/freedesktop/ModemManager1/Bearer/0 $ qmicli -d /dev/cdc-wdm0 -p --nas-get-rf-band-info [/dev/cdc-wdm0] Successfully got RF band info Radio Interface: 'lte' Active Band Class: 'eutran-20' Active Channel:'6400' $ mmcli -m 0 --command="AT+QENG=\"servingcell\"" response: '+QENG: "servingcell","NOCONN","CAT-M","FDD",242,01,105ED03,496,6400,20,3,3,78BF,-51,-6,-28,24,76 Relevant part of the ModemManager log: ModemManager[6395]: [1594121691.792737] Setting new list of bands: 'eutran-8' ModemManager[6395]: [/dev/cdc-wdm0] sent message... << RAW: << length = 39 << data = 01:26:00:00:03:01:00:4A:00:33:00:1A:00:17:01:00:01:15:08:00:80:00:00:00:00:00:00:00:12:08:00:00:00:00:00:00:00:00:00 ModemManager[6395]: [/dev/cdc-wdm0] sent generic request (translated)... << QMUX: << length = 38 << flags = 0x00 << service = "nas" << client = 1 << QMI: << flags = "none" << transaction = 74 << tlv_length = 26 << message = "Set System Selection Preference" (0x0033) << TLV: << type = "Change Duration" (0x17) << length = 1 << value = 01 << translated = permanent << TLV: << type = "LTE Band Preference" (0x15) << length = 8 << value = 80:00:00:00:00:00:00:00 << translated = 8 << TLV: << type = "Band Preference" (0x12) << length = 8 << value = 00:00:00:00:00:00:00:00 << translated = (null) ModemManager[6395]: [/dev/cdc-wdm0] received message... << RAW: << length = 20 << data = 01:13:00:80:03:01:02:4A:00:33:00:07:00:02:04:00:00:00:00:00 ModemManager[6395]: [/dev/cdc-wdm0] received generic response (translated)... << QMUX: << length = 19 << flags = 0x80 << service = "nas" << client = 1 << QMI: << flags = "response" << transaction = 74 << t
Re: Feature request: 'any' keyword for bearers
Hey Nick, > My favourite feature of the 1.14 release is the ‘any’ keyword for modems and > SIMs. Any chance we can get the same for bearers? > Well, what to say... :D I think the "any" keyword makes sense for modems and SIMs when you're sure you have one single modem in the system. It's very neat to integrate scripts that make use of mmcli. Now, for bearers, the logic is not so clear, because with one single modem you may still have multiple bearers, but we could still follow the same reasoning and warn that it will find the *first* bearer object even if there may be more. If the system uses the Simple interface, where we kind of guarantee that only one bearer object is used, this may also work quite cleanly. Patches welcome! :D Please open a new Issue in gitlab if you'd like this tracked. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: [Resolved] Re: Issue building MM 1.14 on Ubuntu 18.04
I commented those two lines (and also PKG_FIXUP:=autoreconf) and build is
successful.
I'm not sure why those lines are there. Maybe, Nick will have some idea.
Amol
-Original Message-
From: Aleksander Morgado
Sent: Tuesday, 7 July 2020 2:04 PM
To: Amol Lad
Cc: Nick ; ModemManager (development)
Subject: Re: [Resolved] Re: Issue building MM 1.14 on Ubuntu 18.04
Hey Amol,
> After commenting PKG_FIXUP:=autoreconf, I'm getting below error:
>
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash
> /home/alad/openwrt/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/Mode
> mManager-1.14.0/missing aclocal-1.16 -I m4
> /home/alad/openwrt/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/Mode
> mManager-1.14.0/missing: line 81: aclocal-1.16: command not found
>
> OpenWrt "master" has automake version 1.15.1.
>
> Any suggestion?
>
That may be due to these lines that modify configure.ac, which force an
autoreconf either way even if AUTORECONF=1 not given:
$(SED) 's|^\(GLIB_MKENUMS\)=.*|\1=$(STAGING_DIR_HOSTPKG)/bin/glib-mkenums|'
\
$(PKG_BUILD_DIR)/configure.ac
$(SED)
's|^\(GDBUS_CODEGEN\)=.*|\1=$(STAGING_DIR_HOSTPKG)/bin/gdbus-codegen|'
\
$(PKG_BUILD_DIR)/configure.ac
Why are those lines in the Makefile? This looks like a hack to workaround some
build system error. Are we not using the correct glib-mkenums or gdbus-codegen
from staging if those lines are removed?
Both libmbim and libqmi also use glib-mkenums, and they don't have those lines.
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: [Resolved] Re: Issue building MM 1.14 on Ubuntu 18.04
Hey Amol,
> After commenting PKG_FIXUP:=autoreconf, I'm getting below error:
>
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash
> /home/alad/openwrt/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.14.0/missing
> aclocal-1.16 -I m4
> /home/alad/openwrt/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.14.0/missing:
> line 81: aclocal-1.16: command not found
>
> OpenWrt "master" has automake version 1.15.1.
>
> Any suggestion?
>
That may be due to these lines that modify configure.ac, which force
an autoreconf either way even if AUTORECONF=1 not given:
$(SED) 's|^\(GLIB_MKENUMS\)=.*|\1=$(STAGING_DIR_HOSTPKG)/bin/glib-mkenums|'
\
$(PKG_BUILD_DIR)/configure.ac
$(SED)
's|^\(GDBUS_CODEGEN\)=.*|\1=$(STAGING_DIR_HOSTPKG)/bin/gdbus-codegen|'
\
$(PKG_BUILD_DIR)/configure.ac
Why are those lines in the Makefile? This looks like a hack to
workaround some build system error. Are we not using the correct
glib-mkenums or gdbus-codegen from staging if those lines are removed?
Both libmbim and libqmi also use glib-mkenums, and they don't have those lines.
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: [Resolved] Re: Issue building MM 1.14 on Ubuntu 18.04
Hi Aleksander,
After commenting PKG_FIXUP:=autoreconf, I'm getting below error:
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash
/home/alad/openwrt/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.14.0/missing
aclocal-1.16 -I m4
/home/alad/openwrt/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.14.0/missing:
line 81: aclocal-1.16: command not found
OpenWrt "master" has automake version 1.15.1.
Any suggestion?
Amol
-Original Message-
From: ModemManager-devel On
Behalf Of Aleksander Morgado
Sent: Tuesday, 7 July 2020 12:20 PM
To: Nick
Cc: ModemManager (development)
Subject: Re: [Resolved] Re: Issue building MM 1.14 on Ubuntu 18.04
Hey Nick
> Fixed - Issue was resolved by including autoconf-archive in the Openwrt
> toolchain, as demonstrated by this commit.
> https://github.com/openwrt/openwrt/commit/3c1d1d4332c7fbaccea01b92b28f
> 6d96f7222492
>
You're being forced to use autoconf-archive in the openwrt setup because the
ModemManager package in openwrt has:
PKG_FIXUP:=autoreconf
None of libqmi, libmbim, ModemManager should require autoreconf if building
from a source tarball, only when building from git. By explicitly running
autoreconf, the build is trying to rebuild the configure script instead of
using the provided one in the tarball.
I would definitely remove that line if possible. I think it was already removed
from libqmi and libmbim packages.
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Feature request: 'any' keyword for bearers
Hey, My favourite feature of the 1.14 release is the ‘any’ keyword for modems and SIMs. Any chance we can get the same for bearers? * mmcli: ** Added a new 'any' lookup keyword for the --modem and --sim options, useful when the system is only expected to have one single device. Best, Nick ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
