Date: Mon, 20 Dec 2004 20:42:24 +0100 From: Ranjit <r4nj1t@xs4all.nl> To: freebsd-mobile@freebsd.org Subject: Trouble with "if_fxp.ko" kernel module ? Message-ID: <1103571744.846.6.camel@ceylonica.cubnet.cub> In-Reply-To: <20041220120103.3F4F616A4CF@hub.freebsd.org> References: <20041220120103.3F4F616A4CF@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-9mPUVAesLiYml8aHVmho Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 1. (Gary E. RAFE, Ph.D.) > Has anyone seen this behavior: >=20 Hi Gary,=20 I ran into this myself.=20 =46rom rom /usr/src/sys/i386/conf/GENERIC # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) It won't work without miibus. > 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: >=20 > 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 >=20 > Adding "device miibus" and "device fxp" to the custom kernel, > and a reboot, results in a working Ethernet port: >=20 > 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 >=20 > Is this known behavior ? >=20 > I seem to recall being able to use the kernel module approach > to access the Ethernet port in 5.2.1-RELEASE. >=20 > 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. >=20 > ------------------------------ >=20 > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" >=20 > End of freebsd-mobile Digest, Vol 92, Issue 1 > ********************************************* >=20 --=-9mPUVAesLiYml8aHVmho Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBxysgqvkwR1WdokwRAhCAAJ9UNWjgMMTX3vIBrU2+xVIsvNrX7wCfa6iZ eWJjMYG6cfGiwCv0yEo+8Cw= =ks2r -----END PGP SIGNATURE----- --=-9mPUVAesLiYml8aHVmho--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1103571744.846.6.camel>