From owner-freebsd-hardware Thu Oct 5 14:00:32 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA21698 for hardware-outgoing; Thu, 5 Oct 1995 14:00:32 -0700 Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA21691 for ; Thu, 5 Oct 1995 14:00:16 -0700 Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.67.25]) by pahtoh.cwu.edu (8.6.12/8.6.9) with ESMTP id NAA10924 for ; Thu, 5 Oct 1995 13:59:46 -0700 Received: (from skynyrd@localhost) by tahoma.cwu.edu (8.6.12/8.6.9) id NAA22118; Thu, 5 Oct 1995 13:59:45 -0700 Date: Thu, 5 Oct 1995 13:59:40 -0700 (PDT) From: Chris Timmons To: freebsd-hardware@freebsd.org Subject: ASUS P55TP4XE and DC21140 PCI ETHERNET Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk I'm having a problem with the DC21140 10/100 PCI ethernet adapter whereby the driver appears to read but misinterpret the ROM on the card: /kernel: de0 rev 17 int a irq 10 on pci0:9 /kernel: reg20: virtual=0xf4786000 physical=0xfbfff000 size=0x80 /kernel: de0: can't read ENET ROM (why=-4) (00000000000000000000000000000000000001010000f80007a1004100444535 /kernel: de0: DC21140 [10-100Mb/s] pass 1.1 Ethernet address unknown The string returned in the message does include the adapter's ethernet address, which makes me suspect that the problem may just have to do with adjusting an offset somewhere so that this can be interpreted correctly. Any ideas? It seems like I'm real close to having this working... -Chris SOFTWARE: 2.0.5-950622-SNAP, problem also appears with the 2.1.0-950928-SNAP boot floppy. HARDWARE: ASUS P55TP4XE, P100, 32mb RAM PCI BUS 1 SC200 NCR SCSI - IRQ 11 1 DC21140 - IRQ 10 ISA 1 Generic VGA - IRQ 1 NOTES: The DC21140 can run and pass the extensive diagnostic suite included on the DOS install diskette - this on the same hardware. Removing the SC200 from the PCI bus and booting the machine from floppy does not mitigate the problem. Enabling all shadow memory ranges in the BIOS doesn't help.