Driver for 5.4.51-v7l+ kernel not found

Raspberry Pi Network HATs
1

Hi!

My Raspberry Pi 4G/LTE Cellular Modem Kit with Quectel EC25 Mini PCle 4G/LTE Module was working fine until yesterday when I did sudo apt update and upgrade for on latest raspian installation running on PI4. VERSION_ID=“10” VERSION="10 (buster)"VERSION_CODENAME=buster

Now the gmi auto-connect service is dead and also the sudo ./quectel-CM -s internet returns no file found.
If i reinstall all from start (following the doc all steps) Checking Kernel

Driver for 5.4.51-v7l+ kernel not found.

Before running sudo ./qmi_install.sh shield was disconnected.

Also it looks like the installation does not give needed rights to the folder files/quectel-CM.
Because running the
cd files/quectel-CM will return files/quectel-CM: Permission denied.

So i changed the permission chmod for files/quectel-CM
run: sudo ./quectel-CM -s internet
sudo: ./quectel-CM: command not found.

It looks like the installer is not able to install the sudo ./quectel-CM.
All goes downhill from there.

Is there a new way to setup the shield? I had lots of permission problem also during my initial installation put I was able to overcome these problems.

My raspian is setup in default way only the default password is changed. No special user settup.

my ls /usr/src returns:

linux-headers-5.4.51+ linux-headers-5.4.51-v7l+ sense-hat

linux-headers-5.4.51-v7+ qmi_reconnect.sh

How I can get this up and running again?

2

I am on a raspberry PI 4, with this exact same issue. Down to the permissions on the files directory.

Driver for 5.4.51-v7l+ kernel not found

3

I am also on Raspberry PI 4 with the same issue, I changed the permissions as mentioned above then I faced the same error above which is “Driver for 5.4.51-v7l+ kernel not found”.

I modified the setup script to use the Driver for 4.19.1 and it installed but I end up with the following result:
[07-22_19:00:03:454] Auto find usbnet_adapter = wwan0
[07-22_19:00:03:455] netcard driver = qmi_wwan, driver version = 22-Aug-2005
[07-22_19:00:03:455] Modem works in QMI mode
[07-22_19:00:03:479] cdc_wdm_fd = 7
[07-22_19:00:03:578] Get clientWDS = 17
[07-22_19:00:03:609] Get clientDMS = 1
[07-22_19:00:03:641] Get clientNAS = 4
[07-22_19:00:03:673] Get clientUIM = 2
[07-22_19:00:03:705] Get clientWDA = 1
[07-22_19:00:03:736] requestBaseBandVersion EC25AFFAR07A06M4G
[07-22_19:00:03:865] requestGetSIMStatus SIMStatus: SIM_READY
[07-22_19:00:03:865] requestSetProfile[1] broadband///0
[07-22_19:00:03:929] requestGetProfile[1] broadband///0
[07-22_19:00:03:961] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:00:03:993] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[07-22_19:00:03:993] ifconfig wwan0 down
[07-22_19:00:04:001] ifconfig wwan0 0.0.0.0
[07-22_19:00:04:058] requestSetupDataCall WdsConnectionIPv4Handle: 0x871cde60
[07-22_19:00:04:185] change mtu 1500 -> 1430
[07-22_19:00:04:185] ifconfig wwan0 up
[07-22_19:00:04:194] busybox udhcpc -f -n -q -t 5 -i wwan0
udhcpc: started, v1.30.1
No resolv.conf for interface wwan0.udhcpc
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, failing
[07-22_19:00:45:527] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:00:45:560] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:00:45:591] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:00:52:151] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:00:52:183] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:00:54:327] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:02:31:439] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-22_19:02:41:199] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE

And it never gets an IP address, so I run the AT command “AT+CGPADDR” which give me the following response:
AT+CGPADDR
+CGPADDR: 1,“10.110.174.174”
+CGPADDR: 2,“0.0.0.0,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
+CGPADDR: 3,“0.0.0.0,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
And apparently it got an IP address but the old version of the driver “4.19.1” seems that it can not get that IP address from the module.

