lkml.org 
[lkml]   [1996]   [Aug]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: cant build ramdisk :-(
On Sat, 3 Aug 1996, Herbert Rosmanith wrote:

>
> hi,
>
> i followed the instructions in linux/Documentation/ramdisk.txt:
>
> dd if=linux/arch/i386/boot/zImage of=/dev/fd0
> rdev /dev/fd0 /dev/fd0
> rdev -r /dev/fd0 49152
>
> but when I boot with this disk, the kernel would say:
>
> VFS: insert root floppy and press ENTER .... I do so
> VFS: mounted root [ext2fs] readonly (I'm not in front of the
> machine right now)
>
> shouldnt the first message read something like "VFS: insert ramdisk floppy" ?
>

No, insert the disk with the root on, you don't have to load it into a
ramdisk, but it can be. You get the same message even if you just mount
the floppy directly.

> kernel is 2.0.10
>
> I also tried to install lilo on the bootdisk (install=/mnt/boot/boot.b,
> append="prompt_ramdisk=1" or similar), but all lilo does is print either
> "LI" or "LIL". according to the faq, I have problems with my SCSI system,
> which is not true, since this particular computer doesn't have a SCSI
> adapter at all... and yes, this *IS* lilo.19.tar.gz which I just downloaded
> an hour ago.
>

Hmm, the lilo docs don't say that as far as I can see, they say this:

LILO start message
- - - - - - - - -

When LILO loads itself, it displays the word "LILO". Each letter is printed
before or after performing some specific action. If LILO fails at some
point, the letters printed so far can be used to identify the problem. This
is described in more detail in the technical overview.

Note that some hex digits may be inserted after the first "L" if a
transient disk problem occurs. Unless LILO stops at that point, generating
an endless stream of error codes, such hex digits do not indicate a severe
problem.

(<nothing>) No part of LILO has been loaded. LILO either isn't installed
or the partition on which its boot sector is located isn't active.
L<error>... The first stage boot loader has been loaded and started,
but it can't load the second stage boot loader. The two-digit error
codes indicate the type of problem. (See also section "Disk error
codes".) This condition usually indicates a media failure or a geometry
mismatch (e.g. bad disk parameters, see section "Disk geometry").
LI The first stage boot loader was able to load the second stage boot
loader, but has failed to execute it. This can either be caused by a
geometry mismatch or by moving /boot/boot.b without running the map
installer.
LIL The second stage boot loader has been started, but it can't load
the descriptor table from the map file. This is typically caused by a
media failure or by a geometry mismatch.
LIL? The second stage boot loader has been loaded at an incorrect
address. This is typically caused by a subtle geometry mismatch or by
moving /boot/boot.b without running the map installer.
LIL- The descriptor table is corrupt. This can either be caused by a
geometry mismatch or by moving /boot/map without running the map
installer.
LILO All parts of LILO have been successfully loaded.

> /herp
>
>

Looks like Linux tells LILO one geomertry (when you ran lilo to install
the loader), and the BIOS is using annother ....

Bryn
--
PGP key pass phrase forgotten, \ Overload -- core meltdown sequence
again :( and I don't care ;) | initiated.
/ This space is intentionally left
| blank, apart from this text ;-)
\____________________________________



\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.046 / U:3.812 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site