1 |
Hi Mike, |
2 |
|
3 |
thank you for your explanations! :) |
4 |
|
5 |
But.... |
6 |
|
7 |
|
8 |
Mike Edenfield <kutulu@××××××.org> [11-01-21 21:48]: |
9 |
> On 1/21/2011 3:05 PM, meino.cramer@×××.de wrote: |
10 |
> |
11 |
> > solfire:/root>dmesg | grep -i ahci |
12 |
> > ahci 0000:00:11.0: version 3.0 |
13 |
> > *0* ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 |
14 |
> > *1* ahci 0000:00:11.0: irq 78 for MSI/MSI-X |
15 |
> > *2* ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode |
16 |
> > *3* ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part |
17 |
> |
18 |
> > ahci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44 |
19 |
> > *4* ahci 0000:07:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode |
20 |
> > *5* ahci 0000:07:00.0: flags: 64bit ncq pm led clo pmp pio slum part |
21 |
> > *6* ahci 0000:07:00.0: setting latency timer to 64 |
22 |
> |
23 |
> > For me bare eye this looks like the kernel ha switched all seven ports |
24 |
> > to AHCI. |
25 |
> |
26 |
> To say that the kernel "switched" the ports is probably misleading. The |
27 |
> kernel is just trying to hook up the devices it finds to the device |
28 |
> drivers it has available. |
29 |
> |
30 |
> You told the kernel it was ok to use the AHCI driver. The kernel |
31 |
> located those ports, detected that they supported the AHCI interface, |
32 |
> and thus, attached the AHCI SATA driver to them. If you had told your |
33 |
> BIOS that those ports should be operated as IDE instead of AHCI, then |
34 |
> the kernel wouldn't have found any supported AHCI hardware and you |
35 |
> probably wouldn't be able to boot. |
36 |
|
37 |
.....before the BIOS was set to IDE the kernel used AHCI. |
38 |
After switching the BIOS to AHCI the kernel acts identical to |
39 |
what it did before. |
40 |
|
41 |
So it seems, that the BIOS has no influence. Mark mentioned this |
42 |
before. |
43 |
|
44 |
Only switching the kernel to IDE (only for experimenting) leads |
45 |
to a non-bootable system. |
46 |
|
47 |
|
48 |
> > Why is line *1* of the first block missing in the second block, |
49 |
> > Volker? Why is line *2* talking about "0x3f" while line *4* is using |
50 |
> > "0x3", Volker? Why differ line *5* from line *3*, Volker? What does |
51 |
> > all these flags mean? |
52 |
> |
53 |
> You could also dig into the internals of the libahci.c driver to figure |
54 |
> out what all of those display items mean. In this case, your seeing two |
55 |
> different PCI busses with slightly different capabilities; just off the |
56 |
> top of my head, one is probably a 6-port PCI-X bus and the other a |
57 |
> 2-port PCI bus, but I'd have to go look up the specs to your motherboard |
58 |
> to really find out. |
59 |
|
60 |
Ok, I save this for tommorrow. Here it is now 21r:59 in the evening |
61 |
and I stood up 3:40 this night/morning today. |
62 |
I think, there is enough AHCI and IDE left for tommorow... :) |
63 |
|
64 |
|
65 |
> --Mike |
66 |
> |
67 |
|
68 |
Thanks to you all who have helped ! |
69 |
|
70 |
mcc |