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 1M1qyr-0001Wy-RM for garchives@archives.gentoo.org; Wed, 06 May 2009 23:56:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D0110E08FC; Wed, 6 May 2009 23:56:52 +0000 (UTC) Received: from mail-gx0-f176.google.com (mail-gx0-f176.google.com [209.85.217.176]) by pigeon.gentoo.org (Postfix) with ESMTP id 9E108E08FC for ; Wed, 6 May 2009 23:56:52 +0000 (UTC) Received: by gxk24 with SMTP id 24so1058189gxk.10 for ; Wed, 06 May 2009 16:56:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=jmX3zUWuYLSgeIql7KipaNWf+xK65qjxnuCCwoqzRBE=; b=C+tI4eaZQkz8jVQHehVq1ps8sr37DSM7zxqio39TelfQiLrUCbRX69ZlzDcA2i2WMx qJa+kkl152CcQuQWJqhxdnAG11ZoQX39bxH2Hvo2gdQvTGUakXREPsVmfcNBemrR0Ylv T7ceE3CEgIhac5B5dMOoS1wff4+j2qL8/QFpE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=G85I18KyUwlzDIuFqLT81hDKem9jpbn4VtM5mAL/LrQQoweEeQ7te6/6Qwq4oWKkwC mjLDa0B4a162IIAE3b1w7hxbL1i6fcDLrYqOWcGAdW4kvwDnLPylOwNkCdi40uA6EOvn qOWrJgnWNOuxKnN0Ismwxg4cfoGHulrfuMlBA= 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.90.70.15 with SMTP id s15mr1524414aga.42.1241654212300; Wed, 06 May 2009 16:56:52 -0700 (PDT) In-Reply-To: <53673.4294.qm@web31606.mail.mud.yahoo.com> References: <53673.4294.qm@web31606.mail.mud.yahoo.com> Date: Wed, 6 May 2009 16:56:52 -0700 Message-ID: Subject: Re: [gentoo-user] can't stop the panic on eeepc From: James Ausmus To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=00163630f0ef42122204694726f4 X-Archives-Salt: 751bc25a-cf8f-4ea9-a928-f54578f65f6a X-Archives-Hash: 628a4ed22502e36fd74af9fe5d8bfd06 --00163630f0ef42122204694726f4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Wed, May 6, 2009 at 4:38 PM, maxim wexler wrote: > > > # CONFIG_BLK_DEV_IDE_SATA is not set > > deprecated, possible conflict but I set it anyway > > > # CONFIG_SATA_AHCI is not set > > doubtful if I need it but set it anyway > > > # CONFIG_SATA_PMP is not set > > definitely nothing to do with my system, didn't set it. > > > > > Not sure, anyway, try it... > > > > Still panics! Same place, same message. > > Guess I'll try that initrd thing next. If you're building all of your drivers into the kernel statically (=y/*) and not as modules (=m), then using an initrd will not help you in the least - it is only useful in a situation like this when you need additional "modularized" drivers loaded before the kernel will see your rootfs. How did you initially get your Gentoo install on there - what did you boot - CD or USB? You should be able to boot that medium again, then check to see what driver it is using for the drive controller. I'm sure there's a more direct way to do this, but here is how I can easily find the info: cd /sys/block ls -al (should show something like): total 0 drwxr-xr-x 2 root root 0 May 6 16:48 . drwxr-xr-x 12 root root 0 Apr 22 10:49 .. lrwxrwxrwx 1 root root 0 May 6 16:51 fd0 -> ../devices/platform/floppy.0/block/fd0 lrwxrwxrwx 1 root root 0 May 6 16:51 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 May 6 16:51 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 May 6 16:51 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 May 6 16:51 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 May 6 16:51 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 May 6 16:51 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 May 6 16:51 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 May 6 16:51 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 May 6 16:51 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 May 6 16:51 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 May 6 16:51 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 May 6 16:51 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 May 6 16:51 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 May 6 16:51 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 May 6 16:51 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 May 6 16:51 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 May 6 16:51 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 May 6 16:51 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 May 6 16:51 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 May 6 16:51 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 May 6 16:51 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 May 6 16:51 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 May 6 16:51 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 May 6 16:51 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 May 6 16:51 sda -> ../devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda lrwxrwxrwx 1 root root 0 May 6 16:51 sdb -> ../devices/pci0000:00/0000:00:1f.2/host3/target3:0:0/3:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 May 6 16:51 sdc -> ../devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host83/target83:0:0/83:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 May 6 16:51 sr0 -> ../devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sr0 Find your hard drive (let's use sda as the example here), and cd into the link up to the hostX part: cd ../devices/pci0000:00/0000:00:1f.2/ ls -al driver (should show something like) lrwxrwxrwx 1 root root 0 May 6 16:49 driver -> ../../../bus/pci/drivers/ata_piix >From this I can tell that it is the "ata_piix" driver that is used for the controller that my sda disk is connected to. From there you can modify your kernel config to include the correct driver (compiled statically, I'd recommend, for your root device at least), and then you should be good to go. HTH- -James > > mw > > > __________________________________________________________________ > Connect with friends from any web browser - no download required. Try the > new Yahoo! Canada Messenger for the Web BETA at > http://ca.messenger.yahoo.com/webmessengerpromo.php > > --00163630f0ef42122204694726f4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, May 6, 2009 at 4:38 PM, maxim we= xler <blissfix@y= ahoo.com> wrote:

> # CONFIG_BLK_DEV_IDE_SATA is not set

deprecated, possible conflict but I set it anyway

> # CONFIG_SATA_AHCI is not set

doubtful if I need it but set it anyway

> # CONFIG_SATA_PMP is not set

definitely nothing to do with my system, didn't set it.

>
> Not sure, anyway, try it...
>

Still panics! Same place, same message.

Guess I'll try that initrd thing next.

If you'= re building all of your drivers into the kernel statically (=3Dy/*) and not= as modules (=3Dm), then using an initrd will not help you in the least - i= t is only useful in a situation like this when you need additional "mo= dularized" drivers loaded before the kernel will see your rootfs.

How did you initially get your Gentoo install on there - what did you b= oot - CD or USB? You should be able to boot that medium again, then check t= o see what driver it is using for the drive controller. I'm sure there&= #39;s a more direct way to do this, but here is how I can easily find the i= nfo:

cd /sys/block
ls -al
(should show something like):


tot= al 0
drwxr-xr-x=A0 2 root root 0 May=A0 6 16:48 .
drwxr-xr-x 12 root = root 0 Apr 22 10:49 ..
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 fd0 -&= gt; ../devices/platform/floppy.0/block/fd0
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop0 -> ../devices/virtual/b= lock/loop0
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop1 -> ../dev= ices/virtual/block/loop1
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop= 2 -> ../devices/virtual/block/loop2
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop3 -> ../devices/virtual/b= lock/loop3
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop4 -> ../dev= ices/virtual/block/loop4
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop= 5 -> ../devices/virtual/block/loop5
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop6 -> ../devices/virtual/b= lock/loop6
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 loop7 -> ../dev= ices/virtual/block/loop7
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram0= -> ../devices/virtual/block/ram0
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram1 -> ../devices/virtual/bl= ock/ram1
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram10 -> ../devic= es/virtual/block/ram10
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram11 = -> ../devices/virtual/block/ram11
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram12 -> ../devices/virtual/b= lock/ram12
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram13 -> ../dev= ices/virtual/block/ram13
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram1= 4 -> ../devices/virtual/block/ram14
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram15 -> ../devices/virtual/b= lock/ram15
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram2 -> ../devi= ces/virtual/block/ram2
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram3 -= > ../devices/virtual/block/ram3
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram4 -> ../devices/virtual/bl= ock/ram4
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram5 -> ../device= s/virtual/block/ram5
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram6 -&g= t; ../devices/virtual/block/ram6
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram7 -> ../devices/virtual/bl= ock/ram7
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram8 -> ../device= s/virtual/block/ram8
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 ram9 -&g= t; ../devices/virtual/block/ram9
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 sda -> ../devices/pci0000:00/= 0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx=A0 1 root ro= ot 0 May=A0 6 16:51 sdb -> ../devices/pci0000:00/0000:00:1f.2/host3/targ= et3:0:0/3:0:0:0/block/sdb
lrwxrwxrwx=A0 1 root root 0 May=A0 6 16:51 sdc -> ../devices/pci0000:00/= 0000:00:1d.7/usb1/1-3/1-3:1.0/host83/target83:0:0/83:0:0:0/block/sdc
lrw= xrwxrwx=A0 1 root root 0 May=A0 6 16:51 sr0 -> ../devices/pci0000:00/000= 0:00:1f.1/host0/target0:0:0/0:0:0:0/block/sr0
=A0

Find your hard drive (let's use sda as the example here), an= d cd into the link up to the hostX part:

cd ../devices/pci0000:00/00= 00:00:1f.2/
ls -al driver
(should show something like)
lrwxrwxrwx = 1 root root 0 May=A0 6 16:49 driver -> ../../../bus/pci/drivers/ata_piix=

From this I can tell that it is the "ata_piix" driver that is= used for the controller that my sda disk is connected to. From there you c= an modify your kernel config to include the correct driver (compiled static= ally, I'd recommend, for your root device at least), and then you shoul= d be good to go.


HTH-

-James




mw


=A0 =A0 =A0_______________________________________________________________= ___
Connect with friends from any web browser - no download required. Try the n= ew Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.y= ahoo.com/webmessengerpromo.php


--00163630f0ef42122204694726f4--