Created attachment 93285 [details] Screencast showing the issue Hi, I have an EliteBook 850 G1 form HP with an integrated Huawei M906ME 4G Modem. HP call it LT4112 Gobi, and it uses a Qualcomm chipset. Under Gnome it works without issue. I can see the IMEI, configure the modem and I'm connected right away. Unfortunately when I try to add a connection under Plasma 5 I only get to choose "Generic GSM" or "Generic CDMA". A connection configured with Gnome works under Plasma. You can see the issue in the attached screencast. Below is the output of dmesg relevant to the modem, I hope you can help me. [ 5.264789] usbserial: USB Serial support registered for Qualcomm USB modem [ 5.266236] qcserial 2-6:1.0: Qualcomm USB modem converter detected [ 5.266302] usb 2-6: Qualcomm USB modem converter now attached to ttyUSB0 [ 5.266827] usbcore: registered new interface driver cdc_wdm [ 5.272802] qcserial 2-6:1.1: Qualcomm USB modem converter detected [ 5.273384] qmi_wwan 2-6:1.4: cdc-wdm0: USB WDM device [ 5.450807] qmi_wwan 2-6:1.4 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-6, WWAN/QMI device, XXXXXXXXXXXX [ 5.450845] usbcore: registered new interface driver qmi_wwan [ 5.451826] qcserial 2-6:1.2: Qualcomm USB modem converter detected [ 5.453733] usb 2-6: Qualcomm USB modem converter now attached to ttyUSB2 [ 5.455073] qcserial 2-6:1.5: Qualcomm USB modem converter detected [ 5.455154] usb 2-6: Qualcomm USB modem converter now attached to ttyUSB3 [ 5.470479] qmi_wwan 2-6:1.4 wwp0s20u6i4: renamed from wwan0 Thanks!
Have you tried creating a connection using "Generic GSM"? 4G is still a GSM protocol, so it should work with "Generic GSM".
Created attachment 93386 [details] Screencast under Kubuntu - Generic GSM connection Hello Lamarque, as requested I tried adding a connection with "generic GSM device". The PIN query and sudo prompt came so I guess the card unlocked sucessfully, but a connection could not be established. The two error messages at the end read "Timeout while registering in the GSM network" and "The connection has been deactivated" I'll add the journalctl output right away (Then I have to switch the simcard back to the other modem for the kded5 restarting).
Created attachment 93387 [details] Journald of current boot - Kubuntu 15.04
Well, registering to a GSM network is indeed time consuming, it can take up to four minutes. Probably ModemManager is timing out before registration completes. If that is the case then a second attempt should work. Registration starts only after the sim card in pin unlocked. If there is no pin locking then it starts right after modem is powered up, so not using a pin usually gives more time for registration to complete. Maybe not related to this bug but the messages below mean your old connections' secrets (including pin) have not been imported: Jun 28 18:13:15 HP-EliteBook-850-G1 org.kde.kwalletd5[1198]: Migration agent starting... Jun 28 18:13:16 HP-EliteBook-850-G1 org.kde.kwalletd5[1198]: Migration wizard returned an error or has been canceled. The migration agent will resume upon next daemon start Jun 28 18:13:16 HP-EliteBook-850-G1 org.kde.kwalletd5[1198]: Migration agent stop.
I don't think it's a registration problem. As you can see, in GNOME it gets a lease almost instantly after I finish configuring the connection. Even before that, when I hit configure it already shows the IMEI and the operator. So it is already registered. On plasma it also works if the connection was created by the Gnome network manager. I believe the problem is that the Plasma connection editor does not recognise the modem and only gives me the option to use a generic GSM device. So maybe it tries to register a dummy device. Can there be a problem interfacing with the qcserial driver my modem uses?
And regarding the migration. I don't use kwallet. I want my connections to come up without having to enter another password. This is why I always click "Allow all users to use this connection" to get kwallet out of the picture. I also have no credentials to migrate on this machine.
"Generic Gsm" is just a fallback string when Plasma NM is not able to detect modem's manufacturer and model. From driver point of view all Gsm modems are treated like "Generic Gsm". It seems Gnome's applet tries to pin unlock modems earlier than Plasma NM does. Both Plasma NM and Gnome's applet are just GUI for ModemManager, which is the one that handles all driver related things, so this does not look like a driver issue at all. Well, can you do a test for me? Create a Gsm connection using Gnome's applet and Plasma NM using the same modem but with different connection names. Then send me the files they created so can take a look at them. The files are usually saved in /etc/NetworkManager/system-connections/<connection name>. Depending on your distribution they might be saved in other another place, but I think Arch and Kubuntu save them in that directory.
Created attachment 93397 [details] Arch Gnome without PIN Log of Archlinux Gnome with PIN query disabled
Created attachment 93398 [details] Arch Plasma after adding Connection with Gnome
Created attachment 93399 [details] Arch Plasma only connection
Created attachment 93400 [details] Arch connection file created with Gnome
Created attachment 93401 [details] Arch connection file created with Plasma
Comment on attachment 93401 [details] Arch connection file created with Plasma >[connection] >id=Yesss Plasma >uuid=fdb37424-88ba-4620-a02f-e552e9c326fc >type=gsm >permissions= >secondaries= > >[gsm] >apn=web.yesss.at >number=*99# >password-flags=4 >pin-flags=4 > >[ipv4] >dns-search= >method=auto > >[ipv6] >dns-search= >method=auto
So far so strange. I then tried it with Kubuntu again and at first it failed as well but then it connected... journal log and connection file coming right away
Created attachment 93402 [details] Kubuntu connection file
Created attachment 93403 [details] Journalctl of kubuntu without PIN query
Created attachment 93406 [details] Journalctl after reboot - No connectivity Alright, so after a reboot I'm unable to connect again. See attached journal
(In reply to Paul Konecny from comment #6) > And regarding the migration. I don't use kwallet. I want my connections to > come up without having to enter another password. This is why I always click > "Allow all users to use this connection" to get kwallet out of the picture. > I also have no credentials to migrate on this machine. The lines below indicate that KUbuntu is using kwallet's pam integration, so as long as you use your user password to lock kwallet then pam will automatically unlock it right after you login without any user intervention: Jun 29 17:37:20 HP-EliteBook-850-G1 sddm[882]: Checking for pam module Jun 29 17:37:20 HP-EliteBook-850-G1 sddm[882]: Got pam-login Jun 29 17:37:20 HP-EliteBook-850-G1 sddm[882]: kwalletd: Waiting for hash on 17- Jun 29 17:37:20 HP-EliteBook-850-G1 sddm[882]: kwalletd: waitingForEnvironment on: 20 Jun 29 17:37:20 HP-EliteBook-850-G1 sddm[882]: kwalletd: client connected Jun 29 17:37:20 HP-EliteBook-850-G1 sddm[882]: kwalletd: client disconnected
(In reply to Paul Konecny from comment #17) > Created attachment 93406 [details] > Journalctl after reboot - No connectivity > > Alright, so after a reboot I'm unable to connect again. See attached journal By the snippet below it looks like dhcp requests are timing out. Also, registration to operator's network sometimes times out as well. Can Jun 29 17:38:11 HP-EliteBook-850-G1 NetworkManager[757]: <info> Auto-activating connection 'Yesss 2'. ... Jun 29 17:38:11 HP-EliteBook-850-G1 ModemManager[737]: <info> Simple connect state (4/8): Wait to get fully enabled ... Jun 29 17:38:11 HP-EliteBook-850-G1 ModemManager[737]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> enabled) Jun 29 17:38:11 HP-EliteBook-850-G1 ModemManager[737]: <info> Simple connect state (5/8): Register ... Jun 29 17:39:12 HP-EliteBook-850-G1 ModemManager[737]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (searching -> idle) Jun 29 17:39:12 HP-EliteBook-850-G1 NetworkManager[757]: <warn> (cdc-wdm0) failed to connect modem: Network timeout ... Jun 29 17:38:16 HP-EliteBook-850-G1 ModemManager[737]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> searching) ... ... Jun 29 17:38:37 HP-EliteBook-850-G1 login[1916]: pam_unix(login:session): session opened for user paul by LOGIN(uid=0) ... Jun 29 17:39:23 HP-EliteBook-850-G1 ModemManager[737]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> registering) ... Jun 29 17:39:23 HP-EliteBook-850-G1 ModemManager[737]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (searching -> registered) ... Jun 29 17:39:23 HP-EliteBook-850-G1 NetworkManager[757]: <info> (cdc-wdm0): modem re-registered; re-checking autoconnect Jun 29 17:39:23 HP-EliteBook-850-G1 NetworkManager[757]: <info> Auto-activating connection 'Yesss 2'. Jun 29 17:44:32 HP-EliteBook-850-G1 NetworkManager[757]: <info> Activation (wwan0) Beginning DHCPv4 transaction (timeout in 45 seconds) ... Jun 29 17:45:17 HP-EliteBook-850-G1 NetworkManager[757]: <info> (cdc-wdm0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] ... Jun 29 17:47:53 HP-EliteBook-850-G1 NetworkManager[757]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested) ... Jun 29 17:48:29 HP-EliteBook-850-G1 kernel: usb 1-1: USB disconnect, device number 2
All this looks like driver issue to me or your operator's network has weak signal or is busy where you live. For the dhclient timeouts can you check if there is more than one instance of it running (for the same interface) when that happen? If so then one dhclient may be conflicting to the other.
It should not be signal quality. I've got almost full 4G bars on my phone with the same operator and considering the larger antennas in the notebook this should not be the source of this problem. https://krivokuca.net/2012/08/hp-8560p-gobi-3000-qcserial-and-gobiserial-blues/ Here one guy also has problems with qcserial and switched to "GobiSerial" and they had to maintain it out-of-tree and even fork it. Any idea where I should report this if it really is a driver issue?
qcserial and GobiSerial are ModemManager's drivers. You should report MM bugs in https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager
Hmmm actually they are kernel modules. So you should report bugs in https://bugzilla.kernel.org/. Probably there is a bug entry about this issue there already.
Hi Lamarque, it seems that this issue indeed was originating from the driver https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=59536da34513c594af2a6fd35ba65ea45b6960a1 According to this link it should be fixed in Kernel 4.4 As soon as I get my hands on this Kernel I'll retest. Thanks!
modemmanager-qt-5.3.1 has never been released, but I guess 5.9.0 was meant here because Plasma-5.3.1 depends on modemmanager-qt-5.9.0.
Paul, were you able to test with newer kernel?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!