LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This 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.

Notices


Reply
  Search this Thread
Old 03-19-2002, 02:32 AM   #1
Oooska
LQ Newbie
 
Registered: Jan 2002
Location: Bangor, ME
Distribution: Slackware 8
Posts: 20

Rep: Reputation: 0
Boot up problems with new kernel.


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:
Code:
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
 
Old 03-19-2002, 07:12 AM   #2
Bert
Senior Member
 
Registered: Jul 2001
Location: 406292E 290755N
Distribution: GNU/Linux Slackware 8.1, Redhat 8.0, LFS 4.0
Posts: 1,004

Rep: Reputation: 46
I think you need to tell the system where the root partition is,

eg. root=/dev/hda2

Bert
 
Old 03-19-2002, 02:37 PM   #3
Oooska
LQ Newbie
 
Registered: Jan 2002
Location: Bangor, ME
Distribution: Slackware 8
Posts: 20

Original Poster
Rep: Reputation: 0
I'm assuming you mean I have to add it to my lilo.config file. This is the current file:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
vga = 795
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins

image = "/boot/bzImage"
	root = /dev/hda1
	label = "Linux 2.4.18"
	read-only

image = "/boot/vmlinuz-2.2.19"
  	root = /dev/hda1
  	label = "Linux 2.2.19"
	read-only
# Linux bootable partition config ends
Is there something wrong with it? When I run /sbin/lilo it doesn't give me any errors. Linux 2.2.19 boots just fine, 2.4.18 does not. Thanks.
 
Old 03-19-2002, 03:37 PM   #4
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 58
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.

Cheers,

Finegan
 
Old 03-19-2002, 03:58 PM   #5
taz.devil
Senior Member
 
Registered: Nov 2001
Location: Wa. State
Distribution: Slackware
Posts: 1,261

Rep: Reputation: 45
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.
 
Old 03-19-2002, 04:31 PM   #6
Oooska
LQ Newbie
 
Registered: Jan 2002
Location: Bangor, ME
Distribution: Slackware 8
Posts: 20

Original Poster
Rep: Reputation: 0
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.

As for vga =795, I know. I prefer 1280 x 1024 res instead of 1024 x 768. There's been no problem there (except somem silly emulator doesn't work in that res for some reason...)

Last edited by Oooska; 03-19-2002 at 04:34 PM.
 
Old 03-19-2002, 04:46 PM   #7
taz.devil
Senior Member
 
Registered: Nov 2001
Location: Wa. State
Distribution: Slackware
Posts: 1,261

Rep: Reputation: 45
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.
 
Old 03-19-2002, 09:21 PM   #8
Oooska
LQ Newbie
 
Registered: Jan 2002
Location: Bangor, ME
Distribution: Slackware 8
Posts: 20

Original Poster
Rep: Reputation: 0
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
 
Old 03-20-2002, 04:02 AM   #9
jdctx
Member
 
Registered: Feb 2002
Posts: 71

Rep: Reputation: 15
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
 
Old 03-20-2002, 12:33 PM   #10
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 58
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.

Cheers,

Finegan
 
Old 03-20-2002, 02:26 PM   #11
Oooska
LQ Newbie
 
Registered: Jan 2002
Location: Bangor, ME
Distribution: Slackware 8
Posts: 20

Original Poster
Rep: Reputation: 0
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.
 
Old 03-20-2002, 02:45 PM   #12
taz.devil
Senior Member
 
Registered: Nov 2001
Location: Wa. State
Distribution: Slackware
Posts: 1,261

Rep: Reputation: 45
Quote:
Originally posted by Oooska

image = "/boot/bzImage"
root = /dev/hda1
label = "Linux 2.4.18"
read-only

image = "/boot/vmlinuz-2.2.19"
root = /dev/hda1
label = "Linux 2.2.19"
read-only
# Linux bootable partition config ends

Is there something wrong with it? When I run /sbin/lilo it doesn't give me any errors. Linux 2.2.19 boots just fine, 2.4.18 does not. Thanks.
Humor me for a second and if you could, get rid of the quotes in your entries, rerun lilo and reboot and tell us what it does. Here's what mine looks like if you can see anything different also.

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 200
change-rules
reset
vga = 791
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = Win98
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda5
label = Slack
read-only
# Linux bootable partition config ends
 
Old 03-20-2002, 04:45 PM   #13
Oooska
LQ Newbie
 
Registered: Jan 2002
Location: Bangor, ME
Distribution: Slackware 8
Posts: 20

Original Poster
Rep: Reputation: 0
When I take out the quotes I get a lovely error telling me that there's a syntax error.
 
Old 03-20-2002, 05:18 PM   #14
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 58
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"
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal # End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = Win98andOtherBadHabits
table = /dev/hda

image = /vmlinuz
root = /dev/hda2
label = Slack-2.2.19
read-only

image = /boot/slapMeSilly
root = /dev/hda2
label = 2.4.17
read-only

image = /boot/IwantWorkingsound
root = /dev/hda5
label = Bob-2.4.17
read-only

image = /boot/ILikeDoughnuts
root = /dev/hda5
label = Bob-17-fixt
read-only

image = /boot/Blergh
root = /dev/hda2
label = JacksBroken2.4.18
read-only

image = /boot/vmlinuz-2.4.7-10
root = /dev/hdc1
label = RedHat7.2
read-only

other=/dev/hda4
table=/dev/hda
label=FreeBSD

Lilo dies weird things, but I'm pretty certain it could boot my toaster if I tried hard enough, try just changing the roots... but really, a kernel re-compile is probably the best guess.

Cheers,

Finegan
 
Old 03-20-2002, 06:15 PM   #15
isajera
Senior Member
 
Registered: Jun 2001
Posts: 1,635

Rep: Reputation: 45
Quote:
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel boot problems Canadian_2k2 Linux - Software 11 01-25-2006 05:42 AM
Kernel boot problems PalmGuy Linux - Software 3 06-25-2005 04:25 PM
More Problems on kernel boot!! chansen0421 Linux - Newbie 0 07-26-2004 11:13 PM
Kernel update boot problems, no boot loader StaticSage Red Hat 2 01-09-2004 07:05 AM
boot problems in new kernel apberzerk Linux - General 4 10-19-2003 06:01 PM


All times are GMT -5. The time now is 04:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration