I dont think linksys cares too much about linux--maybe in a few months the drivers will be built into the system

I think your right about linksys, not caring for Linux users. I have been emailing them for Well over a week now , with no response.

Ok, heres what I got when I ran- [root@localhost root]# /sbin/cardctl ident
Socket 0:
product info: "Realtek", "Rtl8139"
manfid: 0x0000, 0x024c
function: 6 (network)

I can't get the card to fully connect to the AP. Here is the relevant output from my /var/log/messages.

Nov 23 12:11:26 localhost kernel: ******** RTL8180 Wireless Lan Driver 2003-10-17 loaded********
Nov 23 12:11:26 localhost kernel: RTL8180: 05:00.0: region #0 IS a PIO resource!
Nov 23 12:11:26 localhost kernel: RTL8180: request_region(0x00004800,0x00000100) !
Nov 23 12:11:26 localhost kernel: RTL8180: Turn on RTL_DDEBUG_OUTINFO
Nov 23 12:11:26 localhost kernel: RTL8180: Using RTL private command [ssid]
Nov 23 12:11:26 localhost kernel: RTL8180: RTL8180: Set AP mSsid = <network ssid>
Nov 23 12:11:26 localhost kernel: RTL8180: Using RTL private command [ssid2scan]
Nov 23 12:11:26 localhost kernel: RTL8180: Using RTL private command [networktype]
Nov 23 12:11:26 localhost kernel: RTL8180: Using RTL private command [wepmode]
Nov 23 12:11:26 localhost kernel: RTL8180: Set wepmode = OFF
Nov 23 12:11:27 localhost kernel: RTL8180: ------ Enable wlan driver ------
Nov 23 12:11:27 localhost kernel: RTL8180 WLAN driver version 1.4
Nov 23 12:11:27 localhost kernel: RTL8180: wireless LAN controller RTL8180 + philips RF.
Nov 23 12:11:27 localhost kernel: RTL8180: PHILIPS_Config()
Nov 23 12:11:27 localhost kernel: RTL8180: PHILIPS_Config() - Analog mode
Nov 23 12:11:27 localhost kernel: RTL8180: Set dot11PrivacyInvoked = 0.
Nov 23 12:11:27 localhost kernel: RTL8180: encryptmode = RTL_ENC_NONE
Nov 23 12:11:27 localhost kernel: RTL8180: wepkeymode = WEP_MODE_OFF
Nov 23 12:11:28 localhost kernel: RTL8180: Select a BSS and Join it at channel 6.
Nov 23 12:11:30 localhost kernel: RTL8180: Join Request Timeout 1 times. Select another BSS to Join.

Instead of getting the wlan0 connection status, I see the bolded message. It repeats the Select a BSS and Join Request Timeout over and over until I disable the wlan0 interface.

While this is occurring, here is the output from /proc/rtl8180/status:

$ cat /proc/rtl8180/status
---------------------------------------
Driver status
---------------------------------------

rtl8180_pci_driver version 1.4 loaded.
The Network is configured as Infrastructure mode.
MacAddr = 00:09:5b:22:17:27
ioaddr = 0x4800
irq = 11


---------------------------------------
Wireless Link status
---------------------------------------

Link Fail!

Channel number = 6
beacon period = 100
BSSID = 0x00 0x30 0x65 0x02 0x78 0xc4
SSID = <network ssid>
Capability = 0x01
AID = 0x00
Operational rates = <1><2><5.5><11>Mbps
Current TX operational rates = <1>Mbps
--
While it is trying to connect to the AP, the Link light on the card flashes three times, pauses for a couple seconds and flashes three times, over and over.

I also run Windows 2000 on this laptop and as near as I can tell the settings between Windows and Linux match, yet the card works in Windows. It obviously can see my AP, it just doesn't get the link to it.

I set up the wlanup as a startup script, but here are the relevant parts from it (iwpriv stuff).

/etc/sysconfig/wlan (gets sourced by /etc/init.d/wlan)
SSID=<network ssid>
WEPMODE=off
NETWORKTYPE=infra
CHANNEL=6

