Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

On Thu, 9 Mar 2006 3aoo-cvfd AT dea.spamcon.org wrote:

> sindi keesan wrote:
> > Does Slackware 10.2 have it?
> > I don't even know where to look - under modules?
>
> Unfortunately recent Slackwares no longer have a separate
> directory where you can download modules.  Here's what the
> MANIFEST for Slack 10.2 says about wireless modules:
>
> lib/modules/2.4.31/kernel/drivers/net/wireless/airo_cs.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/atmel.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/orinoco_cs.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/airo.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/atmel_cs.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/orinoco_tmd.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/orinoco_pci.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/orinoco.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/hermes.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/orinoco_plx.o.gz
> lib/modules/2.4.31/kernel/drivers/net/wireless/prism54/
>
> Cheers,
> Steven

Thanks.  There seems to be no rtl8180 module compiled for Slackware 10.2 
at the official sites.

Where would I look for ndiswrapper, and is it a module or something else?
It is something you use in combination with Windows drivers.  Someone said 
to use the Win2K not the WinXP driver for this chip.  Ubuntu and DSL come 
with ndiswrapper, but DSL 2.2 has left out a lot of things to fit into 
50MB, and put them into another 'dpkg' package which I can't even find, 
that might contain the ndiswrapper, and I can't understand how to use 
Debian packages with apt-get.  I would rather, if possible, not use
ndiswrapper, which other people found tricky.


To compile the network module rtl8180.o, which calls for 2.4 or 2.6 
kernel, for kernel 2.4.31, I think I need to put kernel source into 
/lib/modules/2.4.31/build (along with a .config file for the compiled 
kernel I am using) or direct the Makefile to wherever I put it if not 
there. (I put 2.2.16 source code in /kernelcompile so I could find it 
easily).  Then type 'make' and it should produce a module.

I probably also need kernel headers to compile anything with 2.4.31 so I 
got those from SW10.2 (1.1MB download).

Installpkg put them into
/usr/include/linux
(according to /var/log/packages/kernel*)

However, /usr/include/linux is a symlink to
/usr/src/linux-2.2.16/include/linux
which is where linuxinc for 2.2.16 put the 2.2.16 kernel headers.

So the 2.4.31 headers appear to have overwritten the 2.2.16 headers.
There are dates on the .h files of 1998 to 2005. They have no mention 
of any kernel version in them.    Maybe they are not really kernel 
specific and the 2.4.31 means they are updated to work with 2.4.31 and 
continue working with older kernels such as 2.2.16?

I don't have kernel source code for either kernel on this computer yet so 
I cannot check if I can still make config for 2.2.16.  No big deal, I was 
using a different computer to compile 2.2.16 and am going to compile 
2.4.31 on this computer, in order fix mii.o, which I might want to get 
working before compiling other ethernet modules that could require it, or 
require a kernel that is more network-compatible.  David, if you have some 
ethernet card that uses mii.o I would really appreciate your help getting 
this working as I cannot understand the documentation for kernel 
configuration very well.  It took me a week of trial and error to get 
a working 2.2.16 sound kernel.

Before installing kernel headers for 2.4.31 should I have undone the 
symlink to 2.2.16 and made a /usr/src/linux-2.4.31/ and symlinked to that 
(and switched the symlink if I compile again with 2.2.16 kernel source)?
Why did the install.sh not do that?  Did linuxinc install.sh make the 
linux-2.2.16 to linux symlink?

A very confused Sindi