From: Gene Heskett <gene.heskett@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Phillip Susi <psusi@cfl.rr.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: floppy question of the hour
Date: Sun, 01 Jun 2008 20:50:29 -0400 [thread overview]
Message-ID: <200806012050.30124.gene.heskett@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0806012053440.4055@fbirervta.pbzchgretzou.qr>
On Sunday 01 June 2008, Jan Engelhardt wrote:
>On Wednesday 2008-05-28 00:26, Gene Heskett wrote:
>>On Tuesday 27 May 2008, Phillip Susi wrote:
>>>Gene Heskett wrote:
>>
>>Also, does anyone know how long after a floppy is inserted before it is
>>recognized? From observation today, it appears to be something in the 5
>> minute territory before a getfdprm returns data instead of "/dev/fd0: no
>> such device".
>
>I have a SONY USB floppy drive which used to get read within 2s
>after inserting a new floppy. Which means it somehow signalled
>the host, probably through an USB command.
>
>Just as I tried again now (with 2.6.23.17), this does not happen
>anymore so I suspect udev or the kernel changed in some way.
This is attached directly to end connector on the 34 pin floppy cable.
What I have found that seems to work, is to put the disk in, then hit it with a
junk, 1 block read from dd. That will take about 25-30 seconds to fail with an
I/O error.
Then I can do the 'setfdprm' thing, check it with getfdprm, and go ahead and
write the disk image with dd.
But if I don't knock on the door & fail once, just relying on getting a good
response from getfdprm from the setfdprm operation before trying dd, it will
_never_ work. It has to be hammered on by dd before setfdprm and getfdprm will
work, and then dd can write to it just fine.
Houston, we have a problem. But I now know how to work around it sorta like
McGiver would do I guess, but what about the next user who will never see this
thread without a truly diligent search? He will be similarly screwed, but the
only heavy breathing will be from frustration.
If the kernel should somehow shrink so it could fit on a floppy again, I'd bet
this would be fixed yet this week. :) But we all know what the chances of that
happening are. :( It would however, be muchly appreciated by us old farts
using floppies to get stuff to/from a legacy computer.
Thanks guys.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Wash: "It's Jayne being so generous with his cut that confuses and frightens
me."
Zoe: "It does kind of freeze the blood."
--Episode #10, "War Stories"
next prev parent reply other threads:[~2008-06-02 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 1:14 Gene Heskett
2008-05-24 9:28 ` Stefan Richter
2008-05-24 12:52 ` Gene Heskett
2008-05-27 21:49 ` Phillip Susi
2008-05-27 22:26 ` Gene Heskett
2008-06-01 19:00 ` Jan Engelhardt
2008-06-02 0:50 ` Gene Heskett [this message]
2008-06-02 10:28 ` Kay Sievers
2008-05-28 13:42 ` Lennart Sorensen
2008-05-28 19:38 ` Phillip Susi
2008-05-28 19:59 ` Lennart Sorensen
2008-05-28 21:58 ` Gene Heskett
2008-05-28 21:50 ` Gene Heskett
2008-05-28 21:46 ` Gene Heskett
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=200806012050.30124.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=axboe@kernel.dk \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®