Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On Sun, May 30, 2010 at 07:48:38PM +0200, Lars Engels wrote: On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Correction: Wireless actually works if you set the channel manually and start wpa_supplicant afterwards. So wpa_supplicant no longer seems to be able to change the channel itself. The issue is still present in r209168. pgpeSZcZqNAnK.pgp Description: PGP signature
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 15 Jun 2010, at 08:03, Lars Engels wrote: On Sun, May 30, 2010 at 07:48:38PM +0200, Lars Engels wrote: On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Correction: Wireless actually works if you set the channel manually and start wpa_supplicant afterwards. So wpa_supplicant no longer seems to be able to change the channel itself. The issue is still present in r209168. Which driver? I works fine with my ath. -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 08:03, Lars Engels wrote: The issue is still present in r209168. Which driver? I works fine with my ath. ath0: Atheros 5424/2424 mem 0xd400-0xd400 irq 16 at device 0.0 on pci2 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 pgp3xegg3kPOL.pgp Description: PGP signature
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 15 Jun 2010, at 09:17, Lars Engels wrote: On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 08:03, Lars Engels wrote: The issue is still present in r209168. Which driver? I works fine with my ath. ath0: Atheros 5424/2424 mem 0xd400-0xd400 irq 16 at device 0.0 on pci2 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 Can you identify the revision that broke it? -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On Tue, Jun 15, 2010 at 09:25:22AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 09:17, Lars Engels wrote: On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 08:03, Lars Engels wrote: The issue is still present in r209168. Which driver? I works fine with my ath. ath0: Atheros 5424/2424 mem 0xd400-0xd400 irq 16 at device 0.0 on pci2 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 Can you identify the revision that broke it? Unfortunately not the exact revision. Doug wrote that it stopped working at r208626 and before it also worked for me. pgp5qR2lCd5u8.pgp Description: PGP signature
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 06/15/10 09:32, Lars Engels wrote: On Tue, Jun 15, 2010 at 09:25:22AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 09:17, Lars Engels wrote: On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 08:03, Lars Engels wrote: The issue is still present in r209168. Which driver? I works fine with my ath. ath0:Atheros 5424/2424 mem 0xd400-0xd400 irq 16 at device 0.0 on pci2 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 Can you identify the revision that broke it? Unfortunately not the exact revision. Doug wrote that it stopped working at r208626 and before it also worked for me. The problem I had was related to other things, not wpa_supplicant directly. I upgraded my -current a few days ago and it's working fine for me, both before and after Rui's latest update (using the wpi driver). hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On Tue, Jun 15, 2010 at 10:02:44AM -0700, Doug Barton wrote: On 06/15/10 09:32, Lars Engels wrote: On Tue, Jun 15, 2010 at 09:25:22AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 09:17, Lars Engels wrote: On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote: On 15 Jun 2010, at 08:03, Lars Engels wrote: The issue is still present in r209168. Which driver? I works fine with my ath. ath0:Atheros 5424/2424 mem 0xd400-0xd400 irq 16 at device 0.0 on pci2 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 Can you identify the revision that broke it? Unfortunately not the exact revision. Doug wrote that it stopped working at r208626 and before it also worked for me. The problem I had was related to other things, not wpa_supplicant directly. I upgraded my -current a few days ago and it's working fine for me, both before and after Rui's latest update (using the wpi driver). Good to hear that it's working for you. In my case, it was PEBKAC. To quote Firefox: Well, this is embarrassing. When I upgraded my machine I also removed all installed Ports and cleaned up my rc.conf. Somehow I changed ifconfig_wlan0 to fconfig_wlan0. After inserting the missing 'i' I have a working wireless connection again. Now please forget what you've just read and only remember that my problem is fixed. ;-) pgpVAl0pUgq23.pgp Description: PGP signature
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 28 May 2010, at 23:03, Doug Barton wrote: On 05/28/10 13:18, Doug Barton wrote: I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Correction, the problem seems to be more generally with wpa_supplicant. I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 RF2133 phy 8.1) and it doesn't work with the latest kernel either. However, the same card is working fine with the older kernel (I'm using it now). I don't know what problem you're having but try using wlandebug to understand what's going on. Regards, -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Correction: Wireless actually works if you set the channel manually and start wpa_supplicant afterwards. So wpa_supplicant no longer seems to be able to change the channel itself. pgp7ShShBMbzE.pgp Description: PGP signature
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 5/29/10, Rui Paulo rpa...@freebsd.org wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo Yes, that was also my suspicion, and after seeing, via top(1), that ifconfig is stuck in the *taskq state while attempting to set up the wlan, I believe either r208623, or r208624, or both, is responsible for the regression. b. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 05/29/10 03:54, b. f. wrote: On 5/29/10, Rui Paulorpa...@freebsd.org wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Bartondo...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo Yes, that was also my suspicion, and after seeing, via top(1), that ifconfig is stuck in the *taskq state while attempting to set up the wlan, I believe either r208623, or r208624, or both, is responsible for the regression. Reverting those two changes allows wpa_supplicant to work again. Thanks for the hint bf. Zach? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 05/28/10 13:18, Doug Barton wrote: I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Correction, the problem seems to be more generally with wpa_supplicant. I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 RF2133 phy 8.1) and it doesn't work with the latest kernel either. However, the same card is working fine with the older kernel (I'm using it now). Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 05/28/10 13:18, Doug Barton wrote: I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Correction, the problem seems to be more generally with wpa_supplicant. I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 RF2133 phy 8.1) and it doesn't work with the latest kernel either. However, the same card is working fine with the older kernel (I'm using it now). I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. b. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. b. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
