Anyone have an idea? I know this has been dead for some time but I have now figured out that my signal is not readable when I am downloading large files (IE iso images). I workaround I have been using is d4x (downloader for X) so that I can limit my download speeds and keep from getting the errors... 404 On Sun, 13 Jun 2004 21:27:29 -0400, Matt Burke <textbox@gmail.com> wrote:
I've also been getting this:
Jun 13 21:10:55 slacker kernel: p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped. Jun 13 21:11:59 slacker kernel: p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped. Jun 13 21:13:03 slacker kernel: p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped. Jun 13 21:14:07 slacker kernel: p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped. Jun 13 21:15:12 slacker kernel: p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
On Thu, 10 Jun 2004 03:56:37 -0400, Matt Burke <textbox@gmail.com> wrote:
I'm running SUSE 9 pro on a Toshiba Satellite 1115-S123, my wireless card is a Microsoft Broadband Networking MN-520 (prism chipset), and my access point is a D-Link DI-514. In Gnome, I have the wireless applet in the toolbar to show my current signal strength. From time to time, the applet will show N/A and when I check /var/log/messages I get this (ignore the old dates):
May 31 13:00:55 slacker kernel: prism2sta_mlmerequest: Failed to read wlan0 statistics: error=-61 May 31 13:00:57 slacker kernel: prism2sta_mlmerequest: Failed to read wlan0 statistics: error=-61 May 31 13:00:58 slacker kernel: NETDEV WATCHDOG: wlan0: transmit timed out May 31 13:00:58 slacker kernel: hfa384x_tx_timeout: Implement me. May 31 13:00:59 slacker kernel: prism2sta_mlmerequest: Failed to read wlan0 statistics: error=-61 May 31 13:01:03 slacker last message repeated 2 times May 31 13:01:03 slacker kernel: NETDEV WATCHDOG: wlan0: transmit timed out May 31 13:01:03 slacker kernel: hfa384x_tx_timeout: Implement me. May 31 13:01:07 slacker kernel: prism2sta_mlmerequest: Failed to read wlan0 statistics: error=-61
When this happens I lose all connectivity to the access point. I cannot get wlan0 back up using rc network restart - I have to go in to YaST, change the settings then change them back to what they were, and apply the settings. As far as I knew YaST was basically doing the rc network restart as I was not changing any settings. If YaST cannot bring wlan0 back up I have to restart.
On every boot I must also manually bring wlan0 up and add a route. I made a script for this but it's a real pain in the butt. I guess my questions are:
Does anyone have an idea what is going on with wlan0 and why the card cannot read the signal?
Is there anyway I can get my wlan0 IP and route to stay even after reboot?
Any info or help would be great, thanks in advance =]
Matt
(By the way, I did get great joy from contacting Microsoft's Broadband Networking support and thanking them for using the Prism chipset in there cards - helping me get wireless working in Linux)
-- 404 - Textbox Networks