netdev - Re: Debian Bookworm requires r8168-dkms for RTL8111D

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47017183-419c-438b-8b5b-b2b584bd62f2@gmail.com>
Date: Sun, 21 Jul 2024 22:08:33 +0200
From: Heiner Kallweit <hkallweit1@...il.com>
To: Dave Gomboc <dave_gomboc@....org>, nic_swsd@...ltek.com,
 romieu@...zoreil.com
Cc: netdev@...r.kernel.org
Subject: Re: Debian Bookworm requires r8168-dkms for RTL8111D - regression
 from Buster 10.13.0

On 21.07.2024 03:33, Dave Gomboc wrote:
> I am sending this email because of the suggestion in
> /usr/share/doc/r8168-dkms/README.Debian.
> 
> Installation using a Debian Bookworm 12.2.0 amd64 DVD-ROM does not
> find the onboard gigabit ethernet (RTL8111D-based) on one of my
> mainboards (Gigabyte GA-890GPA-UD3H).  The network came up fine as
> soon as I used apt-offline to update/upgrade, then to fetch and
> install r8168-dkms.
> 
> Installation using a Debian Bullseye 11.8.0 amd64 DVD-ROM does not
> find the onboard NIC either.  However, installation using a Debian
> Buster 10.13.0 amd64 DVD-ROM does find the onboard NIC and can use it
> directly.  (Unfortunately, installing from that DVD-ROM later failed
> for some other reason.)
> 
> With r8168-dkms in operation, the relevant part of "lspci -v -v -v" reads:
> 
> 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Co
> ntroller (rev 03)
>        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+
>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>        Latency: 0, Cache Line Size: 4 bytes
>        Interrupt: pin A routed to IRQ 18
>        NUMA node: 0
>        Region 0: I/O ports at ee00 [size=256]
>        Region 2: Memory at fdfff000 (64-bit, prefetchable) [size=4K]
>        Region 4: Memory at fdff8000 (64-bit, prefetchable) [size=16K]
>        Expansion ROM at fd600000 [virtual] [disabled] [size=128K]
>        Capabilities: <access denied>
>        Kernel driver in use: r8168
>        Kernel modules: r8168
> 
> Please let me know if there is further information I can provide that
> would assist you in getting this supported directly by the r8169
> driver.
> 
Questions regarding downstream kernels should be addressed to the support
of the respective distribution.

Please retest with a recent mainline kernel.
What do you mean with "does not find the device"? Even lspci doesn't show it?
Please provide a full dmesg log.

It's not clear which kernel version you're using. Please make sure that it's a
version including the following fix:
5d872c9f46bd ("r8169: fix issue caused by buggy BIOS on certain boards with RTL8168d")

> Dave Gomboc
>