Arch Linux

tom0000

Member

Registered: 2015-02-03

Posts: 5

Anker USB 3 hub with Realtek 8153 GbE driver problem

Device shows up in lsusb and lshw, but is shown in lshw as UNCLAIMED.
dmesg only displays the detected hubs, plus one extra SuperSpeed USB device (but nothing after that).

My arch kernel (3.18.5-1-ARCH) has USB_RTL_8152 compiled as a module, but it doesn't autoload even though it thinks it should support that device:

$ lsusb -d 0bda:
Bus 003 Device 009: ID 0bda:8153 Realtek Semiconductor Corp. 
$ modinfo /lib/modules/3.18.5-1-ARCH/kernel/drivers/net/usb/r8152.ko.gz  | grep 8153
description:    Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
alias:          usb:v0BDAp8153d*dc*dsc*dp*ic*isc*ip*in*

If I manually try to load it via

$ sudo modprobe -v r8152

I get this in dmesg:

r8152: disagrees about version of symbol module_layout

Googling that message suggests that it often means the driver was compiled against the wrong kernel version, and that can be checked by looking at the --modversions output of the module. I did that for this and the one for my wireless card (which is working fine) and they match:

$ modprobe --dump-modversions /lib/modules/3.18.5-1-ARCH/kernel/drivers/net/usb/r8152.ko.gz | grep module_
0x1243024e	module_layout
$ modprobe --dump-modversions /lib/modules/3.18.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz | grep module_
0x1243024e	module_layout

The vermagic also matches between those two:

$ modinfo /lib/modules/3.18.5-1-ARCH/kernel/drivers/net/usb/r8152.ko.gz | grep vermag
vermagic:       3.18.5-1-ARCH SMP preempt mod_unload modversions 
$ modinfo /lib/modules/3.18.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz | grep vermag
vermagic:       3.18.5-1-ARCH SMP preempt mod_unload modversions

Anyone have any advice on moving forward?

tom0000

Member

Registered: 2015-02-03

Posts: 5

Re: Anker USB 3 hub with Realtek 8153 GbE driver problem

As an update to this issue, the driver did load correctly if the device was attached during boot, and I am then free to remove/reattach it.

This is still a strange situation though, so I'd appreciate any suggestions on how to figure out the driver loading issue.