From owner-freebsd-hardware Wed Sep 11 11:39:43 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6671737B400 for ; Wed, 11 Sep 2002 11:39:39 -0700 (PDT) Received: from pescado.nosc.mil (pescado.nosc.mil [128.49.4.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80FB843E42 for ; Wed, 11 Sep 2002 11:39:37 -0700 (PDT) (envelope-from homyk@nosc.mil) Received: from weeds (weeds.spawar.navy.mil [128.49.212.17]) by pescado.nosc.mil (Netscape Messaging Server 4.15) with ESMTP id H2AEHY00.F8G; Wed, 11 Sep 2002 11:39:34 -0700 Message-Id: <4.2.0.58.20020911123431.01f2bce0@mailsd1.spawar.navy.mil> X-Sender: homyk@mailsd1.spawar.navy.mil X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 11 Sep 2002 12:41:04 -0700 To: David =?iso-8859-1?Q?Sieb=F6rger?= From: "Yau Keung Hom" Subject: Re: NIC on Compaq EV0 510R Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <20020911173033.GA1373@rucus.ru.ac.za> References: <4.2.0.58.20020911104437.01f2b330@mailsd1.spawar.navy.mil> <3D7EB097.8FBE8E41@spawar.navy.mil> <3D7EB097.8FBE8E41@spawar.navy.mil> <4.2.0.58.20020911104437.01f2b330@mailsd1.spawar.navy.mil> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Adding 103B got the kernel to recognize the board. Everything comes up,=20 but the interface isn't working. Pinging from it has the error: ping: sendto: Permission denied ifconfig seems happy, and the interface responds to arp (other hosts on the= =20 net have an arp entry for this board), but it doesn't respond to ping, nor= =20 can I send from it. Any ideas on this? I've seen the sendto error before= =20 (on other NIC cards) when the interface was in the wrong media, but I'm not= =20 sure what is causing this one. Incidently, what PCI device number does your 82562 NIC use? Yau Keung At 07:30 PM 9/11/02 +0200, David Sieb=F6rger wrote: >On Wed 2002-09-11 (11:15), Yau Keung Hom wrote: > > Here is my dmesg output > > > > pci0: at 29.7 irq 5 > > pcib1: at device 30.0 on= pci0 > > pci5: on pcib1 > > pci5: (vendor=3D0x8086, dev=3D0x103b) at 8.0 irq 5 > > <5 lines deleted> > > pci0: (vendor=3D0x8086, dev=3D0x24c5) at 31.5 irq 5 > > > > and my pciconf output ( I only included the unknown devices) > >According to /usr/share/misc/pci_vendors, these are: > > > none1@pci0:29:7: class=3D0x0c0320 card=3D0x00b90e11= chip=3D0x24cd8086 > > rev=3D0x01 hdr=3D0x00 > >82801DB (ICH4) USB EHCI Controller > > > none2@pci0:31:5: class=3D0x040100 card=3D0x00ad0e11= chip=3D0x24c58086 > > rev=3D0x01 hdr=3D0x00 > >82801DB (ICH4) AC'97 Audio Controller > > > none3@pci5:8:0: class=3D0x020000 card=3D0x00120e11 chip=3D0x103b8086= rev=3D0x81 > > hdr=3D0x00 > >82801DB (ICH4) LAN Controller with 82562EM/EX PHY > > > The network device shows up in the PCI, but it doesn't appear to be > > recognized by the driver. Is it enough to add 0x103b to the ident= table? > >Unless the 82562EM/EX are significantly different from the other fxp >chips (unlikely), that ought to do the trick. Give it a try, and if >it works, file a PR so that the driver can be updated. > > >-- >David Sieb=F6rger >drs@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message