From: Tim Moore <timothymoore@bigfoot.com>
To: Pascal Schmidt <pleasure.and.pain@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: System crashes with via82cxxx ide driver
Date: Thu, 30 Aug 2001 17:14:15 -0700 [thread overview]
Message-ID: <3B8ED6D7.CE237CE2@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108310035530.2970-100000@neptune.sol.net>
> > 2.2.20p9, ide.2.2.19.05042001.patch.bz2, e2fsck v1.19.
> How did you get both the 2.2.20 pre-patch and the ide patch to apply? I
> get a couple of rejects.
1. Do the pre patch first.
2. The rejects didn't make any difference. init/main.c.rej was SCSI
hd[m-t] addresses which were easy to drop in by hand,
drivers/block/ide.c.rej was comments & spacing, and the others were in
Configure.help or Makefile EXTRAVERSION conflicts. These don't matter
in most cases where the ide patch makes sense.
> > 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev
> > 10)
> The IDE part of my chipset is only revision 06, so perhaps this is a bug
> fixed in your revision.
I've another machine that uses the same kernel+ide:
00:00.0 Host bridge: VIA Technologies, Inc. VT82C585VP [Apollo VP1/VPX]
(rev 10)
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA
[Apollo VP] (rev 02)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev
02)
00:08.0 VGA compatible unclassified device: 3DLabs Permedia II 2D+3D
(rev 01)
00:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
00:0a.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
rgds,
tim.
--
next prev parent reply other threads:[~2001-08-31 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 20:52 System crashes with via82cxxx ide driver Pascal Schmidt
2001-08-30 21:45 ` Tim Moore
2001-08-30 22:37 ` Pascal Schmidt
2001-08-31 0:14 ` Tim Moore [this message]
2001-08-31 14:49 ` Pascal Schmidt
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=3B8ED6D7.CE237CE2@bigfoot.com \
--to=timothymoore@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pleasure.and.pain@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.