From: thomas schorpp <t.schorpp@gmx.de>
To: linux-ide@vger.kernel.org
Subject: hdparm ATA Security Options return errors
Date: Mon, 17 Oct 2005 19:14:25 +0200 [thread overview]
Message-ID: <4353DBF1.1060001@gmx.de> (raw)
In-Reply-To: <S1750797AbVJQQjQ/20051017163916Z+71@vger.kernel.org>
hi,
hdparm
ATA Security Options:
--security-unlock PWD Unlock drive, using password PWD (DANGEROUS)
--security-set-pass PWD Lock drive, using password PWD (DANGEROUS)
--security-disable PWD Disable drive locking, using password
PWD (DANGEROUS)
--security-mode MODE Specify user/master password and
high/maximum security
fail by returning errors "cannot allocate mem", "invalid argument", with
hdparm binary from debian stable...sid / whax /knoppix with kernels
2.6.11...2.6.13...latest debian sid image with
usual via ide + sil680 controllers and
ATA device, with non-removable media
Model Number: Maxtor 6E040L0
Serial Number: E14FQN5E
Firmware Revision: NAR61590
Standards:
Supported: 7 6 5 4
ATA device, with non-removable media
Model Number: ST3120026A
Serial Number: 3JT4RYCB
Firmware Revision: 8.01
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 2
Supported: 6 5 4 3
.
does it help to compile hdparm from source against the vanilla kernel?
wheres the latest source? biblio? or is there a cvs?
meanwhile ill take a look at the debian sid source package's code...
y
tom
next parent reply other threads:[~2005-10-17 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1750797AbVJQQjQ/20051017163916Z+71@vger.kernel.org>
2005-10-17 17:14 ` thomas schorpp [this message]
2005-10-17 17:41 ` hdparm ATA Security Options return errors thomas schorpp
2005-10-17 20:31 ` Mark Lord
2005-10-17 20:52 ` thomas schorpp
2005-10-19 7:56 ` thomas schorpp
2005-10-19 15:12 ` Mark Lord
2005-10-19 15:20 ` thomas schorpp
2005-10-19 16:24 ` thomas schorpp
2005-10-20 3:10 ` Mark Lord
2005-10-19 17:35 Timothy Thelin
2005-10-20 3:09 ` Mark Lord
2005-10-20 7:51 ` thomas schorpp
2005-10-20 11:18 ` thomas schorpp
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=4353DBF1.1060001@gmx.de \
--to=t.schorpp@gmx.de \
--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).