Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

20.08 Orange Pi 4 - Kernel Enabled Bootsplash

Featured Replies

@Igor

Kernel enabled Bootsplash works great on the recent 20.08 on Orange Pi 4. However there is a delay of around 20 - 30 seconds before this Bootsplash comes up. Is is possible to enable bootsplash on u-boot also on this image?

 

I built a custom image 20.08-trunk with option "Kernel enabled bootsplash' disabled however could not see u-boot bootspalsh on this image.

 

-Rajesh

 

4 hours ago, Rajesh said:

@Igor

 

- is this a critical issue? No.

- does this issue requires my personal attention? No.

- will community significantly benefit by solving this problem? No

- are we friends? No

 

4 hours ago, Rajesh said:

Is is possible to enable bootsplash on u-boot also on this image?


(Probably) not developed / supported and there are no plans nor resources to develop something like that if you came up with an idea and you don't provide money that we can hire people. Open ideas here https://forum.armbian.com/forum/38-feature-requests/ and please don't tag my name since I don't have time to read wishes. Which mean I also have no time to do anything about.

 

4 hours ago, Rajesh said:

I built a custom image 20.08-trunk with option "Kernel enabled bootsplash' disabled however could not see u-boot bootspalsh on this image

 

Enabled at desktop only:

https://github.com/armbian/build/blob/master/config/boards/orangepi4.conf#L8

Explanation:
https://github.com/armbian/build/blob/master/config/boards/README.md

  • Author
On 8/26/2020 at 6:16 PM, Igor said:

 

- is this a critical issue? No.

- does this issue requires my personal attention? No.

- will community significantly benefit by solving this problem? No

- are we friends? No

 


(Probably) not developed / supported and there are no plans nor resources to develop something like that if you came up with an idea and you don't provide money that we can hire people. Open ideas here https://forum.armbian.com/forum/38-feature-requests/ and please don't tag my name since I don't have time to read wishes. Which mean I also have no time to do anything about.

 

 

Enabled at desktop only:

https://github.com/armbian/build/blob/master/config/boards/orangepi4.conf#L8

Explanation:
https://github.com/armbian/build/blob/master/config/boards/README.md

 

I am not working for on any commercial or for profit project. Looks like you have some very good thing going on here so this is just a feedback. Please ignore if you think it is not important.

There are no expectations that this will be fixed. 

 

I tried buster desktop. I am not able to see the boot logo. Verified the config file you have listed and they are as expected.

Plymouth also does not work. May be it just one of those orange pi thing.  It is just that looking at a blank screen for 20-30 seconds when device comes up is odd.

I believe kernel enabled bootsplash has been abandoned but not too sure.

 

-R

 

so armbian uses the bootslpash.armbian file in /lib/firmware/ for the boot logo....how is this generated if we want to change it?

it is not a bootsplash problem

 

at boot the kernel searches for device and activates them and if a device takes time to get seen by the kernel the kernel get a amount of time to wait

so when a device for example my usb3 got called before the bootsplash there is no bootsplash because kernel is waiting for the usb before he wants to put something on screen.

 

you can see that effect if you boot through a console then you see the kernel spit out messages sometimes fast sometimes slower

and it happens even more when you reboot but that is more less nowdays because the drivers are getting better

 

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.