PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Problem mit Intel e1000


piepre
2006-08-30, 12:54:40
moin, ich habe ein Problem mit Intel Gigabit Netzwerkkarten. Der Treiber e1000 ist fest in den Kernel (2.6.17.11) kompiliert und die Netzwerkkarte wird auch erkannt und ich kann sie konfigurieren. Es ist jedoch nicht möglich die Karte dazu bewegen irgendwelche Pakete ans Netzwerk zu senden, oder zu empfangen. System ist Busybox + paar Programme, andere Karten, bzw. trieber (z.B. tg3) laufen ohne Probleme.

Hat jemand eine Idee?

ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:23:CC:21:78
inet addr:192.168.4.94 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:359 errors:0 dropped:56 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:159945 (156.1 KiB) TX bytes:384 (384.0 B)
Base address:0xac00 Memory:fc7e0000-fc800000

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:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

ethtool eth0
Settings for eth0:
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: Half
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes

dmesg
000 - 000000001fff0000 (ACPI NVS)
<4> BIOS-e820: 000000001fff0000 - 0000000020000000 (reserved)
<4> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
<4> BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
<5>511MB LOWMEM available.
<6>found SMP MP-table at 000ff780
<7>On node 0 totalpages: 131040
<7> DMA zone: 4096 pages, LIFO batch:0
<7> Normal zone: 126944 pages, LIFO batch:31
<6>DMI 2.3 present.
<6>Intel MultiProcessor Specification v1.4
<6> Virtual Wire compatibility mode.
<6>OEM ID: Intel Product ID: P5MT-S APIC at: 0xFEE00000
<4>Processor #0 15:4 APIC version 20
<6>I/O APIC #1 Version 32 at 0xFEC00000.
<6>I/O APIC #2 Version 32 at 0xFEC10000.
<4>Enabling APIC mode: Flat. Using 2 I/O APICs
<6>Processors: 1
<4>Allocating PCI resources starting at 30000000 (gap: 20000000:dee00000)
<4>Built 1 zonelists
<5>Kernel command line: initrd=rescue.img init=/sbin/init ramdisk_size=32768 rw root=/dev/ram0 BOOT_IMAGE=rescue
<7>mapped APIC to ffffd000 (fee00000)
<7>mapped IOAPIC to ffffc000 (fec00000)
<7>mapped IOAPIC to ffffb000 (fec10000)
<6>Enabling fast FPU save and restore... done.
<6>Enabling unmasked SIMD FPU exception support... done.
<6>Initializing CPU#0
<4>PID hash table entries: 2048 (order: 11, 8192 bytes)
<4>Detected 3200.813 MHz processor.
<6>Using tsc for high-res timesource
<4>Console: colour VGA+ 80x25
<4>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<4>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Memory: 509452k/524160k available (3705k kernel code, 14156k reserved, 2015k data, 236k init, 0k highmem)
<4>Checking if this processor honours the WP bit even in supervisor mode... Ok.
<4>Calibrating delay using timer specific routine.. 6410.05 BogoMIPS (lpj=12820100)
<4>Mount-cache hash table entries: 512
<7>CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000000
<7>CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000649d 00000000 00000000
<4>monitor/mwait feature present.
<4>using mwait in idle threads.
<6>CPU: Trace cache: 12K uops, L1 D cache: 16K
<6>CPU: L2 cache: 2048K
<7>CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000649d 00000000 00000000
<4>CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03
<6>Checking 'hlt' instruction... OK.
<6>Checking for popad bug... OK.
<6>SMP alternatives: switching to UP code
<6>Freeing SMP alternatives: 0k freed
<4>ExtINT not setup in hardware but reported by MP table
<4>ENABLING IO-APIC IRQs
<6>..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
<6>checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
<6>Freeing initrd memory: 3390k freed
<6>NET: Registered protocol family 16
<6>PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=6
<4>Setting up standard PCI resources
<6>Generic PHY: Registered new driver
<5>SCSI subsystem initialized
<6>usbcore: registered new driver usbfs
<6>usbcore: registered new driver hub
<4>PCI: Probing PCI hardware
<7>PCI: Probing PCI hardware (bus 00)
<6>PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
<4>PCI: PXH quirk detected, disabling MSI for SHPC device
<7>Boot video device is 0000:06:02.0
<6>PCI: Transparent bridge - 0000:00:1e.0
<6>PCI: Using IRQ router PIIX/ICH [8086/27b8] at 0000:00:1f.0
<6>PCI->APIC IRQ transform: 0000:00:1c.0[A] -> IRQ 129
<6>PCI->APIC IRQ transform: 0000:00:1c.4[A] -> IRQ 129
<6>PCI->APIC IRQ transform: 0000:00:1c.5[B] -> IRQ 137
<6>PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 161
<6>PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 153
<6>PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 161
<6>PCI->APIC IRQ transform: 0000:00:1f.1[A] -> IRQ 145
<6>PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 153
<6>PCI->APIC IRQ transform: 0000:00:1f.3[B] -> IRQ 153
<6>PCI->APIC IRQ transform: 0000:03:04.0[A] -> IRQ 137
<6>PCI->APIC IRQ transform: 0000:03:04.1[B] -> IRQ 145
<6>PCI->APIC IRQ transform: 0000:03:06.0[A] -> IRQ 153
<6>PCI->APIC IRQ transform: 0000:03:06.1[B] -> IRQ 129
<6>PCI->APIC IRQ transform: 0000:04:00.0[A] -> IRQ 129
<6>PCI->APIC IRQ transform: 0000:05:00.0[A] -> IRQ 137
<6>PCI->APIC IRQ transform: 0000:06:02.0[A] -> IRQ 153
<6>PCI: Bridge: 0000:02:01.0
<6> IO window: a000-afff
<6> MEM window: fc700000-fc7fffff
<6> PREFETCH window: ff700000-ff7fffff
<6>PCI: Bridge: 0000:01:00.0
<6> IO window: a000-afff
<6> MEM window: fc700000-fc7fffff
<6> PREFETCH window: ff700000-ff7fffff
<6>PCI: Bridge: 0000:00:1c.0
<6> IO window: a000-afff
<6> MEM window: fc700000-fc7fffff
<6> PREFETCH window: ff700000-ff7fffff
<6>PCI: Bridge: 0000:00:1c.4
<6> IO window: disabled.
<6> MEM window: fc800000-fc8fffff
<6> PREFETCH window: ff800000-ff8fffff
<6>PCI: Bridge: 0000:00:1c.5
<6> IO window: disabled.
<6> MEM window: fc900000-fc9fffff
<6> PREFETCH window: ff900000-ff9fffff
<6>PCI: Bridge: 0000:00:1e.0
<6> IO window: b000-dfff
<6> MEM window: fca00000-feafffff
<6> PREFETCH window: 30000000-300fffff
<7>PCI: Setting latency timer of device 0000:00:1c.0 to 64
<7>PCI: Setting latency timer of device 0000:01:00.0 to 64
<7>PCI: Setting latency timer of device 0000:00:1c.4 to 64
<7>PCI: Setting latency timer of device 0000:00:1c.5 to 64
<7>PCI: Setting latency timer of device 0000:00:1e.0 to 64
<6>NET: Registered protocol family 2
<4>IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
<4>TCP established hash table entries: 16384 (order: 4, 65536 bytes)
<4>TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
<6>TCP: Hash tables configured (established 16384 bind 8192)
<6>TCP reno registered
<6>Initializing Cryptographic API
<6>io scheduler noop registered
<6>io scheduler anticipatory registered (default)
<6>io scheduler deadline registered
<6>io scheduler cfq registered
<7>PCI: Setting latency timer of device 0000:00:1c.0 to 64
<4>assign_interrupt_mode Found MSI capability
<7>Allocate Port Service[0000:00:1c.0:pcie00]
<7>Allocate Port Service[0000:00:1c.0:pcie02]
<7>PCI: Setting latency timer of device 0000:00:1c.4 to 64
<4>assign_interrupt_mode Found MSI capability
<7>Allocate Port Service[0000:00:1c.4:pcie00]
<7>Allocate Port Service[0000:00:1c.4:pcie02]
<7>PCI: Setting latency timer of device 0000:00:1c.5 to 64
<4>assign_interrupt_mode Found MSI capability
<7>Allocate Port Service[0000:00:1c.5:pcie00]
<7>Allocate Port Service[0000:00:1c.5:pcie02]
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
<6>serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
<6>serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
<6>Floppy drive(s): fd0 is 1.44M
<4>floppy0: no floppy controllers found
<4>RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
<6>loop: loaded (max 8 devices)
<4>Compaq SMART2 Driver (v 2.6.0)
<6>HP CISS Driver (v 2.6.10)
<6>v2.3 : Micro Memory(tm) PCI memory board block driver
<4>MM: desc_per_page = 128
<6>Intel(R) PRO/1000 Network Driver - version 7.0.33-k2
<6>Copyright (c) 1999-2005 Intel Corporation.
<6>e1000: 0000:03:04.0: e1000_probe: (PCI-X:120MHz:64-bit) 00:04:23:cc:21:78
<6>e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
<6>e1000: 0000:03:04.1: e1000_probe: (PCI-X:120MHz:64-bit) 00:04:23:cc:21:79
<6>e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
<6>e1000: 0000:03:06.0: e1000_probe: (PCI-X:120MHz:64-bit) 00:04:23:cc:21:7a
<6>e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
<6>e1000: 0000:03:06.1: e1000_probe: (PCI-X:120MHz:64-bit) 00:04:23:cc:21:7b
<6>e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
<6>pcnet32.c:v1.32 18.Mar.2006 tsbogend@alpha.franken.de
<6>e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
<6>e100: Copyright(c) 1999-2005 Intel Corporation
<6>ThunderLAN driver v1.15
<6>TLAN: 0 devices installed, PCI: 0 EISA: 0
<6>ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
<6>tg3.c:v3.59 (June 8, 2006)
<7>PCI: Setting latency timer of device 0000:04:00.0 to 64
<6>eth4: Tigon3 [partno(BCM95721) rev 4201 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:17:31:ad:37:55
<6>eth4: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
<6>eth4: dma_rwctrl[76180000] dma_mask[64-bit]
<7>PCI: Setting latency timer of device 0000:05:00.0 to 64
<6>eth5: Tigon3 [partno(BCM95721) rev 4201 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:17:31:ad:37:56
<6>eth5: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
<6>eth5: dma_rwctrl[76180000] dma_mask[64-bit]
<6>Marvell 88E1101: Registered new driver
<6>Davicom DM9161E: Registered new driver
<6>Davicom DM9131: Registered new driver
<6>Cicada Cis8204: Registered new driver
<6>LXT970: Registered new driver
<6>LXT971: Registered new driver
<6>QS6612: Registered new driver
<6>forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.54.
<6>tun: Universal TUN/TAP device driver, 1.6
<6>tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<6>dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
<6>winbond-840.c:v1.01-d (2.4 port) Nov-17-2001 Donald Becker <becker@scyld.com>
<6> http://www.scyld.com/network/drivers.html
<6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
<6>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
<6>ICH7: IDE controller at PCI slot 0000:00:1f.1
<6>ICH7: chipset revision 1
<6>ICH7: not 100% native mode: will probe irqs later
<6> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
<6> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
<7>Probing IDE interface ide0...
<4>hda: SONY CD-RW/DVD-ROM CRX850E, ATAPI CD/DVD-ROM drive
<4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<7>Probing IDE interface ide1...
<7>Probing IDE interface ide1...
<6>hda: ATAPI 24X DVD-ROM CD-R/RW drive, 1536kB Cache, UDMA(33)
<6>Uniform CD-ROM driver Revision: 3.20
<4>Loading Adaptec I2O RAID: Version 2.4 Build 5go
<6>Detecting Adaptec I2O RAID controllers...
<6>Adaptec aacraid driver (1.1-5[2409]-mh1)
<4>scsi: <fdomain> Detection failed (no card)
<6>megasas: 00.00.02.04 Fri Feb 03 14:31:44 PST 2006
<4>GDT-HA: Storage RAID Controller Driver. Version: 3.04
<4>GDT-HA: Found 0 PCI Storage RAID Controllers
<4>3ware Storage Controller device driver for Linux v1.26.02.001.
<4>3ware 9000 Storage Controller device driver for Linux v2.26.02.007.
<6>nsp32: loading...
<6>ipr: IBM Power RAID SCSI Device Driver version: 2.1.3 (March 29, 2006)
<7>libata version 1.20 loaded.
<7>ahci 0000:00:1f.2: version 1.2
<7>PCI: Setting latency timer of device 0000:00:1f.2 to 64
<6>ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
<6>ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part
<6>ata1: SATA max UDMA/133 cmd 0xE080E900 ctl 0x0 bmdma 0x0 irq 233
<6>ata2: SATA max UDMA/133 cmd 0xE080E980 ctl 0x0 bmdma 0x0 irq 233
<6>ata3: SATA max UDMA/133 cmd 0xE080EA00 ctl 0x0 bmdma 0x0 irq 233
<6>ata4: SATA max UDMA/133 cmd 0xE080EA80 ctl 0x0 bmdma 0x0 irq 233
<6>ata1: SATA link up 1.5 Gbps (SStatus 113)
<7>ata1: dev 0 cfg 49:2f00 82:346b 83:7f09 84:6063 85:3469 86:be09 87:6063 88:203f
<6>ata1: dev 0 ATA-7, max UDMA/100, 156301488 sectors: LBA48
<6>ata1: dev 0 configured for UDMA/100
<6>scsi0 : ahci
<6>ata2: SATA link down (SStatus 0)
<6>scsi1 : ahci
<6>ata3: SATA link down (SStatus 0)
<6>scsi2 : ahci
<6>ata4: SATA link down (SStatus 0)
<6>scsi3 : ahci
<5> Vendor: ATA Model: FUJITSU MHV2080B Rev: 0000
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 3a 00 00
<5>SCSI device sda: drive cache: write back
<5>SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 3a 00 00
<5>SCSI device sda: drive cache: write back
<6> sda: sda1 sda2 sda3 sda4
<5>sd 0:0:0:0: Attached scsi disk sda
<5>sd 0:0:0:0: Attached scsi generic sg0 type 0
<6>scsi4 : scsi_debug, version 1.75 [20050113], dev_size_mb=8, opts=0x0
<5> Vendor: Linux Model: scsi_debug Rev: 0004
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sdb: 16384 512-byte hdwr sectors (8 MB)
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 63 00 00 00
<5>SCSI device sdb: drive cache: write back
<5>SCSI device sdb: 16384 512-byte hdwr sectors (8 MB)
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 63 00 00 00
<5>SCSI device sdb: drive cache: write back
<6> sdb: unknown partition table
<5>sd 4:0:0:0: Attached scsi disk sdb
<5>sd 4:0:0:0: Attached scsi generic sg1 type 0
<7>PCI: Setting latency timer of device 0000:00:1d.7 to 64
<6>ehci_hcd 0000:00:1d.7: EHCI Host Controller
<6>ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
<6>ehci_hcd 0000:00:1d.7: debug port 1
<7>PCI: cache line size of 128 is not supported by device 0000:00:1d.7
<6>ehci_hcd 0000:00:1d.7: irq 161, io mem 0xfebffc00
<6>ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 4 ports detected
<7>ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
<6>USB Universal Host Controller Interface driver v3.0
<7>PCI: Setting latency timer of device 0000:00:1d.0 to 64
<6>uhci_hcd 0000:00:1d.0: UHCI Host Controller
<6>uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
<6>uhci_hcd 0000:00:1d.0: irq 161, io base 0x0000ec00
<6>usb usb2: configuration #1 chosen from 1 choice
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 2 ports detected
<7>PCI: Setting latency timer of device 0000:00:1d.1 to 64
<6>uhci_hcd 0000:00:1d.1: UHCI Host Controller
<6>uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
<6>uhci_hcd 0000:00:1d.1: irq 153, io base 0x0000e880
<6>usb usb3: configuration #1 chosen from 1 choice
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>Initializing USB Mass Storage driver...
<6>usb 1-4: new high speed USB device using ehci_hcd and address 2
<6>usb 1-4: configuration #1 chosen from 1 choice
<6>scsi5 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<6>usbcore: registered new driver usb-storage
<6>USB Mass Storage support registered.
<6>usbcore: registered new driver hiddev
<6>usbcore: registered new driver usbhid
<6>drivers/usb/input/hid-core.c: v2.6:USB HID core driver
<6>serio: i8042 AUX port at 0x60,0x64 irq 12
<6>serio: i8042 KBD port at 0x60,0x64 irq 1
<6>md: raid1 personality registered for level 1
<6>md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
<6>md: bitmap version 4.39
<6>TCP bic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>NET: Registered protocol family 15
<4>Using IPI Shortcut mode
<6>md: Autodetecting RAID arrays.
<6>md: autorun ...
<6>md: ... autorun DONE.
<5>RAMDISK: Compressed image found at block 0
<4>VFS: Mounted root (ext2 filesystem).
<6>Freeing unused kernel memory: 236k freed
<6>input: AT Translated Set 2 keyboard as /class/input/input0
<5> Vendor: USB 2.0 Model: Mobile Disk Rev: 1.00
<5> Type: Direct-Access ANSI SCSI revision: 02
<5>SCSI device sdc: 507904 512-byte hdwr sectors (260 MB)
<5>sdc: Write Protect is on
<7>sdc: Mode Sense: 03 00 80 00
<3>sdc: assuming drive cache: write through
<5>SCSI device sdc: 507904 512-byte hdwr sectors (260 MB)
<5>sdc: Write Protect is on
<7>sdc: Mode Sense: 03 00 80 00
<3>sdc: assuming drive cache: write through
<6> sdc:<3>ldm_parse_privhead(): Cannot find PRIVHEAD structure. LDM database is corrupt. Aborting.
<3>ldm_validate_privheads(): Cannot find PRIVHEAD 1.
<4> unable to read partition table
<5>sd 5:0:0:0: Attached scsi removable disk sdc
<5>sd 5:0:0:0: Attached scsi generic sg2 type 0
<7>usb-storage: device scan complete
<5>SCSI device sdc: 507904 512-byte hdwr sectors (260 MB)
<5>sdc: Write Protect is off
<7>sdc: Mode Sense: 03 00 00 00
<3>sdc: assuming drive cache: write through
<5>SCSI device sdc: 507904 512-byte hdwr sectors (260 MB)
<5>sdc: Write Protect is off
<7>sdc: Mode Sense: 03 00 00 00
<3>sdc: assuming drive cache: write through
<6> sdc:<3>ldm_parse_privhead(): Cannot find PRIVHEAD structure. LDM database is corrupt. Aborting.
<3>ldm_validate_privheads(): Cannot find PRIVHEAD 1.
<4> unable to read partition table

Bufi
2006-08-30, 19:34:02
Sag mal, ist das normal daß da ganze 6 NICs im Rechner stecken? Wenn ja: bist du dir auch sicher daß du das Kabel in der richtigen Karte eingesteckt hast?
(kleine Frage am Rande: Für was braucht man derart viele NICs?)

Ist das der komplette Output von ifconfig? (ich frage weil halt dmesg meint es wären 4 e1000 und 2 Tigon3 Karten drinne, eth0 bis eth5)

Noch seltsamer ist aber daß eth0 nur 100MB half-duplex hat. (wobei, wenn die Karte Link hat ist auch ein Kabel eingesteckt, hm). Wirklich sicher daß das richtige Kabel drinnsteckt? Also nicht daß z.B. das Kabel zum DSL-Router in der NIC steckt und du versuchst das interne Netz zu erreichen.

Also so auf Anhieb fällt mir jetzt aber auch nix dazu ein. Die e1000 funktionieren garantiert, habe hier noch eine PCI Karte rumfliegen (dank onboard ist die im Moment arbeitslos)

P.S. ich seh ja gerade daß der Rechner vollgestopft ist mit Hardware. Passt da überhaupt noch was rein? :)

piepre
2006-08-31, 09:15:05
Das ist eine Firewall (mit Intel Entry Server Board), da benötigt man so viele NICs :)
Das Kabel ist richtig eingesteckt.
100 MBit Half Duplex kommt bei autoneg raus, da er mit einem etwas älteren HUB verbunden ist. Habe mit ethtool auch schon Vol Duplex, 10BaseT, usw. getestet.
Die Karte funktioniert auch, wenn ich ein anderes System starte (da liegt der Treiber als Modul vor).
Es ist nur eth0 konfiguriert, deswegen so wenig Ausgaben bei ifconfig.
Vielleicht gibt es ein Problem im Zusammenspiel mit Busybox?

