From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 31 16:09:59 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F2D341B for ; Tue, 31 Dec 2013 16:09:59 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0FACD1D3D for ; Tue, 31 Dec 2013 16:09:58 +0000 (UTC) Received: from [127.0.0.1] (mail.kevlo.org [220.135.115.6]) by ns.kevlo.org (8.14.6/8.14.6) with ESMTP id rBVG9eIT044130; Wed, 1 Jan 2014 00:09:42 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <52C2EC52.9040603@FreeBSD.org> Date: Wed, 01 Jan 2014 00:09:54 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Toomas Aas Subject: Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything References: <20131230203659.957651ynumecyn40@webmail.raad.tartu.ee> <52C258A9.60907@FreeBSD.org> <20131231120936.214215rumdf13u1w@webmail.raad.tartu.ee> In-Reply-To: <20131231120936.214215rumdf13u1w@webmail.raad.tartu.ee> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Dec 2013 16:09:59 -0000 Toomas Aas wrote: > Hello Kevin! > >> I hate debugging problems on the last day of the year :-) > > Look at the bright side - one more problem fixed in 2013 :) > >> It seems like the firmware forgot to MFC. I just MFC'ed r256717. >> Tested on the 9.2-STABLE (r260119) with the TL-WN727N wlan device. > > Confirmed, now it also works for me. Cool! > > BTW, for some reason I cannot build a kernel with "device runfw". > > I added the following to my kernel config: > > options IEEE80211_DEBUG > device run > device runfw > device wlan > device wlan_amrr > device wlan_wep > device wlan_ccmp > device wlan_tkip > > and buildkernel failed: > > clang -c -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel > -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > -Werror /usr/src/sys/dev/usb/wlan/if_run.c > clang -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel > -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -c > runfw.c > uudecode -o runfw /usr/src/sys/contrib/dev/run/rt2870.fw.uu > ld -b binary --no-warn-mismatch -d -warn-common -r -o runfw.fwo > ld: no input files > *** [runfw.fwo] Error code 1 > > I removed "device runfw" from kernel config, leaving everything else > as is. Kernel built successfully and runfw seems to work as loadable > module. Problem fixed by gonzo in r252064. It's just MFC'ed to stable/9 as r260134. :-) > > Happy end_of_the_year! Happy New Year! Kevin