On Tue, Mar 13, 2018 at 10:14 AM, Arjen Balfoort <arjenbalfo...@solydxk.com> wrote:
> I'm currently building a RPi3 version of SolydX. For the Xfce desktop to > successfully load I need to change the boot parameters. > > cmdline.txt: > console=tty0 console=ttyS1,115200 root=/dev/mmcblk0p2 rw elevator=deadline > fsck.repair=yes net.ifnames=0 rootwait cma=256M quiet splash loglevel=0 > vt.global_cursor_default=0 plymouth.ignore-serial-consoles > > config.txt: > arm_control=0x200 > kernel=vmlinuz-4.14.0-3-arm64 > initramfs initrd.img-4.14.0-3-arm64 followkernel > disable_splash=1 > enable_uart=1 > device_tree=bcm2837-rpi-3-b.dtb > gpu_mem=16 > dtoverlay=pi3-disable-bt > dtparam=audio=on > > Note: I needed the "cma=256M" in cmdline.txt. Any lower Xfce would freeze > on login. > > As the OP mentioned, these files are now overwritten with each initramfs > update. I tried to create a hook script for initramfs-tools to restore > backup files to cmdline.txt and config.txt but so far I didn't succeed in > that. > > In a desktop environment it regularly happens that initramfs is updated > and overwriting these files always results in a frozen desktop and that is > not something I can trust our users with. > > Is there a way to prevent this behavior or does anybody know how to run a > script after initramfs has been updated? > I think we should rename our hook from “raspi3-firmware” to “50raspi3-firmware”. update-initramfs uses run-parts(8) to invoke hooks, so you could then ship a hook with a higher number which would be guaranteed to run after the raspi3-firmware hook. Let me know if that sounds good, and I’ll prepare a package upload. > > _______________________________________________ > Pkg-raspi-maintainers mailing list > pkg-raspi-maintain...@lists.alioth.debian.org > https://lists.alioth.debian.org/mailman/listinfo/pkg-raspi-maintainers > -- Best regards, Michael