From: "Bobby D. Bryant" <bdbryant@mail.utexas.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Mike Frisch <mfrisch@saturn.tlug.org>
Subject: Re: Status of ALi MAGiK 1 support in 2.4.?
Date: Tue, 29 May 2001 15:11:57 +0600 [thread overview]
Message-ID: <3B1367DD.A71E8066@mail.utexas.edu> (raw)
In-Reply-To: <3B12DCCF.6524A99@mail.utexas.edu> <20010529100713.A3845@saturn.tlug.org>
Mike Frisch wrote:
> On Tue, May 29, 2001 at 05:18:39AM +0600, Bobby D. Bryant wrote:
> > sailing ever since. The only problems that I'm are ware of are a
> > (maybe) DMA problem and a (maybe) SMBus problem, per below. Right now
>
> I noticed the Win32 benchmark/test application Sandra mentioned an SMBus
> problem with the A7A266 as well. I have yet to try lm_sensors myself,
> but it looks like I won't get far.
My sensors are working and appear to give the correct numbers; I'm just
getting a regular spew of messages from the SMB resets.
> > May 22 21:45:07 pollux kernel: ALI15X3: IDE controller on PCI bus 00 dev
> > 20
> > May 22 21:45:07 pollux kernel: PCI: No IRQ known for interrupt pin A of
> > device 00:04.0. Please try using pci=biosirq.
>
> I get the same message, but it does not appear to dramatically affect
> my performance. As I mentioned, I am getting 25MB/s (through hdparm; I
> have yet to try anything more) with my Quantum Fireball. My DMA is
> enabled in the BIOS and detected by the kernel.
That's interesting, in light of the other message I just sent (i.e., DMA
enabled in BIOS, but *not* detected by the kernel).
What version of the BIOS are you running? I'm still on the 1003b, because
I've heard a few horror stories about 1004 that have put me off upgrading.
I'm on kernel 2.4.4, with Athlon optimizations.
> > The routing to IQR 0 sounds funny to me, but this is already way beyond
> > what I understand.
>
> Do you have the PnP operating system setting in the BIOS turned off?
> (ie. telling the BIOS you have non-PnP aware O/S) I noticed that prior
> to doing this, all of my PCI cards were listed as IRo 0.
I think I tried it both ways earlier. At any rate, since I had to reboot to
check the DMA settings I went ahead and set it back to 'off', and it still
says the same thing.
Thanks,
Bobby Bryant
Austin, Texas
next prev parent reply other threads:[~2001-05-29 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 23:18 Status of ALi MAGiK 1 support in 2.4.? Bobby D. Bryant
2001-05-29 12:35 ` Alan Cox
2001-05-29 9:04 ` Bobby D. Bryant
2001-05-30 21:48 ` Stefan Jaschke
2001-05-29 14:07 ` Mike Frisch
2001-05-29 9:11 ` Bobby D. Bryant [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-28 15:57 Axel Thimm
2001-05-28 16:09 ` Mike Frisch
2001-05-28 16:17 ` Alan Cox
2001-05-28 16:28 ` Mike Frisch
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=3B1367DD.A71E8066@mail.utexas.edu \
--to=bdbryant@mail.utexas.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mfrisch@saturn.tlug.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.