[opensuse] Wireless setup worked once on 10.3
I've got a Dell Laptop with Broadcomm 4300 wireless card in it. The very first time I setup wireless, I installed the firmware as per instructions on the web. I managed to connect to my wireless lan (802.11g, hidden SSID, WPA-2 encryption) fine with KNetworkManager. However, since that one and only time, I've never been able to connect to my wireless LAN again. KNetworkManager keeps on telling me that it's found a "new" wireless network (*MY* wireless network) but I can't connect to it. Can anyone suggest what I need to do to get this working again (or at least switch on some debgugging so I can see where it's going wrong) ? I'm running 32bit 10.3, up-to-date with patches. Thanks, GR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed January 2 2008 14:52:18 GR wrote:
I've got a Dell Laptop with Broadcomm 4300 wireless card in it.
The very first time I setup wireless, I installed the firmware as per instructions on the web. I managed to connect to my wireless lan (802.11g, hidden SSID, WPA-2 encryption) fine with KNetworkManager.
However, since that one and only time, I've never been able to connect to my wireless LAN again.
KNetworkManager keeps on telling me that it's found a "new" wireless network (*MY* wireless network) but I can't connect to it.
I found that it takes sometimes 3 or 4 attempts to pass the 36% (or 38%?, anyway phase 2 out of 5 according to /var/log/NetworkManager) progress mark and succeed connecting. Sometimes it does it at the first attempt. I could not find a pattern and I could not find any useful information in the logs. Another annoying behaviour is that KNetworkManager sometimes does not "see" my home network nor the neighbour's, only some "default" (we broadcast the SSID). I tried to wait a little to see if my network was not announcing itself immediately, but no luck. After switching to Windows to verify that the signal was good and coming back, KNetworkManager "saw" all the networks and connected right at the 2nd try. I am still seeing if there is a pattern, so I know how to report a bug. -- Carlos FL "It is not worth an intelligent man's time to be in the majority. By definition, there are already enough people to do that." - G. H. Hardy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 02 January 2008 4:18 pm Carlos F. Lange wrote:
Another annoying behaviour is that KNetworkManager sometimes does not "see" my home network nor the neighbour's, only some "default" (we broadcast the SSID). I tried to wait a little to see if my network was not announcing itself immediately, but no luck. After switching to Windows to verify that the signal was good and coming back, KNetworkManager "saw" all the networks and connected right at the 2nd try.
Carlos, I have the same wifi card on two machines. Similar problem to yours, It appears the card is not being powered on by the LInux drivers setup. Booting to xp allows the card to be powered up as evident by the little lite on the laptop. Have you checked your var/log/messages? Also look at var/log/NetworkManager. Whenever mine fails the message in this one says activation of the card failed. Another thing that might make a difference is to disable the Ipv6 stuff. I eventually gave up and started using a usb wireless with 10db antenna. It uses the Zydas ZD1211 firmware provided by suse. I figured we shouldn't have to reboot to windows to restart the darned network card. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed January 2 2008 21:46:16 Richard Atcheson wrote:
Carlos, I have the same wifi card on two machines. Similar problem to yours, It appears the card is not being powered on by the LInux drivers setup. Booting to xp allows the card to be powered up as evident by the little lite on the laptop.
My case is different, because I see the light on and it is obviously finding that "default" network from somewhere. But today I couldn't test it because it worked right at boot-up. Like the proverbial TV set when you called the technician...
Have you checked your var/log/messages? Also look at var/log/NetworkManager. Whenever mine fails the message in this one says activation of the card failed.
I remember looking at them when connection attempts failed, but not when the card was not seeing the WLAN. I will report back the next time. -- Carlos FL "It is not worth an intelligent man's time to be in the majority. By definition, there are already enough people to do that." - G. H. Hardy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 3 Jan 2008 08:22:18 GR wrote:
I've got a Dell Laptop with Broadcomm 4300 wireless card in it.
The very first time I setup wireless, I installed the firmware as per instructions on the web. I managed to connect to my wireless lan (802.11g, hidden SSID, WPA-2 encryption) fine with KNetworkManager.
However, since that one and only time, I've never been able to connect to my wireless LAN again.
KNetworkManager keeps on telling me that it's found a "new" wireless network (*MY* wireless network) but I can't connect to it.
Can anyone suggest what I need to do to get this working again (or at least switch on some debgugging so I can see where it's going wrong) ?
I'm running 32bit 10.3, up-to-date with patches.
Thanks,
GR
I had exactly the same problem using KNetworkManager with a Broadcom card (bcm4318). After fighting with it for too long, I dumped KNetworkManager and went back to using the legacy ifup method. Worked faultlessly ever since. It seems to me that the only reason for KNetworkManager is if you need to roam between wireless networks (e.g. using public hot-spots or work/home situations). Where you're only using one wireless network ifup seems to be much more reliable, at least with the Broadcom chipsets. Cheers, Rodney. -- =============================================== Rodney Baker VK5ZTV rodney.baker@optusnet.com.au =============================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 3 Jan 2008 17:00:58 +1030 Rodney Baker <rodney.baker@optusnet.com.au> wrote:
On Thu, 3 Jan 2008 08:22:18 GR wrote:
I've got a Dell Laptop with Broadcomm 4300 wireless card in it.
The very first time I setup wireless, I installed the firmware as per instructions on the web. I managed to connect to my wireless lan (802.11g, hidden SSID, WPA-2 encryption) fine with KNetworkManager.
However, since that one and only time, I've never been able to connect to my wireless LAN again.
KNetworkManager keeps on telling me that it's found a "new" wireless network (*MY* wireless network) but I can't connect to it.
Can anyone suggest what I need to do to get this working again (or at least switch on some debgugging so I can see where it's going wrong) ?
I'm running 32bit 10.3, up-to-date with patches.
Thanks,
GR
I had exactly the same problem using KNetworkManager with a Broadcom card (bcm4318). After fighting with it for too long, I dumped KNetworkManager and went back to using the legacy ifup method. Worked faultlessly ever since.
It seems to me that the only reason for KNetworkManager is if you need to roam between wireless networks (e.g. using public hot-spots or work/home situations). Where you're only using one wireless network ifup seems to be much more reliable, at least with the Broadcom chipsets.
Cheers, Rodney.
Ok... at the risk of getting scolded again for suggesting this, I've got a Dell Inspiron (AMD 64 Athlon X2) with the Broadcom wireless chipset using the bcm43xx drivers. This chipset has native support in Suse 10.3, however not native enough to work out of the box. So, following experience gained while using Fedora Core 7 on an older Dell Inspiron I went to the trusted ndiswrapper. http://ndiswrapper.sourceforge.net/joomla/ OpenSUSE ndiswrapper info http://software.opensuse.org/search {keyword: ndiswrapper} Be sure to do as much reading about how to setup and use this, because it will definitely benefit you later the more you know about how to use this tool. Below is the script I use to initialize my wireless using ndiswrapper: -------------------- #!/bin/sh echo 'Starting Home WLAN' /sbin/modprobe -r bcm43xx echo 'Setting Dependency Mod...' /sbin/depmod -a echo 'Mod Probing ndiswrapper...' /sbin/modprobe ndiswrapper #echo 'Scanning For All Wireless LAN Access Points...' #/sbin/iwlist eth1 scan echo 'Setting Specific Wireless Network Access Point...' /usr/sbin/iwconfig eth1 essid <your WAP essid> #echo 'Scanning For Specific Access Point...' #/usr/sbin/iwlist eth1 scan echo 'Setting Wireless LAN To Managed Mode...' /usr/sbin/iwconfig eth1 mode Managed echo 'Setting WEP Encryption Key...' /usr/sbin/iwconfig eth1 key restricted <insert your wep key here> echo 'Setting Specific Wireless Network Access Point...' /usr/sbin/iwconfig eth1 essid DeltaFlyer echo 'Bring Up Wireless LAN Interface...' #/sbin/ifconfig eth1 up /sbin/dhclient eth1 #/sbin/dhcpcd eth1 --------------------- -- Mark "Drunkenness is not an excuse for stupidity. If you're stupid when you're sober then that's one thing, but if you're sober when you're stupid, then you're just plain stupid!" ============================================== Powered by CentOS5 (RHEL5) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos F. Lange -
GR -
Mark Weaver -
Richard Atcheson -
Rodney Baker