On Mon, 5 May 2008 14:25:46 -0700
"John Andersen"
On Mon, May 5, 2008 at 2:10 PM, Jerry Feldman
wrote: One issue I see is that you are using ndiswrapper and a broadcom wireless. At lease since 10.2, SuSE and other versions of Linux have a native broadcom driver. Additionally, you would need to get the latest version of fwcutter, and install the firmware, usually into /lib/firmware either under the kernel of into /lib/firmware/b43. I no longer run SuSE on my laptop (because of a work requirement to use Ubuntu), but when it ran SuSE 10.2 I found the native driver to work rather well, and more reliably than ndiswrapper. IMHO, you should run ndiswrapper only if you have no other option.
First, please don't top post on this list.
Second, I've used ndiswrapper for years and never had this problem. Its utterly reliable.
The problem is appearing at dhcp renewal time. Machine changes its name (a dhcp option that should not be used), and this causes all sorts of issues of connectivity.
Sorry for the top post. I usually try to follows the conventions of the
list.
I used to use ndiswrapper myself, but it has been implicated in many
problems over the years. The newer broadcom drivers are more reliable,
and while ndiswrapper does work, and possibly is not a problem on your
system, there are some other things I may have pointed out. Try
disabling your firewall temporarily and see if that has any affect on
the connectivity. Additionally, are you able to get the wireless back
by temporarily taking ndiswrapper down with rmmod and then bringing it
back up with insmod or modprobe. Have you used iwconfig manually.
--
--
Jerry Feldman