@daniel It seems you know your way around the RUT955. Can you help me pleeeease?
I tested some more uqmi commands but really, --get-signal-info is the only one which gives any positive feedback. all the other commands don't give a reply or give errors...
@sajonasra I'm not sure if I ever tried with a PIN code set. To exclude PIN-code related modem quirks, try disabling PIN entirely using another device (cellphone) and remove the PIN option from UCI. If that works, we at least know where to dig...
Hey daniel,
thanks for the info. so, PIN switched off. I took out the SIM from UCI, meaning that I deleted the entry.
Or is there any other way I have to deactivate it?
The reaction of the router is "Call failed".
Feel free to submit an official patch, or ask a developer to do so. As this seems to be a reasonable precaution, anyway. (Which I always fiddle myself using AT-cmd for the PPP-connection via EC25).
How do I get the Modem Running? Do I need to change the GPIO Pins in /etc/board.d/03_gpio_switches ? If I do that, dmesg says : export_store: invalid GPIO 44 export_store: invalid GPIO 45 export_store: invalid GPIO 33
Using RUT955 myself, with EC25. Running very well, both in USA and in Germany and in Bulgaria. Using recent openwrt, custom built.
Assuming, you also have an EC25, make shure, it is the correct subversion, depending upon your location.
And flash newest firmware to the EC25.
Finally: Which version of openwrt, are you using PPP or QMI ?
There are two (quite different) version of the RUT955, both with EC25 modem, and what you are describing sounds like you have flashed the wrong image for the hardware you got.
older: teltonika_rut955-h7v3c0 => need screwdriver to open case in order to access SIM cards
newer: teltonika_rut955 => sim card slots accessible from outside, comes with metal pin to drag them out.
This looks like the correct image for that version of the device. Please share output of logread after boot and also content of /etc/config/network so we can see what's going on there.
Sat Mar 5 09:05:28 2022 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyS13, subsystem=tty, sysfspath=/sys/devices/platform/serial8250/tty/ttyS13
Sat Mar 5 09:05:28 2022 user.notice ModemManager: hotplug: event reported: action=add, name=ttyS13, subsystem=tty
Sat Mar 5 09:05:28 2022 authpriv.notice dropbear[3300]: Auth succeeded with blank password for 'root' from 192.168.6.10:55188
Sat Mar 5 09:05:28 2022 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyATH1, subsystem=tty, sysfspath=/sys/devices/platform/ahb/ahb:apb/18500000.uart/tty/ttyATH1
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: event reported: action=add, name=ttyATH1, subsystem=tty
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyACM0, subsystem=tty, sysfspath=/sys/devices/platform/ahb/1b000000.usb/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM0
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: event reported: action=add, name=ttyACM0, subsystem=tty
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: no need to wait for modem at sysfs path /sys/devices/platform/ahb/1b000000.usb/usb1/1-1/1-1.3
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: cached event found: action=add, name=wlan0, subsystem=net, sysfspath=/sys/devices/platform/ahb/18100000.wmac/net/wlan0
Sat Mar 5 09:05:29 2022 user.notice ModemManager: hotplug: event reported: action=add, name=wlan0, subsystem=net
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: cached event found: action=add, name=br-lan, subsystem=net, sysfspath=/sys/devices/virtual/net/br-lan
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: event reported: action=add, name=br-lan, subsystem=net
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: cached event found: action=add, name=eth0.1, subsystem=net, sysfspath=/sys/devices/virtual/net/eth0.1
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: event reported: action=add, name=eth0.1, subsystem=net
Sat Mar 5 09:05:30 2022 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Sat Mar 5 09:05:32 2022 daemon.info [2088]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/ahb/1b000000.usb/usb1/1-1/1-1.3': not supported by any plugin
Sat Mar 5 09:05:32 2022 daemon.info [2088]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/ahb/18100000.wmac': not supported by any plugin
This looks a bit wrong. Afaik ttyUSB1 is the GPS interface. Where did you copy that config from? I guess it's better you just use the LuCI frontends for either uqmi or modemmanager to create the config, as in that way you will end up with a working configuration.
Ok, so probably the modem is not powered on for some reason, and that could be because you got yet another newer version of the device sold under the same name.
Please share the output of dmesg so we can know more...