1 |
Volker Armin Hemmann <volkerarmin@××××××××××.com> [11-01-22 03:04]: |
2 |
> On Friday 21 January 2011 21:05:30 meino.cramer@×××.de wrote: |
3 |
> > Mark Knecht <markknecht@×××××.com> [11-01-21 20:36]: |
4 |
> > > On Fri, Jan 21, 2011 at 11:16 AM, Volker Armin Hemmann |
5 |
> > > <volkerarmin@××××××××××.com> wrote: |
6 |
> > > <SNIP> |
7 |
> > > |
8 |
> > > >> I'm happy to be corrected (by Volker I'm sure) but that's my |
9 |
> > > >> guess |
10 |
> > > >> as to what you're seeing. |
11 |
> > > > |
12 |
> > > > you are confusing bios calls and bios programming chips as.... also |
13 |
> > > > - is there any good reason to use IDE mode? Any? At all? |
14 |
> > > |
15 |
> > > I don't believe I'm 'confusing bios calls with bios programming'. The |
16 |
> > > BIOS can do whatever it wants to in programming the chips as long as |
17 |
> > > grub can still find the kernel. After grub finds the kernel the kernel |
18 |
> > > is free to override whatever chip programming the BIOS has done and |
19 |
> > > reprogram the chips as it sees best. |
20 |
> > > |
21 |
> > > I think the issue meino possibly has is that he likely didn't include |
22 |
> > > an Int13 type driver in the kernel or most likely his system would |
23 |
> > > have booted like it did in the _very_ old days. |
24 |
> > > |
25 |
> > > I agree that there isn't any good reason I know of to use IDE mode |
26 |
> > > unless the other modes the BIOS provides don't work. |
27 |
> > > |
28 |
> > > I cannot get into my Asus BIOS at the moment, but as I remember it |
29 |
> > > Asus gave me something like |
30 |
> > > |
31 |
> > > IDE |
32 |
> > > AHCI |
33 |
> > > AHCI + compatibility |
34 |
> > > |
35 |
> > > IIRC I had to use the last one to get mine to boot but I may be wrong |
36 |
> > > about that. I only mention this as meino is also using Asus so he |
37 |
> > > might look for similar options. |
38 |
> > > |
39 |
> > > - Mark |
40 |
> > |
41 |
> > Hi, |
42 |
> > |
43 |
> > I switched the BIOS from IDE (kernel is using AHCI) to AHCI (kernel |
44 |
> > uses AHCI). The dmesg says (I did a dmesg | grep -i ahci now, previous |
45 |
> > check was done with dmesg | grep AHCI only): |
46 |
> > |
47 |
> > solfire:/root>dmesg | grep -i ahci |
48 |
> > ahci 0000:00:11.0: version 3.0 |
49 |
> > *0* ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 |
50 |
> > *1* ahci 0000:00:11.0: irq 78 for MSI/MSI-X |
51 |
> > *2* ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA |
52 |
> > mode *3* ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio |
53 |
> > slum part scsi0 : ahci |
54 |
> > scsi1 : ahci |
55 |
> > scsi2 : ahci |
56 |
> > scsi3 : ahci |
57 |
> > scsi4 : ahci |
58 |
> > scsi5 : ahci |
59 |
> > ahci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44 |
60 |
> > *4* ahci 0000:07:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA |
61 |
> > mode *5* ahci 0000:07:00.0: flags: 64bit ncq pm led clo pmp pio slum part |
62 |
> > *6* ahci 0000:07:00.0: setting latency timer to 64 |
63 |
> > scsi6 : ahci |
64 |
> > scsi7 : ahci |
65 |
> > |
66 |
> > For me bare eye this looks like the kernel ha switched all seven ports |
67 |
> > to AHCI. Lines marked with "*n*" are still a riddle to me. May be |
68 |
> > Volker will give us some enlightment? |
69 |
> > Why is line *1* of the first block missing in the second block, |
70 |
> > Volker? Why is line *2* talking about "0x3f" while line *4* is using |
71 |
> > "0x3", Volker? Why differ line *5* from line *3*, Volker? What does |
72 |
> > all these flags mean? |
73 |
> > |
74 |
> |
75 |
> you know - there are websites for that. Google is your friend. But even a |
76 |
> glance would reveal to you: |
77 |
> two different chips. |
78 |
> One using MSI for interrupts the second not. |
79 |
> |
80 |
> > I find this interesting: |
81 |
> > |
82 |
> > http://www.linuxquestions.org/questions/linux-hardware-18/6-tips-for-improvi |
83 |
> > ng-hard-drive-performance-835034/ |
84 |
> |
85 |
> it is a start. But the first link there... just saying.. there is no magically |
86 |
> correct value for stride or chunk. |
87 |
> |
88 |
> Oh and if you are using AFT drives make sure the partitions are set up |
89 |
> correctly. |
90 |
> |
91 |
> Also: |
92 |
> https://ata.wiki.kernel.org/index.php/Main_Page |
93 |
> |
94 |
|
95 |
Hi Volker, |
96 |
|
97 |
I have done the partition alignment thingy when I installed my disk a |
98 |
year ago (or so). Thanks for the hint anyway... :) |
99 |
|
100 |
If you know a webite, which explains all that low level stuff like the |
101 |
flags I mentioned I would be happy, if would be so kind to post the |
102 |
link here. |
103 |
|
104 |
Thanks a lot for your help in advance! |
105 |
Best regards, |
106 |
mcc |