Temp fix for broken network Rock-5B

#1

What is happening is $sudo apt autoremove is removing the drivers that are installed since they do not have a dependency. Temp fix is to place them on hold.

This is assumes the network is still up because apt autoremove was not used. If it broke after running autoremove you will more than likely have better luck getting back up by laying down a fresh image.

   $ sudo apt-mark hold r8125-dkms radxa-system-config-r8125-dkms

fred@rock5b:~$ sudo apt-get autoremove
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
liba52-0.7.4 libdbus-glib-1-2 libdca0 libmodule-scandeps-perl r8125-dkms radxa-system-config-r8125-dkms
0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded.
After this operation, 1,604 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
fred@rock5b:~$ sudo apt-mark hold r8125-dkms radxa-system-config-r8125-dkms
[sudo] password for fred:
r8125-dkms set on hold.
radxa-system-config-r8125-dkms set on hold.
fred@rock5b:~$ sudo apt-get autoremove
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
liba52-0.7.4 libdbus-glib-1-2 libdca0 libmodule-scandeps-perl
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
After this operation, 585 kB disk space will be freed.
Do you want to continue? [Y/n]

#2

Use sudo apt autopurge instead of sudo apt autoremove

1 Like
#3

Thank you for sharing that, either way it should not remove critical drivers from the system.

For some one that flies outside of the developer orbit those package names are meaning less. They would not realize the system is going to break as a result. Its not even remotely recoverable after that happens since the network is totally disabled.

#4

Because we used the kernel-owned r8169 instead of r8125-dkms, r8125-dkms is no longer dependent because it will cause incomplete data when transferring large files. Sorry to bring you a bad experience.

#5

The debian 12 is still running r8125. I did have to create a recipe for our yocto and it is based on r8125. Did not realize that r8169 is the correct one so that will be changed, thank you.

fred@rock5b:~$ lsmod | grep r8125
r8125 163840 0
fred@rock5b:~$ lsmod | grep r8169
fred@rock5b:~$ uname -a
Linux rock5b 6.1.43-20-rk2312 #3e26818dc SMP Tue Nov 19 07:21:24 UTC 2024 aarch64 GNU/Linux
fred@rock5b:~$

#6

Because the radxa-system-config-r8125-dkms configuration file loads r8125 first, you won’t see r8169 run

#7

r8125 is removed and the network breaks so it must still be integral part of the system. Why is chromium browser so deeply attached?