LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-15-2008, 06:44 PM   #1
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Rep: Reputation: Disabled
wireless problem on -current


I'm experiencing some problems with using wireless on -current.

1. I can manually run wpa_supplicant and get an ip address via dhcpcd.
2. If I run "/etc/rc.d/rc.inet1 restart" it sees wlan0, starts wpa_supplicant, but fails to get an ip address.
3. When I boot, I get an ip address sometimes but not other times. When I do _not_ get an ip address, I see the messages about trying to get an ip address, my MAC address, etc. When I _do_ get an ip on boot, I don't see any messages at all about it trying to get the ip address.

So I'm not sure what to check from here. There must be some difference about how rc.inet1 runs wpa_supplicant compared to how I run it manually.

Any ideas?

Thanks in advance,
Brian
 
Old 04-15-2008, 07:49 PM   #2
trryhend
LQ Newbie
 
Registered: Oct 2007
Posts: 26

Rep: Reputation: 15
Quote:
Originally Posted by BCarey View Post
I'm experiencing some problems with using wireless on -current.

1. I can manually run wpa_supplicant and get an ip address via dhcpcd.
2. If I run "/etc/rc.d/rc.inet1 restart" it sees wlan0, starts wpa_supplicant, but fails to get an ip address.
3. When I boot, I get an ip address sometimes but not other times. When I do _not_ get an ip address, I see the messages about trying to get an ip address, my MAC address, etc. When I _do_ get an ip on boot, I don't see any messages at all about it trying to get the ip address.

So I'm not sure what to check from here. There must be some difference about how rc.inet1 runs wpa_supplicant compared to how I run it manually.

Any ideas?

Thanks in advance,
Brian

There are several issues that could cause dhcp queries to fail on a wireless network. If it's not a fully supported wireless NIC, things don't always work as expected and you may just have to tinker around until you get it to associate and acquire IP info quickly and reliably.

You might try extending the timeout; Add timeout line to dhclient.conf add 5 or 10 seconds to the default;
timeout 65 ;
or
timeout 70 ;

If you're always connecting to the same network, you could just hard code the settings. You can put lines in rc.local
Something like:
iwconfig wlan0 essid linksys
dhclient

But I think wpa_supplicant has a place for essid, so you could try that instead.
 
Old 04-16-2008, 01:06 AM   #3
pdw_hu
Member
 
Registered: Nov 2005
Location: Budapest, Hungary
Distribution: Slackware, Gentoo
Posts: 346

Rep: Reputation: Disabled
I've exactly the same issue. Using iwl4965 with wpa2-personal encryption.
 
Old 04-16-2008, 12:13 PM   #4
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by pdw_hu View Post
I've exactly the same issue. Using iwl4965 with wpa2-personal encryption.
I'm using b43.

Brian
 
Old 04-16-2008, 12:15 PM   #5
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by trryhend View Post
There are several issues that could cause dhcp queries to fail on a wireless network. If it's not a fully supported wireless NIC, things don't always work as expected and you may just have to tinker around until you get it to associate and acquire IP info quickly and reliably.

You might try extending the timeout; Add timeout line to dhclient.conf add 5 or 10 seconds to the default;
timeout 65 ;
or
timeout 70 ;

If you're always connecting to the same network, you could just hard code the settings. You can put lines in rc.local
Something like:
iwconfig wlan0 essid linksys
dhclient

But I think wpa_supplicant has a place for essid, so you could try that instead.
I connect to different networks, so I can't hardcode it. Also, I'm using dhcpcd, not dhclient (although I did try with dhclient).

I will keep tinkering, and probably see if ndiswrapper works better.

Brian
 
Old 04-18-2008, 10:23 AM   #6
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by BCarey View Post
I connect to different networks, so I can't hardcode it. Also, I'm using dhcpcd, not dhclient (although I did try with dhclient).

I will keep tinkering, and probably see if ndiswrapper works better.

Brian
Using ndiswrapper did not help.

Brian
 
Old 04-18-2008, 02:56 PM   #7
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
OK, so are networks really alive? Can they learn and change their behavior?
Two nights ago, I could not get an ip address on my home network for anything, even though I connected fine at my office. Last night I managed to get it to connect using the Insane Method (trying it over and over again). Today I went home and got an address immediately by killing dhcpcd and re-running it. Then I got back to my office and I didn't even have to rerun dhcpcd, I was just automatically connected.

Now the strange thing is I didn't do anything except keep beating my head against a wall, which technically shouldn't change much (at least not much about the computer). Frankly, all this network stuff seems a bit like voodoo to me (no offense to practicants or network engineers).

rc.inet1 is still not working.

Brian
 
Old 04-18-2008, 06:21 PM   #8
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,140
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,

Post the '/etc/rc.d/rc.inet1.conf'.
 
Old 04-18-2008, 06:31 PM   #9
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by onebuck View Post
Hi,

Post the '/etc/rc.d/rc.inet1.conf'.
Here's the relevant section:

Code:
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"
I have also tried adding
Code:
WLAN_WPACONF[4]="/etc/wpa_supplicant.conf"
which was suggested somewhere, but it didn't help
Brian
 