/etc/init.d/wlan
# If the modules aren't loaded, load them.
lsmod | grep "^rtl8180_24x" 2>&1>/dev/null
if [ $? != 0 ]; then
insmod /lib/modules/`uname -r`/wlan-ng/rtl8180_24x.o 2>&1>/dev/null
fi
lsmod | grep "^priv_part" 2>&1>/dev/null
if [ $? != 0 ]; then
insmod -f /lib/modules/`uname -r`/wlan-ng/priv_part.o 2>&1>/dev/null
fi
# Turn debugging messages on
iwpriv wlan0 msglevel 1
# Settings for the WAP.
iwpriv wlan0 wlan_para ssid=$SSID
iwpriv wlan0 wlan_para ssid2scan=$SSID
iwpriv wlan0 wlan_para networktype=$NETWORKTYPE
iwpriv wlan0 wlan_para wepmode=$WEPMODE
# Enable the interface
iwpriv wlan0 enable
# This interface should be configured via DHCP:
# Disabling until wlan0 connects to AP
#sleep 10
#dhclient wlan0 2>/dev/null
--
The access point doesn't have WEP enabled, it is configured to channel 6, DHCPd and DHCP(client) enabled. There is a network password but as near as I can tell that is just to administer the device. The most frustrating part is that it works just fine in Windows, and that it sees the SSID and MAC for the AirPort. I've tried authtype={sharedkey|opensystem|both} and none of those options worked. I've tried making up new wlan_para-meters and those didn't work either .
--
Wireless card: Netgear MA521
Access Point: Apple Airport Base Station (Snow)
Linux distribution: Red Hat 9
Experience level of user: Advanced / Guru (just not with Wireless - yet...)

Actually it was realtek I contacted, they are the ones that are releasing the code as far as I know. I don't think Linksys is going to be the one to release a new driver.



From: "Ann Yeh" <ann@realtek.com.tw>
To: "'David Phillips'" <david@dcphillips.net>


Dear Sir,
Thank you for your e-mail.

The current driver didn't support Kernel 2.6.X now. It will be released
near future.


-----------------------------------------------
(Realtek Semiconductor Corp.)
Sincerely Yours,
Ann Yeh (¸_¿P©g)
Technical Support Engineer
Tel: (O) 886-3-5780211 ext:3834
Fax: 886-3-5776598
---------------------------------------------
Please include ALL previous mail when
Sending replies. Thank You!!!


-----Original Message-----
From: David Phillips [mailto:david@dcphillips.net]
Sent: Thursday, November 20, 2003 10:36 AM
To: nicfae@realtek.com.tw
Subject: rtl8180

Hi,

I have a Linksys WPC11 ver4 with the 8139 chip

product info: "Realtek", "Rtl8139"
manfid: 0x0000, 0x024c
function: 6 (network)

I am using the rtl8180_24x driver with the 2.4 Linux kernel.

Can you tell me if there is a way to use the card with the 2.6 kernel?

What is the status being able to obtain the driver source so I can build

it myself?

Thanks,

David Phillips

Kewl, thanks for all your help. Still havent gotten it to work. But , will work on it. until i figure it out, and get it working, even though Im getting alittle discouraged. But will continue to work on it. Thanks, everyone for all your help.

my lspci


02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.: Unknown device 8180 (rev 20)
Subsystem: Linksys: Unknown device 0019
Flags: bus master, medium devsel, latency 64, IRQ 5
I/O ports at 4000 [size=256]
Memory at 20800000 (32-bit, non-prefetchable) [size=512]
Capabilities: [50] Power Management version 2



This is also what I had before getting it working.

I had to get cardbus working, pcmcia was working but cardbus support was not.

Monday I bought a Gigafast WF721-AEX and discovered when I opened the box that it was a Realtek. The README begins -

-- RTL8180 Linux driver version 0.1

The driver is verified in three linux kernel as follows:
rtl8180_rh71.o -> Red Hat 7.1 (kernel 2.4.2-2).
rtl8180_rh72.o -> Red Hat 7.2 (kernel 2.4.7-10).
rtl8180_rh73.o -> Red Hat 7.3 (kernel 2.4.18-3).
...

