Arch Linux User Repository

Cannot install on 5.17 latest kernel. Installs fine on 5.15 lts.

==> dkms install --no-depmod r8152/2.15.20211119 -k 5.17.1-arch1-1
Error! Bad return status for module build on kernel: 5.17.1-arch1-1 (x86_64)
Consult /var/lib/dkms/r8152/2.15.20211119/build/make.log for more information.
==> WARNING: `dkms install --no-depmod r8152/2.15.20211119 -k 5.17.1-arch1-1' exited 10

It works. Thank you!

I've fixed the compilation issue in a new release, but not yet tested with my Dell docking station. "Should work"

Fails with exit code 10 on recent kernel:

...
(3/3) Install DKMS modules
==> dkms install --no-depmod r8152/2.15.20210629 -k 5.15.2-arch1-1
Error! Bad return status for module build on kernel: 5.15.2-arch1-1 (x86_64)
Consult /var/lib/dkms/r8152/2.15.20210629/build/make.log for more information.
==> WARNING: `dkms install --no-depmod r8152/2.15.20210629 -k 5.15.2-arch1-1' exited 10
==> dkms install --no-depmod r8152/2.15.20210629 -k 5.10.79-1-lts
==> depmod 5.10.79-1-lts

Change arch to 'any'. I don't see why it needs to be i686 and x86_64 only.

Hello, Thanks for making this available. I'm testing it on Manjaro now, with the help of someone who actually knows how to compile new modules into the kernel. I realize y'all can't support Manjaro installs. I'm posting more to see if anyone has noticed the same behavior.

I and another user have run into an issue. With an adapter using the 8156 chipset attached to a Raspberry Pi running Manjaro ARM via the first USB 3.0 port, the Pi can no longer boot from an SSD attached to the second USB 3.0 port. No drive activity at all.

The current solution is to plug the SSD drive into the USB 2.0 port. It works fine, but it's slower.

There's a better than even chance the Pi 4b's USB 3 bus just can't deal with more than one high performance device. The hardware predates USB booting on the Pi being a thing, for example, and a lot of people ran into issues with the USB 3 bus having enough power to boot the machine when that was first announced.

I'm not sure where I should be looking for error logs. My dmesg record did not include info going back far enough. Any suggestions for troubleshooting would be welcome.

Thanks!

Shouldn't line 28 -e "s/@PKGVER@/${_pkgbase}/g" \ be -e "s/@PKGVER@/${pkgver}/g" \ ?

Solves the problem thanks

Thanks a lot mic_e for your patch. PR merged and package updated :)

Seems to be broken. With kernel 5.7.2-arch1-1 and r8152-dkms 2.13-1

I get the error message "couldn't register device" with the following traceback:

https://pastebin.com/j7QacwZB

There's no upstream update, and upstream says that it works up to Linux 5.6 only :(

I'll see if there's an easy patch... I wish they'd just upstream this driver, but looking at the source code it's unlikely to happen.

Edit: I've bisected the kernel between 5.6 and 5.7 to arrive here:

9000edb71ab29d184aa33f5a77fa6e52d8812bb9 is the first bad commit commit 9000edb71ab29d184aa33f5a77fa6e52d8812bb9 Author: Jakub Kicinski kuba@kernel.org Date: Mon Mar 16 13:47:12 2020 -0700

net: ethtool: require drivers to set supported_coalesce_params

Now that all in-tree drivers have been updated we can
make the supported_coalesce_params mandatory.

To save debugging time in case some driver was missed
(or is out of tree) add a warning when netdev is registered
with set_coalesce but without supported_coalesce_params.

Edit: I've created a PR: https://github.com/wget/realtek-r8152-linux/pull/5/files