@ Sherif: Could you let me know what you find once you upgrade to Feisty?
If you're especially keen to find out, you might download the Feisty beta
and do a test from the live CD environment.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
Well, I am using ndiswrapper 1.40 and ubuntu 6.10 Edgy i am waiting for Feisty
to be realesed. It seems that it now works only when i manually set the key to
open
( sudo iwconfig [device-id] ESSID [network-name] key open ) so it connects
to unencrypted network BUT it gives this error ( Error
@ Chris:
I am on kubuntu 6.10, I have downloaded also kubuntu beta live disk 7.04 but
still knetwork hangs at 28% on my Atheros AR5211. On kubuntu 6.06 it used to be
working flawless.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
Well, i found that when i restarted ubuntu, my wireless card connected
to unencrypted network at last, but when i connect to an encrypted
network and try to get back to the unencrypted one it doesn't work, so i
have to restart in order to connect to an unencrypted network :S.
Thanks :)
--
@ smgouda: This sounds like it may be the problem I was seeing. I
haven't done thorough testing, however.
What happens if you try to connect to an unencrypted network twice
(i.e., connect to an encrypted network, then attempt to connect to an
unencrypted network, then attempt to connect to that
@ Sherif: You know what -- we ought to take this discussion elsewhere.
This report is supposedly fixed and is completely littered with random
reports. There's another bug report that is more-specific to our
problem: bug #73759. Anyone interested: please subscribe yourself to
that report.
--
I have a similar issue with atheros chipset AR5211, it does not connect anymre
to my home lan, it stops at 28%
I have also tried Suse 10.2 but I got the same behaviour!
I feel it is more generalized bug not only related bcm cards.
--
Cannot associate with unencrypted networks using bcm43xx
Well, I still cannot associate with unencrypted networks, i have ndiswrapper
1.40 installed and the wireless card works fine with encrypted networks only.
My Card type is:
Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g
Wireless LAN Controller (rev 02)
I have ubuntu
@Fabio: Which version of Ubuntu are you using? Feisty?
I previously thought the problem had gone away since Feisty (in Feisty's
current state, anyway), but I've recently had problems, again, in
connecting to unencrypted networks... It may have been another, more
general problem, though, as I
I can confirm that this works with my broadcomm 4306-based wireless
adapter ndiswrapper (from my comment above) with Edgy with all the
current updates.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
ubuntu-bugs
I doubt this ever was a wpasupplicant problem; rejecting this task.
** Changed in: wpasupplicant (Ubuntu)
Assignee: (unassigned) = Tollef Fog Heen
Status: Confirmed = Rejected
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
Since this is verified as working with ndiswrapper, I'm marking this bug
as closed. Ronald MacNeil and RealMurphy, please file a bug, probably
against the linux-source-2.6.17 (or 2.6.20 if you can verify that it
doesn't work on feisty) package.
** Changed in: network-manager (Ubuntu)
Me too
System:
- kubuntu feisty
- Intel Mac Mini
- Built-in Atheros Airport extreme
Base station:
- Airport
- WEP40 encryption
- Other machines connect fine: Windows, Gentoo, FreeBSD, MacOSX, and even a G4
Cube w/ old-school airport card running Edgy
My Network Manager results are similar to
RealMurphy: This bug is about the bcm43xx chipset using the ndiswrapper
driver. You are using a completely different driver and chipset. Please
file another bug.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
OK, done that, sorry, I thought this to be a more generic problem.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sorry to the developers, but this problem seems to persist:
I'm experiences this problem with an atheros based card
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC
(rev 01)
Subsystem: IBM Unknown device 057e
in a Thinkpad T43p. Dapper had no problems
Same problem. Latest edgy amd64.
Using ndiswrapper with broadcom 4311.
I can connect fine usinf wifi-radar but NetworkManager will not connect to
anything.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
ubuntu-bugs
This is known, and a patch is working its way through the queue right
now.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
There's a lot of confusing and unrelated info in here, but one clear
point (to me, at least) is that the wext wpa_supplicant driver should
be used with the version of ndiswrapper in Edgy, not ndiswrapper.
This was discovered by me in comment #37, rediscovered by Jean Pierre in
comment #48, and
Since upgrade to the kernel 2.6.17-10-386, NetworkManager (up-to-date
edgy) works via ndiswrapper with my card (tnet130 chipset (native (buggy
for me) linux driver: acx)) where it previously did not (or did not very
well - it was unable to set essid, had to be assisted manually).
There must have
Under Dapper, I had the same problem, only able to connect to encrypted
networks. I'm using ndiswrapper/Intel neti2220 driver. I can connect
to non-encrypted networkds through the standard Network settings
dialogue.
Under Edgy, network-manager doesn't connect to any networks, encrypted
or
It now works for me with Jean Pierre Rupp's packages, on a Compaq
Presario V2610CA with Kubuntu Dapper, using a Broadcom BCM 4318 card
with ndiswrapper. Thanks a lot. Note however that it doesn't work with
the native bcm43xx kernel driver, stopping at 28% configuration of
peripheral.
--
Cannot
I can confirm on a presario V2000 (Turion64), running Edgy Knot 3 64bit,
that things work once I've built ndiswrapper 1.23, wireless-tools 29,
and NetworkManager 0.6.4 (off the ftp.gnome.org site), all from source.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
tried w/ latest ndiswrapper, still no luck.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the problem described as above also. I am running a BCM94306
network card. I can connect perfectly at home (WPA2-PSK) but when I
attempt to connect at school (public network) It will not connect. This
is a completely fresh ubunto dapper install with all updates applied and
network manager
I was having the ndiswrapper instead of wext problem as well, with a
rt2500 device using ndiswrapper ( The native driver wouldn't associate
as well, but that's another issue). I was manually using wpa_supplicant
to get around it.
jpierre's packages solved the problem.
Also, ndiswrapper worked
I still see the same problems trying to connect to unencrypted networks
using Jean Pierre Rupp's packages.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
https://launchpad.net/bugs/42504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
To add my 2 cents, I cannot connect to unencrypted networks even using
the bcm43xx driver instead of ndiswrapper. However, once I set my
network to WPA-PSK encryption and used the appropriate login, I
connected immediately.
--
Cannot associate with unencrypted networks using bcm43xx chipset
The packages from Jean Pierre Rupp in
https://launchpad.net/distros/ubuntu/+source/network-
manager/+bug/42504/comments/49 worked for me w/ the ndiswrapper in edgy.
I'm using edgy, currently updated.
--
Cannot associate with unencrypted networks using bcm43xx chipset (ndiswrapper
driver)
I have the problem as described, with Texas Instruments ACX 111
chipset using ndiswrapper (which is to say, it is not necessarily only
Broadcom chipsets). NetworkManager (or wpasupplicant) does not set
essid, if I run manually iwconfig wlan0 essid XXX while it tries to
associate, it works after
I also have a BCM 4318 card in my hp nx6110. Same problem as above
comment, network-manager starts with bcm43xx only once, with ndiswrapper
it does not work at all. Connecting via wpasupplicant -i wlan0 -Dwext
-c/etc/wpasupplicant.conf works fine, when after that dhclient3 is run
manually, using
31 matches
Mail list logo
