You need to run the qmi connection manager, in parallel, open another terminal, and type “sudo dhclient wwan0” and then see if it can ping outside
I was already doing that! I just ran “sudo dhclient wwan0” and it gave me a couple of warnings but for the rest it looks good. So I just ran the browser and it works!? haha
It still doesn’t show in the settings or UI in general, and modem is still not found.
Then can you ping google server with
ping 8.8.8.8 -I wwan0
yeah that works, it’s pinging, But still modem is not found and the network doesn’t show in the UI.
I don’t know exactly what a properly working modem would look like to be honest, it’s my first time with cellular systems. But I’d expect it would show the network on the UI and also recognise the modem right?
Then that means the module and driver are all working fine
For the UI, it is out of our scope, you might need to check with the corresponding OS forum
Ah okay, then the UI I’ll check with Ubuntu forums I guess.
But what about the modem manager? why can’t it find the modem?
from your modem manager error log, it shows that it is opening the wrong serial port:
Jun 01 08:40:17 Helix52X-K52X-test-corley systemd[1]: Starting ModemManager.service - Modem Manager...
Jun 01 08:40:17 Helix52X-K52X-test-corley ModemManager[1750]: <msg> ModemManager (version 1.23.4) starting in system bus...
Jun 01 08:40:17 Helix52X-K52X-test-corley systemd[1]: Started ModemManager.service - Modem Manager.
Jun 01 08:40:21 Helix52X-K52X-test-corley ModemManager[1750]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:06.1/0000:23:00.0': not supported by any plugin
Jun 01 08:40:21 Helix52X-K52X-test-corley ModemManager[1750]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:04:00.0': not supported by any plugin
Jun 01 08:40:21 Helix52X-K52X-test-corley ModemManager[1750]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0': not supported by any plugin
Jun 01 08:40:21 Helix52X-K52X-test-corley ModemManager[1750]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.6/0000:02:00.0': not supported by any plugin
Jun 01 08:40:21 Helix52X-K52X-test-corley ModemManager[1750]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.7/0000:01:00.0': not supported by any plugin
Jun 01 08:40:37 Helix52X-K52X-test-corley ModemManager[1750]: <msg> [device /sys/devices/pci0000:00/0000:00:16.3] creating modem with plugin 'generic' and '1' ports
Jun 01 08:40:37 Helix52X-K52X-test-corley ModemManager[1750]: <wrn> [plugin/generic] could not grab port ttyS5: Cannot add port 'tty/ttyS5', unhandled port type
Jun 01 08:40:37 Helix52X-K52X-test-corley ModemManager[1750]: <wrn> [base-manager] couldn't create modem for device '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
I am following this. I will try a test with my EM7590.
Thank you!
I just restarted the system and it disconnects, shouldn’t it be also automatically connecting to the internet? Or are there any special configs for that?
you can first check if you can use mbim-network utility to establish data connection
If yes, you can then check how to enable this utility as auto-start