From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Lars Brinkhoff <lars.spam@nocrew.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Sound on G4 tower, success
Date: Sun, 28 Oct 2001 21:39:18 +0100 [thread overview]
Message-ID: <20011028203918.4436@smtp.wanadoo.fr> (raw)
In-Reply-To: <854roj7fqf.fsf@junk.nocrew.org>
>
>* kernel compilation without powerbock power management fails.
> (I resynced serveral times.)
>
>* dmasound_pmac as module can't be loaded because of missing
> symbols (pmu_register_sleep_notifier, pmu_unregister_sleep_notifier).
Looks like your build is screwed in some way.
Either you have dangling root files or versions files. Try make mrproper
as root to clean the tree (after backing up your .config).
>* dmasound_pmac can be successfully compiled into the kernel, but
> there is no sound from neither the internal speaker nor from the
> loudspeakers. I haven't tried the headphone output.
Did you try playing with a mixer like gmix ? The best way to try if
the sound driver works is the console beep. There are plenty of
reasons why a userland app would fail emitting sound, but the
console beep is entirely kernel driven.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-28 20:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 3:38 Sound on G4 tower, almost Dave Ray
2001-10-23 3:48 ` Derrik Pates
2001-10-23 18:21 ` Dave Ray
2001-10-23 18:29 ` Derrik Pates
2001-10-23 23:38 ` Sound on G4 tower, success Dave Ray
2001-10-24 2:19 ` Derrik Pates
2001-10-24 10:18 ` Benjamin Herrenschmidt
2001-10-24 10:48 ` Lars Brinkhoff
2001-10-26 12:08 ` Benjamin Herrenschmidt
2001-10-27 3:08 ` James Baughman
2001-10-28 18:59 ` Lars Brinkhoff
2001-10-28 20:39 ` Benjamin Herrenschmidt [this message]
2001-10-29 9:03 ` Lars Brinkhoff
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=20011028203918.4436@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=lars.spam@nocrew.org \
--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).