public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: 2.6.23.9: x86_64: floppy not working: p35 chipset
Date: Fri, 07 Dec 2007 13:23:16 -0500	[thread overview]
Message-ID: <47598F94.6090305@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712071254580.26042@p34.internal.lan>

Justin Piszcz wrote:
>
>
> On Fri, 7 Dec 2007, Bill Davidsen wrote:
>
>> Justin Piszcz wrote:
>>> Trying to format a floppy (2-3 of them) on a GA-P35-DS4 2.0 with a 
>>> regular Sony floppy on Debian x86_64 with kernel 2.6.23.9:
>>>
>>> # fdformat /dev/fd0
>>> Could not determine current format type: No such device
>>> # mformat a:
>>> mformat: Could not get geometry of device (No such device)
>>> #
>>>
>>> # cat /proc/interrupts |grep floppy
>>>   6:         38         37         39         41   IO-APIC-edge      
>>> floppy
>>>
>>> # dmesg|grep -A1 fd0
>>> [   52.689487] Floppy drive(s): fd0 is 1.44M
>>> [   52.704661] FDC 0 is a post-1991 82077
>>>
>>> During the 'attempted format'
>>>
>>
>>>
>>> I've tried a few different floppies, the result is the same.  The 
>>> system is 64-bit only, no 32-bit emulation is enabled using a strict 
>>> 64-bit-only userland.  Has anyone else gotten their floppy drive to 
>>> work under 64-bit?
>>>
>>> Is this just a case of a DOA floppy drive or is something else wrong?
>>>
>> Maybe booting from a 32 bit live CD would help determine that. It 
>> certainly was seen at boot time. Didn't get hooked to some SCSI 
>> device name by udev, did it?
>>
>>
>> -- 
>> Bill Davidsen <davidsen@tmr.com>
>>  "We have more to fear from the bungling of the incompetent than from
>> the machinations of the wicked."  - from Slashdot
>>
>
> Retried with some other floppies and later tried the original, 
> everything seems to be working now, must have been a bad floppy/some 
> transient issue.

Great! I did test that FC8 with a Fedora kernel will see and use the 
floppy. Even found a floppy to use. Now I have to figure out why I have 
a floppy with a gzipped ext2 filesystem on it. :-(
Doesn't appear to be bootable, I thought it might be SYSLINUX for an old 
system which couldn't boot from CD or USB, but that doesn't seem to be 
the case.

Anyway, glad the problem went away.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



      reply	other threads:[~2007-12-07 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06  9:44 2.6.23.9: x86_64: floppy not working: p35 chipset Justin Piszcz
2007-12-07 18:10 ` Bill Davidsen
2007-12-07 17:55   ` Justin Piszcz
2007-12-07 18:23     ` Bill Davidsen [this message]

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=47598F94.6090305@tmr.com \
    --to=davidsen@tmr.com \
    --cc=apiszcz@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@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