Re: FreeBSD 7.2 - iwi error

2009-06-30 Thread Patrick Lamaiziere
Le Mon, 29 Jun 2009 13:53:48 +0300,
Siyan Sabinov Hadzhiev siyan.hadzh...@gmail.com a écrit :

 I have configure bmiss parameter in rc.conf as you said and enable
 debug.iwi in sysctl , Bellow you can see the log entries.
 I remembered that these entries were like yours , Beacon Miss..
 Now they have changed to something different.The iwi0 device timeout
 errors went away after the bmiss config.
 
 So I will try with this config , and I think it will work for me.

You can try the new Intel firmware for iwi, see
http://forums.freebsd.org/showthread.php?t=3849
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: FreeBSD 7.2 - iwi error

2009-06-29 Thread Siyan Sabinov Hadzhiev
Thank you for your reply Jose ,

I have configure bmiss parameter in rc.conf as you said and enable
debug.iwi in sysctl , Bellow you can see the log entries.

Jun 29 13:40:13 bsdt43 kernel: enter FW state 4
Jun 29 13:40:13 bsdt43 kernel: Scan request: index 393 dwell 150/30/30
Jun 29 13:40:13 bsdt43 kernel: Scan 1 2.4GHz channels: 1/BCAST
Jun 29 13:40:13 bsdt43 kernel: sending command idx=13 type=26 len=96
Jun 29 13:40:13 bsdt43 kernel: sending command idx=14 type=23 len=0
Jun 29 13:40:13 bsdt43 kernel: Scan completed (1, 2)
Jun 29 13:40:13 bsdt43 kernel: exit FW state 4
Jun 29 13:40:43 bsdt43 kernel: enter FW state 4
Jun 29 13:40:43 bsdt43 kernel: Scan request: index 394 dwell 150/30/30
Jun 29 13:40:43 bsdt43 kernel: Scan 1 2.4GHz channels: 6/BCAST
Jun 29 13:40:43 bsdt43 kernel: sending command idx=15 type=26 len=96
Jun 29 13:40:44 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:40:44 bsdt43 kernel: exit FW state 4
Jun 29 13:40:44 bsdt43 kernel: enter FW state 4
Jun 29 13:40:44 bsdt43 kernel: Scan request: index 395 dwell 108/30/30
Jun 29 13:40:44 bsdt43 kernel: Scan 1 2.4GHz channels: 11/BCAST
Jun 29 13:40:44 bsdt43 kernel: sending command idx=0 type=26 len=96
Jun 29 13:40:44 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:40:44 bsdt43 kernel: exit FW state 4
Jun 29 13:40:44 bsdt43 kernel: enter FW state 4
Jun 29 13:40:44 bsdt43 kernel: Scan request: index 396 dwell 50/30/30
Jun 29 13:40:44 bsdt43 kernel: Scan 1 2.4GHz channels: 7/BCAST
Jun 29 13:40:44 bsdt43 kernel: sending command idx=1 type=26 len=96
Jun 29 13:40:44 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:40:44 bsdt43 kernel: exit FW state 4
Jun 29 13:40:59 bsdt43 kernel: enter FW state 4
Jun 29 13:40:59 bsdt43 kernel: Scan request: index 397 dwell 149/30/30
Jun 29 13:40:59 bsdt43 kernel: Scan 1 2.4GHz channels: 13/BCAST
Jun 29 13:40:59 bsdt43 kernel: sending command idx=2 type=26 len=96
Jun 29 13:40:59 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:40:59 bsdt43 kernel: exit FW state 4
Jun 29 13:40:59 bsdt43 kernel: enter FW state 4
Jun 29 13:40:59 bsdt43 kernel: Scan request: index 398 dwell 91/30/30
Jun 29 13:40:59 bsdt43 kernel: Scan 1 2.4GHz channels: 2/BCAST
Jun 29 13:40:59 bsdt43 kernel: sending command idx=3 type=26 len=96
Jun 29 13:40:59 bsdt43 kernel: sending command idx=4 type=23 len=0
Jun 29 13:40:59 bsdt43 kernel: Scan completed (1, 2)
Jun 29 13:40:59 bsdt43 kernel: exit FW state 4
Jun 29 13:41:09 bsdt43 kernel: enter FW state 4
Jun 29 13:41:09 bsdt43 kernel: Scan request: index 399 dwell 150/30/30
Jun 29 13:41:09 bsdt43 kernel: Scan 1 2.4GHz channels: 3/BCAST
Jun 29 13:41:09 bsdt43 kernel: sending command idx=5 type=26 len=96
Jun 29 13:41:09 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:41:09 bsdt43 kernel: exit FW state 4
Jun 29 13:41:09 bsdt43 kernel: enter FW state 4
Jun 29 13:41:09 bsdt43 kernel: Scan request: index 400 dwell 91/30/30
Jun 29 13:41:09 bsdt43 kernel: Scan 1 2.4GHz channels: 4/BCAST
Jun 29 13:41:09 bsdt43 kernel: sending command idx=6 type=26 len=96
Jun 29 13:41:09 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:41:09 bsdt43 kernel: exit FW state 4
Jun 29 13:41:09 bsdt43 kernel: enter FW state 4
Jun 29 13:41:09 bsdt43 kernel: Scan request: index 401 dwell 33/30/30
Jun 29 13:41:09 bsdt43 kernel: Scan 1 2.4GHz channels: 5/BCAST
Jun 29 13:41:09 bsdt43 kernel: sending command idx=7 type=26 len=96
Jun 29 13:41:09 bsdt43 kernel: sending command idx=8 type=23 len=0
Jun 29 13:41:09 bsdt43 kernel: Scan completed (1, 2)
Jun 29 13:41:09 bsdt43 kernel: exit FW state 4
Jun 29 13:41:19 bsdt43 kernel: enter FW state 4
Jun 29 13:41:19 bsdt43 kernel: Scan request: index 402 dwell 150/30/30
Jun 29 13:41:19 bsdt43 kernel: Scan 1 2.4GHz channels: 8/BCAST
Jun 29 13:41:19 bsdt43 kernel: sending command idx=9 type=26 len=96
Jun 29 13:41:19 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:41:19 bsdt43 kernel: exit FW state 4
Jun 29 13:41:19 bsdt43 kernel: enter FW state 4
Jun 29 13:41:19 bsdt43 kernel: Scan request: index 403 dwell 106/30/30
Jun 29 13:41:19 bsdt43 kernel: Scan 1 2.4GHz channels: 9/BCAST
Jun 29 13:41:19 bsdt43 kernel: sending command idx=10 type=26 len=96
Jun 29 13:41:19 bsdt43 kernel: sending command idx=11 type=23 len=0
Jun 29 13:41:19 bsdt43 kernel: Scan completed (1, 2)
Jun 29 13:41:19 bsdt43 kernel: exit FW state 4
Jun 29 13:41:40 bsdt43 kernel: enter FW state 4
Jun 29 13:41:40 bsdt43 kernel: Scan request: index 404 dwell 150/30/30
Jun 29 13:41:40 bsdt43 kernel: Scan 1 2.4GHz channels: 10/BCAST
Jun 29 13:41:40 bsdt43 kernel: sending command idx=12 type=26 len=96
Jun 29 13:41:40 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:41:40 bsdt43 kernel: exit FW state 4
Jun 29 13:41:40 bsdt43 kernel: enter FW state 4
Jun 29 13:41:40 bsdt43 kernel: Scan request: index 405 dwell 111/30/30
Jun 29 13:41:40 bsdt43 kernel: Scan 1 2.4GHz channels: 12/BCAST
Jun 29 13:41:40 bsdt43 kernel: sending command idx=13 type=26 len=96
Jun 29 13:41:40 bsdt43 kernel: Scan completed (1, 1)
Jun 29 13:41:40 bsdt43 kernel: exit FW state 4
Jun 29 

