I got a question, how do i create the device wlan0, or where is it in slackware. I installed the linux-wlan-ng, then i tried to do iwconfig wlan0, it is not there, when i do cat /proc/net/dev, there isn't the wlan0, only the lo and eth0. so can anyone tell me how? thanks

See if the module is loaded. I suspect prism2_plx possibly. I am still new to the wireless stuff myself, the last few days. (lsmod) Hotplug may have loaded it.

Then I found I needed to run script in /etc/wlan directory called /etc/wlan/wlan if I recall correctly. Then the wlan0 device will show up.

I think I also had to create a default config file in the /etc/wlan directory for ESSID of the network I setup. This file also configures the channel and the mode, managed or adhoc, etc.

I do not think I really used the iwconfig at all for the prism drivers.

/Edit: (For my LinkSys pc card I had to download the older drivers from last December I think it was. Something about Intersil support, but the latest drivers wouldn't even see my card. ) This turned out to be in reference to the Atmel drivers for USB devices. Not the prism2 drivers.

I will be installing a LinkSys PCI tonight in a Slack 9.0 machine. So I may be able to assist more in a little while, or at least post back on what I had to do.

well, in my /etc/wlan/ directory, i only have shared, wlan.conf and wlancfg-DEFAULT, i don't have /etc/wlan/wlan, so i dunno what to do, my problem right now is just can't bring the wlan0 out, but someone i got the eth1 out, and i dunno what to do with that, when i run . /etc/rc.d/rc.inet1, it says:

root@punkshark:/etc/wlan# . /etc/rc.d/rc.inet1
SIOCADDRT: File exists
Configuring eth0:
ifconfig eth0 192.168.1.16 broadcast 192.168.1.255 netmask 255.255.255.0
Configuring eth1:
ifconfig eth1 192.168.1.1 broadcast 192.168.1.255 netmask 255.255.255.0
SIOCSIFADDR: No such device
eth1: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth1: unknown interface: No such device
SIOCSIFNETMASK: No such device

so right now i dunno what i am suppose to do

I had to edit my prior post, I am getting the different drivers confused. Please reread the earlier post.

The wlan-ng script turned out was in the /etc/pcmcia directory and that was because it was a pc card device.

In the README file of the source tree is description of the commands that need to be run to activate the driver if it is loaded. It uses /sbin/wlanctl-ng for the _pci/_plx/_usb driver modules. They do not use the wlan-ng script. This file also states about not using iwconfig with wlan-ng drivers.

My LinkSys PCI card has not loaded the prism2 drivers at all. So I need to do some searching for some support. My LinkSys pc card used the prism2_cs drivers. My other device I have is a Netgear USB wireless device that is supposed to be based on the Atmel chip. No luck with those drivers either as yet. The pc card on the prism2_cs drivers are working great.

Have the prism2_pci or prism2_plx drivers loaded for your card?

i don't have a adapter, i just have the regular simple pci, so i don't need glx (i think) when i do modprobe orinoco_pci, it says:

modprobe orinoco_pci
/lib/modules/2.4.20/kernel/drivers/net/wireless/orinoco_pci.o: init_module: No such device
/lib/modules/2.4.20/kernel/drivers/net/wireless/orinoco_pci.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20/kernel/drivers/net/wireless/orinoco_pci.o: insmod /lib/modules/2.4.20/kernel/drivers/net/wireless/orinoco_pci.o failed
/lib/modules/2.4.20/kernel/drivers/net/wireless/orinoco_pci.o: insmod orinoco_pci failed

i looked into the dmesg, but i don't get what it is talking about

so am i suppose to use linux-wlan-ng or not? right now, i use orinoco, linux-wlan-ng, and wireless_tools

Well my LinkSys wireless PCI card is worthless! The "lspci" command reported a Broadcom BCM4301 802.11b NIC card. From what I can find out so far there is NO support and will NOT be any support or information given from Broadcom. There appears to be a petition regarding the chip to encourage Broadcom to open the interface specs.

So your SMC PCI card might be a good alternative, if the modules load.

Try "modprobe prism2_pci". It it doesn't report any error messages, then do "dmesg" to see what is reported, if the driver detects the card.

yes the driver detects the card, but when i try modprobe the prism2_pci, it is like the orinoco_pci, it says:

root@punkshark:/etc/wlan# modprobe prism2_pci
/lib/modules/2.4.20/net/prism2_pci.o: init_module: No such device
/lib/modules/2.4.20/net/prism2_pci.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20/net/prism2_pci.o: insmod /lib/modules/2.4.20/net/prism2_pci.o failed
/lib/modules/2.4.20/net/prism2_pci.o: insmod prism2_pci failed

Please explain what you mean by "yes the driver detects the card" because the messages you posted would state otherwise.

I went to smc.com and they had an excellent 9 MByte photo of your card. I could clearly read the chipset on it. Please use the "lspci" to list your PCI adapters to confirm. The photo depicted an ADMtek ADM8211 chip. So you might want to review the following link that turned up when I googled for support on it.

http://www.hpl.hp.com/personal/Jean_...rs.html#ADMtek

here a screen shot in the kde info centerhttp://www.geocities.com/babysharkeater/snapshot2

oh and i forgot, when i do /sbin/lspci -v:


00:0e.0 Network controller: Linksys: Unknown device 8201 (rev 11)
Subsystem: Standard Microsystems Corp [SMC]: Unknown device 2602
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at b800 [disabled] [size=256]
Memory at d9000000 (32-bit, non-prefetchable) [disabled] [size=1K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [c0] Power Management version 2


this is the one

The screenshot is only depicting the same info that the lspci command does. They are just displaying in a GUI form. This indicates that the card is installed and that Linux sees it on the PCI bus. Not that any drivers are loaded or any other support is provided. Merely that it exists and the info is helpfull for identification.

im trying to rebuild my kernel without any PCMCIA support and enable the PCI i need, but what is this error when i tried to make bzImage, i don't know which option is the wrong one i checked:

init/main.o(.text.init+0x80b): In function `do_basic_setup':
: undefined reference to `init_pcmcia_ds'
make: *** [vmlinux] Error 1

wait, so the driver is setup wrong? can u explain it to me with newbie language, :-P, im not good @ networking stuff

Well, I would suspect that after the config is done that you need to do proably make clean and make dep. I think another part of the system is looking for the disabled option and it needs to know that it has been disabled.

From the link in my prior post post (page dated Mar2003) and attempting to google for adm8211.tar.gz not providing any locations available for the driver I have to conclude that the driver is not available yet. Except perhaps for limited Redhat binary on special request. You might consider sending them an email and see if they will provide something for the card.

I also searched over the SMC web site to see if I could locate anyting that might be new but was unable to locate anything. I havn't looked at the ADMtek site though.