Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just attempted to update my kernel from the archaic 2.2.19 to the more recent 2.4.18. I kept most of the settings the same, so that shouldn't have been any problem. However, when I boot up with the latest kernel, I get this error:
VFS: Can not open root device "301" or 03:01.
Please append a correct "root=" boot option.
Kernel Panic: VFS: Unable to mount root fs on 03:01.
It sounds like it's an error that can be corrected without my having to recompile (which would be nice, takes so long to compile, bleh). Anyone have any suggestions? Thanks in advance
Yeah that looks rather just fine. The only guess I could hazard is that you included something that takes a passed parameter to work at all, but I have no idea why that would conflict with you being able to mount the root filesystem.
Just for shi*s 'n giggles, after you compiled the new kernel, what did you do? Step by step if possible. It may sound wierd, but i've also had boot problems with lilo and Slack when I didn't seperate my boot items. Say a hash, etc...
I just noticed that your vga= option says 795 when it should be 791. Could cause a problem too, unless it's a typo.
If you haven't already done a make mrproper on your /usr/src/linux dir, or whatever dir you compiled from, go there and do a make bzlilo and see what that does for you. It's a nice little command that copies renames all the files for you and edit's lilo.conf itself. Edit your lilo.conf, take out the new entry, save and run lilo. Then do the make bzlilo. See if the new kernel will boot after that. Then you can worry about more than one image entry in lilo.
Taz.devil, can you please clarify what you just told me to do? I didn't quite get what you wanted me to do. However, it sounds as if you want me to recompile the kernel. If I do, I'd prefer to do that only when I'm 100% sure I know I'm screwed. I don't really see what make bzlilo can do for me that I haven't already did I guess. Thanks
One slight possible problem could be filesystem support. By default all Linux kernels have ext2 include. Now if you hda1 is ext3 or other the problem maybe that it was not included or was included as module but was not installed with make modules and make modules_install.
The following is just an idea for future kernel upgrades and a do at your own risk.
If you like your 2.2.19 kernel config and just want the extra tweaks of 2.4.18 cp the .config from 2.2.19 to 2.4.18 you might want to backup the .config of 2.4.18 first. After that do a make xconfig as your scanning through you will notice that the configuration is just like that of 2.2.19. Save and exit. Do you make dep,bzImage,and everything else that's appropriate I would suggest doing a make modules and make modules_install just incase. Now if you have issues with the cp .config then just do a make mrproper(sets it do factory default) or delete .config and rename the backup you made to .config
Good idea, but Slack 8 shipped with default kernels 2.2.19 and 2.4.5. There's a pile of support for Reiser in the distro, but its all after-the-fact tweaking and wasn't supported for 2.2.19. Also, his original lilo.conf file in order to support either journaling file system would have had to have had "read-write" after the label.
The errors for booting a kernel that doesn't have filesystem support for what its trying to mount are similar...
Now I know this is a longshot, but on second thought what about the other way around, did you include ext2 support in the kernel? It would have been a default, but you could have unchecked it by accident. Of course, I'm not certain that you can remove ext2 support, but its a thought.
I did use the config file that came with Slack and than modified it slightly (changed the processer from 386 to the Athlon K6-II choice), and the file system is ext. 2. Thanks for the help so far guys.
The labels have to be one character string with no breaks. Hence my bzImage and label names:
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
message = /boot/boot_message.txt
append = "mem=nopentium"
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
# Normal VGA console
vga = normal # End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = Win98andOtherBadHabits
table = /dev/hda
Originally posted by Oooska I followed the NHF at Linuxnewbie.org. Which was make dep, make clean, make bzImage, make modules, make modules_install. Than I edited lilo.conf and rebooted.
i was skimming through your posts here, and noticed that line in particular...
did you run lilo after you editted lilo.conf, but before you rebooted? the changes you make to lilo.conf don't mean anything until you run lilo to edit the boot sector. replacing the kernel and other fun stuff like that will make the boot hang if you haven't run lilo before you reboot.