Floppy Access Goes Nowhere

Net Llama! netllama
Mon May 17 11:49:02 PDT 2004


On 07/05/03 19:45, Kurt Wall wrote:

> Quoth Net Llama!:
> 
>>On 07/05/03 18:44, Kurt Wall wrote:
>>
>>>Hi, list,
>>>
>>>This is strange. I have a standard 3.5" floppy drive. Lately (the last
>>>few weeks), every time I want to use the floppy drive, I slap a floppy
>>>in, try to mount the drive, and it just hangs. The mtools suite does
>>>the same thing. The light goes on as if the disk is being accessed,
>>>but the command prompt never returns. If I call the xterm, the disk
>>>access continues. Just for kicks, I swapped the drive out with a known
>>>good one and still no joy. 
>>>
>>>Kernel-wise, CONFIG_BLK_DEV_FD is enabled, but CONFIG_BLK_DEV_IDEFLOPPY 
>>>isn't (it will be shortly). I don't recall off the top of my head if
>>>IDEFLOPPY was configured in the kernel(s) I was running when this
>>>last worked. I'm kinda stumped. Any ideas?
>>
>>Any errors in dmesg or messages?  If I had to guess, i'd say either the 
>>cable is lose, or the floppy controller on the mobo is dead/dying.
> 
> 
> No joy with CONFIG_BLK_DEV_IDEFLOPPY, either. I've checked the cable,
> and it seems to be okay. Tried it with different floppies, too. I get
> I/O errors during the verify stage of fdformat (the format goes just
> fine). superformat complains mightily, too. This is on one of the systems
> I bought from VA as it was going out of the hardware business (I ended
> up buying three - one each for me, my dad, and my brother). I suppose

Ah, the one i sold you ;)  This is the 420 or the 660?

> I could pop for a controller - they couldn't be that expensive.
> 
> syslog says:
> 
> Jul  5 21:42:10 luther kernel: floppy0: Over/Underrun - retrying
> Jul  5 22:01:58 luther kernel: floppy0: Over/Underrun - retrying
> Jul  5 22:01:58 luther kernel: floppy0: Over/Underrun - retrying
> Jul  5 22:01:59 luther kernel: floppy0: Over/Underrun - retrying
> 
> Turning on debug shows all of ioctl()s going across, but nothing
> that looked bad to me (but I might not know what misbehavior looks
> like, either). A couple of examples:
> 
> Jul  5 22:22:32 luther kernel: floppy0: reschedule timeout lock fdc
> Jul  5 22:22:32 luther kernel: floppy0: reschedule timeout do wakeup

If you can read German, this dude was having the same problem:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&threadm=slrnar15ib.ok.mlimb%40archimedes.lan1&rnum=1&prev=/groups%3Fas_epq%3Dreschedule%2520timeout%2520do%2520wakeup%26safe%3Doff%26ie%3DUTF-8%26oe%3DUTF-8%26as_ugroup%3D*linux*%26lr%3D%26num%3D50%26hl%3Den

Other than that, i'd say that the controller might be dead.  Sorry.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                       	       netllama at linux-sxs.org
Linux Step-by-step & TyGeMo: 		    http://netllama.ipfox.com

   9:10pm  up  6:12,  1 user,  load average: 0.52, 0.53, 0.64



More information about the Linux-users mailing list