You are not logged in.
Pages: 1
Hi everyone !
After a successful install on my Thinkpad T410 laptop with a nice KDE setup with graphical boot, I went on to install Arch on my desktop too with more or less the same setup.
The only (minor) problem I have is that I can't get the Plymouth to show on boot. It works fine on my laptop, so I'd like to understand what is going on here.
I have followed all the steps on the wiki article, but the current state is that nothing shows up between the bootloader and SDDM. Only a gray screen, black, then gray again, then SDDM. Here is my setup :
I am using rEFInd as bootloader. Here are the kernel parameters I have set up :
$ cat /boot/refind_linux.conf
"Normal Boot" "root=""LABEL=ARCH-ROOT"" rw resume=""LABEL=LINUX-SWAP"" nvidia-drm.modeset=1 quiet splash loglevel=3 rd.udev.log_priority=3 vt.global_cursor_default=0 initrd=/intel-ucode.img initrd=/initramfs-%v.img"
"Fallback mode" "root=""LABEL=ARCH-ROOT"" rw resume=""LABEL=LINUX-SWAP"" initrd=/intel-ucode.img initrd=/initramfs-%v-fallback.img"They should be properly taken into account as this shows :
$ cat /proc/cmdline
root="LABEL=ARCH-ROOT" rw resume="LABEL=LINUX-SWAP" nvidia-drm.modeset=1 quiet splash loglevel=3 rd.udev.log_priority=3 vt.global_cursor_default=0 initrd=/intel-ucode.img initrd=/initramfs-linux-zen.imgI have also tried to add `vga=current` as advised in the Silent Boot article, still with no success.
I am using systemd in my initramfs, here is my mkinitcpio.conf file :
$ 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=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
# 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=(/etc/modprobe.d/nvidia.conf)
#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 systemd sd-plymouth autodetect modconf block sd-lvm2 filesystems keyboard fsck)
#HOOKS=(base udev plymouth autodetect modconf block lvm2 filesystems keyboard 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_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()As you can see in the comments, I have tried the udev way too, with no success.
I have activated the sddm-plymouth service in place of sddm, and here is my plymouthd.conf file :
$ cat /etc/plymouth/plymouthd.conf
# Distribution defaults. Changes to this file will get overwritten during
# upgrades.
[Daemon]
Theme=text
ShowDelay=0
DeviceTimeout=8As stated in the wiki, you can see that I have tried setting the ShowDelay setting to 0 and DeviceTimeout to 8, with no success.
The theme is currently the simple "text" one, that I have set with the following command :
$ sudo plymouth-set-default-theme -R textThe default theme spinner was not working either.
Now when I try to display the splash screen manually once booted, with `plymouth --show-splash`, I can make the spinner theme show, but not the text theme... Which makes me suspect that on boot, Plymouth defaults to the text theme, which fails to display.
(On a side note, I can't switch back to a TTY when I manually display the splash screen... Ctrl-Alt-F[1-9] does not work. I have to hit the reset button of the computer because I can't do anything else. Any advice on that ?)
The differences between my desktop and laptop are :
- My laptop does not support UEFI, so I use GRUB as bootloader on it
- My dekstop has a Nvidia GPU (Geforce GTX 960), while my laptop uses integrated Intel graphics with the i915 driver.
So maybe the Nvidia drivers are to blame here ? But what confuses me is that when researching the issue, I saw several people telling that they managed to make it work on their Nvidia setup. I don't think rEFInd is to blame either, because I was using systemd-boot before and the situation was the same.
Can anyone that made it work with Nvidia give me some pointers ?
Here is some additional info :
$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
$ uname -a
Linux archtower 5.6.11-zen1-1-zen #1 ZEN SMP PREEMPT Wed, 06 May 2020 17:32:39 +0000 x86_64 GNU/Linux
$ pacman -Q nvidia-dkms
nvidia-dkms 440.82-1
$ pacman -Q plymouth
plymouth 0.9.4-7
$ lspci -v | grep -A 10 NVIDIA
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960]
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia
--
01:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. GM206 High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f7080000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intelOffline
First of all, did you rebuild your initrd after editing your plymouthd.conf? Have you schecked the status of sddm-plymoutyh.service?
I can't switch back to a TTY when I manually display the splash screen... Ctrl-Alt-F[1-9]
Did you switch first to a text terminal and logged in as root before running the command?
ls /usr/share/plymouth/themesIs text in your themes? (I believe it's default to be there but just check nevertheless.)
I have nvidia with plymouth and I have no problem whatsoever. You might as well run lsmod to check if the nvidia modules are properly loaded.
Offline
First of all, did you rebuild your initrd after editing your plymouthd.conf?
Yes, I made sure to rebuild it after any change I made before rebooting.
Have you schecked the status of sddm-plymoutyh.service?
I don't think the problem comes from SDDM as I have no problem logging in with it. But just in case, here it is the status just after a reboot and login :
$ systemctl status sddm-plymouth.service
● sddm-plymouth.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm-plymouth.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2020-05-08 18:39:23 CEST; 17s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 659 (sddm)
Tasks: 7 (limit: 9341)
Memory: 112.4M
CGroup: /system.slice/sddm-plymouth.service
├─659 /usr/bin/sddm
└─661 /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{11c61ed2-3bca-412d-b8ec-def5dec1646d} -background none -noreset -displayfd 17 -seat seat0 vt1
mai 08 18:39:31 archtower sddm-helper[776]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
mai 08 18:39:31 archtower sddm-helper[776]: [PAM] returning.
mai 08 18:39:31 archtower sddm[659]: Authenticated successfully
mai 08 18:39:31 archtower sddm-helper[776]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
mai 08 18:39:31 archtower sddm-helper[776]: pam_unix(sddm:session): session opened for user superboby by (uid=0)
mai 08 18:39:31 archtower sddm-helper[776]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
mai 08 18:39:31 archtower sddm[659]: Auth: sddm-helper exited successfully
mai 08 18:39:31 archtower sddm[659]: Greeter stopped.
mai 08 18:39:31 archtower sddm-helper[776]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
mai 08 18:39:31 archtower sddm[659]: Session started
$ systemctl status sddm.service
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:sddm(1)
man:sddm.conf(5)Did you switch first to a text terminal and logged in as root before running the command?
Yes, I did exactly as stated in the Plymouth article of the wiki.
Is text in your themes? (I believe it's default to be there but just check nevertheless.)
Yes it is :
$ ll /usr/share/plymouth/themes/
total 36
drwxr-xr-x 2 root root 4096 mai 7 10:19 details
drwxr-xr-x 2 root root 4096 mai 7 10:19 fade-in
drwxr-xr-x 2 root root 4096 mai 7 10:19 glow
drwxr-xr-x 2 root root 4096 mai 7 10:19 script
drwxr-xr-x 2 root root 4096 mai 7 10:19 solar
drwxr-xr-x 2 root root 4096 mai 7 10:19 spinfinity
drwxr-xr-x 2 root root 4096 mai 7 10:19 spinner
drwxr-xr-x 2 root root 4096 mai 7 10:19 text
drwxr-xr-x 2 root root 4096 mai 7 10:19 tribarI have nvidia with plymouth and I have no problem whatsoever. You might as well run lsmod to check if the nvidia modules are properly loaded.
Yes it is loaded. I don't have any other graphical problem, I can play games just fine :
$ lsmod | grep nvidia
nvidia_drm 53248 5
drm_kms_helper 258048 2 nvidia_drm,i915
drm 618496 10 drm_kms_helper,nvidia_drm,i915
nvidia_uvm 1093632 0
nvidia_modeset 1118208 14 nvidia_drm
nvidia 20520960 769 nvidia_uvm,nvidia_modeset
ipmi_msghandler 77824 2 ipmi_devintf,nvidiaThanks !
Offline
Perhaps add the plymouth.debug kernel parameter to see what the log outputs. Also in the wiki:
Make sure that the correct graphics module is added to /etc/mkinicpio.conf if the theme is graphical and not text.
Perhaps try not adding the module to see the text theme? My gut feeling though tells me it shouldn't really matter.
Offline
Perhaps add the plymouth.debug kernel parameter to see what the log outputs.
I have done this while still with the spinner theme activated.
Here is the debug log : https://gist.github.com/rshamsnejad/0c6 … 9a1544fdc1
There are some errors in it, but I don't really know what to make of them...
Perhaps try not adding the module to see the text theme? My gut feeling though tells me it shouldn't really matter.
I have removed all modules from the `MODULES=()` section in `/etc/mkinitcpio.conf`, and switched to the text theme with :
$ sudo plymouth-set-default-theme -R text
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 5.6.11-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [sd-plymouth]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [sd-lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 5.6.11-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [sd-plymouth]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [sd-lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
-> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.4.39-1-lts
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [sd-plymouth]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [sd-lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
-> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.4.39-1-lts
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [sd-plymouth]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [sd-lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successfulI rebooted and nothing changed, apart from the fact that I can see the 2-3 last lines of the boot log very quickly just before SDDM.
Offline
Pages: 1