public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: linux-kernel@vger.kernel.org
Subject: Re: ALI15X3 (was: Problems with Maxtor 4G160J8 and 2.4.19-* +/- ac*)
Date: Wed, 26 Jun 2002 18:55:02 +0200	[thread overview]
Message-ID: <m3it46geu1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <20020624151824.GA5902@branoic.them.org> (Daniel Jacobowitz's message of "Mon, 24 Jun 2002 11:18:24 -0400")

Daniel Jacobowitz <dan@debian.org> writes:

> I've had a lot of problems with ALI15x3; the patch that let me boot
> (found somewhere on the net, do not remember the original author)
> commented out the pci_read_config_byte and two pci_write_config_byte
> calls right below the comment that says "set south-bridge's enable
> bit".  Recent -ac kernels have this in two places.  DMA still works
> after doing that; does this work for you?

I tried commenting out various pci_writes/pci_reads, but I'm not
familiar enough with the code to say whether what I did was
meaningful or not.

In any case, it still didn't let me boot the machine with the 160GB
disk installed.

I've now bought a Highpoint Rocket133SB card and plugged the 160GB
disk into that instead, and everything works fine.  I get DMA to my
main disk via the ALI15X3 controller, and DMA to the 160GB disk via
the Rocket card.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

      reply	other threads:[~2002-06-26 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-22 23:58 Problems with Maxtor 4G160J8 and 2.4.19-* +/- ac* Lars Magne Ingebrigtsen
2002-06-23 14:38 ` ALI15X3 (was: Problems with Maxtor 4G160J8 and 2.4.19-* +/- ac*) Lars Magne Ingebrigtsen
2002-06-23 16:57   ` Fabio Massimo Di Nitto
2002-06-24 15:18   ` Daniel Jacobowitz
2002-06-26 16:55     ` Lars Magne Ingebrigtsen [this message]

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=m3it46geu1.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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