Date: Thu, 1 Nov 2012 19:15:53 +0100 From: Michael Schuh <michael.schuh@gmail.com> To: freebsd-hackers@freebsd.org Subject: ata-intel.c - Intel ICH(7) Controller working modes Message-ID: <CADwRVEYGr1ckpPRBBGcEvAJHQS6MyMksAV0dXwNN6gD_qH-ftg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi @all, after a nightmare of digging the Internet, testing this, testing that, etc i have found a (temporary possible) Solution for a bug, that i reported: http://www.freebsd.org/cgi/query-pr.cgi?pr=173251 This bug is related to ( ?all? ) Machines that are based on INTEL-ICH chipsets withouth the possibility to change its working mode from (compatibility) IDE to AHCI. FreeBSD could not detect any SATA drive. There is no BIOS option to change the working mode of the ICH controller. As you can read in my follow-ups i had to patch the kernel back to its old behavior prior to 8.3 RELEASE. Just that can't be the solution. May be i haven't seen anything that would to get pushed into the loader.conf, but i didn't found anything related that helped. +TUNABLE_INT("hw.ahci.force", &force_ahci); <<< The only thing i found in relation to this. just that didn't worked. May be a more experienced developer can take a look on it and find a way to set the controllers into the new AHCI working mode or fallback to IDE mode if failed on boot time? here some deeper knowledge about the settings. http://rants.atmurray.net/2009/06/sata-ahci-mode-on-systems-without-bios.html It seems that this is not persistent and gets everytime changed back from the Systems BIOS or the chip itself on initialization. in the article is also mentioned that not all chipsets supports ahci. while the author is referring to the same kind of machine, i think it should be possible to swithc the controller to ahci in my case. i could patch back the kernels ata-intel.c driver, just no idea what this means in deep and how i can put the stuff from the article above into it. to enforce a check before the driver gets loaded. i am not a kern developer. i am grateful for any hint or help. from my point of view it would be nice if we can get a working solution into the kernel, so people that use those machines didn't have to patch their kernels all the time. i found more ppl. with that problem. many thanks michael p.s. i am not member of that mailing list, so i will see only answers sent to myself (not only to the list)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADwRVEYGr1ckpPRBBGcEvAJHQS6MyMksAV0dXwNN6gD_qH-ftg>