configuring ADMTek wi-fi

Muzzy · 05-11-2004, 02:04 PM

Code:

$ less README

...

INSTALL
-------
        This file contains installation instruction and requirements.
        A *must* read.

$ less INSTALL

Gives you the installation instuctions for wireless tools.

Muzzy · 05-11-2004, 02:12 PM

You probably already have an older version of wireless tools installed, so I don't think this is your problem. You can test by running as root:

Code:

# iwconfig --version
iwconfig  Version 26
          Compatible with Wireless Extension v16 or earlier,
          Currently compiled with Wireless Extension v16.

Might be your kernel version? Run this command to see which kernel version you are running:

Code:

uname -r

It should be 2.4.22 based on what you told me earlier:

Quote:

I make the soft link by typing ln -s linux-2.4.22 linux-2.4

bitamois · 05-11-2004, 03:25 PM

I did the INSTALL directions for wireless_tools and I didn't get error messages.

# iwconfig --version
iwconfig Version 26
Compatible with Wireless Extension v16 or earlier,
Currently compiled with Wireless Extension v16.

I have kernel 2.4.22 and I've already make a soft link.

If I go to step 5 in the ADM8211 README file

5. If you have source code and you want to compile it by yourself
a. Install wirelss-tool by yourself.

I think I just did this.

b. Make sure you have the kernel 2.4.x source code. I believe I do.

c. You can modify the Make file to fit your environment. We recommend you make a soft link.

I did this already

d. Type "make"

I get, "make: Nothing to be done for 'all'."
I am assuming I am to be in the wireless_tools.26 when I type "make"

Muzzy · 05-11-2004, 03:57 PM

Quote:

a. Install wirelss-tool by yourself.

I think I just did this.

Yep - iwconfig version = 26

Quote:

b. Make sure you have the kernel 2.4.x source code. I believe I do.

I would like you to run 'uname -r' just to check that the kernel you are running is the one you have the source to. It should be really since I doubt you have upgraded your kernel since you installed! But no harm in checking...

I dunno, but maybe you need a configured kernel source. In otherwords, go to your kernel directory and type 'make menuconfig' as root and then exit and save.

c. should be fine. You can check that the link exists by doing:

Code:

ls -l /usr/src

and checking that there is a linux-2.4 and that it points to the 2.4.22 directory.

Quote:

d. Type "make"

I get, "make: Nothing to be done for 'all'."
I am assuming I am to be in the wireless_tools.26 when I type "make"

Nope, this time its from the directory that was created when you untarred 2635ADM8211.tar.

bitamois · 05-11-2004, 04:41 PM

would like you to run 'uname -r' just to check that the kernel you are running is the one you have the source to. It should be really since I doubt you have upgraded your kernel since you installed! But no harm in checking...
------------------------------------
typed
uname -r and got
2.4.22-1.2115.npt1
------------------------------------------------------

I dunno, but maybe you need a configured kernel source. In otherwords, go to your kernel directory and type 'make menuconfig' as root and then exit and save.

c. should be fine. You can check that the link exists by doing:
code:
--------------------------------------------------------------------------------
ls -l /usr/src

------------------------

I just typed
code:
-----------------------------
cd /usr/src
and then
code:
----------------------------
make menuconfig
-----------------------------

I got "Make: *** No rule to make target 'menuconfig' . Stop."
-----------------
typed
code:
--------------------------------
l /usr/src
------------------
I got
-----------------------
total 4
drwxr-xr-x 7 root root 4096 May 10 16:17 redhat

Muzzy · 05-11-2004, 05:03 PM

What is the output of

Code:

ls -l /usr/src

? I didn't understand the last post. Are you sure that you have the kernel sources installed?

Time for bed again!

bitamois · 05-11-2004, 05:20 PM

no, I'm not sure I have the kernel source. How do I know?

Muzzy · 05-12-2004, 10:49 AM

Post: ls -l /usr/src

If you have a directory there called somthing like linux-2.4.22 then you have the source. Don't confuse the directory for the link called linux-2.4, which should be pointing to it.

bitamois · 05-12-2004, 02:33 PM

I type at the root directory
-------------------
ls -l /usr/src

