From owner-freebsd-questions@FreeBSD.ORG Tue Oct 25 01:17:52 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49EE616A41F for ; Tue, 25 Oct 2005 01:17:52 +0000 (GMT) (envelope-from teoheras@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EBC543D5D for ; Tue, 25 Oct 2005 01:17:42 +0000 (GMT) (envelope-from teoheras@gmail.com) Received: by zproxy.gmail.com with SMTP id x3so342224nzd for ; Mon, 24 Oct 2005 18:17:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=A0SSajlseFq3cifl4XL84VSB8cGjVg9fVqOEh2Iv+hlbFcBU8RMEKmLr+qy2Hs7LR/lEZfVPzD0tVrIkUtmmQ8A7GhuXEvdBxAEr0O5xk0SewVR7A//v4v9kGKIWNptnUF0wNwo/1pFFdHmdaUlbpFENDb/oJ7l2pVOOPV8lTMo= Received: by 10.36.216.6 with SMTP id o6mr1420039nzg; Mon, 24 Oct 2005 18:17:41 -0700 (PDT) Received: by 10.36.147.16 with HTTP; Mon, 24 Oct 2005 18:17:41 -0700 (PDT) Message-ID: Date: Mon, 24 Oct 2005 20:17:41 -0500 From: Teo De Las Heras To: freebsd-questions@freebsd.org In-Reply-To: <20051023224002.GB86261@slackbox.xs4all.nl> MIME-Version: 1.0 References: <20051023164050.GA40949@falcon.midgard.homeip.net> <20051023202914.GD82057@slackbox.xs4all.nl> <20051023224002.GB86261@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: How do I name my network interface? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2005 01:17:52 -0000 I have a similar problem with a DFI LanParty Ultra-D with two gigabit on-board NIC's. I DONT see any 'ethernet' subclass devices listed other tha= n the one I have working. Is it simply not supported by the Kernel? The machine in question is dual-booting (with windows), so I can see that the driver for the card that isn't working is NVIDIA. Motherboards website: http://www.dfi.com.tw/Product/xx_product_spec_details_r_us.jsp?PRODUCT_ID= =3D3471&CATEGORY_TYPE=3DLP&SITE=3DUS pciconf -lv output none0@pci0:0:0: class=3D0x058000 card=3D0x00000000 chip=3D0x005e10de rev=3D= 0xa3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D memory isab0@pci0:1:0: class=3D0x060100 card=3D0xcb8410de chip=3D0x005010de rev=3D= 0xa3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D bridge subclass =3D PCI-ISA none1@pci0:1:1: class=3D0x0c0500 card=3D0xcb8410de chip=3D0x005210de rev=3D= 0xa2 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D serial bus subclass =3D SMBus ohci0@pci0:2:0: class=3D0x0c0310 card=3D0xcb8410de chip=3D0x005a10de rev=3D= 0xa2 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D serial bus subclass =3D USB none2@pci0:2:1: class=3D0x0c0320 card=3D0xcb8410de chip=3D0x005b10de rev=3D= 0xa3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D serial bus subclass =3D USB pcm0@pci0:4:0: class=3D0x040100 card=3D0xcb8410de chip=3D0x005910de rev=3D0= xa2 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D multimedia subclass =3D audio atapci0@pci0:6:0: class=3D0x01018a card=3D0xcb8410de chip=3D0x005310de rev= =3D0xa2 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D mass storage subclass =3D ATA atapci1@pci0:7:0: class=3D0x010185 card=3D0xcb8410de chip=3D0x005410de rev= =3D0xa3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D mass storage subclass =3D ATA atapci2@pci0:8:0: class=3D0x010185 card=3D0xcb8410de chip=3D0x005510de rev= =3D0xa3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D mass storage subclass =3D ATA pcib1@pci0:9:0: class=3D0x060401 card=3D0x00000000 chip=3D0x005c10de rev=3D= 0xa2 hdr=3D0x01 vendor =3D 'NVIDIA Corporation' class =3D bridge subclass =3D PCI-PCI none3@pci0:10:0: class=3D0x068000 card=3D0xcb8410de chip=3D0x005710de rev= =3D0xa3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D bridge pcib2@pci0:11:0: class=3D0x060400 card=3D0x00000040 chip=3D0x005d10de rev= =3D0xa3 hdr=3D0x01 vendor =3D 'NVIDIA Corporation' class =3D bridge subclass =3D PCI-PCI pcib3@pci0:12:0: class=3D0x060400 card=3D0x00000040 chip=3D0x005d10de rev= =3D0xa3 hdr=3D0x01 vendor =3D 'NVIDIA Corporation' class =3D bridge subclass =3D PCI-PCI pcib4@pci0:13:0: class=3D0x060400 card=3D0x00000040 chip=3D0x005d10de rev= =3D0xa3 hdr=3D0x01 vendor =3D 'NVIDIA Corporation' class =3D bridge subclass =3D PCI-PCI pcib5@pci0:14:0: class=3D0x060400 card=3D0x00000040 chip=3D0x005d10de rev= =3D0xa3 hdr=3D0x01 vendor =3D 'NVIDIA Corporation' class =3D bridge subclass =3D PCI-PCI hostb0@pci0:24:0: class=3D0x060000 card=3D0x00000000 chip=3D0x11001022 rev= =3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon 64 / Opteron HyperTransport Technology Configuration' class =3D bridge subclass =3D HOST-PCI hostb1@pci0:24:1: class=3D0x060000 card=3D0x00000000 chip=3D0x11011022 rev= =3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon 64 / Opteron Address Map' class =3D bridge subclass =3D HOST-PCI hostb2@pci0:24:2: class=3D0x060000 card=3D0x00000000 chip=3D0x11021022 rev= =3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon 64 / Opteron DRAM Controller' class =3D bridge subclass =3D HOST-PCI hostb3@pci0:24:3: class=3D0x060000 card=3D0x00000000 chip=3D0x11031022 rev= =3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon 64 / Opteron Miscellaneous Control' class =3D bridge subclass =3D HOST-PCI fwohci0@pci1:9:0: class=3D0x0c0010 card=3D0x100615bd chip=3D0x30441106 rev= =3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller' class =3D serial bus subclass =3D FireWire skc0@pci1:10:0: class=3D0x020000 card=3D0x100a15bd chip=3D0x432011ab rev=3D= 0x13 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device =3D '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class =3D network subclass =3D ethernet nvidia0@pci5:0:0: class=3D0x030000 card=3D0x00000000 chip=3D0x014010de rev= =3D0xa2 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' class =3D display subclass =3D VGA On 10/23/05, Roland Smith wrote: > > On Sun, Oct 23, 2005 at 10:52:39PM +0200, Andreas Davour wrote: > > >The "none" only means it's not bound to a driver. You might try the > > >vr(4) driver, although the 6102 is not mentioned in vr(4). > > > > Ok, then "none" makes more sense. It read about the vr driver and it > > worked! How did you know the vr(4) driver was for Rhine I/II/III > > controllers? It feels like there's something I have missed... > > By using this command: "grep Rhine /usr/src/sys/i386/conf/GENERIC", > which returned: "device vr # VIA Rhine, Rhine II". > > Roland > -- > R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain > text. > public key: http://www.xs4all.nl/~rsmith/pubkey.txt > > >