I have a USB 2.5GB ethernet adapter that stopped working after taking the 6.3.5 kernel. I had to boot to previous kernel (kernel-6.2.15-200) to get it to work again.
I see the following ModemManger entries that I believe are related:
Jun 4 06:03:36 noahsark ModemManager[984]: [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1’: not supported by any plugin
Jun 4 06:03:36 noahsark ModemManager[984]: [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:19.0’: not supported by any plugin
Jun 4 06:03:36 noahsark ModemManager[984]: [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0’: not supported by any plugin
I also see this just prior to the ModemManager logs:
Jun 4 06:03:33 noahsark kernel: RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
Jun 4 06:03:33 noahsark kernel: r8152 3-1:1.0 enp0s20u1: carrier on
Jun 4 06:03:33 noahsark kernel: r8169 0000:02:00.0 enp2s0: Link is Down
Jun 4 06:03:33 noahsark kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u1: link becomes ready
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9589] device (enp0s20u1): carrier: link connected
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9596] device (enp0s20u1): state change: unavailable → disconnected (reason ‘carrier-changed’, sys-iface-state: ‘managed’)
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9602] policy: auto-activating connection ‘Wired connection 1’ (10ec9b48-b5d3-3062-9b71-374705ab9cd9)
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9606] device (enp0s20u1): Activation: starting connection ‘Wired connection 1’ (10ec9b48-b5d3-3062-9b71-374705ab9cd9)
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9607] device (enp0s20u1): state change: disconnected → prepare (reason ‘none’, sys-iface-state: ‘managed’)
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9610] manager: NetworkManager state is now CONNECTING
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9611] device (enp0s20u1): state change: prepare → config (reason ‘none’, sys-iface-state: ‘managed’)
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9669] modem-manager: ModemManager available
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9670] device (enp0s20u1): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Jun 4 06:03:33 noahsark NetworkManager[877]: [1685876613.9680] dhcp4 (enp0s20u1): activation: beginning transaction (timeout in 45 seconds)
Device enp0s20u1 is not connected but is plugged into the system. The USB adapter is enp0s20u1c2.
I’m not sure what to look at here but I need to get this fixed so that I can upgrade to FC38.
I have the same problem. The USB 2.5GB ethernet adapter (r8152) that I have also stopped working after upgrading to 6.3 kernel. However it works on 6.2 kernel.
I haven’t had time to work on this as it takes out my entire network as this is my LAN connection to my home network. I was going to try booting without the adapter connected then once up, connect to a different USB port and see if it gets detected. Ideally I was hoping someone else here had the same issue and found a solution.
I do my updates weekly on Saturday nights and my fear is I get another kernel update that does not work and I lose access to the working kernel.
“I was going to try booting without the adapter connected then once up, connect to a different USB port and see if it gets detected.”
I tried this but it didn’t work for me. You can always try on your end.
“My fear is I get another kernel update that does not work and I lose access to the working kernel.”
Same here, What you can do is to backup the OS on an image that you can restore later. Or use snapshots (in case you’re using BtrFS). I’m just commenting and replying so that the thread won’t close or die.
You may be correct here. I have never had to run a previous kernel version. I just assumed that when there was a kernel update the oldest was removed keeping new and 2 previous.
I can confirm adding the udev rule works. I added the rule per that video and after rebooting, the adapter was detected but with a new ID. Old ID was enp0s20u1c2 and now it is enp0s20u1. I had to reconfigure the adapter as it was manually set. Once I did that, it works. I guess this was a blessing in disguise because ethtool always reported that nic as being half-duplex. Now it shows full!
