Driver for 5.4.51-v7l+ kernel not found

ensar · July 27, 2020, 6:08pm

Yes, solved.

See for more information on this: https://www.raspberrypi.org/documentation/raspbian/applications/rpi-update.md

Then follow the instructions here.

ahmed.helmi · July 27, 2020, 6:48pm

Hi Ensar

First I had a Raspberry PI 3B+ and I updated to Raspberry PI 4, And when I used the old image that contains all the setups I need but I faced the issue mentioned here and when applied the new update I ended with the error of “udhcpc: no lease, failing” then I tried to uninstall everything (raspberrypi-kernel-headers, udhcpc and remove the folder named “files”) then run the setup steps from the beginning but also ended up with the same error.

Second I tried to do a clean install on the Raspberry PI 4 from the beginning and followed the setup steps and everything worked correctly with no issue.

Could you please help me in finding the issue about the original image because it is very important to me to work on it to save a lot of time.

thomasseher · July 27, 2020, 9:53pm

Hi Ensar, I have done all exactly as described. But I have the same problem Kernel not found. I dont know what to do now.

carlos · July 31, 2020, 3:33pm

Ensar,

I’m experiencing the same issue as tanelkaus, I’m not being registered to the network, started with a fresh start with the same results, is there any fix? Followed the same steps from your last post.

carlos · August 1, 2020, 6:05pm

If you are experiencing the dhcp issue (that ends with a lease failure), please try the following solution that was shared by another member of the forum:

The reason why “lease fail” is shown, is because dhcpc conflicts with udhcpc. Fixing this is simple; Add “denyinterfaces wwan0” to bottom of /etc/dhcpcd.conf. Then restart dhcpc “sudo systemctl restart dhcpcd”, followed by restarting qmi_reconnect “sudo systemctl restart qmi_reconnect” (or reboot).

kenfred · October 7, 2020, 5:48pm

I am experiencing this issue as well. I had it working after trying a bunch of things I’ve read in the forum, so then I started fresh to make sure I could make it work. Can someone please provide step-by-step instructions from the raspberry pi os desktop image as a base? It doesn’t seem that the provided instructions work.

[10-07_18:44:40:769] Quectel_QConnectManager_Linux_V1.6.0.12
[10-07_18:44:40:771] network interface '' or qmidev '' is not exist
[10-07_18:44:40:771] qmidevice_detect failed
[10-07_18:44:40:771] qmidevice_detect failed

I tried the sudo rpi-update but it didn’t make a difference.

Some info:

pi@raspberrypi:~/files/quectel-CM $ uname -r
5.4.70-v7l+
pi@raspberrypi:~/files/quectel-CM $ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

Harryman01 · October 8, 2020, 4:34pm

Sorry, but this “solution” doesn’t work as the install script will stop if kernels version 5+ are found

case $(uname -r) in
4.14*) echo $(uname -r) based kernel found
echo “${YELLOW}Downloading source files${SET}”
wget https://github.com/sixfab/Sixfab_RPi_3G-4G-LTE_Base_Shield/raw/master/tutorials/QMI_tutorial/src/4.14.zip -O drivers.zip
unzip drivers.zip -d /home/pi/files/ && rm -r drivers.zip;;
4.19*) echo $(uname -r) based kernel found
echo “${YELLOW}Downloading source files${SET}”
wget https://github.com/sixfab/Sixfab_RPi_3G-4G-LTE_Base_Shield/raw/master/tutorials/QMI_tutorial/src/4.19.1.zip -O drivers.zip
unzip drivers.zip -d /home/pi/files/ && rm -r drivers.zip;;
5.4*) echo $(uname -r) based kernel contains driver;;
*) echo “Driver for $(uname -r) kernel not found”;exit 1;

sou you cannot ascertain the issue is fixed because is not

paotang.kao · October 11, 2020, 3:07pm

