Post by Peter Chant Post by jrg
Thanks, Pete, but I've looked at syslinux. I want to have kernel
choices once I get 1 to work. I think the problem may be in the VFAT
format linking to /boot/efi. After eliloconfig, /sda1 contains 3 items
- ?efl ?grub and *.keep, all empty. There is a broken link in /boot,
which is where elilo put the kernel files and linked config-huge-4.14.44
to /boot/efl. Only config is config-huge-4.14.44.x64 - something here
is all wet. I remember reading somewhere that linux has problems
linking to VFAT files - anyone know of any truth in this?
Hmm. Since I upgraded at the weekend I now have a UEFI machine, but it
seems to support legacy boot. However, my syslinux workaround for
issues with my last machine basically just worked for this one.
I'll probably need to look into UEFI - even getting legacy boot to work
on my mother's machine several years ago was a pain.
This efi crap is driving me nutso. Best I can say is I don't feel like
the Lone Ranger after bumbling through this. Just the variations in
file tree structures offered up all over is mind boggling. I d/l'd a
new install iso for current and the install just stops midway through
with no real reason given, Also, I've partitioned and formatted my disk
with the appropriate fs - vfat for efi, swap, ext4 for filesystem (/) -
and the installer can't find any "linux filesystems" and then formats
efi as vfat 9already done) and moves on.
back to linux questions...