From: David Sims <dpsims@virtualdave.com>
To: Jeff Garzik <jgarzik@pobox.com>, Jeremy Higdon <jeremy@sgi.com>,
Paulo Marques <pmarques@grupopie.com>,
Bukie Mabayoje <bukiemab@gte.net>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I need a hardware wizard... I have been beating my head on the wall..
Date: Sat, 29 Jan 2005 20:48:28 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0501292024010.11121-100000@ernie.virtualdave.com> (raw)
In-Reply-To: <41F99AF0.4090902@pobox.com>
Hello people,
Now I _really_ need to bang my head on the wall... :( .... and thank all
you people who responded to my cry for help... I have to admit that I have
been stupid (or just a little clueless).... but I have worked the puzzle!!
It seems that sata_vsc works just fine.... My entire problem involved
the PCI IRQ routing mechanism.... and my lack of understanding of the
interaction between 'Loacl APIC', 'IO-APIC' and power management.... It
seems that you can do what you want with 'Local APIC' and 'IO-APIC' but if
you have not enabled ACPI, the APIC stuff is not enabled... and doesn't
seem to do anything....
I have now enabled both ACPI and APIC (with IO-APIC) and the IRQ
barking has gone away!!
I had a similar problem today with another computer (ASUS
MS4800-MX) where the built in Ethernet on a Via PHY chip (supported by the
SiS900 driver) refused to work... In this case I booted up Knoppix which
worked just fine.... and then started trying to figure out why there was a
difference between knoppix and a vanilla Slackware kernel.... It seems
that Slackware 9.1 does not have ACPI (or APIC or IO-APIC) enabled... Once
I figured that out, it was seemed to make the SIS900 driver work so I
decided to try it on the sata_vsc problem.... The result is history and
everything is working as it should.... It's a shame that the knoppix 3.4
kernel doesn't probe for SATA stuff or I would probably have figured this
out a week ago :(
Meanwhile, a working sata_vsc allows one to turn a Dell Powervault 745N
(Dell's foray into Network Attached Storage) into a good and cheap unix
server with dual gig NICs and 4 SATA disks that can either be run
independently or via software raid!! Cool!
Thanks again for your support for and patience with me... I will be humble
for a while now... ;)
Dave
prev parent reply other threads:[~2005-01-30 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 1:44 I need a hardware wizard... I have been beating my head on the wall David Sims
2005-01-28 1:52 ` Jeff Garzik
2005-01-28 3:04 ` David Sims
2005-01-28 20:52 ` Paulo Marques
2005-01-29 1:13 ` David Sims
2005-01-30 2:48 ` David Sims [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=Pine.LNX.4.21.0501292024010.11121-100000@ernie.virtualdave.com \
--to=dpsims@virtualdave.com \
--cc=bukiemab@gte.net \
--cc=g.liakhovetski@gmx.de \
--cc=jeremy@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
/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).