From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PgNGk-0005xi-GF for garchives@archives.gentoo.org; Fri, 21 Jan 2011 20:07:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 92A61E0D72; Fri, 21 Jan 2011 20:05:32 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pigeon.gentoo.org (Postfix) with SMTP id 1AC9CE0D72 for ; Fri, 21 Jan 2011 20:05:31 +0000 (UTC) Received: (qmail invoked by alias); 21 Jan 2011 20:05:31 -0000 Received: from p54850C4A.dip0.t-ipconnect.de (EHLO gmx.net) [84.133.12.74] by mail.gmx.net (mp069) with SMTP; 21 Jan 2011 21:05:31 +0100 X-Authenticated: #20088476 X-Provags-ID: V01U2FsdGVkX1//OuI4ppb/FhedjNIw5GdZksTqwQPCikJOxRdAEV +i2S02IAQSO8fL Received: by gmx.net (nbSMTP-1.00) for uid 1001 Meino.Cramer@gmx.de; Fri, 21 Jan 2011 21:05:31 +0100 (CET) Date: Fri, 21 Jan 2011 21:05:30 +0100 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] AHCI/IDE-question Message-ID: <20110121200530.GA5878@solfire> References: <20110121184507.GC5787@solfire> <4d39db9a.9505df0a.50d3.ffffbf47@mx.google.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: mutt-ng/devel-r804 (Linux) X-Y-GMX-Trusted: 0 X-Archives-Salt: X-Archives-Hash: 72a7d1b5e244f0235af699755c9e084d Mark Knecht [11-01-21 20:36]: > On Fri, Jan 21, 2011 at 11:16 AM, Volker Armin Hemmann > wrote: > > >> > >> =A0 =A0I'm happy to be corrected (by Volker I'm sure) but that's my gu= ess > >> as to what you're seeing. > > > > you are confusing bios calls and bios programming chips as.... also - i= s there > > any good reason to use IDE mode? Any? At all? >=20 > I don't believe I'm 'confusing bios calls with bios programming'. The > BIOS can do whatever it wants to in programming the chips as long as > grub can still find the kernel. After grub finds the kernel the kernel > is free to override whatever chip programming the BIOS has done and > reprogram the chips as it sees best. >=20 > I think the issue meino possibly has is that he likely didn't include > an Int13 type driver in the kernel or most likely his system would > have booted like it did in the _very_ old days. >=20 > I agree that there isn't any good reason I know of to use IDE mode > unless the other modes the BIOS provides don't work. >=20 > I cannot get into my Asus BIOS at the moment, but as I remember it > Asus gave me something like >=20 > IDE > AHCI > AHCI + compatibility >=20 > IIRC I had to use the last one to get mine to boot but I may be wrong > about that. I only mention this as meino is also using Asus so he > might look for similar options. >=20 > - Mark >=20 Hi, I switched the BIOS from IDE (kernel is using AHCI) to AHCI (kernel uses AHCI). The dmesg says (I did a dmesg | grep -i ahci now, previous check was done with dmesg | grep AHCI only): solfire:/root>dmesg | grep -i ahci ahci 0000:00:11.0: version 3.0 *0* ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 *1* ahci 0000:00:11.0: irq 78 for MSI/MSI-X *2* ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SAT= A mode *3* ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum p= art scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci scsi4 : ahci scsi5 : ahci ahci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44 *4* ahci 0000:07:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA= mode *5* ahci 0000:07:00.0: flags: 64bit ncq pm led clo pmp pio slum part *6* ahci 0000:07:00.0: setting latency timer to 64 scsi6 : ahci scsi7 : ahci For me bare eye this looks like the kernel ha switched all seven ports to AHCI. Lines marked with "*n*" are still a riddle to me. May be Volker will give us some enlightment? Why is line *1* of the first block missing in the second block, Volker? Why is line *2* talking about "0x3f" while line *4* is using "0x3", Volker? Why differ line *5* from line *3*, Volker? What does all these flags mean? I find this interesting: http://www.linuxquestions.org/questions/linux-hardware-18/6-tips-for-improv= ing-hard-drive-performance-835034/ Best regards, mcc