Fedora 33 Ethernet Doesn't Work

Ask Fedora
, ,
1

Hello,

I’m trying to install Fedora 33 to HP ProDesk 405 G6 R7 4750GE as a second OS.
Installation is completed but the only issue - ethernet doesn’t seem to work.
Was tested with Fedora 33 Workstation, Fedora 33 Cinnamon, Fedora 32 Cinnamon.
No matter fully installed or from live-cd - ethernet doesn’t work.
The box doesn’t have wifi, so only ethernet could be established.

With workstation in Gnome the network configuration UI was not available, in Cinnamon - it is exist, but devices drop-down is empty. I tried DHCP, Static configs.
nmcli status shows only lo network (can’t provide output here, sorry).
nmcli d show no devices.
lspci | grep -i ethernet shows: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (Rev 29)
So the device is detected but works wrongly.

Update:
Looks that is a main problem. Just during I’m writing this topic, someone also report an issue on
linux-hardware.org

2

Can you try a F34 nightly build live media image from Fedora nightly compose finder to see if that works? That will have a newer kernel which may support the newer revision of the device.

3

I’ve update kernel to 5.10.19-200.fc33.x86_64 - no success

Seems like that revision of PCI is not supported by kernel yet:
211461

1 Like
4

Just got my Ethernet to USB adapter - that finally working so that is first message I’m able to post from my new box.
I would highly recommend to anybody who would like to buy recent HP ProDesk / EliteDesk to also have some alternative way to connect to Internet - that would save a lot of time.
In my case: the box doesn’t have anything but Ethernet - and that is fiasco, especially for someone who is not so familiar with Linux and with recent fedora trends.

From my perspective it looked like so: fresh install, no internet, no devices, no listed connections, top 20 of google search says how to check/troubleshoot network with network-scripts - which was just empty in f33 because now NetworkManager is the only and default way to handle network connections - but I’m not aware of that, my old laptop uses f32 but first installation was Korora (oh I really miss it) with all network-scripts in place and just running. So first night I spent trying to make the network up - of course without success. Then it became clear that something wrong with hardware, so next night I spend trying to update driver with realtek native - ups, fedora doesn’t include ‘make’ by OOB and I still didn’t have internet connection, so next kernel - of course it was easier even without internet but also took time (all my previous experience was dnf install something), sad is the fact - kernel upgrade didn’t help.

I hope all this long text will help someone to save time/nerves.

thx.

1 Like
5

You had two more options:

  1. Fedora 32 is still a flew month available
  2. Fedora 34 is soon available (Is in beta)
6

I tried F32. And the kernel still doesn’t support RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (Rev 29)
So looks like real option is waiting

7

It comes with kernel 5.11 https://mirror1.cl.netactuate.com/fedora/development/34/
You may give it a try.

When you talk from other distributions, they generally use other kernel versions. You not really can compare with Fedora.

8

It looks like your chipset version is not compatible with the current driver. I have (rev 15) and you have (rev 29).
I just downloaded the beta version of F34 with the 5.11 kernel from here so you might try that and see if it fixes the problem for you.

9

thanks for suggestion.
There is opened ticket on bugzilla.kernel.org 211461 – r8169: support RTL8111 (rev 29)
the comment there:

“I’ve tried 5.11 vanilla kernel and checked kernel git. So far this revision is not supported.
(I also tried vendor drive r8168-8.048.03. It detects NIC succesfully but no traffic is received. Test in
Windows 10 was OK.)”

That ticket is still open, hope the situation will change with few recent kernel releases.

10

It is one month and more he wrote this … sidlo.pavel 2021-01-29 17:05:02 UTC
The fedora 34 Image was updated yesterday … there where already 3 Kernel updates since 01.29.21

11

Hi, will try it a little later.

+ Based on the comment on bugzilla - the issue is resolved at least in the kernel 5.12-rc2.

Thanks

1 Like
12

So Fedora 34 doesn’t help, it is based on kernel 5.11
F33: dmesg -l err

[Mar 8 20:50] ACPI BIOS Error (bug): Failure creating named object [\_GPE._L00], AE_ALREADY_EXISTS (20200925/dswload2-326)
[  +0.000003] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-220)
[  +0.000357] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.I2CD], AE_NOT_FOUND (20200925/dswload2-162)
[  +0.000002] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20200925/psobject-220)
[  +1.312685] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[  +2.618546] r8169 0000:08:00.1: unknown chip XID 54b
[  +1.063926] sd 6:0:0:0: [sda] No Caching mode page found
[  +0.000001] sd 6:0:0:0: [sda] Assuming drive cache: write through

F34 (20210307): dmesg -l err

[Mar 8 19:57] ACPI BIOS Error (bug): Failure creating named object [\_GPE._L00], AE_ALREADY_EXISTS (20201113/dswload2-326)
[  +0.000005] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20201113/psobject-220)
[  +0.000359] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.I2CD], AE_NOT_FOUND (20201113/dswload2-162)
[  +0.000002] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20201113/psobject-220)
[  +2.936670] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[  +2.525160] r8169 0000:08:00.1: unknown chip XID 54b
[  +1.005412] sd 7:0:0:0: [sda] No Caching mode page found
[  +0.000001] sd 7:0:0:0: [sda] Assuming drive cache: write through
[  +8.637656] amdgpu 0000:0a:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR

So the real way: update kernel to 5.12-rc2 or wait it comes form Fedora update.

1 Like
13

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.