From: Evan Thompson <evaner@bigfoot.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
linux-kernel@vger.kernel.org
Subject: Re: VIA IDE controller strangeness (2.4.0-test12/test13-pre5)
Date: Sat, 30 Dec 2000 13:19:30 -0600 [thread overview]
Message-ID: <20001230131930.A3657@evaner.penguinpowered.com> (raw)
In-Reply-To: <20001229185923.A477@evaner.penguinpowered.com> <20001230183414.C1950@emma1.emma.line.org>
In-Reply-To: <20001230183414.C1950@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Sat, Dec 30, 2000 at 06:34:14PM +0100
--(CC replies please)--
On Sat, Dec 30, 2000 at 06:34:14PM +0100, Matthias Andree wrote:
> Could you report the chip set type and revision? Quote the corresponding
> parts from the "lspci -v" output, please. I've been using PC Chips main
> boards with VIA chip sets without IDE difficulties ever since I bought
> one of those in fall 1998. (VIA Apollo MVP3 AGP, VT82C598 + VT82C586
> north+south bridges), both PC Chips M577 and Tyan Trinity S1590S.
Alrighty then (this is output from lspci -v running under 2.2.18pre21):
-- BEGIN OUTPUT --
...
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA
[Apollo VP] (rev 41)
Subsystem: VIA Technologies, Inc. MVP3 ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
(prog-if 8f [Master SecP SecO PriP PriO])
Flags: bus master, medium devsel, latency 32, IRQ 14
I/O ports at 01f0
I/O ports at 03f4
I/O ports at 0170
I/O ports at 0374
I/O ports at ffa0
...
-- END OUTPUT --
Now...one thing I noticed is that Linux is trying to find this IDE
interface through PCI and it reports it on 00:07.1 during -test12 and
-test13-pre5 boot up (I can't get a dmesg output for you 'cause it never
boots...just keeps complaining about hdb: lost interrupt), but the IDE
controller seems to be an ISA device (unless I've read this wrong).
In case I'm configuring something wrong, I've pasted the IDE .config
portions here:
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
ONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_IDE_MODES=y
Hope this stuff helps you guys out.
If somebody wants to tell me a better way to get nvi to wrap lines at 75
chars (other than hitting enter when I think it has to be hit), you could
e-mail me (don't bother sending it to the list).
CC replies please. I don't subscribe to linux-kernel. Sorry.
--
| Evan A. Thompson | He's more fun than trying to skinny |
| evaner@bigfoot.com | dip in the beach in winter... |
| http://evaner.penguinpowered.com | ...in Winnipeg. |
| ICQ: 2233067 / AIM + MSN: Evaner517 | (GnuPG key avaiable upon request.) |
...hmmm...Now I'm going to have to adjust my .signature to fit in 75
chars instead of 79. Darn.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-30 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 0:59 VIA IDE controller strangeness (2.4.0-test12/test13-pre5) Evan Thompson
2000-12-30 17:34 ` Matthias Andree
2000-12-30 19:19 ` Evan Thompson [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=20001230131930.A3657@evaner.penguinpowered.com \
--to=evaner@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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