From: Steffen Haeuser <SteffenH@hyperion-software.de>
To: Iain Sandoe <iain@sandoe.co.uk>, linuxppc-dev@lists.linuxppc.org
Subject: Re: sound again [was: Re: xf4 bug report]
Date: Tue, 25 Jul 2000 18:30:57 -0500 [thread overview]
Message-ID: <yam8241.2878.148063952@mail.lf-online.de> (raw)
In-Reply-To: <200007251558.QAA02148@hyperion.valhalla.net>
Am 25-Jul-00 schrieb Iain Sandoe:
Hi!
>can you do a 'dmesg' and find any lines which have "dmasound" in them?
>Or... are you using sound as modules?
>I assume you are using Ben's binary (pre10-ben2)?
I just checked the message. I was wrong about the DMA stuff... sorry...
it reads
modprobe: can't locate module sound
rc.sysinit: Loading Sound module failed
Sounds as if the module is missing... but I installed the modules
exactly how I found them on the site... and the kernel and system.map
also...
>OK - I'll do it later (just this once :-) I don't want to as a general rule
>- because I have to pay for download bandwidth -- if there's a general move
Well, same here...
>for people to want to download binaries - I'll have to beg some space on an
>ftp server...
>I can't just send you the binaries for the modules - because they wouldn't
>load against an un-patched 2.2.17pre10.
Ah...
>OK, OK, maybe I wasn't clear ==> the dmasound stuff has bits for several
>machines including some of the 68k ones...
Ah :)
>You can find this using "Display Name Registry" on the apple side [it's
>available on the Apple web site IIRC] look under davbus:sound.
Not sure if I know what you mean...
>- or by looking in the /proc/device-tree on the linux side (I hope -
>although, of course, this could be the root of the problem :).
Well, I found the /proc/device-tree... what to look for there ? There are
a lot of files and directories...
Steffen
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-25 23:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 15:58 sound again [was: Re: xf4 bug report] Iain Sandoe
2000-07-25 23:30 ` Steffen Haeuser [this message]
2000-07-25 16:46 ` Franz Sirl
-- strict thread matches above, loose matches on Subject: below --
2000-07-26 18:38 Iain Sandoe
2000-07-26 18:29 Iain Sandoe
2000-07-25 21:41 Iain Sandoe
2000-07-25 19:53 Iain Sandoe
2000-07-26 3:51 ` Steffen Haeuser
2000-07-25 19:30 Iain Sandoe
2000-07-26 14:37 ` Steffen Haeuser
2000-07-26 9:59 ` Michel Dänzer
2000-07-26 11:09 ` Benjamin Herrenschmidt
2000-07-26 12:55 ` Topi Kanerva
2000-07-26 13:10 ` Benjamin Herrenschmidt
2000-07-26 13:13 ` Topi Kanerva
2000-07-25 19:25 Iain Sandoe
2000-07-26 2:53 ` Steffen Haeuser
2000-07-25 18:53 Iain Sandoe
2000-07-26 2:31 ` Steffen Haeuser
2000-07-25 18:35 Iain Sandoe
2000-07-26 1:59 ` Steffen Haeuser
2000-07-26 2:30 ` Steffen Haeuser
2000-07-25 14:42 Iain Sandoe
2000-07-25 22:50 ` Steffen Haeuser
2000-07-25 18:49 ` Geert Uytterhoeven
2000-07-26 18:59 ` Steffen Haeuser
2000-07-26 17:27 ` Michael Schmitz
2000-07-27 0:49 ` Steffen Haeuser
2000-07-26 17:58 ` Michael Schmitz
2000-07-26 18:48 ` Michel Dänzer
2000-07-26 19:28 ` Michael Schmitz
2000-07-27 1:29 ` Steffen Haeuser
2000-07-27 12:13 ` Geert Uytterhoeven
2000-07-27 20:44 ` Steffen Haeuser
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.2878.148063952@mail.lf-online.de \
--to=steffenh@hyperion-software.de \
--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).