Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi All. I have a compaq 17XL365 notebook dual-booting XP Pro and Red Hat 9. I just got the linksys wireless network B kit which comes with a card and router.
The card is the infamous wpc11, but it is version 4! With a little help I've discovered that the controller chip in this card is a realtek 8180L, realtek has driver binaries and source to download on their site, but I have two things going against me...
1. I can install and use Linux reasonably well, but I'm not real good at configuration or alteration outside of the initial install. I'm also kinda shakey doing stuff out of the GUI (read: not afraid, just inexperienced)
2. I am completely new to wireless networking.
Can anybody help me set up this card?
Also, one question to satify a curiosity, if I add a driver by means of an RPM, why if I use the GUI tools to set it up is the driver not listed. (ex. I added the prism2 drivers while attempting the get the card up and running, but using the red hat 9 network setup tool, the prisim2 driver was not listed in the drop down menu.)
The Realtek site has a binary precompiled driver for RH9.0, you just have to insmod it, now....
I've never done that, actually my experience with that card is about 2 hours a month and a half ago with some generic version of the chipset that I borrowed off a kid who had picked it up for ~$20USD in Seoul about a month before. I got it talking WEP for a few minutes and got bored with it. I had to compile it from scratch, which is what steven999 is what you're going to have to do too dude...
The precompiles for RH aren't going to swing into Mandrake just that easily. You'll have to have a compiler and your kernel source installed and make certain that you edit the top of the Makefile to reflect the name of your current kernel, post back if you get lost with it.
Also, all of the settings for it are a little weird, they use the "iwpriv" command for EVERYTHING, even turing the card on, which is a bit annoying. Its all in the README, which isn't that bad of a readme to be honest. There's also another thread in Hardware about this kid too, you might want to check some of that one out too.
Thanks for chiming in. I have been following the other message thread as well, and I've spent quite some time getting nowhere with this card, to the point where I'm actually booting into Win2K for the time being. (yuck.)
I had already compiled the driver with a modified Makefile to account for Mandrake's kernel version. I can insmod it in and lsmod will show it's loaded. depmod -a will say there's missing symbols however.
Using the default wlanup script that comes with the driver didn't get it to work, unfortunately. If I dhcpcd wlan0, my computer crashes and I have to reboot. I'm using a Thinkpad T23, and when I do the dhcpcd, I get some blinking lights and everything is frozen.
If I use ifconfig wlan0 I do see it bound to the right memory address that's reported from lspci.
I do get some strange messages when I dmesg about the driver not being AP or something. I'm not that familiar with wireless cards, so it's eluded me a bit. I also get a message about something regarding PIO and #0.
I'll post more information later when I get to my laptop and get the logs and configuration files off of it.
Okay, I tried that out and got about as far as I ever get. If I do ifconfig wlan0, i get:
wlan0 Link encap:Ethernet HWaddr 00:06:25:2B:B2:5E
inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x4000
(I set the address to 192.168.1.105 instead of 101)
from running dmesg, during bootup I got:
******** RTL8180 Wireless Lan Driver Version 1.0 loaded when 00:35.08********
PCI: Setting latency timer of device 03:00.0 to 64
RTL8180: 03:00.0: region #0 IS a PIO resource!
RTL8180: STA is NOT acting as AP!
RTL8180: #define RTL_LITTLE_ENDIAN
RTL8180: rtl8180_pci_driver loaded. ioaddr=0x4000, irq=11, MAC_addr=0:6:25:2b:b2:5e
That command didn't work (along the lines of syntax error). I tried without the wlan_para and got:
wlan0 Available private ioctl :
senddata (89F3) : set 3 int & get 0
enable (89F4) : set 0 int & get 0
disable (89F5) : set 0 int & get 0
rtl_io (89F2) : set 32 char & get 0
sta_tbl (89F8) : set 16 char & get 0
wlan_para (89F6) : set 128 char & get 0
drv_para (89F7) : set 64 char & get 0
msglevel (89FA) : set 1 int & get 0
set_by_flash (89FB) : set 32 char & get 0
also, here's something I saw a couple days ago, but forgot about. I had redid my wlanup a little to add the infra, and when i ran it i got from dmesg:
RTL8180: Use RTL private command [ssid2scan]
RTL8180: Set ssid2scan = 0x6c(l) 0x69(i) 0x6e(n) 0x6b(k) 0x73(s) 0x79(y) 0x73(s)
RTL8180: Use RTL private command [channel]
RTL8180: Use RTL private command [networktype]
RTL8180: ------ Enable RTL8180 driver ------
RTL8180: Read CONFIG4: RTL8180 + RFMD RF.
RTL8180: Autoload RFChipID in EEPROM -> RTL8180 + MAXIM RF.
RTL8180: Scan PHY channel number = 1
RTL8180: Scan PHY channel number = 2
RTL8180: Scan PHY channel number = 3
RTL8180: Scan PHY channel number = 4
RTL8180: Scan PHY channel number = 5
RTL8180: Scan PHY channel number = 6
RTL8180: Scan PHY channel number = 7
RTL8180: Scan PHY channel number = 8
RTL8180: Scan PHY channel number = 9
RTL8180: Scan PHY channel number = 10
RTL8180: Scan PHY channel number = 11
RTL8180: Neither joining a BSS or starting an IBSS
I tried an experiment and pinged the IP i set for wlan0 and sent/received packets fine (don't know if that means a thing at all).
I'm going to take my laptop to work and try to tackle it there tomorrow. Thanks again for helping along with this!
That's good, this card needs to have its hand held through everything, so just not having tx errors trying to ping yourself means that its half-set-up-right. Try this set, maybe this will beat it senseless:
Hopefully that combination of mungy mess might give it something to latch onto, in the previous scan it looked but didn't find anything, but evidently this kid has to be told the exact name of the ssid to join, which is a bit tedious, but there seems to be 2 commands for that?!?
Okay, tried out all of those settings and got the same thing.
One thing to note: doing a make clean removes all .o files, including a file called priv_part.o. After doing that, I realized there's an open source part and a closed source part to this.
That got me thinking, the download was for redhat 8.0 and I don't remember if redhat 8.0 had gcc 3 series or if that was the release with the redhat special 2.96. I'm wondering now if the priv_part.o isn't binary compatible. I'm hoping I'm wrong about the 2.96 thing, but when I do do a depmod -a, I have been getting Unresolved Symbols in the rtl8180_24x.o.
Alright, I found that version.h in the kernel source in linux-2.4.21-0.13mdk/include/linux had #defined UTS_RELEASE to 2.4.21-0.13mdkcustom insted of 2.4.21-0.13mdk. I changed that and got the module to insmod fine. So I'm going back to trying other things.