Failed to load ldlinux c32 как исправить linux mint

Hi,

I have tried to boot from a DVD with Linux Mint 18 MATE, but without success. Isolinux starts up, but immediately stops again with a message saying «Failed to load ldlinux.c32».

Here is the sequence of steps that I have taken:

• Downloaded the ISO image for Linux Mint 18 «Sarah» — MATE (32-bit) and verified the image exactly as specified in https://linuxmint.com/verify.php
• Burned the ISO image to a DVD (type DVD+R) with K3B’s action «Burn Image»
• Verified the DVD: I can mount it and the file system looks OK
• Tried to boot: Started the PC, inserted the DVD, selected the CD/DVD drive in the BIOS boot menu
• Result: Isolinux starts up, but immediately stops with message «Failed to load ldlinux.c32». Always reproducible, also on another PC.

The reason I am using a DVD instead of an USB device as boot medium is that the BIOS of this old PC from the year 2005 is uncapable to boot from USB.

Alternatively, I tried the Plop Boot Manager at https://www.plop.at/en/bootmanager/index.html: Burned its ISO on a CD and booted from that, in the intent to have it boot from a USB stick which has LM 17.2 on it (and which itself already allowed to boot several machines). Result here: Plop Boot Manager starts off, I select «USB», but then after the message «device connected», the process hangs. (I suspect missing USB drivers could be the culprit. Tried the same on a recent notebook, where Plop Boot Manager succeeded in actually starting the USB boot process, which then failed with an error.)

What can I do to obtain a LM 18 MATE DVD that I can boot from?

I looked everywhere I could for a solution, but only found that the message I got might have to do with changes in isolinux, yet there was nothing specific to the LM 18 image.

Do I need to modify the files in the DVD ISO image before burning it? If so, in which way?

Yves

austin.texas wrote:Which linux do you currently have installed?

I am not sure why you are asking this.

1) The old PC where I want to boot (and maybe then install) LM 18 MATE currently has LM 13 MATE. This is why I want to move to a more recent LTS version. I think using the Update Manager to upgrade «through» all of the LM versions between 13 and 18 is out of discussion. Hence, somehow I need to re-install LM from scratch on that PC.

2) The notebook on which I burnt the LM 18 MATE (32bit) ISO to a DVD with K3B runs LM 17.2 (64bit). But I believe that does not make a difference, does it?

Yves

Cosmo. wrote:There is no need to modify the files on the ISO image. As you noted that this is a not quite recent pc, it might be, that the kernel of LM 18 or other hardware related components to not work with your hardware. Download Mint 17 or LM 17.1 and try to boot from it.

Thank you Cosmo, I will try this.

PS. Sorry for answering so late. I checked every day if my original post was already approved, but couldn’t find it at the top of the list in the board, so I thought it hadn’t been approved yet.

Yves

yvesforkl wrote:

austin.texas wrote:Which linux do you currently have installed?

I am not sure why you are asking this.

First, because the more information you provide, the easier it might be to find a solution.
Second, because the various distributions or versions have different capabilities and/or deficiencies.

Is your CD/DVD drive SATA or IDE?
PLOP does not work with SATA cdrom drives.
The SuperGrub2 CD will boot an .iso file from a flash drive, and does work with SATA.

You may be having a DVD problem like my old ThinkPad T23 did. One batch of DVDs would burn and verify the Mint 18 iso correctly on the computer I use for that, but they could not complete the installation in the T23 drive. I got a message window stating the installer crashed. This happened with three DVDs and two desktop versions.

With a different brand of DVDs, burned with the same procedure, the installation worked. Try running the Integrity Check on the disk before starting installation.

These old DVD drives seem to be touchy about reading a given disc. If you have a different brand available, it may be worth trying.

yvesforkl wrote:Result here: Plop Boot Manager starts off, I select «USB», but then after the message «device connected», the process hangs.

austin.texas wrote:Is your CD/DVD drive SATA or IDE?
PLOP does not work with SATA cdrom drives.

Wasn’t aware that Plop doesn’t work with SATA drives, so I just tested it out. Sure enough, austin.texas is correct — it got stuck with same «Device connected» message that you got yvesforkl.

