Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
anyhow, md5sum is a checksum program (over simplified explination I know)
the md5sum should be in the same place you downloaded the ISO from. or you could just make sure its the ISO is the same size as the one on the FTP site if you're really lazy
does that drive ef mean there are problems with drives E and F I know I have them partitioned as a linux swap and ext filesystem..... I did that with partition magic a long time ago.
its hex probably. Linux doesn't use drive letters, that old legacy DOS habbit (well, ok, Apple does it to)
really there is no evidence to suggest there is anything other than a bad CD image.
what it is halting on is uncompressing the Linux into memory. so from there we go back to the orginal analysis
either the CD is messed up, in that the Linux kernel image is corrupt on the CD, the CDRom drive isn't reading the CD correctly ( I had a CDRom like that in the past, it wouldn't work 95% of the time ), or there is something wrong with something in your computer's hardware dealing with the proccessor, the memory, or the bios, or possibly the controler that the cdrom is on. however hardware issues like this are less likely.
I did a quick search, remembered somethings, and I think I found the probable cause of all of this:
Redhat started using isolinux, the newer program that does basically what syslinux does. while isolinux is really cool, and I could go on about it for awhile in realtionship to a self-booting linux cd that I work on, I'll cut to the chase
isolinux doesn't work on all hardware, the short having to do with some BIOS problems and INIT 13h (personally, I hate the ISA386 architecture)
from the isolinux website:Starting in version 1.65, ISOLINUX supports booting disk images of other operating systems. However, this feature depends on BIOS functionality which is apparently broken in a very large number of BIOSes. Therefore, this may not work on any particular system. No direct workaround is possible; if you find that it doesn't work please complain to your vendor and indicate that "BIOS INT 13h AX=4C00h fails."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.