Well, interesting about hotplug, because pci agent doesn't show up but net.agent does:

[root@localhost network-scripts]# grep pci.agent /var/log/messages
[root@localhost network-scripts]# grep net.agent /var/log/messages
Oct 31 19:43:32 localhost /etc/hotplug/net.agent: creating config file for eth0
Oct 31 19:43:32 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 08:30:04 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 11:21:52 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 11:44:37 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 11:51:48 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 11:58:28 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 12:18:04 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 19:40:01 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 1 20:03:32 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 2 11:20:34 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
Nov 2 11:38:47 localhost /etc/hotplug/net.agent: NET unregister event not supported
Nov 2 11:38:58 localhost /etc/hotplug/net.agent: invoke ifplugd eth0
[root@localhost network-scripts]#

Now that last boot is the one that included the iwconfig enc parameter in the script. It did not work: There was no error at boot, and the module loaded, but it didn't work with the password. I think it showed the password, but didn't work! AND it didn't let me do iwconfig to fix it until I unloaded and reloaded the module! It didn't actually see the access point. Perhaps I need to set more defaults -- I only set one parameter, because iwconfig eth0 normally only needs that one parameter (enc) set to run.

[root@localhost network-scripts]# cat ifcfg-eth0
DEVICE=eth0
ENC=2fd2b4xxxx
BOOTPROTO=dhcp
ONBOOT=yes

I would definitely put a CHANNEL= and an ESSID= in there ahead of ENC, which I would change to KEY=, and ahead of all those I'd put an IPADDRESS= as well, use a trash class c address that doesn't conflict w/anything else on your localnet, this chipset seems to be quirky like that and doesn't seem to want to accept iwconfigs reliably until it's got an ipaddress (well, sometimes at least...), the dhcpcd/dhclient/pump call will change it up for you anyway, so it does no harm.

Weird. I changed the ifcfg-eth0 file to include everything (note a couple of "secrets" are changed for illustration):

DEVICE=eth0
ESSID="WHATITSCALLEDGOESHERE"
CHANNEL=10
KEY=deadbeef00
BOOTPROTO=dhcp
ONBOOT=yes

Yet on boot, after a "taint" warning flies by (but no error), the network isn't up, and this is what I get:

[root@localhost user]# iwconfig eth0
eth0 IEEE 802.11-DS ESSID:"" Nickname:""
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Bit Rate=0kb/s Tx-Power=0 dBm Sensitivity:0/65535
Retry limit:3 RTS thr=2346 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

So it's obviously not taking. Nor can I iwconfig it at that point:

# iwconfig eth0 key 2fd2b4dc6p
Error for wireless request "Set Encode" (8B2A) :
invalid argument "2fd2b4dc6p".

However, on a running system:

[root@localhost]# modprobe -r 8211
[root@localhost]# modprobe 8211
Warning: loading /lib/modules/2.4.22-10mdk/kernel/drivers/net/8211.o will taint the kernel: non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Module 8211 loaded, with warnings

And then:

eth0 IEEE 802.11-DS ESSID:"WHATEVER" Nickname:"localhost"
Mode:Managed Frequency:2.457GHz Access Point: 00:09:5B:BE:EF:00
Bit Rate=11Mb/s Tx-Power=47 dBm Sensitivity:0/65535
Retry limit:3 RTS thr=2346 B Fragment thr=2346 B
Encryption key:DEAD-BEEF-00 Security mode:open
Power Management:off
Link Quality:95 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

And here I am. So apparently the module won't load right on boot but does later. I wonder if the "taint" is doing something bad.

I have the 8211/PCI card working on RedHat9.0, but it times out in about three minutes
after it's activates, you have to keep reactivating it , but it will stay up as long as your on the internet and not let it idle for more than three minutes.
I,m positive it's not a Power Management problem.
Where can you download the drivers for the 8211, other than admtek.com/tw and their
105.tar.gz file, I'm convinced there is a problem with their driver, Am I wrong?

Jim Tate

There are various *copies* of the admtek drivers on various manufacturer websites with various names and dates, though I've seen none yet that are actually different code.

Perhaps indeed you are correct, I have a PCI card of this implementation in my daughter's machine which dual boots win98 and slack 9.0, both os's exhibit quirky behavior with this card, although I must tell you, neither need re-activating every 3 minutes. The quirky-ness seems to be limited to getting the card "up" initially, after that all appears to be well. What are your iwconfig settings for the card?

As far as you being "wrong", since admtek hides code in the closed-source binary: "ADM_Prv.o" that gets linked in when you compile this module, it's impossible to say with any certainty without a rather expert de-compile of that file.

ADM8211 wireless extentions sequence
 

ADMtek has a newer version or source code. v1.05 some RPMs are compiled against v1.03.

I am interested in the working sequence of wireless extension for mandrake 9.1

Problems with ADM8211 in SuSE 8.1, too
 

Hi ,

I have one of the problems discussed in this group, too.

i use a WLAN-Card (NoName) with the ADM8211 chip. On booting the system the module 8211.o (V1.05) is loaded, and an 'iwconfig eth0' brings up the correct parameters inclusive the right encryption key. Now, when i send a ping to my laptop, i got the information that the computer is not reachable. On the laptop (Windows XP) i can see a signal (ping does not work) in the status window, so i guess the cards can 'see' each other. After setting the encryption key again by using iwconfig eth0 key 1234567890 , the card works and reaches the laptop. I read inside this forum that iwconfig needs the parameters in a specific order. Is this the trick i have to consider and could someone post this order?