hrmcrm wrote:You may be having a DVD problem like my old ThinkPad T23 did. One batch of DVDs would burn and verify the Mint 18 iso correctly on the computer I use for that, but they could not complete the installation in the T23 drive. I got a message window stating the installer crashed. This happened with three DVDs and two desktop versions.

With a different brand of DVDs, burned with the same procedure, the installation worked. Try running the Integrity Check on the disk before starting installation.

This is a good suggestion. Have seen situations like this before on the forums where one brand of dvd would fail and a different brand would work. (Has happened with usb sticks too.)

yvesforkl wrote:The reason I am using a DVD instead of an USB device as boot medium is that the BIOS of this old PC from the year 2005 is uncapable to boot from USB.

Are you sure about that? Did you have the bootable usb stick plugged-in before you booted the computer? Sometimes the Bios boot menu won’t show option to boot from usb if there is no bootable usb plugged-in on power-up. Also, the option may only show in the per-session boot menu and not in the main Bios settings menu. Most computers will have one key to hit to get into the main Bios settings and another key to invoke the per-session boot menu. Did you try one way, or both to boot the usb?

@austin.texas,
First, thanks for info on Plop not working with SATA cd/dvd drives. Second, I have a question about your suggestion to use SuperGrub2 cd to boot the iso from a usb. I’ve never used that before and am curious — plus I think OP may be wondering same thing as me about how to do it.

Do you just do a simple copy of iso file to the usb rather than burn the iso image to the usb (using something like UNetbootin or the dd command)? I’m guessing that you mean to just copy the iso and then direct SuperGrub2 to boot it. Is that right?

PLOP does not work with SATA drives. Read item #8 on the PLOP FAQ page.
https://www.plop.at/en/bootmanager/faq.html#faq8

For booting an .iso file from a flash drive using SuperGrub2:
Download the SuperGrub2 .iso and burn it to a CD
http://www.supergrubdisk.org
Connect a usb flash drive with fat32 format (or ext2), and make a folder named boot-isos. The exact name boot-isos is important.
Copy the Mint .iso file that you downloaded into the boot-isos folder on the flash drive.
Boot the computer with the SuperGrub2 CD.
Chose «Boot Manually» from the first menu,

then «»Bootable iso’s».
The program will search all of your drives, looking for any boot-isos folder. It will find the Mint .iso file on the flash drive, and create a menu which will allow you to boot the .iso, just like booting a DVD.
It is a slow process to search your drives and build that menu, so be patient.

Tutorial and Troubleshooting with SuperGRUB2:
http://www.supergrubdisk.org/wiki/SuperGRUB2Disk
http://www.supergrubdisk.org/wiki/Boot_Problems

austin.texas wrote:For booting an .iso file from a flash drive using SuperGrub2:
Download the SuperGrub2 .iso and burn it to a CD
http://www.supergrubdisk.org
Connect a usb flash drive with fat32 format (or ext2), and make a folder named boot-isos. The exact name boot-isos is important.
Copy the Mint .iso file that you downloaded into the boot-isos folder on the flash drive.
Boot the computer with the SuperGrub2 CD.
Chose «Boot Manually» from the first menu,then «»Bootable iso’s».
The program will search all of your drives, looking for any boot-isos folder. It will find the Mint .iso file on the flash drive, and create a menu which will allow you to boot the .iso, just like booting a DVD.
It is a slow process to search your drives and build that menu, so be patient.

Super GRUB2 Disk worked to start a live session from a Mint 18 iso on the hard drive two machines, but it did not find the iso on a fat32 USB flash drive. On both machines, I booted Super GRUB2 Disk from a USB flash drive. It seemed to run correctly, but did not find the option to boot an iso on another USB flash drive in a boot-isos folder. When I started a normal session and dragged the boot-isos folder (exactly the same name) to the hard drive, booting Super GRUB2 Disk and following your procedure offered to boot the iso, then correctly started a live session. This was with Mint 18 KDE 64-bit on one machine, and Mint 18 MATE 32-bit on another.

If OP cannot boot an iso from a USB flash drive with Super GRUB2 Disk, and has room on the hard drive for the iso, this would be a good alternative.

hrmcrm wrote:If OP cannot boot an iso from a USB flash drive with Super GRUB2 Disk, and has room on the hard drive for the iso, this would be a good alternative.

