I don’t mean to hijack the thread, I hope you don’t mind me stepping in since I have the same problem on my hands.
I do believe the issue arises from the changes that came with the upgrade from 34 to 35. There is quite some changes to the Mobile Networks section of the Settings panel now. There seems to be inadequate communication of some sort with the Network Manager - I’ve noticed that the OS keeps automatically creating a new “Standard” connection every time I plug in the USB modem and turn Mobile Connection on. At the same time connections that I’ve created with the Network Manager GUI don’t show up in the Mobile Connections section of the Settings panel, but they do show up in the drop-down menu in the upper right corner of the screen (I use the Gnome desktop).
I’ve confirmed that the problem is not in the USB modem or the SIM-card or the APN I’ve input - the device continues to work just fine on another machine, just like it did on my Fedora installation before the version upgrade.
On my machine nmcli connection up wifi returns Error: unknown connection 'wifi'. I do have WIFI turned on, working, and an active connection to a wireless modem.
A USB device is reconfigured each time it is connected/booted/disconnected and may even take a different device name. For example, with my 3D printer, if I unplug it then plug it back in, what was originally /dev/ttyUSB0 may become /dev/ttyUSB1 and that WILL interfere with the original config and communications. USB devices are configured and removed by udev so to ensure 100% that it is always configured the same you need a rule in /etc/udev/rules.d/ to define how that device should always be configured.
Sorry the name is likely something like wlp3s0 or similar, wifi is the “type”.
There is also rfkill, if you run that and it reports your wlan is HW unblocked and SW blocked rfkill unblock wlan will unblock the SW side and you should be good to go. You may need to be sudo for those commands that change things.
wlan was unblocked under both SOFT and HARD. I ran sudo rfkill unblock wlan anyway for good measure, but nothing changed.
nmcli connection show lists saved connections. The saved Mobile Broadband connections are listed as gsm under TYPE, but under DEVICE for these connections there is just --, although the USB modem is plugged in and powered by the machine. The bridge and wifi connections do have listed devices.
I think I see some confusion here. I know I was misled by my initial understanding.
Your issue at least is an issue with the broadband connection and not the wifi connection and most of the suggestions to date have been wifi related.
This means the issue is likely a driver missing.
Please post the output of dmesg | tail run immediately after plugging in the broadband modem then also inxi -Fxx as well as lsusb while the modem is plugged in. These bits of information may allow us to identify the exact chipset in the modem so we can verify the driver and get the device properly configured.
You also should tell the system to forget the earlier connections seen in the menu from the upper right of the screen so you are working with only one when done.
I agree your issue is similar to the OP, but it is different hardware and thus the fix is likely different.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 058f:3841 Alcor Micro Corp. USB 2.0 PC Camera
Bus 001 Device 006: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 012: ID 25a7:fa61 Areson Technology Corp Elecom Co., Ltd MR-K013 Multicard Reader
Bus 001 Device 016: ID 19d2:0031 ZTE WCDMA Technologies MSM MF110/MF627/MF636
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
shows the device in lsusb. It also is shown with the first line of the output from dmesg.
This means the system sees it, but is not properly configuring it.
I found this link with a search for the line I quoted above and it seem relevant to your issue. I realize that is an old bug discussion but it likely will still apply in that it seems the fix was to create a udev rule so the system properly recognized and configured it. There were other links as well but I did not review all.
If that modem worked with F34 and the upgrade to F35 broke it then it certainly should be reported as a bug since something caused the previously functional device to be no longer configured properly. In fact I would venture that it is almost mandatory that a new bug be filed, even if you get it working with a udev rule. Only with a bug report will the developers be informed of the regression caused here. Log in to Red Hat Bugzilla
No luck yet. Using gedit I added the device to 40-usb_modeswitch.rules, but that didn’t change things. I still get the same behavior and the same output I posted above when I try to manually start the mobile broadband connection.
From your command inxi -Fxx your device name not wifi, but wlp1s0. For the exact name you could check with what @jakfrost suggested above. You’ll never be able to run nmcli connection up wifi if your device name are not wifi for activate Wifi connection.
nmcli connection up doesn’t work neither with the TYPE nor the DEVICE arguments, it works with the NAME argument and that’s the way I use it to try and manually activate said connection - nmcli connection up [name-of-connection]. In this syntax the command turns on and off my WIFI connection just as it should, but, as I said, it returns the activation errors I posted above when I try to turn on my broadband connection.
My last idea. SInce the output of your lsusb already mention Bus 001 Device 016: ID 19d2:0031 ZTE WCDMA Technologies MSM MF110/MF627/MF636 from the article means the dongle already detected as modem by the system (the are commons two mode: storage and modem).
May be you could narrow it down on the setting of wvdial.
OK, so I tried a more comprehensive documentation for wvdial and I got to the following: After I installed the package I ran wvdialconf /etc/wvdial.conf to create and fill in the configuration file (as per instructions) and after scanning the ports for a modem it returned Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? This with the Broadband Connections being turned on or off from the Settings panel and while the modem is plugged in, recognized, and powered by the system.
Is it possible maybe that there is a mounting issue at play?