Re: kernel question
On Wed, 14 Aug 2002 19:41:45 +0100
Richard Kimber <rkimber@ntlworld.com> wrote:
> Thanks, but won't there be some confusion between 2.4.18 and
> 2.4.18- bf2.4? E.g. if I'm trying to build some new modules. I
> don't really understand why there isn't a source file corresponding
> in all respects to the kernel I'm running.
No. There are different steps to comple a new kernel:
-> Get the sources
-> Configure the sources (i.e. determine which drivers to build)
-> Compile the sources
But, for different configurations, there is only _one_ source
package. The bf2.4 and 686 and so on flavors only refer to different
*configurations* of sources before building. The
kernel-image-2.4.18-bf2.4 or -686 or so on packages contain a
*compiled* kernel with modules, which is configured according to
/boot/config-<and so on>. That means, the package maintainer
configures his kernel sources (also those "generic" ones) according
to that config file and compiles them and packages them. The
different kernel image packages just contain a different set of
modules (depending on the source configuration) or they are compiled
for different processors (386,686 etc.; you can run a 386 kernel on a
Pentium II machine but not a 686 kernel on a 80386 based PC).
> Thanks for your replies. I'm actually trying to build emu10k1, but
> make tells me:
>
> *** No rule to make target
> `/usr/src/linux/include/linux/rhconfig.h', needed by `audio.o'.
>
> Why is rhconfig.h missing? Is there something special about
> 2.4.18? I note that all the alsa module debs are for 2.4.16. Is
> this significant?
>
Hmm, I don't know; I've also not got this file, but compiled alsa
without any problems... strange, but I'm always building alsa drivers
with the included RedHat rpm build scripts and then alien, after it
didn't work with debian scripts some time ago. Some common problems
with the kernel sources are:
- there is no symlink /usr/src/kernel-source-x.y.z -> /usr/src/linux
- maybe the kernel sources have at least to be configured and "make
dep"ed, i.e.: copy /boot/config-<and so on> to
/usr/src/linux/.config, cd /usr/src/linux, make menuconfig (only
works with libncurses5-dev installed) and leave the menu immediately,
say yes to "save your new kernel configuratioin", make dep.
But there are other solutions you can try, they are probably much
easier:
- just load the emu10k1 module included in the kernel image package
using modconf or...
- get another kernel image (for example 586tsc for pentium or 686)
and download the corresponding alsa-modules-2.4.18-<flavor> package
from unstable; install alsa-base and alsa-utils and libasound2 by
apt-get and alsa-modules-2.4.18-<flavor>.deb by dpkg -i
alsa-modules-2.4.18-<flavor>.deb . But I don't know how the sound
cards can be configured nowadays ;), I've done it by just loading the
modules using modconf. If you use alsa, there another issue: The
channels will be muted by default, that means you'll hear nothing.
I'm using KDE here, so this is no problem, because the kmixer sets
the volume of all channels to the previous values at the startup of
KDE. The new alsa startup scripts (included in alsa-base AFAIK) seem
to autoload modules and previous channel volumes at startup, but I've
just got no idea of how to configure this autoload *g*.
Regards,
Stephan Hachinger
Reply to: