Just installed Leap 42.2. After looking at lsusb, I can see that there is this broadband
##### lsusb #############################
Bus 001 Device 007: ID 8087:0a2a Intel Corp.
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 03f0:521d Hewlett-Packard
Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp.
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
But in NetworkManager there is no Mobile Broadband entry…
I’m not sure it’s as simple as the following, but maybe worth a shot…did you try the udev rule mentioned here?
eg /etc/udev/rules.d/30-mobile-broadband.rules
Just did with your line and then replaced VID PID with my values. No go… But looking at usb-devices output I see that there is no driver for device. I think there should be something. Now witch module should I try to load?
Hi, it seems that your modem has been added to the 2.4 version of package usb_modeswitch-data.
You can find it in the “hardware” repository: search for it at openSUSE Software
and “Show unstable packages”. You may have to install a matching version of usb_modeswitch too.
Although, some claim that they were able to get the device working via the usbserial driver, that won’t expose the QMI functionality that the device is capable of. Refer to this reply by Bjorn Mork) with a suggestion to first try
some further steps outlined there. It might be that the udev rule can be changed to reflect the desired configuration, and a recent ModemManager is required as well.
Thank you very much for help. I installed Tumbleweed to have latest packages, also installed newest usb_modeswitch and usb_modeswitch-data. After that I did exactly what was written in Mint forum post. And bingo! I have working 3G! Now will try to do this with Leap. Just one question. How to make this to stay after reboot ? Because after reboot it goes away…
This is a workaround designed to get your hardware functioning with the option driver to provide a basic level of support for this chipset. (AFAIU, it should be capable of 4G with qmi_wwan driver and correct config mode). Longterm, the chipset should be added to the driver explicitly and you could compile the driver from source to do this yourself. However, for now you could create a script containing the commands that you typed that gets executed at boot, then create a systemd service to have it run at boot…
Ok, the error seems to be related to the wvdial command. I recommend removing it from your script as part of this troubleshooting exercise. Although I don’t have this device, I was able to start the custom service without error once I removed the wvdial command. My thinking is that the device is not initialised at the time the wvdial program runs. That could be automated with another service if desired, or maybe a delay inserted using the sleep command.
BTW, instead of using wvdial dialling utility to initiate the connection, you should be able to get NetworkManager to recognise the device and activate it. You need to make sure NM is running first, but after that you should be able to add a mobile broadband connection using the NM connection editor.
Strange thing happen. My modem is gone… Output of lsusb:
Bus 003 Device 005: ID 8087:0a2a Intel Corp.
Bus 003 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 003 Device 003: ID 04ca:7053 Lite-On Technology Corp.
Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Will try to remove service and reboot…
Nothing happened after removing service and rebooting. Still no modem???
Went to bios to look for settings and maybe for some diagnostic and found setting: “wwan quick connect”. After switching it off and rebooting modem come back! I think that modem was switched off somehow when system was sleeping, and not woke up when system woke up. Of cause do not know if switching off mentioned option will help…
BTW, instead of using wvdial dialling utility to initiate the connection, you should be able to get NetworkManager to recognise the device and activate it. You need to make sure NM is running first, but after that you should be able to add a mobile broadband connection using the NM connection editor.
No, modem do not work until I run wvdial… I can not make broadband connection using NM (I am on Gnome). Modem is there but I can not use it. After wvdial run I can add mobile broadband connection using the NM.
So, with only ‘wvdial’ removed from the script the huawei.service starts ok? Check the status again with
systemctl status huawei.service
As a test, you should be able to run ‘wvidal 3G’ manually once you’ve logged in.
To automate the dialling, you can try inserting a delay in your script like this
sleep 10
wvdial 3G
The delay value (in seconds) might have to be experimented with a bit.
Alternatively, create an autostart file so that the dialling utility runs a bit later when you login. The 3G device will be initialised by then. The exact method will depend on the desktop environment you’re using.