Nie mam obecnie dostępu do serwera. serwer ma dwie karty sieciowe intela, eth0 wykrywa i mam skonfigurowane połączenie na tym interfejsie.
Polecenie:
daje mi informacje o eth0, że karta jest 
podniesiona i jakieś itd. oraz informacje o lo.
W wyniku polecenia:
wyszukałem dwa interfejsy Ethernet. jeden z nich działa i jest to eth0 drugi natomiast oznaczony jest tylko jako:
 Grml podał mi pełne nazwy modeli kart sieciowych, także wychodzi na to, że do tej nierozpoznanej karty nie ma sterowników.
Jutro wkleję dokładne wyniki poleceń.
Dodane:
Wyniki polecenia
Kod: Zaznacz cały
 lspci -k
00:00.0 Host bridge: Intel Corporation Clarksfield/Lynnfield DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Clarksfield/Lynnfield PCI Express Root Port 1 (rev 11)
        Kernel driver in use: pcieport-driver
        Kernel modules: shpchp
00:05.0 PCI bridge: Intel Corporation Clarksfield/Lynnfield PCI Express Root Port 3 (rev 11)
        Kernel driver in use: pcieport-driver
        Kernel modules: shpchp
00:08.0 System peripheral: Intel Corporation Clarksfield/Lynnfield System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Clarksfield/Lynnfield Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Clarksfield/Lynnfield System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Clarksfield/Lynnfield Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Device d150 (rev 11)
00:10.1 System peripheral: Intel Corporation Device d151 (rev 11)
00:19.0 Ethernet controller: Intel Corporation Device 10ef (rev 05)
00:1a.0 USB Controller: Intel Corporation Ibex Peak USB2 Enhanced Host Controller (rev 05)
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd
00:1c.0 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 1 (rev 05)
        Kernel driver in use: pcieport-driver
        Kernel modules: shpchp
00:1c.6 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 7 (rev 05)
        Kernel driver in use: pcieport-driver
        Kernel modules: shpchp
00:1c.7 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 8 (rev 05)
        Kernel driver in use: pcieport-driver
        Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation Ibex Peak USB2 Enhanced Host Controller (rev 05)
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Ibex Peak LPC Interface Controller (rev 05)
00:1f.2 IDE interface: Intel Corporation Ibex Peak 4 port SATA IDE Controller (rev 05)
        Kernel driver in use: ata_piix
        Kernel modules: ide-pci-generic, ata_piix, ata_generic
00:1f.3 SMBus: Intel Corporation Ibex Peak SMBus Controller (rev 05)
00:1f.5 IDE interface: Intel Corporation Ibex Peak 2 port SATA IDE Controller (rev 05)
        Kernel driver in use: ata_piix
        Kernel modules: ide-pci-generic, ata_piix, ata_generic
02:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0073 (rev 02)
        Kernel driver in use: megaraid_sas
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
        Kernel driver in use: e1000e
        Kernel modules: e1000e
07:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200e [Pilot] ServerEngines (SEP1) (rev 02)
ff:00.0 Host bridge: Intel Corporation Device 2c50 (rev 04)
ff:00.1 Host bridge: Intel Corporation Device 2c81 (rev 04)
ff:02.0 Host bridge: Intel Corporation Device 2c90 (rev 04)
ff:02.1 Host bridge: Intel Corporation Device 2c91 (rev 04)
ff:03.0 Host bridge: Intel Corporation Device 2c98 (rev 04)
ff:03.1 Host bridge: Intel Corporation Device 2c99 (rev 04)
ff:03.2 Host bridge: Intel Corporation Device 2c9a (rev 04)
ff:03.4 Host bridge: Intel Corporation Device 2c9c (rev 04)
ff:04.0 Host bridge: Intel Corporation Device 2ca0 (rev 04)
ff:04.1 Host bridge: Intel Corporation Device 2ca1 (rev 04)
ff:04.2 Host bridge: Intel Corporation Device 2ca2 (rev 04)
ff:04.3 Host bridge: Intel Corporation Device 2ca3 (rev 04)
ff:05.0 Host bridge: Intel Corporation Device 2ca8 (rev 04)
ff:05.1 Host bridge: Intel Corporation Device 2ca9 (rev 04)
ff:05.2 Host bridge: Intel Corporation Device 2caa (rev 04)
ff:05.3 Host bridge: Intel Corporation Device 2cab (rev 04)
 
Wyniki:
Kod: Zaznacz cały
ifconfig -a
eth0   Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::240:d0ff:fec0:741f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3324 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3436 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1763456 (1.6 MiB)  TX bytes:533637 (521.1 KiB)
          Memory:ce220000-ce240000
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:234 errors:0 dropped:0 overruns:0 frame:0
          TX packets:234 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:15385 (15.0 KiB)  TX bytes:15385 (15.0 KiB)
 
Na stronce Intela jest sterownik e1000e-1.2.20.tar.gz 
http://downloadcenter.intel.com/SearchR ... hernet+PHY
Instalacja poleceniem:
 wyświetla jakieś błędy, podejrzewam, że makefile jest coś nie tak ze ścieżką do 
jądra.
Czy ktoś oblatany w temacie mógłby utworzyć z tego archiwum pakiet instalacyjny deb?