1 |
On Wed, May 6, 2009 at 4:38 PM, maxim wexler <blissfix@×××××.com> wrote: |
2 |
|
3 |
> |
4 |
> > # CONFIG_BLK_DEV_IDE_SATA is not set |
5 |
> |
6 |
> deprecated, possible conflict but I set it anyway |
7 |
> |
8 |
> > # CONFIG_SATA_AHCI is not set |
9 |
> |
10 |
> doubtful if I need it but set it anyway |
11 |
> |
12 |
> > # CONFIG_SATA_PMP is not set |
13 |
> |
14 |
> definitely nothing to do with my system, didn't set it. |
15 |
> |
16 |
> > |
17 |
> > Not sure, anyway, try it... |
18 |
> > |
19 |
> |
20 |
> Still panics! Same place, same message. |
21 |
> |
22 |
> Guess I'll try that initrd thing next. |
23 |
|
24 |
|
25 |
If you're building all of your drivers into the kernel statically (=y/*) and |
26 |
not as modules (=m), then using an initrd will not help you in the least - |
27 |
it is only useful in a situation like this when you need additional |
28 |
"modularized" drivers loaded before the kernel will see your rootfs. |
29 |
|
30 |
How did you initially get your Gentoo install on there - what did you boot - |
31 |
CD or USB? You should be able to boot that medium again, then check to see |
32 |
what driver it is using for the drive controller. I'm sure there's a more |
33 |
direct way to do this, but here is how I can easily find the info: |
34 |
|
35 |
cd /sys/block |
36 |
ls -al |
37 |
(should show something like): |
38 |
|
39 |
|
40 |
total 0 |
41 |
drwxr-xr-x 2 root root 0 May 6 16:48 . |
42 |
drwxr-xr-x 12 root root 0 Apr 22 10:49 .. |
43 |
lrwxrwxrwx 1 root root 0 May 6 16:51 fd0 -> |
44 |
../devices/platform/floppy.0/block/fd0 |
45 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop0 -> |
46 |
../devices/virtual/block/loop0 |
47 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop1 -> |
48 |
../devices/virtual/block/loop1 |
49 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop2 -> |
50 |
../devices/virtual/block/loop2 |
51 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop3 -> |
52 |
../devices/virtual/block/loop3 |
53 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop4 -> |
54 |
../devices/virtual/block/loop4 |
55 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop5 -> |
56 |
../devices/virtual/block/loop5 |
57 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop6 -> |
58 |
../devices/virtual/block/loop6 |
59 |
lrwxrwxrwx 1 root root 0 May 6 16:51 loop7 -> |
60 |
../devices/virtual/block/loop7 |
61 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram0 -> ../devices/virtual/block/ram0 |
62 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram1 -> ../devices/virtual/block/ram1 |
63 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram10 -> |
64 |
../devices/virtual/block/ram10 |
65 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram11 -> |
66 |
../devices/virtual/block/ram11 |
67 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram12 -> |
68 |
../devices/virtual/block/ram12 |
69 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram13 -> |
70 |
../devices/virtual/block/ram13 |
71 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram14 -> |
72 |
../devices/virtual/block/ram14 |
73 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram15 -> |
74 |
../devices/virtual/block/ram15 |
75 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram2 -> ../devices/virtual/block/ram2 |
76 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram3 -> ../devices/virtual/block/ram3 |
77 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram4 -> ../devices/virtual/block/ram4 |
78 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram5 -> ../devices/virtual/block/ram5 |
79 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram6 -> ../devices/virtual/block/ram6 |
80 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram7 -> ../devices/virtual/block/ram7 |
81 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram8 -> ../devices/virtual/block/ram8 |
82 |
lrwxrwxrwx 1 root root 0 May 6 16:51 ram9 -> ../devices/virtual/block/ram9 |
83 |
lrwxrwxrwx 1 root root 0 May 6 16:51 sda -> |
84 |
../devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda |
85 |
lrwxrwxrwx 1 root root 0 May 6 16:51 sdb -> |
86 |
../devices/pci0000:00/0000:00:1f.2/host3/target3:0:0/3:0:0:0/block/sdb |
87 |
lrwxrwxrwx 1 root root 0 May 6 16:51 sdc -> |
88 |
../devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host83/target83:0:0/83:0:0:0/block/sdc |
89 |
lrwxrwxrwx 1 root root 0 May 6 16:51 sr0 -> |
90 |
../devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sr0 |
91 |
|
92 |
|
93 |
Find your hard drive (let's use sda as the example here), and cd into the |
94 |
link up to the hostX part: |
95 |
|
96 |
cd ../devices/pci0000:00/0000:00:1f.2/ |
97 |
ls -al driver |
98 |
(should show something like) |
99 |
lrwxrwxrwx 1 root root 0 May 6 16:49 driver -> |
100 |
../../../bus/pci/drivers/ata_piix |
101 |
|
102 |
From this I can tell that it is the "ata_piix" driver that is used for the |
103 |
controller that my sda disk is connected to. From there you can modify your |
104 |
kernel config to include the correct driver (compiled statically, I'd |
105 |
recommend, for your root device at least), and then you should be good to |
106 |
go. |
107 |
|
108 |
|
109 |
HTH- |
110 |
|
111 |
-James |
112 |
|
113 |
|
114 |
|
115 |
> |
116 |
> mw |
117 |
> |
118 |
> |
119 |
> __________________________________________________________________ |
120 |
> Connect with friends from any web browser - no download required. Try the |
121 |
> new Yahoo! Canada Messenger for the Web BETA at |
122 |
> http://ca.messenger.yahoo.com/webmessengerpromo.php |
123 |
> |
124 |
> |