From owner-freebsd-hardware Sat Jun 10 22:12: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from europa.engg.ksu.edu (Europa.engg.ksu.edu [129.130.81.112]) by hub.freebsd.org (Postfix) with ESMTP id 7F34637BECE for ; Sat, 10 Jun 2000 22:11:57 -0700 (PDT) (envelope-from dave@europa.engg.ksu.edu) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by europa.engg.ksu.edu (8.9.3/8.9.3) with ESMTP id AAA19656; Sun, 11 Jun 2000 00:11:54 -0500 (CDT) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by phobos.engg.ksu.edu (8.9.3+Sun/8.9.1) with SMTP id AAA12872; Sun, 11 Jun 2000 00:20:59 -0500 (CDT) Message-Id: <200006110520.AAA12872@phobos.engg.ksu.edu> Date: Sun, 11 Jun 2000 00:20:58 -0500 (CDT) From: Dave Haney Reply-To: Dave Haney Subject: Re: 3COM 3C900B-TPO (xl0) under FreeBSD 4.0-RELEASE To: ryan@sasknow.com Cc: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 2MGAhRDuDQnYGSwtak2czg== X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4m sparc Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ryan, For what it's worth; I have this card working under FreeBSD on a AlphaStation 200. I've never had any problems with it. Have a nice day. [snip] xl0: <3Com 3cSOHO100-TX OfficeConnect> port 0x10100-0x1017f mem 0x82020100-0x8202017f irq 9 at device 13.0 on pci0 xl0: interrupting at ISA irq 9 xl0: Ethernet address: 00:50:da:75:d9:d2 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto [snip] >Delivered-To: freebsd-hardware@freebsd.org >Date: Sat, 10 Jun 2000 23:06:18 -0600 (CST) >From: Ryan Thompson >To: freebsd-hardware@FreeBSD.ORG >Subject: 3COM 3C900B-TPO (xl0) under FreeBSD 4.0-RELEASE >MIME-Version: 1.0 >X-Loop: FreeBSD.org > > >Hello all, > >I scanned the mailing lists with no real luck. Are there any known >problems with the 3C900B-TPO cards (xl0 driver) under 4.0? I got the >following message in relation to xl0 (if memory serves!) > >xl0: could not map memory/ports > >(I assume this means "conflict" in one form or another). This is a PCI >card with no jumpers, so there appears to be little I can do to move the >card to a different memory range. > >As luck (or planning!) would have it, I didn't have another card (same or >different type) handy to test. I may try a netgear (dc0) card next week. > >- Ryan > >-- > Ryan Thompson > Systems Administrator, Accounts > Phone: +1 (306) 664-1161 > > SaskNow Technologies http://www.sasknow.com > #106-380 3120 8th St E Saskatoon, SK S7H 0W2 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message Dave Haney College of Engineering Computer Systems Analyst Kansas State University dave@engg.ksu.edu 785.532.4643 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message