From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: linux-kernel@vger.kernel.org
Subject: ALI15X3 (was: Problems with Maxtor 4G160J8 and 2.4.19-* +/- ac*)
Date: Sun, 23 Jun 2002 16:38:44 +0200 [thread overview]
Message-ID: <m3hejurrez.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3ofe2vpa4.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 23 Jun 2002 01:58:59 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I've tried quite a few of the 2.4.19-pre patches, with or without
> various -ac patches, including pre10 + ac2, and they all basically
> display one of two behaviors: The machine either hangs just before
> detecting the disk, or when doing the partition check for the disk.
[...]
> ALI15X3: IDE controller on PCI bus 00 dev 20
> PCI: No IRQ known for interrupt pin A of device 00:04.0. Please try using pci=biosirq.
> ALI15X3: chipset revision 196
> ALI15X3: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:pio, hdd:DMA
After poking around a bit, it seems like the real problem might be
with the ALI15X3 driver. I disabled that driver, and now I can boot
using 2.4.19-pre10-ac2. Of course, that leaves me with no DMA...
So -- is this a general problem with this driver, or does it only
show up when using disks bigger than 128GiB?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-06-23 14:39 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 ` Lars Magne Ingebrigtsen [this message]
2002-06-23 16:57 ` ALI15X3 (was: Problems with Maxtor 4G160J8 and 2.4.19-* +/- ac*) Fabio Massimo Di Nitto
2002-06-24 15:18 ` Daniel Jacobowitz
2002-06-26 16:55 ` Lars Magne Ingebrigtsen
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=m3hejurrez.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