xfs
[Top] [All Lists]

Re: Can't get initial console

To: "Marcelo E. Magallon" <marcelo.magallon@xxxxxxxxxxx>
Subject: Re: Can't get initial console
From: Jason Walker <unseen@xxxxxxxxx>
Date: Thu, 18 Jan 2001 10:00:33 -0500 (EST)
Cc: linux-xfs@xxxxxxxxxxx
Comments: SoVerNet Verification (on garnet.sover.net) [192.168.1.3] from pm1a3.stj.sover.net [209.198.94.3] 209.198.94.3 Thu, 18 Jan 2001 09:59:57 -0500 (EST)
In-reply-to: <20010118143932.A1292@barock.informatik.uni-stuttgart.de>
Sender: owner-linux-xfs@xxxxxxxxxxx
Hello Marcelo,

        Personally, i just did the CVS thing and I have been using it since
2.4.0test10.  Perhaps you might try that?  What version of modutils, etc
are on the box booting the kernel?  As you probobly know, 2.4 requires
newer versions of several packages.  Have you tried a plain 2.4 kernel on
it and seeing if you had the same problem?  Also, what about the box you
are building on? There are requirements for compiling the kernel, the most
notable and the one that got me stuck, was the right compiler.  you *have*
to use gcc 2.95.2  nothing newer, nothing older :)  the kernel wouldn't
even build with the compiler I had installed (some newer
compiler..Debian/Sid) To be honest it sounds like you might need to upgrade
some of the packages on your test box, but that's just a hunch.
/usr/src/linux/Documentation/Changes has all that info.  That's al the help
I can offer, I am not a developer, just someone insane enough to have a
beta kernel with a beta OS, on a beta fs ;)  Hope this helped!

Jason Walker/RegEx

On Thu, 18 Jan 2001, Marcelo E. Magallon wrote:

> Hi,
> 
>     I'm having a problem as of late with our XFS test box (and I haven't
>  had the time to take a look at it until today).  The kernel boots,
>  mounts the root partition (XFS) and tries to open the initial console
>  and fails.  If I pass the rw parameter to the kernel, it's able to get
>  an initial console, eventually the root filesystem gets remounted ro
>  and the boot fails (this is probably a problem in the SuSE boot
>  scripts).  This started happening arround the time 2.4.0 was checked
>  in.  At the moment I'm working my way thru this:
> 
>     kernel-2.4.0-XFS-test13-pre3+athlon.20001228.tar.gz
>     kernel-2.4.0-XFS-test13-pre3+athlon.20001229.tar.gz
>     kernel-2.4.0-XFS-test13-pre3+athlon.20001230.tar.gz
>     kernel-2.4.0-XFS-test13-pre3+athlon.20001231.tar.gz
>     kernel-2.4.0-XFS-test13-pre3+athlon.20010101.tar.gz
>     kernel-2.4.0-XFS-test13-pre3+athlon.20010102.tar.gz
>     kernel-2.4.0-XFS-prerelease+athlon.20010103.tar.gz
>     kernel-2.4.0-XFS-prerelease+athlon.20010104.tar.gz
>     kernel-2.4.0-XFS+athlon.20010106.tar.gz
>     kernel-2.4.0-XFS+athlon.20010107.tar.gz
>     kernel-2.4.0-XFS+athlon.20010108.tar.gz
>     kernel-2.4.0-XFS+athlon.20010109.tar.gz
>     kernel-2.4.0-XFS+athlon.20010110.tar.gz
>     kernel-2.4.0-XFS+athlon.20010111.tar.gz
>     kernel-2.4.0-XFS+athlon.20010112.tar.gz
>     kernel-2.4.0-XFS+athlon.20010113.tar.gz
>     kernel-2.4.0-XFS+athlon.20010114.tar.gz
>     kernel-2.4.0-XFS+athlon.20010115.tar.gz
>     kernel-2.4.0-XFS+athlon.20010116.tar.gz
>     kernel-2.4.0-XFS+athlon.20010118.tar.gz
> 
>  (the missing builds are due to problems in the box that actually builds
>  the kernels) 
> 
>  Has anyone else seen this?
> 
>  TIA,
> 
> --
> Marcelo
> 



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