Without any doubt, booting the .iso when it is on the hard drive is faster, and many times easier than placing the .iso on a flash drive. However, that creates some minor problems when it comes time to install.
For starters, the partition that the .iso is on is mounted. That is obvious, because you are using the .iso as your live operating system. The installation program will pop up a warning that you have mounted partitions, asking if you want to unmount them. You have to say «No». So right off the bat, you have one partition on the hard drive that you cannot install to or alter. And the next logical conclusion is that «Use entire disk» is no longer an option.
If you have created your root, swap, and /home partitions previously with Gparted, you can proceed and install to those partitions.
However, if you use the installation program to create your partitions, the installation will fail, because one necessary step in creating those partitions is to rewrite the partition table. That is not possible with one partition mounted.
Now you understand why I suggested putting the .iso on a flash drive.

@austin.texas,
Thanks for pointing out the negatives of installing with an .iso on the hard drive, and offering work-arounds for each of them.

I did more testing and found why SuperGrub2 did not find the .iso on a USB flash drive. I had only the SuperGrub2 flash drive plugged in when I powered on the system and selected the boot source. I plugged in the other USB flash drive containing the .iso at that point, before starting SuperGrub2. That made the second USB flash drive unavailable.

When both USB flash drives were plugged in when the system powered on, SuperGrub2 found the .iso on the second USB flash drive and booted it into a live Mint session.

This is a very useful tool. Glad you mentioned it.
Thanks,

Thank you very much for your help. I proceeded exactly as you recommended: viewtopic.php?f=46&t=231064#p1224805

However, after I had booted SuperGrub2 from CD, it was not able to detect the ISO I had put in directory /boot-isos on the USB flash drive, i.e. the «Boot-isos» menu had no entries in it.

I have tried it with all 4 USB slots (AFAIK that machine has 2 different USB controllers), always with the same result. Additionally, for each of the 4 slots, SuperGrub2’s partition listing did include everything (HDD, CD, even floppy disk), but nothing from the USB flash drive.

So I suppose it could rather be a problem with missing USB drivers (which could have tripped up Plop, too).

At that point, I see no point in insisting to boot from USB on that machine (even indirectly).

I know that I still have the option to place the ISO on the HDD and boot from there (with all caveats, as having to partition beforehand due to the inability to unmount for partitioning, and not being able to use the disk space taken up by the ISO earlier than when the installation is completed).

In that situation, however, I rather give up on the idea of using that old (and noisy) computer and will buy me a new, silent Mintbox…

Thanks again to all of you for your help in this thread. (BTW, neither the BIOS menus nor the boot menu had the option to boot directly from USB.)

Yves

I’m trying to put Ubuntu on my desktop. Right now, it and my laptop are running Manjaro 3.18. I’ve been using Unetbootin to create the live USB on my laptop. I’ve tried several different versions of Ubuntu, as well as a couple other distros. I’ve removed and reinstalled Unetbootin a few times as well. I’ve reformatted the USB drive each time between tries (FAT32 normally, but I tried ext4 once just to see if anything different would happen). I’ve used this USB drive many times before for this same purpose. No matter what I try, I get the error:

Failed to load ldlinux.c32
Boot Failed: Press a key to retry...

If there’s any other information that would help, let me know.

asked Mar 27, 2015 at 10:56

Just came across the same problem. I thought I would share what worked for me for future visitors.

Turns out I had an outdated version of the Rufus software used to create the bootable drive.

I updated the software and that solved the problem.

answered Jul 30, 2016 at 18:29

answered Mar 27, 2015 at 20:49

I faced the same issue when trying to install Fedora 22 from a USB loaded with the DVD image. It turns out the DVD image was corrupted. I downloaded a second image and diff showed that the two images were different. Indeed, I was able to boot from the second image with no problem.

I had the same issue turns out it was the flash drive I was using . Was able to try on another flash drive and everything worked fine.Hope it helps.

I had exactly the same issue because of the iso using older Ubuntu mount. Rufus was able to detect and update it and now the iso in the usb is working fine. I am pretty sure this can fix your issue.

forbi

Member

Registered: 2013-12-21

Posts: 45

[Solved] Syslinux Failed to load ldlinux.c32

[root@archiso /]# syslinux-install_update -iam
Syslinux BIOS install successful
Boot Flag Set - /dev/sda1
Installed MBR (/usr/lib/syslinux/bios/mbr.bin) to /dev/sda

[root@archiso /]# ls -l /boot/syslinux/
total 2112
-rw-r--r-- 1 root root       0 Aug  4 18:41 SYSLINUX_AUTOUPDATE
-rw-r--r-- 1 root root    1596 Aug  4 18:41 cat.c32
-rw-r--r-- 1 root root   24716 Aug  4 18:41 chain.c32
-rw-r--r-- 1 root root    1228 Aug  4 18:41 cmd.c32
-rw-r--r-- 1 root root    3660 Aug  4 18:41 cmenu.c32
-rw-r--r-- 1 root root    1464 Aug  4 18:41 config.c32
-rw-r--r-- 1 root root    4184 Aug  4 18:41 cptime.c32
-rw-r--r-- 1 root root    4480 Aug  4 18:41 cpu.c32
-rw-r--r-- 1 root root    1748 Aug  4 18:41 cpuid.c32
-rw-r--r-- 1 root root    2748 Aug  4 18:41 cpuidtest.c32
-rw-r--r-- 1 root root    1568 Aug  4 18:41 debug.c32
-rw-r--r-- 1 root root    4040 Aug  4 18:41 dhcp.c32
-rw-r--r-- 1 root root    1988 Aug  4 18:41 disk.c32
-rw-r--r-- 1 root root    8660 Aug  4 18:41 dmi.c32
-rw-r--r-- 1 root root   11928 Aug  4 18:41 dmitest.c32
-rw-r--r-- 1 root root    3232 Aug  4 18:41 elf.c32
-rw-r--r-- 1 root root    2716 Aug  4 18:41 ethersel.c32
-rw-r--r-- 1 root root   10436 Aug  4 18:41 gfxboot.c32
-rw-r--r-- 1 root root    1576 Aug  4 18:41 gpxecmd.c32
-rw-r--r-- 1 root root  165464 Aug  4 18:41 hdt.c32
-rw-r--r-- 1 root root    3704 Aug  4 18:41 hexdump.c32
-rw-r--r-- 1 root root    1804 Aug  4 18:41 host.c32
-rw-r--r-- 1 root root    4120 Aug  4 18:41 ifcpu.c32
-rw-r--r-- 1 root root    1720 Aug  4 18:41 ifcpu64.c32
-rw-r--r-- 1 root root    4260 Aug  4 18:41 ifmemdsk.c32
-rw-r--r-- 1 root root    1872 Aug  4 18:41 ifplop.c32
-rw-r--r-- 1 root root    1648 Aug  4 18:41 kbdmap.c32
-rw-r--r-- 1 root root    4896 Aug  4 18:41 kontron_wdt.c32
-rw-r--r-- 1 root root  116368 Aug  4 18:41 ldlinux.c32
-r--r--r-- 1 root root   60928 Aug  4 18:41 ldlinux.sys
-rw-r--r-- 1 root root    5076 Aug  4 18:41 lfs.c32
-rw-r--r-- 1 root root  182532 Aug  4 18:41 libcom32.c32
-rw-r--r-- 1 root root   66744 Aug  4 18:41 libgpl.c32
-rw-r--r-- 1 root root  101840 Aug  4 18:41 liblua.c32
-rw-r--r-- 1 root root   24172 Aug  4 18:41 libmenu.c32
-rw-r--r-- 1 root root   23672 Aug  4 18:41 libutil.c32
-rw-r--r-- 1 root root    4700 Aug  4 18:41 linux.c32
-rw-r--r-- 1 root root    2960 Aug  4 18:41 ls.c32
-rw-r--r-- 1 root root    6820 Aug  4 18:41 lua.c32
-rw-r--r-- 1 root root   10200 Aug  4 18:41 mboot.c32
-rw-r--r-- 1 root root    2452 Aug  4 18:41 meminfo.c32
-rw-r--r-- 1 root root   26084 Aug  4 18:41 menu.c32
-rw-r--r-- 1 root root    3336 Aug  4 18:41 pci.c32
-rw-r--r-- 1 root root 1011638 Aug  4 18:41 pci.ids
-rw-r--r-- 1 root root    3460 Aug  4 18:41 pcitest.c32
-rw-r--r-- 1 root root    2956 Aug  4 18:41 pmload.c32
-rw-r--r-- 1 root root    1640 Aug  4 18:41 poweroff.c32
-rw-r--r-- 1 root root    3116 Aug  4 18:41 prdhcp.c32
-rw-r--r-- 1 root root    1476 Aug  4 18:41 pwd.c32
-rw-r--r-- 1 root root   12356 Aug  4 18:41 pxechn.c32
-rw-r--r-- 1 root root    1356 Aug  4 18:41 reboot.c32
-rw-r--r-- 1 root root   13792 Aug  4 18:41 rosh.c32
-rw-r--r-- 1 root root    1608 Aug  4 18:41 sanboot.c32
-rw-r--r-- 1 root root    3148 Aug  4 18:41 sdi.c32
-rw-r--r-- 1 root root   15428 Aug  4 18:41 sysdump.c32
-rw-r--r-- 1 root root    7544 Aug  4 18:41 syslinux.c32
-rw-r--r-- 1 root root    2513 Aug  4 18:10 syslinux.cfg
-rw-r--r-- 1 root root    3068 Aug  4 18:41 vesa.c32
-rw-r--r-- 1 root root    2180 Aug  4 18:41 vesainfo.c32
-rw-r--r-- 1 root root   26632 Aug  4 18:41 vesamenu.c32
-rw-r--r-- 1 root root    1840 Aug  4 18:41 vpdtest.c32
-rw-r--r-- 1 root root    2460 Aug  4 18:41 whichsys.c32
-rw-r--r-- 1 root root    3528 Aug  4 18:41 zzjson.c32

LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda1 rw
    INITRD ../intel-ucode.img,../initramfs-linux.img

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 27,833

Website

Re: [Solved] Syslinux Failed to load ldlinux.c32

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: [Solved] Syslinux Failed to load ldlinux.c32

forbi

Member

Registered: 2013-12-21

Posts: 45

Re: [Solved] Syslinux Failed to load ldlinux.c32

root@archiso ~ # fdisk -l
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x73230cb6

Device     Boot     Start       End   Sectors Size Id Type
/dev/sda1  *         2048 104859647 104857600  50G 83 Linux

root@archiso ~ # arch-chroot /mnt
[root@archiso /]# cat /boot/syslinux/syslinux.cfg
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
#   * menu.c32 - provides a text menu
#   * vesamenu.c32 - provides a graphical menu
#   * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
#   * hdt.c32 - hardware detection tool
#   * reboot.c32 - reboots the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples

DEFAULT linux
PROMPT 0        # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl

# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32

# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda1 rw
    INITRD ../intel-ucode.img,../initramfs-linux.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda1 rw
    INITRD ../initramfs-linux-fallback.img

LABEL linux
    MENU LABEL Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda2 rw
    INITRD ../intel-ucode.img,../initramfs-linux.img

#LABEL windows
#        MENU LABEL Windows
#        COM32 chain.c32
#        APPEND hd0 1

LABEL hdt
        MENU LABEL HDT (Hardware Detection Tool)
        COM32 hdt.c32

LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32

LABEL poweroff
        MENU LABEL Poweroff
        COM32 poweroff.c32

ooo

Member

Registered: 2013-04-10

Posts: 1,637

Re: [Solved] Syslinux Failed to load ldlinux.c32

which filesystem are you using on sda1?

forbi

Member

Registered: 2013-12-21

Posts: 45

Re: [Solved] Syslinux Failed to load ldlinux.c32

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 27,833

Website

Re: [Solved] Syslinux Failed to load ldlinux.c32

Oops, sorry — I’ve never used syslinux on a single (boot on root) partition.  I misunderstood how it would work.  Sorry for the noise.

ooo

Member

Registered: 2013-04-10

Posts: 1,637

Re: [Solved] Syslinux Failed to load ldlinux.c32

forbi

Member

Registered: 2013-12-21

Posts: 45

Re: [Solved] Syslinux Failed to load ldlinux.c32

AsmundEr

Member

From: Trondheim, Norway

Registered: 2010-05-07

Posts: 14

Re: [Solved] Syslinux Failed to load ldlinux.c32

Steve Lockwood

Member

Registered: 2017-08-31

Posts: 1

Re: [Solved] Syslinux Failed to load ldlinux.c32

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,018

Website

Re: [Solved] Syslinux Failed to load ldlinux.c32