Realtek ethernet driver issue, network unclaimed, ubuntu 18.04
10,508
You don't need r8168-dkms
with new kernels.
Remove it by sudo apt purge r8168-dkms
and the adapter will be managed by the kernel in-tree module.
Related videos on Youtube
Author by
lnx4m3
Updated on September 18, 2022Comments
-
lnx4m3 over 1 year
i'm getting error network UNCLAIMED, and i see through the forums that it states the drivers. well, my kernel is 5.3.0-20-generic, and it states when i try to install the drivers, its the latest...and its not working. do i need to downgrade to the prior version of the drivers or wait till the create it for this kernel? funny thing is my wireless interface is working...any help in the right directions, thanks.
$ sudo lshw -C network *-network UNCLAIMED description: Ethernet controller product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.1 bus info: pci@0000:01:00.1 version: 12 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list configuration: latency=0 resources: ioport:e000(size=256) memory:df214000-df214fff memory:df210000-df213fff
$ sudo apt-get install r8168-dkms Reading package lists... Done Building dependency tree Reading state information... Done r8168-dkms is already the newest version (8.046.00-1). 0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
-
lnx4m3 over 4 yearsi was able to fix issue, by installing updated or latest realtek drivers:)
-
Eliah Kagan over 4 yearsWould you be willing to post an answer explaining how you did that? I believe that may help others who find this by searching.
-
ComputerScientist over 3 yearsHow do you install it if you do not have internet access?
-
lnx4m3 over 2 years@Eliah Kagan sorry for the late post, resolution below.
-
lnx4m3 over 2 years@ComputerScientist be resourceful :)
-
-
ComputerScientist over 3 yearsHi @qualia, after you do this how do you actually get the error (UNCLAIMED) to go away? Is there anything else? I followed your instructions and rebooting did not seem to fix.