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.
Is this the RH or the slackware box?
I'm not sure what slack has but you can use the RH 1st install CD to boot to rescue mode. You can also use a livecd like knoppix.
you probably screwed up you boot-loader - get (even better - HAVE) a rescue CD or floppy and boot with that - then you can repair what got damaged or rewrite your boot-loader (or put a undamaged copy of your kernel to where it has to be - but I highly doubt that your kernel is still there, but damaged...)
depending on the filesystem you use on your linux-partition, there are programs which will give you read/write access to linux from windows - if it is ext2, there is one - but you will have to find that yourself.
There is - for what you want to do - not much point in trying to do it from windows. you could just copy or change some files - but to change the boot-configuration - it will not only have to be changed in the config-files but also needs to be written to boot-sector of some partition or to the mbr - that you cannot do from within windows...
well the problem is not at the lilo but after linux starts to boot up
i choose linux from lilo (hdb5)
and it starts up(goes through all the hardware checking and stuff)... but then it comes to some error:
VFS: Cannot open root device "345" or hdb5
Please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on hdb5
weird++
this all started after i reconfigured/recompiled my kernel... most of the stuff i marked as built-in.... i guess i should've marked them as modules instead lol
what might have happened here is - you made a new kernel - and replaced you old one with it - by copying the kernel to where it has to be - and with the same name - which effectively overwrites your old one and leaves you with the new one. Now - if you misconfigured something while configuring the kernel - such as: not compiling in the filesystem you have on your / partition the kernel boots up and then does not know, how to access the / filesystem and cannot continue - and gives up with a kernel-panic
This was worst case scenario - I could also be - from what you describe:
you did everything all-right, but then forgot to update lilo by running "lilo -v"
Actually - you also forgot to copy the new system-map file to its place...I hav never installed a kernel like you did - I do:
make menuconfig
make
make_modules
make_modules install
cp ./System-map /boot System-map
cp ./arch/i386/boot/bzImage /boot/new_kernel_name
...so I do not overwrite the old one.
then I change /etc/lilo.conf to include the new kernel - but I still keep my old one this way
run: lilo -v
followed by: depmod -a
and THEN I'm ready to reboot
Question: do you have a rescue-CD or floppy ?
please look into the threads of the last couple of days - I have commented on this quite a lot and many times - search by keyword or by name...and see if it is helping you farther.
"you probably screwed up you boot-loader"
i always her of people having this problem. thir is a cool trick to
keep the boot loader in tact even if you have formatted your root partition. make a 1GB ext2 partition on your drive. and win you install grub (my favorite) instead of putting it on your root's /boot/grub, put it in that 1GB ext2 partition.
some tools for mounting Ext partitions from Windowa
Did you mean: Ext2 Installable File System For Windows - this one I use
("It provides Windows NT4.0/2000/XP/2003/Vista with full access to Linux Ext2 volumes (read access and write access). This may be useful if you have installed both Windows and Linux as a dual boot environment on your computer.") Explore2fs - is something like you really need LTOOLS (old name:LREAD) -just other tool.
PS: But be careful:
"You can use hibernate (suspend to disk) in Windows only if you resume Windows subsequently. Furthermore, you can use hibernate (suspend to disk) in Linux only if you attempt to resume Linux subsequently. It means that you should shutdown Windows before booting Linux and vice-versa. You cannot mix the two operating systems."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.