From: Nick Pasich <newsletters@NickAndBarb.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: no device found for TX4000
Date: Wed, 5 Oct 2005 11:05:23 -0700 [thread overview]
Message-ID: <20051005180223.GA17900@10.1.0.5> (raw)
Jeff,
I'm running Slackware 10.1 and have compiled linux-2.6.13.3 kernel
with the sata_promise.c as kernel resident.
I received the following in the kernel log:
********************************************************************************
Oct 4 16:51:24 Server05 kernel: ata1: PATA max UDMA/133 cmd 0xF0800200 ctl 0xF0
Oct 4 16:51:24 Server05 kernel: ata2: PATA max UDMA/133 cmd 0xF0800280 ctl 0xF0
Oct 4 16:51:24 Server05 kernel: ata3: PATA max UDMA/133 cmd 0xF0800300 ctl 0xF0
Oct 4 16:51:24 Server05 kernel: ata4: PATA max UDMA/133 cmd 0xF0800380 ctl 0xF0
Oct 4 16:51:24 Server05 kernel: ata1: no device found (phy stat 00000000)
Oct 4 16:51:24 Server05 kernel: scsi1 : sata_promise
Oct 4 16:51:24 Server05 kernel: ata2: no device found (phy stat 00000000)
Oct 4 16:51:24 Server05 kernel: scsi2 : sata_promise
Oct 4 16:51:24 Server05 kernel: ata3: no device found (phy stat 00000000)
Oct 4 16:51:24 Server05 kernel: scsi3 : sata_promise
Oct 4 16:51:24 Server05 kernel: ata4: no device found (phy stat 00000000)
Oct 4 16:51:24 Server05 kernel: scsi4 : sata_promise
********************************************************************************
I then compiled sata_promise.c as a module and received the same message
on a modprobe....
Any help would be appreciated.....
---( Nick Pasich )---
next reply other threads:[~2005-10-05 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 18:05 Nick Pasich [this message]
2005-10-05 22:13 ` no device found for TX4000 Jeff Garzik
2005-10-05 22:27 ` Nick Pasich
2005-10-07 13:43 ` Nick Pasich
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=20051005180223.GA17900@10.1.0.5 \
--to=newsletters@nickandbarb.net \
--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).