Even so, I have problems. I am a newbie. Very much.

I am on SUSE 8.2, kernel release 2.4.20-4gb. My biggest struggle right now is figuring out what the Gigafast is doing, or not doing, in its PCMCIA slot. The little green LED is out. I actually didn't notice that it has an LED until I read parts of this thread and looked for it! I don't think it has ever lit. At any rate, this card does not behave at all like my 3Com (3CXE589ET). Using some KDE applets for laptops (newbie, remember), I don't get a change in state for the slot when I remove the card. Remove the 3Com and the state of its slot updates nicely, reinsert it and -voila!- there it is again. But the Gigafast does not play nicely....

I am going to be reading about "rpm -ql pcmcia" but would appreciate any help right now, and thanks.

I finally got my Realtek 8180L-PCI to work (the pcimcia version should work too). A little howto:

After a fresh install of debian woody system I've got a 2.4.18-bf2.4 kernel. I think that the key is to compile kernel and drivers with exacly the same gcc version. So I compiled a 2.4.20 kernel on my own and after that i used a fresh makes kernel-headers to build a driver. It works!

http://www.debian.org/doc/FAQ/ch-kernel.en.html- instructions how to make own kernel under debian

and now step by step..
1. install debian system
2. install packages nedded to compile kernel and run drivers:
apt-get install kernel-package gcc libncurses5-dev wireless-tools unzip
(i may forgot about something)
3. download a linux-2.4.20 kernel source from http://kernel.org
4. untar it:
tar -zxf linux-2.4.20.tar.gz
5. go inside into kernel directory:
cd linux-2.4.20
6. configre your new kernel:
make menuconfig (for rookie: don't change anything in menu)
7. make your kernel and prepare kernel-image:
make-kpkg kernel-image kernel-headers
8. there should be a two debian packages maked, so simply install them as a normal packages
dpkg -i kernel-XXXX.deb kernel-headers-xxxxxxx.deb (the lilo should be automaticly updated, but i suggest to make a rescue disk)
9. reboot system.
-----------the kernel step is done, let's install the drivers---------
10. download a linux drivers from:
http://www.realtek.com.tw/downloads/...x?Keyword=8180

i've got a gcc-2.95, but the driver version for gcc 3,2 works,not a 2,96. -isn't it strange? - of corse the kernel version is more important than gcc at this point)

11. unzip drivers:
unzip rtl8180.......

12. go into drivers directory:
cd rtl8180......

13. now you must edit the Makefile and:
change the kernel version from 2.4.20.8 to 2.4.20
change the path to kernel-headers files from /usr/src/linux-[...] to /usr/src/kernel-headers-[...]

14. make the driver:
make

15. now you need to edit the wlanup file for your need (ssid2scan,and ip configuration mostly - you can use config files included earlier in the topic)

16. now pray to start the driver without 'kernel panic'
./wlanup

(if it start properly you should be able to ping the accesspoint)

17. now you need to set a 'default gateway' in your rooting table:
route add default gateway <gateway ip>

18. now prepare a startup script and enjoy ))

<<thanks to vercan for a good idea - he did it as first one>>
If there are errors in my howto please correct me..

Hi,

did anyone get the driver work with kernel 2.4.22/sid?
It compiles fine, but when I insmoded the module and try to enable the card (iwpriv wlan0 enable), iwpriv says that enable is an
invalid command. The other commands in the wlanup-script are also invalid commands.

iwpriv wlan0 says the following:

wlan0 Available private ioctl :
ºs@Ø? (BFFFF050) : set 572 (null) & get 0 int
hz
@ (40052060) : set 1088 byte & get 4 int
èðÿ¿¿? (40017054) : set 1480 & get 4
p
@ (80484F8) : set 164 (null) & get 2047
¸n
@ (7A5A1C4) : set 288 (null) & get 2047
? (0000) : set 1152 addr & get 1 int

