I am running RH6.1 on my system with kernel
2.2.14. I have also tried this under 2.2.13.
I have a 3c900 card that works nicely (uses
the 3c59x driver) with my DSL. I have this
compiled into the kernel because whenever I
try to use it as a module, the card will not
initialize nor work properly. What follows is
from running dmesg once trying to use 3c59x
as a module:
eth0: transmit timed out, tx_status 00 status e000.
Flags; bus-master 1, full 1; dirty 0 current 16.
Transmit list 00000000 vs. c7044a00.
0: @c7044a00 length 8000024e status 0000024e
1: @c7044a10 length 8000024e status 0000024e
2: @c7044a20 length 8000024e status 0000024e
3: @c7044a30 length 8000024e status 0000024e
4: @c7044a40 length 8000024e status 0000024e
5: @c7044a50 length 8000024e status 0000024e
6: @c7044a60 length 8000024e status 0000024e
7: @c7044a70 length 8000024e status 0000024e
8: @c7044a80 length 8000024e status 0000024e
9: @c7044a90 length 8000024e status 0000024e
10: @c7044aa0 length 8000024e status 0000024e
11: @c7044ab0 length 8000024e status 0000024e
12: @c7044ac0 length 8000024e status 0000024e
13: @c7044ad0 length 8000024e status 0000024e
14: @c7044ae0 length 8000024e status 8000024e
15: @c7044af0 length 8000024e status 8000024e
This repeats twice. During bootup with a modular
3c59x driver and eth0 set to activate at bootup
(I am using dhcpcd), there is a loooooong delay as
the above errors play out. The end result is that
the 3com doesn't connect to the net, doesn't get
an IP address, doesn't work. If I manually run
dhcpcd or ifup eth0 after bootup, initialization
still fails. I have also tried NOT activating it
at bootup and doing it manually. Doesn't work.
It works GREAT when compiled into the kernel,
however. Properly identified, properly initialized,
and an IP is assigned.
The next problem involves trying to add a second
card (a netgear card, forget the name but it uses
the tulip driver). I wanted to add the second
card so I could connect my laptop to my desktop
system sometimes to permit both internet access to
my laptop at home and for the exchange of files
between my desktop and laptop (now running RH6.0
until I can upgrade to 6.1).
With the 3com driver compiled into the kernel and
the tulip used as a module for eth1, it doesn't
work. As soon as I add the netgear, my 3com wont
work. Trying to activate the 3com on eth0 results
in the same situation as trying to use the 3com
driver as a module - initialization fails. Letting
kudzu detect and setup the netgear also results in
an entry being made to conf.modules in which both
eth0 and eth1 is aliased to tulip.
I removed the eth0 alias and rebooted - bootup messages
indicate that the 3com is properly detected and
initialized and the tulip module gets loaded but I
am unable to activate eth0. I have checked the
network settings and this occurs even when I remove
all settings for eth1 using nettool from control-panel
(I just don't "get" linuxconf...it isn't self-explanatory
for many entries).
I have also made sure that eth1 doesn't get activated
at bootup but eth0 still fails to activate. Removing
the netgear card results in eth0 (3com) working again
but only when it is compiled into the kernel - NEVER
as a module.
Can anyone explain what the deal is?
patrick
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
