Wykrywanie kart sieciowych

Krotki - 09-06-2009 12:33
Witam.

Ostatnimi czasy mam mały problem z wykrywaniem kart sieciowych. Otóż posiadam 4 karty w komputerze: 00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0d.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Po restarcie komputera czasami widzi mi wszystkie karty, a czasami nie wykrywa jednej z RTL8139. Karty są w 100% sprawne.

Syslog przy błędnym wykrywaniu kart: kernel: [ 3.675839] 8139too Fast Ethernet driver 0.9.28
kernel: [ 3.676503] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
kernel: [ 3.677551] PCI: setting IRQ 11 as level-triggered
kernel: [ 3.677560] ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
kernel: [ 3.678763] eth0: RealTek RTL8139 at 0xe400, 00:30:4f:22:94:db, IRQ 11
kernel: [ 3.678823] eth0: Identified 8139 chip type 'RTL-8100B/8139D'
kernel: [ 3.679267] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
kernel: [ 3.679325] PCI: setting IRQ 10 as level-triggered
kernel: [ 3.679333] ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
kernel: [ 3.680544] eth1: RealTek RTL8139 at 0xe800, 00:30:4f:1c:d8:91, IRQ 10
kernel: [ 3.680604] eth1: Identified 8139 chip type 'RTL-8100B/8139D'
kernel: [ 3.703606] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
kernel: [ 3.703666] PCI: setting IRQ 9 as level-triggered
kernel: [ 3.703673] ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
kernel: [ 4.202141] e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
kernel: [ 4.202209] e100: Copyright(c) 1999-2006 Intel Corporation
kernel: [ 4.202370] ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
kernel: [ 4.225801] e100: eth2: e100_probe: addr 0xfecff000, irq 9, MAC addr 00:30:05:06:b0:96
kernel: [ 6.615165] r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
kernel: [ 6.616153] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
kernel: [ 6.616214] PCI: setting IRQ 5 as level-triggered
kernel: [ 6.616222] ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
kernel: [ 6.617332] eth0: RTL8110s at 0xd0846400, 00:0e:2e:6f:ff:77, XID 04000000 IRQ 5
kernel: [ 36.755621] udevd version 125 started
kernel: [ 37.324868] udev: renamed network interface eth2 to eth3
kernel: [ 37.373030] udev: renamed network interface eth1_rename to eth2
kernel: [ 39.633938] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
kernel: [ 71.550114] r8169: eth0: link up
kernel: [ 71.680286] ip_tables: (C) 2000-2006 Netfilter Core Team
kernel: [ 75.834495] eth2: link up, 100Mbps, full-duplex, lpa 0xC1E1
kernel: [ 80.523398] HTB: quantum of class 10002 is big. Consider r2q change.
kernel: [ 81.812039] eth0: no IPv6 routers present
kernel: [ 83.607392] tun: Universal TUN/TAP device driver, 1.6
kernel: [ 83.607473] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
kernel: [ 83.769635] Bridge firewalling registered
kernel: [ 83.803781] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
kernel: [ 84.130266] device tap0 entered promiscuous mode
kernel: [ 84.138316] br0: port 1(tap0) entering learning state
kernel: [ 86.596062] eth2: no IPv6 routers present
kernel: [ 94.316061] br0: no IPv6 routers present
kernel: [ 94.912049] tap0: no IPv6 routers present
kernel: [ 99.136053] br0: topology change detected, propagating
kernel: [ 99.136127] br0: port 1(tap0) entering forwarding state Czyli wykrywane są 2 sztuki RLT8139 jako eth0 i eth1. Następnie e100 jako eth2 i znowu jako eth0 wskakuje sterownik RTL8110s. O co tu chodzi? Oczywiście potem żadna karta RTL8139 nie odpowiada.

