On Thu, Jan 14, 2016 at 07:41:59PM -0700, Chris Wojo wrote:
> Here is a one liner from the beacons at home:
It seems this AP does not support 802.11n and is using WEP.
Is this correct?
> Here are a few beacons from work:
There's nothing unusual in these beacons as far as I can tell.
> This wo
ration to runtime image
sending command 0x6c qid 9, idx 1
sending command 0x6c qid 9, idx 2
sending command 0x6c qid 9, idx 3
sending command 0x6c qid 9, idx 4
sending command 0x6c qid 9, idx 5
sending command 0x6c qid 9, idx 6
sending command 0x6c qid 9, idx 7
sending command 0x6c qid 9, idx 8
se
On Tue, Jan 12, 2016 at 07:11:55PM -0700, Chris Wojo wrote:
> So it appears that iwm0 does work on snapshot #1800 on my home wireless AP.
> The errors previously reported still occur on the office network where
> several AP's are using the same NWID.
> I would be more than happy to troubleshoot
On Mon, 11 Jan 2016 13:16:53 -0700 Stefan Sperling wrote
> On Mon, Jan 11, 2016 at 11:13:03AM -0700, Chris Wojo wrote:
> > I'm trying to connect to a wireless access point but receive "iwm0: could
> > not initiate 2 GHz scan" from dmesg.
>
>
On Mon, Jan 11, 2016 at 11:13:03AM -0700, Chris Wojo wrote:
Hello Chris,
> Currently, I'm running a snapshot 5.9-beta # 1800.
>
> I'm trying to connect to a wireless access point but receive "iwm0: could
> not initiate 2 GHz scan" from dmesg.
>
> dhclien
On Mon, Jan 11, 2016 at 11:13:03AM -0700, Chris Wojo wrote:
> I'm trying to connect to a wireless access point but receive "iwm0: could not
> initiate 2 GHz scan" from dmesg.
I'm seeing these message sometimes but they are transient
and scanning usually works fine a
Currently, I'm running a snapshot 5.9-beta # 1800.
I'm trying to connect to a wireless access point but receive "iwm0: could not
initiate 2 GHz scan" from dmesg.
dhclient comes back with no link.
I have tried changing media from "autoselect mode 11n" to autosel
7 matches
Mail list logo
