Well, as the post states I have a Ethernet port showing unknown after a reboot. Been running for a few years fine. Tried rebooting and restarting the network manager but I’m a loss here. Hardware is a nuc11 with an i7 and 2.5 gbe nic

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 noprefixroute

valid_lft forever preferred_lft foreverNZB Geek API: HMiN8DoCH6sEeqj7q7UE0Mtg4ewuXrZ6

Planet API: 842708488f4250ba2e98f460de23daa8

Update: I have found the NIC, it’s showing as “unclaimed”.

    • @EnragedzeusOP
      link
      0
      edit-2
      2 days ago

      F, I think my NIC just died then

      Edit: nic is enabled in bios and ifconfig only shows loop back and wlol.

      • Dave.
        link
        fedilink
        22 days ago

        If you occasionally boot to windows, it’s known to leave NICs in an unusable state if you just hibernate/quick power off. You need to boot back to windows and so a “proper” shutdown for it to come good.

      • @just_another_person
        link
        22 days ago

        Did you possibly update your kernel recently? Perhaps before your reboot?

        Check dmesg output and see if there’s anything useful in there.

        • @EnragedzeusOP
          link
          1
          edit-2
          2 days ago

          Anything I should be grepping for? Nothing stuck out after a few scrolls

          Edit:auto correct

          • @just_another_person
            link
            12 days ago

            Anything about modules failing to load. What distro are you on? I would check and see if you can still boot into the previous kernel version and see if the interface comes back. You should have the previous version available to select in your boot menu.

            • @EnragedzeusOP
              link
              21 day ago

              Ding ding. Booting into old kernel fixed it

              • @just_another_person
                link
                1
                edit-2
                1 day ago

                Okay, so now you need to get the kernel versions, and start looking up the “why”. Is this a problem with the specific kernel build you got upgraded to, or was there a config change that messed something up?

                If you know the current version works, there’s nothing super wrong with staying on it for awhile to avoid the issue, but it’s probably best to identify the cause so you don’t live in fear of future upgrades.

                What are the two version numbers you have now, and which one works?

                • @EnragedzeusOP
                  link
                  113 hours ago

                  I had to leave and won’t be back for a couple days. Tried googling was Fedora 41 is on and I just know it’s 6.11. Once I get back I’ll look at grub and update.

      • @[email protected]
        link
        fedilink
        English
        1
        edit-2
        2 days ago

        You haven’t given any info on your environment, but does it show up in the OS? In lspci or nmtui or whatever? Is it listed in /etc/network/interfaces or your distro’s equivalent?

        • @EnragedzeusOP
          link
          1
          edit-2
          2 days ago

          It does not show up in the network manager (Fedora). Ifconfig also only shows loopback and wifi.

          I did now find it at the bottom of the command so that’s something at least.

          lspci

          00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)

          00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)

          00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01)

          00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #0 (rev 01)

          00:07.3 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #3 (rev 01)

          00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)

          00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)

          00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 01)

          00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #1 (rev 01)

          00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)

          00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)

          00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

          00:15.0 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)

          00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)

          00:17.0 SATA controller: Intel Corporation Tiger Lake-LP SATA Controller (rev 20)

          00:1c.0 PCI bridge: Intel Corporation Tiger Lake-LP PCI Express Root Port #5 (rev 20)

          00:1c.6 PCI bridge: Intel Corporation Tiger Lake-LP PCI Express Root Port #7 (rev 20)

          00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)

          00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)

          00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)

          00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)

          01:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD (rev 01)

          58:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)

          59:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)

          • @[email protected]
            link
            fedilink
            English
            12 days ago

            Try booting from a live disk. If it works there, it’s probably an update or config change that’s causing problems.