Go Back   openSUSE Forums > Archives > SLS Archives > ARCHIVES - SuSE Linux > ARCHIVES - Network & Security > ARCHIVES - Wireless Networking
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - Wireless Networking Support for wireless networking in suse.

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 08-May-2008, 10:01
J Seglem
Guest
 
Posts: n/a
Default

After setting up the wireless connection successfully I am not able to keep it.

For example, I close the lid on my laptop at night and open again in the morning and the network is not connected. If I click through YaST-Network Configuration I can see the details are there, but after clicking finish it does not connect. I found if I go into a terminal and SU the command iwconfig eth1 essid <networkname> I am able to connect.

Any thoughts how to get a persistent connection? Thanks.

Misc facts
3 other laptops-2 macs and a Zonbu stay connected just fine.
The laptop with the issue is a brand new Lenovo R61 with SUSE 10
  #2 (permalink)  
Old 08-May-2008, 10:45
broch
Guest
 
Posts: n/a
Default

what sort of action is caused by closing lid?
power off
suspend to disk
suspend to ram
turn off monitor
nothing
  #3 (permalink)  
Old 08-May-2008, 12:11
thestig
Guest
 
Posts: n/a
Default

Quote:
After setting up the wireless connection successfully I am not able to keep it.

For example, I close the lid on my laptop at night and open again in the morning and the network is not connected. If I click through YaST-Network Configuration I can see the details are there, but after clicking finish it does not connect. I found if I go into a terminal and SU the command iwconfig eth1 essid <networkname> I am able to connect.

Any thoughts how to get a persistent connection? Thanks.

Misc facts
3 other laptops-2 macs and a Zonbu stay connected just fine.
The laptop with the issue is a brand new Lenovo R61 with SUSE 10
[/b]
as i think broch is hinting at, some of the 'close lid functions' can disable the wireless. what if it's something like a suspend command at lid close, you may want to tell it to do nothing, and just lock the session before you close the lid and then try again.
  #4 (permalink)  
Old 08-May-2008, 13:09
J Seglem
Guest
 
Posts: n/a
Default

I did play with the Power Management window. It seems to have just a few options (Acoustic is one). I'll check there when I get home and on the machine. I'll see if I can dig deeper on what happens. Nothing had jumped out at me initially. I'll post my findings. Appreciate the help.
  #5 (permalink)  
Old 08-May-2008, 20:16
J Seglem
Guest
 
Posts: n/a
Default

I checked power options and it is set to Performance for both battery and AC. Closing the lid seems to put the laptop to sleep, though I see no where to turn that setting off

To reconnect I have to follow these steps:
$ iwconfig eth1 essid "networkname"
then open Network Card and click on my wireless card and hit edit. The correct info is all there. I hit finish and after a moment I'm connected.

Card: Intel PRO/Wireless 3945 ABG
Connection: Verizon FIOS
  #6 (permalink)  
Old 09-May-2008, 00:44
thestig
Guest
 
Posts: n/a
Default

Quote:
I checked power options and it is set to Performance for both battery and AC. Closing the lid seems to put the laptop to sleep, though I see no where to turn that setting off

To reconnect I have to follow these steps:
$ iwconfig eth1 essid "networkname"
then open Network Card and click on my wireless card and hit edit. The correct info is all there. I hit finish and after a moment I'm connected.

Card: Intel PRO/Wireless 3945 ABG
Connection: Verizon FIOS
[/b]
you have exactly the same card as me. and i'm having no problems. on the battery icon (kpowersave) right click on it, configure kpowersave>general settings tb>button events. will be clear to you then. if both ac adapter and battery are performance you only need to change these for performance. this should do the trick. if you are still getting problems, what driver are you using for wireless, i use ipw3945, though this doesn't last with a network with suspend/resume cycles. if your network has this you need the iwlwifi drivers. but stick with ipw3945 for now and try the button events in kpowersave. may also want to stop suspend etc after x amount of time, as if you close lid and nothing happens, but it's set to suspend to ram after 2hours, you still might get problem

hope this helps, let us know.
  #7 (permalink)  
Old 10-May-2008, 05:32
J Seglem
Guest
 
Posts: n/a
Default

I had clicked through buttons/sliders and set the computer to "Never" go to sleep. I'll try it a few times. The good thing I have found is that if I do shut down and reboot everything does reconnect nicely. I had made an assumption that sleep or shut down would cause the same issue. That appears not to be true.

Thanks!
  #8 (permalink)  
Old 10-May-2008, 07:00
thestig
Guest
 
Posts: n/a
Default

Quote:
I had clicked through buttons/sliders and set the computer to "Never" go to sleep. I'll try it a few times. The good thing I have found is that if I do shut down and reboot everything does reconnect nicely. I had made an assumption that sleep or shut down would cause the same issue. That appears not to be true.

Thanks!
[/b]
ok that is good, i will be surprised if that does not solve your problem
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2