For lack of a better place to put this...
I just finished building a new computer for a friend, which I am running as I write this. The specs are as follows;
MB = Gigabyte GA-970A -D3 with AM3+ Socket
CPU = Amd FX 4100 3.8 GHz 4-Core
PSU = Antec BP 550 Watt Modular
RAM = 8 GB Patriot DDR3 1333 MHz
PCI Add-in Card = Syba Ultra ATA-133 IDE Controller Card
Optical Drive = TSSTcorp CDDVDW SH-222BB - SATA
Video Card = nVidia GeForce 8600GT - PCIe
This is virtually the same as my own current main machine, with the exception that this MB lacks a Firewire connector. Both have the combo UEFI/BIOS that automatically switches between which form of booting code is used, based on the size of the boot drive. Below 2.2 TB the familiar BIOS form is used; over that, the UEFI rules dominate.
There is a slight variance in the boot order settings in the BIOS. In mine I set the order as CD-ROM, USB-HDD, Hard Drive. This board would not boot to the generic CD-ROM setting, but on further inspection, I found an option to boot from the TSSTcorp CDDVDW SH-222BB
device, specifically. It would seem the newer BIOS version is more precise, and therefore more picky, about how code is actually executed. That's a first for me.
With this setting I have been able to boot to a Win2K installation disk, but on trying the PCLinuxOS 64 bit Test05 liveCD, I get this error;ISOLINUX 3.85 2010-02-20 ETCD Copyright (C) 1994 - 2010 H. Peter Anvin et al
No DEFAULT or UI Configuration Found
Another first for me... two on the same day... how lucky.
The same thing happens with any of the PCLinuxOS liveCDs I try on this machine.
Doing a Google search, This turns out to be a common error when using a USB stick
as a booting device, (but almost unheard of from within a liveCD) with the solution being to change the isolinux directory name
, and the isolinux.cfg
, and isolinux.bin
file names to syslinux.cfg
. Alternatively, some users report changing the USB stick format to FAT16, rather than FAT32, also works.
In my case, this error is the result of trying to boot from the liveCD
, burned at the lowest speed possible
, after passing an md5sum check
of the d/l image
, and then a further md5sum check
of the burned disk
. Syslinux reports that since version 4.02
this is no longer a problem, but we are still using version 3.85
, as seen in the error message. http://www.syslinux.org/wiki/index.php/The_Syslinux_Projecthttp://www.syslinux.org/wiki/index.php/ISOLINUX
A while back, AS
made some modifications to the mylivecd script
, and I don't know if those have anything to do with this present problem, or not. It is a very real problem, though.
At the error message Boot:
prompt, I can manually type this;Boot: vmlinuz livecd=livecd initrd=initrd.gz root=/dev/rd/3 acpi=on vga=791 keyb=us splash=verbose
...which is essentially the execution line
of the first boot menu option
, and the liveCD boots precisely as it should. I am typing this from that liveCD.
This took me about an hour to figure out, what with Google searches and such. I highly doubt that any Linux newbie types would be that fortunate if confronted by this error. Whether this is caused by changes
to the mylivecd script
, or the need for an upgraded version
, or both
, it needs to be fixed