Any support is highly appreciated.

4

I follow the directions for QMI install on this page: QMI Interface Internet Connection Setup Using Sixfab Shield/HAT
++++~ $ cd files/quectel-CM
pi@MYHOSTNAME:~/files/quectel-CM $ sudo ./quectel-CM -s internet
sudo: unable to resolve host MYHOSTNAME: Name or service not known
[07-22_21:01:07:478] Quectel_QConnectManager_Linux_V1.5.9
[07-22_21:01:07:480] network interface ‘’ or qmidev ‘’ is not exist
[07-22_21:01:07:480] qmidevice_detect failed
pi@MYHOSTNAME:~/files/quectel-CM $

What do you think could be the issue?

5

pi@MYHOSTNAME:~ $ sudo ./qmi_install.sh
Clear Files
Change directory to /home/pi
Downloading source files
–2020-07-22 21:47:20-- https://github.com/sixfab/Sixfab_RPi_3G-4G-LTE_Base_Shield/raw/master/tutorials/QMI_tutorial/src/quectel-CM.zip
Resolving github.com (github.com)… 140.82.113.4
Connecting to github.com (github.com)|140.82.113.4|:443… connected.
HTTP request sent, awaiting response… 302 Found
Location: https://raw.githubusercontent.com/sixfab/Sixfab_RPi_3G-4G-LTE_Base_Shield/master/tutorials/QMI_tutorial/src/quectel-CM.zip [following]
–2020-07-22 21:47:21-- https://raw.githubusercontent.com/sixfab/Sixfab_RPi_3G-4G-LTE_Base_Shield/master/tutorials/QMI_tutorial/src/quectel-CM.zip
Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.4.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.4.133|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 143823 (140K) [application/zip]
Saving to: ‘quectel-CM.zip’

quectel-CM.zip 100%[===================>] 140.45K 187KB/s in 0.8s

2020-07-22 21:47:23 (187 KB/s) - ‘quectel-CM.zip’ saved [143823/143823]

Archive: quectel-CM.zip
creating: /home/pi/files/quectel-CM/
inflating: /home/pi/files/quectel-CM/GobiNetCM.c
inflating: /home/pi/files/quectel-CM/MPQCTL.h
inflating: /home/pi/files/quectel-CM/MPQMI.h
inflating: /home/pi/files/quectel-CM/MPQMUX.c
inflating: /home/pi/files/quectel-CM/MPQMUX.h
inflating: /home/pi/files/quectel-CM/Makefile
inflating: /home/pi/files/quectel-CM/NOTICE
inflating: /home/pi/files/quectel-CM/QMIThread.c
inflating: /home/pi/files/quectel-CM/QMIThread.h
inflating: /home/pi/files/quectel-CM/QmiWwanCM.c
inflating: /home/pi/files/quectel-CM/ReleaseNote.txt
inflating: /home/pi/files/quectel-CM/default.script
inflating: /home/pi/files/quectel-CM/device.c
inflating: /home/pi/files/quectel-CM/ethtool-copy.h
creating: /home/pi/files/quectel-CM/libmnl/
inflating: /home/pi/files/quectel-CM/libmnl/README
inflating: /home/pi/files/quectel-CM/libmnl/attr.c
inflating: /home/pi/files/quectel-CM/libmnl/callback.c
creating: /home/pi/files/quectel-CM/libmnl/dhcp/
inflating: /home/pi/files/quectel-CM/libmnl/dhcp/dhcp.h
inflating: /home/pi/files/quectel-CM/libmnl/dhcp/dhcpclient.c
inflating: /home/pi/files/quectel-CM/libmnl/dhcp/dhcpmsg.c
inflating: /home/pi/files/quectel-CM/libmnl/dhcp/dhcpmsg.h
inflating: /home/pi/files/quectel-CM/libmnl/dhcp/packet.c
inflating: /home/pi/files/quectel-CM/libmnl/dhcp/packet.h
inflating: /home/pi/files/quectel-CM/libmnl/ifutils.c
inflating: /home/pi/files/quectel-CM/libmnl/ifutils.h
inflating: /home/pi/files/quectel-CM/libmnl/libmnl.h
inflating: /home/pi/files/quectel-CM/libmnl/nlmsg.c
inflating: /home/pi/files/quectel-CM/libmnl/socket.c
inflating: /home/pi/files/quectel-CM/main.c
inflating: /home/pi/files/quectel-CM/mbim-cm.c
inflating: /home/pi/files/quectel-CM/qmap_bridge_mode.c
inflating: /home/pi/files/quectel-CM/quectel-qmi-proxy.c
inflating: /home/pi/files/quectel-CM/udhcpc.c
inflating: /home/pi/files/quectel-CM/udhcpc_netlink.c
inflating: /home/pi/files/quectel-CM/util.c
inflating: /home/pi/files/quectel-CM/util.h
Checking Kernel
Driver for 5.4.51-v7l+ kernel not found
pi@MYHOSTNAME:~ $

