Of “dmesg.txt” (no underscore “_
”) and “dmesg_.txt” (an underscore “_
” in log name) it looks like both show a difference in HUBs, so I’m not sure which one is which of those. What condition is different between the two dmesg logs? Can you describe what differs for the two log files? Both do show the same repeating (and definite error, despite not calling it an error) log line:
[ 499.995801] cdc_ncm 1-2.3.1:2.0 usb0: 1000 mbit/s downlink 1000 mbit/s uplink
(but the second “dmesg_.txt” does seem to get further)
The “log_lsusb_.txt” (with “_
” underscore) shows one fewer device than the other log, that being:
Bus 002 Device 004: ID 0bda:8156 Realtek Semiconductor Corp.
Can I verify which HUB is used for the “lsusb
” case with or without the underscore “_
”? The tree view with “_
” runs at USB3.1 gen. 1 speeds, while the tree view without underscore “_
” loses signal quality and drops back to USB2 speeds. I’m not sure if signal actually contributes to that repeated line in dmesg
logs, but it seems unlikely to be the primary cause. The log does not indicate how or why the device is continuously dropping and reconnecting (there is no disconnect log, only repeated connects).
I’d like to see a verbose “lsusb
” for this device in the case where it runs at the full USB3.1 speed (you’ll have to use or ignore the HUB based on whichever log shows “5000M
” at the end of its description under “lsusb -t
”, but I don’t know yet what the HUB setup was):
sudo lsusb -vvv -d 0bda:8156 2>&1 | tee log_verbose.txt
This is likely unrelated, but is the system being shut down cleanly? I see this:
[ 499.158614] FAT-fs (sda1): unable to read boot sector to mark fs as dirty
A side note on USB ID follows, and may not be particularly relevant, but could be of interest to some since it relates to how mature the driver detection might be:
FYI, product ID 0bda is “Realtek” (not a surprise), and within Realtek, device 8156 is not fully described. I’ve seen this ID many times on the forums, so it isn’t new, but the official repository ID list is not yet updated…this in itself might cause issues at times finding a driver, but your system did find cdc_ncm
, so that isn’t an issue. There is this comment on IDs (I include because it has been described back in late 2020, and it seems many people have used this adapter since then):
Name: RTL8156 2.5GBASE-T Ethernet Adapter
Not sure if "2.5 Gigabit Ethernet Adapter" would be a better name
Windows names it a "Realtek USB 2.5GbE Family Controller"
Chip is inside a Delock 2.5Gigabit LAN Adapter (66299), Chip name according to manual, I did not break open the plastic case
iProduct 2 USB 10/100/1G/2.5G LAN
Cmdr_Zod
2020-12-31 13:03:01