Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Sep 2003 16:05:11 -0500
From:      David Leimbach <leimy2k@mac.com>
To:        Will Andrews <will@csociety.org>
Cc:        Soren Schmidt <sos@spider.deepcore.dk>
Subject:   Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
Message-ID:  <9D00B12E-F2C0-11D7-A349-0003937E39E0@mac.com>
In-Reply-To: <20030929193808.GT72999@procyon.firepipe.net>
References:  <61180692781.20030929202947@buz.ch> <200309291913.h8TJDmCI013173@spider.deepcore.dk> <20030929193808.GT72999@procyon.firepipe.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Hey Will and Soren! :)
On Sep 29, 2003, at 2:38 PM, Will Andrews wrote:

> On Mon, Sep 29, 2003 at 09:13:48PM +0200, Soren Schmidt wrote:
>> First off, there is ONLY support for Promise and HPT "soft RAID"
>> in the ATA driver, other vendors products are *not* supported (yet).
>>
>> Second, there seem to be a problem with some sil3112 setups where
>> timeouts and what not ruins the lunch, but so far I've not been
>> able to reproduce..
>
> I am still unable to use my SATA drive, it's probed incorrectly
> as I posted earlier.  Reverting to the August 10th 00:00 UTC
> kernel fixes this problem, so I concluded that ATAng broke this.
>

I am not running a very recent CURRENT but I do have ATAng from a fairly
early point and it works here.  [I have the same chipset as Will 
SiI3112A RAID]

> If it makes any difference, my model is a SiI3112 RAID
> controller, but I only have one drive and it probes as ad4... the
> situation doesn't improve any if I add "ataraid".  But maybe
> ATAng doesn't take into account the difference between a "normal"
> and a "RAID" SiI 3112, if any?
>

Even Linux probes both disks even though I have but one.

I don't use any RAID capabilities beyond enabling the hardware to access
SATA.

> Here are my dmesg's again (Sep 18th, Aug 10th kernels):
> http://csociety.org/~will/dmesg.badATAng
> http://csociety.org/~will/dmesg.Aug10.preATAng
>
> The problem shown in the first dmesg still showed itself when I
> tried a new kernel on Sep 25th.
>

I'd have to reboot and see how recent my FreeBSD stuff is... I have been
rather distracted by the job which pays me salary :).

> Regards,
> -- 
> wca
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D00B12E-F2C0-11D7-A349-0003937E39E0>