mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Kitchener <stephen@g6dzj.demon.co.uk>
To: <linux-kernel@vger.kernel.org>
Subject: Error message after lilo on 2.4.17
Date: Wed, 9 Jan 2002 21:36:06 +0000	[thread overview]
Message-ID: <E16OQOR-00072j-0B@finch-post-11.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

Hi,

I hope this it the right place, it is kernel related.

I have built a 2.4.17 kernel from source on a machine here, via make 
mrproper, make xconfig, make bZimage, make mdules, make modules_install, 
,make install. Im just repeating them here so that you can see what I have 
done :-).

Checked the lilo.config, run /sbin/lilo and booted the machine.

When the machine boots it finds the kernel, lilo dosnt hang but I get this...

uncompressing linux. OK booting the kernel
Unknown bridge resourse at 0: assuming transparent
mkroot: mknod failed: 17
mount error 16 Mounting ext3 flags. Kernel panic no init found.
Try passing init=option to kernel.

The first two lines appear when I am booting from a 2.4.8 kernel, but things 
load correctly there and the 2.4.8 kernel and modules were installed the same 
way as the 2.4.17 version, so I am at a loss as to what I have missed.

Can someone help please

-- 
Stephen Kitchener

[-- Attachment #2: copy of lilo --]
[-- Type: text/plain, Size: 1342 bytes --]

boot=/dev/sda
map=/boot/map
install=/boot/boot.b
vga=normal
default=248-341-radio
keytable=/boot/uk.klt
lba32
prompt
timeout=50
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
        label=linux
        root=/dev/sda1
        initrd=/boot/initrd.img
        append=" devfs=mount quiet"
        vga=788
        read-only
image=/boot/vmlinuz
        label=linux-nonfb
        root=/dev/sda1
        initrd=/boot/initrd.img
        append=" devfs=mount"
        read-only
image=/boot/vmlinuz
        label=failsafe
        root=/dev/sda1
        initrd=/boot/initrd.img
        append=" devfs=mount failsafe"
        read-only
other=/dev/fd0
        label=floppy
        unsafe

image=/boot/vmlinuz-2.4.8-34.1mdk
        label=248-341
        root=/dev/sda1
        read-only
        optional
        vga=normal
        append=" devfs=mount quiet"
        initrd=/boot/initrd-2.4.8-34.1mdk.img

image=/boot/vmlinuz-2.4.17
        label=2417
        root=/dev/sda1
        read-only
        optional
        vga=normal
        append=" devfs=mount quiet"
        initrd=/boot/initrd-2.4.17.img

image=/boot/vmlinuz-2.4.8-34.1mdk-Radio
        label=248-341-Radio
        root=/dev/sda1
        read-only
        optional
        vga=normal
        append=" devfs=mount quiet"
        initrd=/boot/initrd-2.4.8-34.1mdk-Radio.img

             reply	other threads:[~2002-01-09 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 21:36 Stephen Kitchener [this message]
2002-01-15 14:13 ` Stephen C. Tweedie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E16OQOR-00072j-0B@finch-post-11.mail.demon.net \
    --to=stephen@g6dzj.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®