RM500Q-AE latest linux drivers and installation manual

jfrog · June 30, 2023, 1:18pm

Sorry, I cannot validate mbim tools operation on my side at the moment.
But please show the output of cat /etc/mbim-network.conf

vedrax7 · June 30, 2023, 1:25pm

my bad the APN spelling was wrong

pi@RevPi45698:~ $ sudo cat /etc/mbim-network.conf
APM=internet
APN_USER=ipa
APN_PASS=xxxxx
APN_AUTH=PAP
PROXY=yes

I entered the above details in the .conf file and again ran the mbim-network start, set ip script and then ping. The connection was setup I could get the ping. I stopped the ping and tried ping command again and it gave the same error: network is unreachable.
Now mbim-network start command has this output:

root@RevPi45698:/home/pi# mbim-network /dev/cdc-wdm0 start
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
Loading profile at /etc/mbim-network.conf…
APN: internet
APN auth protocol: PAP
APN user: ipa
APN password: xxxxxx
mbim-proxy: yes
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 8
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘999400000256440’ SIM ICCID: ‘8900099100002144403F’ Ready info: ‘none’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 4)
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=4 --no-close --device-open-proxy’…
[/dev/cdc-wdm0] Registration status: Network error: ‘unknown’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘custom’ Current cellular class: ‘gsm’ Provider ID: ‘99940’ Provider name: ‘DA’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘6’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 6)
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close --device-open-proxy’…
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 8)
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=’‘,auth=‘PAP’,username=‘ipa’,password=‘xxxxx’ --no-open=8 --no-close --device-open-proxy’…

jfrog · June 30, 2023, 1:51pm

Do you have the same with “APN” corrected ?

vedrax7 · June 30, 2023, 2:00pm

this is the current output with “APN” corrected

root@RevPi45698:/home/pi# ping 8.8.8.8
connect: Network is unreachable
root@RevPi45698:/home/pi# mbim-network /dev/cdc-wdm0 status
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
Loading profile at /etc/mbim-network.conf…
APN: internet
APN auth protocol: PAP
APN user: ipa
APN password: fffffff
mbim-proxy: yes
Getting status with ‘mbimcli -d /dev/cdc-wdm0 --query-connection-state --device-open-proxy’…
Status: deactivated
root@RevPi45698:/home/pi# mbim-network /dev/cdc-wdm0 start
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
Loading profile at /etc/mbim-network.conf…
APN: internet
APN auth protocol: PAP
APN user: ipa
APN password: zzzzz
mbim-proxy: yes
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘999400000256440’ SIM ICCID: ‘8900099100002144403F’ Ready info: ‘none’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 4)
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=4 --no-close --device-open-proxy’…
[/dev/cdc-wdm0] Registration status: Network error: ‘unknown’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘custom’ Current cellular class: ‘gsm’ Provider ID: ‘99940’ Provider name: ‘DA’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘6’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 6)
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close --device-open-proxy’…
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 8)
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘internet’,auth=‘PAP’,username=‘ipa’,password=‘xxxxx’ --no-open=8 --no-close --device-open-proxy’…
error: couldn’t get IP configuration response message: Transaction timed out
Network start failed
[/dev/cdc-wdm0] Successfully connected [/dev/cdc-wdm0] Connection status: Session ID: ‘0’ Activation state: ‘activated’ Voice call state: ‘none’ IP type: ‘ipv4’ Context type: ‘internet’ Network error: ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘11’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 11)
root@RevPi45698:/home/pi# cd Documents
root@RevPi45698:/home/pi/Documents# ./mbim-set-ip.sh /dev/cdc-wdm0 wwan0
Requesting IPv4 and IPv6 information through mbimcli proxy:
error: couldn’t get IP configuration response message: ContextNotActivated
error: couldn’t get IP configuration response message: ContextNotActivated
Applying the following network interface configurations:
ip link set wwan0 down
ip addr flush dev wwan0
ip -6 addr flush dev wwan0
ip link set wwan0 up
Network interface configurations completed.
root@RevPi45698:/home/pi/Documents# ping 8.8.8.8
connect: Network is unreachable

jfrog · June 30, 2023, 2:12pm

Once mbim-network is completed run
mbimcli -d /dev/cdc-wdm0 -p --query-ip-configuration
and nothing else.

vedrax7 · June 30, 2023, 2:19pm

error: couldn’t get IP configuration response message: ContextNotActivated

jfrog · June 30, 2023, 2:26pm

Try to repeat the command as shown here, use your current transaction ID.

vedrax7 · June 30, 2023, 2:29pm

root@RevPi45698:/home/pi# mbim-network /dev/cdc-wdm0 start
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
Loading profile at /etc/mbim-network.conf…
APN: internet
APN auth protocol: PAP
APN user: ipa
APN password: XXXX
mbim-proxy: yes
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 11
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘999400000256440’ SIM ICCID: ‘8900099100002144403F’ Ready info: ‘none’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 4)
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=4 --no-close --device-open-proxy’…
[/dev/cdc-wdm0] Registration status: Network error: ‘unknown’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘custom’ Current cellular class: ‘gsm’ Provider ID: ‘99940’ Provider name: ‘DA’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘6’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 6)
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close --device-open-proxy’…
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 8)
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘internet’,auth=‘PAP’,username=‘ipa’,password=‘xxxxx’ --no-open=8 --no-close --device-open-proxy’…
Network started successfully
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 11)
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi# mbimcli -d /dev/cdc-wdm0 -p --query-ip-configuration
[/dev/cdc-wdm0] IPv4 configuration available: ‘address, gateway, dns, mtu’
IP [0]: ‘192.168.241.5/30’
Gateway: ‘192.168.241.6’
DNS [0]: ‘8.8.8.8’
DNS [1]: ‘8.8.4.4’
MTU: ‘1452’
[/dev/cdc-wdm0] IPv6 configuration available: ‘none’
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi#
root@RevPi45698:/home/pi# ping 8.8.8.8
connect: Network is unreachable

jfrog · June 30, 2023, 2:40pm

Great, but you’re trying to ping too early. You now see that the modem has something from the carrier, but this information is local to the modem. You need to configure your interface like wwan0, set the default route and only after all of these you can try ping. My understanding that mbim-set-ip.sh supposed to do exactly this - pull the information from the modem and apply it to the interface.
Next time you can try running the script like this:
bash -x mbim-set-ip.sh {required arguments}
and see if there are any errors.

vedrax7 · July 5, 2023, 9:31am

these are the errors

root@RevPi45698:/home/pi# bash -x ./mbim-set-ip.sh /dev/cdc-wdm0 wwan0
bash: ./mbim-set-ip.sh: No such file or directory
root@RevPi45698:/home/pi# cd Documents
root@RevPi45698:/home/pi/Documents# bash -x ./mbim-set-ip.sh /dev/cdc-wdm0 wwan

ipv4_addresses=()
ipv4_gateway=
ipv4_dns=()
ipv4_mtu=
ipv6_addresses=()
ipv6_gateway=
ipv6_dns=()
ipv6_mtu=
CONTROLDEV=/dev/cdc-wdm0
DEV=wwan0
echo ‘Requesting IPv4 and IPv6 information through mbimcli proxy:’
Requesting IPv4 and IPv6 information through mbimcli proxy:
mbimcli -d /dev/cdc-wdm0 -p --query-ip-configuration
error: couldn’t get IP configuration response message: ContextNotActivated
++ mbimcli -d /dev/cdc-wdm0 -p --query-ip-configuration=0
error: couldn’t get IP configuration response message: ContextNotActivated
IPDATA=
read -r line
‘[’ -z ‘’ ‘]’
continue
read -r line
[[ -n ‘’ ]]
++ mktemp
execfile=/tmp/tmp.D5FBYqfWhX
printf ‘ip link set wwan0 down\n’
printf ‘ip addr flush dev wwan0 \n’
printf ‘ip -6 addr flush dev wwan0 \n’
printf ‘ip link set wwan0 up\n’
[[ 0 > 0 ]]
[[ 0 > 0 ]]
echo ‘Applying the following network interface configurations:’
Applying the following network interface configurations:
cat /tmp/tmp.D5FBYqfWhX
ip link set wwan0 down
ip addr flush dev wwan0
ip -6 addr flush dev wwan0
ip link set wwan0 up
bash /tmp/tmp.D5FBYqfWhX
rm /tmp/tmp.D5FBYqfWhX
echo ‘Network interface configurations completed.’
Network interface configurations completed.

root@RevPi45698:/home/pi/Documents# mbim-network /dev/cdc-wdm0 start
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
/usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
Loading profile at /etc/mbim-network.conf…
APN: internet
APN auth protocol: PAP
APN user: ipa
APN password: vfk4ever
mbim-proxy: yes
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 8
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy’…
error: couldn’t open the MbimDevice: Transaction timed out
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open= --no-close --device-open-proxy’…
error: invalid transaction ID specified:
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open= --no-close --device-open-proxy’…
error: invalid transaction ID specified:
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘internet’,auth=‘PAP’,username=‘ipa’,password=‘vfk4ever’ --no-open= --no-close --device-open-proxy’…
error: invalid transaction ID specified:
Network start failed

vedrax7 · July 6, 2023, 10:32am

any help would be really appreciated

jfrog · July 6, 2023, 6:41pm

Try libmbim-devel Info Page

vedrax7 · July 18, 2023, 11:45am

No improvements. I think these could be posibile issues/solutions:

can updating the kernel version help in any way?

if yes, can you please give me detailed steps to update the kernel?

OR maybe I can reset the modem completely and then repeat the process of adding and loading the driver?
ALSO, when the RevPi boots up, I get this message in the boot logs

[FAILED] Failed to start dhcpcd on all interfaces

jfrog · July 18, 2023, 6:31pm

I do not see any issue with the modem or OS. The problem is probably with mbim-set-ip.sh script.
You have the connection established and IP information obtained:

All you need is to configure an interface with the data obtained from the nodem.
There is an example here, look for

After the network started, one can query current IP configuration like this:

vedrax7 · August 29, 2023, 12:57pm

I have got it working now finally!

The issue was with my 5G network and then the Firewall was blocking the ports.

Thank you so much for your help throughout.

arli24 · September 13, 2023, 11:13am

Hello,
can you please give more details on how you fixed it? I am also having some issues to connect to the OAI 5G SA with my Quectel modem. The device seems to register to the network as the MBIM GUI shows, but I am not able to get an IP and connect to the internet.

Any help would be appreciated