[opensuse] Return of wireless problem (v11.4) -- with variations
I needed totest changes in the WIRED setup for the laptop, and therefore disabled wireless operation of the ROUTER I did nothing to any wireless setting of the laptop itself. When I finished, I removed the cable connection, rebooted again, and thought to ascertain that wireless operation was again in order. It isn't. Networkmanager, for example, says that the connection to the AP is "Activating", and the signal is strong. "Enable networking" is checked. "Enable wireless" is also checked, but it is greyed out. In YaST>Network Settings>Overview, both wired and wireless controllers are listed, ONLY when in General Options, ifup is chosen. When User controlled with Networkmanager is chosen, only the wired controller is listed; I do not remember anything like that previously. Also in this case, the lower window in Overview (the description of the wireless controller) is greyed out, as are the buttons for Add. Edit, and Delete at the bottom. I have rebooted several times, without success. For that matter, when a similar problem occured recently and healed itself after a reboot as suggested by another user of this list, I am sure that the successful boot was the first I had tried; in other words, I am not convinced that restoration of wireless networking behaves altogether rationally, even in terms of officially expected behavior. Can someone see what is happening here, and offer a clue on how to fix it? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2011-03-26 at 19:36 +0200, Stan Goodman wrote:
I needed totest changes in the WIRED setup for the laptop, and therefore disabled wireless operation of the ROUTER I did nothing to any wireless setting of the laptop itself. When I finished, I removed the cable connection, rebooted again, and thought to ascertain that wireless operation was again in order.
It isn't. Networkmanager, for example, says that the connection to the AP is "Activating", and the signal is strong. "Enable networking" is checked. "Enable wireless" is also checked, but it is greyed out.
In YaST>Network Settings>Overview, both wired and wireless controllers are listed, ONLY when in General Options, ifup is chosen. When User controlled with Networkmanager is chosen, only the wired controller is listed; I do not remember anything like that previously. Also in this case, the lower window in Overview (the description of the wireless controller) is greyed out, as are the buttons for Add. Edit, and Delete at the bottom.
I have rebooted several times, without success. For that matter, when a similar problem occured recently and healed itself after a reboot as suggested by another user of this list, I am sure that the successful boot was the first I had tried; in other words, I am not convinced that restoration of wireless networking behaves altogether rationally, even in terms of officially expected behavior.
Can someone see what is happening here, and offer a clue on how to fix it?
-- Stan Goodman Qiryat Tiv'on Israel
Hi Stan, this may not be the answer that you are looking for, but try going to manage connections in networkmanager to see if your wireless connection is listed under the wireless tab. If it isn't, then click Add. When the kde control module dialog box displays, look near the top for SSID, and to the right find a button marked Scan. Click on that button to see which networks are available. Click on the network of your choice, then you will have to input the type of security and password on the previous dialog box. If nothing shows up when you scan, your radio probably isn't on. Check to make sure that the wireless on switch is on. If it isn't, turn it on and reboot. That's enuff for this post, try it and post back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 26 March 2011 22:05:57 Mark Misulich wrote:
On Sat, 2011-03-26 at 19:36 +0200, Stan Goodman wrote:
I needed totest changes in the WIRED setup for the laptop, and therefore disabled wireless operation of the ROUTER I did nothing to any wireless setting of the laptop itself. When I finished, I removed the cable connection, rebooted again, and thought to ascertain that wireless operation was again in order.
It isn't. Networkmanager, for example, says that the connection to the AP is "Activating", and the signal is strong. "Enable networking" is checked. "Enable wireless" is also checked, but it is greyed out.
In YaST>Network Settings>Overview, both wired and wireless controllers are listed, ONLY when in General Options, ifup is chosen. When User controlled with Networkmanager is chosen, only the wired controller is listed; I do not remember anything like that previously. Also in this case, the lower window in Overview (the description of the wireless controller) is greyed out, as are the buttons for Add. Edit, and Delete at the bottom.
I have rebooted several times, without success. For that matter, when a similar problem occured recently and healed itself after a reboot as suggested by another user of this list, I am sure that the successful boot was the first I had tried; in other words, I am not convinced that restoration of wireless networking behaves altogether rationally, even in terms of officially expected behavior.
Can someone see what is happening here, and offer a clue on how to fix it?
Hi Stan,
this may not be the answer that you are looking for, but try going to manage connections in networkmanager to see if your wireless connection is listed under the wireless tab. If it isn't, then click Add. When the kde control module dialog box displays, look near the top for SSID, and to the right find a button marked Scan. Click on that button to see which networks are available. Click on the network of your choice, then you will have to input the type of security and password on the previous dialog box.
If nothing shows up when you scan, your radio probably isn't on. Check to make sure that the wireless on switch is on. If it isn't, turn it on and reboot.
That's enuff for this post, try it and post back.
Hi . Is tyhis perchance a laptop ? , If so you have checked that the Wireless card is actually on does the machine have a little button to press to turn wirelesson and off for power saving if so press it . If i disable wireless on on my Compaq Presario laptop in yast ( as i have to to use the vodafone dongal ) i have to press the button to get the wireless to come back to life . Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.7-desktop KDE Development Platform: 4.5.5 (KDE 4.5.5) "release 1" 07:37 up 3 days 9:44, 5 users, load average: 0.00, 0.05, 0.03 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 27 March 2011 at 16:43:40 (GMT+2) Peter Nikolic
On Saturday 26 March 2011 22:05:57 Mark Misulich wrote:
On Sat, 2011-03-26 at 19:36 +0200, Stan Goodman wrote:
I needed totest changes in the WIRED setup for the laptop, and therefore disabled wireless operation of the ROUTER I did nothing to any wireless setting of the laptop itself. When I finished, I removed the cable connection, rebooted again, and thought to ascertain that wireless operation was again in order.
It isn't. Networkmanager, for example, says that the connection to the AP is "Activating", and the signal is strong. "Enable networking" is checked. "Enable wireless" is also checked, but it is greyed out.
In YaST>Network Settings>Overview, both wired and wireless controllers are listed, ONLY when in General Options, ifup is chosen. When User controlled with Networkmanager is chosen, only the wired controller is listed; I do not remember anything like that previously. Also in this case, the lower window in Overview (the description of the wireless controller) is greyed out, as are the buttons for Add. Edit, and Delete at the bottom.
I have rebooted several times, without success. For that matter, when a similar problem occured recently and healed itself after a reboot as suggested by another user of this list, I am sure that the successful boot was the first I had tried; in other words, I am not convinced that restoration of wireless networking behaves altogether rationally, even in terms of officially expected behavior.
Can someone see what is happening here, and offer a clue on how to fix it?
Hi Stan,
this may not be the answer that you are looking for, but try going to manage connections in networkmanager to see if your wireless connection is listed under the wireless tab. If it isn't, then click Add. When the kde control module dialog box displays, look near the top for SSID, and to the right find a button marked Scan. Click on that button to see which networks are available. Click on the network of your choice, then you will have to input the type of security and password on the previous dialog box.
If nothing shows up when you scan, your radio probably isn't on. Check to make sure that the wireless on switch is on. If it isn't, turn it on and reboot.
That's enuff for this post, try it and post back.
Hi . Is tyhis perchance a laptop ? , If so you have checked that the Wireless card is actually on does the machine have a little button to press to turn wirelesson and off for power saving if so press it
It is a laptop. Please see the very first line of my query, above.
If i disable wireless on on my Compaq Presario laptop in yast ( as i have to to use the vodafone dongal ) i have to press the button to get the wireless to come back to life .
There is no dongle involved here, and no button available to resuscitate the wireless controller.
Pete .
The machine is working again now, and (just as in the first time this phenomenon happened) I do not know what made it come to life. I am quoting most of the thread because I want the history to be clear. Before I wrote of the problem, I rebooted. Nearly every time I made a change in any setting, in my effort to make a connection, I booted again (usually by shutting down and starting again), with no result. And I'm pretty sure that there was nothing that I tried only once. The only thing that is new since I admitted defeat and asked for help is that it sat overnight. In particular, there is nothing in Mark's suggestions that I did not try (more than once) before writing. There is a difference in what brought the problem to light in the two cases. On the previous occasion, I had disabled wireless in the networkmanager icon, and then found that simply enabling it again was ineffective. This time, remembering the previous experience, I avoided monkeying with the wireless controller itself, and instead disabled wireless in the router; I think I did that while there was a live wireless connection, and only then rebooted to make the wired controller picked up the connection; perhaps that's the problem. In the future, I will be careful to make the change only in the router, and only when there is no connection, i.e., the machine is off, in hope of preventing a recurrence. But nothing would surprise me. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Mark Misulich -
Peter Nikolic -
Stan Goodman