From owner-freebsd-questions Mon Feb 19 19:53:34 2001 Delivered-To: freebsd-questions@freebsd.org Received: from newfrontiers.nfis.com (newfrontiers.nfis.com [206.151.91.4]) by hub.freebsd.org (Postfix) with ESMTP id 2B30237B401 for ; Mon, 19 Feb 2001 19:53:29 -0800 (PST) Received: from monsterbox (pub76.hunt2.nfis.com [206.151.91.176]) by newfrontiers.nfis.com (8.9.0/8.9.0) with SMTP id WAA00369 for ; Mon, 19 Feb 2001 22:55:08 -0500 Message-ID: <001001c09af1$83296d60$1101a8c0@monsterbox> From: "Tom Dean" To: Subject: miibus device and intel 815e chipsets Date: Mon, 19 Feb 2001 22:59:22 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C09AC7.994FFF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C09AC7.994FFF20 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: 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_000D_01C09AC7.994FFF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello again,
 
    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. 
 
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.  
 
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:
 
sis0: <NatSemi DP83815 = 10/100BaseTX> at=20 device 11.0 on pci2 
sis0: couldn't map = ports/memory
device_probe_and_attach: sis0 attach = returned=20 6
 
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:
 
dc0: <82c169 PNIC 10/100BaseTX> = at device=20 11.0 on pci2
dc0: couldn't map=20 ports/memory
device_probe_and_attach: dc0 attach = returned=20 6   
 
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.
 
Tom Dean
tomdean@nfis.com
=
------=_NextPart_000_000D_01C09AC7.994FFF20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message