When trying to boot LiveCD 2004.0-x86-20040204 on recent intel mb the live CD fails to boot. It crashes after listing the sata HD and CD properly. The motherboard I have tried are: Intel D865PERL Intel D875PERL Both fail at the same spot. Reproducible: Always Steps to Reproduce: 1.Boot LiveCD on this hardware 2. 3. Actual Results: Machine freezes and has to be powered down. Expected Results: boot not relevant
I did manage to boot the 2.6 kernel LiveCD for November. After installing Gentoo and Kernel 2.6.3-r1 on the machine the sata disk, which showed up as /dev/sda under the liveCD was not recognized on boot. After some investigation, it appears that the initrd is not detecting the sata disk because it doesn't ever load libata. I reconfigured the kernel so that ATA Disk support, SCSI Disk support, Serial ATA Support and the intel PIIX/ICH Sata driver were all compiled in. After that all runs as expected. I think you should see if the same problem could be effecting the new LiveCD.
I'm downloading the x86 image now but I know for a fact the i686 "LiveCD" is not bootable (yes I checked the MD5 sum). Regardless of the hardware you can't easily boot a non-boot CD.
I checked the x86 LiveCD and it is also a nonbootable CD unlike the 1.4 LiveCD which was bootable. Why release a "Live"CD if it is nonbootable... I guess that's a bug.
What LiveCDs did you try exactly? For x86 architecture, the following two are marked as LiveCD in our documentation: install-x86-minimal-2004.0.iso install-x86-universal-2004.0.iso Both have been extensively tested and work on most hardware. Of course, we cannot guarantee 100% functionality on all hardware. The packages-* ISOs are not marked as LiveCD in our documentation. If you are referring to the livecd/ directory on the mirrors, then perhaps we should rewrite it to read "isos/" or something similar to avoid all confusion.
Well that makes a world of difference thanks. ...and changing the directory name would be a welcomed change.
do do the 2004.0 bootable livecds fix your problem?
Closing due to no response