Hi there, I despise complexity and Grub has been giving me headaches on Voidlinux.. https://www.reddit.com/r/voidlinux/comments/gk5h5c/everytime_i_update_void_i_need_to_manually/ I've switched to Syslinux, but I have the following queries. ??sda1 vfat FAT32 D91B-36F7 190.7M 61% /boot ??sda2 ext4 1.0 0dd25845-8fa5-41e9-b82c-c63c27cf5d18 49.5G 50% / When I do a linux update, the Void package drops in a new files that look like vmlinuz-5.6.6_1/initramfs-5.6.6_1.img. How does one generate the /boot/EFI/syslinux/syslinux.cfg ? Since /boot is FAT32, no symlinks can be used. Ideally syslinux could just allow me to browse and select the kernel/initrd, but that doesn't appear possible to do. Kind regards,
On Thu, May 21, 2020 at 11:53 PM Kai Hendry via Syslinux < syslinux at syslinux.org> wrote:> > When I do a linux update, the Void package drops in a new files that look > like vmlinuz-5.6.6_1/initramfs-5.6.6_1.img. How does one generate the > /boot/EFI/syslinux/syslinux.cfg ? >I'm not familiar with your distribution, but if it doesn't provide scripts to generate the syslinnux.cfg, there is probably a way to provide your own. On my systemd-based Fedora system, I can drop scripts in /etc/kernel/install.d that will then get called whenever kernels are added or removed. Those scripts can generate or update the syslinux.cfg file on /boot. The version of the kernel being added or removed is provided as a parameter to the scripts.> > Since /boot is FAT32, no symlinks can be used. > > Ideally syslinux could just allow me to browse and select the > kernel/initrd, but that doesn't appear possible to do. >There is something called the "Boot Loader Specification" that adds support for drop-in config files on /boot. With the the drop-in support, new kernels just appear on the boot menu without having to modify syslinux.cfg. Unfortunately, the patch doesn't appear to have been approved/pulled into the upstream code base yet. If you want that, you would have to compile your own copy of syslinux with the patch applied.
On Fri, 22 May 2020, Kai Hendry via Syslinux wrote:> I despise complexity and Grub has been giving me headaches on Voidlinux.. > > https://www.reddit.com/r/voidlinux/comments/gk5h5c/everytime_i_update_void_i_need_to_manually/ > > I've switched to Syslinux, but I have the following queries. > > ??sda1 vfat FAT32 D91B-36F7 190.7M 61% /boot > ??sda2 ext4 1.0 0dd25845-8fa5-41e9-b82c-c63c27cf5d18 49.5G 50% / > > > When I do a linux update, the Void package drops in a new files that look like vmlinuz-5.6.6_1/initramfs-5.6.6_1.img. How does one generate the /boot/EFI/syslinux/syslinux.cfg ? > > Since /boot is FAT32, no symlinks can be used. > > Ideally syslinux could just allow me to browse and select the kernel/initrd, but that doesn't appear possible to do.I think maybe what you want is this: http://sprunge.us/CJGUA6 . I use something similar on my non-UEFI Void systems, which I also boot using syslinux.
Thanks James, That script looks like it will work. Thought the next thing that really puzzles me is efibootmgr. Is it's job to boot syslinux or replace it? hendry at knuckles /etc/kernel.d $ sudo efibootmgr BootCurrent: 000B Timeout: 6 seconds BootOrder: 0004,000B,0005,0001,0002,0003,0000,0006 Boot0000* Windows Boot Manager Boot0001* Linux Boot Manager Boot0002* ubuntu Boot0003* void_grub Boot0004* SATA : PORT 0 : Samsung SSD 850 EVO 120GB : PART 0 : Boot Drive Boot0005* LAN : Realtek PXE B03 D00 Boot0006* Void Linux with kernel 5.6 Boot000B* Syslinux https://www.reddit.com/r/voidlinux/comments/gp09un/efibootmgr_mount_sysfirmwareefiefivars_wrong/ Sidenote: "Boot Loader Specification" looks interesting. I see mention of it back in 2014... haha https://www.syslinux.org/archives/2014-November/022775.html Kind regards,
Reasonably Related Threads
- Voidlinux integration
- [PATCH] customize: password: use SHA-512 on Void Linux and Arch Linux
- Having trouble getting started on writing a WDC 65816 backend
- [PATCH] inspect: recognize the Kali Linux distribution (RHBZ#1544227)
- [PATCH 0/5] Small inspection improvements