From: Marc Singer <elf@buici.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: VIA SATA not recognizing drives
Date: Sun, 9 May 2004 00:39:14 -0700 [thread overview]
Message-ID: <20040509073914.GA4881@buici.com> (raw)
In-Reply-To: <409D5126.2060205@pobox.com>
On Sat, May 08, 2004 at 05:29:10PM -0400, Jeff Garzik wrote:
> Marc Singer wrote:
> > libata version 1.02 loaded.
> > sata_via version 0.20
> > sata_via(0000:00:0f.0): routed to hard irq line 10
> > ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 10
> > ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 10
> > ata1: no device found (phy stat 00000000)
> > ata1: thread exiting
> > scsi0 : sata_via
> > ata2: no device found (phy stat 00000000)
> > ata2: thread exiting
> > scsi1 : sata_via
>
>
> Those "phy stat 00000000" are the hardware saying there is no SATA
> device attached.
>
> Are you sure you plugged them into the VIA SATA ports? Maybe you have a
> Promise chip on-board too, or something like that? Or SATA is disabled
> in BIOS?
I'm embarassed to say, though not too proud to admit, that the power
cables weren't properly seated. It's working just fine.
I have another question, though. I've patched the ide driver to
permit an IDE interface to operate without an IRQ. It needs a little
bit of tweaking before it will be accepted by that IDE maintainer.
Are you planning to subsume all of the IDE functionality into libata
that is handled by the other IDE driver? If so, have you considered
adding polling mode?
Cheers.
next prev parent reply other threads:[~2004-05-09 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 19:31 VIA SATA not recognizing drives Marc Singer
2004-05-08 21:29 ` Jeff Garzik
2004-05-09 7:39 ` Marc Singer [this message]
2004-05-11 6:54 ` Jeff Garzik
2004-05-11 16:12 ` Marc Singer
2004-05-20 2:14 ` Jeff Garzik
2004-05-20 2:21 ` Marc Singer
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=20040509073914.GA4881@buici.com \
--to=elf@buici.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).