You are not logged in.

Pages: 1

#1 2025-02-22 19:09:10

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

[SOLVED] Network stopped working after reboot

Every time when I turn on the PC, I like running "pacman -Syu" and then doing a reboot just for the sake of it, specially after a kernel update, since the whole process takes no more than a minute anyway. So a few days ago I did exactly that, but after the reboot, I had no internet connection anymore, and ping was returning the message "Temporary failure in name resolution". I can still chroot from another distro and run any command in there just fine.

I looked inside pacman.log, and the log from that update is as follows:

[2025-02-19T18:54:53-0300] [PACMAN] Running 'pacman -Syu'
[2025-02-19T18:54:53-0300] [PACMAN] synchronizing package lists
[2025-02-19T18:54:53-0300] [PACMAN] starting full system upgrade
[2025-02-19T18:55:07-0300] [ALPM] running '60-mkinitcpio-remove.hook'...
[2025-02-19T18:55:07-0300] [ALPM] transaction started
[2025-02-19T18:55:07-0300] [ALPM] upgraded libpng (1.6.46-1 -> 1.6.47-1)
[2025-02-19T18:55:08-0300] [ALPM] upgraded linux (6.13.2.arch1-1 -> 6.13.3.arch1-1)
[2025-02-19T18:55:08-0300] [ALPM] upgraded openmpi (5.0.6-2 -> 5.0.7-1)
[2025-02-19T18:55:08-0300] [ALPM] upgraded spectacle (1:6.3.1-1 -> 1:6.3.1.2-1)
[2025-02-19T18:55:08-0300] [ALPM] transaction completed
[2025-02-19T18:55:08-0300] [ALPM] running '30-systemd-daemon-reload-user.hook'...
[2025-02-19T18:55:08-0300] [ALPM] running '30-systemd-update.hook'...
[2025-02-19T18:55:08-0300] [ALPM] running '60-depmod.hook'...
[2025-02-19T18:55:09-0300] [ALPM] running '90-mkinitcpio-install.hook'...
[2025-02-19T18:55:09-0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2025-02-19T18:55:09-0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2025-02-19T18:55:09-0300] [ALPM-SCRIPTLET] ==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
[2025-02-19T18:55:09-0300] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET] ==> Starting build: '6.13.3-arch1-1'
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-02-19T18:55:10-0300] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-02-19T18:55:12-0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET] ==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET] ==> Starting build: '6.13.3-arch1-1'
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-02-19T18:55:13-0300] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2025-02-19T18:55:17-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
[2025-02-19T18:55:17-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-02-19T18:55:17-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
[2025-02-19T18:55:18-0300] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2025-02-19T18:55:18-0300] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2025-02-19T18:55:18-0300] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2025-02-19T18:55:18-0300] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-02-19T18:55:18-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2025-02-19T18:55:18-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2025-02-19T18:55:19-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2025-02-19T18:55:19-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2025-02-19T18:55:19-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
[2025-02-19T18:55:19-0300] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
[2025-02-19T18:55:20-0300] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-02-19T18:55:20-0300] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-02-19T18:55:22-0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-02-19T18:55:22-0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2025-02-19T18:55:23-0300] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-02-19T18:55:23-0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2025-02-19T18:55:23-0300] [ALPM] running 'gtk-update-icon-cache.hook'...
[2025-02-19T18:55:23-0300] [ALPM] running 'update-desktop-database.hook'...

I also looked at my resolv.conf file, and the content is:

# Generated by NetworkManager
nameserver [my ip address]
nameserver 8.8.8.8

Which is the exact same content of the file in my other distro.

Anyone know what is going on?

Last edited by Metallinatus (2025-02-23 23:56:24)

Offline

#2 2025-02-22 21:14:46

-thc
Member
Registered: 2017-03-15
Posts: 998

Re: [SOLVED] Network stopped working after reboot

Metallinatus wrote:

I also looked at my resolv.conf file, and the content is:

# Generated by NetworkManager
nameserver [my ip address]
nameserver 8.8.8.8

Which is the exact same content of the file in my other distro.

Why is your Arch box' IP address the first "nameserver"? Does your Arch box run a local DNS server?

Offline

#3 2025-02-22 21:34:59

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

127.0.0.1 would be for resolved… there's generally no need to obfuscate IPv4 from the private range, they're meaningless outside your LAN.
Also some pacman log won't help here…

ip a
ip r
resolvectl status
ping -c1 _gateway
ping -c1 8.8.8.8
ping -c1 google.com

and in doubt please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#4 2025-02-23 00:54:45

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

ip a:

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 forever

ip r didn't return me anything;

resolvectl status:

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
  Current DNS Server: 1.1.1.1#cloudflare-dns.com
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
                      2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net
                      2001:4860:4860::8888#dns.google

ping -c1 _gateway:

ping: _gateway: Name or service not known

I think the underscore was a typo, so I did it again without it and I got the temporary failure message.