and I get:
---------------------------------
total 4
drwxr-xr-x 7 root root 4096 May 10 16:17 redhat

bitamois · 05-12-2004, 02:44 PM

Also, If I cd into
/usr/src/redhat/SOURCES

I type
ls
I don't see anything.

bitamois · 05-12-2004, 02:48 PM

I was reading the Redhat manuals last night that said the "linux" directory doesn't exist in Redhat. Instead it is
/usr/src/redhat

Muzzy · 05-12-2004, 03:41 PM

Well that is definitely the problem!

I am not sure what the best way for you to do this is. I would definitely NOT recommend moving any files around because it might break some Red Hat stuff, I have no idea what sort of strange things Red Hat gets up to...

What you might be able to do is make a link, so that the files appear to be in both places at once. You can do this without modifying any existing files. To do this, first you need to find the right directory. The directory probably contains a file called REPORTING-BUGS, so you could search for that file:

Code:

$ locate REPORTING-BUGS

If no results are returned, it might be because your locate database is not up-to-date, so try doing updatedb as root first (this will take some minutes), then run the locate command again. If you still get no results, it's because the file doesn't exist.

The path you need is everything between the first and last slashes, inclusive /usr/src/...../, which I will refer to as /path/to/your/sources/ form now on, but you need to type in the correct path! Check that you have the right path:

Code:

$ ls /path/to/your/sources/
COPYING        Makefile        System.map  include  lib          scripts
CREDITS        README          arch        init     mm           vmlinux
Documentation  REPORTING-BUGS  drivers     ipc      net
MAINTAINERS    Rules.make      fs          kernel   patches.txt

(actual contents of this directory could vary slightly)
Now create a link to this directory:

Code:

ln -s /path/to/your/kernel/sources /usr/src/linux-2.4

Then check your link is working:

Code:

$ ls /usr/src/linux-2.4/
COPYING        Makefile        System.map  include  lib          scripts
CREDITS        README          arch        init     mm           vmlinux
Documentation  REPORTING-BUGS  drivers     ipc      net
MAINTAINERS    Rules.make      fs          kernel   patches.txt

Now, if you got all that working, go back to compiling your driver!

Muzzy · 05-12-2004, 03:49 PM

Just noticed that you posted this:

Quote:

Also, If I cd into
/usr/src/redhat/SOURCES

I type
ls
I don't see anything.

So I think you need to download your kernel sources, or install them from your CD, then once you have done that, my previous post applies.

bitamois · 05-13-2004, 10:31 AM

Hi Muzzy,

I started a new thread (see RH9 2.4.22 kernel source install trouble)

This appears to be a separate and unrelated problem. I will return to this problem when I get this sorted out.

Thanks again.

bitamois · 05-14-2004, 03:34 PM

Hey hey,

I got it!

It turns out I had to install gcc32 and the kernel source.

I followed the directions in step 5. I am past 5! Woo hoo!

During the compile it did warn me about tainting the kernel. Darn it I meant to copy and include it in this before rebooting, sorry. I think it was just informational.
---------------------------------------------------------
5. If you get the source code and you want to compile it by yourself.
a. Install wireless-tool by yourself.
(We recommand wireless-tools-25)
b. Make sure you have the kernel 2.4.x source code.
c. You can modify the Makefile to fit your enviroment. We recommad
you make a soft link linux-2.4 of kernel source in /usr/src/
eg. If you had kenrel source linux-2.4.20 in /usr/src/
type "ln -s linux-2.4.20 linux-2.4"
d. Type "make"
e. The file 8211.o is the ADM8211 linux driver
f. "insmod 8211.o" to test your linux driver
(If you encounter some error messages, please try "insmod -f 8211.o")

-------------------------------------------------
I may need help with the final step.

I am rebooting.
------------------------------------------------

6. Reboot your system and use the command "netconfig" to configure your
network.You may need start network using "/etc/rc.d/init.d/network start" to take effect.
You can use either iwconfig or kwifimanager(In KDE) to setup up your
wireless lan.
---------------------------------------------------------------

Thanks again, Muzzy. I counldn't have gotten this far without you!

Steve