On Sun, 2002-04-21 at 21:09, David Z Maze wrote: > Peter Whysall <peter@guildenstern.dyndns.org> writes: > > On Sun, 2002-04-21 at 19:22, Ron Johnson wrote: > >> Related question: how do you _compile_ extra kernel modules > >> after the kernel is installed and running? > > > > You could do your make (x|menu)config to select what you'd > > forgotten, then do: > ... > > If you're like me and have fallen under the spell of make-kpkg, > > you'd do this: > > > > make-kpkg modules > > That doesn't do what you think it does at all. Specifically, > 'make-kpkg modules' attempts to build signed uploadable versions of > kernel module packages that have their source unpacked under > /usr/src/modules (or $MODULES_LOC, if that's set). Most people will > want to use 'make-kpkg modules-image', which doesn't sign the > modules. And in any case, this won't rebuild the modules that are > built from the kernel source tree; you need to re-run 'make-kpkg > kernel-image' for that. (It wouldn't hurt to bump the kernel revision > number if you do this, though that might require you to rebuild all of > your external modules, too.) Ah. The reason I did this is that I've got the NVIDIA and au8830 drivers as external modules that I build with --added_modules. One lives and learns. -- Peter Whysall peter.whysall@ntlworld.moc The TLD in my email address is sdrawkcab. Debian GNU/Linux 3.0 sid -- kernel 2.4.18
Attachment:
signature.asc
Description: This is a digitally signed message part