Whenever I poweroff or reboot my computer, the screen “freezes” for 1-2s and simply powers off or reboots, without actually printing out those usual logs,- y’know the ones when the services get stopped and such..
eg. like this one (random image from the internet for representation, and not from my actual PC) , but for shutting down/rebooting procedure
Quick sum: using Nvidia (nvidia) + mainline linux kernel + wayland + plasma, so technically everything default really.
The oddest thing is during booting up my PC, the usual bootup logs are correctly printed out to my screen… I do not use plymouth or any fancy stuffs, I like to see texts on my screen during boot or poweroff/reboot, and the latter doesn’t want to work, and I’m tearing my hair out right now, because on my almost identical (also Nvidia) “testing/dummy” machine everything just works…
It’s a random image from the internet, not from my machine, that’s why I wrote “eg”, but yeah I should have been more clear than that (edited my OP now for clarity) sorry… I just wanted to represent which “log” I was thinking about
# GRUB boot loader configuration
GRUB_DEFAULT='0'
GRUB_TIMEOUT='5'
GRUB_DISTRIBUTOR='EndeavourOS'
GRUB_CMDLINE_LINUX_DEFAULT='nowatchdog nvme_load=YES nvidia_drm.modeset=1 loglevel=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 '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 `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-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
GRUB_BACKGROUND='/usr/share/endeavouros/splash.png'
#GRUB_THEME="/path/to/gfxtheme"
# 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='false'
# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
#GRUB_DISABLE_OS_PROBER=false
GRUB_EARLY_INITRD_LINUX_STOCK=''
The dracut conf is untouched also, and at defaults:
$ cat /etc/dracut.conf.d/eos-defaults.conf
omit_dracutmodules+=" network cifs nfs nbd brltty "
compress="zstd"
$ cat /etc/dracut.conf
# PUT YOUR CONFIG IN separate files
# in /etc/dracut.conf.d named "<name>.conf"
# SEE man dracut.conf(5) for options
So could it be because my PC is so fast that not even the log can render to my screen at poweroff/reboot?
Oh ! Thank you for your feedback for clarifying this,- now at least I know I’m not the only one with this issue, because this thing keeps bugging my mind to a point I’m tearing my last hairs out
Can I ask what GPU you have? And also can you tell/remember when this behavior started to arise, or you’re also on a fresh install?
I don’t think it’s normal to be honest both with you and @joekamprad , and the reason for that is I have two additional installs of EndeavourOS on two different machines of mine, and the poweroff/reboot procedure never hangs, never freezes, and perfectly shows the poweroff log - as it should work on every linux system. The best part, is that my two other PCs were also installed the same way, having also the identical softwares on them, and no tweakings were made, because I ain’t look for no trouble… And to even further top it off, one of those machines is also equipped with Nvidia card (a bit older one - Quadro K620 series) and as I said, poweroff logs work on it aswell without any mini freeze or whatsoever.
Yes, and that’s why it is in my config also.. - or what’s your point now? I don’t really get it, can you please further elaborate your statement in a more detailed manner?
I haven’t added it, it was there by default. Look, since I don’t really know about arch, I don’t dare to touch anything, so every single config file I post here, are made by you (or anyone else working for endeavouros team) - this is how you guys shipped that config for me/us..
Why though? Your point is to remove that then and do a dracut-rebuild afterwards? Side note, it is also how it looks on my dummy (testing) machine (which is also equipped with Nvidia) and the poweroff/reboot doesn’t ministutters and displays the logs perfectly, so I doubt that this would be the line causing it..
One very important note though, but I don’t want to manipulate your guys thoughts, so I’m just sharing what I experienced: I can’t switch to other TTYs via the ctrl+alt+F(1-7) keys, because my monitor goes “no-signal” mode (this is with my GTX 1050 Ti card). There are still unsolved misteries, and it seems it’s not a unique problem, now as @keescase also noted..
However, on my other K620 Nvidia, I can switch to TTY… Could it be it then? When we poweroff/reboot, we actually see a TTY because linux switches to it during the poweroff/reboot procedure?
Well I don’t have Nvidia , but a AMD IGP, and it is no stutter or freeze or anything, just a small delay for maybe even less of a second. If this should be a problem at all I would have noticed it somehow.
But you’re also not seeing that usual poweroff/reboot log printed on screen while powering off or rebooting your pc, and instead experience a mini-stutter/freeze, correct?
You’re only seeing the logs printed on-screen, while booting in, am I right?
Perfect. Thank you very much for clarifying. So rest assured this isn’t an Nvidia issue (or GPU in general) for sure, we’ve just isolated this right now. This is either a config regression (which is shipped by default with EOS…) or something else, so I’m very curious right now of what can we do in order to squash this bug once and for all… @joekamprad ?
i5-6500 CPU @ 3.20GHz
I just wanted to represent which “log” I was thinking about