Hi kenfred.
I just boot up my LTE IoT shield and was likewise struggling with the installation. I had no error on installation but when running quectel-CM i had the same " network interface ‘’ or qmidev ‘’ is not exist" error.
While i was pulling my hair out trying to figure out the next step (including various things stated here, I notice my board has a pwrkey button. I pressed it once, and the LED marked STAT lit up and LED labelled Netlight start blinking blue. Upon which when i run quectel-CM the Connection Manager ran. Having said that, I couldn’t get a connection going.
[10-11_23:04:24:145] Quectel_QConnectManager_Linux_V1.6.0.12
[10-11_23:04:24:147] Find /sys/bus/usb/devices/1-1.4 idVendor=0x2c7c idProduct=0x296, bus=0x001, dev=0x006
[10-11_23:04:24:147] Auto find qmichannel = /dev/cdc-wdm0
[10-11_23:04:24:147] Auto find usbnet_adapter = wwan0
[10-11_23:04:24:147] netcard driver = qmi_wwan, driver version = 22-Aug-2005
[10-11_23:04:24:148] ioctl(0x89f3, qmap_settings) failed: Operation not supported, rc=-1
[10-11_23:04:24:148] Modem works in QMI mode
[10-11_23:04:24:159] cdc_wdm_fd = 7
[10-11_23:04:24:174] Get clientWDS = 1
[10-11_23:04:24:176] Get clientDMS = 1
[10-11_23:04:24:178] Get clientNAS = 1
[10-11_23:04:24:180] Get clientUIM = 1
[10-11_23:04:24:182] Get clientWDA = 1
[10-11_23:04:24:184] requestBaseBandVersion BG96MAR02A10M1G
[10-11_23:04:24:194] requestGetSIMStatus SIMStatus: SIM_READY
[10-11_23:04:24:194] requestSetProfile[1] shwap///0
[10-11_23:04:24:210] requestGetProfile[1] shwap///0
[10-11_23:04:24:214] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
[10-11_23:04:24:216] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[10-11_23:04:24:216] ifconfig wwan0 down
[10-11_23:04:24:226] ifconfig wwan0 0.0.0.0
[10-11_23:05:08:684] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
[10-11_23:06:23:692] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW

but at least the CM saw the card. lol.

ensar · October 12, 2020, 11:09am

Hi @kenfred,

Please follow the updated tutorial here:

kenfred · October 14, 2020, 3:25pm

@paotang.kao Thank you! Yes, when I press that button, wwan0 is finally recognized. I would expect qmi_reconnect to be able to enable the hardware.

@ensar, should the driver/service assert the power up sequence? How can I make the hat work upon reboot without manually pushing the button?

@paotang.kao Like you, that did not completely fix the issue. The interface is unable to get a lease/ip address. I can solve that by doing what others in this thread have done: disabling dhcpcd. HOWEVER, this only works while the PI is still on. When I do this and reboot I don’t get ANY of my network interfaces, so I’m forced to connect a keyboard and monitor an restart dhcpcd.

@ensar Can you clarify the interaction between dhcpdc and udhcpc and advise on the best way to have them play together so I get all of my network interfaces on reboot, including LTE? Thanks!!

pi@raspberrypi:~ $ sudo systemctl status qmi_reconnect.service
● qmi_reconnect.service - QMI Auto Connection
   Loaded: loaded (/etc/systemd/system/qmi_reconnect.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-10-14 16:14:54 BST; 28s ago
 Main PID: 1452 (sh)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/qmi_reconnect.service
           ├─1452 /bin/sh /usr/src/qmi_reconnect.sh
           ├─1472 sudo ./quectel-CM -s hologram
           └─1473 ./quectel-CM -s hologram

Oct 14 16:15:04 raspberrypi sh[1452]: udhcpc: started, v1.30.1
Oct 14 16:15:04 raspberrypi sh[1452]: No resolv.conf for interface wwan0.udhcpc
Oct 14 16:15:04 raspberrypi udhcpc[1498]: wwan0: deconfigured
Oct 14 16:15:04 raspberrypi sh[1452]: udhcpc: sending discover
Oct 14 16:15:07 raspberrypi sh[1452]: udhcpc: sending discover
Oct 14 16:15:10 raspberrypi sh[1452]: udhcpc: sending discover
Oct 14 16:15:13 raspberrypi sh[1452]: udhcpc: sending discover
Oct 14 16:15:16 raspberrypi sh[1452]: udhcpc: sending discover
Oct 14 16:15:20 raspberrypi udhcpc[1519]: wwan0: configuration failed: leasefail:
Oct 14 16:15:20 raspberrypi sh[1452]: udhcpc: no lease, failing

dan.horn · February 1, 2021, 8:14pm

So this has not been solved from what I can see, is it common for Sixfab to just ignore issues like this?

I need more data as we are considering rolling out a platform with these HAT’s but without complete and timely support we’ll have to use another vendor.

network interface ‘’ or qmidev ‘’ is not exist

uname -a
Linux DietPi 5.10.11-v8+ #1399 SMP PREEMPT Thu Jan 28 12:14:03 GMT 2021 aarch64 GNU/Linux

ensar · February 1, 2021, 8:43pm

Hi @dan.horn,

Could you please let me know more details on this? Which module do you use? About your issue, it is better to share more information with us. What have you done, could you describe your test steps, then we can help to confirm where is the problem.
I did the same steps and to me, it works.

pi@raspberrypi:~/files/quectel-CM $ uname -a
Linux raspberrypi 5.10.11-v7l+ #1398 SMP Wed Jan 27 22:14:45 GMT 2021 armv7l GNU/Linux

pi@raspberrypi:~/files/quectel-CM $ sudo ./quectel-CM -s super
[02-01_20:42:43:895] Quectel_QConnectManager_Linux_V1.6.0.12
[02-01_20:42:43:897] Find /sys/bus/usb/devices/1-1.1 idVendor=0x2c7c idProduct=0x125, bus=0x001, dev=0x003
[02-01_20:42:43:897] Auto find qmichannel = /dev/cdc-wdm0
[02-01_20:42:43:897] Auto find usbnet_adapter = wwan0
[02-01_20:42:43:898] netcard driver = qmi_wwan, driver version = 5.10.11-v7l+
[02-01_20:42:43:899] ioctl(0x89f3, qmap_settings) failed: Operation not supported, rc=-1
[02-01_20:42:43:899] Modem works in QMI mode
[02-01_20:42:43:927] cdc_wdm_fd = 7
[02-01_20:42:44:024] Get clientWDS = 8
[02-01_20:42:44:153] Get clientDMS = 1
[02-01_20:42:44:184] Get clientNAS = 3
[02-01_20:42:44:217] Get clientUIM = 1
[02-01_20:42:44:249] Get clientWDA = 1
[02-01_20:42:44:281] requestBaseBandVersion EC25EFAR06A04M4G
[02-01_20:42:44:602] requestGetSIMStatus SIMStatus: SIM_READY
[02-01_20:42:44:602] requestSetProfile[1] super///0
[02-01_20:42:44:697] requestGetProfile[1] super///0
[02-01_20:42:44:729] requestRegistrationState2 MCC: 286, MNC: 3, PS: Attached, DataCap: LTE
[02-01_20:42:44:760] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[02-01_20:42:44:761] ifconfig wwan0 down
[02-01_20:42:44:778] ifconfig wwan0 0.0.0.0
[02-01_20:42:44:889] requestSetupDataCall WdsConnectionIPv4Handle: 0x871fb980
[02-01_20:42:45:050] change mtu 1500 -> 1360
[02-01_20:42:45:051] ifconfig wwan0 up
[02-01_20:42:45:068] 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
[02-01_20:43:00:665] File:ql_raw_ip_mode_check Line:105 udhcpc fail to get ip address, try next:
[02-01_20:43:00:666] ifconfig wwan0 down
[02-01_20:43:00:680] echo Y > /sys/class/net/wwan0/qmi/raw_ip
[02-01_20:43:00:680] ifconfig wwan0 up
[02-01_20:43:00:692] 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 select for 100.67.142.4
udhcpc: lease of 100.67.142.4 obtained, lease time 7200
Too few arguments.
Too few arguments.

Please follow the updated tutorial here:

Don’t hesitate to let us know if you have any questions or comments.

Thanks.

dan.horn · February 2, 2021, 11:30pm

Was working fine, put it away for a few months, did an apt update and it stopped.

Raspberry Pi 3G/4G & LTE Base HAT with EC25-A

Now have it all installed and it’s not recognizing that the HAT exists so don’t understand what happened.

Did raspi-update, checked kernels were tested in script and the only thing I’ve done was change “pi” to “dietpi” as the home directory for the installer to find the main directory which works fine. P.S. this should be a question in the script not hardwired I’d think?

Tried different USB cables and all the lights seem to be good on the HAT so I’m at a loss as to what to do at this point.

Thanks, Dan

lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 003: ID 1997:2433

Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

./quectel-CM -s super

[02-01_20:58:22:221] Quectel_QConnectManager_Linux_V1.6.0.12

[02-01_20:58:22:222] network interface ‘’ or qmidev ‘’ is not exist

[02-01_20:58:22:222] qmidevice_detect failed

ensar · February 3, 2021, 9:56am

After preparing your hardware, could you share the following command outputs:

uname -a
lsusb -t
dmesg | grep tty
sudo cat /sys/kernel/debug/usb/devices
lsb_release -a

Useful links:

dan.horn · February 3, 2021, 1:59pm

root@DietPi:~# uname -a
Linux DietPi 5.10.11-v8+ #1399 SMP PREEMPT Thu Jan 28 12:14:03 GMT 2021 aarch64 GNU/Linux
root@DietPi:~# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
root@DietPi:~# dmesg | grep tty
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:C4:81:C4 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=tty1 root=PARTUUID=8f4dbd00-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet net.ifnames=0
[ 0.000150] printk: console [tty1] enabled
[ 0.718772] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 21, base_baud = 0) is a PL011 rev2
[ 1.634014] systemd[1]: Created slice system-getty.slice.
root@DietPi:~# sudo cat /sys/kernel/debug/usb/devices

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 5.10
S: Manufacturer=Linux 5.10.11-v8+ xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:01:00.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4
D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=2109 ProdID=3431 Rev= 4.21
S: Product=USB2.0 Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms

T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs= 1
P: Vendor=1997 ProdID=2433 Rev= 1.10
S: Manufacturer=
S: Product=mini keyboard
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=8ms
I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=82(I) Atr=03(Int.) MxPS= 32 Ivl=1ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev= 5.10
S: Manufacturer=Linux 5.10.11-v8+ xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:01:00.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

ensar · February 3, 2021, 3:15pm

Your problem may be caused by DietPi OS. The module you are using is not recognized by the operating system. You can let them know about this issue or install the drivers.
Quectel EC25 Mini PCle 4G/LTE Module - Linux USB Driver

dan.horn · February 3, 2021, 6:33pm

That link you sent doesn’t have the driver it just has some Windows scripts and a PDF.
I need the actual driver source so I can complie it and install it.
Can you send me a link that has the source please?
Thanks, Dan

ensar · February 3, 2021, 10:32pm

Please follow the user manual(.pdf) steps.
“This document introduces how to generate the USB driver for Quectel module in Linux OS, and how to use the module after the USB driver is loaded successfully.”

Thanks.

dan.horn · February 4, 2021, 4:44pm

Ok, so it appears the board is bad since the board doesn’t show up using lsusb, which it should regardless of the driver as it’s a hardware device.

What is the process for me to get a new working card to use with my EC25 LTE card?

Thank you,
Dan

dan.horn · February 4, 2021, 4:45pm

Incidently I tried four USB cables and it still didn’t work so it’s definately the HAT.