All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny ter Haar <dth@lin-gen.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Drivers under 2.4
Date: Thu, 11 Jan 2001 11:58:33 +0100	[thread overview]
Message-ID: <20010111115833.A27971@lin-gen.com> (raw)
In-Reply-To: <20010110223836.A7321@gruyere.muc.suse.de> <Pine.LNX.4.30.0101110003020.30013-100000@prime.sun.ac.za> <93k1k0$87v$1@voyager.cistron.net> <20010111113134.A20569@gruyere.muc.suse.de>
In-Reply-To: <20010111113134.A20569@gruyere.muc.suse.de>; from ak@suse.de on Thu, Jan 11, 2001 at 11:31:34AM +0100



According to Andi Kleen:
> "Doesn't work" isn't a very useful bug report. What happens exactly?
> Do the RX/TX/error counters increase when you try to send packets? 


no, the counters you see with ifconfig eth0 are set to zero
for rx and to 1 for tx.

So it's trying to send out data but somehow it doesn't work.
Since the driver version is the same (althoud the output is
slihtly different which seems odd) i suspect the PCI
probing to be folded somewhere.

How could i provide people with more info ?

Thanks,

Danny
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-11 10:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  9:12 Failure building 2.4 while running 2.4. Success in building 2.4 while running 2.2 Silviu Marin-Caea
2001-01-09 10:17 ` Alessandro Suardi
2001-01-09 10:33   ` Failure building 2.4 while running 2.4. Success in building 2.4 Alan Cox
2001-01-09 18:20     ` Failure building 2.4 while running 2.4. There is no such thing Silviu Marin-Caea
2001-01-09 18:43       ` Alan Cox
2001-01-09 19:57       ` Drivers under 2.4 Dennis
2001-01-09 20:13         ` suser checks in 2.2.x Bosko Radivojevic
2001-01-09 18:39           ` Arnaldo Carvalho de Melo
2001-01-10 18:22       ` Drivers under 2.4 Dennis
2001-01-10 20:01         ` Hans Grobler
2001-01-10 21:37         ` Dennis
2001-01-10 21:38           ` Andi Kleen
2001-01-10 22:08             ` Hans Grobler
2001-01-11 10:24               ` Danny ter Haar
2001-01-11 10:31                 ` Andi Kleen
2001-01-11 10:58                   ` Danny ter Haar [this message]
2001-01-11 11:36                     ` Andrew Morton
2001-01-11 11:58                       ` Danny ter Haar
2001-01-11 14:00                         ` Danny ter Haar
2001-01-11 14:32                           ` Jeff Garzik
2001-01-11 16:33                             ` Danny ter Haar
2001-01-11 16:44                               ` Hans Grobler
2001-01-12 11:50                                 ` PRoblem with pcnet32 under 2.4.0 , was :Drivers " Danny ter Haar
2001-01-12 12:01                                   ` Hans Grobler
2001-01-12 12:16                                     ` Danny ter Haar
2001-01-12 22:33                                   ` Thomas Bogendoerfer
2001-01-15 16:29                                     ` Danny ter Haar
2001-01-11 12:56                 ` Drivers " Alan Cox
2001-01-09 10:28 ` Failure building 2.4 while running 2.4. Success in building 2.4 while running 2.2 Alan Cox
2001-01-09 16:10 ` [rlug] " Eugen
2001-01-09 19:01 ` J Sloan

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=20010111115833.A27971@lin-gen.com \
    --to=dth@lin-gen.com \
    --cc=ak@suse.de \
    --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.