From: James Lamanna <jlamanna@its.caltech.edu>
To: linux-kernel@vger.kernel.org
Subject: Fasttrak 100 configuration
Date: Mon, 27 Nov 2000 20:26:49 -0800 [thread overview]
Message-ID: <3A233409.CD297146@its.caltech.edu> (raw)
So I'm trying to get the Promise Fasttrack 100 driver included
with 2.4.0-test10 to work on my system.
I have 2 45GB drives hooked up in RAID0.
I'm trying to install directly onto the drives, but I'm having
a couple problems.
It seems to detect the controller card and the drives, but
they are not assigned to any devices.
Any suggestions?
Thanks,
--James Lamanna
Here is some info:
dmesg:
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
PDC20265: IDE controller on PCI bus 00 dev 88
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode.
PDC20265: FORCING BURST BIT 0x00 -> 0x01 ACTIVE
ide0: BM-DMA at 0x6400-0x6407, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x6408-0x640f, BIOS settings: hdc:DMA, hdd:pio
PDC20267: IDE controller on PCI bus 00 dev 58
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER
Mode.
PDC20267: neither IDE port enabled (BIOS)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This line is interesting I thought...
/proc/pci:
Bus 0, device 11, function 0:
RAID bus controller: Promise Technology, Inc. 20267 (rev 2).
IRQ 10.
Master Capable. Latency=32.
I/O at 0x9400 [0x9407].
I/O at 0x9000 [0x9003].
I/O at 0x8800 [0x8807].
I/O at 0x8400 [0x8403].
I/O at 0x8000 [0x803f].
Non-prefetchable 32 bit memory at 0xd5000000 [0xd501ffff].
Bus 0, device 17, function 0:
Unknown mass storage controller: Promise Technology, Inc. 20265 (rev
2).
IRQ 10.
Master Capable. Latency=32.
I/O at 0x7800 [0x7807].
I/O at 0x7400 [0x7403].
I/O at 0x7000 [0x7007].
I/O at 0x6800 [0x6803].
I/O at 0x6400 [0x643f].
Non-prefetchable 32 bit memory at 0xd4800000 [0xd481ffff].
/proc/ide/pdc202xx:
PDC20265 Chipset.
------------------------------- General Status
Burst Mode : enabled
Host Mode : Normal
Bus Clocking : 33 PCI Internal
IO pad select : 10 mA
Status Polling Period : 5
Interrupt Check Status Polling Delay : 7
--------------- Primary Channel ---------------- Secondary Channel
-------------
enabled enabled
66 Clocking disabled disabled
Mode PCI Mode PCI
FIFO Empty FIFO Empty
--------------- drive0 --------- drive1 -------- drive0 ----------
drive1 ------
DMA enabled: no no yes no
DMA Mode: NOTSET NOTSET NOTSET
NOTSET
PIO Mode: NOTSET NOTSET NOTSET
NOTSET
-
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/
reply other threads:[~2000-11-28 4:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A233409.CD297146@its.caltech.edu \
--to=jlamanna@its.caltech.edu \
--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