From owner-freebsd-current Tue Dec 7 9: 2:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 5CC2214DEA for ; Tue, 7 Dec 1999 09:02:50 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id MAA00662; Tue, 7 Dec 1999 12:02:49 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Tue, 7 Dec 1999 12:02:49 -0500 (EST) From: Kenneth Culver To: Pat Lynch Cc: freebsd-current@freebsd.org Subject: Re: Sound Blaster ViBRA16X and pcm driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just use pnpinfo to find out device vender id's and logical id's. It appears that the ViBRA16X is supported (with the correct logical id) in /usr/src/sys/dev/sound/isa/sbc.c but for some reason a driver is still not being attached for it. Any suggestions? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 7 Dec 1999, Pat Lynch wrote: > On Mon, 6 Dec 1999, Doug White wrote: > > > > > > > unknown0: at port 0x2f8-0x2ff irq 3 on isa0 > > > unknown1: at port > > > 0x220-0x22f,0x300-0x301,0x388-0x38b ir > > > q 9 drq 0,1 on isa0 > > > unknown2: at port 0x201 on isa0 > > > > > > So what exactly do I need to do to get this working? > > > > Can you report the entire dmesg? I suspect this is only one of the > > logical devices. > > > > the nice thing about the old PnP code (in -STABLE and earlier) is that it > showed the Vendor ID and Serials so that it would be trivial to check > whether this is the issue or not. (the driver may simply not know thats > its a card thats supported? incomplete ID list in the driver?) > > having not looked at newpcm for a few months and not having a -current box > here currently to look at source, I couldn't say whther this is the case > or not. > > the question I have is, is there an easy way for a "user" to probe for > these ID's and get this kind of information? > > -Pat > > ___________________________________________________________________________ > > Pat Lynch lynch@rush.net > lynch@bsdunix.net > Systems Administrator Rush Networking > ___________________________________________________________________________ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message