From: Michal Jaegermann <michal@harddata.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Michal Jaegermann <michal@harddata.com>,
dalecki@evision-ventures.com, linux-kernel@vger.kernel.org
Subject: Re: CRAP in 2.4.18-pre7
Date: Sun, 27 Jan 2002 20:40:02 -0700 [thread overview]
Message-ID: <20020127204002.A5220@mail.harddata.com> (raw)
In-Reply-To: <20020126171545.GB11344@fefe.de> <3C52E671.605FA2F3@mandrakesoft.com> <3C540A90.5020904@evision-ventures.com> <20020127114642.A2288@mail.harddata.com> <20020127225845.1bc1453a.skraw@ithnet.com>
In-Reply-To: <20020127225845.1bc1453a.skraw@ithnet.com>; from skraw@ithnet.com on Sun, Jan 27, 2002 at 10:58:45PM +0100
On Sun, Jan 27, 2002 at 10:58:45PM +0100, Stephan von Krawczynski wrote:
> On Sun, 27 Jan 2002 11:46:42 -0700
> Michal Jaegermann <michal@harddata.com> wrote:
>
> > Well, from what I know 'tulip' driver in later 2.4 kernels simply does
> > NOT work with any of my tulip cards, on x86 or on alpha,
> Hm, maybe you should shortly state which vendor (OEM or the like) you are
> using.
Ok, how about these:
# lspci -v -s 2:5.0
02:05.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41)
Subsystem: Digital Equipment Corporation DE500 Fast Ethernet
Flags: bus master, medium devsel, latency 96, IRQ 3
I/O ports at c400 [size=128]
Memory at db002000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at <unassigned> [disabled] [size=256K]
# lspci -n -s 2:5.0
02:05.0 Class 0200: 1011:0019 (rev 41)
and (another machine runing something "old" at the moment):
# lspci -v -s 0:5.0
00:05.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22)
Subsystem: Unknown device 1025:0310
Flags: bus master, medium devsel, latency 32, IRQ 18
I/O ports at 8000
Memory at 0000000004200000 (32-bit, non-prefetchable)
# lspci -n -s 0:5.0
00:05.0 Class 0200: 1011:0009 (rev 22)
This is what I happen to have on hands right now.
> I generally cannot confirm any problems with tulip-driver in 2.4.
Lucky you! The same goes for me if you do s/2.4/2.2/. :-)
> Maybe this is a specific problem with a certain vendor or board type?
Well, the vendor seems to be tulip designers and for a board type I had
exactly the same results with various x86 and Alpha boards.
If you will search through linux-kernel archives you will notice that
some people were able to restart a network with 2.4 tulip drivers by
unplugging a cable and plugging it back. Even this trick does not work
in my case. Yes, I am aware about negotiation troubles with tulips.
Forcing speed also does not help. 'de4x5' is still fine or you will be
not reading this. :-)
Michal
next prev parent reply other threads:[~2002-01-28 3:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 17:15 question about sparc 64-bit user land Felix von Leitner
2002-01-26 17:24 ` Ben Collins
2002-01-26 17:25 ` Jeff Garzik
2002-01-27 14:11 ` CRAP in 2.4.18-pre7 Martin Dalecki
2002-01-27 16:50 ` Jeff Garzik
2002-01-27 17:32 ` Martin Dalecki
2002-01-27 17:53 ` root
2002-01-27 21:08 ` H. Peter Anvin
2002-01-28 12:06 ` Martin Dalecki
2002-01-28 15:37 ` H. Peter Anvin
2002-01-27 18:46 ` Michal Jaegermann
2002-01-27 21:58 ` Stephan von Krawczynski
2002-01-28 3:40 ` Michal Jaegermann [this message]
2002-01-26 18:07 ` question about sparc 64-bit user land Andreas Jaeger
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=20020127204002.A5220@mail.harddata.com \
--to=michal@harddata.com \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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.