On Tue, 2013-11-12 at 13:54 -0500, John Baldwin wrote:
Guys, it still doesn't work. Two days ago, when I changed my AP setup,
in rc.conf and then run «sudo service netif restart» I'd observed two
copies of the wpa_supplicant.
System is CURRENT b9061d4, I can't see the pgrep patch on it...
_
A lot of work has gone on in -current with the iwn driver. It's quite
possible that the recent changes has broken things.
Would you please do this:
* recompile with IWN_DEBUG defined in your kernel cofig
* sysctl dev.iwn.0.debug=0x13ff
(That turns on command debugging, tx/rx debugging, interrupt
Hi,
I don't plan a backport of any of this just yet.
I'd like to let the changes shake out a bit first. There's been some
reports about things not working between 10.0 and 11.0 (eg, 5 minutes
ago someone reported the centrino 100 doesn't work!) and I'd like to
get those fixed before we consider a
Hi,
Here's some fixes from mav, shoehorned into the current driver framework.
Mav - where'd you get your changes from?
http://people.freebsd.org/~adrian/iwn/20131207-iwn-6235-1.diff
This enables the 6235.
It now doesn't firmware panic upon startup. I've passed _no_ traff
Huh? 10.0 works fine on the 9565? Ive not changed anything in the ath
driver since then.
Adrian
On Dec 7, 2013 2:14 PM, "Peter Edson" wrote:
> when I do the destroy, it says it wasn't already configured.
>
> when I get to the supplicant part it says wpa_supplicant 1046 ioctl
> something somethi
Try 10.0b4 and run with it again. It may have been a fluke. Which laptop is
it? It could be some cut price version I need driver hacks for :(
Adrian
On Dec 7, 2013 2:45 PM, "Peter Edson" wrote:
> it worked on 10 beta 4. Was autodetected during the USB install process.
>
> I used wpa supplicant t
Hi Adrian!
Please commit the attached patch, to fix iwn2030 when compiled in to kernel.
On 12/7/13, Adrian Chadd wrote:
> Hi,
>
> I don't plan a backport of any of this just yet.
>
> I'd like to let the changes shake out a bit first. There's been some
> reports about things not working between 1
Hi,
On Sat, Dec 7, 2013 at 3:21 PM, Adrian Chadd wrote:
> Hi,
>
> Here's some fixes from mav, shoehorned into the current driver framework.
>
> Mav - where'd you get your changes from?
>
> http://people.freebsd.org/~adrian/iwn/20131207-iwn-6235-1.diff
>
>
1.
# uname -a
FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2
r259057M: Sun Dec 8 08:27:41 CST 2013
r...@x201i.honestqiao.com:/usr/obj/usr/src/sys/HonestQiaoKernel11
amd64
# pciconf -lv
iwn0@pci0:2:0:0:class=0x028000 card=0x13158086 chip=0x00848086
rev=0x00 hdr=0x00
Hi.
Can you paste the whole dmesg log from the time you start WPA supplicant up
to when it crashes? I'd like to see what commands lead to the firmware
crash.
Thanks!
Adrian
On Dec 7, 2013 7:13 PM, "乔楚" wrote:
> 1.
> # uname -a
> FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2
Well does it work manually on head? I'd like to make sure there are no
problems there.
On Dec 7, 2013 7:36 PM, "Peter Edson" wrote:
> Hey, I went ahead and reinstalled 10 beta 4 and it does not work
> automatically, but running the commands manually does work -- even rebooted
> and it is still wo
Hi Monthadar and others,
I'm starting to tackle this again.
-a
On 29 July 2013 06:11, Adrian Chadd wrote:
> So what's the specific difference between normal station and meshSTA?
>
>
>
> -adrian
>
> On 29 July 2013 03:24, Monthadar Al Jaberi wrote:
>> On Mon, Jul 29, 2013 at 5:32 AM, Adrian
12 matches
Mail list logo
