Date: Mon, 19 Feb 2001 15:41:01 -0500 From: "Tom Dean" <tomdean@nfis.com> To: <freebsd-questions@FreeBSD.ORG> Subject: Intel 815e chipset support and miibus device Message-ID: <000d01c09ab4$465f10c0$1101a8c0@monsterbox>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C09A8A.5C5C6FA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello again,
I sent an email to you the other day regarding a question about =
support for the Netgear FA311in FreeBSD4.2-RELEASE. I was told to make =
sure that device "sis" and device "miibus" are in my kernel. They are, =
and I even setup and compiled a custom kernel for my pc. =20
I apologize if this email message becomes too time consuming--my current =
system is a Pentium III 933-MHz Coppermine on an ASUS CUSL2. The CUSL2 =
utilizes the Intel 815e chipset which I'm not too sure if FreeBSD =
completely supports. I checked the release notes for version 4.2 and it =
said that new ATA 100 controllers are supported. =20
I booted the generic kernel and my custom kernel to check and see if =
either one picked up my NIC successfully. When I ran dmesg for both =
kernels it read something like this:
=20
sis0: <NatSemi DP83815 10/100BaseTX> at device 11.0 on pci2=20
sis0: couldn't map ports/memory
device_probe_and_attach: sis0 attach returned 6
The funny thing is that also when I ran dmesg, the device "miibus" never =
shows up in either kernel, and each kernel has that device supported. =
However, FreeBSD does pick up the ATA 100 controller and calls it "Intel =
ICH2 ATA 100," and well as the other USB devices. I have the Complete =
FreeBSD and I also have the Handbook, and I know that sis0 is dependent =
upon miibus because of the transceiver type. I tried it with another =
NIC, the Netgear FA310. Same thing happens:
=20
dc0: <82c169 PNIC 10/100BaseTX> at device 11.0 on pci2=20
dc0: couldn't map ports/memory
device_probe_and_attach: dc0 attach returned 6 =20
It seems that FreeBSD isn't detecting the miibus device which isn't =
allowing my NIC to operate. Could that be related to my i815e chipset, =
or is there another device I have to enable in the kernel? I've also =
tried moving the cards around in other PCI slots and manually setting =
IRQs in the BIOS but that didn't work. Please respond. I really =
appreciate how quickly my previous question was answered. Thank you =
very much.
Tom Dean
tomdean@nfis.com
------=_NextPart_000_0008_01C09A8A.5C5C6FA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3207.2500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello again,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> I sent an email to =
you the other=20
day regarding a question about support for the Netgear FA311in=20
FreeBSD4.2-RELEASE. I was told to make sure that device "sis" and =
device=20
"miibus" are in my kernel. They are, and I even setup and compiled =
a=20
custom kernel for my pc. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I apologize if this email message =
becomes too time=20
consuming--my current system is a Pentium III 933-MHz Coppermine on an =
ASUS=20
CUSL2. The CUSL2 utilizes the Intel 815e chipset which I'm not too =
sure if=20
FreeBSD completely supports. I checked the release notes =
for=20
version 4.2 and it said that new ATA 100 controllers are=20
supported. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I booted the generic kernel and my =
custom=20
kernel to check and see if either one picked up my NIC=20
successfully. When I ran dmesg for both kernels it read =
something=20
like this:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>sis0: <NatSemi DP83815 =
10/100BaseTX> at=20
device 11.0 on pci2 </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>sis0: couldn't map =
ports/memory</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>device_probe_and_attach: sis0 attach =
returned=20
6</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>The funny thing is that also when I ran =
dmesg, the=20
device "miibus" never shows up in either kernel, and each kernel=20
has that device supported. However, FreeBSD does pick up the =
ATA 100=20
controller and calls it "Intel ICH2 ATA 100," and well as the other =
USB=20
devices. I have the Complete FreeBSD and I also have=20
the Handbook, and I know that sis0 is dependent upon miibus because =
of the=20
transceiver type. I tried it with another NIC, the Netgear =
FA310. =20
Same thing happens:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>dc0: <82c169 PNIC 10/100BaseTX> =
at device=20
11.0 on pci2 </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>dc0: couldn't map=20
ports/memory</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>device_probe_and_attach: dc0 attach =
returned=20
6 </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>It seems that FreeBSD isn't detecting =
the miibus=20
device which isn't allowing my NIC to operate. Could that be =
related to my=20
i815e chipset, or is there another device I have to enable in the =
kernel? =20
I've also tried moving the cards around in other PCI slots and manually =
setting=20
IRQs in the BIOS but that didn't work. Please respond. I =
really=20
appreciate how quickly my previous question was answered. Thank =
you very=20
much.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Tom Dean</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>tomdean@nfis.com</FONT></DIV></BODY></HTML>
------=_NextPart_000_0008_01C09A8A.5C5C6FA0--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000d01c09ab4$465f10c0$1101a8c0>