[root@EndeavourOS /]# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0
sda
├─sda1 ext4 1.0 d1a3e63f-1931-4b17-a860-b6cbef37c814 66.8G 25% /
└─sda2 ext4 1.0 e59c880a-817f-4803-ab45-7d3cc09f3480
sr0 iso9660 Joliet Ex EOS_202112 2021-12-17-11-32-24-00
[root@EndeavourOS /]#
This looks like a successful chroot.
If you want to post the content of the mkinitcpio.conf, run
cat /etc/mkinitcpio.conf
copy the terminal output and post it here.
1 Like
[root@EndeavourOS /]# cat /etc/mkinitcpio.conf
# 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=(piix ide_disk reiserfs)
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 block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont filesystems fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
[root@EndeavourOS /]#
I always create a separate partition for my user home at the install, perhaps that’s the problem ?
There is nothing there.
Would doing
mkinitcpio -P
and perhaps
grub-mkconfig -o /boot/grub/grub.cfg
make sense at this stage?
BTW, @linuxuser501, what is in your /etc/default/grub ?
cat /etc/default/grub
[root@EndeavourOS /]# cat /etc/default/grub
# GRUB boot loader configuration
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="EndeavourOS"
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nowatchdog nvme_load=YES"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false
# 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 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu
# 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 `vbeinfo'
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-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME=/boot/grub/themes/EndeavourOS/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
[root@EndeavourOS /]#
I would run those two commands above. When it is done, type exit followed by enter.
Reboot.
If you get any error message, post them here.
Tried both commands with sucess, didn’t see any errors on the terminal but still stuck at the blackscreen at boot
1 Like
I would like to try the command from this comment, does anyone knows how to do that ?
https://aur.archlinux.org/packages/nvidia-340xx-dkms#comment-864543
It looks like a command to run after installing nvidia or maybe even an install command but i don’t know to tell.
I am glad that i burned a backup Dvd 2 days ago
Hi
Iam probably going to put my foot in it and offer wrong advice, however.
You are getting a black screen when trying to boot? Where I come from I know that
the dkms number off your nvida card must mach the number off your kernel for them to function.
Soo you have to match them up I believe. Then you stand a chance off booting successfully.
Now I dont know a lot about the process of doing this, I am only basing this off your comment
that you wish to try this "nvidia-340-dkms-> comment-864543. specifically dkms…
What kernel are you using?
What graphics hardware are you using?
The secret is finding the sweat spot, Iam not the one to know what commands to display
the correct information to work it out sorry. Someone else will have to help with that
IF THAT IS THE PROBLEM. @ricklinux @Bryanpwo
I HIH you. here Iam new so take it with a pinch of salt.
–
Data
Hi Data
Yes
I just use the kernel that comes by default on endeavour os, i believe it’s this one:
linux 5.17.5.arch1-2
Neofecth says “NVIDIA GeForce 210” but you can find more information here:
https://clbin.com/UYChd
Hi
I see you have or are using ‘nouveau’ drivers at the moment
Kernel: 5.17.5-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
Device-1: NVIDIA GT218 [GeForce 210] vendor: ZOTAC driver: nouveau
Not sure how to mach up the kernel to dkms number, and even if this is the error
that is stopping your boot. Sorry Iam not much help.
Iam new I come from Arcolinux we have an alis rip
which allowed the user to supply a list off installed or recently installed packages.
this would help if we new the programs installed in your update.
Do you remember at all what what was being updated or installed in the update???
Ive tried rip here its not an alis off endovour so it does not work, cliped this graphic
from an arco video. also expac has to be installed.
That would help but the command is very long and the chances of typo or it working here
is slim.
Here is the complete url to video about rip. ArcoLinux : 703 use the alias rip to see the Recent Installed Packages - YouTube
HIH I dig my self a hole.
–
Data
I do remember a few programs-packages being updated: linux, chromium, firefox-developer-edition, etc, i do not remember much more, i am on a Live CD right now i’d need to chroot to find out and i am not really very good with that, not sure if i can be very helpful
I’ll try to watch the video and see what i can do
Btw i had managed to get the drivers installed for the nvidia a few days ago thanks to the help of the forum here, you can check the topic for more information:
Hi
You and me I could not understand/workout chroot either.
Not sure if that log you pasted is off the live system or your actual hardward drivers.
Sorry.
–
Data
actual hardware drivers
How did you get on last night ? I had to go get some sleep.
Did you get any sense ?
For all at home: I have received a pm about this topic.
–
Data
I am still booting the Live CD from a dvd so i can access the forum
@jruschme did the update break your system too ??
No Iam good Im just trying to help you. Im Golden.
Thank you, that’s highly appreciated !!, my mention was to jruschme tho, he uses the same legacy nvidia drivers like me.
If you are not comfortable with such problems, I would suggest you switch to using the open source nouveau driver.
As it is stated in the AUR project, they can’t provide good/immediate support and suggest tom keep your kernel from updating, which is not a good/accepted approach on Archlinux. As such, if you keep 340, you have lots of possibilities your boot will again break.
If you want to continue with 340, you have to chroot to your installed system, and run the proper dkms command (including the current kernel version name, the output of uname -r) to install nvidia modules to the kernel. This should be done on each kernel or nvidia upgrade.
I don’t use this driver and cannot guarantee anything, so take responsibility of your own system.