When I mount the CD, I see the same tree of files and directories that I get when I mount the .iso on the loop device.

This is a good thing. <snip>

cdrecord -dev 0,1,0 -v speed=8 LiveCD-9.1.iso

(According to the manpage, -data is the default).

This should have worked. I am not sure why it will not boot on your machines. I did the procedure that I described before and it works. If BIOS can boot from CD and you can see the directory structure, then I am not sure. Maybe some others can help. Marshall

On Wed, 5 May 2004, Frederic Soulier wrote:

I had the same problem. I burnt the Live 9.1 CD 4 times using K3b, Nero & Alcohol 120% with the same result: an unbootable CD on 2 different systems. The only way I managed to boot it is to use Smart Boot Manager and force the boot from the CD.

I'm glad I'm not alone ;) I was starting to get worried. I have a Pioneer DVR-107 on one system (a custom dual P3) and an Asus DVD-RW converted to a Pioneer DVD-106 on the other (Dell dimension 4100). Both systems have no problem booting Fedora Core 1, Fedora Core 2 (Test versions), Mandrake 9.2, Mandrake 10.0, Arch Linux, Gentoo, etc...

If there's a sensible explanation I'd like to hear it :)

I got this explanation from a member of my local LUG: Some older BIOS (notably ASUS motherboards for AMD K6-2 processors) will not boot from a CDROM which contains a 2.88Mb boot floppy image. One of my test machines is indeed a K6-2(450), and the other a gateway with a PII-300. I tried it on my Dell Latitude Cpt (Celeraon 500) and it recognized the CD, booted the kernel, but then gave me several 'out-of-memory' errors, a segfault, and finally a kernel panic while it was still trying to load modules. I guess 128MB isn't enough to run the live-eval. I hope I have better luck tomorrow when the 9.1pro upgrade is scheduled to arrive! -- Rick Green "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin

*** Reply to message from Brad Shelton on Thu, 06 May 2004 14:31:59 -0400***

Just fer grins, I d'loaded the iso and burned it, with k3b and it boots and runs fine so it looks like it is system dependent. I thought perhaps there might be iso file corruption during download er sump'n, but that doesn't appear to be the case.... at least not on this system.

yup, As far as the download and booting on most of the computers I've got here w/ no problems... including a couple of Asus Mobos... but I think they might be newer... (asus A7n266 )is on this box.. there is an older one whic doesn't have an easy way to tell what it is, but it's about 4 years old.. if that helps. It took forever to download the thing, even after I found a semi local mirror... So, do make certain you got everything. One version actually did try to make a bootable disk from an incomplete download... Which became obvious when the nubmers didn't match.. tho apparently the Key did .. restarted the download and got the rest... made my iso w/ k3b v. 0.10 and I've put it onto hardware everywhere I find a computer that the folks would allow me to... -- j -- nemo me impune lacessit it's just an afterthought; okay ? : Third Law of Advice: Simple advice is the best advice.

For this example, Synaptic displays its progress dialog with the two bars moving together left to right and then stopping about 1/3 of the way. Synaptic then reloads it indexes and displays the packages selected for installation or removal. (rpm -qv synaptic -> synaptic-0.48.2-rb1.) This type of error has happened on Pro 9.0 thru -215 using KDE 3.1 & 3.2+ rar_3.3.0-0.pm.1_i586.rpm is chosen. Synamptic adds dependenciy a52dec_0.7.4-3.pm.0_i686.rpm and the removal of the obsoleted unrar-3.2.2-36. By hand, rpm -iv a52dec_0.7.4-3.pm.0_i686.rpm gives error message "warning: a52dec_0.7.4-3.pm.0_i686.rpm: V3 DSA signature: NOKEY, key ID 5f6842a4," which must be what Synaptic is quitting on. It's reasonable not to install the RPM but Synaptic should show the errors. Am I overlooking something here? -- Phil