Re: 2.0.31: RAMDISK: Could not get major 1

Markus Riepe (mriepe@gmx.net)
25 Oct 1997 17:20:03 +0200


Excuse me,

I found the error by myself.

The problem was a double definition in /etc/lilo.conf and in the
boot-script.

Markus Riepe <mriepe@gmx.net> wrote:
> Hi,

> I compiled ramdisk as a module, and I mount a ramdisk on /tmp.
> At boottime I got the following message:

> <4>RAMDISK: Could not get major 1[EXT II FS 0.5b, 95/08/09, bs=1024, fs=1024, gc=1, bpg=8192, ipg=2048, mo=002b]

> It worked fine in 2.0.31.pre-9.

> But, after booting (2.0.31) I see no differences,
> the ramdisk is mounted on /tmp and got the right size.

> Whats the problem?

> This is the bash-script, how I mount the ramdisk:
> # Ramdisk
> modprobe rd rd_size=0x2000
[...]

This modprobe was the problem. In /etc/lilo.conf I said

append="auto ramdisk_size=0x2000"

But, there was no problem in 2.0.30 and 31-pre9?

Markus

-- 
mailto:mriepe@gmx.net                     PGP-Public-Key-ID: 0xFF1F2839 
Gemaess  Paragraph  28 Abs. 3 Bundesdatenshutzgesetz  widerspreche  ich 
hiermit ausdruecklich der Nutzung oder Uebermittlung  meiner Daten fuer
Werbezwecke oder fuer die Markt- oder Meinungsforschung.