From: Ricci Daniele <ricci@trinityteam.it>
To: linux-kernel@vger.kernel.org
Subject: PDC20276 Linux driver
Date: Tue, 12 Nov 2002 15:52:09 +0100 [thread overview]
Message-ID: <200211121452.gACEq9G09512@trinityteam.it> (raw)
Hello,
I have a Gigabyte 7DPXDW-P, a dual Athlon motherboard whit a FastTrak
controller onboard and I found some difficulties installing the driver.
Kernel deviceses initialization recognise my PDC20276 controller and find
the disks connected (/dev/hde and /dev/hdg) and the array I made with them
(/dev/ataraid/d0 RAID1). I tryed to write in /dev/ataraid/d0 but after about
half a gigabyte written, the system stops to write and the process(es) writing
appare(s) in the outputo of ps with the flag D (IO waiting). After a lot of
tryes I tryed to write in /dev/hde and /dev/hdg at different times, but the
same thing happens.
Is the problem in the FastTrak driver, in the PDC20276 driver, or in my
hardware?
Is there a known bug?
Do somebody has the same mothrboard and can use PDC20276? If yes, can u tell
me how to do?
How can I do to debug degug the ide driver or the PDC driver? Or What
documentation have I to read?
Thank you for your time,
Daniele.
next reply other threads:[~2002-11-12 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 14:52 Ricci Daniele [this message]
2002-11-12 15:33 ` PDC20276 Linux driver Alan Cox
2002-11-12 15:23 ` ricci
2002-11-12 15:55 ` Alan Cox
2002-11-12 15:43 ` ricci
2002-11-12 16:06 ` Alan Cox
2002-11-12 15:53 ` ricci
2002-11-12 16:53 ` Geoffrey Lee
2002-11-12 17:28 ` ricci
2002-11-12 20:38 ` GA-7VRXP is a bad motherboard [was Re: PDC20276 Linux driver] Bryan O'Sullivan
2002-11-12 21:13 ` Priit Laes
2002-11-12 22:41 ` Geoffrey Lee
2002-11-12 23:06 ` Ruth Ivimey-Cook
2002-11-13 7:32 ` Priit Laes
2002-11-13 12:03 ` ricci
2002-11-13 12:19 ` PDC20276 Linux driver ricci
[not found] <1037192260.1501.1.camel@darkstar>
2002-11-13 13:51 ` ricci
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=200211121452.gACEq9G09512@trinityteam.it \
--to=ricci@trinityteam.it \
--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