You are not logged in.

#1 2022-06-30 21:20:53

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Network stopped working after pipewire installation

Hey,

I was trying to switch from alsamixer to pipewire, but in the process of installing pipewire. I installed pipewire, pipewire-pulse, and pipewire-media-session with:

sudo pacman -S pipewire pipewire-pulse pipewire-media-session

I then ran this command:

sudo systemctl --user enable pipewire pipewire-pulse pipewire-media-session

but when I rebooted the computer, the network was gone. I have tried doing the exact same command but instead of enable I used disable, but nothing is working. I have removed all pipewire packages, but there's still no network.

sudo journalctl -b

The journalctl file is available here:
https://pastebin.com/ePMVJR1f

sudo journalctl -b -u NetworkManager

https://pastebin.com/fqHvyxcg

The output of ip link can be shown here:

$ ip link
1. lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2. enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:33:61:24 brd ff:ff:ff:ff:ff:ff

The output of lspci -k can be shown here:
https://pastebin.com/FS3RnHqN

The output of networkctl can be shown here:
https://pastebin.com/Z2Bdg3jZ

sudo dmesg | grep r8169

https://pastebin.com/LPixNQab

I have tried most of what's available on this forum from people's similar posts, but nothing seems to be working.

Offline

#2 2022-06-30 21:28:09

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,740

Re: Network stopped working after pipewire installation

As a sanity check, verify the version numbers reported by uname -a and by pacman -Q linux are the same.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2022-06-30 21:33:58

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Re: Network stopped working after pipewire installation

uname -a

Linux ilittlebig 5.18.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat 25 Jun 2022 20:22:01 +0000 x86_64/GNU/Linux

pacman -Q linux

linux 5.18.7.arch1-1

Last edited by ilittlebig (2022-06-30 21:38:56)

Offline

#4 2022-06-30 21:44:46

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,740

Re: Network stopped working after pipewire installation

Looks good.  What is the output of lspci -k   ?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2022-06-30 21:47:37

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Re: Network stopped working after pipewire installation

This is the output of lspci -k
https://pastebin.com/FS3RnHqN

Offline

#6 2022-06-30 21:52:30

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,740

Re: Network stopped working after pipewire installation

All I see is the wired network.  Is that the one that is not working -- because it look health?  Or are we looking for a different network (WiFi, for example)?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#7 2022-06-30 21:55:59

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Re: Network stopped working after pipewire installation

We are looking at the only wired connection, and yes, that's the weird part. Everything looks like it should be working but it's not.

Offline

#8 2022-06-30 22:01:38

seth
Member
Registered: 2012-09-03
Posts: 50,008

Re: Network stopped working after pipewire installation

You've networkmanager & dhcpcd enabled and they play the stooges vs. the door.
Pick one, disable the other.

Online

#9 2022-06-30 22:08:37

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Re: Network stopped working after pipewire installation

I disabled dhcpcd with:

sudo systemctl disable dhcpcd
sudo systemctl disable dhcpcd@enp6s0

but there's still no internet.

Though when I ping 1.1.1.1 it gives me this output:

PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
From 192.168.0.1 icmp_seq=2 Redirect Host(New nexthop: 1.1.1.1)
From 192.168.0.1 icmp_seq=3 Redirect Host(New nexthop: 1.1.1.1)
From 192.168.0.1 icmp_seq=1 Destination Host Unreachable 
From 192.168.0.1 icmp_seq=2 Destination Host Unreachable 
From 192.168.0.1 icmp_seq=3 Destination Host Unreachable 
From 192.168.0.1 icmp_seq=4 Redirect Host(New nexthop: 1.1.1.1)
From 192.168.0.1 icmp_seq=5 Redirect Host(New nexthop: 1.1.1.1)

And when I ping google.com it gives me this output:

ping: google.com: No adress associated with hostname

Offline

#10 2022-06-30 22:12:14

seth
Member
Registered: 2012-09-03
Posts: 50,008

Re: Network stopped working after pipewire installation

"disable --now" or also "stop" and you might need to restart NM in order to settle things down.
Or reboot.

Also

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Online

#11 2022-06-30 22:34:44

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Re: Network stopped working after pipewire installation

I had no luck getting the internet working with disabling dhcpcd with --now, but that long command gave me this output:

dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-network-generator.service        | sysinit.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-timesyncd.service                | sysinit.target.wants
xdg-user-dirs-update.service             | default.target.wants

Offline

#12 2022-06-30 23:07:31

seth
Member
Registered: 2012-09-03
Posts: 50,008

Re: Network stopped working after pipewire installation

It was the *three* stooges after all.
Disable systemd-network.d, same problem

If it still doesn't work, post an updated journal.

Online

#13 2022-06-30 23:27:08

ilittlebig
Member
Registered: 2022-06-30
Posts: 7

Re: Network stopped working after pipewire installation

I disabled it with --now, but it's still not working, here's the new journalctl output though:
https://pastebin.com/APLADvAH

Offline

#14 2022-07-01 07:10:28

seth
Member
Registered: 2012-09-03
Posts: 50,008

Re: Network stopped working after pipewire installation

Why did you switch from

Jun 30 21:55:12 ilittlebig NetworkManager[573]: <info>  [1656618912.3893] dhcp-init: Using DHCP client 'internal'

to

Jul 01 01:23:50 ilittlebig NetworkManager[527]: <info>  [1656631430.3213] dhcp4 (enp6s0): dhclient started with pid 573

??

Either way, you get a lease

Jul 01 01:23:50 ilittlebig NetworkManager[527]: <info>  [1656631430.3213] dhcp4 (enp6s0): dhclient started with pid 573
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPREQUEST for 192.168.0.100 on enp6s0 to 255.255.255.255 port 67
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPNAK from 192.168.1.254
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPDISCOVER on enp6s0 to 255.255.255.255 port 67 interval 8
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPOFFER of 192.168.0.100 from 192.168.0.1
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPREQUEST for 192.168.0.100 on enp6s0 to 255.255.255.255 port 67
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPNAK from 192.168.1.254
Jul 01 01:23:50 ilittlebig dhclient[573]: DHCPACK of 192.168.0.100 from 192.168.0.1

But you're restricted to

Jul 01 01:23:50 ilittlebig NetworkManager[527]: <info>  [1656631430.3790] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 01 01:23:50 ilittlebig NetworkManager[527]: <info>  [1656631430.3792] manager: NetworkManager state is now CONNECTED_SITE

Output of

ip a
ip r
cat /etc/resolv.conf
ping -c1 _gateway
ping -c1 192.168.0.1
ping -c1 8.8.8.8
ping -c1 google.com

Online

Board footer

Powered by FluxBB