ping -c1 8.8.8.8:

ping: connect: Network is unreachable

ping -c1 google.com

ping: google.com: Temporary failure in name resolution

sudo journalctl -b | curl -F 'file=@-' 0x0.st
this one returned to me:

curl: (6) Could not resolve host: 0x0.st
seth wrote:

127.0.0.1 would be for resolved… there's generally no need to obfuscate IPv4 from the private range, they're meaningless outside your LAN.
Also some pacman log won't help here…

Ok, that's good to know. And yeah, I figured the pacman log wouldn't help much, but just in case, since the update was the last thing I did before the network stopped working.

-thc wrote:

Why is your Arch box' IP address the first "nameserver"? Does your Arch box run a local DNS server?

I don't know, it's the same in my Linux Mint generated resolv.conf.

Offline

#5 2025-02-23 08:57:48

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

So you've no network device at all.

uname -a
pacman -Qs 'kernel|firmware'
lspci -k
this one returned to me:

Because there's no network conneciton.

sudo journalctl -b > /tmp/journal.txt

and then usb-walk that file to a system with internet connection to upload it.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#6 2025-02-23 15:01:10

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

uname -a

Linux archlinux 6.13.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:55 +0000 x86_64 GNU/Linux

pacman -Qs 'kernel|firmware'

local/embree 4.3.3-1
    Collection of high-performance ray tracing kernels
local/fuse3 3.16.2-1
    Interface for userspace programs to export a filesystem to the Linux kernel
local/iptables 1:1.8.10-2
    Linux kernel packet control tool (using legacy interface)
local/kmod 33-3
    Linux kernel module management tools and library
local/lib32-libdrm 2.4.124-1
    Userspace interface to kernel DRM services (32-bit)
local/libdrm 2.4.124-1
    Userspace interface to kernel DRM services
local/libnetfilter_conntrack 1.0.9-2
    Library providing an API to the in-kernel connection tracking state table
local/libnfnetlink 1.0.2-2
    Low-level library for netfilter related kernel/userspace communication
local/libsysprof-capture 47.2-3
    Kernel based performance profiler - capture library
local/linux 6.13.3.arch1-1
    The Linux kernel and modules
local/linux-api-headers 6.13-1
    Kernel headers sanitized for use in userspace
local/linux-firmware 20250210.5bc5868b-1
    Firmware files for Linux
local/linux-firmware-whence 20250210.5bc5868b-1
    Firmware files for Linux - contains the WHENCE license file which documents the vendor license
    details
local/mtdev 1.1.7-1
    A stand-alone library which transforms all variants of kernel MT events to the slotted type B
    protocol

lspci -k

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
        Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
lspci: Unable to load libkmod resources: error -2
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
        Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
        Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
        Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
        Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
        Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
        Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
        Subsystem: ASRock Incorporation Device ffff
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
        Subsystem: ASRock Incorporation Device ffff
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c0)
        Kernel driver in use: pcieport
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
        Kernel driver in use: pcieport
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (rev c0)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3985
        Kernel driver in use: amdgpu
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
04:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller
        Subsystem: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
        Kernel driver in use: xhci_hcd
04:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller
        Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller
        Kernel driver in use: ahci
04:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port
        Subsystem: ASMedia Technology Inc. Device 0201
        Kernel driver in use: pcieport
05:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
        Subsystem: ASMedia Technology Inc. Device 3308
        Kernel driver in use: pcieport
05:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
        Subsystem: ASMedia Technology Inc. Device 3308
        Kernel driver in use: pcieport
06:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. NV3 NVMe SSD [E27T] (DRAM-less) (rev 01)
        Subsystem: Kingston Technology Company, Inc. NV3 NVMe SSD [E27T] (DRAM-less)
        Kernel driver in use: nvme
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: ASRock Incorporation Motherboard (one of many)
08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function (rev c8)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 1636
08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
08:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
        Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
08:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
        Subsystem: ASRock Incorporation Device ffff
        Kernel driver in use: xhci_hcd
08:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
        Subsystem: ASRock Incorporation Device ffff
        Kernel driver in use: xhci_hcd
08:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller
        Subsystem: ASRock Incorporation Device 1204
seth wrote:
sudo journalctl -b > /tmp/journal.txt

and then usb-walk that file to a system with internet connection to upload it.

I am just moving files between drives, and using the internet through another distro in the same PC. And I didn't realize I was trying to upload the file, but I learned about it on the handful link in your signature now, thanks.
Here it is: http://0x0.st/8TJv.txt

Offline

#7 2025-02-23 15:11:42

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

local/linux 6.13.3.arch1-1
…
Linux archlinux 6.13.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:55 +0000 x86_64 GNU/Linux

You're booting an old kernel.

BOOT_IMAGE=/boot/vmlinuz-linux

from the root partition.

Chances are you mounted something else into /boot before the udpate - fix that.

mount | grep boot

