Package Details: xmm7360-pci-spat-dkms-git 1:0-3

Git Clone URL: https://aur.archlinux.org/xmm7360-pci-spat-dkms-git.git (read-only, click to copy)
Package Base: xmm7360-pci-spat-dkms-git
Description: Driver for the Fibocom L850-GL / Intel XMM7360 LTE modem – module sources
Upstream URL: https://github.com/SimPilotAdamT/xmm7360-pci-SPAT
Licenses: GPL, BSD
Conflicts: xmm7360-pci-dkms-git, xmm7360-pci-utils-git
Provides: xmm7360-pci-spat-dkms
Replaces: xmm7360-pci-spat-dkms
Submitter: SimPilotAdamT
Maintainer: SimPilotAdamT
Last Packager: SimPilotAdamT
Votes: 5
Popularity: 0.013731
First Submitted: 2024-02-22 19:23 (UTC)
Last Updated: 2024-03-04 15:38 (UTC)

Dependencies (2)

Required by (1)

Sources (4)

Pinned Comments

thotypous commented on 2025-05-04 02:34 (UTC)

Orphaning this package since upstream is unmaintained. Please use the fork xmm7360-pci-spat-dkms-git instead.

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

sptvar commented on 2025-03-25 01:10 (UTC) (edited on 2025-03-25 01:11 (UTC) by sptvar)

I had problems with building modules for kernels 6.6 and higher:

error: initialization of ‘ssize_t (*)(struct tty_struct *, const u8 *, size_t)’ {aka ‘long int (*)(struct tty_struct *, const unsigned char *, long unsigned int)’} from incompatible pointer type ‘int (*)(struct tty_struct *, const unsigned char *, int)’ [-Werror=incompatible-pointer-types] .write = xmm7360_tty_write,

The problem is solved by this pull request: https://github.com/xmm7360/xmm7360-pci/pull/220

I think it is useful to add it to the AUR package

Kadzi commented on 2024-11-08 09:26 (UTC)

I wasn't able to compile xmm7360-pci-dkms package with newer kernels. But this fork works flawlessly.

nursoda commented on 2024-03-10 03:23 (UTC) (edited on 2024-03-10 03:26 (UTC) by nursoda)

Thanks for this PKGBUILD, but please explain why one should use this package rather than xmm7360-pci-dkms. Please also add some information in your GitHub fork's README, so that one knows what the changes are for, and maybe also add the upstream author's last commit ;)

c-kr commented on 2023-09-17 08:06 (UTC) (edited on 2023-09-17 08:30 (UTC) by c-kr)

I had the same problems getting it to work. Kernel module loads but channel opening always resulted in:

INFO:root:Attach failed - waiting to see if we just weren't ready

My final solution was to boot into a windows to go live environment, installing the official windows driver, making sure it connects and than instantly rebooting into arch, being able to connect without any additional changes.

Credits to: https://github.com/xmm7360/xmm7360-pci/issues/98#issuecomment-842844878 and https://github.com/xmm7360/xmm7360-pci/issues/173#issuecomment-1118905045

There should be a hint in the installation docs that the modem needs to be enabled in windows first. I have added it to the arch wiki guide.

kata55 commented on 2023-08-19 22:34 (UTC) (edited on 2023-08-19 22:42 (UTC) by kata55)

Hi @thotypus,

Thank you so much for the example - I successfully blacklisted the iosm module as you instructed. Note that I observed that this results in different devices being created under /dev/, most notably without iosm the /dev/wwan0at* devices don't get created.

Unfortunately, I still haven't managed to make the modem work. This is getting too complex of an issue, so I created this issue on the upstream GitHub repo: https://github.com/xmm7360/xmm7360-pci/issues/209

Thanks for the package btw! Really helpful, especially when I'm creating myself a little script to automate the OS setup.

thotypous commented on 2023-08-02 20:56 (UTC)

Hi kata55,

It's working here on 6.4.7. I can't reboot right now, but last time I checked it was working with linux-lts too.

You need to blacklist iosm. For example, create a /etc/modprobe.d/xmm7360.conf file containing blacklist iosm. I'm not sure if it would be acceptable per Arch standards for the package to do the blacklisting by itself.

kata55 commented on 2023-08-02 20:52 (UTC)

Hey, just wanted to confirm that this package builds and installs fine with 6.1.41 kernel. This is on a Yoga X1 Gen 3 (20LD). It displays under lspci -k:

04:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem (rev 01)
    Subsystem: Intel Corporation XMM7360 LTE Advanced Modem
    Kernel driver in use: iosm
    Kernel modules: iosm, xmm7360

However, it does not seem to switch the used kernel driver (iosm) automatically upon installing; Is this behavior as expected, and how do I go about switching the modem's kernel driver permanently?

nursoda commented on 2022-06-11 13:30 (UTC)

See https://github.com/xmm7360/xmm7360-pci/issues/179

Kadzi commented on 2022-06-02 17:20 (UTC)

I'm having problem with dkms build. ==> dkms install --no-depmod xmm7360-pci-git/r229.cf6625a -k 5.18.1-arch1-1 Error! Bad return status for module build on kernel: 5.18.1-arch1-1 (x86_64) Consult /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build/make.log for more information. ==> WARNING: `dkms install --no-depmod xmm7360-pci-git/r229.cf6625a -k 5.18.1-arch1-1' exited 10

The error is: /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build/xmm7360.c:1175:13: warning: the comparison will always evaluate as 'true' for the address of 'td_ring' will never be NULL [-Waddress] 1175 | if (xmm->td_ring) { | ^~~ /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build/xmm7360.c:209:24: note: 'td_ring' declared here 209 | struct td_ring td_ring[16]; | ^~~~~~~ /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build/xmm7360.c: In function 'xmm7360_probe': /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build/xmm7360.c:1455:15: error: implicit declaration of function 'pci_set_dma_mask' [-Werror=implicit-function-declaration] 1455 | ret = pci_set_dma_mask(dev, 0xffffffffffffffff); | ^~~~~~~~~~~~~~~~ cc1: some warnings being treated as errors make[2]: [scripts/Makefile.build:288: /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build/xmm7360.o] Error 1 make[1]: [Makefile:1834: /var/lib/dkms/xmm7360-pci-git/r229.cf6625a/build] Error 2 make[1]: Leaving directory '/usr/lib/modules/5.18.1-arch1-1/build' make: *** [Makefile:9: default] Error 2

Does anyone know how to solve this?

yast commented on 2022-02-12 05:31 (UTC)

The kernel-5.15-comapt.patch now fails to be applied. It looks like the source file is already patched to support 5.15 and 5.16 kernels.