Use traditional ifup instead of Network Manager. SuSE 10.1 - Use the wlan kernel & install the firmware upgrade.(On my IBM T60, this is a little switch near the IR port, on other systems it may be an ACPI keyboard switch like Fn+F5 or something you can enable or disable in the BIOS.) You may still have problems on some systems if the "kill switch" is turned on. SuSE 10.1/2 - use the Extras non-oss CD disk 6 or install the packages ipw-firmware and ipw3945d from a non-oss repository.To connect to get this fix using Network Manager, you will need to turn the wireless radio on and off using the hardware switch on your computer until Network Manager finally connects (tip: turn radio off, wait until NM shows no connection icon, turn radio on, once the connecting icon appears, wait about 5-6 sec., and if no progress is made, turn radio off until no connection icon appears, repeat until connection progress is made, then wait for connection). The traditional "ifup" process is reported to work as an alternative to the GUI Network Manager. You can install the update by adding " " as a software repository, then in YaST Software Management, search for ipw3945, and update your kernel module (reboot to take effect). There is an upstream fix, but it hasn't made it into the regular updates. SuSE 10.3 - Works, but there is a bug.Other than that standard network manager seems normal. May need traditional ifup since sometimes card misses available networks. On SuSE 10.1 need to use the Extras CD disk 6. On SuSE 10.1 and 10.2, the ipw-firmware package from the Non-OSS add-on CD (or non-oss repo) is required.On SuSE 10.0, there could be a problem using that device in conjunction with 802.11b routers.WPA not tested.įor suse 10.2 to work, the ipw-firmware package from the Non-OSS add-on CD (or non-oss repo) is required. Works without problems on openSuSE 10.2 圆4 and 10.3 圆4 using the win2k_圆4 driver and ndiswrapper. Non of the Winxp/95 drivers that I have tried worked with ndsiwrapper. Works perfectly with madwifi on both 10.1 and 10.2 - Minimal setup if any.Install bcm43xx-fwcutter from DVD or OSS-repo and run as root the included script: install_bcm43xx_firmware from the /usr/sbin directory.ġ0.1 Works with ndiswrapper(64bit drivers also work with ndiswrapper). For SL 10.1 and 10.2: Here is a workaround using ndiswrapper or madwifi.ġ0.2 Native kernel driver. (SLES/NLD 9 - i386 only) needs nongpl kernel package. SL 10.1: Here is a workaround using ndiswrapper or madwifi. SL 10.2-10.3: Here is a workaround using ndiswrapper or madwifi. On some machines, when supended to disk, it won't connect anymore until next reboot. Install it using the ndiswrapper (not recommended) or the madwifi driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |