From owner-freebsd-questions Sat Sep 23 16:27:23 2000 Delivered-To: freebsd-questions@freebsd.org Received: from aero.org (aero.org [130.221.16.2]) by hub.freebsd.org (Postfix) with ESMTP id F030437B424 for ; Sat, 23 Sep 2000 16:27:20 -0700 (PDT) Received: by aero.org id <17100-2>; Sat, 23 Sep 2000 16:27:10 -0700 Received: from rushe.aero.org(130.221.201.83) via SMTP by aero.org, id smtpdAAAa29620; Sat Sep 23 16:26:54 2000 Received: from calamari.aero.org (calamari.aero.org [130.221.202.67]) by rushe.aero.org (8.9.3/8.9.3) with ESMTP id QAA23170; Sat, 23 Sep 2000 16:26:53 -0700 (PDT) Received: (from cal@localhost) by calamari.aero.org (8.9.3+Sun/8.9.3) id QAA05389; Sat, 23 Sep 2000 16:26:52 -0700 (PDT) Message-Id: <200009232326.QAA05389@calamari.aero.org> From: cal@rushe.aero.org To: freebsd-questions@FreeBSD.ORG Subject: Re: dmesg codes, , MORE INFO Cc: cal@rushe.aero.org, janko@parmenides.utp.net, matt@gsicomp.on.ca Date: Sat, 23 Sep 2000 16:27:01 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanx to all who replied - more information: the specific dmesg lines i am wondering about are pci0:(vendor=0x12eb, dev=0x0001) at 14.0 irq 10 on one 4.0 desktop machine, and pci1:(vendor=0x1274, dev=0x1371) at 9.0 irq 10 pci1:(vendor=0x12b9, dev=0x1008) at 11.0 irq 9 pci0:(vendor=0x8086, dev=0x2413) at 31.3 irq 10 on a different (newer) one (the lines were not all consecutive, but they did occur in this order) the NICs in both machines are properly recognized and working, to answer one of the respondents what i am actually looking for is a table of vendors with these vendor and device codes (yes, i expect it to be very long) - is it a FreeBSD specific list? if not, then where does it come from, some industry or manufacturing association? either way, where can i find a recent version of the list? more later, i expect, cal Dr. Christopher Landauer Aerospace Integration Science Center cal@aero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message