solution (was: Re: Kernel-Version Problem (wrong uname output))

--MGYHOYXEY6WxJCY8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Sorry, I've forgotten to send the attached mail to the list!

Florian
-- 
Florian Rossol
 gpg-key:	http://www.stud.uni-hannover.de/~ruessel/gnupg.html

--MGYHOYXEY6WxJCY8
Content-Type: message/rfc822
Content-Disposition: inline

Date: Sun, 27 Oct 2002 19:04:17 +0100
From: Florian Rossol <[email protected]>
To: Guy <[email protected]>
Subject: solution (was: Re: [gentoo-newbies] Kernel-Version Problem (wrong uname output))
Message-ID: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
User-Agent: Mutt/1.3.27i

On Sun, Oct 27, 2002 at 07:59:54AM -0500, Guy wrote:
> The problems you described still point to a different kernel.

You are right.

> Normally, a fresh Gentoo install on a newly formatted drive
> would install a boot kernel named 'bzImage'. Not 'vmlinuz'.

Yes, I know. That wasn't the problem.

> Did you check /usr/src/linux/arch/i386/boot/bzImage and
> compare it to whatever you have in /boot?

It's the same.

My fault was my lilo-configuration. I use lilo because I normaly use
SuSE-Linux and installed gentoo for testing. My wrong lilo-config
booted the kernel from SuSE-Linux with the root-partition of gentoo.

Thanks for your help

Florian


-- 
Florian Rossol
 gpg-key:	http://www.stud.uni-hannover.de/~ruessel/gnupg.html

--MGYHOYXEY6WxJCY8--