From: Adam Huffman <bloch@verdurin.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Boot problem with PDC20269
Date: Sun, 24 Feb 2002 03:19:47 +0000 [thread overview]
Message-ID: <20020224031947.A1098@bloch.verdurin.priv> (raw)
In-Reply-To: <20020223205342.C2603@bloch.verdurin.priv> <Pine.LNX.4.30.0202232200290.13755-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0202232200290.13755-100000@mustard.heime.net>; from roy@karlsbakk.net on Sat, Feb 23, 2002 at 22:02:33 +0100
On Sat, 23 Feb 2002, Roy Sigurd Karlsbakk wrote:
> > > er .. I'm running a PDC20269 with a few drives. Is that supposed to be
> > > impossible?
> > >
> > > roy
> > >
> >
> > May I ask which kernel you are running?
>
> linux-2.4.18pre3 + tux + linuxdiskcert.org's ide_2.4.17 patch
> --
> Roy Sigurd Karlsbakk, Datavaktmester
>
I've managed to boot successfully now with 2.4.18-rc2-ac2.
I get the following messages when I mount the IBM 60GXP:
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
PDC202XX: Primary channel reset.
ide2: reset: success
but mounting does proceed. No such problem with the Maxtor.
Adam
next prev parent reply other threads:[~2002-02-24 3:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 1:53 Adam Huffman
2002-02-23 3:56 ` Andre Hedrick
2002-02-23 12:14 ` Gunther Mayer
2002-02-23 13:16 ` Adam Huffman
2002-02-23 20:18 ` Mike Fedyk
2002-02-23 20:33 ` Roy Sigurd Karlsbakk
2002-02-23 20:36 ` Mike Fedyk
2002-02-23 20:53 ` Adam Huffman
2002-02-23 21:02 ` Roy Sigurd Karlsbakk
2002-02-24 3:19 ` Adam Huffman [this message]
2002-02-25 16:09 ` Holger Lubitz
2002-02-25 16:39 ` Alan Cox
2002-02-25 16:46 ` Mike Fedyk
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=20020224031947.A1098@bloch.verdurin.priv \
--to=bloch@verdurin.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®