linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stanko Juzbasic <stanko.juzbasic@zg.tel.hr>
To: Bill Schottstaedt <bil@ccrma.Stanford.EDU>,
	paulus@cs.anu.edu.au,
	"linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Audio file open problem on LINUXPPC 1999 solution
Date: Wed, 28 Jul 1999 14:32:13 +0200	[thread overview]
Message-ID: <379EF84B.8E9B69D4@zg.tel.hr> (raw)


To whoever it may concern

It seems I found the cause and solution to the LINUXPPC 1999 audio file
open problem I wrote about two days ago:

The problem occurs only if one installs the new LINUXPPC 1999 filesystem
from scratch using the release CD-ROM installer. It has several  bugs,
among which this one:

- it fails to create /dev/dsp (eventhough it creates /dev/dsp1...),
without giving a notice
- default system sound apps have an endianness problem, so they don’t
give a proper
    error message.

The solution is to [MAKEDEV audio] manually and rebuild CCRMA sndlib,
and sound will work perfectly.

Best,

Stanko
.



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

             reply	other threads:[~1999-07-28 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-28 12:32 Stanko Juzbasic [this message]
1999-07-28 14:38 ` Audio file open problem on LINUXPPC 1999 solution Jerry Quinn

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=379EF84B.8E9B69D4@zg.tel.hr \
    --to=stanko.juzbasic@zg.tel.hr \
    --cc=bil@ccrma.Stanford.EDU \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@cs.anu.edu.au \
    /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;
as well as URLs for NNTP newsgroup(s).