Continuous "QmiWwanThread poll err/hup/inval" output upon executing "sudo ./quectel-CM [my args]"]

Raspberry Pi Network HATs
1

I received the Raspberry Pi 4G/LTE Cellular Modem Kit (with an EC25-A) yesterday. This kit included a Twilio SIM card. I set it up with a raspberry pi 4B (8GB edition) per the Getting Started tutorial before following the QMI Interface with Base HAT tutorial. However, I get the following QmiWwanThread poll err when I run “sudo ./quectel-CM -s wirelessDOTtwilioDOTcom”. This message continuously outputs until I kill the process.

[07-28_10:52:57:145] poll fd = 7, events = 0x0008
[07-28_10:52:57:145] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:145] poll fd = 7, events = 0x0008
[07-28_10:52:57:145] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:145] poll fd = 7, events = 0x0008
[07-28_10:52:57:145] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:145] poll fd = 7, events = 0x0008
[07-28_10:52:57:146] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:146] poll fd = 7, events = 0x0008
[07-28_10:52:57:146] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:146] poll fd = 7, events = 0x0008
[07-28_10:52:57:146] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:146] poll fd = 7, events = 0x0008
[07-28_10:52:57:146] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:146] poll fd = 7, events = 0x0008
[07-28_10:52:57:146] QmiWwanThread poll err/hup/inval
[07-28_10:52:57:146] poll fd = 7, events = 0x0008
[07-28_10:52:57:146] QmiWwanThread poll err/hup/inval

After activating the SIM via Twilio’s guide, I put it in my iPhone and set the APN to “wirelessDOTtwilioDOTcom” with all other credentials blank. In my iphone I’m able to get internet connection, but I can’t seem to get an ip address using my raspberry pi set up. I’ve deactivated the dhcpcd service per this post. Can anyone provide some assistance?

2

Old post, but I’m curious were you able to resolve it? We’re experiencing the same error.

3

I had to set up a new account (forgot my password) but I’m the same person who you’ve replied to.

It’s been a while but if I remember correctly, I got it working when I switched from an 8gb raspberry pi4 to the 4gb raspberry pi 4. Are you using an 8GB pi 4? I think it had something to do with the 64-bit raspberry pi OS.