| 1 |
Mark Knecht <markknecht@×××××.com> [11-01-21 20:36]: |
| 2 |
> On Fri, Jan 21, 2011 at 11:16 AM, Volker Armin Hemmann |
| 3 |
> <volkerarmin@××××××××××.com> wrote: |
| 4 |
> <SNIP> |
| 5 |
> >> |
| 6 |
> >> I'm happy to be corrected (by Volker I'm sure) but that's my guess |
| 7 |
> >> as to what you're seeing. |
| 8 |
> > |
| 9 |
> > you are confusing bios calls and bios programming chips as.... also - is there |
| 10 |
> > any good reason to use IDE mode? Any? At all? |
| 11 |
> |
| 12 |
> I don't believe I'm 'confusing bios calls with bios programming'. The |
| 13 |
> BIOS can do whatever it wants to in programming the chips as long as |
| 14 |
> grub can still find the kernel. After grub finds the kernel the kernel |
| 15 |
> is free to override whatever chip programming the BIOS has done and |
| 16 |
> reprogram the chips as it sees best. |
| 17 |
> |
| 18 |
> I think the issue meino possibly has is that he likely didn't include |
| 19 |
> an Int13 type driver in the kernel or most likely his system would |
| 20 |
> have booted like it did in the _very_ old days. |
| 21 |
> |
| 22 |
> I agree that there isn't any good reason I know of to use IDE mode |
| 23 |
> unless the other modes the BIOS provides don't work. |
| 24 |
> |
| 25 |
> I cannot get into my Asus BIOS at the moment, but as I remember it |
| 26 |
> Asus gave me something like |
| 27 |
> |
| 28 |
> IDE |
| 29 |
> AHCI |
| 30 |
> AHCI + compatibility |
| 31 |
> |
| 32 |
> IIRC I had to use the last one to get mine to boot but I may be wrong |
| 33 |
> about that. I only mention this as meino is also using Asus so he |
| 34 |
> might look for similar options. |
| 35 |
> |
| 36 |
> - Mark |
| 37 |
> |
| 38 |
|
| 39 |
Hi, |
| 40 |
|
| 41 |
I switched the BIOS from IDE (kernel is using AHCI) to AHCI (kernel |
| 42 |
uses AHCI). The dmesg says (I did a dmesg | grep -i ahci now, previous |
| 43 |
check was done with dmesg | grep AHCI only): |
| 44 |
|
| 45 |
solfire:/root>dmesg | grep -i ahci |
| 46 |
ahci 0000:00:11.0: version 3.0 |
| 47 |
*0* ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 |
| 48 |
*1* ahci 0000:00:11.0: irq 78 for MSI/MSI-X |
| 49 |
*2* ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode |
| 50 |
*3* ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part |
| 51 |
scsi0 : ahci |
| 52 |
scsi1 : ahci |
| 53 |
scsi2 : ahci |
| 54 |
scsi3 : ahci |
| 55 |
scsi4 : ahci |
| 56 |
scsi5 : ahci |
| 57 |
ahci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44 |
| 58 |
*4* ahci 0000:07:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode |
| 59 |
*5* ahci 0000:07:00.0: flags: 64bit ncq pm led clo pmp pio slum part |
| 60 |
*6* ahci 0000:07:00.0: setting latency timer to 64 |
| 61 |
scsi6 : ahci |
| 62 |
scsi7 : ahci |
| 63 |
|
| 64 |
For me bare eye this looks like the kernel ha switched all seven ports |
| 65 |
to AHCI. Lines marked with "*n*" are still a riddle to me. May be |
| 66 |
Volker will give us some enlightment? |
| 67 |
Why is line *1* of the first block missing in the second block, |
| 68 |
Volker? Why is line *2* talking about "0x3f" while line *4* is using |
| 69 |
"0x3", Volker? Why differ line *5* from line *3*, Volker? What does |
| 70 |
all these flags mean? |
| 71 |
|
| 72 |
I find this interesting: |
| 73 |
|
| 74 |
http://www.linuxquestions.org/questions/linux-hardware-18/6-tips-for-improving-hard-drive-performance-835034/ |
| 75 |
|
| 76 |
|
| 77 |
Best regards, |
| 78 |
mcc |
Archives