Kernel panic on boot up of newly compiled kernel

Kernel panic on boot up of newly compiled kernel

Post by Pedro Fonse » Mon, 12 Nov 2001 03:49:44



Greetings.

I just did my first kernel compile today! I have Red Hat 7.1, but I
came up with some problems with a network driver, so people
recommended me to compile a new recent kernel...

So, the problem is that when I boot up the new kernel, a kernel panic
happens. These are the last 4 lines written to stdout:

request_module[block-major-3]: Root fs not mounted
VFS: Cannot open root device "305" or 03:05
Please append a correct "root=" boot option
Kernel  panic: VFS: Unable to mount root fs on 03:05

This is my '/etc/lilo.conf' file:

boot=/dev/hda
map=/boot/map
install=/boot/boot.d
default=linux
prompt
timeout=50

image=/boot/vmlinuz-2.4.2-2
        label=linux
        read-only
        root=/dev/hda5

image=/boot/vmlinuz-2.4.14
        label=linux-new
        read-only
        root=/dev/hda5

The new image on the file was merely copied and pasted from the
previous one (I only changed the label and the boot image file). Oh,
and I did not forget to do 'make modules' and 'make modules_install'!

Please, any help?

 
 
 

Kernel panic on boot up of newly compiled kernel

Post by Ian » Thu, 29 Nov 2001 10:16:25


Did you do - >'lilo' at some point after editing lilo.conf?

> Greetings.

> I just did my first kernel compile today! I have Red Hat 7.1, but I
> came up with some problems with a network driver, so people
> recommended me to compile a new recent kernel...

> So, the problem is that when I boot up the new kernel, a kernel panic
> happens. These are the last 4 lines written to stdout:

> request_module[block-major-3]: Root fs not mounted
> VFS: Cannot open root device "305" or 03:05
> Please append a correct "root=" boot option
> Kernel  panic: VFS: Unable to mount root fs on 03:05

> This is my '/etc/lilo.conf' file:

> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.d
> default=linux
> prompt
> timeout=50

> image=/boot/vmlinuz-2.4.2-2
>         label=linux
>         read-only
>         root=/dev/hda5

> image=/boot/vmlinuz-2.4.14
>         label=linux-new
>         read-only
>         root=/dev/hda5

> The new image on the file was merely copied and pasted from the
> previous one (I only changed the label and the boot image file). Oh,
> and I did not forget to do 'make modules' and 'make modules_install'!

> Please, any help?


 
 
 

1. Kernel Panic for newly compiled 1.2.0

I am sorry if this has been posted before, but i havn't seen a satisfactory
answer yet.

I just obtained and compilefd the 1.2.0 kernel from funet, and compiled it
with minimal fuss, but when i tried to boot i had major problems:
===
Partition ckeck:
hda: hda1
hdb: bad partition table
MINIX-fs: unable to read superblock
EXT2-fs: unable to read superblock
MSDOS bread failed
UMSDOS Beta 0.6 (compatibility level 0.4, fast msdos)
MSDOS bread failed
Kernel panic: VFS: Unable to mount root fs on 03:42
===

But when i boot with my old kernel 1.1.59 there is no problem.

I have a 486sx33 w 4MB RAM , 1mb Cirrus Logic VL bus Gr card
hda1 = MSDOS 250meg
hdb1 = MSDOS 250meg
hdb2 = EXT2-fs 250meg
hdb3 = swap 16meg
hdb4 = swap 4 meg

Kernel options compiled in are:
SBP support
ext2fs
msdos
umsdos

Any ideas as to why this happens?

I have just upgraded the kernel; all the rest of the software is slackware
release 1.1.59 (and works fine, including X and xdm)

If anymore info is needed let me know

Tom
--
| Tom Davidson                     | God did not create the world in 7 days; |
| St. Edmunds College, Cambridge   | He screwed around for 6 days and        |

2. Downloading NS Enterprise Server for HP-UX onto a PC?

3. Newly compiled 2.4.5 kernel refuses to boot...

4. linuxversion of Mozilla

5. Newly-compiled kernel hangs at boot

6. Anybody built XFree86 for WinNT or Win95 ?

7. Booting the computer with a newly compiled kernel

8. .bashrc problem

9. Newly compiled kernel won't boot!

10. Precompiled kernel boots, newly-compiled won't?

11. please help: newly compiled kernel cannot compile (2.0.34 slackware)

12. kernel panic on a 2.2.5 kernel new compile

13. Kernel panic on running newely compiled kernel