linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* no device found for TX4000
@ 2005-10-05 18:05 Nick Pasich
  2005-10-05 22:13 ` Jeff Garzik
  0 siblings, 1 reply; 4+ messages in thread
From: Nick Pasich @ 2005-10-05 18:05 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: linux-ide


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 )---





^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-10-07 13:43 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-05 18:05 no device found for TX4000 Nick Pasich
2005-10-05 22:13 ` Jeff Garzik
2005-10-05 22:27   ` Nick Pasich
2005-10-07 13:43   ` Nick Pasich

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).