From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Derek Homeier <supas100@astrophysik.uni-kiel.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: general module gottcha...
Date: Wed, 12 Jul 2000 14:06:05 +0100 [thread overview]
Message-ID: <200007121306.OAA00655@hyperion.valhalla.net> (raw)
Wed, Jul 12, 2000, Derek Homeier wrote:
> On Wed, 12 Jul 2000, Iain Sandoe wrote:
>>
>> > I did compile dmasound as module (I noticed that after applyiing your
patch,
>> > dmasound was unselected in .config - is there a reason for this?).
>>
>> Yes, the CONFIG_DMASOUND changed to a set of CONFIG_DMASOUND_XXXX for the
>> various different platforms. Note there is no such thing as 'dmasound.o'
>> any more :-)
>>
>> you have to modprobe:
>> soundcore
>> dmasound_core <params>
>> dmasound_awacs
>>
> Ay, that may be the rub! I think I've still seen 'dmasound.o' when I did
> a lsmod. I did not change conf.modules, that's for sure.
> I have no idea, though, where I might have got the old dmasound.o from,
> because I made a 'mrproper' before the last compiles.
This is because (as things stand) modules_install does *not* remove un-built
modules - just overwrites rebuilt ones with the new versions...
This is probably the only sensible behaviour (gurus?)...
I am (usually) paranoid and do a:
rm -rf /lib/modules/kernel-version-i'm-working-on
before doing modules_install :-)
> I can imagine that
> would have messed up everything a bit, though I'm wondering how the
> module got loaded with the wrong kernel version at all...
Hmmm.. it's probably a little too tolerant - I have module versioning
switched on in all my compiles and that is quite successful at whining when
you've forgotten to delete/update something.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-12 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 13:06 Iain Sandoe [this message]
2000-07-12 13:43 ` general module gottcha Derek Homeier
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=200007121306.OAA00655@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=supas100@astrophysik.uni-kiel.de \
/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).