Henrique de Moraes Holschuh wrote:
On Wed, 06 Jun 2007, Björn Steinbrink wrote:HDAPS support is available, revision is MB2IA60A.That would usually rule out the possibility of it being the firmware, but we have different disks, so different firmware. It looks like I will have to try 2.6.22 to know for sure.
"hdparm -I" should list "Automatic Acoustic Management feature set" (near the bottom) for any drive that *does* support the -M feature. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Bad behaviour after hdparm -M 128
- From: Henrique de Moraes Holschuh <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- References:
- Re: Bad behaviour after hdparm -M 128
- From: Robert Hancock <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Henrique de Moraes Holschuh <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Björn Steinbrink <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Henrique de Moraes Holschuh <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Björn Steinbrink <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Henrique de Moraes Holschuh <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Björn Steinbrink <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- From: Henrique de Moraes Holschuh <[email protected]>
- Re: Bad behaviour after hdparm -M 128
- Prev by Date: Re: [patch/rfc] implement memmem() locally in kallsyms.c
- Next by Date: Re: [REPOST PATCH] sata_promise: use TF interface for polling NODATA commands
- Previous by thread: Re: Bad behaviour after hdparm -M 128
- Next by thread: Re: Bad behaviour after hdparm -M 128
- Index(es):
 |