>>>>> On Sat, 20 Apr 2002,"Murty" == Murty Rompalli wrote:
Murty> First, you dont have all the features enabled in kernel; if you are trying
Murty> to boot off of the raid disks, it may not work with modules. Build them
Murty> statically.
I'm not trying to boot off raid. I just have it for achiving/backup (for now).
Murty> Promise proprietary driver (aka fake scsi driver) knows how to deal with
Murty> "neither port enabled in BIOS"
Oh, understood. In fact, their instructions even force you to disable ide2 and ide3, looking at it now.
Murty> Otherwise, you have to specify what ide2 and ide3 are , at boot time. For
Murty> example
Murty> boot linux ide2=0xd000,0xd402,11 ide3=0xd800,0xdc02,14
Murty> You can find IO numbers from Fasttrack BIOS (press Cntrl+F at boot
Murty> time) or in linux (cat /proc/pci)
OH!
In /proc/pci I had:
Bus 0, device 10, function 0:
RAID bus controller: Promise Technology, Inc. 20267 (rev 2).
IRQ 9.
Master Capable. Latency=64.
I/O at 0xa800 [0xa807].
I/O at 0xac00 [0xac03].
I/O at 0xb000 [0xb007].
I/O at 0xb400 [0xb403].
I/O at 0xb800 [0xb83f].
Non-prefetchable 32 bit memory at 0xe5000000 [0xe501ffff].
so I added:
ide2=0xa800,0xac00 ide3=0xb000,0xb400
Now, even though it's saying neither port is enabled:
PDC20267: IDE controller on PCI bus 00 dev 50
PCI: Found IRQ 9 for device 00:0a.0
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: ROM enabled at 0xe3000000
PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode.
PDC20267: neither IDE port enabled (BIOS)
It definitely IS recognizing my drive! It's hde below:
hda: Maxtor 90845D4, ATA DISK drive
hdb: Maxtor 91303D6, ATA DISK drive
hdc: PLEXTOR CD-R PX-W8432T, ATAPI CD/DVD-ROM drive
hde: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hde: IBM-DTLA-307060, ATA DISK drive
hdf: probing with STATUS(0x00) instead of ALTSTATUS(0xff)
hdf: probing with STATUS(0x00) instead of ALTSTATUS(0xff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xa800-0xa807,0xac00 on irq 9
blk: queue c03c0ba0, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03c0ba0, I/O limit 4095Mb (mask 0xffffffff)
hda: 16514064 sectors (8455 MB) w/256KiB Cache, CHS=1027/255/63, UDMA(33)
blk: queue c03c0cdc, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03c0cdc, I/O limit 4095Mb (mask 0xffffffff)
hdb: 25450992 sectors (13031 MB) w/512KiB Cache, CHS=1584/255/63, UDMA(33)
hde: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63
Sadly though, when it tries to access the drive:
Partition check:
hda: hda1 hda2
hdb: hdb1
hde:hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
ide2: reset: master: error (0x00?)
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
ide2: unexpected interrupt, status=0x58, count=1
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
ide2: reset: master: error (0x00?)
end_request: I/O error, dev 21:00 (hde), sector 0
unable to read partition table
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
I feel I'm much closer . . . this drive worked fine 10 minutes ago with the Promise driver, so I'm confident this is not a cabling issue . . . any idea what I can try next?
Thanks very much for your help so far.
-Darren
