Problem with WLAN on HP ProBook 455 G1 after new Installation

I installed the driver from the AUR, reboot - no change!

Alright, sorry to hear that.
I have no more ideas.
Hopefully someone will chime in to take it from there. Good luck!

1 Like

Drop the sudo from the commands I gave, maybe it works then.
(If that is, what pebcack means.)
Still, I think you should check your sdb-drive for bad sectors and potential issues.

As for the pipewire problem: that’s a minor matter for now, because I have sound (from wherever …). I’m just surprised that such things can happen after a NEW INSTALLATION. Such elementary things should have come along first. With my computer I never had such grout. Same system.

Then all is good in pipewire-land!

check with:

pactl info

you should see something like the following line among others:

Server Name: PulseAudio (on PipeWire 0.3.51)


systemctl --user status pipewire

1 Like

Not on the laptop, on my desktop computer.

systemctl start pipewire.service
systemctl enable pipewire.service

This makes no difference, because then it asks for the password, so sudo after all.

Oh, sorry, that’s what you meant … No, I just said that it worked fine in live mode, except for the wifi. But there I still had hope that it is fixed after installation.

[uwe@HALhp ~]$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 116
Tile Size: 65472
User Name: uwe
Host Name: HALhp
Server Name: PulseAudio (on PipeWire 0.3.51)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_14.2.analog-stereo
Default Source: alsa_input.pci-0000_00_14.2.analog-stereo
Cookie: 03ac:91ef
[uwe@HALhp ~]$ 

Das sieht ok aus.

1 Like
[uwe@HALhp ~]$ sytemctl --user status pipewire
bash: sytemctl: Kommando nicht gefunden.

For the missing WLAN: Is it possible that FirewallD is blocking something?

Nope. Must be a driver-issue, as someone up-thread pointed out. :wink:

1 Like

Again, if I were you, I’d start all over with installing Arch-Linux, like already said before.

I will probably have no choice …

Im no expert by any means just trying to help…
Do you have the r8168(or r8168-lts if youre using lts kernel) package installed? By checking specs your laptop has a realtek card so might give it a shot…
Edit: I think i misread ralink for realtek sorry ive never heard of ralink…

No, because on my main computer I also use the LTS kernel and did not install that separately. I will switch to the current kernel and see if there is a difference.

I chose the suggested r8169 after installation.

no change

After some digging ive found this:
Seems like you need to blacklist some other driver and keep rt3290. If you have the drivers installed like they have. But someone else might wanna chime in. Also the thread is old so i dont know if it still applies or not…

1 Like

By the way: I booted an ISO of Manjaro Xfce (don’t hit me, please!) and the WLAN connected without problems. So what is broken here?

Could an offline installation bring the missing driver?

When you installed did you select the r8169 at the beginning of the install? It asks if you want to use the default r8169 or use r8168.

Edit: Check if r8168 is installed

pacman -Qi r8168