FreeBSD 7.2 - iwi error

2009-06-28 Thread Siyan Sabinov Hadzhiev

Hello List ,

I am new in this list , so if these is an old topic forgive me.I have 
successfully installed FreeBSD 7.2 to IBM T43 Laptop.I am using wireless
network with WPA key.My Laptop has Intel Pro Wireless 2200.I installed
iwi driver and firmware successfully.

I am successfully connecting to my home and ofis wireless networks with
wpa supplicant.However every 4 or 5 minutes my connection gets down and
i got iwi0: firmware stuck in state 4 , resetting  and then iwi0
device timeout  errors.These drops my connection , after that it take
30 seconds to my connection come back up.Then after 5 minutes again same
errors and these goes on.

I search a little bit on Google however find nothing usefull.

Is there anybody who faced with same problem?
And is there any solutions or upgrades for that issue.

Best Regards
Siyan

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: FreeBSD 7.2 - iwi error

2009-06-28 Thread Jose Garcia Juanino
El domingo 28 de junio a las 20:25:51 CEST, Siyan Sabinov Hadzhiev escribió:
 
 Hello List ,
 
 I am new in this list , so if these is an old topic forgive me.I have 
 successfully installed FreeBSD 7.2 to IBM T43 Laptop.I am using wireless
 network with WPA key.My Laptop has Intel Pro Wireless 2200.I installed
 iwi driver and firmware successfully.
 
 I am successfully connecting to my home and ofis wireless networks with
 wpa supplicant.However every 4 or 5 minutes my connection gets down and
 i got iwi0: firmware stuck in state 4 , resetting  and then iwi0
 device timeout  errors.These drops my connection , after that it take
 30 seconds to my connection come back up.Then after 5 minutes again same
 errors and these goes on.
 
 I search a little bit on Google however find nothing usefull.
 
 Is there anybody who faced with same problem?
 And is there any solutions or upgrades for that issue.

I have such wireless interface on a Dell Latitude D505, and I have
experienced that annoying problem many times.

Enable debug.iwi sysctl and tell us what messages you see in
/var/log/messages log file.

In my own laptop, I saw these messages before the disconnection:

X kernel: Beacon miss: XX = YY

After that I increased bmissthreshold parameter of ifconfig in rc.conf,
and the problem went away.

Hope this helps, and sorry for my poor english.

Best regards


pgppxp8Zi1uS2.pgp
Description: PGP signature