From owner-freebsd-mobile@FreeBSD.ORG  Mon Dec 20 04:23:04 2004
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6775816A4CF
	for <freebsd-mobile@freebsd.org>;
	Mon, 20 Dec 2004 04:23:04 +0000 (GMT)
Received: from msgfe02.utad.utoledo.edu (msgfe02.utad.utoledo.edu
	[131.183.1.34])	by mx1.FreeBSD.org (Postfix) with ESMTP id F056743D46
	for <freebsd-mobile@freebsd.org>;
	Mon, 20 Dec 2004 04:23:03 +0000 (GMT)	(envelope-from rafege@mail.com)
Received: from lmrmac.uhw.utoledo.edu ([131.183.85.137]) by
	msgfe02.utad.utoledo.edu with Microsoft SMTPSVC(6.0.3790.211);
	Sun, 19 Dec 2004 23:23:01 -0500
Date: Sun, 19 Dec 2004 23:23:03 -0500
From: rafege@mail.com (Gary E. RAFE, Ph.D.)
Organization: Rouillard & Rafe
To: freebsd-mobile@freebsd.org
Message-ID: <41C653A7.nailACV113TLB@mail.com>
User-Agent: nail 11.3 8/18/04
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2004 04:23:01.0168 (UTC)
	FILETIME=[977CA300:01C4E64B]
Subject: Trouble with "if_fxp.ko" kernel module ?
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: rafege@mail.com
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2004 04:23:04 -0000

Has anyone seen this behavior:

Toshiba Satellite Pro 6100, FreeBSD 5.3-RELEASE,
system installed in a port replicator,
a custom kernel *without* "device miibus" and "device fxp".
Loading kernel modules "miibus.ko" & "if_fxp.ko" results in
the kernel messages:

fxp0: <Intel 82801CAM (ICH3) Pro/100 VE Ethernet> port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2
fxp0: Disabling dynamic standby mode in EEPROM
fxp0: New EEPROM ID: 0xfffd
fxp0: EEPROM checksum @ 0xff: 0xffff -> 0xbbb9
fxp0: Ethernet address: ff:ff:ff:ff:ff:ff

Adding "device miibus" and "device fxp" to the custom kernel,
and a reboot, results in a working Ethernet port:

fxp0: <Intel 82801CAM (ICH3) Pro/100 VE Ethernet> port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2
miibus0: <MII bus> on fxp0
inphy0: <i82562ET 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:00:39:xx:xx:xx

Is this known behavior ?

I seem to recall being able to use the kernel module approach
to access the Ethernet port in 5.2.1-RELEASE.

Regards to the list...
--
Gary E. RAFE, Ph.D.	<mailto:rafege@mail.com>
Please do not send me HTML-encoded mail.
It will be discarded automatically.