On Sun, 10 Jan 2010 20:25:10 +0100, Mathias wrote:
> On Sun, 10 Jan 2010, Camaleón wrote:
>> @OP: Mathias, can you specify what kind of errors are you experiencing
>> with *any* of the drivers? Detection issues, package drop/lost issues,
>> connection problems, intermittent errors, system locks...?
> Well, I kinda just did, in the previous post/mail. But if you want I can
> describe it. It's a Serverworks III LE machine with the NIC on the
> motherboard, and a long time ago I installed what was lenny/sid back
> then, I think. Had some problems with it, but nothing major, then with a
> recent upgrade it stopped working, and new kernels wouldn't work either,
> just re-boot/reset. So now I have managed to install stable/lenny on it,
> from scratch. I saved all the data, home and etc on another disc for
> later use. I guess I'll use e100 from now on, but back then when it was
> not working properly, the e100 was installed with the default kernel.
> Yesterday I complied my own kernel so now I'm doing the finishing
> touches on the system. This server is a SMP/Dual P3 with 768MB RAM and
> will be used as a ftp, ssh, apache (very little, mysql and a few others.
> Let me know if you need more info.
You'll need to be a bit more specific when you state "it was not working
That is, every situation may requiere different actions:
You can get the module loaded but experience some glitches when
performing some network consuming tasks (i.e., while copying files over
nfs, or while running any program) or you can get your system not to load
the network's card configuration at all.
In the first case I will dig a bit what can be cause of the error by
reviewing the logs and perform some tests, tweaking services, etc...
In the latter case I would not doubt and try to load another network
In fact, that was exactly what I had to do some years ago: my network
card was successfully running "sk98lin" driver (Marvell chipset) and some
day it just stopped working: the system could not get any network
settings (ip, gateway, netmask...) so I changed the driver and tested
with "skge". Problem solved.
I mean, do not worry so much about the driver to use unless you are
facing some specific problems. In that case, just test with another one
(if available) and see if that solves the problem, whatever the problem
There usually are not "better" or "worse" drivers, just one that works
and other that doesn't.
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org