6

I have even attempted to run a full upgrade, no packages updated as I have the latest and greatest. I ran through the install instructions two times and still not able to get the QMI driver for this device.

Can anyone help me?

7

Hi all,
The QMI installer will be updated soon according to the new kernel driver.
I will let you know once I receive further updates.

Thank you.

2 Likes
8

Hi ensar, do you have any timeline to have this update live? For us it’s urgent to have this driver update to get some of our projects running, many thanks.

1 Like
9

yes, any timeline of when this will be updated? especially since we have already purchased the hardware from you that cant be used right now. a timeline would be appreciated.

11

QMI installer updated. Please try to install it again.
If this doesn’t work or you have more questions, just let me know and I’ll be happy to help.

Thank you.

2 Likes
12

I tried the installer again and still this is what I get: Checking Kernel
Driver for 5.4.51-v7l+ kernel not found

Just to confirm, I am following the instructions here: https://docs.sixfab.com/docs/qmi-interface-with-base-hat

13

Hi!

Did you remove the old .sh installation file from pi/home/?

If you download a new one the new will have a number in the filename. For example xxxxx 1.
So you could have just started the previous version.

14

Hi All

I could finish the installation. I did just the installation for now. This went well i can do the rest tomorrow

15

I followed those steps and looks like I was able to download the driver this time, but now I am at step 13 of the installer and I get this:

pi@MYHOSTNAME:~ $ cd files/quectel-CM
pi@MYHOSTNAME:~/files/quectel-CM $ sudo ./quectel-CM -s internet
[07-25_13:31:01:222] Quectel_QConnectManager_Linux_V1.5.9
[07-25_13:31:01:224] network interface ‘’ or qmidev ‘’ is not exist
[07-25_13:31:01:224] qmidevice_detect failed
pi@MYHOSTNAME:~/files/quectel-CM $

Can anyone help on this matter?

17

Make sure that the micro USB cable is connected between the hat and the Rasp PI

Also make sure that AP name of your network provider is “internet” otherwise change it in the command[quote=“gerald.king, post:15, topic:566, full:true”]
I followed those steps and looks like I was able to download the driver this time, but now I am at step 13 of the installer and I get this:

pi@MYHOSTNAME:~ $ cd files/quectel-CM
pi@MYHOSTNAME:~/files/quectel-CM $ sudo ./quectel-CM -s internet
[07-25_13:31:01:222] Quectel_QConnectManager_Linux_V1.5.9
[07-25_13:31:01:224] network interface ‘’ or qmidev ‘’ is not exist
[07-25_13:31:01:224] qmidevice_detect failed
pi@MYHOSTNAME:~/files/quectel-CM $

Can anyone help on this matter?
[/quote]

