From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Jan Rekorajski <baggins@sith.mimuw.edu.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
jes@trained-monkey.org
Subject: Re: acenic breakage in 2.4.13-pre
Date: Wed, 24 Oct 2001 10:56:44 -0400 [thread overview]
Message-ID: <3BD6D6AC.B9CF58EB@mandrakesoft.com> (raw)
In-Reply-To: <20011024164533.C15474@sith.mimuw.edu.pl>
Jan Rekorajski wrote:
>
> On Tue, 23 Oct 2001, Jeff Garzik wrote:
>
> > If there are no complaints nor better suggestions, I would prefer to use
> > the code in acenic.c / 8139cp.c as a base, since that code has been
> > stable for a little while.
>
> Speaking of acenic - it's broken in 2.4.13-pre. I have 3c985 and all I
> get with 2.4.13-pre is "Firmware NOT running!". After I backed the
> changes from -pre patch it started and works fine. Maybe the problem is
> I have it in 32bit PCI slot?
Several people have reported this bug.
Alexey, are the 2.4.13 acenic changes yours? You had mentioned hacking
on it... Jes, the maintainer, is CC'd too.
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-10-24 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 14:45 acenic breakage in 2.4.13-pre Jan Rekorajski
2001-10-24 14:56 ` Jeff Garzik [this message]
2001-10-24 15:24 ` David S. Miller
2001-10-24 15:29 ` David S. Miller
2001-10-24 16:04 ` Jan Rekorajski
2001-10-24 16:36 ` David S. Miller
2001-10-24 18:49 ` Jan Rekorajski
2001-10-24 19:14 ` J Sloan
2001-10-24 20:10 ` [PATCH] Acenic fix (was Re: acenic breakage in 2.4.13-pre) David S. Miller
2001-10-24 15:40 ` acenic breakage in 2.4.13-pre David S. Miller
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=3BD6D6AC.B9CF58EB@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=baggins@sith.mimuw.edu.pl \
--cc=jes@trained-monkey.org \
--cc=kuznet@ms2.inr.ac.ru \
--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 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.