wireless rtl80211

Message

proficus · #1 Post by **proficus** » Fri 02 May 2008, 06:18

If it's not too late..

I have wireles pci adapter with Realtek chipset 8185,
and network connection does not work with wep encryption, might be the problem is with current 80211 drivers.
Would it be possibe to include latest 8185 drivers?

http://www.realtek.com.tw/downloads/dow ... loads=true

p.s.
Puppy rocks!

still using $%indows for internet due to the above problem..

tempestuous · #2 Post by **tempestuous** » Fri 02 May 2008, 07:04

First, it would be useful to know what version of Puppy you're talking about. There are big differences in kernels between the 2.x, 3.x and 4.x series, and differences in what modules are already available as add-on packages.

Since the r8180 module seems to be working for you without encryption, then it's probably just a problem of encryption-related modules not loading, which has been reported and discussed several times before. Please see "PART 4: Troubleshooting, encryption problems" section of the wifi HOWTO -
http://www.murga-linux.com/puppy/viewto ... 339#159339
The additional modules that you are likely to need using the r8180 with WEP are:

ieee80211_crypt_wep-rtl
arc4
ecb

proficus · #3 Post by **proficus** » Fri 02 May 2008, 07:35

Thanks for the hints.
I have already tried ieee80211_crypt_wep-rtl - no success.
I will try to put arc4 and ecb, and will provide the results.

