RPi2 splash image

Raspberry Pi 2

RPi2 splash image

Postby prajwal » Tue Aug 04, 2015 2:26 pm

Hi

I wanted to change the splash image on bootup of the RPi2. So I tried to follow the instructions on the following forum discussion:
viewtopic.php?f=64&t=8537&p=45725&hilit=splash#p45725

and its previous linked forum discussion:
viewtopic.php?f=31&t=7133

But the files & folders that are referred to during the discussions such as init, mkinitcpio AND commands such as initramfs are not available in my system. In the new initcpio folder there are 3 sub-folders called hook, udev and istall.

I know that Arch Linux ARM is now using systemd for the controls.

Any idea on how I can change the splash screen on boot in the latest Arch system (from Jul 2015).
Below is the output of uname -a on my system

Thanks in advance for any help / guidance.

$this->bbcode_second_pass_code('', '
[root@Mantis-system-expt Plymouth-lite-master]# uname -a
Linux Mantis-system-expt 4.0.9-2-ARCH #1 SMP PREEMPT Tue Jul 28 19:06:38 MDT 2015 armv7l GNU/Linux
')
Last edited by prajwal on Tue Aug 04, 2015 6:59 pm, edited 1 time in total.
prajwal
 
Posts: 8
Joined: Fri Jul 31, 2015 6:26 am

Re: RPi2 splash image

Postby WarheadsSE » Tue Aug 04, 2015 2:54 pm

$this->bbcode_second_pass_quote('', 'a')rchARM

Arch Linux ARM, or even ALARM. We've got legal permissions to use the name, but it has to be correct.

Everything you need for using an initrd is attainable through the repos. And making use of an initrd is no different than on other platforms other than where you tell the bootloader to use it.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: RPi2 splash image

Postby prajwal » Tue Aug 04, 2015 7:00 pm

Hi.

Thanks for the correction. it is now corrected in my first post to Arch Linux ARM. Sorry about that.

Thanks for the inputs about initd.
prajwal
 
Posts: 8
Joined: Fri Jul 31, 2015 6:26 am

Re: RPi2 splash image

Postby prajwal » Wed Aug 05, 2015 5:46 pm

Hello Again.

I am still unable to get the boot splash. I followed the steps given in
viewtopic.php?f=31&t=7133

but am getting just a black screen and no splash image.
More specifically, I followed the following steps:

    I downloaded the patched version of the plymouth-lite package from the link in page 2 of the above linked discussion. That is i downloaded the package in the following link:
    https://github.com/T4d3o/Plymouth-lite

    I extracted and ran ./configure && make. This setup the ply-image in my /usr/bin

    I modified mkinitcpio.conf, and /usr/lib/initcpio/init files

    I ran the mkinitcpio command

    I modified the /boot/config.txt and /boot/cmdline.txt

I have also downloaded the "systemd" files from the link in page 1 of the forum discussion (i.e. from https://github.com/embedded-webruntime/plymouth-lite), but, now I am not entirely sure as to what is required to enable the plymouth-lite-start.service.

I tried copying only the plymouth-lite-start.service file to /usr/share/systemd/system, and then tried to enable it using systemctl enable. But I got the following output:

$this->bbcode_second_pass_code('', '
[root@Mantis-system-expt system]# systemctl enable /usr/lib/systemd/system/plymouth-lite-start.service
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
')

Any idea where I am going wrong. Since mashley said that the instructions worked for him on a Raspberry Pi 2, I think I am missing some step here. Any suggestions on how I can get the splash image on the screen?
prajwal
 
Posts: 8
Joined: Fri Jul 31, 2015 6:26 am

Re: RPi2 splash image

Postby prajwal » Fri Aug 07, 2015 7:03 am

OK. The problem is resolved. I was missing the correct linking of the plymouth-lite-start.service. The service has to be linked in the sysinit.target.wants folder.

An updated and detailed guide has been included along with all the other files in the following repository:

https://github.com/T4d3o/Plymouth-lite

Many thanks to T4d3o for the guide and for the patched package.

To summarize:

i. Download and install the patched version of plymouth-lite from the GIT repository link provided above in this comment.
ii. Extract the package and run configure & make commands to setup ply-image.
iii. Modify the /etc/mkinitcpio.conf and the /usr/lib/initcpio/init files as detailed in the guide in the repository.
iv. Run the mkinitcpio command with the correct options
v. Modify the /boot/config.txt and /boot/cmdline/txt files
vi. Copy the plymouth-lite-start.service to /usr/lib/systemd/system folder.
vii. Create the reuqisite symbolic link in the /usr/lib/systemd/system/sysinit.target.wants sub-folder.

The exact commands to be executed are detialed in the guide in the repository.

Thanks
Prajwal
prajwal
 
Posts: 8
Joined: Fri Jul 31, 2015 6:26 am


Return to Broadcom

Who is online

Users browsing this forum: No registered users and 7 guests