From: "Matt H." <lkml@lpbproductions.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Promise SX-6000 and kernel 2.6.5
Date: Thu, 15 Apr 2004 23:00:58 -0700 [thread overview]
Message-ID: <200404152302.38441.lkml@lpbproductions.com> (raw)
In-Reply-To: <1082093803.4962.86.camel@bene.samgtp>
I can also confirm that this card doesn't work in 2.6 when using the generic
i2o drivers.
Matt H.
On Thursday 15 April 2004 10:36 pm, you wrote:
> Hello!!!
>
> I am sorry for the letter, but allow to address to you with my problem.
> Has bought Promise SX-6000 Pro the controller and has established on him
> Linux Redhat. All - is excellent!! Has updated a nucleus for 2.6.5 - I
> can not pick up the controller in any way. Source codes of a nucleus
> taking place on your site do not approach for 2.6 nucleus :(
>
> Can you know the possible decision of my problem??
>
> Yours faithfully and hope, Alexey.
>
> P.S.1 firmware drivers for 2.4.x kernel download is
> http://www.eventus.de/linux.html
>
> P.S.2
>
> In make menuconfig has disconnected support of all PDC Promise. Has
> included all I2O devices in a nucleus.
>
> ns linux # cat .config|grep I2O
> # I2O device support
> CONFIG_I2O=y
> CONFIG_I2O_PCI=y
> CONFIG_I2O_BLOCK=y
> CONFIG_I2O_SCSI=y
> CONFIG_I2O_PROC=y
>
>
> dmesg send 0 i2o controllers
>
> I2O Core - (C) Copyright 1999 Red Hat Software
> I2O: Event thread created as pid 17
> i2o: Checking for PCI I2O controllers...
> 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...
> i2o_scsi.c: Version 0.1.2
> chain_pool: 0 bytes @ f7ae85a0
> (512 byte buffers X 4 can_queue X 0 i2o controllers)
>
>
> lspci:
>
> 02:02.1 Class ff00: Intel Corp. 80960RM [i960RM Microprocessor] (rev 02)
> (prog-if 01)
> Subsystem: Promise Technology, Inc. SuperTrak SX6000 I2O CPU
> Flags: bus master, medium devsel, latency 32, IRQ 22
> Memory at f6000000 (32-bit, prefetchable) [size=4M]
> Expansion ROM at <unassigned> [disabled] [size=64K]
>
> -
> 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:[~2004-04-16 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 5:36 Alex Murphy
2004-04-16 6:00 ` Matt H. [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-15 13:38 Promise SX-6000 and Kernel 2.6.5 Alex Murphy
2004-04-13 9:09 Alex Murphy
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=200404152302.38441.lkml@lpbproductions.com \
--to=lkml@lpbproductions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@lpbproduction.scom \
/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
all inboxes | Powered by JetHome®