Open lprobsth opened 2 years ago
Further investigation of this problem has shown that after loading the kernel module the module first comes up as wwan0
. I then bringup the modem with open_xdatachannel.py. The first run is successful and I also get a connection for some seconds. The connection then breaks down and the devices shows up as ttyXMM2
in network-manager.
I have now tested kernel versions 6.1.0, 5.19.17 and 5.15.76. This behavior of the modem keeps present.
I assume that it has to do with something other on the system (network-manager, modem manager, ...).
Removing Modem Manager did indeed solve the problem.
I just got to get it working with Debian Trixie, kernel 6.5.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1 (2023-11-29) x86_64 GNU/Linux
1) I went DKMS path and had to enroll dkms mok key ( mokutil --import /var/lib/dkms/mok.pub
)
2) After reboot (and confirmation of MOK modification) i checked the module is loaded and created config file /etc/xmm7360 from /usr/src/xmm7360-pci-1fce92b4d5811f4bbee6dc514b39214944a8a381/xmm7360.ini.sample
3) I used noresolv=True and dbus=True, and hit the error name 'devpath' is not defined
4) I disabled dbus integration and launched the rpc/open_xdatachannel.py
again
And everything works nicely so far
Bottom line is you maybe don't have to uninstall NetworkManager to get it working
I'm using xmm7360-pci on manjaro (6.0.6-1-MANJARO) - up until this point very successful.
Since the newest kernel update the bringup of the modem fails.
It seems that the modem got the name
ttyXMM2
while xmm7360 expectswwan0
. I have blocked the iosm kernel module. What else can mess up the modem this way?