Troy Dawson wrote:
> Stefano Stalio wrote:
>> I was trying to instal SL308 on a TYAN server mounting a TYAN S5372
>> motherboard. The two gigabit NICs are intel 92563EB.
>> I can install the OS via http. The system starts and loads the e1000 modu
>> le.
>>
>> dmesg tells me that eth0 is up
>> e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
>>
>> or, accprding to the switch i connect it to
>>
>> e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
>>
>> but the network does not work. Everything works when i connect the cable
>> to eth2 (the fast ethernet interface).
>>
>> I tried downloading the driver from the intel site, compiling and install
>> ing
>> it but insmod says:
>>
>> /lib/modules/2.4.21-47.0.1.ELsmp/kernel/drivers/net/e1000/e1000.o:
>> unresolved symbol pci_set_consistent_dma_mask
>>
>> Does anybody have an answer?
> 
> dmesg doesn't really tell you if the network is up or not.  And with 
> some drivers, it just says "Hey I'm up and ready" when really it isn't.
> 
> The two tools I usually use are ifconfig and ethtool
> 
> You said you moved the cable from one port to the other, but you didn't 
> say anything about reconfiguring the network so that the IP address 
> moved from one port to the other.
> 
> If this is true, that you only moved the cable from one to the other and 
> then it worked, then you really only have the one network interface 
> configured, the one you think is eth2.
> 
> Anyway, the first steps are to see which network interface is actually 
> up.  Do that by doing
> 
>   /sbin/ifconfig
> 
> That will list all the network interfaces that are up.
> Then look and see what they are and their speed.
> 
>   /sbin/ethtool eth0
> 
> Hopefully that will help track things down.
> 
> Troy

I skipped everything regarding the ip addresses because I am sure
I got the right interfaces. I did many tests so I am sure of what I am saying.
Now I am trying to use eth1. here is what i get:

/sbin/ifconfig

eth1      Link encap:Ethernet  HWaddr 00:E0:81:71:95:DB
          inet addr:172.16.4.218  Bcast:172.16.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1505 errors:0 dropped:3986 overruns:0 frame:0
          TX packets:1033 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:153840 (150.2 Kb)  TX bytes:66112 (64.5 Kb)
          Base address:0x2020 Memory:d8020000-d8040000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:71182 errors:0 dropped:0 overruns:0 frame:0
          TX packets:71182 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7973327 (7.6 Mb)  TX bytes:7973327 (7.6 Mb)

/sbin/ethtool eth1

Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: umbg
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes



dmesg:

e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
NETDEV WATCHDOG: eth1: transmit timed out

I think the second message on dmesg is to be considered.



-- 
Stefano Stalio - Servizio Calcolo 		tel   0862-437423
Istituto Nazionale di Fisica Nucleare		fax   0862-437570
Laboratori Nazionali del Gran Sasso
SS 17/bis - km 18.910 				[log in to unmask]
67010 Assergi - L`Aquila