linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: "Michel Ddnzer" <michdaen@iiic.ethz.ch>, linuxppc-dev@lists.linuxppc.org
Subject: Re: problems when recompiling dmasound modules
Date: Thu, 04 Jan 2001 09:56:34 +0000	[thread overview]
Message-ID: <200101040956.JAA16492@hyperion.valhalla.net> (raw)



> Whenever I rebuild my linux-pmac-devel tree when the kernel version changed I
> get bitten by this:
> The sound modules don't get rebuilt so their version doesn't match the kernel
> version and they can't be insmoded.
> I can investigate to find a solution myself but I figured it should be easier
> for Geert or one of the other dmasound hackers to fix it.

I just did (after an absence of nearly six months ;-) :

rsync ppc.samba.og::linux-pmac-devel - which picked up 2.4.0-t13-p3
make mrproper
make menuconfig (selected, amongst other things, sound card support built
in, pmac sound as module)
make dep vmlinux modules modules_install
  - I saw it compile the damsound_core, dmasound_awacs
copied the kernel to my MacOS partition...
rebooted
modprobe dmasound_awacs

and viola!
it seemed to work as before...

(so maybe that wasn't what you were saying at all ;-)

ciao,
Iain.

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

             reply	other threads:[~2001-01-04  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04  9:56 Iain Sandoe [this message]
2001-01-04 11:51 ` problems when recompiling dmasound modules Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2001-01-05 15:58 Iain Sandoe
2001-01-05 21:20 ` Michel Dänzer
2001-01-04 13:17 Iain Sandoe
2001-01-05 15:10 ` Michel Dänzer
2001-01-05 15:20   ` Geert Uytterhoeven
2001-01-04  3:59 Michel Dänzer

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=200101040956.JAA16492@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=michdaen@iiic.ethz.ch \
    /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).