Date: Tue, 7 Dec 1999 11:38:51 -0500 (EST) From: Pat Lynch <lynch@bsdunix.net> To: Doug White <dwhite@resnet.uoregon.edu> Cc: Kenneth Culver <culverk@culverk.student.umd.edu>, freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster ViBRA16X and pcm driver Message-ID: <Pine.BSF.4.05.9912071134490.10407-100000@bytor.rush.net> In-Reply-To: <Pine.BSF.4.21.9912061830360.43415-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 6 Dec 1999, Doug White wrote: > > > > unknown0: <SupraExpress 56i> at port 0x2f8-0x2ff irq 3 on isa0 > > unknown1: <Creative ViBRA16X PnP> at port > > 0x220-0x22f,0x300-0x301,0x388-0x38b ir > > q 9 drq 0,1 on isa0 > > unknown2: <Game> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9912071134490.10407-100000>