View previous topic :: View next topic |
Author |
Message |
FOSSilized_Daemon n00b
Joined: 08 Mar 2019 Posts: 20
|
Posted: Sun May 03, 2020 2:22 pm Post subject: Syslinux: Failed to load ldlinux.c32 |
|
|
I am trying to install Gentoo Linux on an old Toshiba so I can test and play around with different Gentoo things for when I get my next laptop. I followed through the handbook and everything, but keep having one issue. I use syslinux as my bootloader and really prefer it, but when I reboot I get the following error:
Code: |
Failed to load ldlinux.c32
Boot failed: please change disks and press a key to continue.
|
I have that module in /boot/syslinux and am using a very basic syslinux setup. When I setup up syslinux I did the following:
Code: |
# install syslinux
emerge --ask sys-boot/syslinux
# copy all needed .c32 files over
mkdir -p /boot/syslinux
cp /usr/share/syslinux/{reboot,poweroff,ldlinux,libutil,libcom32}.c32 /boot/syslinux
# install extlinux and MBR
extlinux --install /boot/syslinux
dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda
# get the kernel and initramfs version
kernelv=$(ls /boot/ | grep "vmlinuz-$release")
initramfsv=$(ls /boot/ | grep "initramfs-$release.img")
# add support for decrypting at boot and setup general settings by editing /boot/syslinux/syslinux.cfg
DEFAULT main
PROMPT 1
TIMEOUT 50
LABEL main
LINUX ../$kernelv
APPEND root=/dev/gentoolvm/root cryptdevice=UUID=$rootuuid:gentooluks rw auditd=1
INITRD ../$initramfsv
LABEL fallback
LINUX ../vmlinuz-fallback
APPEND root=/dev/gentoolvm/root cryptdevice=UUID=$rootuuid:gentooluks rw auditd=1
INITRD ../initramfs-fallback
LABEL reboot
COM32 reboot.c32
LABEL poweroff
COM32 poweroff.c32
|
I have no idea what I am doing wrong and am really confused. Could someone please help me understand how to fix this? Thank you for your time.
#### What I Have Tried
I was already told to run lld *.c32 in /boot/syslinux/, but it doesn't say I am missing any modules (as it shouldn't); however it does say the following:
[code]
lld: You don't have permissions to execute: reboot.c32
lld: You don't have permissions to execute: poweroff.c32
lld: You don't have permissions to execute: ldlinux.c32
lld: You don't have permissions to execute: libutil.c32
lld: You don't have permissions to execute: libcom32.c32
I am unsure what if anything I am supposed to do with those errors as I have never had to deal with this before when setting up syslinux. _________________ Arch LOL
Last edited by FOSSilized_Daemon on Sun May 03, 2020 4:26 pm; edited 1 time in total |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22695
|
Posted: Sun May 03, 2020 4:23 pm Post subject: |
|
|
The instructions say: Code: | and make sure the correct partition in set active. | You do not mention whether you did this, or checked that it had already been done. Which partition(s) are active on this device? I think you want to have exactly one partition marked as active, and it should be the one which contains the filesystem holding /boot. |
|
Back to top |
|
|
FOSSilized_Daemon n00b
Joined: 08 Mar 2019 Posts: 20
|
Posted: Sun May 03, 2020 4:29 pm Post subject: |
|
|
Hu wrote: | The instructions say: Code: | and make sure the correct partition in set active. | You do not mention whether you did this, or checked that it had already been done. Which partition(s) are active on this device? I think you want to have exactly one partition marked as active, and it should be the one which contains the filesystem holding /boot. |
I apologize for my confusion, but could you elaborate a little bit more? I set root and the UUID for it (as I am using lvm + LUKS). Are you refering to where I create the parition for /boot/? If so I have those steps below:
Code: |
# create paritions fdisk /dev/sda:
fdisk /dev/sda:
n # create a new physcial parition
p # choose primary
1 # select partition number 1
ENTER # select default sector
+512M # use 512M of disk space
a # flag bootable
n # create a new physcial parition
p # choose primary
2 # select partition number 2
ENTER # select default sector
ENTER # use the rest of the disk
t # select type
2 # parition 2
8e # set type to linux file system
w # write changes
# encrypt the linux filesystem
cryptsetup -v -c serpent-xts-plain64 -s 512 --hash whirlpool --iter-time 5000 --use-random luksFormat /dev/sda2
# open the linux filesystem
cryptsetup luksOpen /dev/sda2 gentooluks
# create lvm group on gentooluks
pvcreate /dev/mapper/gentooluks
vgcreate gentoolvm /dev/mapper/gentooluks
# create lvm partitions
lvcreate --name root -L 50G gentoolvm
lvcreate --name swap -L 2G gentoolvm
lvcreate --name home -l 100%FREE gentoolvm
# create filesystems
mkfs.ext4 -L boot /dev/sda1
mkfs.ext4 -L root /dev/gentoolvm/root
mkfs.ext4 -L home /dev/gentoolvm/home
mkswap /dev/gentoolvm/swap
|
_________________ Arch LOL |
|
Back to top |
|
|
cntrmx n00b
Joined: 01 Oct 2024 Posts: 1
|
|
Back to top |
|
|
bstaletic Guru
Joined: 05 Apr 2014 Posts: 375
|
Posted: Thu Nov 21, 2024 4:54 pm Post subject: |
|
|
Your /dev/sda1 is the /boot partition. In fdisk, when you p the disk, you should see something like this; Code: | Device Boot Start End Sectors Id Type Start-C/H/S End-C/H/S Attrs
/dev/sda1 * 2048 104859469 104857422 83 Linux 0/32/33 1023/254/63 80
/dev/sda2 104859648 488397167 383537520 83 Linux 383/53/55 705/80/63
|
Notice the asterisk in the Boot column - that is the active partition marker.
With MBR/legacy boot, your boot partition needs to be marked as active. |
|
Back to top |
|
|
|