Bugzilla – Bug 417335
knetworkmanager doesn't find wireless networks
Last modified: 2008-08-18 08:21:41 UTC
On openSuse 11.0 the knetworkmanager doesn't find wireless networks. If it does find them, it displays the signal strength incorrectly. I am using 11.0 32 bit, and am comparing it to the normal and reliable operation it had on openSuse 10.3 32 bit. On 11.0 I can have the laptop about 3 feet away from the wireless router and it will display a signal strength of 6 or 7 when it should be full scale. It won't pick up networks I know are operating nearby and can access. This is the same problem detailed for Opensuse 64 bit systems at this bug report: https://bugzilla.novell.com/show_bug.cgi?id=416508&GoAheadAndLogIn=1
On the opensuse mailing list after I submitted this bug, it was reported by another user that he found that if one installs compat-wireless rpms from the build service that the knetworkmanager operates normally. I installed the compat-wireless rpms from the repos via yast, instead of from the build service and knetwork manager seems to indicate more normal operation now as it displays the signal strength for the wireless network in my home. I haven't been able to test its range sensitivity other than there are a couple of my neighbor's wireless networks that normally indicate a 6-7 signal strength that I could usually pick up with knetwork manager when I had 10.1, 10.2, or 10.3 installed. I am not able to indicate them now with 11.0 installed, but I also changed the driver on the wireless with the 11.0 installation. On the 10.x installations, I used a WinXP driver with ndiswrapper. That didn't work on the 11.0 installation, so I changed to madwifi as the wireless driver.
(In reply to comment #0 from Mark Misulich) > This is the > same problem detailed for Opensuse 64 bit systems at this bug report: > > https://bugzilla.novell.com/show_bug.cgi?id=416508&GoAheadAndLogIn=1 If this is the same issue (regardless of the architecture) there is no need to have two open bugs. *** This bug has been marked as a duplicate of bug 416508 ***