[gobolinux-users] Kernel modules woahs

[Lucas C. Villa Real]

On Feb 7, 2008 1:21 AM, James Mathews <jammers at gmail.com> wrote:
> Hey.
>
> I've recently installed gobo linux and I'm loving it, brilliant idea
> and well implemented.
>
> I'm having a little trouble with some kernel modules though....
>
> I have an rt2500 wi-fi card. There are kernel drivers for this (I used
> them in my last linux setup). I downloaded the drivers and compiled
> the modules. I ran modules_install from the makescript with the
> drivers and It installed them to:
>
> /Programs/Linux/2.6.23.8/Resources/Unmanaged/System/Kernel/Modules/2.6.23.8-Gobo/extra/rt2500.ko

You need to install it at $target/$goboModules instead, and then use
the unmanaged_files=() to specify that
"$goboModules/Current/extra/rt2500.ko" will be generated by your
recipe after SymlinkProgram is invoked. This is how we do it in the
Ndiswrapper recipe:

make_variables=(
    "DESTDIR=$target"
    "INST_DIR=$target/Resources/Unmanaged/${goboKernel}/Modules/Current/misc"
    "KBUILD=$goboModules/Current/build"
)

unmanaged_files=(
    "${goboKernel}/Modules/Current/misc/ndiswrapper.ko"
)

The variable names might change in the make_variables array, though.

> I added:
>
> alias ra0 rt2500
>
> Into modprobe.conf
>
> and:
> UserDefinedModules=(
>    rt2500
> )
>
> to my boot options.
>
> However when I boot, the kernel module is not loaded. And when I run
>
> modprobe rt2500
>
> FATAL: Module rt2500 not found.
>
> However if I run
> insmod /Programs/Linux/2.6.23.8/Resources/Unmanaged/System/Kernel/Modules/2.6.23.8-Gobo/extra/rt2500.ko
>
> then it works (as one would expect).
>
>
> Is my module installed in the wrong location? Or have I got an option
> wrong somewhere?

Yep, that happens because you installed and symlinked Rt2500 and not
the Linux package. If you run 'SymlinkProgram Linux' and answer 'y' to
get its unmanaged files installed everything should work as expected
(given that you run 'depmod -a' as well).

However it's not good practice to allow an application to store files
in another one's domain. The suggestions above should be enough to
generate a good recipe.

-- 
Lucas
powered by /dev/dsp