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 1SN90G-0005xb-8W for garchives@archives.gentoo.org; Wed, 25 Apr 2012 20:39:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D0CE5E05F9; Wed, 25 Apr 2012 20:39:17 +0000 (UTC) Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 10062E05B4 for ; Wed, 25 Apr 2012 20:36:59 +0000 (UTC) Received: by vbbfc26 with SMTP id fc26so454639vbb.40 for ; Wed, 25 Apr 2012 13:36:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=ru60zwV4LQ/EDQ5COrxwCq9QbbdjbCT3994/1Rk3ZBs=; b=zYH+E3BR77Op92dwxia2bOZFaFs5SIrCVRKZxFQh10wTMIrzfuFNrDJcYtJqi6NkkD HcECDlwAG271nyynyV7Ewg2mOx6VBlmAnHQJf2PY2nPbiHJuaExmCbGjkeE40zwaCt/h a8DXqeZEOA/rmPlyG/JzjKFUg9nCkMhIl6YkWTNjU0I2SHO3pD6qhudK3C67zEJx9Spz igvbPXckeS+VoKmeQaqur6WfqhMwpPWvIQcz0pmiUYfYPiIO2yUVOGhab9anEWivdx4k BveuIDTO1nfE/MMsfxdWWq8n7lplIQQZaFIpoWp6i0/wZSygNpT4WEAMyCiqxAHVVTMm mlmQ== 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.220.227.70 with SMTP id iz6mr4023929vcb.29.1335386219512; Wed, 25 Apr 2012 13:36:59 -0700 (PDT) Received: by 10.220.227.7 with HTTP; Wed, 25 Apr 2012 13:36:59 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 Apr 2012 05:36:59 +0900 Message-ID: Subject: Re: [gentoo-user] 3.2.12 Kenel wont boot From: Seong-ho Cho To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 5ac18ec6-cad7-4395-a486-96cdde5b4ff0 X-Archives-Hash: ebb2d455cd512f8a0f7061541793e128 well ... what is filesystem of sr? then ... did you check that filesystem item [M] instead of [*] ?? if you want to use some specific file system you may make sure whether you checked correspond filesystem by * or not. I don't know how did you set many objects but I believe that you already know what this problem causes Cheers :D Seong-ho, Cho 2012/4/26 James : > 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 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 > > > > >