From: Kevin Fenzi <kevin@tummy.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux aacraid devel <linux-aacraid-devel@dell.com>
Subject: Re: aacraid and large memory problem (2.6.0-test11)
Date: Wed, 3 Dec 2003 15:28:38 -0700 [thread overview]
Message-ID: <20031203222840.6A4E6F7C86@voldemort.scrye.com> (raw)
In-Reply-To: <1070488662.21904.6.camel@markh1.pdx.osdl.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Mark" == Mark Haverkamp <markh@osdl.org> writes:
Mark> I set up my machine to boot on the aacraid disk and it booted OK
Mark> for me. Maybe its a problem with a particular model?
Mark> lspci on mine says:
Mark> 02:04.0 RAID bus controller: Digital Equipment Corporation
Mark> DECchip 21554 (rev 01) Subsystem: Adaptec Adaptec 5400S
This one says:
05:01.0 RAID bus controller: Adaptec AAC-RAID (rev 01)
Subsystem: Adaptec AAC-RAID
Flags: bus master, fast Back2Back, 66Mhz, slow devsel, latency 64, IRQ 96
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [80] Power Management version 2
It's a 2200S controller.
bios version 6008
Mark> -- Mark Haverkamp <markh@osdl.org>
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/zmOY3imCezTjY0ERAtOeAKCCCos81FiV0oy89ojnJQiTCK212QCgkO8/
1rARggxxE7xP8YVggM2f6vI=
=+t3d
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-12-03 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 19:35 aacraid and large memory problem (2.6.0-test11) Kevin Fenzi
2003-12-02 20:21 ` Mark Haverkamp
2003-12-03 16:16 ` bill davidsen
2003-12-03 20:51 ` Kevin Fenzi
2003-12-03 21:57 ` Mark Haverkamp
2003-12-03 22:28 ` Kevin Fenzi [this message]
2003-12-03 22:53 ` bill davidsen
2003-12-03 23:25 ` Mark Haverkamp
2003-12-11 17:53 ` Kevin Fenzi
2003-12-03 20:57 Kevin Fenzi
2003-12-03 21:26 ` bill davidsen
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=20031203222840.6A4E6F7C86@voldemort.scrye.com \
--to=kevin@tummy.com \
--cc=linux-aacraid-devel@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.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;
as well as URLs for NNTP newsgroup(s).