[syslinux] Fail to set up UEFI syslinux on ArchLinux USB Flash Drive

alex lupu alupu01 at gmail.com
Wed Mar 18 20:31:23 PDT 2015

On Wed, Mar 18, 2015 at 8:06 AM, Ferenc Wagner <wferi at niif.hu> wrote:

> alex lupu <alupu01 at gmail.com> writes:
> > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote:
> >> alex lupu via Syslinux <syslinux at zytor.com> writes:
> >>​>​ Obviously it would work IF I moved the vmlinuz
> >>> and initramfs ​files from /dev/sdd2 to /dev/sdd1.
> >>> I figured that would probably be considered non-standard Arch
> >>
> >> The standard solution is to have your boot partition (sdd1) mounted as
> >> /boot in your Linux system, and then your kernel and initramfs files are
> >> automatically put (and updated) on the right partition.  Then you can
> >> refer to them as /vmlinuz and /initramfs from the Syslinux config (where
> >> sdd1 is "mounted" at /)
> >

> Move everything belonging to your OS (like vmlinuz*, initrd*,
> config*, System.map* etc.) from your current /boot into your current
> /boot/efi, so that after changing the mount point of sdd1 everything
> will be in its usual place again.  Then change your Syslinux config:
> drop /EFI from your LINUX and INITRD paths, so that they look like
> LINUX /vmlinuz...
> INITRD /vmlinuz...
> as these files are now in the root of sdd1.

​Hi Feri,​

That's exactly what I've had all along (and working fine as I said)
i.e., vmlinuz and initram on _sdd1_ in
​the ​
/EFI/ directory.

BTW, credit goes to Ady who said in a previous post,
"... So, your "root" can still be pointing to sdd2; as long as the
"vmlinuz-linux" and "initramfs-linux.img" files are located in sdd1
directly under the "EFI" directory."

Except, you're suggesting I move'em up (so to speak)
 / of sdd1
​ from /EFI/​
(and changing the 'syslinux.cfg' to reflect
 new file placement).

I suppose you favor this overall change so that

> ​t​
> his way your OS and
> Syslinux will find the same files via different paths.  Upgrading your
> kernel will place all the files into the right place.  If your OS has
> bootloader integration magic, it may even provide the corresponding
> Syslinux config.  Or you can generate it at boot time via something like
> automenu.lua in current Syslinux.

I'm for simplicity
​in getting my feet wet in Arch ​
(I don't aim that high in life, like using 'automenu.lua'
​, etc.
, your way or mine do not change the basic law of
​ ​
​which states ​
that currently Syslinux can only handle one partition (sdd1 in our case),
as I
​was lamenting​
 in a previous post.

​Thanks and best wishes,
-- Alex​

More information about the Syslinux mailing list