Re: ModemManager and Iridium 9522b
Hi Aleksander, I have a rule in place, but I'm having some trouble with this new build w/ udev that I've implemented. Getting this undefined symbol error. Using nm I see that a number of the symbols in ModemManager are undefined. Was there something I missed during build? pi@raspberrypi:/ $ sudo /usr/sbin/ModemManager --debug ModemManager[3940]: [1523895791.274715] ModemManager (version 1.7.991) starting in system bus... ModemManager[3940]: [1523895791.294654] Bus acquired, creating manager... (ModemManager:3940): GLib-GObject-WARNING **: /build/glib2.0-tTvduh/glib2.0-2.42.1/./gobject/gsignal.c:2461: signal 'handle-report-kernel-event' is invalid for instance '0x1ed960' of type 'MMBaseManager' ModemManager[3940]: [1523895791.298455] [filter] created ModemManager[3940]: [1523895791.298712] [filter] explicit whitelist: yes ModemManager[3940]: [1523895791.298810] [filter] virtual devices forbidden: yes ModemManager[3940]: [1523895791.298881] [filter] net devices allowed:yes ModemManager[3940]: [1523895791.298955] [filter] cdc-wdm devices allowed:yes ModemManager[3940]: [1523895791.299030] [filter] tty devices: ModemManager[3940]: [1523895791.299097] [filter] blacklist applied:yes ModemManager[3940]: [1523895791.299165] [filter] manual scan only applied: yes ModemManager[3940]: [1523895791.299231] [filter] platform driver check:yes ModemManager[3940]: [1523895791.299296] [filter] driver check: no ModemManager[3940]: [1523895791.299366] [filter] cdc-acm interface check: no ModemManager[3940]: [1523895791.299433] [filter] with net check: no ModemManager[3940]: [1523895791.299497] [filter] default: allowed ModemManager[3940]: [1523895791.301395] [plugin manager] looking for plugins in '/usr/lib/ModemManager' ModemManager[3940]: [1523895791.327725] [plugin manager] loaded plugin 'Altair LTE' ModemManager[3940]: [1523895791.329527] [plugin manager] loaded plugin 'Haier' ModemManager[3940]: [1523895791.331273] [plugin manager] loaded plugin 'Motorola' ModemManager[3940]: [1523895791.333617] [plugin manager] loaded plugin 'Dell' ModemManager[3940]: [1523895791.335778] [plugin manager] loaded plugin 'Sierra' ModemManager[3940]: [1523895791.337920] [plugin manager] loaded plugin 'X22X' ModemManager[3940]: [1523895791.340636] [plugin manager] loaded plugin 'Huawei' ModemManager[3940]: [1523895791.342376] [plugin manager] loaded plugin 'Via CBP7' ModemManager[3940]: [1523895791.343850] [plugin manager] loaded plugin 'MTK' ModemManager[3940]: [1523895791.345617] [plugin manager] loaded plugin 'Pantech' ModemManager[3940]: [1523895791.347314] [plugin manager] loaded plugin 'Novatel' ModemManager[3940]: [1523895791.349727] [plugin manager] loaded plugin 'Option' ModemManager[3940]: [1523895791.351436] [plugin manager] loaded plugin 'Longcheer' ModemManager[3940]: [1523895791.352973] [plugin manager] loaded plugin 'AnyDATA' ModemManager[3940]: [1523895791.354648] [plugin manager] loaded plugin 'Quectel' ModemManager[3940]: [1523895791.365374] [plugin manager] loaded plugin 'Sierra (legacy)' ModemManager[3940]: [1523895791.367073] [plugin manager] loaded plugin 'Samsung' ModemManager[3940]: [1523895791.368915] [plugin manager] loaded plugin 'Telit' ModemManager[3940]: [1523895791.370729] [plugin manager] loaded plugin 'Thuraya' ModemManager[3940]: [1523895791.376274] [plugin manager] loaded plugin 'Cinterion' ModemManager[3940]: [1523895791.380341] [plugin manager] loaded plugin 'Option High-Speed' ModemManager[3940]: [1523895791.382610] [plugin manager] loaded plugin 'Generic' ModemManager[3940]: [1523895791.395142] [plugin manager] loaded plugin 'Novatel LTE' ModemManager[3940]: [1523895791.397750] [plugin manager] loaded plugin 'Linktop' ModemManager[3940]: [1523895791.400546] [plugin manager] loaded plugin 'Nokia (Icera)' ModemManager[3940]: [1523895791.402262] [plugin manager] loaded plugin 'Nokia' ModemManager[3940]: [1523895791.403920] [plugin manager] loaded plugin 'Wavecom' ModemManager[3940]: [1523895791.406486] [plugin manager] loaded plugin 'Iridium' ModemManager[3940]: [1523895791.408795] [plugin manager] loaded plugin 'Ericsson MBM' ModemManager[3940]: [1523895791.410306] [plugin manager] loaded plugin 'SimTech' ModemManager[3940]: [1523895791.412066] [plugin manager] loaded plugin 'ZTE' ModemManager[3940]: [1523895791.413886] [plugin manager] loaded plugin 'u-blox' ModemManager[3940]: [1523895791.414222] [plugin manager] successfully loaded 32 plugins ModemManager[3940]: [1523895791.418825] Service name 'org.freedesktop.ModemManager1' was acquired ModemManager[3940]: [1523895791.419105] Starting automatic device scan... ModemManager[3940]: [1523895791.434350] Finished device scan... /usr/sbin/ModemManager: symbol lookup error: /usr/sbin/ModemManager: undefined symbol: mm_kernel_event_properties_get_type On Fri, Aug 4, 2017 at 8:51
Re: ModemManager and Iridium 9522b
Hey, > > I have a rule in place, but I'm having some trouble with this new build w/ > udev that I've implemented. Getting this undefined symbol error. Using nm > I see that a number of the symbols in ModemManager are undefined. Was there > something I missed during build? > > pi@raspberrypi:/ $ sudo /usr/sbin/ModemManager --debug > ModemManager[3940]: [1523895791.274715] ModemManager (version > 1.7.991) starting in system bus... > ModemManager[3940]: [1523895791.294654] Bus acquired, creating > manager... > > (ModemManager:3940): GLib-GObject-WARNING **: > /build/glib2.0-tTvduh/glib2.0-2.42.1/./gobject/gsignal.c:2461: signal > 'handle-report-kernel-event' is invalid for instance '0x1ed960' of type > 'MMBaseManager' How did you build and install this custom build you have? This totally looks like a new ModemManager binary trying to run with an older libmm-glib library. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: ModemManager and Iridium 9522b
Hey Eric,
>
> Thanks for the quick reply! I don't think that is possible. I don't think
> it even likes 38400. See below from the manual:
>
> 5.121 +IPR - Fixed DTE Rate (Revised Implementation)
>
> This implementation applies to the 9522A/9505A IS060xx and later and all
> software releases for
> 9522B, 9555(A), 9523, 9575, 9601, 9602, 9602-SB, and 9603.
>
> Set Command: +IPR=[,]
>
> Set the data rate at which the ISU will accept commands. The change in data
> rate takes effect after the
> result code (e.g., OK) is received by the DTE.
> takes the following values:
>
> 1 600 bps
> 2 1200 bps
> 3 2400 bps
> 4 4800 bps
> 5 9600 bps
> 6 19200 bps (default)
> 7 38400 bps
>
> Note: The use of 38400 bps with ISU models “9505” or “9522” is not
> recommended because the ISU
> can not handle this rate without losing some bits of data.
>
Ok, so then you'll need to manually specify the baudrate that is going
to be used to open the port. You can do this only in ModemManager git
master (not in 1.6.x or before), by specifying a custom udev rule
like, see:
https://lists.freedesktop.org/archives/modemmanager-devel/2017-March/004075.html
For a USB modem, it would be something like:
# vim /lib/udev/rules.d/77-mm-serial-iridium.rules
ACTION!="add|change|move", GOTO="mm_serial_iridium_end"
SUBSYSTEM=="tty", ATTRS{idVendor}=="1edd", ENV{ID_MM_TTY_BAUDRATE}="19200"
LABEL="mm_serial_iridium_end"
For a serial modem, try to use the DEVPATH instead (as there's no
vid:pid to match), e.g.:
# vim /lib/udev/rules.d/77-mm-serial-iridium.rules
ACTION!="add|change|move", GOTO="mm_serial_iridium_end"
DEVPATH=="/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/*",
ENV{ID_MM_TTY_BAUDRATE}="19200"
LABEL="mm_serial_iridium_end"
Once the rule is in place:
$ sudo udevadm control --reload
$ sudo udevadm trigger
And restart ModemManager.
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: ModemManager and Iridium 9522b
Hey > > I am trying to get my Iridium 9522b modem recognized using mmcli. It is > connected on /dev/ttyUSB2 with 19200, 8, N, 1. I can successfully > communicate via AT commands through pyserial or minicom, so I'm confident > that it is functioning. > > Below are the scan and list outputs from mmcli as well as lsusb. The > usb-serial cable connected to the Iridium is Bus001 Device005. > > pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ sudo mmcli -S > successfully requested to scan devices > pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ mmcli -L > > No modems were found > > pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ lsusb > Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, > Ltd FT232 USB-Serial (UART) IC > Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial > Port > Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, > Ltd FT232 USB-Serial (UART) IC > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 > Fast Ethernet Adapter > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ > > I know that there is a plugin for Iridium modems, specifically this 9522b > that I am using. Is there something I need to do to get it to detect it? > Can you update the baudrate configuration in the modem itself to be 57600bps? Also, could you run ModemManager in debug mode to get full debug logs? See: https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
ModemManager and Iridium 9522b
Hello, I am trying to get my Iridium 9522b modem recognized using mmcli. It is connected on /dev/ttyUSB2 with 19200, 8, N, 1. I can successfully communicate via AT commands through pyserial or minicom, so I'm confident that it is functioning. Below are the scan and list outputs from mmcli as well as lsusb. The usb-serial cable connected to the Iridium is Bus001 Device005. pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ sudo mmcli -S successfully requested to scan devices pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ mmcli -L No modems were found pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ lsusb Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:/usr/lib/arm-linux-gnueabihf/ModemManager $ I know that there is a plugin for Iridium modems, specifically this 9522b that I am using. Is there something I need to do to get it to detect it? Thanks, Eric -- Eric Younkin Physical Scientist NOAA OCS, Hydrographic Systems and Technology Branch 1315 East-West Highway N/CS11, Room 7854 Silver Spring, MD 20910 Office: 301-713-2809 x139 Cell: 828-331-8197 ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
