Re: Bad behaviour after hdparm -M 128

2007-06-11 Thread Tino Keitel
On Thu, Jun 07, 2007 at 22:50:04 -0300, Henrique de Moraes Holschuh wrote: [...] > I just tracked it down to hdparm. Version 6.9 (the one in Debian stable) > doesn't work right with libata. Version 7.5 (the one in Debian unstable) > works fine. > > So, at least in my side, there are *no* kerne

Re: Bad behaviour after hdparm -M 128

2007-06-07 Thread Henrique de Moraes Holschuh
On Thu, 07 Jun 2007, Mark Lord wrote: > 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 differ

Re: Bad behaviour after hdparm -M 128

2007-06-07 Thread Mark Lord
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 t

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Henrique de Moraes Holschuh
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. -- "One disk to

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Björn Steinbrink
On 2007.06.06 18:03:37 -0300, Henrique de Moraes Holschuh wrote: > On Wed, 06 Jun 2007, Björn Steinbrink wrote: > > On 2007.06.06 13:48:54 -0300, Henrique de Moraes Holschuh wrote: > > > I am also using libata PIIX like the first person reporting the problem, > > > but > > > it is a PATA drive beh

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Henrique de Moraes Holschuh
On Wed, 06 Jun 2007, Björn Steinbrink wrote: > On 2007.06.06 13:48:54 -0300, Henrique de Moraes Holschuh wrote: > > On Wed, 06 Jun 2007, Björn Steinbrink wrote: > > > On 2007.06.06 12:44:42 -0300, Henrique de Moraes Holschuh wrote: > > > > On Wed, 06 Jun 2007, Robert Hancock wrote: > > > > > >I use

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Björn Steinbrink
On 2007.06.06 13:48:54 -0300, Henrique de Moraes Holschuh wrote: > On Wed, 06 Jun 2007, Björn Steinbrink wrote: > > On 2007.06.06 12:44:42 -0300, Henrique de Moraes Holschuh wrote: > > > On Wed, 06 Jun 2007, Robert Hancock wrote: > > > > >I used kernel 2.6.21 with the libata PIIX SATA driver and a

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Henrique de Moraes Holschuh
On Wed, 06 Jun 2007, Björn Steinbrink wrote: > On 2007.06.06 12:44:42 -0300, Henrique de Moraes Holschuh wrote: > > On Wed, 06 Jun 2007, Robert Hancock wrote: > > > >I used kernel 2.6.21 with the libata PIIX SATA driver and a > > > >Seagate ST98823AS drive. > > > > > > Yes, that's expected if the

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Björn Steinbrink
On 2007.06.06 12:44:42 -0300, Henrique de Moraes Holschuh wrote: > On Wed, 06 Jun 2007, Robert Hancock wrote: > > >I used kernel 2.6.21 with the libata PIIX SATA driver and a > > >Seagate ST98823AS drive. > > > > Yes, that's expected if the drive rejects the command. > > Are *all* SATA drives rej

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Henrique de Moraes Holschuh
On Wed, 06 Jun 2007, Robert Hancock wrote: > >I used kernel 2.6.21 with the libata PIIX SATA driver and a > >Seagate ST98823AS drive. > > Yes, that's expected if the drive rejects the command. Are *all* SATA drives rejecting the command? Mine doesn't accept it, either. And it should, AFAIK, unl

Re: Bad behaviour after hdparm -M 128

2007-06-06 Thread Robert Hancock
Tino Keitel wrote: Hi, I tried to enable acoustic management on my SATA drive, because hdparm -I reported a recommended value of 128, and a current value of 0 (off). I did this: $ sudo hdparm -M 128 /dev/sda /dev/sda: setting acoustic management to 128 HDIO_DRIVE_CMD:ACOUSTIC failed: Input/o