Re: [gentoo-user] can't stop the panic on eeepc

[James Ausmus <james.ausmus@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 4509 bytes --]

On Wed, May 6, 2009 at 4:38 PM, maxim wexler <blissfix@yahoo.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 (=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
>
>

[-- Attachment #2: Type: text/html, Size: 5552 bytes --]