Studierende der Universitaet des Saarlandes <[EMAIL PROTECTED]> writes:
> Could you post the output of
>
> #tulip-diag -mm -aa -f
>
> with the broken driver?
> Some code that's required for Linksys Tulip clones was moved from pnic
> specific part into the generic part, perhaps that causes prob
In article <[EMAIL PROTECTED]> you wrote:
> Okay, so Jeff Garzik already knows about this - I told him last week -
> but seeing as how the code has made it to a Linus pre-release without
> a fix I thought I'd better post the breakage description to l-k!
Try drivers from http://sourceforge.net/pr
> Could you post the output of
>
> #tulip-diag -mm -aa -f
>
> with the broken driver?
> Some code that's required for Linksys Tulip clones was moved
> from pnic specific part into the generic part, perhaps that
> causes problems.
Here is the output from the kernels I've tested to try to get the
Could you post the output of
#tulip-diag -mm -aa -f
with the broken driver?
Some code that's required for Linksys Tulip clones was moved from pnic
specific part into the generic part, perhaps that causes problems.
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe li
Okay, so Jeff Garzik already knows about this - I told him last week -
but seeing as how the code has made it to a Linus pre-release without
a fix I thought I'd better post the breakage description to l-k!
The symptoms are:
In 2.4.5-pre4 (and 2.4.4-ac8 and above - note: I didn't try -ac7)
system
Well, I guess I should chip in here with the rather amusing fact that
2.4.4 is the first kernel *not* to do this to me... ;-)
I am, of course, glad to help out testing stuff if needed. My card is
also a LinkSys LNE100TX v4.1, which the tulip driver identifies as an
ADMtek Comet rev 17 (althoug
On 01-May-2001, Jeff Garzik wrote:
> Ronny Haryanto wrote:
> >
> > Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
>
> Does 2.4.3 work for you?
Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug
introduced between 2.4.3 and 2.4.4. Too bad I ca
Ronny Haryanto wrote:
>
> Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
Does 2.4.3 work for you?
--
Jeff Garzik | Game called on account of naked chick
Building 1024|
MandrakeSoft |
-
To unsubscribe from this list: send the line "unsubscribe linux-ker
Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
The log says:
Apr 30 10:30:59 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out
Apr 30 10:30:59 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12
, resetting...
Apr 30 10:31:07 fluke kernel:
Well it would appear the tulip driver regressed from 2.4.2-ac22 and
2.4.3. (2.4.3-ac12 isn't working either) Once again, my tulip card just
spews carrier errors and doesn't even get a link light.
If someone could point me to a patch I would appreciate it. I have
attached any pretient information
10 matches
Mail list logo