Make sure that the micro USB cable is connected between the hat and the Rasp PI

Also make sure that AP name of your network provider is “internet” otherwise change it in the command

18

I have replaced the USB cable three times. Also, I am following the instructions provided by SixFab which is listed ABOVE. Nowhere does it say name the device. Our network provider is Twilio/T-Mobile and their apn is wireless.twilio.com.

19

yep same thing.
sudo ./quectel-CM -s internet or sudo ./quectel-CM -s my.provider.xx

[07-26_21:06:50:988] Quectel_QConnectManager_Linux_V1.5.9
[07-26_21:06:50:989] network interface ‘’ or qmidev ‘’ is not exist
[07-26_21:06:50:989] qmidevice_detect failed

Update. My cable was lose. So this fixed the issue.

New problem no lease.
sudo ./quectel-CM -s internet.xxxx.xx
[07-26_21:59:32:553] Quectel_QConnectManager_Linux_V1.5.9
[07-26_21:59:32:554] Find /sys/bus/usb/devices/1-1.1 idVendor=0x2c7c idProduct=0x125, bus=0x001, dev=0x003
[07-26_21:59:32:554] Auto find qmichannel = /dev/cdc-wdm0
[07-26_21:59:32:554] Auto find usbnet_adapter = wwan0
[07-26_21:59:32:554] netcard driver = qmi_wwan, driver version = 22-Aug-2005
[07-26_21:59:32:555] Modem works in QMI mode
[07-26_21:59:32:574] /proc/4372/fd/7 -> /dev/cdc-wdm0
[07-26_21:59:32:574] /proc/4372/exe -> /home/pi/files/quectel-CM/quectel-CM
[07-26_21:59:48:576] cdc_wdm_fd = 7
[07-26_21:59:48:675] Get clientWDS = 20
[07-26_21:59:48:706] Get clientDMS = 1
[07-26_21:59:48:738] Get clientNAS = 4
[07-26_21:59:48:770] Get clientUIM = 1
[07-26_21:59:48:802] Get clientWDA = 1
[07-26_21:59:48:834] requestBaseBandVersion EC25EFAR06A04M4G
[07-26_21:59:48:963] requestGetSIMStatus SIMStatus: SIM_READY
[07-26_21:59:48:963] requestSetProfile[1] internet.xxxx.xx///0
[07-26_21:59:49:027] requestGetProfile[1] internet.xxxx.xx///0
[07-26_21:59:49:059] requestRegistrationState2 MCC: 248, MNC: 3, PS: Attached, DataCap: LTE
[07-26_21:59:49:090] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[07-26_21:59:49:090] ifconfig wwan0 down
[07-26_21:59:49:111] ifconfig wwan0 0.0.0.0
[07-26_21:59:49:155] requestSetupDataCall WdsConnectionIPv4Handle: 0x871d4dd0
[07-26_21:59:49:283] ifconfig wwan0 up
[07-26_21:59:49:291] busybox udhcpc -f -n -q -t 5 -i wwan0
udhcpc: started, v1.30.1
No resolv.conf for interface wwan0.udhcpc
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, failing
[07-26_22:00:04:936] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
[07-26_22:00:04:965] ifconfig wwan0 down
[07-26_22:00:04:977] ifconfig wwan0 0.0.0.0
[07-26_22:00:05:159] QmiWwanThread exit
[07-26_22:00:05:160] qmi_main exit

Final update to the saga.

I uninstalled my Pitunne service. After this sudo ./quectel-CM -s internet.xxxx.xx
magically started to work.

20

Replaced the USB cable yet again, and now the wwan0 is identified. Ran the following sudo ./quectel-CM -s wireless.twilio.com and get a lot further. I am NOT getting an IP address though. Any idea on how I can fix this?

21

Hi, same problem and can I be noticed when a new update to the kernel is released?

22

Hi ensar, Is that problem with the kernel solved? Where can I find the update of the kernel?
thanks for your help.