LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Kernel Problem (https://www.linuxquestions.org/questions/linux-newbie-8/kernel-problem-48369/)

dvong3 03-05-2003 05:03 AM

Kernel Problem
 
HI,

I just upgrade the kernel on my Redhat 7.2 using up2date. The problem I am having is the kernel can not detect my filesystem ext3. Also the lilo.config is missing an entry. Here is my lilo.config below. Can any one help?

[root@mrtg danny]# cat /etc/lilo.conf
prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.7-10
label=linux.bak
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/hda3

image=/boot/vmlinuz-2.4.18-26
label=linux
root=/dev/hda3
read-only

Neuronet 03-05-2003 06:31 AM

What do you mean by 'the kernel can not detect my filesystem ext3'?

How do you know that you have an entry missing? What error does it give when you type lilo at the command prompt?

I don't know about this up2date app that you mention, I compiled my kernel from source. You can get the latest sources and instructions from kernel.org

Neuronet.

UnTamed 03-05-2003 08:12 AM

More than the entry, if you're missing the actual initrd for your new kernel, that's what you got to solve. Look into /boot to see if you got a initrd-2.4.18-26, if so, just add the correct entry to lilo.conf [...and run /sbin/lilo].
If not, find out what kernel pkgs up2date actually installed.
rpm -qa | grep kernel
as you'll most likely need the kernel-sources to create a new initrd [...maybe the headers too???].

Anyway, see man mkinitrd and mkinitrd --help, iirc it was quite easy to figure but it's been a while since I've had to mess with that and the distros I run now,don't use it.

HTH.

Quigi 03-05-2003 12:46 PM

I'm having very similar issues after (network) upgrading from redhat 7.1 to 8.0

To answer some of Neuronet and UnTamed's questions,

Querying 'rpm -qa | grep kernel' reports:
kernel-2.4.18-14

But 'uname -srv' gives a very old kernel:
Linux 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001

Apparently this causes all kernel modules to be missing -- depmod fails with:
depmod: Can't open /lib/modules/2.4.2-2/modules.dep for writing
(the directory /lib/modules/2.4.2-2 does not exist).

Lacking ext3 manifests, e.g., when I try to mount:
mount: fs type ext3 not supported by kernel

Running lilo gives:
Fatal: open /boot/boot.b: No such file or directory

My lilo.conf appears to name the new kernel:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/messagte
linear
default=linux

image=/boot/vmlinuz-2.4.18-14
label=2.4.18-14
read-only
initrd=/boot/initrd-2.4.18-14.img
append="root=LABEL=/"

other=/dev/hda1
optional
label=dos

(apparently indentation doesn't make it to the post.)

Any hints about how to get the right kernel from RPM to boot would be appreciated.


All times are GMT -5. The time now is 09:04 AM.