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.
Well, if the CD boots on 2 other systems then it pretty much rules out the valid burn issue, however, If you had burned the CD on another drive there may be some problem with your CDR reading that it is a bootable CD.
If you have more then one drive one your system try the other drive. If not, I would suggest copy the knoppix.iso to your machine and burn the CD on YOUR Drive.
Originally posted by simple so then the linux cd should boot fine if done properly..... point?
the point is that the bios is obviously booting the drive, as if it wasn't then the windows cd wouldn't boot... so there's no need to "hit esc" and select anything...
that doesn't make too much sense, but i guess you're saying what he said? it's booting to the hard drive and not from cd drive? but does with the windows cd, not with a properly burned .iso as a disc image, well hitting esc he would be able to pick the cd drive, and see it "trying" to boot if there was a proper bootable disc in it, if his BIOS weren't setup properly.. and if they are should still TRY and boot, if it isn't theres something he's not saying, or is trying to say linux sucks you should use the windows cd people because it works for me? (Just a thought)
Originally posted by simple if it isn't theres something he's not saying, or is trying to say linux sucks you should use the windows cd people because it works for me? (Just a thought)
what on earth are you talking about?? LOL... he mentioned the windows cd was booting properly to rule-out that his bios might not be set to boot from the cd... it's quite simple...
Originally posted by win32sux what on earth are you talking about?? LOL... he mentioned the windows cd was booting properly to rule-out that his bios might not be set to boot from the cd... it's quite simple...
i'm saying then it should work and be no problem, who here could actually solve this as being a problem? if 1. bios is set up right 2. disc image is right 3. a bootable disc worked 4. the cd worked on two other computers not this one 5. we're still unsure about the light blinking, but if it is, then it's trying but not finding a boot record on the iso? maybe his computer just doesn't like knoppix before it tries it? or what, what could it be... hmm.
anyways... pilypala, i've read of similar issues occuring when a bootable ISO is burned with a "--boot-load-size" higher than 4... i'm not sure what program you used to burn the CD but this could be a reasonable explanation as to why it boots on the other PCs but not on yours... like, some BIOSes won't boot a cd if it was burned with a --boot-load-size 32, for example... take a look at what Patrick Volkerding wrote in the Slackware isolinux README:
Quote:
Techincally the --boot-load-size should be a lot bigger, like 20 or so in order to hold the isolinux.bin boot block. However, setting it to 4 causes it to load on more BIOSes. I don't know why, but I've had so many people report this to me that I'm inclined to believe it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.