make sure nothing's mounted there, re-install the kernel, pay attention to any kind of errors (the kernel image is copied into /boot by mkinitcpio), reboot and see whether you're now booting the 6.13.3 kernel.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#8 2025-02-23 15:26:34

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

seth wrote:

local/linux 6.13.3.arch1-1
…
Linux archlinux 6.13.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:55 +0000 x86_64 GNU/Linux

You're booting an old kernel.

BOOT_IMAGE=/boot/vmlinuz-linux

from the root partition.

Chances are you mounted something else into /boot before the udpate - fix that.

I updated first thing when turning on the PC, there was nothing mounted. Although I ran an update through chroot once after the internet stopped working, don't know if that has anything to do with this.

seth wrote:
mount | grep boot

make sure nothing's mounted there, re-install the kernel, pay attention to any kind of errors (the kernel image is copied into /boot by mkinitcpio), reboot and see whether you're now booting the 6.13.3 kernel.

Not sure how to reinstall the kernel, do I just run 'pacman -S linux' through chroot?

Offline

#9 2025-02-23 16:03:26

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

do I just run 'pacman -S linux' through chroot?

For instance, yes.
Pay attention to any errors and check the mounted paths before.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#10 2025-02-23 17:08:55

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

seth wrote:

do I just run 'pacman -S linux' through chroot?

For instance, yes.
Pay attention to any errors and check the mounted paths before.

Ok, I did that, updated without anything mounted, then rebooted back into the system, but uname -a returned me the same as before, still on 6.13.2.
I didn't get any error on the update, only warnings.
If you want to take a look:

[root@Mint /]# pacman -S linux
warning: linux-6.13.3.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-6.13.3.arch1-1

Total Installed Size:  138,42 MiB
Net Upgrade Size:        0,00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) reinstalling linux                           [######################] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.13.3-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.13.3-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

Last edited by Metallinatus (2025-02-23 17:09:24)

Offline

#11 2025-02-23 17:13:43

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.13.3-arch1-1'

It's building for the 6.13.3 kernel…

file /boot/vmlinuz-linux

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#12 2025-02-23 17:23:37

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

seth wrote:
file /boot/vmlinuz-linux

/boot/vmlinuz-linux: Linux kernel x86 boot executable, bzImage, version 6.13.3-arch1-1 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC Mon, 17 Feb 2025 17:42:11 +0000, RO-rootFS, Normal VGA, setup size 512*39, syssize 0xd3620, jump 0x26c 0x8cd88ec0fc8cd239 instruction, protocol 2.15, from protected-mode code at offset 0x2cc 0xcfea99 bytes ZST compressed, relocatable, handover offset 0xd23030, legacy 64-bit entry point, can be above 4G, 32-bit EFI handoff entry point, 64-bit EFI handoff entry point, EFI kexec boot support, xloadflags bit 5, max cmdline size 2047, init_size 0x3e45000

Offline

#13 2025-02-23 17:30:08

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

That's the most recent kernel…

findmnt -T /boot/vmlinuz-linux

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#14 2025-02-23 17:59:21

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

seth wrote:

That's the most recent kernel…

findmnt -T /boot/vmlinuz-linux
TARGET SOURCE       FSTYPE OPTIONS
/      /dev/nvme0n1 ext4   rw,relatime

Ok, I don't know if it's worthy mentioning, but I copied this installation from another drive using clonezilla some 2 weeks ago, but everything worked fine until last Thursday so I don't know.

Offline

#15 2025-02-23 21:21:20

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,175

Re: [SOLVED] Network stopped working after reboot

Is the other drive still attached to that system?
It's likely referenced in the bootloader config and you're loading the kernel from there but then boot the new disk as root device?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#16 2025-02-23 23:54:01

Metallinatus
Member
Registered: 2022-01-26
Posts: 11

Re: [SOLVED] Network stopped working after reboot

seth wrote:

Is the other drive still attached to that system?
It's likely referenced in the bootloader config and you're loading the kernel from there but then boot the new disk as root device?

Ok so, long story short, yes.
The old SSD was still connected, so I unplugged it, and then I couldn't even boot into the system using its own bootloader anymore, but could still boot it through the Mint bootloader for some reason, and the network was working! I tried booting through Mint's bootloader before with the old SSD still plugged in and the network still didn't work, so yeah.
So I tried creating another bootloader for Arch, then I found out that system didn't have a EFI partition, so I tried to create one, but I couldn't create a backup because fdisk didn't find a filesystem on the drive (ok, just what happened during that disk cloning?), so I went ahead anyway because I decided I would just clone the old SSD again if something happened. Something happened, so I cloned the SSD again, unplugged the SSD again and turned the PC back on and the cloned system booted completely fine and with internet connection, and that's how I'm using it right now.
So I don't know what happened the first time I cloned the system, but that was the root of the problem.
Thanks for all the help! I will mark the issue as solved now.

Offline

Pages: 1

Board footer

Powered by FluxBB