Ethernet communication problem using Intel PRO/1000 GT Desktop Adapter - Suse

Hello everyone,

Last week I started last to use SUSE 11 installed on a PC used for an old project.
I have a problem with the network card (Intel PRO/1000 GT Desktop Adapter).
Connecting the ethernet cable to a Beckhoff module (EK1100), the light on the PC-Port lights up, while nothing happens on the module.
This happens even if connected to a switch instead of the Beckhoff module.
The Beckhoff module has been tested with an another PC and it works.

I have already done several tests, but without positive results:

  • changed the cable
  • changed network card slot in the PCI
  • reinstalled the network card driver (e1000)

Someone with more experience knows by chance what could be the problem?

Thanks to anyone who decides to help me! :):slight_smile:

If you require SLED/SLES support (as opposed to openSUSE), please post here instead:
https://forums.suse.com/forum.php

Sorry I mean openSUSE 11 (i586) - Version 11.0

Ok, well that’s a very old version - it went EOL July 26th, 2010! Any particular reason for not using a currently supported version?

What is reported when you connect the ethernet cable?

/usr/sbin/ethtool eth0

It is a system composed of three computers: openSUSE to receive data from Beckhoff, xPC target running MATLAB and a Host PC with Windows.

Update openSUSE means changes all the setup and I’m trying to avoid it.
I hope to find another way.


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

The ethtool output shows the ethernet link is up and connected at 100Mb/s FD. I know nothing about the hardware you’ve connected it to, but assuming layer 3 connectivity is required to reach the device, have you undertaken the appropriate IP address configuration?

What does the following report?

/sbin/ifconfig

Looking further into this, I now relaise that the EtherCAT protocol is in use here, and requires a specialised driver stack (including ethercat.ko module) for operation. It’s well beyond my experience/knowledge…

http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Etherlab
https://www.ethercat.org/en/products/263FCDB7639F4DDFB3587C18F46BA289.htm

I’m not in a position to help further with this, (and I doubt most others here would be able to assist meaningfully either).

ifconfig
eth1    Link encap:Ethernet HWaddr 00:08:98:BC:00:78 
          BROADCAST MULTICAST HTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          Rx bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth2    Link encap:Ethernet HWaddr 00:08:98:BC:00:77
          BROADCAST RLNNING MULTICAST MTU:1500 Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:3327 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:1136594 (1.0 Mb) 

eth3    Link encap:Ethernet HWaddr 00:04:75:FF:32:09 
          inet addr:192.168.1.96 Bcast:192.168.1.127 Mask:255.255.255.128 
          UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:4 errors:0 dropped:0 overruns: 0 carrier:0 
          collisions:0 txqueuelen: 1000 
          RX bytes:0 (0.0 b) TX bytes:240 (240.0 b) 
          Interrupt:10 Base address: 0x4c00 

lo       Link encap: Local Loopback inet addr:127.0.0.1 Mask: 255.0.0.0 
          UP LOOPBACK RUNNING HTU:16436 Metric:1 
          RX packets:72 errors:0 dropped:0 overruns:0 frase:0 
          TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:0 
          Rx bytes:4664 (4.5 Kb) TX bytes: 4664 (4.5 Kb)

In any case, thank you for the help!

On Thu 16 Aug 2018 07:06:03 AM CDT, jam hir0 wrote:

jam_hir0;2877414 Wrote:
> I started last to use SUSE 11

Sorry I mean openSUSE 11 (i586) - Version 11.0

Hi
So from your using openSUSE 11…

So, I’m interested in the system you tested on and it worked as to what
OS and kernel release and well as the kernel module.

Can you provide this information?

Way back then 11.x was around I did build some of the ethercat modules
for a forum user from memory and also upstreamed the patches.

Can you post the output from the openSUSE 11 system;


uname -a


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.6-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!