Hi, new here, it wasn't clear to me if this should be in the "Installation and configuration" section as this is happening part way through an installation procedure or if it should be in the networking section - hoping I guessed right?
I am following the Debian text-based installation method because the "bare metal" installer doesn't work on the computer I am trying to install to (it seems to fail to start X then gives up and asks me to reboot).
I got Debian installed, network working just fine, and followed the instruction to apt install pve-kernel-5.15 then reboot.
After the reboot, it would not start - it was trying to access the ramdisk and seemed to get stuck.
I rebooted and chose the older kernel from the boot menu, which worked, and I found a comment on there being a 5.19 kernel that might solve some hardware-related issues with newer systems, so I installed that, rebooted, and it let me log in.
However, once I was in, the network was down.
The same configuration is still working perfectly in the Debian 5.10 kernel if I reboot into that, but it shows the link as down under the 5.19-pve kernel.
This is the output of ethtool enp1s0 under the (working) 5.10 kernel:
Under the (broken) 5.19-pve kernel:
Here is ethtool -i under the (working) 5.10 kernel:
And under the (broken) 5.19-pve kernel:
ip a under the working 5.10:
ip a under the broken 5.19-pve:
ip ro under the working 5.10:
ip ro under the broken 5.19-pve:
lspci | fgrep Ethernet (same output for both):
content of /etc/network/interfaces (with one field redacted):
Any ideas?
I am following the Debian text-based installation method because the "bare metal" installer doesn't work on the computer I am trying to install to (it seems to fail to start X then gives up and asks me to reboot).
I got Debian installed, network working just fine, and followed the instruction to apt install pve-kernel-5.15 then reboot.
After the reboot, it would not start - it was trying to access the ramdisk and seemed to get stuck.
I rebooted and chose the older kernel from the boot menu, which worked, and I found a comment on there being a 5.19 kernel that might solve some hardware-related issues with newer systems, so I installed that, rebooted, and it let me log in.
However, once I was in, the network was down.
The same configuration is still working perfectly in the Debian 5.10 kernel if I reboot into that, but it shows the link as down under the 5.19-pve kernel.
This is the output of ethtool enp1s0 under the (working) 5.10 kernel:
Code:
Settings for enp1s0:
Supported ports: [ TP MII ]
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: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
master-slave cfg: preferred slave
master-slave status: slave
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: d
Link detected: yesUnder the (broken) 5.19-pve kernel:
Code:
Settings for enp1s0:
Supported ports: [ TP MII ]
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: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Auto-negotiation: on
master-slave cfg: forced master
master-slave status: resolution error
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: d
Link detected: noHere is ethtool -i under the (working) 5.10 kernel:
Code:
driver: r8169
version: 5.10.0-21-amd64
firmware-version: rtl8168h-2_0.0.2 02/26/15
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
root@pve1:~# cat ethtool_i_enp1s0
driver: r8169
version: 5.19.17-2-pve
firmware-version: rtl8168h-2_0.0.2 02/26/15
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: noAnd under the (broken) 5.19-pve kernel:
Code:
driver: r8169
version: 5.19.17-2-pve
firmware-version: rtl8168h-2_0.0.2 02/26/15
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
root@pve1:~# cat ethtool_i_enp1s0
driver: r8169
version: 5.19.17-2-pve
firmware-version: rtl8168h-2_0.0.2 02/26/15
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: noip a under the working 5.10:
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 68:1d:ef:30:b8:65 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.111/24 brd 192.168.1.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::6a1d:efff:fe30:b865/64 scope link
valid_lft forever preferred_lft foreverip a under the broken 5.19-pve:
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 68:1d:ef:30:b8:65 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.111/24 brd 192.168.1.255 scope global enp1s0
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether e0:75:26:82:9e:70 brd ff:ff:ff:ff:ff:ffip ro under the working 5.10:
Code:
default via 192.168.1.1 dev enp1s0 onlink
192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.111ip ro under the broken 5.19-pve:
Code:
default via 192.168.1.1 dev enp1s0 onlink linkdown
192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.111 linkdownlspci | fgrep Ethernet (same output for both):
Code:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)content of /etc/network/interfaces (with one field redacted):
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug enp1s0
iface enp1s0 inet static
address 192.168.1.111
netmask 255.255.255.0
gateway 192.168.1.1
dns-domain **redacted**
dns-nameservers 192.168.1.1Any ideas?