I'm closing this bug basing on your last comments.
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Invalid
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received this bug notification because you are a member of Ubuntu
Bugs,
I believe we can mark this as Invalid as this is not an issue. I was one
of the commenters at the time and I can vouch the hardwre works well.
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received this bug notification because you are a memb
I don't have this problem in 10.04 using the same hardware referenced in
comment #21 above.
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There have been many changes in Ubuntu since that time you reported the
bug and your problem may have been fixed with some of the updates. If
you could test the current Ubuntu development version (10.04), this
would help us a lot. If you can test it, and it is still an issue, we
would appreciate if
I am getting this behaviour with Gutsy and an IPW3945, is there a more
appropriate (not ndiswrapper) bug to report this behaviour too? Also
what information should I include. Thanks.
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received th
Same here, it works fine for me now with with Ubuntu Gutsy and ipw3945,
iwl4965 and ath_pci cards without having to do "iwconfig eth1 essid x
mode managed".
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received this bug notification because
Now with Kubuntu Gusty and I don't experience this bug anymore, i.e my
bcm4318 connects automaticaly with knetworkmanager, without having to
rely on the "iwconfig eth1 essid x mode managed" command.
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
I was installing Xubuntu Gutsy on an HP Compaq v5000 with a bcm4318
wireless chipset; I encountered the same problem and was successful with
mlaverdiere 's fix. (The problem appeared to be the same on other
versions of Gutsy as well.) So the bug is still alive . . .
--
NetworkManager finds wire
confirmed on latitude d800, bcm4306, ndiswrapper
just a few tips to complete mlaverdiere tricks :
instead of creating a new init.d script, just add the commands in /etc/rc.local
much easier than adding new init.d and rc links there ;)
regarding /etc/acpi/ stuff, the file '99-bcm43xxactivation' n
Hi,
I am experiencing this in an X60s running i386 Gutsy with an Intel
ipw3945 card. Network manager does not associate. If I disable Network
Manager wireless, do:
sudo iwconfig eth1 essid x mode managed
then re-enable Network Manager wireless, it associates properly.
--
NetworkManager finds
Does anyone have any experience trying mlaverdiere's fix on the the BCM4309
Vers. 2 chipset? I have an older Copmpaq 2100 laptop (2108US) with a similar
problem (on Feisty). I have limited experience with networking hardware, so
any suggestions and instructions you might have would be apprecia
I just want to clarify the item 3 of my previous comment above (#17), in
case it might be useful for someone.
In order to automate the workaround to make ndiswrapper + network-
manager works with my bcm43xx card, I have created and **made
executable** the following files:
File #1: /etc/init.d/b
I have the problem with network manager gnome Ubuntu Feisty i follow
this
https://help.ubuntu.com/community/WifiDocs/Device/Broadcom_BCM4311_rev_01_(ndiswrapper)?highlight=(WifiDocs%2FDevice
#head-f744e28e6c78eb83d22be77819b130016a8e51f3 to install driver
Broadcom_BCM4311 and network manager won't
Here are my findings related to this bug on Feisty, with a bcm4318 card
and network-manager:
1. Upgrading from Edgy to Feisty lead me to a regression with respect to
this bug, i.e. things were working right with Edgy, but not with Feisty
as far as ndiswrapper (or bcm43xx) + network-manager are con
Yep same problem here with Dell Inspiron 2200 using Broadcom 4318 --
does anyone know when a fix will be out for this? Turning on and off the
wireless card from the notebook does not help for me. Attempting to use
the wicd/ndiswrapper 1.4.2 suggestion - will report back if it fixes the
problem.
--
Ram (and others), can you confirm whether you are actually seeing
symptoms more or less like those that I describe in bug 73759?
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received this bug notification because you are a member of Ubuntu
B
i can confirm this on a Dell D410 with ndiswrapper and the following
chipset:
02:03.0 Network controller: Broadcom Corporation BCM4311 [AirForce 54g]
802.11a/b/g PCI Express Transceiver (rev 02)
wifi-radar is also working ok'ish. Not perfect as soemtimes it wont get
the IP, etc... but works 80% o
I'll second using Wicd as a temporary fix.
On 4/23/07, bedfojo <[EMAIL PROTECTED]> wrote:
>
> I found a workaround: compile and install the latest version of
> ndiswrapper (1.42) from its website. Use wicd instead of network-
> manager. All works perfectly now.
>
> --
> NetworkManager finds wirele
I found a workaround: compile and install the latest version of
ndiswrapper (1.42) from its website. Use wicd instead of network-
manager. All works perfectly now.
--
NetworkManager finds wireless network, does not connect
https://bugs.launchpad.net/bugs/85468
You received this bug notification b
I can also confirm this bug as a regression in Feisty from Dapper.
I am running an Acer 3613WLMi laptop with the Broadcom 4318 chipset.
Under Dapper, using ndiswrapper and the Acer bcmwl5 driver, I could
connect first time and quickly to my home WPA network.
Under Feisty, on a cold boot, network
I'm not sure if my problem is related to this bug but here goes: I'm the
owner of an old Toshiba Satellite Laptop. Since it has no internal WLAN
card I resort to an external USB stick, namely the Fritz! WLAN USB Stick
(see:
http://www.avm.de/en/press/announcements/2006/2006_07_11.php3?linkident=meh
I have same problem on an IBM Thinkpad T30 with Prism2 running hostap
driver.
I see that NM disconnects from my WPA network with "sudo iwconfig wlan0
essid x mode managed", but then fails to connect to an unencrypted
network -- in fact, it pretty much freezes the desktop, as seen here:
https://bu
I can confirm it with a D-Link DWL-G122 USB device. The LED flicker on
startup showing various connects and disconnects until KNetworkmanager
gives up. Simply plugging out, reinserting the stick and network-manager
connects after a few seconds to a WPA secured network.
--
NetworkManager finds wir
I am also having the same issue on a bcm4318 which is the card that
comes in my compaq m2000
I can't log in to the network. I can see the essid and even if I type a
wrong password it will detect it as wrong password and prompt for a new
one. I am on feisty beta.
--
NetworkManager finds wireless
I am seeing similar issues when using Network Manager and the Linux-
native bcm43xx driver, described in bug #73759. I am wondering if my
issue might be due to Network Manager's flawed disassociation logic that
you (Scott) speak of.
I'm trying to understand how the NM bug mentioned is relevant...
I tracked it down. Basically, disassociation doesn't occur properly.
NM has incorrect disassociation logic, but because of how wpa_supplicant
interacts it doesn't matter.
wpa_supplicant does an proper disassociation, but the ndiswrapper driver
doesn't handle it properly.
So, in short, it's a bug
After running the supplied command line, Network Manager attached to the
wireless network without resorting to hardware buttons.
Is there anything I can do or test to aid in your ndiswrapper /
wpa_supplicant investigation?
- Jonathan
On 3/8/07, Scott Robinson <[EMAIL PROTECTED]> wrote:
>
> Inste
Instead of reseting the wireless card, can you please try (in a
terminal):
sudo iwconfig ethX essid x mode managed
Replacing "ethX" with the proper interface. Leave the "essid x" as
written. Afterward, then select the network.
There is a bug in ndiswrapper / wpa_supplicant I am investigating w
** Changed in: Ubuntu
Sourcepackagename: None => network-manager
--
NetworkManager finds wireless network, does not connect
https://launchpad.net/bugs/85468
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Should have mentioned: This is on Feisty.
--
NetworkManager finds wireless network, does not connect
https://launchpad.net/bugs/85468
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
30 matches
Mail list logo