Old 04-22-2008, 09:55 PM   #10
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
Can anyone please help with this? It's a critical issue. I actually decided to back down to 12.0 because of this, but it couldn't handle the lvm on top of luks, so I need to fix it on -current. I think it is a driver issue.

Basically, at my office I can get on the network, although not with rc.inet1. By manually running wpa_supplicant and dhcpcd I get on and can run normally.

At home, on the other hand, I can only get online occasionally, and when I do there is lots of packet loss (even between my computer and the router) and performance is horrible. When dhcpcd fails, if I look on the router, it shows that it has handed an ip address to my computer, but my computer doesn't seem to know about it. If I watch iwconfig, I can see that it periodically disassociates and looses the encryption key. Turning wpa off entirely on the router, however, does not help the situation. Even so, I don't think it is the router because my wife's computer running 12.0 connects and runs flawlessly and rapidly, and I never had problems with it under 12.0 either.

I'm happy to provide any other information which could be useful to diagnose this.

Thanks in advance,
Brian
 
Old 04-23-2008, 06:54 AM   #11
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
Quote:
Originally Posted by BCarey View Post
Can anyone please help with this? It's a critical issue. I actually decided to back down to 12.0 because of this, but it couldn't handle the lvm on top of luks, so I need to fix it on -current.
Hi Brian,

I'm sorry I can't help with the wlan issue, but I can say that Slackware 12.0 with the mkinitrd package from Slackware current is able to handle lvm on top of luks, because I'm using this setup since two days myself.

EDIT: The only major change I made is that I upgraded the kernel to 2.6.24.3. Don't know if that makes a big difference though.

There was a nice post from alienbob that gave a howto for this, and together with the readme files on lvm from your Slackware CD it should work fine. I just see that it is probably the post you used for your install, the last reply in this thread came from you (http://www.linuxquestions.org/questi...71#post3093171)

If you can't get your wlan to work with current right now, the lvm/luks stuff is worth to give it one more try even on 12.0.

Last edited by titopoquito; 04-23-2008 at 07:11 AM.
 
Old 04-23-2008, 09:02 AM   #12
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by titopoquito View Post
Hi Brian,

I'm sorry I can't help with the wlan issue, but I can say that Slackware 12.0 with the mkinitrd package from Slackware current is able to handle lvm on top of luks, because I'm using this setup since two days myself.

EDIT: The only major change I made is that I upgraded the kernel to 2.6.24.3. Don't know if that makes a big difference though.

There was a nice post from alienbob that gave a howto for this, and together with the readme files on lvm from your Slackware CD it should work fine. I just see that it is probably the post you used for your install, the last reply in this thread came from you (http://www.linuxquestions.org/questi...71#post3093171)

If you can't get your wlan to work with current right now, the lvm/luks stuff is worth to give it one more try even on 12.0.
For some reason when I tried I could not run lilo. mkinitrd ran fine, but lilo did not install. Unfortunately I didn't write down the error message. I will probably try this again if noone can help with the wireless issue.

Brian
 
Old 04-23-2008, 01:02 PM   #13
bstrik
LQ Newbie
 
Registered: Sep 2003
Location: Netherlands
Distribution: ARCH
Posts: 11

Rep: Reputation: 0
Hi,

I had the same issues with an intel iwl3945.
I solved it by changing the SLEEP commands in /etc/rc.d/rc.wireless.
There are 2 places where the command "$IFCOMMAND up" is given followed by a "sleep 1" (line 111/112 and 304/305).
After I changed them to "sleep 3" i had no more problems getting a wireless connection.
 
Old 04-23-2008, 01:39 PM   #14
pdw_hu
Member
 
Registered: Nov 2005
Location: Budapest, Hungary
Distribution: Slackware, Gentoo
Posts: 346

Rep: Reputation: Disabled
Quote:
Originally Posted by bstrik View Post
I solved it by changing the SLEEP commands in /etc/rc.d/rc.wireless.
Great tip, it worked! Thanks!
 
Old 04-23-2008, 03:12 PM   #15
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 65
Quote:
Originally Posted by bstrik View Post
Hi,

I had the same issues with an intel iwl3945.
I solved it by changing the SLEEP commands in /etc/rc.d/rc.wireless.
There are 2 places where the command "$IFCOMMAND up" is given followed by a "sleep 1" (line 111/112 and 304/305).
After I changed them to "sleep 3" i had no more problems getting a wireless connection.
To try and help out on WHY it worked:

The 'sleep' command tells the program to 'wait' for a period of time, then run. Somewhere, there is another prog that has to run before the '$IFCOMMAND' can be successfully run.

Now the question is: Where is it, and what is it?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
slackware current question on the current kernels davimint Slackware 3 06-03-2007 07:39 AM
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 01:42 PM
cvs diff the most current and second last current version powah Linux - Software 1 03-30-2006 01:02 PM
Wireless, USB Mouse problems with Slackware-current Korazail Slackware 7 12-23-2005 05:24 PM
current Slack-Current giving troubles? r_jensen11 Slackware 5 02-02-2004 05:08 PM


All times are GMT -5. The time now is 06:39 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration