Comment # 2 on bug 1045720 from
Created attachment 734728 [details]
Output mmcli --modem=*

This is not a kernel issue, but an ModemManager-Problem.

I have made a new installation, using the official Leap 42.3 release.

After the installation, I used the mmcli:
-----------------------
gs@gs12lnx:~> mmcli -L
No modems were found
gs@gs12lnx:~> mmcli -S
successfully requested to scan devices
gs@gs12lnx:~> mmcli -L
No modems were found
-----------------------
After that I re-installed the ModemManager form Tumbleweed, which gave the
result (after reboot):
-----------------------
gs@gs12lnx:~> mmcli -L
error: couldn't find the ModemManager process in the bus
-----------------------
Then I re-installed the ModemManager of Leap 42.3 from
Suse-Download-PackageSearch, which gave the result (after reboot):
-----------------------
gs@gs12lnx:~> mmcli -L
Found 1 modems:
        /org/freedesktop/ModemManager1/Modem/0 [Generic] MBIM [1199:9079]
-----------------------
I add the output of the command "mmcli --modem=x" ---> See attachment.

So the modem in Tumbleweed is active, in Leap 42.3 is it not.

What can I do to solve this problem???


You are receiving this mail because: