Boot failure : No DEFAULT or UI configuration directive found!

1

Reason for the Error :

Generally the iso image that are intended to be burned and booted from CD/DVD has all the files required for Boot in the “ISOLINUX” folder. Whereas the iso images that are intended to be run from USB has all the files required for boot in the “SYSLINUX” folder. So when you try to burn and boot a CD/DVD iso from USB, it cannot recognize the type of boot medium as it will not have “syslinux” folder it will simply give “Boot failure : No DEFAULT or UI configuration directive found“.

Solution for the Error :

Open the USB installation media, then rename the following:

isolinux –> syslinux (folder)
isolinux.bin –> syslinux.bin
isolinux.cfg –> syslinux.cfg

This will work.....

0 0
2

Quite recently my laptop’s backlight stopped working and I had to start using an older laptop whose HDD no longer works. I created a Live CD USB drive using Pendrive Linux’s utility for Linux Mint.

However, while booting with the pendrive I got an error saying:

SYSLINUX 3.85 2010-02-20 CBIOS Copyright (c) 1994-2010 H. Peter Anvin et al
No DEFAULT or UI configuration directive found!
boot:

This error kept happening no matter what I did. I tried to use another USB drive to create a new bootable drive, used different flavors of Linux but had the same problem. I searched around several forums but the solution for it wasn’t easy.

However, I did find the solution and wanted to post it here so that other users who face this problem can find it easily. In order to fix this problem, you will have to plugin the USB drive into another computer and then rename the “isolinux” folder to “syslinux”. In addition to that also rename the “isolinux.bin” and...

0 0
3

Situation: I have an old HTPC, with Win 7 and XBMC running, but I would like to switch it to openelec. It is an AMD based system with a Gigabyte GA-MA78GM-S2H motherboard.

First issue that I had, was that the motherboard refused to boot from USB. After a few hours of trial and error, I found that formatting the stick to FAT fixed the issue

So, now it will finally boot from the installation USB stick, I'm getting the dreaded "No default or UI configuration directive found" error, and the machine refuses to do anything else. I googled (alot) and found some possible fixes, one of which is formatting in FAT (which I had already done). Another solution says to enter a command like "mboot.c32 -c boot.cfg", but I cannot enter anything. Yet another solution is to rename some isolinux files to syslinux, but there is only 1 cfg file like that on the stick, and it is already called syslinux.

I also tried using different USB sticks of different sizes (1GB/4GB) and...

0 0
4

Problem:
When trying to run a laptop from a bootable usb stick (with Ubuntu on it) stumbled at the error:
ERROR: No configuration file found
No DEFAULT or UI configuration directive found!
Boot:

What I did try to fix the error (didn’t work for me):
* triple checking the BIOS options (booting from usb drives supported and activated… Saving… Choosing defaults and then saving… NOTHING.)
* typically I use only 1 usb flash as a bootable drive, and it usually works fine. Nevertheless, I used different other flash drives (all I had) to check if the problem was a faulty usb stick…
* rebooting, pressing F12, choosing booting from Usb drive… And getting the same error “No configuration file found”.
* renaming isolinux.bin and isolinux.cfg files to syslinux.bin and syslinux.cfg respectively.
* moving the syslinux folder into the boot folder (at the bootable drive).

What finally worked for me: (A VERY simple step indeed :)
...

0 0
5
...
0 0
6

I’m new, so i beg your pardon from the outset.

I’ve reviewed a few other people’s questions who had the same problem.

I’m an utter noob to linux and would love to give it a try. hence the bootable usb.

I’ve been using Universal USB installer and UNetbootin.

I’ve changed the name of the folder, .bin and .cfg files to syslinux, syslinux.bin, syslinux.cfg.

I’ve allowed unetbootin to download another copy of the iso to install, with the same results as above.

I’ve tried formatting my usb’s in command prompt to FAT or FAT16, however to no avail. It said something about the USB being too big? i did this with both a 32gb usb and an 8gb USB. both with the same results.

How can i fix this...

0 0
7

Hi,

I did Downloaded CentOS-6.4-x86_64-bin-DVD1.iso from http://mirror.nbrc.ac.in/centos/6.4/isos/x86_64/ using DAP (Download Accelerator Plus).

After Downloaded the CentOS-6.4-x86_64-bin-DVD1.iso I did check md5sum. The server version and local downloaded file iso showing same md5 key. That means the downloaded file is fine. Then I write the DVD from iso to Create a CentOS 6.4 bootable disk. Disk created successfully.

Now when I am trying to boot using this Disk. I am getting the following error.

-------------

ISOLINUX 4.02 2012-07-21 ETCD (...)
EDD: Error 1000 reading sector 2024330
No Default or UI Configuration directive found.
boot: _

-------------

Even after this error i checked this link http://bugs.centos.org/view.php?id=5377

And did as followed.

1 Open the iso
2 Rename the isolinux folder to syslinux .
3 Rename the isolinux.bin and isolinux.cfg files in the same folder to syslinux.bin...

0 0
8

So I have copied (as usual the iso into usb disk (/dev/sdc)

sudo dd bs=4M if=archlinux-2014.08.01-dual.iso of=/dev/sdc

but when I boot to my new PC, it shows

ISOLINUX 6.03 6.03-pre18* EHDD Copyright (C) 1994-2014 H. Peter Anvin et al No DEFAULT or UI configuration directive found!

I have tried also for archlinux-2014.05.01-dual.iso and manjaro-xfce-0.8.10-x86_64.iso, but it shows the same result.

I have tried to rename syslinux folder, syslinux.bin, syslinux.cfg to isolinux, as suggested here: http://askubuntu.com/questions/329704/s … tive-found using isomaster, then dd back to usb, but it won't boot at all.

Note: this never happened on my previous PC..

Motherboard: MSI H81M-E33

How to solve this problem?

Last edited by kokizzu (2014-08-22...

0 0
9

Hope it's OK to jot this down, even if I cannot accept answer immediately (and hope it's OK for SO - as there is a C patch below):

It seems I screwed up the hard disk on my desktop PC ({DRDY err}). So I wanted to run a bootable media to run fsck, but the CD on this desktop is broken, so I can only use USB flash. I have a couple of USB thumbdrives with Ubuntu and Suse - these start booting on the desktop; but during boot, udev tries to detect hard drives, and since the hard disk is screwed, it just loops there, and the respective OS never finishes booting.

So I tried to download SystemRescueCd; I have this USB thumbdrive, on which I tried to install SystemRescueCD:

# lsusb with sudo, to retrieve all info $ sudo lsusb -v -d 058f:6387 | grep -i 'id\|iManufacturer\|iProduct\|iSerial\|bInterface' Bus 001 Device 043: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive idVendor 0x058f Alcor Micro Corp. idProduct 0x6387 Transcend JetFlash Flash Drive ...
0 0
10

Intermittent problems are really hard to track down. If you see anything in common when the problem occurs, it might help. Like does it happen during restarts, or cold boots after being completely shutdown?

If the error seems to be related to your Video Editor, maybe it is involved in causing the problem.

The message seems to be saying no User Interface is found. Perhaps it is referring to a user profile. But that should be there unless it is being corrupted.

Memory can be involved, since most of the OS is put in memory for use. During sleep or hibernation, files are written to the drives for use later. Page files are used all the time, which are written to hard drives. If the memory was having a problem, it might show up a corruption on the system. Most folks suggest running a memory test for a longer period that just one or two scans.

If you ever get a real Blue Screen, there might be a dump report made that could point to your problem.

If you...

0 0
11

When you get that message, it means SYSLINUX can't find the configuration file, syslinux.cfg (or it is indeed not written properly - unlikely in your case). For GPartedLive, it is located in /syslinux.

A quick workaround is to copy the contents of /syslinux (everything in it) to the root of your USB drive. SYSLINUX will always look in the root for syslinux.cfg. SYSLINUX 3.86 also seems to have some bugs with its ability to find the configuration file when it is nested inside directories - SYSLINUX 4.0 seems a lot more reliable and resilient.

For a not-so-quick-and-less-likely-to-work-but-potentially-cleaner workaround, try manually telling SYSLINUX where to look by doing the following (assuming you're using Windows) -

Download SYSLINUX 3.86. Extract win32\syslinux.exe to your desktop. Run the Command Prompt as administrator (Start -> All Programs -> Accessories -> right-click on Command Prompt, click Run as administrator). Find your desktop, if Windows Vista/7,...
0 0
12

I was trying to install CentOS7 to a newly assembled computer. The only way is to install from usb. I followed the instruction and dd the iso to usb drive. When I use it to boot, it give me error "Boot failure : No DEFAULT or UI configuration directive found". I searched online and found this answer:

Generally the iso image that are intended to be burned and booted from CD/DVD has all the files required for Boot in the “ISOLINUX” folder. Whereas the iso images that are intended to be run from USB has all the files required for boot in the “SYSLINUX” folder. So when you try to burn and boot a CD/DVD iso from USB, it cannot recognize the type of boot medium as it will not have “syslinux” folder it will simply give “Boot failure : No DEFAULT or UI configuration directive found“.

So according to some posts, the fix is to rename the ISOLINUX folder and 2 files underneath it with ISOLINUX name to SYSLINUX. However, when I insert the usb drive to my other linux computer, it...

0 0