From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Greg Stark <gsstark@mit.edu>,
linux-kernel@vger.kernel.org,
Patrick McFarland <pmcfarland@downeast.net>
Subject: Re: OSS Audio borked between 2.6.6 and 2.6.10
Date: Mon, 14 Mar 2005 01:03:55 +0000 [thread overview]
Message-ID: <200503140103.55354.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <874qff89ob.fsf@stark.xeocode.com>
On Sunday 13 March 2005 22:26, you wrote:
> Patrick McFarland <pmcfarland@downeast.net> writes:
> > On Saturday 12 March 2005 01:31 pm, Greg Stark wrote:
> > > OSS Audio doesn't work properly for Quake3 in 2.6.10 but it worked in
> > > 2.6.6. In fact I have the same problems in 2.6.9-rc1 so I assume 2.6.9
> > > is affected as well. This is with the Intel i810 drivers.
> >
> > Why are you not using ALSA?
>
> Well frankly because whenever I tried it it didn't work. The i810 drivers
> were *completely* broken in the 2.6 kernel I original installed, 2.6.5 I
> think.
>
> In any case I understood that Quake doesn't work with alsa drivers because
> it depends on mmapped output which they don't support at all. Or something
> like that. I gave up on them when I found OSS worked reliably.
Quake3's doing something strange with the OSS devices. You can work around it
in ALSA's OSS emulation by disabling the record features for the quake3.x86
binary, and it should all work fine.
echo "quake3.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
echo "quake3.x86 0 0 disable" > /proc/asound/card0/pcm0c/oss
(I gleamed the above from google.com, you might need to modify it slightly).
The intel8x0 driver is probably one of the most widely used ALSA drivers, so
I'd hope it wasn't broken! My laptop uses the driver, it is superb.
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/CSim Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
next prev parent reply other threads:[~2005-03-14 1:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 18:31 Greg Stark
2005-03-13 6:52 ` Patrick McFarland
2005-03-13 22:26 ` Greg Stark
2005-03-14 0:48 ` Martin Schlemmer
2005-03-14 1:03 ` Alistair John Strachan [this message]
2005-03-14 3:50 ` Greg Stark
2005-03-14 4:07 ` Andrew Morton
2005-03-14 4:42 ` Greg Stark
2005-03-14 4:55 ` Andrew Morton
2005-03-14 5:39 ` Greg Stark
2005-03-14 5:57 ` Andrew Morton
2005-03-14 6:21 ` Greg Stark
2005-03-14 6:48 ` Andrew Morton
2005-03-14 8:59 ` Greg Stark
2005-03-14 9:53 ` Andrew Morton
2005-03-14 15:40 ` Greg Stark
2005-03-14 15:52 ` John W. Linville
2005-03-22 0:38 ` Andrew Morton
2005-03-22 4:16 ` Greg Stark
2005-03-14 15:33 ` John W. Linville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200503140103.55354.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=gsstark@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pmcfarland@downeast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®