Przy poprawnym starcie syslog wygląda następująco: kernel: [ 3.747980] 8139too Fast Ethernet driver 0.9.28
kernel: [ 3.749669] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
kernel: [ 3.749729] PCI: setting IRQ 11 as level-triggered
kernel: [ 3.749737] ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
kernel: [ 3.750912] eth0: RealTek RTL8139 at 0xe400, 00:30:4f:22:94:db, IRQ 11
kernel: [ 3.750973] eth0: Identified 8139 chip type 'RTL-8100B/8139D'
kernel: [ 3.751404] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
kernel: [ 3.751462] PCI: setting IRQ 10 as level-triggered
kernel: [ 3.751470] ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
kernel: [ 3.753763] eth1: RealTek RTL8139 at 0xe800, 00:30:4f:1c:d8:91, IRQ 10
kernel: [ 3.753822] eth1: Identified 8139 chip type 'RTL-8100B/8139D'
kernel: [ 3.784012] e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
kernel: [ 3.784012] e100: Copyright(c) 1999-2006 Intel Corporation
kernel: [ 3.784676] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
kernel: [ 3.784738] PCI: setting IRQ 9 as level-triggered
kernel: [ 3.784746] ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
kernel: [ 3.808177] e100: eth2: e100_probe: addr 0xfecff000, irq 9, MAC addr 00:30:05:06:b0:96
kernel: [ 3.813278] USB Universal Host Controller Interface driver v3.0
kernel: [ 3.813449] ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
kernel: [ 4.285638] Uniform Multi-Platform E-IDE driver
kernel: [ 4.285711] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
kernel: [ 4.292380] r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
kernel: [ 4.292968] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
kernel: [ 4.293028] PCI: setting IRQ 5 as level-triggered
kernel: [ 4.293037] ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
kernel: [ 4.294143] eth3: RTL8110s at 0xd084c400, 00:0e:2e:6f:ff:77, XID 04000000 IRQ 5
kernel: [ 36.888658] udevd version 125 started
kernel: [ 37.566140] udev: renamed network interface eth0_rename to eth0
kernel: [ 37.589346] udev: renamed network interface eth2 to eth3
kernel: [ 37.616000] udev: renamed network interface eth3_rename to eth1
kernel: [ 37.637492] udev: renamed network interface eth1_rename to eth2
kernel: [ 48.816559] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
kernel: [ 48.947163] ip_tables: (C) 2000-2006 Netfilter Core Team
kernel: [ 50.521379] r8169: eth1: link up
kernel: [ 51.498057] eth2: link up, 100Mbps, full-duplex, lpa 0xC1E1
kernel: [ 54.913794] HTB: quantum of class 10002 is big. Consider r2q change.
kernel: [ 54.919086] HTB: quantum of class 10020 is big. Consider r2q change.
kernel: [ 55.015239] HTB: quantum of class 10002 is big. Consider r2q change.
kernel: [ 58.373300] tun: Universal TUN/TAP device driver, 1.6
kernel: [ 58.373378] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
kernel: [ 58.594053] Bridge firewalling registered
kernel: [ 58.642496] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
kernel: [ 58.700911] device eth1.10 entered promiscuous mode
kernel: [ 58.700992] device eth1 entered promiscuous mode
kernel: [ 58.711818] device tap0 entered promiscuous mode
kernel: [ 58.721056] br0: port 2(tap0) entering learning state
kernel: [ 58.721139] br0: port 1(eth1.10) entering learning state
kernel: [ 59.616037] eth0: no IPv6 routers present
kernel: [ 61.008065] eth1.10: no IPv6 routers present
kernel: [ 61.028055] eth1: no IPv6 routers present
kernel: [ 61.852036] eth1.20: no IPv6 routers present
kernel: [ 62.244037] eth2: no IPv6 routers present
kernel: [ 69.068038] br0: no IPv6 routers present
kernel: [ 69.164031] tap0: no IPv6 routers present
kernel: [ 73.720031] br0: topology change detected, propagating
kernel: [ 73.720101] br0: port 2(tap0) entering forwarding state
kernel: [ 73.720156] br0: topology change detected, propagating
kernel: [ 73.720212] br0: port 1(eth1.10) entering forwarding state Czy ktoś wie co należy zrobić żeby sprzęt zawsze uruchamiał się poprawnie?

fnmirk - 10-06-2009 18:08
Sprawdź zawartość pliku: /etc/udev/rules.d/70-persistent-net.rules Cyfra z przodu-persistent-net.rules, może być inna. Dla pewności wyczyść jego zawartość i zrestartuj komputer. Jak zamieniałeś fizycznie karty miejscami w gniazdach to może się zmienić kolejność interfejsów sieciowych. Wykonaj przed zmianami kopię pliku.

Krotki - 11-06-2009 11:14
Kasowałem jego zawartość i to nic nie pomagało. W wspomnianym pliku zmieniałem kolejność interfejsów, ale czy to może mieć znaczenie ?

Na razie zamieniłem kartę z chipem rlt8169 na rlt8139 i teraz wstaje jak trzeba. Wnioskuje ze coś ze sterownikami pewnie, bo karta pod windowsem śmiga.

zanotowane.pl

doc.pisz.pl

pdf.pisz.pl

minister.pev.pl