I tried 3.95, and most current 3.99 (ftp://ibiblio.org/pub/linux/distributio ... monkey.iso)
(hard disk install)

Anyway, for me, after some years playing around with linux, it is still difficult to add new module, look for tips in forums, etc.
I would be happy to see it working out-of-the-box, just with net wizzard.

proficus · #4 Post by **proficus** » Fri 02 May 2008, 08:51

So, I have tried it. Maybe it is not just WEP problem, the iwlist does not show any network available.

Here are the details:

#ifconfig wlan0 down
#modprobe ieee80211_rtl
#modprobe r8180
#modprobe ieee80211_crypt_wep_rtl
#modprobe arc4
#modprobe ecb
#iwconfig wlan0 essid "Internetas 22"
#iwconfig wlan0 mode managed
#iwconfig wlan0 key s:vesta 1
#ifconfig wlan0 up

#ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:12:C9:57:15:35
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:332 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:18234 (17.8 KiB)
Interrupt:3 Memory:f8968000-f8968100

#iwlist wlan0 scan
wlan0 No scan results

#ifplugstatus wlan0
wlan0: unplugged

#dhcpcd wlan0
Error, wlan0: timed out
Warning, wlan0: using IPV4LL address 169.254.72.120

---
here I attached Windows working config:
Status: Associated BSSID = 00-90-D0-EB-9D-A7
SSID: Internetas 22
Wireless mode: Infrastructure
Encryption: WEP
Tx Rate: 36 Mbps
Channel: 1
Link quality 100%
Signal Strength 100%
Auth. mode: Open system
Encryption mode: WEP-Key
Key length: 64bits

tempestuous · #5 Post by **tempestuous** » Fri 02 May 2008, 09:18

A few suggestions:

Bring up the interface after loading all the modules, and before running the first iwconfig command. So after "modprobe ecb" do this

Code: Select all

ifconfig wlan0 up

proficus wrote:#iwconfig wlan0 key s:vesta 1

Does your WEP password really have a space in it? If so, I think you will need quotation marks like this s:"vesta 1".
Or better still, use the true WEP hex key instead of the WEP password. Sometimes the password fails to convert to the correct hex key.

proficus · #6 Post by **proficus** » Fri 02 May 2008, 09:44

Tried all suggested things - no luck.

It seems suspicious that iwlist wlan0 scan is performed very quickly (no real search for access points?)

Also iwconfig wlan0 commit does not work - "operation not supported". although dmesg shows no errors, regarding keyit shows "setting WEP key".

tempestuous · #7 Post by **tempestuous** » Fri 02 May 2008, 14:53

proficus wrote:I tried 3.95, and most current 3.99

I see you're using Puppy4 alpha/beta. Clearly the driver is not behaving, which is not surprising since Puppy's r8180 module is based on the deprecated rtl8180-sa2400 source code (heavily patched).

Puppy4 final is about to be released, with 2 kernel versions available.
I think that the r8180 module in the older 2.6.21.7 kernel should work OK, so I suggest you get this version.

In the long term, the latest "rtl-wifi" r8180 module will need to be compiled for Puppy4's 2.6.25 kernel, and maybe this will get a better result.

proficus · #8 Post by **proficus** » Fri 02 May 2008, 21:46

Puppy4 final is about to be released, with 2 kernel versions available.
I think that the r8180 module in the older 2.6.21.7 kernel should work OK, so I suggest you get this version.

I see that current 3.99 version has the 2.6.21.7 kernel (at least my uname -r says so).

I will try to compile newer rtl drivers (provided by Realtek) when kernel source for the Puppy 4.0 is available.

tempestuous · #9 Post by **tempestuous** » Sat 03 May 2008, 03:59

proficus wrote:I see that current 3.99 version has the 2.6.21.7

I'm losing track of the different vesions available. Now at least we know that you are using the Puppy4 "retro" kernel - the same as Puppy3 - and not to be confused with Puppy3-retro!!.
Let's sort this out: I had been assuming that your wifi adaptor works WITH NO encryption, and fails WITH encryption.
But now I see I may have misinterpreted your earlier information, and maybe the device has never succeeded at all, even without encryption?

proficus wrote:I have wireles pci adapter with Realtek chipset 8185

Ah, the 8185 chipset, that's significant. There are several 8185 PCI ID's not defined in the old Realtek source code ... I don't suppose your PCI card is the Belkin F5D7000 v7?

I have just recompiled the r8180 driver - the same (old) version that Puppy currently has, but with source code patched to properly define the Belkin F5D7000 v7 (PCI) and F5D7010 v7 (Cardbus) devices. Available here -
http://www.murga-linux.com/puppy/viewto ... 470#144470
I suggest you install this revised driver and try it.
If still no success, try the alternative "rtl-wifi" drivers in that same post.

If still no success, wait for Puppy4 with the 2.6.25 kernel. 2.6.25 has a new type of wifi subsystem, "mac80211", which the new rtl-wifi drivers are designed to work properly with.

proficus · #10 Post by **proficus** » Sat 03 May 2008, 07:44

No, my card is not Belkin.
It is Trendnet TEW-432PI

I'll wait for the new version.

Big thanks for the attempts to help!

tempestuous · #11 Post by **tempestuous** » Sat 03 May 2008, 10:59

OK, I give up on the old opensource driver.
I just compiled the proprietary version from the Realtek website, now attached to the same post as before -
http://www.murga-linux.com/puppy/viewto ... 470#144470
I can say that the proprietary code, and the resultant modules, look almost identical to the "rtl-wifi" versions, which are the NEW opensource versions.

proficus · #12 Post by **proficus** » Sun 04 May 2008, 05:37

With the latest proprietary driver:

Code: Select all

#iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:90:D0:EB:9D:A7
                    ESSID:"Internetas 22"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:1
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
                    Quality:0  Signal level:0  Noise level:158
                    Extra: Last beacon: 40ms ago

In Network wizzard, all steps say OK, however dhcpcd does not acquire IP address.

Code: Select all

#dhcpcd wlan0
Error, wlan0: timed out
Warning, wlan0: using IPV4LL address 169.254.3.158

And the autoconnect.sh hangs my PC.
One try hanged it on the following:
"pass 2. check TITLE 1 -> 00-90-D0-EB-9D-A7
using profile inetas"

(the MAC and profile names are from the Network configuration wizzard).

Another time it hanged on pass 2. Check TITLE 3, when "Saving profile" 33% message was popping up.

p.s. I don't know how to provide debugging info.

tempestuous · #13 Post by **tempestuous** » Sun 04 May 2008, 13:09

Forget about the 2.6.21 kernel. The Realtek source code is clearly unreliable with this older kernel.
Grab Puppy-4.00-k2.6.25. It's currently at "sanity check" stage and available here
http://distro.ibiblio.org/pub/linux/dis ... py-4.00rc/
The final version should only be a day or two away.

I just checked, and the Realtek driver is included. It's now called "rtl8180" not "r8180" as before.

proficus · #14 Post by **proficus** » Mon 05 May 2008, 06:49

Dmesg shows some error, and dhcpcd does not acquire IP address.
All other things seem to be working.

p.s. What wireless pci card (brand, model) would work without problems?

Code: Select all

# dmesg | tail
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:eb:9d:a7
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: authenticate with AP 00:90:d0:eb:9d:a7
wlan0: authenticate with AP 00:90:d0:eb:9d:a7
wlan0: authentication with AP 00:90:d0:eb:9d:a7 timed out

# dhcpcd wlan0     
Error, wlan0: timed out
Warning, wlan0: using IPV4LL address 169.254.204.189 

---


# lsmod

ieee80211_crypt_tkip    11520  0 
ieee80211_crypt_ccmp     7808  0 
ieee80211_crypt_wep     6016  0 
ieee80211              35656  0 
ieee80211_crypt         7044  4 ieee80211_crypt_tkip,ieee80211_crypt_ccmp,ieee80211_crypt_wep,ieee80211
rtl8180                31616  0 
mac80211              132492  1 rtl8180
cfg80211               19848  1 mac80211
eeprom_93cx6            3200  1 rtl8180

# ifconfig wlan0 up
# iwconfig wlan0 essid "Internetas 22" ap 00:90:D0:EB:9D:A7 key 7665737461
# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:264 (264.0 B)  TX bytes:264 (264.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:14:D1:48:FE:FE  
          inet addr:169.254.204.189  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST 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:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wmaster0  Link encap:UNSPEC  HWaddr 00-14-D1-48-FE-FE-00-00-00-00-00-00-00-00-00-00  
          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:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

# iwconfig 
lo        no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"Internetas 22"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:90:D0:EB:9D:A7   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:7665-7374-61
          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

# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:90:D0:EB:9D:A7
                    ESSID:"Internetas 22"
                    Mode:Master
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Signal level=19/65  
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:tsf=0000005b8c02c188

[/code]

tempestuous · #15 Post by **tempestuous** » Mon 05 May 2008, 10:42

I suggest some troubleshooting:
First try to establish a connection with NO encryption. Does dhcpcd work? If not, there are certain versions of dhcpcd which are better than others, but just to check that a connection will definitely work you can bypass dhcpcd altogether and set a static IP address. Instructions here -
http://www.murga-linux.com/puppy/viewto ... 774#145774

If successful, try again with WEP encryption. I have a suspicion that you still need to load these 2 modules manually before WEP will work -
arc4
ecb

proficus wrote:What wireless pci card (brand, model) would work without problems?

I regard the Ralink chipsets as quality, reliable devices, and the Ralink Linux drivers as trim, reliable code. I can't tell you a Brand.

kalleanka · #16 Post by **kalleanka** » Mon 12 May 2008, 21:20

Warning, wlan0: using IPV4LL address 169.254.204.189

its the wrong ip set. So try:

kill dhcpcd eth1 (wireless)

and run pwireless-0.7.2

and it should work. I think pwireless-0.7.2 calls dhcpcd with some flags and thats the diffrence.

proficus · #17 Post by **proficus** » Fri 16 May 2008, 18:18

tempestuous wrote:I
I regard the Ralink chipsets as quality, reliable devices, and the Ralink Linux drivers as trim, reliable code. I can't tell you a Brand.

I purchased msi pc70se (wireless 11n PCI card), with Ralink chipset.
I tried to load all available modules, but couldn't get it recognized.
Where could I find the drivers?

tempestuous · #18 Post by **tempestuous** » Sat 17 May 2008, 07:41

Ooh, that's a very new wifi device.
If it's supported in Linux yet, the correct driver should be the latest "rt61pci" driver in Puppy4-2.6.25.
Run "lsmod" to see if Puppy4-2.6.26 has recognised your device and loaded the rt61pci driver. If not, try to manually load the driver -

Code: Select all

modprobe rt61pci

Even if there are no errors, there's still no guarantee that a network interface will be created. Run -

Code: Select all

ifconfig -a

and

Code: Select all

iwconfig

to check.

If no success, please report the output of

Code: Select all

lspci -n

proficus · #19 Post by **proficus** » Sat 17 May 2008, 20:36

Thanks for the hint - didn't consider obvious thing that older devices are better supported.

No succes with the module.
Output of lspci -v attached.

tempestuous · #20 Post by **tempestuous** » Sun 18 May 2008, 03:25

PCI ID 1814:0601 is a wifi adaptor with Ralink RT2800 chipset. This modern chipset is not currently supported by the opensource rt2x00 series drivers in the Linux kernel, but they do plan it in the future -
http://rt2x00.serialmonkey.com

For now, I have compiled the vendor-supplied Linux driver from
http://www.ralinktech.com/ralink/Home/S ... Linux.html

It's available as a dotpet for Puppy3.x and 4.0 here -
http://www.murga-linux.com/puppy/viewto ... 442#198442

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

wireless rtl80211

wireless rtl80211