Boot stuck at target graphical interface

Edited my message for more diagnostic stuff.

/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

resolving dependencies...
looking for conflicting packages...

Packages (1) nvidia-dkms-525.60.11-1

Total Installed Size:  68.44 MiB
Net Upgrade Size:       0.00 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Running pre-transaction hooks...
(1/2) Performing snapper pre snapshots for the following configurations...
IO Error (.snapshots is not a btrfs subvolume).
==> root: 
(2/2) Remove upgraded DKMS modules
==> dkms remove nvidia/525.60.11
:: Processing package changes...
reinstalling nvidia-dkms...
:: Running post-transaction hooks...
(1/9) Arming ConditionNeedsUpdate...
(2/9) Install DKMS modules
==> dkms install --no-depmod nvidia/525.60.11 -k 6.0.12-zen1-1-zen
Error! Bad return status for module build on kernel: 6.0.12-zen1-1-zen (x86_64)
Consult /var/lib/dkms/nvidia/525.60.11/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/525.60.11 -k 6.0.12-zen1-1-zen' exited 10
(3/9) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 6.0.12-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 6.0.12-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> 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: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci

When I pipe pacman to netcat termbin.com 9999 the output seems to be cut-off

Still the same problem????

DKMS make.log for nvidia-525.60.11 for kernel 6.0.12-zen1-1-zen (x86_64)
Thu Dec 15 12:58:07 AM IST 2022
make[1]: Entering directory '/usr/lib/modules/6.0.12-zen1-1-zen/build'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 12.2.0
  You are using:           

The C compiler 'cc' does not appear to be able to
create executables.  Please make sure you have 
your Linux distribution's gcc and libc development
packages installed.

*** Failed CC sanity check. Bailing out! ***


Warning: Compiler version check failed:

The major and minor number of the compiler used to
compile the kernel:

gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0

does not match the compiler used here:

cc: error while loading shared libraries: libhiredis.so.1.0.0: cannot open shared object file: No such file or directory

It is recommended to set the CC environment variable
to the compiler that was used to compile the kernel.

To skip the test and silence this warning message, set
the IGNORE_CC_MISMATCH environment variable to "1".
However, mixing compiler versions between the kernel
and kernel modules can result in subtle bugs that are
difficult to diagnose.

*** Failed CC version check. ***

make[2]: *** [/var/lib/dkms/nvidia/525.60.11/build/Kbuild:335: cc_sanity_check] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1849: /var/lib/dkms/nvidia/525.60.11/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.0.12-zen1-1-zen/build'
make: *** [Makefile:82: modules] Error 2

Ok got it, as I said ccache has symlinks, which I will remove

I canā€™t thank you enough @TNE
Iā€™ll be wary about my environment variables.

sudo btrfs subvolume list /

ID 257 gen 844841 top level 5 path @home
ID 258 gen 844839 top level 5 path @root
ID 259 gen 843335 top level 5 path @srv
ID 260 gen 844840 top level 5 path @cache
ID 261 gen 844841 top level 5 path @log
ID 262 gen 844835 top level 5 path @tmp
ID 276 gen 843340 top level 5 path @_backup_20221412214741565
ID 309 gen 844841 top level 5 path @
ID 310 gen 844840 top level 309 path .snapshots

Is this fine?

You will probably want to delete _backup_20221412214741565 in btrfs assistant and that will be that.

Where would those symlinks even be? /usr/local/bin?

Sorry whats the path to it?

From the ccache docs:

Let ccache masquerade as the compiler. This method is most useful when you wish to use ccache for all your compilations. To do this, create a symbolic link to ccache named as the compiler. For example, here is set up ccache to masquerade as gcc and g++:

cp ccache /usr/local/bin/ ln -s ccache /usr/local/bin/gcc ln -s ccache /usr/local/bin/g++

On platforms that donā€™t support symbolic links you can simply copy ccache to the compiler name instead for a similar effect:

cp ccache /usr/local/bin/gcc cp ccache /usr/local/bin/g++

And so forth. This will work as long as the directory with symbolic links or ccache copies comes before the directory with the compiler (typically /usr/bin) in PATH.

That should do it.

Done, thanks.

I hereby bestow upon you the Most Dramatic Developer Award for Garuda 2022.
:trophy:

P.S. Thanks for the great read.
:rofl:

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.