From owner-freebsd-isp Tue Apr 15 11:16:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA26771 for isp-outgoing; Tue, 15 Apr 1997 11:16:35 -0700 (PDT) Received: from fireball.blast.net (fireball.blast.net [204.141.163.53]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26764 for ; Tue, 15 Apr 1997 11:16:31 -0700 (PDT) Received: from flashpoint.blast.net (flashpoint.blast.net [204.141.163.62]) by fireball.blast.net (8.8.5/8.8.5) with ESMTP id OAA06582 for ; Tue, 15 Apr 1997 14:17:00 -0400 (EDT) Message-Id: <199704151817.OAA06582@fireball.blast.net> From: "Pat McPartland" To: Subject: Re: smc9332 and freeBSD 2.1.5 problems Date: Tue, 15 Apr 1997 14:12:56 -0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, so far I've upgraded to 2.2.1 and recompiled my kernel for device de0 device de1 controller is ncr0 I added a -link1 -link2 to my sysconfig and I get: de0: enabling 10base port de0 transmission timeout. I added a -link1 link2 , then link2, then link1 link2... Just hangs at add net default: gateway xxx.xxx.xxx.xxx Every time the link lights start as ON then as soon as de0 probe comes up the lights go OFF. What else could it be? A PCI conflict?? It doesn't seem that any sysconfig will work. Pat mcp@blast.net ---------- From: Russ Panula To: Pat McPartland Cc: Blaine Minazzi ; freebsd-isp@freebsd.org Subject: Re: smc9332 and freeBSD 2.1.5 problems Date: Wednesday, April 09, 1997 5:14 PM Hi Pat, On Wed, 9 Apr 1997 15:42:37 -0400, "Pat McPartland" wrote: >These cards are PCI cards. How would I set the kernel to find these cards? > How does the kernel handle PCI? > Within your kernel config file you should be able to specify: controller pci0 device de0 device de1 And the cards should be detected. Some bios setups will let you assign IRQ's manually to the cards. Make sure you are using the correct ethernet port on the card. Try adding -link2 or link2 to your ifconfig statements. >---------- >> From: Blaine Minazzi >> To: Pat McPartland >> Subject: Re: smc9332 and freeBSD 2.1.5 problems >> Date: Wednesday, April 09, 1997 12:56 PM >> >> Pat McPartland wrote: >> > >> > Hello, >> > I am trying to get smc9332 10/100 cards to work in FreeBSD. They >detect as >> > de0 and de1. >> > >> > Well, first, I can't even get one to work. I set up the card as such >in >> > sysconfig: >> > network_interfaces="de0 lo0" >> > ifconfig_de0="inet xxx.xxx.xxx.xxx netmask 255.255.255.0" >> > ifconfig_lo0="inet localhost" >> > >> > and de0 is enabled (i'm using GENERIC kernel at the moment). >> > No error, it just can't find anything on the network. Note this worked >> > with 3com Etherlink3 (ep0). >> > >> > And the cards work in my win95 machine. >> > >> > I am going to trying to setup two of these cards in a dual-homed >machine. >> > >> > Fun,fun,fun. >> > >> > Thanks, >> > >> > Pat >> > >> > Patrick McPartland >> > mcp@blast.net >> >> Hate to ask a silly question, but are the cards set up at the interupt >> and address that the kernel is compiled with? >> >> I would suggest that you either: >> >> a: Look at the config of the kernel and check the address and IRQ the >> card is supposed to work at, and set the cards there. >> >> b: recompile the kernel with the parameters you need. >> >> I would personally go with option b... >> >> Oh yeah... if these are software set cards, did WIN95 "HELP" you >> by resetting the cards to what IT wanted? I have seen it happen with >> other cards. WinBLows changes settings on them without even a "by your >> leave". >> >> I would also get ONE card working FIRST. then go to dual homed. >> >> Good Luck >> >> Blaine >