You are not logged in.
I can't figure my way out of this one. Ethernet port appears to be recognized, but does not connect to anything.
[kyle@Lexington ~]$ lspci | grep -i net
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0e)
So it's some sort of realtek chip being recognized.
[kyle@Lexington ~]$ ip link show
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: enp1s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether fe:50:14:7b:d0:19 brd ff:ff:ff:ff:ff:ff permaddr 8a:63:84:fc:a9:99
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 04:7b:cb:c8:0d:04 brd ff:ff:ff:ff:ff:ff
Assuming enp1s0f0 is the ethernet port, it says state is "down".
Tried "sudo ip link set enp1s0f0 up", made no difference. The wiki's suggestion was something about bios settings on 15 year old gigabyte motherboards, nothing to do with a brand new thinkpad.
I have no idea what to do next.
Last edited by kyle_h (2023-12-11 20:46:20)
Offline
Assuming enp1s0f0 is the ethernet port, it says state is "down".
No, it says "NO-CARRIER" what means there's no cable plugged in, the wifi chio is up, though?
How do you seek to connect to the network (wired or wifi, what network managing service do you use)?
In doubt, please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
Well it's an ethernet port that doesn't work, and so I'm trying to connect over ethernet. I bought the T14 specifically because it has one.
I definitely have a cable plugged in, and I know that the cable and the router work because I plugged them into another machine, and they work there.
System boot journal:
Last edited by kyle_h (2023-12-11 21:12:12)
Offline
ethtool enp1s0f0
Dec 11 20:53:26 Lexington kernel: enp1s0f0: 0xffffc90000191000, 74:5d:22:c9:57:b9, IRQ 46
Dec 11 20:53:26 Lexington kernel: r8168 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168ep-3.fw failed with error -2
Dec 11 20:53:26 Lexington kernel: r8168 0000:01:00.0: Unable to load firmware rtl_nic/rtl8168ep-3.fw (-2)
pacman -Qs firmware
Otherwise, do you get better behavior w/ the r8169 driver (remove the r8168 package)?
Offline
kyle@Lexington Desktop]$ ethtool enp1s0f0
Settings for enp1s0f0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
netlink error: Operation not permitted
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: no
[kyle@Lexington Desktop]$ pacman -Qs firmware
local/alsa-firmware 1.2.4-3
Firmware binaries for loader programs in alsa-tools and hotplug firmware
loader
local/b43-fwcutter 019-4
firmware extractor for the b43 kernel module
local/edk2-aarch64 202311-1
Firmware for Virtual Machines (aarch64)
local/edk2-arm 202311-1
Firmware for Virtual Machines (armv7)
local/edk2-ovmf 202311-1
Firmware for Virtual Machines (x86_64, i686)
local/linux-firmware 20231211.f2e52a1c-1
Firmware files for Linux
local/linux-firmware-whence 20231211.f2e52a1c-1
Firmware files for Linux - contains the WHENCE license file which documents
the vendor license details
local/qemu-system-alpha-firmware 8.1.3-1
Firmware for QEMU system emulator for Alpha
local/qemu-system-arm-firmware 8.1.3-1
Firmware for QEMU system emulator for ARM
local/qemu-system-hppa-firmware 8.1.3-1
Firmware for QEMU system emulator for HPPA
local/qemu-system-microblaze-firmware 8.1.3-1
Firmware for QEMU system emulator for Microblaze
local/qemu-system-ppc-firmware 8.1.3-1
Firmware for QEMU system emulator for PPC
local/qemu-system-riscv-firmware 8.1.3-1
Firmware for QEMU system emulator for RISC-V
local/qemu-system-s390x-firmware 8.1.3-1
Firmware for QEMU system emulator for S390
local/qemu-system-sparc-firmware 8.1.3-1
Firmware for QEMU system emulator for SPARC
local/qemu-system-x86-firmware 8.1.3-1
Firmware for QEMU system emulator for x86
local/rtl8821au-dkms-git 5.12.5.2.r221.gcf0f873-1
rtl8821AU and rtl8811AU chipset driver with firmware v5.12.5.2
local/sof-firmware 2023.09.2-1
Sound Open Firmware
removing r8168 does not change how the system behaves at all.
Offline
Boot some live distro (grml, knoppix) and see whether the link is detected there.
Make sure the cable is firmly plugged into the jack and doesn't wiggle (sometimes the latch protection collides w/ the case and prevents a complete enter) - there's supposed to be a notable "snap".
Btw
Dec 11 20:53:21 Lexington systemd[1]: Found device Seagate ZP2000GV30012 endeavouros.
Offline