Sound on G4 tower, success

Dave Ray g4tinker at
Wed Oct 24 09:38:21 EST 2001

--- Derrik Pates <dpates at> wrote:
> What errors are those? Nothing you've posted so far
> looks like an error to
> me.
> > Oct 19 20:53:48 garuda kernel: tumbler:no device
> That's from not having a devnode for "amp-mute",
> "headphone-mute" or
> "headphone-detect". I don't think that's a problem.
> > Oct 19 20:53:48 garuda kernel: i2c-keywest: Ack
> Status
> > on addr expected but got: 0x09 on addr: 0x34
> That's just because the tas3001 driver code (the
> mixer for the
> Tumbler/Texas) is searching all available I2C buses,
> and the first one
> doesn't have what it's looking for.

Thanks for your insight to these error messages. After
seeing your confidence that syslog looked okay, I
hypothesized that the output jacks may be live even
though the built-in speaker is dead silent. I plugged
the output audio jacks to an amplifier, and voila,
sound is is working there just fine.

Under MacOS (and Open Firmware) the internal speaker
is on by default, and turns off only when the audio
jack is physically connected. I assumed it was a
hardware switch and that if sound is working, I should
expect to hear it on the internal speaker. Not the
case apparently with dmasound_pmac. The speaker is
completely dead, and the output jack is always on,
regardless of whether a plug is connected. Is this a
bug? (Don't get me wrong, I'm delighted that it

This should go in some FAQ. Who's maintaining an FAQ
for the Mac G4 towers?

Thanks for all your help looking over my data,


** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list