The pain with the Net Drivers (ne*, xirc2ps_c, etc)

From: Adrian Pop (adrpo@ida.liu.se)
Date: Fri Oct 25 2002 - 22:07:01 EST


Hi,

Sorry for bothering you people but i can't stand this anymore!
Trying to net-install a linux distribution or even get the
kenel to hack it and change these damn timeouts is impossible
since kernel 2.2 or so.
Should we throw these old network cards away and buy new ones?
Or we should probably install Windows to be able to download the
linux kernel and then to hack it?
I had to borrow another network card to upgrade my linux
after trying for 1 week to download it with xircom one.

Why can't you make the timeouts as parameters?

Now I need to restart my network card from 2 and 2 minutes to
be able to download more from the damn kernel.
It isn't a problem only for xirc2ps_cs, it is a problem for
ne drivers too and probably more others.
If you don't want your card to reset after
flooding your kernel log with tx timeouts you have to change the
timeouts by hand. Of course that is possible if you are EVER able to
download the hole kernel with the shitty driver you already have.

Well, that's about all.
Sorry for this email, i just reached the limit of my patience.

Now back to that "pushing the patience to the limits" game called
"downloading the kernel".

Regards,
Adi/

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



This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:30 EST