linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tomasz  B±tor" <tomba@bartek.tu.kielce.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is the SiI 0680 chipset status?
Date: Thu, 4 Sep 2003 03:42:07 +0200	[thread overview]
Message-ID: <20030904014207.GA8579@bartek.tu.kielce.pl> (raw)
In-Reply-To: <1062589779.19059.8.camel@dhcp23.swansea.linux.org.uk>

Witam,
Dnia Wed, Sep 03, 2003 at 12:49:40PM +0100 Alan Cox napisal(a):

> On Maw, 2003-09-02 at 17:55, Tomasz B??tor wrote:
> > I recently got MiNt PCI IDE ATA/133 RAID controller based on SiI 0680
> > chipset. I browsed through the archives and I know that the driver is
> > known to be broken and simply doesn't work.
> 
> It just works. You do want 2.4.22 ideally, and you want 2.4.22-ac to use
> hotplug.

It doesn't for me. I have no idea what could I possibly do wrong, but
I've tried dozens of possibilities without any luck. Compiling in
siimage.c = drive errors, ide2 reset and infinite loop of "lost
interrupt" messages at boot time. Without siimage.c compiled and with
ide2=xxx ide3=xxx parameters in lilo, disks are visible, but of course
there is no DMA.

Any ideas?

t.

ps. yes, I use 2.4.22, without hotplug.

-- 
  Tomasz Bątor  e-mail: tomba@bartek.tu.kielce.pl  ICQ: 101194886
 ------ ---- -- - -  -    -   -  -  -   -    -  - - -- ---- ------
"The most important job is not to be governor, or first lady in my case."
                        -- George W. Bush

  reply	other threads:[~2003-09-04  1:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 16:55 What is the SiI 0680 chipset status? Tomasz  B±tor
2003-09-03 11:49 ` Alan Cox
2003-09-04  1:42   ` Tomasz  B±tor [this message]
2003-09-04 10:06     ` Alan Cox
2003-09-04 10:53       ` Tomasz  B±tor
2003-09-04  2:19   ` "bleating edge" " Resident Boxholder
2003-09-03 12:42 ` Sebastian Piecha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030904014207.GA8579@bartek.tu.kielce.pl \
    --to=tomba@bartek.tu.kielce.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).