lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAG1a4rttmkFW2UrmGvAvop3==ZqjATDj09DLtdCKedGdy-cRgg@mail.gmail.com>
Date:	Fri, 19 Aug 2011 00:27:46 -0400
From:	Pavel Ivanov <paivanof@...il.com>
To:	Dan Williams <dcbw@...hat.com>
Cc:	Gábor Stefanik <netrolller.3d@...il.com>,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>,
	Jouni Malinen <jmalinen@...eros.com>,
	Vasanthakumar Thiagarajan <vasanth@...eros.com>,
	Senthil Balasubramanian <senthilkumar@...eros.com>,
	linux-wireless@...r.kernel.org, ath9k-devel@...ema.h4ckr.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ath9k: make driver usable standalone

On Thu, Aug 18, 2011 at 6:56 PM, Pavel Ivanov <paivanof@...il.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