From nobody@FreeBSD.org  Sun Dec 16 14:24:38 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id E2D7937B417
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 16 Dec 2001 14:24:36 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id fBGMOaN42107;
	Sun, 16 Dec 2001 14:24:36 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200112162224.fBGMOaN42107@freefall.freebsd.org>
Date: Sun, 16 Dec 2001 14:24:36 -0800 (PST)
From: Olaf Zaplinski <oz@mediascape.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: still no support for Intel "eepro100" NICs
X-Send-Pr-Version: www-1.0

>Number:         32913
>Category:       kern
>Synopsis:       still no support for Intel "eepro100" NICs
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Dec 16 14:30:00 PST 2001
>Closed-Date:    Tue Dec 18 12:23:51 PST 2001
>Last-Modified:  Tue Dec 18 12:25:05 PST 2001
>Originator:     Olaf Zaplinski
>Release:        4.4
>Organization:
>Environment:
had to delete BSD - if it has no network, it's useless :-(
Problem is there with both standard and self compiled kernel
>Description:
- tried FreeBSD 4.4 and had to learn that both my several years old Intel Pro/100B and also my newer Pro/100+ do not work, fxp0 says "could not map [address|register]" (don't remember the exact phrase). Same as with 4.0 (this was the last time I wanted to try BSD). Both cards work fine under Win9x/2K + Linux 2.4.x
- Machine A (older card) has Intel LX chipset
- Machine B (newer card, BSD test install) has Via 694X/694Z chipset
- swapping cards between machines and reinstall on B did not help

Info for the older card (Linux):

00:10.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 02)
        Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
        Flags: bus master, medium devsel, latency 66, IRQ 11
        Memory at fecfe000 (32-bit, prefetchable) [size=4K]
        I/O ports at f800 [size=32]
        Memory at fed00000 (32-bit, non-prefetchable) [size=1M]
        Expansion ROM at <unassigned> [disabled] [size=1M]

>How-To-Repeat:
Just buy that Intel NIC and try to ping your default gw ;-)
>Fix:
install Linux? ;-) (SCNR)
I would like to test BSD/compare with Linux, but I only have Intel NICs both at home and at work
>Release-Note:
>Audit-Trail:

From: David Greenman <dg@root.com>
To: Olaf Zaplinski <oz@mediascape.de>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/32913: still no support for Intel "eepro100" NICs
Date: Sun, 16 Dec 2001 14:28:00 -0800

 >had to delete BSD - if it has no network, it's useless :-(
 >Problem is there with both standard and self compiled kernel
 >>Description:
 >- tried FreeBSD 4.4 and had to learn that both my several years old Intel Pro/100B and also my newer Pro/100+ do not work, fxp0 says "could not map [address|register]" (don't remember the exact phrase). Same as with 4.0 (this was the last time I wanted to try BSD). Both cards work fine under Win9x/2K + Linux 2.4.x
 >- Machine A (older card) has Intel LX chipset
 >- Machine B (newer card, BSD test install) has Via 694X/694Z chipset
 >- swapping cards between machines and reinstall on B did not help
 >
 >Info for the older card (Linux):
 >
 >00:10.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 02)
 >        Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
 >        Flags: bus master, medium devsel, latency 66, IRQ 11
 >        Memory at fecfe000 (32-bit, prefetchable) [size=4K]
 >        I/O ports at f800 [size=32]
 >        Memory at fed00000 (32-bit, non-prefetchable) [size=1M]
 >        Expansion ROM at <unassigned> [disabled] [size=1M]
 >
 >>How-To-Repeat:
 >Just buy that Intel NIC and try to ping your default gw ;-)
 
    Both the Pro/100B and Pro/100+ boards are fully supported. The problem
 that you described is a problem with your motherboard PCI BIOS not properly
 allocating a shared memory region for the device registers to be mapped.
 
 -DG
 
 David Greenman
 Co-founder, The FreeBSD Project - http://www.freebsd.org
 President, TeraSolutions, Inc. - http://www.terasolutions.com
 Pave the road of life with opportunities.
State-Changed-From-To: open->closed 
State-Changed-By: dg 
State-Changed-When: Tue Dec 18 12:23:51 PST 2001 
State-Changed-Why:  
Submitter solved the problem by setting the "PNP OS" BIOS 
option to "NO". 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=32913 
>Unformatted:
