From: Steffen Haeuser <SteffenH@hyperion-software.de>
To: Iain Sandoe <iain@sandoe.co.uk>,
daenzerm@student.ethz.ch, linuxppc-dev@lists.linuxppc.org
Subject: Re: xf4 bug report
Date: Tue, 25 Jul 2000 16:14:21 -0500 [thread overview]
Message-ID: <yam8241.1088.147753120@mail.lf-online.de> (raw)
In-Reply-To: <200007251356.OAA14220@hyperion.valhalla.net>
Am 25-Jul-00 schrieb Iain Sandoe:
Hi!
>>> Another problem BTW with this Kernel is that I do not get the sound
working
>>> with it (but could be a configuration problem... I had not yet the time to
>>> look after it).
>>
>> Don't bother, that's a known problem as well. Blame Apple for not releasing
>> specs for the latest sound chips...
>which machine, which kernel (and, if possible, which sound chip - can be
>found from the MacOS side if not the Linux) ?
A "blue/white" G3 Mac first Revision. Kernel is: 2.2.17pre10-ben2 (with the
older
kernel Sound worked - at least I cannot remember that an error message during
OS-booting happened, I never tried out the sound then.
But the new Kernel is needed for the X Server V4)
>I'm trying to build a pattern to help track down the different issues & fix
Sounds nice :)
Steffen
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-25 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 13:57 xf4 bug report Iain Sandoe
2000-07-25 21:14 ` Steffen Haeuser [this message]
2000-07-25 14:47 ` Benjamin Herrenschmidt
2000-07-25 22:52 ` Steffen Haeuser
[not found] <yam8240.1296.140609408@mail.lf-online.de>
2000-07-25 13:48 ` Michel Dänzer
2000-07-25 21:15 ` Steffen Haeuser
2000-07-25 14:24 ` Michel Dänzer
2000-07-25 21:41 ` Steffen Haeuser
2000-07-25 14:37 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 8:18 Jack Howarth
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=yam8241.1088.147753120@mail.lf-online.de \
--to=steffenh@hyperion-software.de \
--cc=daenzerm@student.ethz.ch \
--cc=iain@sandoe.co.uk \
--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).