From: Larry Finger <Larry.Finger@lwfinger.net>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: Question about LS120 floppies
Date: Thu, 02 Jul 2009 19:20:08 -0500 [thread overview]
Message-ID: <4A4D4EB8.5080503@lwfinger.net> (raw)
In-Reply-To: <4A4D48A6.2060204@gmail.com>
Robert Hancock wrote:
> On 07/02/2009 11:12 AM, Alan Cox wrote:
>> On Thu, 02 Jul 2009 09:01:02 -0500
>> Larry Finger<Larry.Finger@lwfinger.net> wrote:
>>
>>> Robert Hancock wrote:
>>>> On 07/01/2009 02:30 PM, Larry Finger wrote:
>>>>> I have been trying to help someone on the openSUSE forums. He is
>>>>> running a 2.6.27 kernel and finds that his "Super Floppy" drive works
>>>> Are they using the old IDE drivers, or libata? Do they have any kernel
>>>> output, etc?
>>> In 2.6.27, I think he has the old IDE driver, but I'm not sure. In any
>>> case, the entire thread on the openSUSE forum is at
>>>
>>> http://forums.opensuse.org/hardware/417147-ls-120-opensuse-11-a.html
>>>
>>> Thanks for any help you can give.
>>
>> Basically four content free pages. Ignoring all the stuff about HAL the
>> hardware is detected and the drive reports that the media type is not
>> supported.
>>
>> That all appears to be working beautifully, although I've no idea why the
>> media type is not supported - I wonder if something is trying to read the
>> wrong block sizes or if the LS120 has some magic no standard bits.
>>
>> Unfortunately they are very very obscure hardware.
>
> Yes, definitely a lot of uninformed speculation on that thread. The
> floppy driver has nothing to do with any IDE/ATA drive like this, and if
> OpenSUSE is using libata drivers then attempting to load the IDE floppy
> driver is also useless.
>
> It would be useful if the reporter could verify that the drive is at all
> functional with that media under any OS. That "Cannot read medium -
> unknown format" is being reported by the drive itself in response to a
> "read capacity" request, not the driver. So unless there's some magic
> that the driver needs to do to get the drive to recognize the disc, it
> seems like a hardware problem.
The OP seemed more interested in ranting about the state of drivers in
Linux than in getting his device to work. He is sending the hardware
and a couple of new disks to me so that I can figure what is wrong.
He is currently trying to purchase a Panasonic drive on Ebay, as he
claims that the coding is different than for the Matshitu drives. At
least there is a different driver under DOS. These drives don't even
have Windows drivers. I'm prepared to try his drive with FreeDOS on my
machine when it arrives.
Larry
next prev parent reply other threads:[~2009-07-03 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 20:30 Question about LS120 floppies Larry Finger
2009-07-02 5:22 ` Robert Hancock
2009-07-02 14:01 ` Larry Finger
2009-07-02 17:12 ` Alan Cox
2009-07-02 23:54 ` Robert Hancock
2009-07-03 0:20 ` Larry Finger [this message]
2009-08-02 23:19 ` Larry Finger
2009-08-03 2:42 ` Robert Hancock
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=4A4D4EB8.5080503@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--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).