From: Trevor Woerner <ppc339@vtnet.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: can't write
Date: Wed, 28 May 2003 23:19:27 -0400 [thread overview]
Message-ID: <200305282319.27041.ppc339@vtnet.ca> (raw)
Now that I can get to the point where I can configure and mount my
compact flash card I find yet another interesting twist... I can't
write to the device.
If I mount it read-only everything is fine. I can read the device, do a
directory listing, copy thing from it, execute binaries, open files...
all that nice stuff. But the instant I try to write, things go up in
smoke.
I wrote my own test modules to try to isolate this issue so I can study
it more. My module gives the same results the kernel gets: no matter
what is written to the device (ATA command 0x30), the entire sector
always ends up being entirely filled with zeros.
Whether I write "0xbeef" 256 times or copy one sector (say sector 0) to
some other place. When I read the newly written sector back, all it
contains are zeros.
Anyone seen something like this before?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-05-29 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 3:19 Trevor Woerner [this message]
[not found] ` <20030529100632.A22378@forte.austin.ibm.com>
2003-05-30 11:09 ` can't write Trevor Woerner
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=200305282319.27041.ppc339@vtnet.ca \
--to=ppc339@vtnet.ca \
--cc=linuxppc-dev@lists.linuxppc.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).