Date: Sun, 18 Apr 2010 11:39:35 +0100 From: Rui Paulo <rpaulo@freebsd.org> To: Alexander Motin <mav@FreeBSD.org> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: SPOOFED: Re: SVN rev 206755 breakage Message-ID: <987831E7-4893-4F2F-B96F-A1E25BD9BCA0@freebsd.org> In-Reply-To: <4BCA9F44.50002@FreeBSD.org> References: <4BCA325A.1060600@protected-networks.net> <mailpost.1271550720.7316110.69309.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> <4BCA9F44.50002@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 Apr 2010, at 06:57, Alexander Motin wrote: > Rui Paulo wrote: >> On 17 Apr 2010, at 23:12, Michael Butler wrote: >>> On 04/17/10 18:05, Rui Paulo wrote: >>>> On 17 Apr 2010, at 22:34, Michael Butler wrote: >>>>> The revision labeled: >>>>> >>>>> SVN rev 206755 on 2010-04-17 11:40:39Z by rpaulo >>>>> >>>>> Add another ICH7M chipset that works. >>>>> >>>>> .. is incorrect and will cause some laptops to not boot. >>>> So, in AHCI mode it doesn't find the disks? >>> No - the driver fails to attach (ENXIO). >> >> But since ahci failed to attach, won't atapci attach later? > > If probe succeeded - no. > >> Can you show me the dmesg? > > More important probably would be `pciconf -lvcb`. > > Intel controllers after ICH6 change both ID and set of resources, > depending on AHCI enabled in BIOS. There is separate set of IDs for > controllers with AHCI enabled. As I can see, Linux handles ID 0x27c4 as > non-AHCI SATA. If for some reason this ID could be used for both modes > (I have doubts), It can be used in both modes. atapci used to attach to it on my MacBook. > we may try to set AHCI_Q_NOFORCE flag to make driver > check PCI class/subclass, if it is correct there. Regards, -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?987831E7-4893-4F2F-B96F-A1E25BD9BCA0>