View previous topic :: View next topic |
Author |
Message |
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Thu May 12, 2005 8:29 pm Post subject: [Not Solved] very slow wlan0 dhcpcd - DWL-122 |
|
|
I've read a few threads on this topic, but none seem to solve my problems.
Here is my setup:
I have Gentoo running on my iBook (ppc arch) and have a Dlink DWL-122 wlan stick for wireless connectivity. It is using the prism2 drivers installed through linux-wlan-ng. The stick works fine, it hotplugs great and I can start it up using /etc/init.d/wlan start.
Here is the problem:
It takes forever getting an IP address when I do /etc/init.d/net.wlan0 start. net.wlan0 is a symlink to net.eth0. I am using baselayout-1.9.4-r6.
I read that I should change the dhcpcd -z to dhcpcd -k in the net.eth0/wlan0 scripts and this would solve the problem. I thought it did at 1'st but it really did nothing.
I also read that upgrading to a newer baselayout would solve my problem. I upgraded to the ~ppc baselayout (version 1.11.11-r3). This caused new problems, since it apparently uses /etc/conf.d/wireless for wlan0, and completely disregards linux-wlan-ng's wireless approach (/etc/conf.d/wlan.conf).
I downgraded back to 1.9.4-r6, whcih was a struggle since some files weren't restored properly, like init.d/net.eth0. I was able to restore net.eth0 and net.lo using the stage I installed from.
Now using /etc/init.d/net.wlan0 almost always fails, and if it does work it takes several minutes to obtain an IP address. This basically makes using the wireless impossible.
Can anyone give me some help or some suggestions. I'm unfortualtly stuck with linux-wlan-ng for now.
Last edited by mikegpitt on Tue Aug 30, 2005 2:09 am; edited 4 times in total |
|
Back to top |
|
|
Dr. Heywood Floyd n00b
Joined: 19 Jan 2004 Posts: 16 Location: Davis, CA
|
Posted: Tue May 31, 2005 6:26 am Post subject: OK... some comments and questions. |
|
|
First off D-Link sucks. Try Linksys or Netgear for a router.
Have you checked your signal and changed the channel on which you send out the DHCP lisc? Sometimes different channels (frequencies) do better in certain room. For example, channel 6 sucks in my house while channel 11 is great.
So, check the signal strength and try a new channel. Or borrow a router (a good one) and test it. I bet it's the D-Link. I had a D-Link and hated the POS. It's a donation for an animal shelter now. _________________ "What the hell is that?"
-- Last words of a programmer
and
-- Last words of a nuclear bomb testing dummy |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
Posted: Tue May 31, 2005 10:13 am Post subject: Re: very slow wlan0 dhcpcd |
|
|
mikegpitt wrote: | I read that I should change the dhcpcd -z to dhcpcd -k in the net.eth0/wlan0 scripts and this would solve the problem. I thought it did at 1'st but it really did nothing.
I also read that upgrading to a newer baselayout would solve my problem. I upgraded to the ~ppc baselayout (version 1.11.11-r3). This caused new problems, since it apparently uses /etc/conf.d/wireless for wlan0, and completely disregards linux-wlan-ng's wireless approach (/etc/conf.d/wlan.conf). |
It does solve a problem with dhcpcd, but not the problem you're describing. The -z to -k fix is only for when you change networks.
And baselayout-1.11.x and upwards do not support linux-wlan-ng directly. You have to disable support for it which can be achieved like so
modules=( "!iwconfig" "!wpa_supplicant" ). However, essitnet module should still work fine - this maps config_ESSID to config_wlan0 so you can change network settings per ESSID still. |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Fri Jun 03, 2005 3:22 am Post subject: |
|
|
Floyd:
My router is actually a Linksys, but my USB network stick is a DLink. The reason I bought it was becasue many people have reported it working well for them.
UberLord:
Do you think I should upgrade to the ~ppc baselayout then?
I'm pleased to see this post got dug up, I thought it was lost forever. I am still having the problems as I discussed above. No clue what is actually going on though. |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
Posted: Fri Jun 03, 2005 6:24 am Post subject: |
|
|
mikegpitt wrote: | Do you think I should upgrade to the ~ppc baselayout then? |
I would recommend using baselayout-1.11.12-r4 - which is ~ppc I believe |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Mon Jun 20, 2005 10:01 pm Post subject: |
|
|
I upgraded to the ~ppc baselayout, but I'm still having the same problems. I decided to try it out for a while just to make sure, but wlan0 still hangs very long when getting an ip via dhcp, and it often fails.
Anyone have any other ideas of what to try? |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
Posted: Mon Jun 20, 2005 11:03 pm Post subject: |
|
|
Try another dhcp client like udhcpc or dhclient |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Sun Jul 03, 2005 5:02 pm Post subject: |
|
|
Ok new update... I switched to dhclient, and again, at first I thought there was some improvment but I'm still having the same problems. I'm on the wireless right now, but it took five failures before it woudl connect. One interesting thing is that at the end of the 4'th time the light stopped flashing (which is a good sign) then on the 5'th try it connected quickly. I've noticed this trend, but don't know what it means.
I didn't try udhcp, as it is ~ppc masked, and I figured it would probably give the same problem anyways.
Maybe the problem isn't with the dhcp client, but somewhere else. I'm using the latest ~ppc linux-wlan-ng (it is only ~ppc). |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Sun Jul 10, 2005 4:26 pm Post subject: |
|
|
Another update...
I'm still having problems, but I recently updated to the 2.6.12 kernel and I noticed some new errors in my dmesg, which I think is deffinitly related to my problems.
This is the error: Code: | p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped. |
This error occurs many times and ends when I am able to connect and get an IP from the dhcp server.
I did some google'ing and I read something that it may be a problem with interrupts. I'm not sure if this is true or not, but here is the output of /proc/interupts:
Code: | mikeg@bonsai ~ $ cat /proc/interrupts
CPU0
1: 0 OpenPIC Edge PMac Output
2: 0 OpenPIC Edge PMac Input
24: 25 OpenPIC Level ide1
25: 1126404 OpenPIC Level VIA-PMU
26: 1341 OpenPIC Level keywest i2c
29: 0 OpenPIC Level ohci_hcd:usb1
39: 74986 OpenPIC Level ide0
40: 2 OpenPIC Level ohci1394
42: 98726 OpenPIC Level keywest i2c
47: 78829 OpenPIC Level GPIO1 ADB
48: 653899 OpenPIC Level radeon@pci:0000:00:10.0
61: 0 OpenPIC Edge Sound Headphone Detection
63: 41980 OpenPIC Level ohci_hcd:usb2, ohci_hcd:usb3, ehci_hcd:usb4
BAD: 0 |
EDIT: p80211knetdev_hard_start_xmit errors were occuring because I was trying to brodcast for an IP without being connected to an access point first.
Last edited by mikegpitt on Mon Aug 29, 2005 7:29 pm; edited 1 time in total |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Mon Aug 29, 2005 7:27 pm Post subject: |
|
|
Ok so this thread is way old but I think I finally solved my problems. I tried a million things, but I think the main problem is the /etc/init.d/wlan script. I'm not sure why, but I dont think it was settign my ssid properly. I found a script on google, and modified it a bit for my purposes. This is what I'm using now to connect to the net:
Code: | #!/bin/sh
#usage ./wireless_start.sh myssid
echo -n "Joining wireless network: "
echo $1
sudo modprobe prism2_usb
sudo rmmod prism2_usb
sudo modprobe prism2_usb prism2_doreset=1
sudo wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
sudo wlanctl-ng wlan0 lnxreq_autojoin ssid="$1" authtype=opensystem
sudo /etc/init.d/net.wlan0 restart |
I'm using the 2.6.12 kernel and linux-wlan-ng-pre26. |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Tue Aug 30, 2005 2:11 am Post subject: |
|
|
Nevermind... it isn't working afterall. The script above works temporarily, but then spits error out to /var/log/messages, and then won't stay conencted very long.
After I was able to use the wireless using the regular /etc/init.d/wlan script, this unfortunatly was only temporary.
I've had a nightmare over the last 4 months struggling with the DWL-122. I'm really not sure what to try next... |
|
Back to top |
|
|
|