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
4 matches
Mail list logo
