xfs
[Top] [All Lists]

Re: XFS for Linux 1.0.1 Released

Subject: Re: XFS for Linux 1.0.1 Released
From: "D. Stimits" <stimits@xxxxxxxxxx>
Date: Wed, 11 Jul 2001 03:13:07 -0600
Cc: linux-xfs@xxxxxxxxxxx
References: <200107102103.f6AL3am18531@xxxxxxxxxxxxxxxxxxxx> <20010711105428.A21601@xxxxxxxxx>
Reply-to: stimits@xxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Jan-Frode Myklebust wrote:
> 
> I'm trying to get this installed on a Dell
> PowerEdge 4400, and am having some problems. I never
> could get the XFS-1.0 release into this, so it's a
> standard RH 7.1 system at the moment.
> 
> http://www.dell.com/us/en/esg/topics/esg_pedge_towermain_servers_1_pedge_4400.htm
> 
> The kernel-smp-2.4.5-SGI_XFS_1.0.1.i686.rpm doesn't
> include the aacraid patch, so I have to use the
> kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm
> 
> I Install the kernel:
> 
> # rpm -ivh kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm
> 
> make the initrd image, and move it to /boot:
> 
> # mkinitrd initrd-2.4.3-SGI_XFS_1.0.1smp.img 2.4.3-SGI_XFS_1.0.1smp
> 
> Add an entry to /etc/lilo.conf:
> 
> image=/boot/vmlinux-2.4.3-SGI_XFS_1.0.1smp
>        label=linux-xfs
>        initrd=/boot/initrd-2.4.3-SGI_XFS_1.0.1smp.img
>        read-only
>        root=/dev/sda1
> 
> but when I run lilo I get the message:
> 
> # lilo
> Added linux *
> Fatal: Kernel doesn't support initial RAM disks

Don't trust rpm to update the kernel. Run rpm -i on the source rpm, then
get the tarball out of /usr/src/redhat/SOURCES/, do a cp -adpR on
whatever subdir it is to the usual /usr/src/ location after backing up
(and completely moving out of the way) any old kernels. Then run make
menuconfig (or some config) manually before doing the rest. You have to
select initial ram disk support.

I also don't know if it is a failure to run lilo and point it at an
uncompressed kernel, but you probably should copy the bzImage over as
vmlinuz and point lilo at that instead of the uncompressed vmlinux image
(keep vmlinux for debugging). Building from source is about the only way
to go for any kernel install at all. At least I think so.

If you have a requirement to access your raid controller during bootup,
you will want to specifically name any raid modules in your mkinitrd
command (unless it is compiled directly in).

D. Stimits, stimits@xxxxxxxxxx

> 
> Will I have to build a new kernel from source to fix
> this? BTW: what's the latest "recommended" version
> in cvs?
> 
> Does anybody know why the aacraid module isn't in the
> linus-tree?
> 
>   -jf


<Prev in Thread] Current Thread [Next in Thread>