Yes, I have.
[uwe@HAL ~]$ pacman -Qi r8168
Fehler: Paket »r8168« wurde nicht gefunden
install with sudo pacman -S r8168 ?
Yes install the r8168 package and reboot.
1 Like
The WiFi? Does it work or not? You have the following:
Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe
vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 pcie: speed: 2.5 GT/s
lanes: 1 bus-ID: 03:00.0 chip-ID: 1814:3290
This chip is hit or miss and sometimes works and other times not. I see it has the correct module loaded for it. There is one other package in the AUR for this chip but not sure it works.
Edit: Hopefully the Ethernet will work with the r8168 package installed.
nope, I have r8168 installed, reboot, no success.
What does this show now?
inxi -Na
[uwe@HALhp ~]$ inxi -Na
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard ProBook 450/455 driver: N/A modules: r8169 pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe
vendor: Hewlett-Packard driver: N/A modules: rt2800pci pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 1814:3290
class-ID: 0280
Can you uninstall the r8168 and reboot again as it isn’t working on r8168.
What can I say … I do not know what is going on here … After uninstalling the r8168 first nothing has changed, have then also uninstalled the dkms driver from the AUR again _ reboot - connection WLAN positive … It drives me crazy when I do not know what caused it …
Thanks in any case for your help! 
I have to go sleep now 
2 Likes
systemctl
Please pay attention to the orthography!
1 Like
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2022-05-19 12:35:58 CEST; 1min 20s ago
TriggeredBy: ● pipewire.socket
Main PID: 697 (pipewire)
Tasks: 2 (limit: 8550)
Memory: 6.8M
CPU: 97ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─ 697 /usr/bin/pipewire
Mai 19 12:35:58 HALhp systemd[566]: Started PipeWire Multimedia Service.
Mai 19 12:35:58 HALhp pipewire[697]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Mai 19 12:35:58 HALhp pipewire[697]: mod.rt: could not set nice-level to -11: Datei oder Verzeichni>
Mai 19 12:35:58 HALhp pipewire[697]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Mai 19 12:35:58 HALhp pipewire[697]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Mai 19 12:35:58 HALhp pipewire[697]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Mai 19 12:35:58 HALhp pipewire[697]: mod.rt: could not make thread 705 realtime using RTKit: Datei >
lines 1-18/18 (END)
Update:
In the end, the solution:
The originator of the whole thing was simply the incorrectly selected network driver after installation. Welcome offers the r8169 as recommended and the r8168 as alternative. I stupidly chose the r8169, because it runs better on my main computer. Well, that was crap … Switched to the r8168 and the WLAN connected without any problems. No r8168 LTS needed!.
Thanks to all the helpers!
1 Like
Yes this happens because some of these chips run on one or the other and some will run on both such as mine. Sometimes even though they work on both one or the other doesn’t come out of hibernation or sleep properly and reactivate the lan.
2 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.