Return-path: Received: from mail-ew0-f46.google.com ([209.85.215.46]:35896 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750859Ab1HSE2S (ORCPT ); Fri, 19 Aug 2011 00:28:18 -0400 MIME-Version: 1.0 In-Reply-To: References: <1313695217.23920.4.camel@dcbw.foobar.com> <1313699724.23920.18.camel@dcbw.foobar.com> From: Pavel Ivanov Date: Fri, 19 Aug 2011 00:27:46 -0400 Message-ID: (sfid-20110819_062841_607952_7C45308D) Subject: Re: [PATCH] ath9k: make driver usable standalone To: Dan Williams Cc: =?ISO-8859-1?Q?G=E1bor_Stefanik?= , "Luis R. Rodriguez" , Jouni Malinen , Vasanthakumar Thiagarajan , Senthil Balasubramanian , linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Aug 18, 2011 at 6:56 PM, Pavel Ivanov wrote: >> Or, since I'm a NetworkManager developer, is there something that you're >> not sure how to make NM do, or are you just looking to experiment? > > I want to make the wireless work when kernel is compiled without > WIRELESS_EXT. Last time I tried it Ubuntu (I guess I should say > NetworkManager) wasn't able to discover any wireless networks in our > area and wasn't able to connect to my default network. Was it supposed > to do that? Well, I guess I should say sorry. After all this discussion I've tried to compile and boot kernel without WIRELESS_EXT once more. And now it worked. Last time I tried it was 3.0. Driver from vanilla sources didn't work, so I compiled compat-wireless-3.0-2 and it did warn me during compilation, something like "WIRELESS_EXT is not set, something won't work". Then after boot syslog had somewhat the same message and wireless didn't work. That's why I started this thread. Now with 3.1-rc2 everything works as is, no warnings in syslog and NetworkManager connects to my network without any problems. I don't know what has changed but I feel very sorry for all this mess. Pavel