Realtek usb ethernet adapter not working

[sisxph]

Describe the bug

My RTL8157 ( Wisdpi ) is not recognized and not working under bluefin:latest

What did you expect to happen?

It should be working out of the box as it is under fedora-atomic

Output of bootc status

to do

Output of groups

to do

Extra information or context

output of lsusb

[Boyda-dev]

I have the same issue with the same adapter

output of bootc status:

Staged image: ghcr.io/ublue-os/bluefin-dx-nvidia-open:latest
Digest: sha256:143178f633d77e205b285131b4289f697f337adee847e8abbb2d821c290326d1 (amd64)
Version: latest-42.20250801.3 (2025-08-01T06:26:03Z)

● Booted image: ghcr.io/ublue-os/bluefin-dx-nvidia-open:latest
Digest: sha256:6ef8becdc0aa9e64a680734af92aca0f756f0d646d69ac5e34d3c546dec49e2e (amd64)
Version: latest-42.20250731.1 (2025-07-31T07:28:08Z)

Rollback image: ghcr.io/ublue-os/bluefin-dx-nvidia-open:latest
Digest: sha256:4fa87d0c1ae13ada1c8bcd480ec70298aac3b67f444c9964d55fff355ededf59 (amd64)
Version: latest-42.20250730.2 (2025-07-30T10:53:23Z)

output of groups:

wheel dialout docker incus-admin libvirt

output of lsusb:

Bus 001 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 002 Device 002: ID 0bda:8157 Realtek Semiconductor Corp. USB 5G Ethernet
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 004: ID 0763:2012 M-Audio M-Audio Fast Track Pro
Bus 003 Device 005: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 003 Device 006: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI)
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 003: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub

[CrustyB]

Similar issue. The NIC connects at 1Gb/s, and works... Kind-of. Latency is about 10X normal. Tried on Fedora 42 kernel 6.15.9-201.fc42.x86_64 and Proxmox 8.4.11 optional kernel 6.14.8-2-bpo12-pve 100Mb/s, 2.5Gb/s and 5Gb/s rates are not shown to be advertised at all.

Seems to be a kernel driver issue and not related to ublue-os, Fedora, or Debian.

[repires]

AI Generated:

The RTL8157 USB Ethernet adapter issue on Bluefin is a known problem and appears to be a broader Linux kernel driver issue, not something specific to Bluefin. The device is detected by lsusb but doesn't function properly as a network device. Other users have reported similar problems on Fedora and Proxmox with recent kernels, and higher speeds (2.5Gb/s, 5Gb/s) are not advertised, with high latency at 1Gb/s. This suggests the root cause is upstream in the kernel driver, not in Bluefin itself. There are no recent Bluefin updates or pull requests that address this adapter, and Bluefin inherits its driver support from Fedora and the mainline kernel, with no explicit inclusion or blacklisting of the RTL8157 driver/module in its build scripts or configs.

If you need the adapter working immediately, manual driver installation (building from source, DKMS/akmods) is sometimes possible, but this can cause update headaches and requires Secure Boot management. There are no pre-built akmod or COPR packages for this driver in Bluefin. The best course is to monitor Fedora and upstream kernel bug trackers for RTL8157-related fixes, and keep Bluefin updated to the latest kernel releases, as future updates may improve support. If you find the device works on Fedora Atomic but not Bluefin, double-check the exact kernel versions and modules loaded, as that may help pinpoint the difference.

For more details and community discussion, see the original issue thread and related kernel driver context.