blaede.family is one of the many independent Mastodon servers you can use to participate in the fediverse.
Private Mastodon server for members of the Blaede family.

Administered by:

Server stats:

6
active users

Can anyone familiar with GNOME, NetworkManager, Fedora Silverblue, or Intel network cards help?

I have an Intel NUC running Fedora Silverblue 40 with GNOME 46. It’s connected to Ethernet but at some point I connected it to Wi-Fi. Since the Ethernet connection gives better performance—and I don’t want unnecessary interference—I turn off Wi-Fi in GNOME. Whenever I reboot, both Ethernet AND Wi-Fi are disabled. If I leave Wi-Fi enabled, it remains enabled when I reboot.

@cassidy hello. One of NetworkManager developers here.

What do you mean "ethernet disabled". Mind sharing output of "nmcli c" and "nmcli d"? DM is okay, if there's anything secret.

@lkundrak it’s disabled as in the quick toggle in GNOME (and the GNOME Settings panel) shows that it’s turned off, but I can toggle it back on.

I did after this boot, and `nmcli c` shows `enp2s0` as the ethernet connection’s name, `lo` as the loopback device’s name, then a couple of saved SSIDs with `--` in the device column. I'll check what it shows when I reboot without toggling it back on.

@cassidy "nmcli c" certainly doesn't list "enp2s0" device, because it lists configuration profiles that apply to devices. verbatim output would help me not second-guess (you can use a pastebin if the output is too big to fit in a toot).

I'm going to assume you got a connection profile named "enp2s0". Does "nmcli -f connection.autoconnect c show enp2s0" say "yes"? If so, something's wrong with the device. "nmcli d" should indicate if it's available for configuration.

If it says "no", then "nmcli c modify enp2s0 connection.autoconnect yes" will do the trick.

(sorry I don't know what precisely does the toggle in GNOME do. CLI will be quicker)

@lkundrak

cassidyjames@nuc11:~$ nmcli c
NAME UUID TYPE DEVICE
enp2s0 ba80e6e1-81b3-458c-abe3-85439c702fb6 ethernet enp2s0
lo 7e4c0d19-742f-4984-8a06-68da84dad794 loopback lo
Cassidy’s Pixel 8 fcdcf7a2-f683-4084-886a-f518ac12a70d wifi --
QT-KT 1f1e9bbf-3572-4079-9ed6-214450e4f87b wifi --

@cassidy yes, this means that connection profile with NAME "enp2s0" is active on a DEVICE named "enp2s0".
That means ethernet should be connected.

@lkundrak hm,

$ nmcli -f connection.autoconnect c show enp2s0
connection.autoconnect: no

I wonder if I changed something accidentally in the settings?? I’ll switch that on and then be happy, it sounds like.

Thanks so much!

Cassidy James :eos: :gg: :fh:

@lkundrak aha, maybe I toggled this! 🙈

(I honestly didn’t even realize there were all these settings for the wired connection exposed in GNOME Settings, oops)

Edit: yep, I turned this on, rebooted, and Ethernet remained connected. I feel like a dummy, but thanks everyone for the help!