Re: wireless on Averatec rt2500 chipset

[Paul Kimoto <kimoto@lightlink.com>]

On Thu, Feb 24, 2005 at 06:33:15PM -0500, Phillip Lynx wrote:
> "/lib/modules/2.4.27-speakup/build/Rules.make: No such file or directory
> make: *** No rule to make target
> '/lib/modules/2.4.27-speakup/build/Rules.make'. Stop.
> 
> There is no "build" folder for the Rules.make to be in...
> I've tried an empty "Rules.make" file in a build dir I made, but it seems to
> need some rules to be in the Rules file, go figure...
> How do I find or make Rules.make?
> 
> I would greatly appreciate knowing what to do/try next. I have tried the
> other steps on the directions page, as well as what ideas I could find
> elsewhere, (such as the "empty. Rules.make file)

/lib/modules/2.*/build is expected to be a symbolic link pointing to the
kernel source code.  Rules.make is a file in the kernel source.

-rw-r--r--  1 root src 9325 Feb 18  2004 Rules.make

I don't know whether you will have to install the full source code (I don't
use Debian kernels or even kernel-package).

You might also like to try the CVS version of this driver:
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/rt2400 login
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/rt2400 co source

***

My recipe for building the driver would go something like this:

Install kernel source code.  Find relevant .config file and put it in the
kernel source directory.  While there, run 
$ make include/linux/version.h symlinks oldconfig include/config/MARKER \
       `/bin/pwd`/include/linux/modversions.h

Go to driver source directory.  Run
$ make PATCHLEVEL=4 KERNDIR=/usr/src/linux_SOURCE_CODE_DIRECTORY clean
$ make PATCHLEVEL=4 KERNDIR=/usr/src/linux_SOURCE_CODE_DIRECTORY

Put the resulting kernel module rt2500.o in some appropriate directory
under /lib/modules/2.4.WHATEVER_VERSION.  Make sure that the line

alias ra0 rt2500

is in some file in /etc/modutils.  Make sure that /sbin/update-modules and
/sbin/depmod are run before trying to load the module.

Make sure that /etc/network/interfaces knows what to do with the "ra0"
interface.