[SLE] Intel Pro/1000 MT Quad Port is not working under SLES9

From: Rainer Blaes (Rainer.Blaes_at_space.eads.net)
Date: 01/03/05

  • Next message: Johan Nielsen: "Re: [SLE] Hardware compatibility list" 
    Date: Mon, 03 Jan 2005 15:51:40 +0100
To: suse-linux-e@suse.com

    Dear all,

    we are running on an x86 system SLES 9 where we added an Intel Pro/1000
    Ethernet MT Quad adapter.
    The system recognized this board and with YAST we configured for examples
    two interfaces ie. "ifconfig -a" is showing the correct properties.
    But we are not able from other sytems in the same subnet to communicate
    (ping)
     with their respective Ethernet ports.
    Firewall is not active i.e. "iptables -L" says:

         Chain INPUT (policy ACCEPT)
         target prot opt source destination

        Chain FORWARD (policy ACCEPT)
        target prot opt source destination

        Chain OUTPUT (policy ACCEPT)
        target prot opt source destination

    Also pls. see our "ifconfig -a" ouput for the configured eth2/eth3 ports:

       eth2 Link encap:Ethernet HWaddr 00:04:23:09:C9:55
      inet addr:149.243.228.79 Bcast:149.243.228.255 Mask:255.255.255.0
      inet6 addr: fe80::204:23ff:fe09:c955/64 Scope:Link
      UP BROADCAST MULTICAST MTU: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)
      Base address:0xc400 Memory:fc000000-fc020000

      eth3 Link encap:Ethernet HWaddr 00:04:23:09:C9:56
      inet addr:149.243.226.60 Bcast:149.243.226.255 Mask:255.255.255.0
      inet6 addr: fe80::204:23ff:fe09:c956/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:105 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:11516 (11.2 Kb) TX bytes:292 (292.0 b)
      Base address:0xc000 Memory:fb800000-fb820000
     
    Our idea is that this behavior has something to do with "acpi" but
    using the "acpi=oldboot" value (menu.lst) didn't the trick.
    Any tipps, comments are welcome!

    Many thanks in advance!

    Rainer 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Johan Nielsen: "Re: [SLE] Hardware compatibility list"

    Relevant Pages