Yeah, Waterloo's routers are not touchable by me, either :-)
--
[iwl*] intel drivers take overly long to associate to WPA for some hardware
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
If it doesn't change anything, how is it going to help this bug?
Regards,
Kash
--
[iwl*] intel drivers take overly long to associate to WPA for some hardware
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The default Intrepid kernel (2.6.27-7-generic) has XEN config options
set and will not allow nVidia drivers to be built due to Xen sanity
checks.
# grep XEN /boot/config-2.6.27-7-generic
CONFIG_HVC_XEN=y
CONFIG_NETXEN_NIC=m
CONFIG_XEN=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_BLKDEV
Trying to associate with 00:15:70:4d:bc:18 (SSID='CAMPUS-AIR' freq=2412 MHz)
CTRL-EVENT-SCAN-RESULTS
Associated with 00:15:70:4d:bc:18
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
EAP-PEAP: Failed to select forced PEAP version 1
CTR
Oops, forgot to type that I am connecting to a WPA2 network, using
PEAP... It doesn't connect, just asks me for the username/password over
and over.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bu
** Bug watch added: Debian Bug tracker #461932
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461932
** Also affects: knetworkmanager (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461932
Importance: Unknown
Status: Unknown
--
[Intrepid] iwl3945 + iwlagn -- netwo
> I too am having problems connecting to a WPA Enterprise network at my
> college. I have tried with bot NetworkManager & wicd with no success.
>
>
Yes, this is a major problem, and nothing much is being done about it. I
was able to get WPA Enterprise working on Hardy when it failed to work
o
Same here on two machines with iw3945 and rtl8180.
--
[iwl*] intel drivers take overly long to associate to WPA for some hardware
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
wicd displays the same symptoms. It works fine with a WPA2 Personal network,
but fails miserably with WPA-Enterprise (PEAP and MSCHAPv2 (?))
On Wed, Jan 21, 2009 at 4:45 PM, Tom Chiverton wrote:
> @Kash: When you say 'Same here' do you mean wicd displays the same
> symptoms as NetworkManager, or
Er, this bug is wrt WPA Enterprise. If you cannot connect to a
personal network, your drivers are borked.. Personal worked fine for
me the whole time.
On 16-Feb-09, at 9:30 PM, "Scott R." wrote:
> Any progress on this bug?
>
> I also am on an intrepid install with problems connecting to a l
10 matches
Mail list logo
