Date: Sun, 2 Dec 2001 17:54:25 +1030 From: Greg Lehey <grog@FreeBSD.org> To: rsharpe@ns.aus.com Cc: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@freebsd.dk>, Zwane Mwaikambo <zwane@linux.realnet.co.sz>, freebsd-hackers@FreeBSD.org Subject: Re: UDMA33 and SiS5591 on FreeBSD 4.4-RELEASE Message-ID: <20011202175425.F61248@monorchid.lemis.com> In-Reply-To: <3C09D6F9.7070504@ns.aus.com> References: <Pine.LNX.4.33.0112011343270.11026-100000@netfinity.realnet.co.sz> <200112011205.fB1C5r243828@freebsd.dk> <20011202115509.B61248@monorchid.lemis.com> <3C09D6F9.7070504@ns.aus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 2 December 2001 at 17:53:37 +1030, Richard Sharpe wrote:
> Greg Lehey wrote:
>> On Saturday, 1 December 2001 at 13:05:53 +0100, Søren Schmidt wrote:
>>
>>> It seems Zwane Mwaikambo wrote:
>>>
>>>> Hi,
>>>> I've got a box which boots up with UDMA33 but during the boot
>>>> sequence gets write problems and ends up disabling it and i presume
>>>> falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have
>>>> had no problems running it at UDMA33.
>>>>
>>>> Host: SiS 5591 (revision?)
>>>> Disk: Seagate 3.2G ATA2
>>>>
>>> Ohhh, I need alot more info before I can tell whats going on..
>>> I need at least the dmesg from a verbosely booted system and
>>> also a pciconf -l to tell what chips you have.
>>
>> Note that there are other chips out there which return the same PCI
>> information but which appear to be capable of ATA 100. I recently
>> gave a patch to Richard Sharpe (copied) which he says was able to get
>> his "SiS 5591" to run at ATA 100. I'm still waiting for feedback from
>> him before forwarding it to you. I also have a machine with a "SiS
>
> Attached is the patch I am using, which is based on what Greg gave me.
> It tries UDMA5 first, and steps down ...
I'd really appreciate the dmesg output, in particular this line:
> + if (bootverbose)
> + printf ("SiS 5513/5591, udmamode %d\n", udmamode);
Hmm. I suppose you didn't do a verbose boot. Could you try it,
please?
Also, you said (elsewhere) you had some issues with the attached file.
What were they?
Greg
--
See complete headers for address and phone numbers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011202175425.F61248>