SteeMan Posted December 18, 2022 Share Posted December 18, 2022 I was doing some testing today on aml-s9xx-box builds and noticed that with meson64-current (6.0.13) kernels the boot logo is showing, but with meson64-edge (6.1.0) kernels it does not. I know there was a recent commit that probably is causing this, something about removing the old way of handling boot logos. So my question is, what needs to change to convert to the new way? I suspect it has something to do with the append line that the build process is inserting into the extlinux.conf file: append root=UUID=0ffde9aa-5a6a-4d6f-bbef-0d8daf439537 rw no_console_suspend c onsoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=boo tsplash.armbian 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted December 18, 2022 Share Posted December 18, 2022 1 hour ago, SteeMan said: So my question is, what needs to change to convert to the new way? Keeping kernel bootsplash is getting out of control ... it was disabled while we anyway moved to plymouth. Check here: https://github.com/armbian/build/pulls?q=is%3Apr+plymouth+ 0 Quote Link to comment Share on other sites More sharing options...
SteeMan Posted December 19, 2022 Author Share Posted December 19, 2022 @Igor Thanks for that info, I was able to track down what was the cause. I will have some additional questions when I get time to attempt a fix. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.