LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices


Reply
  Search this Thread
Old 06-26-2011, 01:36 PM   #1
superdog
Member
 
Registered: Feb 2008
Distribution: slackware, suse, anything that begins with S
Posts: 46

Rep: Reputation: 17
WICD and r8192e_pci


I have a samsung n130 netbook running zenwalk 7.0 and tinycore. When I try to use WICD as a ntwork manager it will not connect to the access point (using wep) unless i type in a terminal "iwconfig essid Waaaaa key XXXX" and from there it connects as normal. It's driving me mad as I don't like when things don't work properly, it also did this in opensuse 11.3. Anyone know a solution to this? Below is the output of dmesg if that's any help...

Code:
Linux kernel driver for RTL8192 based WLAN cards
Copyright (c) 2007-2008, Realsil Wlan
rtl819xE 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
rtl819xE 0000:02:00.0: setting latency timer to 64
Dot11d_Init()
IRQ 16
netif_stop_queue() cannot be called before register_netdev()
Linking with Waaaaa,channel:1, qos:0, myHT:1, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
r8169 0000:03:00.0: eth0: link down
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
r8169 0000:03:00.0: eth0: link down
r8169 0000:03:00.0: eth0: link down
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
r8169 0000:03:00.0: eth0: link down
r8169 0000:03:00.0: eth0: link down
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:2
=================>ieee80211_authentication_req():auth->algorithm is 0
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
Linking with Waaaaa,channel:1, qos:0, myHT:0, networkHT:0
===>ieee80211_associate_procedure_wq(), chan:1
=================>ieee80211_authentication_req():auth->algorithm is 0
==========>to link with AP using SEC(1, 1)
Associated successfully
Using G rates:108
Successfully associated, ht not enabled(0, 0)
============>normal associate
DHCP pkt src port:68, dest port:67!!
DHCP pkt src port:68, dest port:67!!
 
Old 06-28-2011, 01:21 PM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello,

have you tried to connect without wicd? My wireless network has wpa2 encryption, I use only wpa_supplicant. wpa_supplicant can also manage wep.

Could you please post the relevant parts of your /etc/rc.d/rc.inet1.conf?

Markus
 
Old 07-06-2011, 06:34 PM   #3
superdog
Member
 
Registered: Feb 2008
Distribution: slackware, suse, anything that begins with S
Posts: 46

Original Poster
Rep: Reputation: 17
I can connect fine without wicd, which is what annoys me. For now I have everything set to connect automatically at startup using wpa_supplicant and rc.inet1.conf (thanks for the tip, markush), where before I was doing it manually. It just annoys me because I can plug my alfa card in and use wicd to connect fine on wlan1 but when i try to connect using wlan0 (the r8192e_pci card) it tells me the password is bad. I suppose i have to live with it for now though. Thanks again

Quote:
IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
USE_DHCP[4]="yes"
WLAN_ESSID[4]=O_o
WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=the proper key is in here but i removed it as im paranoid!"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"
WLAN_WPAWAIT[4]=30

Last edited by superdog; 07-06-2011 at 06:39 PM.
 
Old 07-07-2011, 12:19 AM   #4
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello superdog,

I don't know if this works if your system has different wireless NICs wlan0 and wlan1, but I'm using my laptop in several networks and I have an entry for every network in my wpa_supplicant.conf. It connects to the available network automatically.

Note that there are manpages for wpa_supplicant and wpa_supplicant.conf as well (which in your case may be more interesting).

Do you have the respective entries for your wlan1 in your /etc/rc.d/rc.inet1.conf file?

Markus

Last edited by markush; 07-07-2011 at 12:21 AM.
 
Old 07-07-2011, 12:41 AM   #5
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,841

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
I actually configured my router for wpa even though it has wep also, as wpa is supposed to be more secure. It even connects my wheezy os which drops connection on wep security.

Last edited by EDDY1; 07-07-2011 at 12:43 AM.
 
Old 07-13-2011, 01:52 AM   #6
kasl33
Member
 
Registered: Oct 2004
Location: USA
Distribution: Ubuntu-Server, Mac OS X, Arch Linux
Posts: 356

Rep: Reputation: 48
do NOT use WEP. It is very insecure and simple to crack.

modprobe r8193 would load the correct kernel module. WICD is superior to networkmanager but does use wpa. Not sure why it wouldn't connect to wep.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Wicd anon258 Linux - Software 2 03-31-2011 11:00 AM
wicd Polanski Linux - Software 14 04-13-2010 06:51 PM
where is wicd 1.7 ? witek Slackware 6 01-25-2010 04:36 PM
WICD tray icon says not connected, WICD manager says conneted to wired network?!?! intheshadows Linux - Newbie 1 12-24-2009 12:15 PM
Slack 13 and wicd technik733 Slackware 4 12-21-2009 05:04 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook

All times are GMT -5. The time now is 07:59 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration