PDA

View Full Version : 10BaseT problem on 3c900



Canis
09-21-2003, 06:11 PM
I have trouble getting my Ethernet card to work. It is a 3C900. I connected it using a twistet pair cable to my router. Starting Windows everything works fine, so it shouldn't be Hardware.

I am working with Knoppix 3.2 which is based on Linux kernel 2.4.22.

I can ping on myself, but when pinging my gateway I get:
====
PING 192.168.0.1 (192.168.0.1): 56 data bytes

--- 192.168.0.1 ping statistics ---
19 packets transmitted, 0 packets received, 100% packet loss
====

After that ifconfig says:

====
eth0 Protokoll:Ethernet Hardware Adresse 00:60:08:C8:B6:B3
inet Adresse:192.168.0.101 Bcast:192.168.0.255 Maske:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:3 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:9 Basisadresse:0xb800

lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:41 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:3656 (3.5 KiB) TX bytes:3656 (3.5 KiB)
====

dmesg says (including the audio device working on same interrupt):

====
PCI: Found IRQ 9 for device 02:0c.0
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
See Documentation/networking/vortex.txt
02:0c.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xb800. Vers LK1.1.18-ac
PCI: Setting latency timer of device 02:0c.0 to 64
00:60:08:c8:b6:b3, IRQ 9
product code 4b4c rev 00.0 date 12-03-97
Internal config register is 330218, transceivers 0xe138.
8K word-wide RAM 3:5 Rx:Tx split, 10base2 interface.
Enabling bus-master transmits and whole-frame receives.
02:0c.0: scatter/gather enabled. h/w checksums disabled
eth0: Dropping NETIF_F_SG since no checksum feature.
Creative EMU10K1 PCI Audio Driver, version 0.20, 00:02:24 Sep 6 2003
PCI: Found IRQ 9 for device 02:0a.0
PCI: Setting latency timer of device 02:0a.0 to 64
emu10k1: EMU10K1 rev 7 model 0x8061 found, IO at 0xd400-0xd41f, IRQ 9
ac97_codec: AC97 Audio codec, id: 0x8384:0x7608 (SigmaTel STAC9708)
emu10k1: SBLive! 5.1 card detected
====

The silly thing: It states 10base2 even if I insert in modules.conf:

====
options eth0 debug=1 options=0 full_duplex=1
====

What can I do else?

Stephen
09-21-2003, 10:18 PM
The silly thing: It states 10base2 even if I insert in modules.conf:

====
options eth0 debug=1 options=0 full_duplex=1
====

What can I do else?
You should not be putting the line in modules.conf it should be put in either it's own file in /etc/modutils or in /etc/modutils/aliases and the line does not look like it is correct to set my card for full-duplex I use this in the aliases file.


# Added by me for network card full duplex
alias eth0 tulip
options tulip options=4


This forces the tulip driver to use the full duplex settings you should be doing similar for your cards module (3c59x IIRC).

You can also check in /etc/network/interfaces to make sure that you have the settings right for the gateway and that the module for the card is actually loaded and in use.

Canis
09-22-2003, 01:00 AM
Thanx for your answer!

I will look after the files you statet.

The options will depend on what the driver does recognize, so the paramters of tulip and 3c59x are not comparable.

The module is loaded.

Stephen
09-22-2003, 01:15 AM
The options will depend on what the driver does recognize, so the paramters of tulip and 3c59x are not comparable.

The module is loaded.

The options would be different for each driver you should look in the docs for the module for the correct settings. The module is loaded but is it in use?

Canis
09-22-2003, 12:53 PM
Now it is running! It was that nasty little "eth0" in the options stament where i had to use the name of the module instead!

Thanx a lot again, for this solution after hours of stupid experimenting!

I also inserted it into /etc/modutils/aliases now

Stephen
09-22-2003, 08:49 PM
Now it is running! It was that nasty little "eth0" in the options stament where i had to use the name of the module instead!

Thanx a lot again, for this solution after hours of stupid experimenting!

I also inserted it into /etc/modutils/aliases now

I just noticed I forgot to tell you to run update-modules as root, you are supposed to do that to update the modules.conf after making changes in the files. Good to hear you got it going BTW.