This is the modem
https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-lte-cat4-usb-dongle/
Following the instructions
https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte-cat4-usb-sticks-in-linux-using-mbim-usb-mode/
mmcli --scan-modems
successfully requested to scan devices
mmcli --list-modems
No modems were found
The bizarre thing is that
an older modem onetouch works fine now
It seems working with windows.
but is is not detected correctly with Linux.
Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
It is also not detected by
modem-manager-gui
enp0s20f0u11 ethernet connected Teucidide
nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se'
connection.autoconnect yes gsm.pin
Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
missing enabled missing enabled
nmcli device show cdc-wdm
Error: Device 'cdc-wdm' not found.
nmcli connection show
NAME UUID TYPE DEVICE
Teucidide 05bc1961-b71a-375a-80f0-d1d43969bfce ethernet enp0s20f0u11
lo 2f316384-0efb-49e0-891a-ecbc70275b83 loopback lo
virbr0 6b485fdf-8003-46d4-bbcf-00e6c3b53151 bridge virbr0
3-sweden b25e5d45-379a-42fe-b340-7a8477d058d5 gsm --
(enp0s20f0u11)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: fe80::68ac:7fff:fe44:5b09
DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
ip link set enp0s20f0u11 up
ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > The manufacturer says compatible Linux
>
> To be blunt, that may just mean it worked on one distro, perhaps one
> that doesn't care about what software it installs (not as in malware,
> but ones that include non-free things the other distros don't).
>
> It might mean it worked when the user did a lot of work to enable it.
> Without details you won't know. And there's also a chance that since
> they first released it, and it did work on Linux, they've built a new
> model with a different chipset.
>
> Did you check if the manufacturer expects you to download a driver from
> their website?
>
> --
>
> uname -rsvp
> Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
>
> Boilerplate: All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.
>
>
>
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
