Network Manager 0.7.0 not connecting to Wireless Networks

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

So it is linux fault and not network-manager.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Correct that would be Linux.
If i remember correctly now when i installed Hardy i had to download updates first before i could connect on Wireless. I think i was given a proprietary driver by the name of lo i think.
Heres the requested info.

1. "uname -a" = Linux Kaizer 2.6.26-5-generic #1 SMP Sun Aug 10 20:28:44 UTC 2008 x86_64 GNU/Linux

2. "dmesg.log" =

2. "dmesg.log" = dont get anything, just starts a new line.

3. "sudo lspci -vvnn > lspci-vvnn.log" = same as 2.

"dmesg > dmesg.log" writes the output of dmesg to the file dmesg.log in the current directory. So if you just opened a terminal and runs "dmesg > dmesg.log" you will find the file in your home directory. Same with lspci-vvnn.log. This file should be in the same directory.

Oh ok ,sorry bout that. have attached the file

lspci-vvnn.log

Ok i now have the bcml5.inf driver installed and my Wireless controller seems to be working but im still not able to connect

....:~$ ndiswrapper -l
bcmwl5 : driver installed
 device (14E4:4315) present

r:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
          Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
          Bit Rate:54 Mb/s Tx-Power:32 dBm
          RTS thr:2347 B Fragment thr:2346 B
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

r:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1d:72:35:92:70
          inet addr:24.31.148.233 Bcast:24.31.149.255 Mask:255.255.254.0
          inet6 addr: fe80::21d:72ff:fe35:9270/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:50618 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9717 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18540899 (18.5 MB) TX bytes:1301828 (1.3 MB)
          Interrupt:16

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:806 errors:0 dropped:0 overruns:0 frame:0
          TX packets:806 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:40832 (40.8 KB) TX bytes:40832 (40.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:1f:e1:11:ea:77
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17 Memory:f0300000-f0304000

Uinstalled that Windows driver, did updates today and the wl restricted driver came through which got my card working again and am connected with wireless now however is seems the problem is with WAP and WEP. Me and a couple others had to disable it.

WPA and WEP that was.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Solved with 2.6.27-2