From: Amith Varghese <amith@xalan.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-2.4.19-rc1-ac4 + Promise SX6000 + i2o
Date: 18 Jul 2002 00:31:21 -0400 [thread overview]
Message-ID: <1026966681.4537.119.camel@viper> (raw)
In-Reply-To: <1026941364.4547.91.camel@viper>
Just for more information... I too have the PDC20276 chip which Alan had
mentioned in in linux 2.4.19rc1-ac3 changelog as the following:
o Newer SX6000 has PDC20276 chips. Handle this (me)
I tried 2.4.19rc2 and 2.4.19rc1-ac7 with no success. I'm willing to try
and debug this, but i don't have a really good idea how to. If someone
can give me some ideas that would be great.
Thanks
Amith
On Wed, 2002-07-17 at 17:29, Amith Varghese wrote:
> I'm getting similar results, but I haven't tried anyting in 2.4.19
> series yet... this is my situation
>
> I am trying to put together a new machine using the promise sx6000
> raid card and I am having some problems with getting the OS to
> recognize the raid array. Here are the facts
>
> * dual athlon 1900
> * asus a7m266-d motherboard w/ latest bios (A006)
> * 1GB RAM
> * Realtek RTL-8139 ethernet card
> * Promise SX6000
>
> * using 6 120GB western digital HD's
> * total array size is 600GB defined as RAID 5
> * using the latest bios (Revision 77) for the promise sx6000
> * have the OS set to "Other"
>
> The redhat 7.3 doesn't seem to load the i20 block driver on boot and
> therefore it can't find any drives when trying to install the OS. So
> what I have done is compiled a new kernel on my other linux machine
> that has the i2o support, i2o pci support, and i2o block support. I
> then replaced the vmlinuz file within the boot.img file provided by
> redhat. When I boot the machine it looks promising. I get the
> following messages:
>
> Loading I2O core - (c) Copyright 1999 Red Hat Software
> Linux I2O PCI support (c) 1999 Red Hat Software
> i2o: Checking for PCI I2O controllers...
> i2o: I2O controller on bus 2 at 49.
> i2o: PCI I2O controller at 0xF3000000 size=4194304
> I2O: Promise workarounds activated.
> i2o/iop0: Installed at IRQ 10
> i2o: 1 I2O controller found and installed.
> Activating I2O controllers...
> This may take a few minutes if there are many devices
> i2o/iop0: Reset rejected, trying to clear
> i2o/iop0: LCT has 5 entries
> i2o/iop0: Configuration dialog desired.
> I2O configuration manager v 0.04.
> (C) Copyright 1999 Red Hat Software
> I2O Block Storage OSM v0.9
> (C) Copyright 1999-2001 Red Hat Software
> i2o_block: Checking for Boot device...
> i2o_block: Checking for I2O Block devices...
> i2ob: Installing tid 11 device at unit 0
> i2o/hda: Max segments 28, queue def 32, byte limit 14336.
> i2o/hda: Type 128: 572366MB, 512 byte sectors.
> i2o/hda: Maximum sectors/read set 2 256.
> Partitition check:
> i2o/hda:
>
> However, it hangs here and does nothing. I left it on all night and
> no change. Does anyone have any ideas why it might be hanging? Is
> there something else I should try? Do I need to pass any arguments to
> the kernel? If anyone needs more info I would be glad to give it.
> Any help would be greatly appreciated.
>
> Thanks
> Amith
>
>
>
> Viktors Rotanovs <Viktors@Rotanovs.com> wrote in message
> news:<linux.kernel.9016512704.20020717045236@Rotanovs.com>...
> > Hi,
> >
> > I've found numerious reports that Promise SX6000 works fine with
> > 2.4.18+ kernels, and tried it with 2.4.18 and 2.4.19-rc1-ac4 kernels
> > with i2o support.
> >
> > Here are the results:
> >
> > 2.4.18: finds controller, but doesn't find disk device on it.
> > 2.4.19-rc1-ac4: loads i2o_block and i2o_core fine and doesn't load
> > i2o_pci. When I try to load i2o_pci manually, it shows a lot of
> > timeouts.
> >
> > I seem to have PDC20276 chip (if i'm not mistaken) marked as new
> > by Alan Cox.
> >
> > OS type on the RAID is set to Other.
> >
> > When I try to run original driver Promise's driver instead of i2o on
> > 2.4.18, it starts showing SCSI timeouts after some time when working
> > under heavy load.
> >
> > I use RAID with ReiserFS.
> >
> > Thanks for any help and have a nice day!
> >
> > Best Wishes,
> > Viktors
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-07-18 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 21:29 2.4.18-2.4.19-rc1-ac4 + Promise SX6000 + i2o Amith Varghese
2002-07-18 4:31 ` Amith Varghese [this message]
2002-07-19 3:11 ` Amith Varghese
2002-07-20 20:39 ` Alan Cox
2002-07-20 21:21 ` Amith Varghese
2002-07-21 0:21 ` Alan Cox
2002-07-21 5:43 ` Andre Hedrick
2002-07-18 7:52 ` Re[2]: " Viktors Rotanovs
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 1:52 Viktors Rotanovs
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=1026966681.4537.119.camel@viper \
--to=amith@xalan.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.