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.
You will need to change the line that says "root=/dev/hdaX" to reflect your real / partition. The important line is the "initrd=/boot/initrd.img" line.
Location: a magical place, on some remote place on the planet
Distribution: Mandrake 10.1 winxp pro, free bsd
Posts: 91
Original Poster
Rep:
Quote:
Originally posted by AutOPSY post the output of fdisk -l
and the contents of your lilo.conf file.
i dont know nor do i know how to view the output of my fdisk -l
but the lilo output should be
linux
failsafe
windows
but i checked the lilo.conf file in the emacs as Thymox reconmaned and there was nothing there....
-----------------------------------------------------------------------------------------------
would be easier for me to reinstall the OS dispite the fact I want to be able run linux and fix all the problems without reinstalling the OS. Dispite the fact I am quite sure that everything can be fixed with reinstalling it
Last edited by only1gameguru; 04-18-2004 at 03:10 PM.
Location: a magical place, on some remote place on the planet
Distribution: Mandrake 10.1 winxp pro, free bsd
Posts: 91
Original Poster
Rep:
this was a head scretcher...
but i found out the trouble...
my brother set the computer up and plugged the harddrive into the wrong IDE contentor thing... which brings me to something why does it make a difference in Linux and not Windows...?
Windows is designed to "guess" what the user does and fix it without the user knowing they did somethign wrong, which is bad when u intentionally do somethign and windows fixes it.
In Linux if you change which IDE cable ur hdd is plugged into, the HDD will get a new "label" (ie from hda to hdc) and the rest of linux wont know how to find the new label.
look at (kernel source tree)/Documentation/devices.txt for the definitions of hda, hdb, hdc etc, etc
and its not really a new label, the kernel sees the devices /dev/hda as the master on ide0 (primary ide slot), /dev/hdc is the slave of the primary ide slot
Hello, I am running mandrake 9.2 and recently compiled the kernel and am experiecing similar problems are the poster of the thread. I've checked my lilo.conf and everything is precisely as it was before the compile, only the vmlinuz value has been changed on all the boot options. What gives? What can I do to fix this?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.