Bug#1036992: r8168-dkms: When Purging this driver, it does not restore the original driver.

[MA]

Package: r8168-dkms
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-23-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages r8168-dkms depends on:
ii dkms 2.8.4-3

r8168-dkms recommends no packages.

r8168-dkms suggests no packages.

[MA]

Package: r8168-dkms
Followup-For: Bug #1036992

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?===> I installed r8168-dkms by accident. To revert it i purged the same package to reload my original driver package(r8169)

* What exactly did you do (or not do) that was effective (or

ineffective)? ===> I tried to purge the r8168-dkms.
* What was the outcome of this action? ==> No expected changes and the driver for my Ethernet still shows as r8168 in lspci -k command
* What outcome did you expect instead?==> i expected the installed driver to be removed and reload the kernel built in driver(which is currently nowhere to be found)

[Andreas Beckmann]

On 31/05/2023 20.52, MA wrote:
> * What was the outcome of this action? ==> No expected changes and the driver for my Ethernet still shows as r8168 in lspci -k command
> * What outcome did you expect instead?==> i expected the installed driver to be removed and reload the kernel built in driver(which is currently nowhere to be found)

which will happen upon reboot

Replacing the network driver would require stopping the network (and all
services using the network), unloading the kernel driver, loading the
new kernel driver, bringing up the network again. That works best if
done by a reboot.

Andreas

[Andreas Beckmann]

[please keep the bug in Cc:]

On 01/06/2023 04.06, Mohammed Anas wrote:
> Sorry to not mention it, But after purging the new driver , i did reboot
> the system. But the old driver was still not loaded.

Weird. How did you purge the new driver?

Please send the output of the following command:

find /lib/modules /usr/src /var/lib/dkms -name '*r8168*'


Andreas

[Mohammed Anas]

i used the below command to purge:
sudo apt purge r8168-dkms

find /lib/modules /usr/src /var/lib/dkms -name '*r8168*'

output:
/lib/modules/5.10.0-23-amd64/kernel/drivers/net/ethernet/realtek/r8168.ko.bak


Please note that I have reinstalled my linux kernel in an attempt to make the ethernet interface work again , which has installed the kernel built-in driver and solved my problem .

Below are the files under /lib/modules/5.10.0-23-amd64/kernel/drivers/net/ethernet/realtek before i reinstalled my kernel and after purging the r8168-dkms driver:
8139cp.ko 
8139too.ko
r8168.ko
r8169.bak

Then i had changed r8168.ko to r8168.ko.bak and r8169.bak to r8169.ko , and reboot, in an attempt to reload the driver r8169, but didn't work. And FInally did a kernel reinstall, which actually solved my issue.

Sender notified by Mailtrack

01/06/23, 21:27:26