[opensuse] Wireless Network Problem
Sometimes, that is every day throughout the day, my wireless network on Latitude D820 under Suse 10.2 starts beeping and /var/log/messages files says it is loosing a link status, then acquires again, then looses again, each time giving a beeb. What is causing this? No one else running Windows has the problem and when I dual boot into WinXP, it also does not do it. If I issue ifplugd -i eth1 -k, it stops it, but of course, stopping the network also. I do a ifplugd -i eth1 and route defualt gw 192.168.11.1 and it wll be OK for awhile. Is there anyway to turn off the beeping and any suggestions for this strange behaviour? Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-01-30 at 22:12 +0800, Art Fore wrote:
Sometimes, that is every day throughout the day, my wireless network on Latitude D820 under Suse 10.2 starts beeping and /var/log/messages files says it is loosing a link status, then acquires again, then looses again, each time giving a beeb. What is causing this? No one else running Windows has the problem and when I dual boot into WinXP, it also does not do it. If I issue ifplugd -i eth1 -k, it stops it, but of course, stopping the network also. I do a ifplugd -i eth1 and route defualt gw 192.168.11.1 and it wll be OK for awhile. Is there anyway to turn off the beeping and any suggestions for this strange behaviour?
Art
I have same laptop, wireless works fine at home (dont use it that much at work). What I have found that the my link breaks every 30min by a reassigning of IP address (DHCP), but my wireless router (and DHCP server) reassign timeout is set max (and not 30min). I dont have beeping (I think, my speakers are on mute most of the time, will check tonight) No solution yet. Check your /var/log/NetworkManager log. E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-01-30 at 16:17 +0200, Hans van der Merwe wrote:
On Tue, 2007-01-30 at 22:12 +0800, Art Fore wrote:
Sometimes, that is every day throughout the day, my wireless network on Latitude D820 under Suse 10.2 starts beeping and /var/log/messages files says it is loosing a link status, then acquires again, then looses again, each time giving a beeb. What is causing this? No one else running Windows has the problem and when I dual boot into WinXP, it also does not do it. If I issue ifplugd -i eth1 -k, it stops it, but of course, stopping the network also. I do a ifplugd -i eth1 and route defualt gw 192.168.11.1 and it wll be OK for awhile. Is there anyway to turn off the beeping and any suggestions for this strange behaviour?
Art
I have same laptop, wireless works fine at home (dont use it that much at work). What I have found that the my link breaks every 30min by a reassigning of IP address (DHCP), but my wireless router (and DHCP server) reassign timeout is set max (and not 30min). I dont have beeping (I think, my speakers are on mute most of the time, will check tonight)
No solution yet.
Check your /var/log/NetworkManager log.
The beeb comes through eventhough I have the headphones plugged in and the volumn set to minimun. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Quoting Art Fore
Sometimes, that is every day throughout the day, my wireless network on Latitude D820 under Suse 10.2 starts beeping and /var/log/messages files says it is loosing a link status, then acquires again, then looses again, each time giving a beeb. What is causing this? No one else running Windows has the problem and when I dual boot into WinXP, it also does not do it. If I issue ifplugd -i eth1 -k, it stops it, but of course, stopping the network also. I do a ifplugd -i eth1 and route defualt gw 192.168.11.1 and it wll be OK for awhile. Is there anyway to turn off the beeping and any suggestions for this strange behaviour?
Just because Windows doesn't alert you to the problem, doesn't mean it isn't happening there too. I had a problem with my hard drives that took me over a year to solve. The problem showed up as CRC errors in syslog. No lost data, ever. Windows never said a word. The problem was the cables, replacing them with $40 80 wire ATA 100 cables and dropping the speed back to ATA 100 from ATA 133 solved the problem. So it wasn't a driver problem and must have been happening in Windows too. Note: cheap ($7), shielded ATA 133 cables did not solve the problem. Dropping from ATA 133 to ATA 100 reduced my disk throughput by 10% according to Bonnie. I can live with it. Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Art Fore
-
Hans van der Merwe
-
Jeffrey Taylor