Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
Two options:
1: Your CD image is bad. Either there is a unnoticed error in the ISO image, or an error burned on the CD. The first is unlikely because I think there is some serious error protection built in the ISO and checked before it is unpacked. (Not sure though). The second is more likely. CD's are terribly error prone (despite of what many people say) and errors go undetected by CD readers. Been there, done that. Try to download again and burn the CD again.
2: Your computer has a hardware error, most likely in the memory. I had this once before, installation crashed every time, but not always at the same point. The box was running fine in Windoze, so that is no acid test!
Since your installation always crashes at the same point, I would think option #1 is most likely.
Did you check sum .iso files for integrity??? Installation can fail if MD5 checksum value does not match the values posted on the linuxiso.org. I downloaded RH9 from linuxiso.org and everything is up and running. No troubles at all.
you also might want to try reburning the ISOs at 8x and no faster. for some reason some media will not take a good ISO at speeds faster then 8x.
also depends on the quality of your burner. name brands do not matter its the quality of the lazer so even some of the best known names can have this issue.
check the sum first, and if that is ok, then reburn at the slower speed.
I downloaded RH9 in windows (from linuxiso.org) and then used a windows version of MD5 checking utility (available on linuxiso.org) to check the MD5 in the windows and then burnt the cd's. I am not sure how you do it in linux. Yet I think there is info on how to do it linux on linuxiso.org.
what is printed to the screen just before you get the bad eip value error message? is there mention to a particular .c file from the kernel? this error message is generated from the "traps.c" file from the kernel source. basically, from how i read the code, the abort happens when the control unit is unable to store a meaningful value in the eip register. which stores memory locations where exceptions are encountered. this would point to a hardware compatibility issue and according to this thread (mandrade example with similar error) and others the offending device can be a motherboard or usb device that is not fully supported.
i would try to take note of what file is mentioned just before the error and if it is something like usb.c, then you have an unsupported usb device that is fouling the boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.