From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SN8vn-0005LI-7G for garchives@archives.gentoo.org; Wed, 25 Apr 2012 20:35:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 82D83E052E; Wed, 25 Apr 2012 20:35:05 +0000 (UTC) Received: from mail-iy0-f181.google.com (mail-iy0-f181.google.com [209.85.210.181]) by pigeon.gentoo.org (Postfix) with ESMTP id BF7EBE04E7 for ; Wed, 25 Apr 2012 20:33:50 +0000 (UTC) Received: by iagk10 with SMTP id k10so659771iag.40 for ; Wed, 25 Apr 2012 13:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=d7oeofZ7jRzRO6BrOyupDpqN1R4Xwnp/SyQebSCF+5I=; b=wRlqpswFCMFfvdQOseBeSS2m0sIKeNZy9qnoSV4O1ktNZwq50Ha2P0mLAIMUJyKf/6 dNLznY6HOAr8a3lFWwy3t0yLpLdNNKBAgNWWnWbmLAWDRUPZgZ9fIR2bZsylzfU85gG5 oy89qRQAIZtWX1KnC0FmvhjpDzp7rVsBHMQhTM+DZ9EXgmWgUATl/8JjysKGCbz4Otew CYLne4ZQv4HUHRhZelqInyC8muC5NEDWiciH8G+Qm0/042FseF0j5/Pj0CvVa9zDZc5E VtdS/xBnlhaRFxnOOshRFNcEtj9W6WLLR/OpcNhSkemG6+hUms0UO0WI6tY0zx91TLwd McCQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.50.222.170 with SMTP id qn10mr4045268igc.57.1335386030268; Wed, 25 Apr 2012 13:33:50 -0700 (PDT) Received: by 10.231.205.193 with HTTP; Wed, 25 Apr 2012 13:33:50 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Apr 2012 16:33:50 -0400 Message-ID: Subject: Re: [gentoo-user] 3.2.12 Kenel wont boot From: Simon To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=14dae9341111f8e28804be86c9fc X-Archives-Salt: a67c6126-7d4d-4804-83a8-29e7aaf371ac X-Archives-Hash: 10419545e1d7a3156302c0a86f355d86 --14dae9341111f8e28804be86c9fc Content-Type: text/plain; charset=ISO-8859-1 The error just means it cannot find any device called /dev/sda4, but can only find your CD (sr0). I get this when booting from a usbkey and I need to tell the kernel to wait 5-10 seconds before detecting hdds. I also had this error when I used a config from my "normal" computers onto an older computer that used IDE and PATA (these were disabled in kernel). Good luck! On Wed, Apr 25, 2012 at 4:17 PM, James wrote: > Hello, > > OK, I manage quite a few gentoo systems. > ONE of them is being a BIT _ _ ! and I cannot > figure out what is obviously simple.... > > I have already migrated most system that I manage > to the 3.2.12 kernel (not testing kernels for me > at this time). > > Background: The system is an old HP AMD dual core laptop: > AMD Turion(tm) 64 X2 Mobile Technology TL-56 > > The error message is this: > > Root-NFS: no NFS server address > VFS: Unable to mount root fs via NFS, try floppy > VFS: Cannot open root device "sda4" or unknown block (2,0) > Please append a correct "root=" boot option; > here are the available partitions: > oboo 1048575 sr0 driver:sr > > Kernel panic - not syncing : VFS : Unable to > mount root fs on unknown block(2,0) > PID:1,comm : swapper /0 > Not tainted 3.2.12-gentoo#2 > > The other (3) series kernels boot and run just fine: > from grub.conf: > #0 > title= Linux 3.2.1-gentoo > root(hd0,1) > kernel /boot/kernel-3.2.1-gentoo root=/dev/sda4 > #1 > title= Linux 3.2.12-gentoo > root(hd0,1) > kernel /boot/kernel-3.2.12-gentoo root=/dev/sda4 > #2 > title= Linux 3.0.6-gentoo > root(hd0,1) > kernel /boot/kernel-3.0.6-gentoo root=/dev/sda4 > > I can even scp over a kernel from a single processor AMD64 > laptop and it boots and runs just fine. > > > When I make a new kernel, I do what I have done for years > with Gentoo: > > cd /usr/src > rm linux > ln -sf linux > cd linux > make menuconfig > make && make models_install > > cp System.map /boot/System.map-3.2.12-gentoo > cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo > cp .config /boot/config-3.2.12-gentoo > > > So all I can think of is NFS is the difference? > I cannot seem to flesh out way the new kernel will > not boot on this system and many others are just fine.... > > maybe I'm missing support for the "sr" driver ? > > ideas? > > James > > > > > > --14dae9341111f8e28804be86c9fc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The error just means it cannot find any device c= alled /dev/sda4, but can only find your CD (sr0).

I get this when bo= oting from a usbkey and I need to tell the kernel to wait 5-10 seconds befo= re detecting hdds.=A0 I also had this error when I used a config from my &q= uot;normal" computers onto an older computer that used IDE and PATA (t= hese were disabled in kernel).

Good luck!


On Wed, Apr 25, 2012 a= t 4:17 PM, James <wireless@tampabay.rr.com> wrote:
Hello,

OK, I manage quite a few gentoo systems.
ONE of them is being a BIT _ _ ! and I cannot
figure out what is obviously simple....

I have already migrated most system that I manage
to the 3.2.12 kernel (not testing kernels for me
at this time).

Background: The system is an old HP AMD dual core laptop:
AMD Turion(tm) 64 X2 Mobile Technology TL-56

The error message is this:

Root-NFS: no NFS server address
VFS: Unable to mount root fs via NFS, try floppy
VFS: Cannot open root device "sda4" or unknown block (2,0)
Please append a correct "root=3D" boot option;
here are the available partitions:
oboo =A01048575 sr0 driver:sr

Kernel panic - not syncing : VFS : Unable to
mount root fs on unknown block(2,0)
PID:1,comm : swapper /0
Not tainted 3.2.12-gentoo#2

The other (3) series kernels boot and run just fine:
from grub.conf:
#0
title=3D Linux 3.2.1-gentoo
root(hd0,1)
kernel /boot/kernel-3.2.1-gentoo root=3D/dev/sda4
#1
title=3D Linux 3.2.12-gentoo
root(hd0,1)
kernel /boot/kernel-3.2.12-gentoo root=3D/dev/sda4
#2
title=3D Linux 3.0.6-gentoo
root(hd0,1)
kernel /boot/kernel-3.0.6-gentoo root=3D/dev/sda4

I can even scp over a kernel from a single processor AMD64
laptop and it boots and runs just fine.


When I make a new kernel, I do what I have done for years
with Gentoo:

cd /usr/src
rm linux
ln -sf <latest.kernel> linux
cd linux
make menuconfig <save any changes>
make && make models_install

cp System.map /boot/System.map-3.2.12-gentoo
cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo
cp .config /boot/config-3.2.12-gentoo


So all I can think of is NFS is the difference?
I cannot seem to flesh out way the new kernel will
not boot on this system and many others are just fine....

maybe I'm missing support for the "sr" driver ?

ideas?

James






--14dae9341111f8e28804be86c9fc--