From: "Sean Rima" <lists@tcob1.net>
To: linux-kernel@vger.kernel.org
Subject: Sound problem with 2.2.19
Date: Monday, 09 Apr 2001 21:29:26 +000 [thread overview]
Message-ID: <9at636$pf9$2@tcob1.net> (raw)
Originally to: All
I am sorry if this is old news but I have not seen any mention of it in the
list.
I keep getting "kernel: Sound error: Couldn't allocate DMA buffer" in my
syslog. However sound was working until this morning. The machine uptime is
below :)
The PC is a IBM PS/2 486DX2, with an AWE32 with 256k. The PC is fitted with
16mb of ram. I have never reported a problem before so excuse if it is a bit
strange.
Sean
--
GNUPG ID 92B9D0CF | YAIM: thecivvie | Fidonet and BBS
ICQ: 679813 | Homepage: http://www.tcob1.net | Newsportal at
Linux User: #124682 | AIM: tcobone | tcob1.uklinux.net
My last power cut was 3d, 4h and 25m ago on Linux 2.2.19.
<-> Information
This message originated from a Fidonet system and was gated at
There Can Only be 1 (http://www.tcob1.net)
For information of Fidonet visit http://www.fidonet.org
Please do not respond direct to this message but via the
next reply other threads:[~2001-04-09 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 21:29 Sean Rima [this message]
2001-04-09 23:50 ` Sound problem with 2.2.19 Sean Rima
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='9at636$pf9$2@tcob1.net' \
--to=lists@tcob1.net \
--cc=linux-kernel@vger.kernel.org \
/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