EndeavourOS gets stuck at system boot after using yay

Hello all friends.

(I’m really sorry to open so many threads, but I’m new to Linux/EOS, and when I manage to fix one thing, another thing breaks, so I have no choice but to open threads, sorry!)

I’ve been using EOS for a week and everything was working fine, but I wanted to install Steam and other programs, so I used these commands today:

yay -S nvidia-utils
yay -S lib32-nvidia-utils
yay -S steam
yay -S blender
yay -S gimp

Everything installed correctly, so I decided to reboot EOS (I always do after installing something).

So, when rebooting, EOS starts showing all those texts with the word [OK], as usual, all with the word [OK] in green color, but it stops at one of them, and doesn’t start EOS.

After waiting several minutes, I pressed the shutdown button, many texts came out again, and the pc shut down.

I didn’t shut it down by force, EOS shut down correctly because it put “shutdown” I think.

I started EOS again, and I can’t get to the login screen, it’s still stuck on the black screen with white letters and green [OK] letters.

I don’t know much about Linux or EOS, but I think maybe the yay command updated something incompatible with my pc or something, I don’t think it was caused by the installation of those 3 programs, but I don’t know, anything is possible.

The only strange thing I saw is that a message about the HD audio driver came out when installing Steam, but I don’t think that’s important, since I stopped having audio, but after a while it came back.

(I’m on Windows because of dual boot)

Thanks in advance for your time and effort.

If you could arch-chroot in from a live iso and share the info from this journalctl -b -0 | grep fail | eos-sendlog command that would help.

Out of curiosity, it would also be nice to see the output of grep -i upgraded /var/log/pacman.log


Thanks friend, I’m going to read that guide and try to get the error log with the flash memory where I have EOS with Ventoy.

Do you think it is possible that this error was caused because I installed EOS in root “/” without making more partitions, on an SSD where there were already 3 Windows 10 partitions, in MBR? Maybe it exceeded more than 4 partitions or something.

I thought this might give me trouble.

I’m not sure. You said it was working fine for a week though, right?

1 Like

Yes, all ok until I did yay and installed all of that today.

You’re right, it must be because of something I did today.

Could be a kernel thing, or something to do with your gpu drivers. Won’t have too much of an idea until we get more info.


Hi again friend.

I saw several tutorials on youtube, I don’t know if I did it correctly, but I used those commands, I’m sure EOS is on sda4, I don’t know why the first command didn’t work the first time.

I think the EOS is already mounted, I put your first command, but it didn’t work. I put the second command and this result appeared.

