[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Promise Fasttrak 100 PDC20267 on Debian

->>In response to your message<<-
  --received from Ron Johnson--
> On Mon, 2003-09-29 at 00:27, Greg Vickers wrote:
> > Hi all,
> > 
> > Just wondering if there is a person or group working on supporting the 
> > mirror features of the Promise Fasttrak 100 PDC20267 on Debian?
> Have you tried moving to a newer kernel?
> According to 'grep -r PDC20267 /usr/src/kernel-source-2.4.19', that
> chip is supported by Debian-packaged kernels.  You will probably
> have to grab the deb directly from the web page, though.

Hi, similarly, I have an onboard Promise RAID chip but with chipset
PDC20276 which, however so close, doesn't seem to be offered the same
support by the 2.4.18(-19) kernel (at least it doesn't explicitely say
it supports it as it does the PDC202067 chipset).  The device is called
MBFastTrak133 and I'm having no luck having the system acknowledge the
mirrored hard drive array.

I've used FastTrak 100 on a Red Hat machine before.  I was instructed
by Promise to use the following kernel options at boot:

    ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0 ide5=0
    ide6=0 i de7=0 ide8=0 ide9=0

with installing the Promise FastTrak 100 driver, a kernel module
appropriately named FastTrak which gets put in with the other kernel
modules for specifically kernel 2.4.18-14 and which gets inserted with
the following alias in /etc/module.conf

    alias scsi_hostadapter FastTrak  ft

This works great, causing the mirrored RAID array to show up as a scsi
device, for me, /dev/sda.

I can't tell that these same kernel options have any effect on my
Debian system and I can't use the same FastTrak, Red Hat driver as
Debian doesn't offer exactly kernel 2.4.18-14 (although with trouble I
suppose I could build this kernel version if this is the only way to

Verifying that the Block Device for PDC202XX is indeed built into the
Debian 2.4.18-ll kernel, I was hoping things might just work.  Using
the same kernel boot options, I was hoping the mirrored devices might
magically show up as /dev/sda or at least individually or
otherwise under some ide device name.  No such success.

Any ideas, tips, thoughts out there?



Paul Yeatman       (858) 534-9896        pyeatman@ucsd.edu
	     ==Proudly brought to you by Mutt==

Reply to: