From: Bryan Fink <bfink@eventmonitor.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: Gigabyte i-Ram cards
Date: Wed, 22 Mar 2006 08:22:26 -0500 [thread overview]
Message-ID: <44214F92.1080901@eventmonitor.com> (raw)
In-Reply-To: <441F63E6.2090204@garzik.org>
Jeff Garzik wrote:
> I'm impressed. I ordered one to help debug BZ#6163, but I think these
> cards will help expose bugs in libata due to their high speed. With
> these cards, we can push more data through libata than would normally
> be possible with a standard disk drive.
Hi. I tried to respond on this topic about a week ago, but I haven't
seen my response show up on any of the mirrors, so I think it must have
not made it through.
Anyway, I just wanted to add that I am also fiddling with the Gigabyte
i-Ram. I haven't tried modifying and recompiling the kernel yet, but I
did have some success another way:
My desktop is a Dell Dimension 5150. In the BIOS, I can set the "SATA
Operation" to either "SATA" or "RAID". If I set it to RAID, linux will
see the i-RAM just fine (under Ubuntu 5.10 Live CD). It loads ahci, and
just takes off. If I have the setting on SATA, then linux does not load
ahci, and does not talk to the i-RAM.
Of note is also the fact that Windows has no issue with talking to the
i-RAM when my system is in SATA-mode.
So, I guess the question is, are Windows and my BIOS ignoring this
"invalid" feature query reply, or are the prodding the card in some way
other than how linux does, which makes the card respond properly?
Good luck to those who are working on this problem, and please let me
know if there is any way I can help.
-Bryan
next prev parent reply other threads:[~2006-03-22 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 2:24 Gigabyte i-Ram cards Jeff Garzik
2006-03-21 3:09 ` Eric D. Mudama
2006-03-21 22:53 ` Jure Pečar
2006-04-07 21:10 ` Jure Pečar
2006-03-22 7:24 ` Mogens Valentin
2006-03-22 7:33 ` Jens Axboe
2006-03-22 13:22 ` Bryan Fink [this message]
2006-03-22 23:29 ` Jeff Garzik
2006-03-23 10:50 ` Tejun Heo
2006-03-23 19:16 ` Mogens Valentin
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=44214F92.1080901@eventmonitor.com \
--to=bfink@eventmonitor.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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 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).