piepre
2006-08-31, 15:07:51
This driver is only supported as a loadable module at this time. Intel is
not supplying patches against the kernel source to allow for static linking
of the driver.
hmmm

Bufi@work
2006-08-31, 17:16:07
hmmm

Jetzt wo ich das so lese: Stimmt, ich hatte den Treiber auch nur als Modul geladen. Aber wo soll der Unterschied zu einkompiliert liegen?
Schonmal als Modul versucht mit der Busybox? Scheint ja wohl wirklich daran zu liegen. Echt seltsam, aber man lernt nie aus.

Und klar, für ne FW braucht man schon evtl. ne ganze Menge NICs (na mindestens mal 2), das stimmt. Dachte ich jetzt so nicht dran wegen den ganzen Platten die da noch drinne sind. Hätte ja auch nen Hochleistungs-Fileserver sein können.

Harleckin
2006-08-31, 18:46:37
Nutzt du iptables?

# iptables -L -v


Stimmt deine Routingtabelle?

$ netstat -rn

piepre
2006-09-01, 08:57:11
Ne, iptables werden nur genutzt, wenn ich das richtige System starte. Busybox ist das Rescue-System.
Routingtabelle ist in ordnung. Da die Netzwerkkarte an einem HUB angeschlossen ist, sollte ich über tcpdump auch Pakete sehen, selbst wenn keine IP konfiguriert ist, leider ist dem nicht so (bei den beiden tg3 Karten schon).
Ich habe mein System gestern nochmal neu kompiliert (mit module-init-tools) und werde nachher testen ob es mit den originalen Intel-Treibern als Modul funktioniert.

piepre
2006-09-01, 10:16:36
hat nichts gebracht :(

es sieht so aus als ob etwas mit der arp-Paketen nicht klappt. Ich sehe im tcpdump, wenn ich einen ping absende, nur arp-Anfragen "arp who-has 192.168.4.96 tell 192.168.4.94". Das tolle dabei ist, dass die 192.168.4.96 die MAC von der 94 bei der ersten Pinganfrage mitbekommt.


edit:
habe es gerade mit einem Crossoverkabel probiert: gleiches Problem...