On 15 Dec, Frank Barknecht wrote: > [EMAIL PROTECTED] hat gesagt: // [EMAIL PROTECTED] wrote: > >> I've currently reached the stage where I've recompiled my kernel >> having applied the latest awe-drv patch, and am trying to get the >> module to load. I've been following the sbawe32 HOWTO to the letter. > > The link is there. > /etc/rcS.d/S15isapnp should be the link to /etc/init.d/isapnp like this:
It is. It seems to be working fine. I didn't know what rcS.d was for, but now I've found some documentation on it everything makes perfect sense. >> humbug:root> modprobe -a sound >> /lib/modules/2.0.36/misc/sound.o: unresolved symbol unload_awe >> /lib/modules/2.0.36/misc/sound.o: unresolved symbol attach_awe > > This does not look good. > I hope you did use make-kpkg (in the kernel-package) for > building your new kernel. It helps getting rid of some mistakes during > installation of kernel and modules. I didn't. I downloaded the source for 2.0.36 and the latest awe patch; http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/ (version 0.4.3-pre4) > Make sure you have: > > CONFIG_MODULES=y > CONFIG_MODVERSIONS=y > CONFIG_KERNELD=y I do. Which suggests to me that my modules don't match my kernel. What does the "unresolved symbol" message actually mean? Could it be that the unload_awe and attach_awe "symbols" aren't being picked up from my attempts to patch the kernel source? > This for now. Please keep asking. Thank you. And thanks for your helpful reply. I suppose my next questions should be "am I likely to have more joy using make-kpkg?", and "should I get a .deb for my kernel source?" -- Graham
