Dennis HilkLinux diagnosticsDE

Ethernet & networking

Realtek RTL8153 USB Ethernet family

RTL8153-based USB Ethernet uses r8152, even though the chip name ends in 8153. USB transport speed and Ethernet link speed must be inspected separately when a dock feels slow.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The Realtek vendor constant is 0bda and the USB table accepts product 8153. Many docks can expose this controller, so the pair does not establish the complete dock brand or its other USB functions.

Curated identifiers
usb 0bda:8153

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The source selects firmware and operations after detecting its silicon version. The USB configuration also documents ECM fallback behavior; observe the interface’s driver rather than assuming every mode binds identically.

  • r8152 — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Conditional firmware path

These inspected files are examples from different detected RTL8153 silicon versions. USB product 8153 alone cannot choose one; driver selection and the actual firmware request are needed.

Checked examples or filename branches, not a complete installation list:

  • rtl_nic/rtl8153a-2.fw
  • rtl_nic/rtl8153b-2.fw

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Read the USB vendor/product pair

lsusb -d 0bda:8153

Confirms a visible USB descriptor pair 0bda:8153. It identifies the controller family, not the dock brand or the bound interface driver. No root access is normally needed.

Inspect the USB topology

lsusb -t

Locate the adapter under its USB bus. Driver names and 480M/5000M describe interface binding and USB transport speed; they do not report Ethernet carrier speed.

Identify the network interface driver

ethtool -i INTERFACE

Replace INTERFACE with the real interface name. Driver and bus-info connect this interface to its device. A displayed firmware-version is adapter information; it does not prove a file was loaded. Candidate: r8152.

Compare supported modes with the current link

ethtool INTERFACE

Supported/advertised link modes describe capability or negotiation offers. Speed, Duplex and Link detected describe the current link, not measured throughput. An unsupported query is a limitation of the interface/driver.

Inspect initialization and firmware requests

sudo journalctl -k -b --no-pager

Elevated access may be needed. Root reads the current boot kernel journal. Locate this controller/interface and the exact requested filename or Safe Mode message. Module-wide firmware declarations are not proof that every listed file was requested for this device.

Limitations & related issues

A 480M USB path can constrain transfers even while Ethernet reports a gigabit link. Suspend-related USB detach/reset messages need the hub and USB power context, not just the Ethernet carrier log.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.