Bug? Linux Mint Elyssa V5 Live CD, from file LinuxMint-5-r1.iso:
This Elyssa Live CD will load and install on an MSI mobo machine but not
a Gateway which easily runs the previous Darnya version of Linux Mint.
Md5Sum check of the ISO download is OK (downloaded twice, from the torrent
link on the Linux Mint website and again from secsup.org.) ISO was burned
3 separate times to CDRs on 2 different PCs at slow speeds, using both
Windows and an installed Linux Mint 4 Darnya.
Repeated Failed boots:
On an older updated Gateway AMD Athlon 1200 mHz/768 MB (which boots and
installs the previous Darnya Live CD OK) the Elyssa Live CD stops short:
it gets to the 1st splash screen which allows selecting automatic boot/
2 manual Start Linux Mint modes/memory test (ran it, passed OK), then it
displays "Loading Casper...", then "Ready", then "Loading...", then
the 2nd splash screen with the horizontally moving loading bar.
Shortly after this it stops accessing the CD drive altogether, then
after a long delay it displays a continuously scrolling text screen with
repeating lines:
"SQUASHFS ERROR: sb_bread failed reading block 0x58c6",
"Unable to read fragment cache block [1629407]",
"Unable to read page, block 1629407, size 87b9...".
This occurs no matter which of the 3 boot modes is selected.
Successful boots on a different machine:
On a more recent MSI AMD Athlon 2800/512 MB machine all 3 of my Elyssa
Live CDs boot up OK, during which the CD drive is accessed more or less
continually until the loading is complete (whereas the Gateway machine
quit accessing the CD drive soon after starting the loading process).
The Gateway machine has not given any problems and runs Windows plus
Linux Mint 4 Darnya and Knoppix Live CDs OK, so evidently there is a
variation in the Elyssa Live CD loader which does not work on certain
PC configurations. Unlike the Darnya Live CD, Elyssa does not have
a help file which suggests various boot options.
Solution?
Can you suggest changes to the boot prompt, or tests, or will future
ISOs fix this problem? Looking around the web indicates that quite
a few people have encountered similar problems.
Thanks for your efforts.



