From: Bryan Fink <bfink@eventmonitor.com>
To: linux-ide@vger.kernel.org, pegasus@nerv.eu.org, htejun@gmail.com,
edmudama@gmail.com, albertcc@tw.ibm.com
Subject: Re: gigabyte iRam not seen by linux
Date: Wed, 15 Mar 2006 14:34:45 -0500 [thread overview]
Message-ID: <44186C55.5060702@eventmonitor.com> (raw)
> The patch at the tail of this mail makes ata_dev_try_classify() ignore
> diagnostic code in FEATURE. If the iRam successfully gets attached
> with the patch, can you please post 'hdparm -I /dev/sdX' and 'hdparm
> --Istdout /dev/sdX' of the iRam?
>
> --- a/drivers/scsi/libata-core.c
> +++ b/drivers/scsi/libata-core.c
> @@ -477,7 +477,7 @@ ata_dev_try_classify(struct ata_port *ap
> else if ((device == 0) && (err == 0x81))
> /* do nothing */ ;
> else
> - return ATA_DEV_NONE;
> + /*return ATA_DEV_NONE*/;
>
> /* determine if device is ATA or ATAPI */
> class = ata_dev_classify(&tf);
Hi, I'm having the same trouble with this card as everyone else. I'm
wondering if anyone would care to comment about what the above patch may
break. Is it going to disable safeguards, such that if a disk in my
system actually does crash, I won't know it? Or, is it simply going to
mean that I should be careful to only plug things into the system that I
know are supported?
I'm in contact with Gigabyte, trying to get their opinion on the
matter. I know others have said that they are very unhelpful when it
comes to linux support, but I'm hoping that if we can show them what's
wrong, they could roll up a fix in a firmware release.
-Bryan
next reply other threads:[~2006-03-15 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 19:34 Bryan Fink [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-10 0:36 gigabyte iRam not seen by linux Jure Pečar
2006-03-10 17:51 ` Tejun Heo
2006-03-11 2:02 ` Albert Lee
2006-03-11 2:46 ` Jure Pečar
2006-03-11 3:31 ` Tejun Heo
2006-03-11 8:20 ` Jure Pečar
2006-03-11 8:58 ` Tejun Heo
2006-03-11 16:12 ` Eric D. Mudama
2006-03-11 16:33 ` Tejun Heo
2006-03-11 16:43 ` Jure Pečar
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=44186C55.5060702@eventmonitor.com \
--to=bfink@eventmonitor.com \
--cc=albertcc@tw.ibm.com \
--cc=edmudama@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=pegasus@nerv.eu.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).