• Problem setting splash screen with Plymouth


    Hi, I’m trying to set a splash screen on boot, after the grub selection.

    I installed the packages plymouth and plymouth-theme-antergos from antergos repos and followed the instructions on https://wiki.archlinux.org/index.php/Plymouth.
    System is up-to-date so are the packages above.

    After setting everything and rebooting, all I can see where the splash screen should be is a gray screen with 3 little white boxes alongside each other and 3 white boxes with question marks in it around the screen, the it proceeds to lightdm login screen normally (I’m using KDE). Example

    Oddly, it works when rebooting/shutting down the machine. I can see the splash screen briefly.

    What did I do wrong? I’ve revised every step and everything looks right, I just can’t see if I missed something

    Sorry I didn’t attached any logs, I’m new to Linux, so I don’t know which logs attach in this situation.

  • @alfatester Rebuild initramfs:

    sudo mkinitcpio --preset linux
    
  • @just
    Still nothing.

  • @alfatester Try to explicitely set the initial VESA graphical boot mode by using vga= parameter.

    • Nvidia, 1920x1080: vga=895
    • ATI, 1366x768, 1600x900: vga=1005
    • All cards, 800x600: vga=789
    • All cards, choose from standard VESA modes: vga=ask
    • Default VESA for any card: vga=normal
  • I would read here: https://forum.antergos.com/topic/7096/background-image-during-boot-process/11
    It seems to do not work well for today systems and kernels…-.

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @just
    I haven’t followed the above yet, because I was doing some testing and found something interesting.

    While following the Plymouth article, you come to a step where you have to set quiet and splash as kernel command line parameters, and the article suggests to see Kernel Parameters for more info.

    On Kernel Parameters page, GRUB section, it says:

     Press e when the menu shows up and add them on the linux line:
    
    linux /boot/vmlinuz-linux root=UUID=978e3e81-8048-4ae1-8a06-aa727458e8ff quiet splash
    
    Press Ctrl+x to boot with these parameters.
    
    To make the change persistent after reboot, while you could manually edit /boot/grub/grub.cfg with the exact line from above, the best practice is to:
    
    Edit /etc/default/grub and append your kernel options to the GRUB_CMDLINE_LINUX_DEFAULT line:
    
        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    

    My linux line in the GRUB parameters is:

    linux /boot/vmlinuz-linux root=UUID=0107a434-5029-4cd3-b8bf-72bfb05d487e rw quiet splash /resume=UUID=0107a434-5029-4cd3-b8bf-72bfb05d487e
    

    So in my parameters quiet and splash are already there. Removing rw and/or /resume… doesn’t work either, but, if I replace my UUID with the one provided on the article, it works! I can see the splash screen, but unfortunately it ends in a very long boot screen, then comes an error screen alerting that the UUID could not be found .

    Should I change my UUID on the /etc/defalt/grub file with the article UUID? I’m afraid of doing it and end locking my machine.

  • @alfatester said in Problem setting splash screen with Plymouth:

    Should I change my UUID on the /etc/defalt/grub file with the article UUID?..

    OMG. Are you kidding? No, you shouldn’t. You must use either UUID, or device name, or device label where the system is installed.

    Again. You must use the UUID of the partition, where Antergos is installed. No UUIDs from an article or any other fantasy UUIDs.

    Use this command to find out all device names and their UUIDs on your computer:

    ls -l /dev/disk/by-uuid/ | sort --key 11
    

    Depending on the number of the partitions the output may be long. Here’s mine, for example:

    ┌──[just]@[alexarc]:~$
    └─> ls -l /dev/disk/by-uuid/ | sort --key 11
    total 0
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 f55b8cff-cde2-46c2-8489-a9fc06206378 -> ../../sda1
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 09d3eba3-d093-4fd3-8bfd-5fecdc464786 -> ../../sda10
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 1bab8ea9-d9c3-48a8-9bb2-9958a63d03e7 -> ../../sda11
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 c2dcb34c-a739-457a-a5b0-f2c8753f5ba0 -> ../../sda12
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 49406132-a34c-43bd-88af-4c5df172787b -> ../../sda13
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 b0071485-8cbf-46a1-b788-97e32cf93a42 -> ../../sda14
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 6bceff92-95bf-4f87-8203-6670e3ab2b89 -> ../../sda15
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 f6703398-5373-4f2d-8ade-a97d858d8556 -> ../../sda16
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 43a8e719-33fc-4800-83ff-0bb5642062bc -> ../../sda2
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 ea4dbc8c-a7a1-4f7f-a1e8-f06d258cec46 -> ../../sda3
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 0d24fd75-462c-40f1-bef4-92f7e1be774d -> ../../sda5
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 585eb10c-fd69-4223-994f-f49e78762720 -> ../../sda6
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 a4fb41bf-62b9-46ef-a3f8-04fff389a1a4 -> ../../sda7
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 49dd8ced-ac45-4dfa-a624-271dab25ca92 -> ../../sda8
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 22d48484-0b4b-4fc5-bed7-e9b046bd6ff3 -> ../../sda9
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 3e10e775-9f5e-4e83-92a0-fbb8588a594c -> ../../sdb1
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 820c1493-5474-49a6-9957-2365af54db67 -> ../../sdb10
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 419d9e14-35be-4f9b-bcc4-24f44515d71a -> ../../sdb11
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 460cc433-f4b6-4536-a206-e0abec1c65a6 -> ../../sdb12
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 3559f30d-da94-4042-9639-20b81400f058 -> ../../sdb13
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 c7a649d9-b704-40fe-b6cb-24f6b7ce7e92 -> ../../sdb14
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 0f3b3652-4aee-4632-a4eb-54144e3e1aad -> ../../sdb15
    lrwxrwxrwx 1 root root 11 Oct  1 18:03 aaf53b63-05bd-44d5-adb6-21ff598a6170 -> ../../sdb16
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 d58c3b5d-e411-4be9-a72c-6548bfc09650 -> ../../sdb2
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 3176b48a-29a6-45d7-aa3a-b31e01dacec6 -> ../../sdb3
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 41fe487c-b321-4da6-8816-78b8939a833a -> ../../sdb5
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 a762f84f-094e-404a-9bd0-a2bf0fb37bea -> ../../sdb6
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 ca0828fd-aaf0-435f-bffa-aeef08b9f7ec -> ../../sdb7
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 8e7c6d64-14df-4563-9746-bb39c0764e31 -> ../../sdb8
    lrwxrwxrwx 1 root root 10 Oct  1 18:03 936b279c-8530-4e0c-b39a-80d4faf723b2 -> ../../sdb9
    ┌──[just]@[alexarc]:~$
    └─> 
    

    If you’re using Grub2 boot loader, remember to regenerate its config after modifying UUID. I do not use it, and can’t recall the command to do it. It is mentioned a zillion times in the forum.

    Not only. If UUID is changed, then initramfs must also be regenerated again. Both Grub 2 and initramfs must point to the / Antergos partition.

  • @just
    Ok, my devices UUID are:

    [[email protected] ~]$ ls -l /dev/disk/by-uuid/ | sort --key 11
    total 0
    lrwxrwxrwx 1 root root 10 out 1 12:04 18A8-60C0 -> ../../sda1
    lrwxrwxrwx 1 root root 10 out 1 12:04 12D7-0287 -> ../../sda2
    lrwxrwxrwx 1 root root 10 out 1 12:04 888AD8968AD8825C -> ../../sda4
    lrwxrwxrwx 1 root root 10 out 1 12:04 1628DCD628DCB5C9 -> ../../sda5
    lrwxrwxrwx 1 root root 10 out 1 12:04 4d9e7d7a-d31e-4795-80e4-96af41660856 -> ../../sda6
    lrwxrwxrwx 1 root root 10 out 1 12:04 3E08D3D608D38AF3 -> ../../sda7
    lrwxrwxrwx 1 root root 10 out 1 12:04 0107a434-5029-4cd3-b8bf-72bfb05d487e -> ../../sda8
    lrwxrwxrwx 1 root root 10 out 1 12:04 151459ea-b940-4dfa-b531-1581ed654b3b -> ../../sda9
    

    Antergos is installed at sda6. The UUID at the kernel parameters points to it.

    linux /boot/vmlinuz-linux root=UUID=4d9e7d7a-d31e-4795-80e4-96af41660856 rw quiet splash resume=UUID=0107a434-5029-4cd3-b8bf-72bfb05d487e
    

    You must use the UUID of the partition, where Antergos is installed.

    So it is

  • Some important info is missing from your post. In any case, solve each single problem is beyond my capabilities.

    UUID - or device name, or device label - in Grub 2 must point to the vmlinuz-linux and initrams-linux.img files, which boot an Arch system.

    These two files are always found in the /boot folder.

    The /boot folder is usually found in the / partition, unless you’ve choosen to install it into a separate boot partition.

    All boot loaders, Grub 2 included, must use the UUID of the partition, where the /boot folder resides. Stop.

    If the /boot folder is found in the / Antergos partition, then use UUID of the / partition.

    If the /boot folder is found in a separate partition, then use the UUID of this partition.

    Remember to regenerate Grub 2 config and initramfs, if UUID was changed.

    It’s that simple.

  • @just
    I understand what you are talking about.

    But the system looks all set. Both vmlinuz-linux and initrams-linux.img are in /boot folder, which is in /, which is the sd6, which UUID is pointed in GRUB.

    And I’ve regenerated both GRUB and and initramfs with:

    grub-mkconfig -o /boot/grub/grub.cfg
    mkinitcpio --preset linux
    

    I have not changed the UUID by any means. I think my previous post sounded like I did, but I didn’t. They are exactly the same prior installing plymouth.

    Looks like plymouth is working but it can’t fetch the theme to show it. All I see is this, no matter which theme I set. But again, it works fine restarting/shutting down.

    Thats odd.

    I really really appreciate the help. But i’m starting to think that my system is one of those from @joekamprad reply.

  • @alfatester I never used plymouth in Antergos, though I do it in other distros. But I just installed and configured plymouth in Antergos, to test your case.

    Plymouth works flawlessly in Antergos, without a problem. When the antergos theme is set, it displays those blue Antergos triangle in the center of the white-greyish screen background, with five fading in and out dots below it. The theme displayed by LiveMedia, for short.

    No problems with plymouth in Antergos here.

  • I’ve found the solution to my problem.

    All I had to do was add my kernel graphics driver under MODULES in mkinitcpio.conf.

    Now it’s working like intended.

Posts 12Views 361
Log in to reply