From owner-freebsd-emulation Fri Oct 23 08:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10041 for freebsd-emulation-outgoing; Fri, 23 Oct 1998 08:30:06 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10005; Fri, 23 Oct 1998 08:30:01 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id KAA26402; Fri, 23 Oct 1998 10:26:13 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 23 Oct 1998 10:26:13 -0500 (CDT) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: "Artem L. Ikoev" Subject: RE: oh. big trouble with awe64/realencoder(linux) in freebsd Cc: freebsd-emulation@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-Oct-98 Artem L. Ikoev wrote: > > freebsd 2.2.7-r > sb awe64 pnp (voxware 3.0-beta950506) > real encoder (linux version) > linux_mod is loaded > > problem: > we need live broadcasting on freebsd. we found only linux version of > real encoder with 'live' function. so, we tried to run it on our > system and we got error : > > --- > LINUX: 'ioctl' fd=4, typ=0x44d(M), num=0xff not implemented > raencoder: Error encountered: Cannot open audio device. > --- > > our sb is working (cat /dev/audio > test; cat test > /dev/audio - ok). > > So? Are any ways to solve this problem? This *may* be reason enough for you to upgrade to FreeBSD 3.0. I had the same sort of problem under 2.2.7-STABLE with an AWE 64, Voxware (with the awedrv 0.4.2c patches), and RealPlayer for Linux. Upgrading to 3.0-CURRENT cured everything for me. Presto! Voila! I had *thought* that the latest mods to the Linux emulation code had been backed into -stable, but even as recently as a week ago or so (the last time I cvsup'ed and built -stable) the problem still existed. Emulation under 3.0, on the other hand, is damn near flawless, as far as I can tell (so far). Despite the warnings Re: 3.0's stability for a production environment, I've found it to be a solid performer, and I feel pretty safe with it (a lot safer than I did with earlier versions of -current, for sure). YMMV, of course. If you're leery of going the full 3.0 upgrade route, you might try upgrading to -stable and see if this helps. Perhaps this problem has been fixed by now. -- Conrad Sabatier Excellent day for putting Slinkies on an escalator. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message