(40017054) : set 1368 (null) & get 1 int
àd
@þÿ¿hñÿ¿Ð» (4004BD40) : set 0 & get 0
ðá@¸n
@(
(0000) : set 1 & get 0


maybe a memory allocation error, but ifconfig works fine:

wlan0 Link encap:Ethernet HWaddr 00:40:F4:93:15:A0
inet addr:192.168.1.25 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
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:9 Base address:0x4000

Btw, I got the card running under knoppix 3.2, the ap is detected but after some time swapper causes a kernel panic.


Thanks

bjo

Has *ANYONE* had *ANY* success with Mandrake? This is my experience with 9.2:

After making sure that I have the best source available from Realtek, I fixed the makefile so it compliles correctly. You dont use /usr/src/linux anymore.. you use /lib/modules/(uname-r)/build/include for all your includes when developing a module. BAD things happen with your build if you dont.

All I got a was a hand-grenade.

Putting liberal amounts of printk's into the available source shows that the module init goes down a rat-hole into Realtek's "private" section of initialization code. Using objdump shows (in assembly) where it disappears, but who really likes digging through ASM unless the REALLY have to.

On INSMOD bad things happen - a total kernel shutdown. This is always manifested by the kernel going into a tailspin die loop, leaving behind it's standard obituary of blinking keyboard lights.

Obviously the author tied himself to a struct (I saw the previous posting on that) that is not static with each distro and kernel build.

This is where I start to rant. I am an engineer who has personally put Linux into embedded systems. I have written modules to talk to hardware, so I'm perfectly capable of either fixing or writing from scratch a driver module. My beef is why the hell does hardware manufacturers have this sudden urge to obfuscate their interfaces and commands from the world. They make silicon - they dont do software. Their only responsibility to the manufacturers that design products using their chipsets is to provide a reference driver set, which we seem to have given. But that "private part" is where we are all experiencing our problems. If they would simply give us the source for that, the our problems would be over and we would be out happily buying their product and recommending it to other users.

But I am seeing more and more (like the dreaded TI ACX100) where the chipset mfgr wants to own the whole boat. Guys, the world doesnt revolve around windows anymore - a lot of corporations and governments are switching to open source. My best advice (and is is addressed to any manufacturers or reps that might be reading this rant) is to stop this trend or get designed out.

I got an ADM8211 -based dlink card working beautifully (Thanks ADMtek, but you are still guilty of trying to make your stuff propreitary), but I still am out $40 bucks on the Linksys and would like to do something with it rather than use it as a paperweight.

Ok - I'll shut up and quietly take my flaming.

Anybody having any success tracking down the private part / kernel discrepency?

henchmenlabs,

I like your rant . If the Netgear MA521 I'm trying to configure just plain worked, I would totally recommend it to people all over the place. However, it doesn't.

A coworker and I have been poking at the strings and symbols of the priv_part object and haven't found *too* much, but the module was compiled against kernel version 2.4.20-8 (the default base kernel for Red Hat 9). We're going to hack at it some more next week and see if we can find an answer to my particular problem.

Hello,

I'm new to Linux and need help installing the WPC11 Ver.4.
I'm running SuSE 8.2 with Kernel version 2.4.20.SuSE. Everthing I do does not work. Have tried the Drivers from Realtek but will not compile even after changing the Makefile kernel version. Help

Man, this thing Is driving me crazy. And not knowing , hardly anything about Linux. But wanting to stick with it. This card is driving me $#$#@#$ Crazy. I can see the rtl8180_24x.o Under ethernet devices, when I go to Internet connection config. But when I go to set up wireless, I don't see anything. Whats going on? I have no idea. Does anyone know.? Any help would be greatly appreciated. Thanks, Everyone.

Also , when I have the card inserted into the PCMCIA slot, my laptop is fine. But when I remove it, I have lights flashing on the keyboard, and the pc doesnt respond. It's like it locks up. I have to , turn it off. And then back on. Does this mean anything? Was just wondering. If anyone had any , ideas on what this could be? Something done wrong on my part? Thanks, for any help , William.