[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sda4 /mnt/boot
mount: /mnt/boot: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sda4 /mnt
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sda4 /mnt/boot
[liveuser@eos-2023.05.28 ~]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# journalctl -b -0 | grep fail | eos-sendlog
==> eos-sendlog: warning: nothing to send.
[root@EndeavourOS /]# grep -i upgraded /var/log/pacman.log
[2023-07-12T16:17:18+0200] [ALPM] upgraded alsa-card-profiles (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:18+0200] [ALPM] upgraded systemd-libs (253.5-2 -> 253.6-2)
[2023-07-12T16:17:18+0200] [ALPM] upgraded systemd (253.5-2 -> 253.6-2)
[2023-07-12T16:17:19+0200] [ALPM] upgraded dracut (059-1 -> 059-2)
[2023-07-12T16:17:19+0200] [ALPM] upgraded fakeroot (1.31-2 -> 1.32-1)
[2023-07-12T16:17:19+0200] [ALPM] upgraded libpipewire (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:19+0200] [ALPM] upgraded pipewire (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:19+0200] [ALPM] upgraded pipewire-audio (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:19+0200] [ALPM] upgraded pipewire-jack (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:19+0200] [ALPM] upgraded mesa (23.1.3-1 -> 23.1.3-2)
[2023-07-12T16:17:20+0200] [ALPM] upgraded firefox (115.0.1-1 -> 115.0.2-1)
[2023-07-12T16:17:20+0200] [ALPM] upgraded fwupd (1.9.2-2 -> 1.9.3-1)
[2023-07-12T16:17:21+0200] [ALPM] upgraded groff (1.23.0-1 -> 1.23.0-2)
[2023-07-12T16:17:21+0200] [ALPM] upgraded grub (2:2.06.r591.g6425c12cd-1 -> 2:2.12rc1-1)
[2023-07-12T16:17:22+0200] [ALPM] upgraded gst-plugin-pipewire (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:22+0200] [ALPM] upgraded inxi ( ->
[2023-07-12T16:17:22+0200] [ALPM] upgraded linux (6.4.2.arch1-1 -> 6.4.3.arch1-1)
[2023-07-12T16:17:24+0200] [ALPM] upgraded linux-headers (6.4.2.arch1-1 -> 6.4.3.arch1-1)
[2023-07-12T16:17:24+0200] [ALPM] upgraded pipewire-alsa (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:24+0200] [ALPM] upgraded pipewire-pulse (1:0.3.73-1 -> 1:0.3.73-2)
[2023-07-12T16:17:24+0200] [ALPM] upgraded systemd-resolvconf (253.5-2 -> 253.6-2)
[2023-07-12T16:17:24+0200] [ALPM] upgraded systemd-sysvcompat (253.5-2 -> 253.6-2)
[2023-07-12T16:17:24+0200] [ALPM] upgraded xorg-server-common (21.1.8-1 -> 21.1.8-2)
[2023-07-12T16:17:24+0200] [ALPM] upgraded xorg-server (21.1.8-1 -> 21.1.8-2)
[2023-07-12T16:17:24+0200] [ALPM] upgraded xterm (383-1 -> 384-1)
[2023-07-14T19:14:59+0200] [ALPM] upgraded alsa-card-profiles (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:14:59+0200] [ALPM] upgraded eos-translations (23-22 -> 23-23)
[2023-07-14T19:14:59+0200] [ALPM] upgraded libnghttp2 (1.54.0-1 -> 1.55.0-1)
[2023-07-14T19:14:59+0200] [ALPM] upgraded harfbuzz (7.3.0-2 -> 8.0.1-1)
[2023-07-14T19:14:59+0200] [ALPM] upgraded harfbuzz-icu (7.3.0-2 -> 8.0.1-1)
[2023-07-14T19:14:59+0200] [ALPM] upgraded eos-bash-shared (23-20 -> 23-22)
[2023-07-14T19:14:59+0200] [ALPM] upgraded eos-hooks (1.14-1 -> 1.15-1)
[2023-07-14T19:14:59+0200] [ALPM] upgraded fakeroot (1.32-1 -> 1.32.1-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded libpipewire (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded pipewire (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded gst-plugin-pipewire (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded pacman-contrib (1.9.0-1 -> 1.9.1-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded pipewire-audio (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded pipewire-alsa (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded pipewire-jack (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded pipewire-pulse (1:0.3.73-2 -> 1:0.3.74-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded poppler (23.06.0-1 -> 23.07.0-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded poppler-glib (23.06.0-1 -> 23.07.0-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded poppler-qt5 (23.06.0-1 -> 23.07.0-1)
[2023-07-14T19:15:00+0200] [ALPM] upgraded sudo (1.9.13.p3-1 -> 1.9.14.p1-1)
[root@EndeavourOS /]# 

hmm you could try running reinstall-kernels in that environment and reboot.
If that doesn’t work, try posting the link from inxi -Fxxc0z | eos-sendlog when you arch-chroot in again.


Hi again friend, I used your command and got this. I’m going to try reinstalling the kernel too.

  Kernel: 6.3.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.1.1 Console: N/A wm: xfwm
    DM: startx Distro: EndeavourOS base: Arch Linux
  Type: Desktop Mobo: Gigabyte model: H61M-D2H-USB3 v: x.x serial: N/A BIOS: Award v: F7
    date: 07/13/2012
  Info: quad core model: Intel Core i5-3470 bits: 64 type: MCP arch: Ivy Bridge rev: 9 cache:
    L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 1600 min/max: 1600/3600 cores: 1: 1600 2: 1600 3: 1600 4: 1600
    bogomips: 25549
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte GV-N105TOC-4GD driver: nouveau
    v: kernel arch: Pascal pcie: speed: 2.5 GT/s lanes: 16 ports: active: DP-1
    empty: DVI-D-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1c82 temp: 43.0 C
  Display: server: X.org v: compositor: xfwm driver: X: loaded: modesetting
    alternate: fbdev,nouveau,nv,vesa dri: nouveau gpu: nouveau display-ID: :0.0
  Monitor-1: DP-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7")
  API: OpenGL Message: GL data unavailable for root.
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Gigabyte 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20
  Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fb9
  API: ALSA v: k6.3.4-arch1-1 status: kernel-api
  Server-1: PipeWire v: 0.3.74 status: n/a (root, process) with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
  Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: Gigabyte driver: atl1c v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 port: df00 bus-ID: 06:00.0 chip-ID: 1969:1083
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Local Storage: total: 694.35 GiB used: 10.64 GiB (1.5%)
  ID-1: /dev/sda vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB speed: 3.0 Gb/s
    serial: <filter>
  ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB speed: 3.0 Gb/s
    serial: <filter>
  ID-3: /dev/sdc vendor: Maxtor model: STM3250310AS size: 232.89 GiB speed: 3.0 Gb/s
    serial: <filter>
  ID-4: /dev/sdd vendor: SanDisk model: USB 3.2Gen1 size: 14.32 GiB type: USB rev: 3.0
    spd: 5 Gb/s lanes: 1 serial: <filter>
  ID-1: / size: 101.38 GiB used: 10.64 GiB (10.5%) fs: ext4 dev: /dev/sda4
  Alert: No swap data was found.
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: nouveau temp: 43.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0
  Processes: 254 Uptime: 4m Memory: total: 8 GiB available: 7.74 GiB used: 1.5 GiB (19.4%)
  Init: systemd v: 253 default: graphical Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 1042 Client: Unknown Client: systemd inxi: 3.3.28

I think I’m doing something wrong, the command seems wrong.

[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sda4 /mnt
[liveuser@eos-2023.05.28 ~]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# reinstall-kernels
bash: reinstall-kernels: command not found
[root@EndeavourOS /]# sudo reinstall-kernels
sudo: reinstall-kernels: command not found
[root@EndeavourOS /]# 

This command is for systemd-boot, but I see grub in the list of updated packages!

1 Like

first issue is that you have to mount the ESP efi partition properly in case you need to reinstall kernels and fix bootloader stuff…
to guide you on this you need to show the partitions first:
lsblk -o name,type,size,PTTYPE,FSTYPE
sudo fdisk -l


and this looks like not fully installed the nvidia drivers…
better use nvidia-inst

EndeavourOS do not install all systems the same, installer is very open to mset system up in very different ways…


Thanks friend, I’m sorry I don’t know much about computers or Linux, I’m sorry if I don’t know how to explain myself.

I am using only SSD Number 1, which is the sda, with dual boot Windows 10 + EOS.

sda1 > windows 10
sda2 > windows 10
sda3 > windows 10
sda4 > EOS

I’m new to Linux, I don’t know how to partition, and my disk is MBR because my gigabyte motherboard is old, I can’t have more than 4 partitions on the same hard disk, because I don’t have GPT/EFI.

So I installed EOS all in root /, since I think I can’t create more than 4 partitions.

When installing EOS the SYSTEMD option didn’t appear because that’s for new pcs, I could only get the GRUB option.

The other hard drives only have files

sdb > hard drive with files
sdc > hard drive with files
sdd > flash drive with Ventoy + EOS

[root@EndeavourOS /]# lsblk -o name,type,size,PTTYPE,FSTYPE
loop0      loop   1.7G        
sda        disk 223.6G        
├─sda1     part    50M        
├─sda2     part 119.4G        
├─sda3     part   535M        
└─sda4     part 103.6G        
sdb        disk 223.6G        
└─sdb1     part 223.6G        
sdc        disk 232.9G        
└─sdc1     part 232.9G        
sdd        disk  14.3G        
├─sdd1     part  14.3G        
│ └─ventoy dm     1.9G        
└─sdd2     part    32M        
[root@EndeavourOS /]# 

[root@EndeavourOS /]# sudo fdisk -l
Disk /dev/sda: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: CT240BX500SSD1  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x07bba333

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048    104447    102400    50M  7 HPFS/NTFS/exFAT
/dev/sda2          104448 250561293 250456846 119.4G  7 HPFS/NTFS/exFAT
/dev/sda3       250562560 251658239   1095680   535M 27 Hidden NTFS WinRE
/dev/sda4       251658240 468857024 217198785 103.6G 83 Linux

Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SA400S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x90fd7f18

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1        2048 468858879 468856832 223.6G  7 HPFS/NTFS/exFAT

Disk /dev/sdc: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: MAXTOR STM325031
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0dee0dee

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1          63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

Disk /dev/sdd: 14.32 GiB, 15376318464 bytes, 30031872 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf881989c

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdd1  *        2048 29966335 29964288 14.3G  7 HPFS/NTFS/exFAT
/dev/sdd2       29966336 30031871    65536   32M ef EFI (FAT-12/16/32)

Disk /dev/mapper/ventoy: 1.91 GiB, 2049585152 bytes, 4003096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb15bb315

Device                   Boot   Start     End Sectors  Size Id Type
/dev/mapper/ventoy-part1 *         64 3775103 3775040  1.8G  0 Empty
/dev/mapper/ventoy-part2      3775104 4002431  227328  111M ef EFI (FAT-12/16/32)

Disk /dev/loop0: 1.69 GiB, 1815875584 bytes, 3546632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

thats not an issue for us here we do help regardless of your level of knowledge

1 Like

I have installed it, I am going to reboot to see if it has worked.

[root@EndeavourOS /]# yay -S nvidia-inst
 -> Avoid running yay as root/sudo.
Sync Explicit (1): nvidia-inst-23-6
resolving dependencies...
looking for conflicting packages...

Package (3)                          New Version  Net Change  Download Size

extra/dkms                           3.0.11-1       0.11 MiB               
endeavouros/nvidia-installer-common  23-6           0.01 MiB       0.02 MiB
endeavouros/nvidia-inst              23-6           0.02 MiB       0.02 MiB

Total Download Size:   0.03 MiB
Total Installed Size:  0.15 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 nvidia-inst-23-6-any                      16.1 KiB  89.6 KiB/s 00:00 [--------------------------------------] 100%
 nvidia-installer-common-23-6-any          17.4 KiB  84.1 KiB/s 00:00 [--------------------------------------] 100%
 Total (2/2)                               33.5 KiB   144 KiB/s 00:00 [--------------------------------------] 100%
(3/3) checking keys in keyring                                        [--------------------------------------] 100%
(3/3) checking package integrity                                      [--------------------------------------] 100%
(3/3) loading package files                                           [--------------------------------------] 100%
(3/3) checking for file conflicts                                     [--------------------------------------] 100%
:: Processing package changes...
(1/3) installing dkms                                                 [--------------------------------------] 100%
Optional dependencies for dkms
    linux-headers: build modules against the Arch kernel [installed]
    linux-lts-headers: build modules against the LTS kernel
    linux-zen-headers: build modules against the ZEN kernel
    linux-hardened-headers: build modules against the HARDENED kernel
(2/3) installing nvidia-installer-common                              [--------------------------------------] 100%
Optional dependencies for nvidia-installer-common
    linux-headers: for nvidia-installer-dkms with kernel linux [installed]
    linux-lts-headers: for nvidia-installer-dkms with kernel linux-lts
    linux-hardened-headers: for nvidia-installer-dkms with kernel linux-hardened
    linux-zen-headers: for nvidia-installer-dkms with kernel linux-zen
    expac: faster way for finding available package versions [installed]
(3/3) installing nvidia-inst                                          [--------------------------------------] 100%
Optional dependencies for nvidia-inst
    linux-headers: for nvidia-inst with kernel linux [installed]
    linux-lts-headers: for nvidia-inst with kernel linux-lts
    linux-hardened-headers: for nvidia-inst with kernel linux-hardened
    linux-zen-headers: for nvidia-inst with kernel linux-zen
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[root@EndeavourOS /]# 
1 Like
Disklabel type: dos

showing you have installed in legacy mode or the Computer is older in age like 10 y old ?
So no need to mount ESP as legacy does not have this :wink:

But it also shows you will not have systemd-boot and using grub.


sudo mount /dev/sda4 /mnt
and chroot into your installed system with this terminal:
sudo arch-chroot /mnt
inside this very one terminal:
can you show the output of these commands too please?

pacman -Qs nvidia
pacman -Qs dracut
1 Like

this is only a tool to easily install nvidia drivers and stuff … you still need to run it …


[2023-07-12T16:17:19+0200] [ALPM] upgraded dracut (059-1 -> 059-2)

i see this in your update log :wink:

so all clear…


simply run
from the chrooted terminal and show the output please!