Trouble connecting to the network via cable

sintev · 2024-05-22 08:00:08

I'm having trouble connecting to the network via cable. I have two SSDs on which there is a different system. On one is Arch, on the other windows. It connects to the second one without a problem, so it's not up to the network. What should I do?

The journalctl -b
https://pastebin.com/jJFtWGRv

Last edited by sintev (2024-05-22 08:12:44)

impossibleveins23 · 2024-05-22 09:27:32

Logs show you are correctly getting IPv4 and IPv6 on: benp0s20f0u2u2 interface.

* Do you have default route (ip route and ip -6 route)?
* What's happen when you ping 1.1.1.1?
* If no ping (and you have default route) perhaps firewall issue?
*If you do have ping, perhaps DNS issue. What's the output of resolvectl?

seth · 2024-05-22 15:20:28

That's their phone. No other NIC seems to show up

I have two SSDs on which there is a different system. On one is Arch, on the other windows

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

If the problem remain, post the output of "lspci -k; lsusb"

svi 22 09:04:07 Spot-Big kernel: pci 0000:04:00.0: [10ec:8168] type 00 class 0x020000 PCIe Endpoint
svi 22 09:04:07 Spot-Big kernel: pci 0000:04:00.0: BAR 0 [io  0x4000-0x40ff]
svi 22 09:04:07 Spot-Big kernel: pci 0000:04:00.0: BAR 2 [mem 0x81204000-0x81204fff 64bit]
svi 22 09:04:07 Spot-Big kernel: pci 0000:04:00.0: BAR 4 [mem 0x81200000-0x81203fff 64bit]
svi 22 09:04:07 Spot-Big kernel: pci 0000:04:00.0: supports D1 D2
svi 22 09:04:07 Spot-Big kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold

looks like the ethernet chip but isn't picked up.
In doubt try the LTS kernel along https://archlinux.org/packages/extra/x86_64/r8168-lts/

Edit:

pacman -Qs 8168

in case you've that installed it blacklists the 8169 module and apparently the 8168 module isn't compatible w/ 6.9?

Last edited by seth (2024-05-22 15:21:32)

sintev · 2024-05-23 07:31:23

impossibleveins23 wrote:

* Do you have default route (ip route and ip -6 route)?

I didn't configure it, it's default.

* What's happen when you ping 1.1.1.1?

Nothing, i don't have ping

* If no ping (and you have default route) perhaps firewall issue?

I don't have firewall

*If you do have ping, perhaps DNS issue. What's the output of resolvectl?

I can't get output.
Failed to get global data: Could not activate remote peer 'org.freedesktop.resolve1': activation request failed: unknown unit

impossibleveins23 · 2024-05-23 07:42:06

As Seth pointed out, you are missing the 8168 Ethernet module.
* What happen when you boot with LTS kernel?

sintev · 2024-05-23 19:33:30

I don't have that much knowledge, I'm a newbie.

seth wrote:

I have two SSDs on which there is a different system. On one is Arch, on the other windows
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

If you'd be so kind as to tell me what to do

Thank you in advance

seth · 2024-05-23 20:11:40

You click the 3rd link in my signature and follow the intructions in the wiki.

Next to that, what about the r8168 situation?

sintev · 2024-05-24 04:53:00

pacman -Qs 8168
local/r8168 8.053.00-5
A kernel module for Realtek 8168 network cards
local/r8168-lts 8.053.00-7
A kernel module for Realtek 8168 network cards for linux-lts

I think I installed it.

I was disable windows hibernation and fast startup, but nothing happend.

Last edited by sintev (2024-05-24 05:10:29)

seth · 2024-05-24 06:02:06

Remove those, https://aur.archlinux.org/packages/r8168 has been dropped into the AUR so right now you've no version for your current kernel, but they blacklist the r8169 driver in /usr/lib/modprobe.d/

If the r8169 driver doesn't work for you, you'll have to build the r8168 package from the AUR or use the LTS kernel since the package for that still exists - for now.

sintev · 2024-05-29 04:22:58

I added a new driver 8168, and 8169 removed. There was also a problem with the static address, for some voodoo reason .
Thanks for your help

seth wrote:

Remove those, https://aur.archlinux.org/packages/r8168 has been dropped into the AUR so right now you've no version for your current kernel, but they blacklist the r8169 driver in /usr/lib/modprobe.d/
If the r8169 driver doesn't work for you, you'll have to build the r8168 package from the AUR or use the LTS kernel since the package for that still exists - for now.

Last edited by sintev (2024-05-29 04:23:28)

seth · 2024-05-29 06:23:18

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2024-05-22 08:00:08

Trouble connecting to the network via cable

#2 2024-05-22 09:27:32

Re: Trouble connecting to the network via cable

#3 2024-05-22 15:20:28

Re: Trouble connecting to the network via cable

#4 2024-05-23 07:31:23

Re: Trouble connecting to the network via cable

#5 2024-05-23 07:42:06

Re: Trouble connecting to the network via cable

#6 2024-05-23 19:33:30

Re: Trouble connecting to the network via cable

#7 2024-05-23 20:11:40

Re: Trouble connecting to the network via cable

#8 2024-05-24 04:53:00

Re: Trouble connecting to the network via cable

#9 2024-05-24 06:02:06

Re: Trouble connecting to the network via cable

#10 2024-05-29 04:22:58

Re: Trouble connecting to the network via cable

#11 2024-05-29 06:23:18

Re: Trouble connecting to the network via cable

Board footer