linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Albrecht Dre? <albrecht.dress@arcor.de>
To: Linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Awacs Burgundy sound w/ 2.4.18?
Date: Thu, 4 Apr 2002 21:47:39 +0200	[thread overview]
Message-ID: <20020404194739.GE30247@regulus> (raw)


[I already posted this to the users list, but apparently nobody had a
solution...]

I upgraded an old rev. 1 iMac (bondi blue) to 2.4.18 from kernel.org, and
this somehow broke sound support. Everything used to work with
2.2.17pre-something, and the *same* mixer/xmms/cd player config now stays
silent on both the headphones and the built in speakers; even the console
beep doesn't work. Also, it is not possible to change any settings using
aumix or any other mixer program (xmixer, gmix).

I add some further information below and hope that somebody can give me
hints to resolve the problem. Any help is really welcome!!!

Thanks in advance,

	Albrecht.


~~~~~~~~~~

The dma sound driver is built into the kernel, and it is recognised upon
startup (2.4.18 from kernel.org, built w/ gcc 2.95.3). However, I got the
same results with the sound stuff built as modules:

-----
PowerMac Burgundy  DMA sound driver rev 016 installed
Core driver edition 01.06 : PowerMac Built-in Sound driver edition 00.07
Write will use    4 fragments of   32768 bytes as default
Read  will use    4 fragments of   32768 bytes as default
-----

Roughly the same kernel config works with an Awacs PowerMac 7300 (seems as
if a have a collection of old machines ;-)).

The output of /dev/sndstat looks a little strange to me:

-----
[root@island /root]# cat /dev/sndstat
PowerMac Burgundy DMA sound driver rev 016 :
Core driver edition 01.06 : PowerMac Built-in Sound driver edition 00.07
44100 s: s/sec
HW AFMTS: signed 16 bit BE signed 16 bit LE
                  === Formats & settings ===
Parameter                 soft                hard
Format   :    signed 16 bit LE    signed 16 bit BE
Samp Rate:         44100 s/sec         44100 s/sec
Channels :                mono              stereo
                  === Sound Queue status ===
Allocated: Buffers  Size
     write:       4 32768
      read:       0     0
Current  : MaxFrg FragSiz MaxAct Frnt Rear Cnt RrSize A B S L  xruns
     write:      4    4096      4    0   -1   0      0 0 0 0 0      5
      read:      0       0      0    0    0   0      0 0 0 0 0      0
-----

Finally, here is the constant output of aumix (== any attempt to change
settings is ignored silently):

-----
[root@island /root]# aumix -q
vol 100, 100
speaker 0, 99
line 100, 100, P
mic 0, 0, P
cd 100, 100, P
pcm2 76, 0
-----


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
        Phone (+49) 228 6199571  -  mailto:albrecht.dress@arcor.de
_________________________________________________________________________

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2002-04-04 19:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020404194739.GE30247@regulus \
    --to=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).