Wifi Drop

[martinhoj]

Hey there.
My wireless go off when I don't use the pi for a little time, but it's ok when I use it. I must restart router and pi many times before it's working again.
This is a B+ Model. I check power for the pi 4.9 volt all the time.
I try with comfast and this Tp link Tl-wn823n. Still the same trouble.
I try with noobs and now it is the standalone raspbmc. Still the same trouble.
Here is the log Your debug xbmc.log: http://xbmclogs.com/show.php?id=370839
Your debug xbmc.old.log: http://xbmclogs.com/show.php?id=370843
I also have this from putty.
I dont think my router is bad. I used to have a model B before B+ and I've never
had any trouble with wifi on that model.
Any ideas is welcome
login as: pi
pi@192.168.1.105's password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
pi@raspbmc:~$ lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
pi@raspbmc:~$ lsmod
Module Size Used by
bcm2708_wdog 2340 1
ipv6 251548 31
xt_state 664 1
iptable_mangle 760 0
iptable_nat 1736 0
nf_conntrack_ipv4 8860 2
nf_defrag_ipv4 760 1 nf_conntrack_ipv4
nf_nat_ipv4 2358 1 iptable_nat
nf_nat 8820 2 nf_nat_ipv4,iptable_nat
nf_conntrack 54280 5 nf_nat,xt_state,nf_nat_ipv4,iptable_nat,nf_conntrack_ipv4
iptable_filter 624 1
ip_tables 10592 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 10532 4 ip_tables,xt_state,iptable_filter,iptable_mangle
joydev 8264 0
snd_soc_tas5713 4128 0
snd_soc_pcm512x 6592 0
snd_soc_wm8804 6064 0
8192cu 458968 0
hid_logitech_dj 9456 0
snd_soc_bcm2708_i2s 4668 0
regmap_mmio 1796 1 snd_soc_bcm2708_i2s
snd_soc_core 99000 4 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_tas5713,snd_soc_bcm2708_i2s
snd_compress 6124 1 snd_soc_core
regmap_i2c 824 4 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core,snd_soc_tas5713
i2c_bcm2708 3596 0
snd_pcm_dmaengine 2428 1 snd_soc_core
regmap_spi 968 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
snd_pcm 62044 2 snd_soc_core,snd_pcm_dmaengine
snd_page_alloc 2984 1 snd_pcm
snd_timer 17252 1 snd_pcm
snd 41760 4 snd_soc_core,snd_timer,snd_pcm,snd_compress
pi@raspbmc:~$ iwconfig wlan0
wlan0 unassociated Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.422 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
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

pi@raspbmc:~$ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:4f:82:0b
inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe4f:820b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1136 errors:0 dropped:0 overruns:0 frame:0
TX packets:1461 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:155445 (151.8 KiB) TX bytes:350067 (341.8 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:342 errors:0 dropped:0 overruns:0 frame:0
TX packets:342 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30024 (29.3 KiB) TX bytes:30024 (29.3 KiB)

wlan0 Link encap:Ethernet HWaddr 10:fe:ed:22:16:20
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:29 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)

[pluggy]

Have you tried the old 8192cu.conf trick ?

http://www.raspberrypi.org/forums/viewt ... 17#p564117

http://www.raspberrypi.org/forums/viewt ... 61#p458761

[martinhoj]

Thanks for the reply.
No i haven't .I thougt that it whas fixed in the normal drivers.It look like it is disabled in mine.
Do you think i have to try that fix you link to ?
Thanks Martin

[pluggy]

It works for the RTL8188CUS chipset wifi adaptors which uses the same driver. What have you to lose ?

[martinhoj]

Thank you.
I must learn how to make the directory?
Any link for that also

[kusti8]

Thank you.
I must learn how to make the directory?
Any link for that also

Make what directory? I have the Edimax 7811UN which uses the 8192CU driver and I recently applied the fix stated by pluggy and it worked.

[martinhoj]

When i input
sudo nano /etc/modprobe.d/8192cu.conf

i get this
options 8192cu rtw_power_mgnt=0 rtw_enusbss=0

Does that mean that it is already fixet or ??

[kusti8]

That means that power management is already turned off. If the problem persists, you may want to get a powered usb hub or a better power supply.

[martinhoj]

I already try to chance powerline and power suply.

When i cant connect. I can always see my network in a scan.But not getting ip adr.
I am also trying with static ip. same story as dhcp.

Is this something to do with security Maybe??

[kusti8]

Probably nothing to do with security. Did you check that the amps are enough for your pi. I once had a blown fuse that I had to replace. Other than that, it may be a badly configured network. Can you try it on another network?

[martinhoj]

Thank you for your support
My power adapter is from a ipad .
That adapter used to work whit my old raspberry B
I just config my D link router for another channel instead of auto.
and only wpa2.
I hope it help. There are many other networks around here.Maybe that
is why??
I let you know if it is working.
Again Thank you..

[kusti8]

Apple chargers are known to not be reliable with the raspberry pi. You can get a good one off Amazon for about $10

[martinhoj]

Apple chargers are known to not be reliable with the raspberry pi. You can get a good one off Amazon for about $10

Ok i did not know that.
That i must try.Thank you.

[pluggy]

Other than fakes, the main problem with Apple chargers is that people buy cheap micro USB leads to use with them. The lead is as least as important as the power supply.

[martinhoj]

Hey..

I am now on another router at my girlfriends house.
It is total stabil here
Maybe there is something wrong whit my router.
Router D-Link 845L is under a year and all other Pc connect without problem.
New firmware is on the router.

Any ideas on the router side to chance to cure the problem ??
Thanks Martin

[DougieLawson]

Any ideas on the router side to chance to cure the problem ??

Install a copy of InSSIDer3 on your Windows laptop. Scan your local area and see what channels are in use by everyone else in your neighbourhood, change the channel on your WiFi to the least used channel (for my APs that's CH3 & CH4).

[martinhoj]

Any ideas on the router side to chance to cure the problem ??

Install a copy of InSSIDer3 on your Windows laptop. Scan your local area and see what channels are in use by everyone else in your neighbourhood, change the channel on your WiFi to the least used channel (for my APs that's CH3 & CH4).

Hey again.I already trying to chance channel number.
But didt help
Other things i can do ??

One thing i dont understand.The pi i getting a dns 192.168.1.1.
Maybe that is why ??


Thanks Martin

[DougieLawson]

Other things i can do ??

Reduce the number of non-WiFi devices that are cluttering the 2.4GHz ISM band. Reduce the number of brick walls between you and the AP. FM is line of sight if your RPi is in the same room as the AP you'll go faster and with a lower power drain.

If WiFi is a real dead loss then look at powerline adapters (which use your house wiring).

Also think about running a root crontab script (every twenty minutes)

Code: Select all

#!/bin/bash

/bin/ping -q -c1 192.168.1.254 > /dev/null # change to your gateway address

if [ $? -eq  0 ]
then
  : #  echo "Network active"

else
  echo "Network down, fixing..."
#  ifdown --force wlan0
  /bin/kill -9 `pidof wpa_supplicant`
  /bin/kill -9 `pidof wpa_cli`
  /sbin/ifup --force wlan0
  /sbin/ip route add default via 192.168.1.254 dev wlan0 # and change this
fi

to restart the broken network.

[martinhoj]

It all works fine now.I bought a linksys A1200 + .it is quite stable now.
No droops. Now I will see if I can get it and work on 5GHz on raspbmc.
I cant see the 5GHz now on the pi.or should I just leave it as it is now.
Thanks for support.Merry christmas.
Martin;-)