Yes, I am using Nvidia GPU and causing some errors for me, but I’m still planning to replace it with AMD one. But, for now, can this be fixed? Or I roll back to another kernel?
Fair enough.
I’ve seen enough problems with it, though, that I’ve purged it from my computer, and every time something like this comes along, it makes me extremely glad from the beginning.
~ cat /etc/default/grub ✔
# GRUB boot loader configuration
GRUB_DEFAULT=0
GRUB_TIMEOUT=30
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Set to 'countdown' or 'menu' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=hidden
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
cat /etc/mkinitcpio.conf INT ✘
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(usbhid xhci_hcd)
MODULES=()
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=()
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No RAID, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect modconf block filesystems fsck)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev modconf block filesystems fsck)
#
## This setup assembles a mdadm array with an encrypted root file system.
## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
# HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
## This setup loads an lvm2 volume group.
# HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr and fsck hooks.
HOOKS=(base udev autodetect modconf kms block keyboard keymap consolefont plymouth filesystems fsck)
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"
Yes - I once had a laptop with dual GPU - Thinkpad T550 - it worked best with the opensource drivers - and by comparison your gpu is older than the one in my Thinkpad.
For the eliminating plymouth from the error pool
Edit your /etc/mkinitcpio.conf and remove plymouth and kms from the hooks line and save the file.
Note: The kms hook is added by an update to mkinitcpio but for the kms hook to work - you will have to enable the nvidia framebuffer - using kernel arguments and for a device that old - I have no idea.
See the Arch Wiki → Kernel mode setting - ArchWiki
That said
if you remove the nvidia driver from your system and add nouveau
you can keep the kms hook in mkinitcpio
if you want to keep the nvidia driver you will have to remove kms from the hooks array
Edit your /etc/default/grub and rmove quiet and splash from the command line and save the file.
Let’s start with changing the driver, may be it’s the problem.
Does clicking (Auto install open source driver) like this screenshot do the job? https://i.imgur.com/1hvjxC5.png
I admit it - I have not - I am no gamer - I was - am - kind trying to help troubleshooting the black screen and one way is switch driver.
I won’t say the nouveau driver is better than nvidia - most likely it is not - process of elimination.
And configuring Nvidia can be a pain - I know - I had my issues over the years with Nvidia on Linux - mostly it didn’t work well - it has gotten better.
Once passed the black screen - it becomes easier to make one small change at time until it works as expected.
I installed them using Pamac and Pacman, both with the same results. But, with Manjaro settings, it gives me an error saying (Not found linux610 nvidia).
~ pamac search --installed 470 ✔
opencl-nvidia-470xx 470.256.02-3 extra
OpenCL implemention for NVIDIA
nvidia-470xx-utils 470.256.02-3 extra
NVIDIA drivers utilities
nvidia-470xx-settings 470.256.02-1 extra
Tool for configuring the NVIDIA graphics driver
nvidia-470xx-dkms 470.256.02-3 extra
NVIDIA drivers - module sources
mhwd-nvidia-470xx 470.256.02-3 extra
MHWD module-ids for nvidia 470.256.02
linux69-nvidia-470xx 470.256.02-10 extra
NVIDIA drivers for linux
libxnvctrl-470xx 470.256.02-1 extra
NVIDIA NV-CONTROL X extension
lib32-opencl-nvidia-470xx 470.256.02-1 multilib
OpenCL implemention for NVIDIA (32-bit)
lib32-nvidia-470xx-utils 470.256.02-1 multilib
NVIDIA drivers utilities (32-bit)
~
pamac search --installed nvidia ✔
egl-wayland 2:1.1.13-2 extra
EGLStream-based Wayland external platform
opencl-nvidia-470xx 470.256.02-3 extra
OpenCL implemention for NVIDIA
mhwd-nvidia-470xx 470.256.02-3 extra
MHWD module-ids for nvidia 470.256.02
mhwd-nvidia-390xx 390.157-14 extra
MHWD module-ids for nvidia 390.157
mhwd-nvidia 550.100-1 extra
MHWD module-ids for nvidia 550.100
linux69-nvidia-470xx 470.256.02-10 extra
NVIDIA drivers for linux
lib32-opencl-nvidia-470xx 470.256.02-1 multilib
OpenCL implemention for NVIDIA (32-bit)
lib32-nvidia-470xx-utils 470.256.02-1 multilib
NVIDIA drivers utilities (32-bit)
nvidia-470xx-utils 470.256.02-3 extra
NVIDIA drivers utilities
nvidia-470xx-settings 470.256.02-1 extra
Tool for configuring the NVIDIA graphics driver
nvidia-470xx-dkms 470.256.02-3 extra
NVIDIA drivers - module sources
sudo mhwd --install pci video-nvidia-470xx ✔
[sudo] password for minaw:
> Installing video-nvidia-470xx...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/nvidia-470xx/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0302
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
multilib downloading...
DEB_Arch_Extra downloading...
warning: nvidia-470xx-utils-470.256.02-3 is up to date -- skipping
warning: nvidia-470xx-settings-470.256.02-1 is up to date -- skipping
warning: libxnvctrl-470xx-470.256.02-1 is up to date -- skipping
warning: lib32-nvidia-470xx-utils-470.256.02-1 is up to date -- skipping
error: target not found: linux610-nvidia-470xx
warning: linux69-nvidia-470xx-470.256.02-10 is up to date -- skipping
Error: pacman failed!
Error: script failed!
sudo mhwd --force --install pci video-nvidia-470xx
> Installing video-nvidia-470xx...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/nvidia-470xx/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0302
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
multilib downloading...
DEB_Arch_Extra downloading...
warning: nvidia-470xx-utils-470.256.02-3 is up to date -- skipping
warning: nvidia-470xx-settings-470.256.02-1 is up to date -- skipping
warning: libxnvctrl-470xx-470.256.02-1 is up to date -- skipping
warning: lib32-nvidia-470xx-utils-470.256.02-1 is up to date -- skipping
error: target not found: linux610-nvidia-470xx
warning: linux69-nvidia-470xx-470.256.02-10 is up to date -- skipping
Error: pacman failed!
Error: script failed!
First pacman fails - second the mhwd script fails because pacman failed.
And you have an unsupported 3rd party repo
Edit your pacman.conf and comment the three/four lines defining the 3rd party repo - save file - start with fixing why pacman fails.
sudo pacman-mirrors --continent
sudo pacman -Syu
This will fix the missing package
$ mbn info linux610-nvidia-470xx -q
Branch : unstable
Name : linux610-nvidia-470xx
Version : 470.256.02-0.2
Repository : extra
Build Date : Sun 21 Jul 2024 06:17:36
Packager : Philip Mueller <philm@manjaro.org>
Branch : testing
Name : linux610-nvidia-470xx
Version : 470.256.02-0.1
Repository : extra
Build Date : Sun 21 Jul 2024 06:04:03
Packager : Philip Mueller <philm@manjaro.org>
Branch : stable
Name : linux610-nvidia-470xx
Version : 470.256.02-0.1
Repository : extra
Build Date : Sun 21 Jul 2024 06:04:03
Packager : Philip Mueller <philm@manjaro.org>