network manager doesnt connect

hello I have a intel 3945ABG PRO/wireless adapter and I cant connect to the internet I have all the drivers for this adapter (it worked fine when I first installed suse now I try to connect and just get nothing like I didn’t even try to connect) so I don’t know what the problem would be…I found a workaround with kwifimanager but now that doesn’t even work…still just nothing (or at best I’ll “get the gear turning” but always WLAN0 failed to connect,and even this is rare.) I also at one point had compat wireless installed but as it prevented even scanning networks I uninstalled it. any ideas?

I have the same device. su terminal and do lspci -v
I get the following.

Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
        Subsystem: Intel Corporation ThinkPad R60e/X60s                                               
        Flags: bus master, fast devsel, latency 0, IRQ 220                                            
        Memory at dfcff000 (32-bit, non-prefetchable) [size=4]                                       
        Capabilities: [c8] Power Management version 2                                                 
        Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable+               
        Capabilities: [e0] Express Legacy Endpoint, MSI 00                                            
        Capabilities: [100] Advanced Error Reporting                                                  
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSVoil-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil-
                CESta:  RxErr- BadTLP+ BadDLLP- Rollover- Timeout- NonFatalErr-                                   
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-                                   
                AERCap: First Error Pointer: 14, GenCap- CGenEn- ChkCap- ChkEn-                                   
        Capabilities: [140] Device Serial Number 3a-bc-9c-ff-ff-3c-1f-00                                          
        Kernel driver in use: iwl3945                                                                             
        Kernel modules: iwl3945 

So are you using knetworkmanager now? I am. I use the kde4 desktop but the networkmanager is actually from kde3

What about encryption? What are you using?[/size]

alright here’s the output of mine, looks pretty much the same as yours…

05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Subsystem: Intel Corporation PRO/Wireless 3945ABG Network Connection
Flags: bus master, fast devsel, latency 0, IRQ 219
Memory at d0100000 (32-bit, non-prefetchable) [size=4]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable+
Capabilities: [e0] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSVoil-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
AERCap: First Error Pointer: 14, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140] Device Serial Number 7e-3a-20-ff-ff-de-18-00
Kernel driver in use: iwl3945
Kernel modules: iwl3945

and yes I’m (trying) to using knetworkmanager for kde3 (and for 4,for that matter),but I always get Wlan0 failed or something to that effect, the only way that I’ve found to work, is to use ifup with kwifimanager.[/size]

I have switched to the kde4 networkmanager now, but the kde3 one used the same settings.
http://thumbnails18.imagebam.com/4488/657c4144876656.gif](http://www.imagebam.com/image/657c4144876656/)

That shows my security method, seems to work well.
My router is configured with address reservation and my wireless MAC is in the trusted devices section.

oh yes thats what mine looked like it just does nothing when I try to connect…also is there anyway to connect to wireless networks using the terminal? kwifimanager for some reason doesn’t like to pick up available networks (have to hit "scan for networks like 50 times before it finally will while “iwlist scan” works great) and one more question is it normal for me, while using ifup to have to go into yast,network settings,and click ok everytime I want to connect to an available network?

I suspect you are just missing something. Everything sounds in place. Check again. Try deleting any saved connections and re-enter them.

I’ve got the same problem. I have installed a version from LXF magazine along my primary Ubuntu system. I have no problem with Ubuntu but with openSUSE the network manager fails to connect. It can see the network and when I tried ifup method and it worked fine, but I would prefer the network manager. Any suggestions?

Same with me. Networkmanager kde 3.5 does see the wifi network but does not connect.

Hi, I had the same problem with NM from both versions and before and after Kernel updates. I am under opensuse 11.1.
I got one time connected the wireless using NM, by setting the network with visible SSID and no encription…
Anyway, after spending days on it, and reading about this common problem with NM, I just:

  1. connected temporarily with wire
  2. used Yast, selected Network settings, under global options, disabled NM by selecting “traditional setting with ifup”.
  3. removed network manager and all its KDE clients.
  4. installed WICD from the opensuse build service:
    Software.openSUSE.org

and restarted. WICD asks for root password everytime you startup but it is a small price for having a reliable wifi manager. Many distros are using WICD instead of NM because it still has too many issues to be solved. The password request by wicd, has also a work around that is to add the user to the group netdev, but I do not have that group listed. Just in case you have it, do:

usermod --append --groups netdev <yourusername>

hope this helps you the way it did to me.
regards

Hello, I tried to follow your hint. Unfortunately it got worse (or better stays the same).
When I try to launch the first time WICD when starting up it complains:
Could not connect to wicd’s D-Bus interface. Check the wicd log for error messages.
The program then closes. If you restart it, it starts normally and then trying to connect to the wireless network it complains:

Unsuccessful connection. Impossible to acquire IP address.
This is the same problem as with network manager. As with NM I can connect without trouble through eth0. This is true either for NM or for WICD.

I did not find any error log messages from WICD.
Both programs see the WLAN well, they try both to connect and both report the same errors. Windows machines do connect on the network.
This very notebook does connect trouble free to WPA/WPA2 networks.
I had Wep connection problems before. Sometimes it helped to fiddle with the alfanumeric/hex/password choice. But this time definitively not.

Any suggestion?

update:
Now I tried to remove everything, to install again. I tried also some suggestions [debian/fso] pyphonelog crashes on start, org.freedesktop.DBus.Error.AccessDenied](http://lists.openmoko.org/pipermail/support/2009-January/004522.html)

Now it still complains about dbus. Then when you restart it does connect to the cable.
It does not connect to wireless.
I then did put: use global dns server into the preferences.
It still says it does not connect, because of IP but below in the program it states that it actually IS connected…and has even the IP adress. Pages do not charge though.
What do I have to set as global dns server? Suggestions?

Hi,

Just had a curious problem. Using 11.2 Gnome worked very fine but, when used the KDE version, just connected but with “!” flag. Some days ago just tried again. Starting with Live 11.2 KDE and continued to show the “!” flag but connected as well. Installed on the computer and continues working very fine. A real mistery.

In any case just check if you are typing the password as ASCII when the system ask you for hex key. It’s very usual start to type the ASCII password instead of the hex version and confuse the 40 / 128 bits.

Regards.