public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
	"J.A. Magallon" <jamagallon@able.es>
Subject: Re: floppy in 2.4.17
Date: Sat, 23 Feb 2002 18:10:49 +0100	[thread overview]
Message-ID: <3C77CD19.2040501@wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0202231100230.11337-100000@filesrv1.baby-dragons.com>

Have you tried booting with "pnpbios=no-res" ?


Mr. James W. Laferriere wrote:
> 	Hello All ,  More info ...  Hth ,  JimL
> 
> On Sat, 23 Feb 2002, Mr. James W. Laferriere wrote:
> 
>>	Hello J.A. , Nice name .  I have verified that the floppy drive
>>	under 2.4.18-pre3 is in the same shape . Hth ,  JimL
>>
> 
>># fdformat /dev/fd0u1440		,  Hmmm ,  Move little tab .
>>/dev/fd0u1440: Read-only file system
>># fdformat /dev/fd0u1440		,  Hmmm ......
>>/dev/fd0u1440: Read-only file system
>># tar -ztvf /dev/fd0			,  Hmmm ,  J.A.'s right .
>>(hang ..wait several minutes..)^C
>>tar (grandchild): Read error on /dev/fd0: Input/output error
>>tar (grandchild): At beginning of tape, quitting now
>>tar (grandchild): Error is not recoverable: exiting now
>>
>>gzip: stdin: unexpected end of file
>>tar: Child returned status 1
>>tar: Error exit delayed from previous errors
>>
> 
> VFS: Disk change detected on device fd(2,28)
> VFS: Disk change detected on device fd(2,28)
> VFS: Disk change detected on device fd(2,28)
> VFS: Disk change detected on device fd(2,28)
> VFS: Disk change detected on device fd(2,0)
> end_request: I/O error, dev 02:00 (floppy), sector 0
> end_request: I/O error, dev 02:00 (floppy), sector 0
> end_request: I/O error, dev 02:00 (floppy), sector 2
> end_request: I/O error, dev 02:00 (floppy), sector 4
> end_request: I/O error, dev 02:00 (floppy), sector 6
> 
> 
> 
>>On Sat, 23 Feb 2002, J.A. Magallon wrote:
>>
>>
>>>Hi.
>>>
>>>I am getting problems with floppy drive in 2.4.17.
>>>All started with floppy not working in 18-rc4, went back to 17
>>>and still does not work. Just plain 2.4.17, no patching.
>>>
>>>mkfs -t ext2 /dev/fd0 just hangs forever.
>>>
>>>mkfs -v -t ext2 /dev/fd0 gives:
>>>
>>>mke2fs 1.26 (3-Feb-2002)
>>>mkfs.ext2: bad blocks count - /dev/fd0
>>>
>>>Hardware:
>>>
>>>Floppy drive(s): fd0 is 1.44M
>>>FDC 0 is a post-1991 82077
>>>ide-floppy driver 0.97.sv
>>>
>>>???
>>>
>>>TIA
>>>




Pierre
-- 
------------------------------------------------
  Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------


  reply	other threads:[~2002-02-23 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23 15:05 floppy in 2.4.17 J.A. Magallon
2002-02-23 15:59 ` Mr. James W. Laferriere
2002-02-23 16:04   ` Mr. James W. Laferriere
2002-02-23 17:10     ` Pierre Rousselet [this message]
2002-02-24  2:09       ` Mr. James W. Laferriere
2002-02-23 18:49 ` Heinz Diehl
2002-02-23 22:00   ` Chris Sykes
2002-02-24  3:05     ` Mike Fedyk
2002-02-24 13:46       ` Heinz Diehl
2002-02-24 20:00         ` Pierre Rousselet

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=3C77CD19.2040501@wanadoo.fr \
    --to=pierre.rousselet@wanadoo.fr \
    --cc=babydr@baby-dragons.com \
    --cc=jamagallon@able.es \
    --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