Many Thanks for your help

Thomas

can't compile at all theses drivers 8211 on mandrake 9.2
 

Please....can anyone know why this makefile for the admtek (1.05) 8211.c always fails on:

In file included from adm8211.c:31:
/usr/src/linux-2.4/include/linux/module.h: At top level:
/usr/src/linux-2.4/include/linux/module.h:301: error: syntax error before "UTS_RELEASE"
adm8211.c:1786: warning: implicit declaration of function `__devexit_p'
adm8211.c:1786: error: initializer element is not constant
adm8211.c:1786: error: (near initialization for `adm8211_driver.remove')

I have made a lot of tries in order to make this code to compile fine, but always unsuccesfully. I have downloaded the kernel sources and make various symlink.
I am using a Toshiba laptop with a PCMCIA board with mandrake 9.2

Thanks.

I get that allot, scrapped 9.2 and i am using fedora worked in 2 minutes,

I'm using Fedora what did you do to get it to work?

Ok Hang on mate go a minute??

The source code seems buggy so i gave up on it and i am using NDISWRAPPER
http://sourceforge.net/projects/ndiswrapper/

which doesnt seem to work in 9.2

next goto the admtek website where you got the source code and download the windows drivers for the card. extract them to a folder.

Log in as Root, have the readme and install files open in a text editor you will need them...after your have extracted the ndiswrapper to a folder do these things that i did and see if it works. The make process for the ndiswrapper asks you for the paths to your windows sys and inf files

in a terminal window

cd ndiswrapper
make
insmod drivers/ndiswrapper.o
cd utils
make
cp /usr/sbin/loadndisdriver

next flick back to the install file and locate the lspci line to get your vendor ID numbers copy and paste that string into the terminal window

it will give you two numbers like so the first block of four is Device ID and the is Vendor ID

xxxx:yyyy

next command

loadndisdriver xxxx yyyy /lib/windrivers/aaaa.sys /lib/windrivers/bbbb.inf

substitute with your sys and inf names and product and vendor numbers.

More to follow this should get you up and running .....

If you dont know VI editor , press INS to be able to edit stuff then Press ESC when you are done ... it will sit there and wait type in :wq and it will save and exit. we need to get it going every boot up...

in the terminal

vi /etc/sysconfig/network-scripts/ifcfg-eth1

# YOUR WIRELESS CARD NAME HERE
# These settings are from the way I configured my wireless router
DEVICE=eth1
BOOTPROTO=dhcp
onBOOT=yes
TYPE=Wireless
ESSID=SMC
KEY=WHATEVER
CHANNEL=1
GATEWAY=192.168.1.1

exit VI editor

type in terminal
iwconfig (look for your wlan card)
iwconfig eth1 mode Managed
iwconfig eth1 key WHATEVER
iwconifg eth1 essid WHATEVER
ifup eth1 (I got an error but then it said '... done' and I knew)
ifconfig (make sure it is in the list)
ping 192.168.1.1 (when this worked I instantly went to google.com to make sure that it was working and Viola! it was)

Now we still need to make it work after we reboot.

I currently do this by issuing the following in /etc/rc.d/rc.local

ifdown eth1
rmmod ndiswrapper
insmod /root/ndiswrapper/driver/ndiswrapper.o
loadndisdriver xxxx yyyy /lib/windrivers/aaaa.sys /lib/windrivers/bbbb.inf
ifup eth1

if something goes wrong at any stage after this just type ifup eth1 in the console..

configured two of these now... the second one choose eth0 as default so try substituting eth0 for eth1 if you are having troubles.

also get kwifi manager

all of this thanks to a quick search using ndiswrapper in these forums...

Yraens69, I setup as per your instruction but I can't get the ADMtek PCI card to
work as eth0, It appears to want to setup as wlan0 and that still won't work.
I'am using Fedora core1

I did dmesg and this is what I get which it inicates it is reading /etc/rc.d/rc.local, I guess.

Ndiswrapper Version 0.4 Loaded
PCI: found IRQ11 for device 00:06.0
PCI: Sharing IRQ11 with 00:10.0
WLAN0: ndiswrapper eathernet device 00:e0:98:af:39:40
Divert: allocating divert_blk for WLAN0
MTRR: No more MTRR's available
MTRR: No more MTRR's available
MTRR: No more MTRR's available


The Device 00:06.0 is Network Controller : linksys: Unknown device 8201 (rev 11)
The Device 00:10.1 is a USB controller.

/sbin/iwconfig , WLAN0 IEEE 802,11b ESSID:"linksys-g"
MODE: Managed Frequency:2.437ghz
Access Point: 00:90:4b:28:d8 6f
Bit rate=11mb/s TXPower:28dBm
Sinsitivity-0/3 RTS thr=2346 B Fragment thr=2346 B
Power Managment:off
Link Quality: 100/100 Signal level: 66/154 Noise level 0/154

/sbin/ifconfig , comes up with lo only, I don't have a eth0

Got any ideals

Jim Tate http://www.linuxquestions.org/questi...readid=108531#

I DID IT!!!
I went into /etc/modules.conf and
modified to read "alias wlan0 ndiswrapper" and then it picked up the device.
But, Why wlan0, instead of eth0?

Finally!!
Thanks to all

Jim Tate