From: jbradford@dial.pipex.com
To: linux-kernel@vger.kernel.org
Subject: Re: ide drive dying?
Date: Sun, 8 Sep 2002 15:14:20 +0100 (BST) [thread overview]
Message-ID: <200209081414.g88EELZK002695@darkstar.example.net> (raw)
In-Reply-To: <alfaco$3u0$1@forge.intermeta.de> from "Henning P. Schmiedehausen" at Sep 08, 2002 10:56:24 AM
> >The firmware update is for many more drives than that, My own
>
> > Model=IBM-DTLA-305040, FwRev=TW4OA60A
>
> >is also recommended, as well as many with a FwRev=xxxOyzzz with zzz<66A.
> >Now i have to find a windows machine to try it out on...
>
> You don't need to. All you need is someone run this tool and send you
> the image it creates. I put mine as boot.img on a CD so I can upgrade
> all the disks I have in boxes without floppy disk drives. It's a self
> booting DOS disk.
As the old firmware is known to be buggy, and those bugs are relevant when using Linux, and updated firmware is available, is it worth checking for the known buggy firmware version in the ide driver?
I realise that we cannot check every drive in the world for compatibility, but if this is a known issue...
John.
next prev parent reply other threads:[~2002-09-08 14:02 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 15:13 DevilKin
2002-09-06 15:26 ` Mike Dresser
2002-09-06 15:39 ` Alan Cox
2002-09-06 15:42 ` Mike Dresser
2002-09-06 16:14 ` Billy Harvey
2002-09-06 16:41 ` Mike Dresser
2002-09-06 18:00 ` jbradford
2002-09-06 17:58 ` Mike Dresser
2002-09-06 15:44 ` Richard B. Johnson
2002-09-06 16:19 ` Craig Ruff
2002-09-06 17:28 ` Daniel Egger
2002-09-06 15:36 ` jbradford
2002-09-06 15:55 ` DevilKin
2002-09-06 17:22 ` jbradford
2002-09-06 19:22 ` DevilKin
2002-09-07 9:30 ` Anders Fugmann
2002-09-07 9:37 ` Udo A. Steinberg
2002-09-07 15:54 ` Holger Lubitz
2002-09-07 16:31 ` jbradford
2002-09-07 12:31 ` Daniel Egger
2002-09-07 13:08 ` jbradford
2002-09-07 13:50 ` Daniel Egger
2002-09-07 15:02 ` jbradford
2002-09-07 20:19 ` Daniel Egger
2002-09-07 20:41 ` jbradford
2002-09-07 21:41 ` Alan Cox
2002-09-07 21:41 ` Alan Cox
2002-09-07 22:00 ` jbradford
2002-09-07 23:19 ` David Forrest
2002-09-08 10:56 ` Henning P. Schmiedehausen
2002-09-08 14:14 ` jbradford [this message]
2002-09-09 21:59 ` Alan Cox
2002-09-07 22:05 ` Andre Hedrick
2002-09-07 7:08 ` Andre Hedrick
2002-09-06 15:37 ` mbs
2002-09-06 15:54 ` Alan Cox
2002-09-06 15:38 ` Alan Cox
2002-09-06 17:33 ` Daniel Egger
2002-09-06 20:31 ` Alan Cox
2002-09-06 15:44 ` mbs
2002-09-06 17:46 ` mbs
2002-09-06 20:32 ` Alan Cox
2002-09-07 12:34 ` Daniel Egger
2002-09-07 7:02 ` Andre Hedrick
2002-09-07 7:42 ` jbradford
2002-09-07 7:50 ` Andre Hedrick
2002-09-06 20:40 Hell.Surfers
2002-09-06 21:01 ` Alan Cox
2002-09-07 1:02 ` Jason L Tibbitts III
[not found] <Pine.LNX.4.33.0209062017230.14523-100000@coffee.psychology.mcmaster.ca>
2002-09-07 6:09 ` jbradford
2002-09-08 0:02 Dieter Nützel
2002-09-08 17:42 ` jbradford
2002-09-09 1:31 ` Nuitari
2002-09-08 19:27 ` Ed Sweetman
2002-09-08 20:11 ` jbradford
2002-09-09 2:37 ` Nuitari
2002-09-09 12:26 ` Joachim Breuer
2002-09-09 18:17 ` Thunder from the hill
2002-09-09 18:55 ` Mike Dresser
2002-09-10 12:48 ` Ookhoi
2002-09-10 13:59 ` Mike Dresser
2002-09-10 14:56 ` jbradford
2002-09-10 15:21 ` Mike Dresser
2002-09-10 15:29 ` Larry McVoy
2002-09-10 20:21 ` Andre Hedrick
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=200209081414.g88EELZK002695@darkstar.example.net \
--to=jbradford@dial.pipex.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
all inboxes | Powered by JetHome®