Re: iwm0: could not initiate scan

2017-05-14 Thread Jan Stary
On May 14 15:55:34, s...@stsp.name wrote: > On Sun, May 14, 2017 at 03:24:34PM +0200, Jan Stary wrote: > > > But please show me your hostname.iwm0 file. > > dhcp > > So you're not setting a network name (and perhaps a WPA password) before > bringing the interface up. Does the message go away if

Re: iwm0: could not initiate scan

2017-05-14 Thread Stefan Sperling
On Sun, May 14, 2017 at 06:06:47PM +0300, G wrote: > sorry for the last email. i wanted to write ifconfig iwm0 chan 5. > Still i dont know what you mean by change to 5GHz channel. 2GHz channels are numbered 1 to 14. 5GHz channels are numbered 36, 40, 48, 50, 52, etc. See

Re: iwm0: could not initiate scan

2017-05-14 Thread G
sorry for the last email. i wanted to write ifconfig iwm0 chan 5. Still i dont know what you mean by change to 5GHz channel. On 05/14/17 17:52, G wrote: > i dont understand what you mean? > If you mean ifconfig scan 5 > > i get > > ifconfig scan 5 > ifconfig: SIOCDIFADDR: Device not configured

Re: iwm0: could not initiate scan

2017-05-14 Thread G
i dont understand what you mean? If you mean ifconfig scan 5 i get ifconfig scan 5 ifconfig: SIOCDIFADDR: Device not configured On 05/14/17 16:31, Stefan Sperling wrote: > On Sun, May 14, 2017 at 04:00:02PM +0300, G wrote: >> I noticed that wifi after a while becomes really slow and i have to

Re: iwm0: could not initiate scan

2017-05-14 Thread Stefan Sperling
On Sun, May 14, 2017 at 03:47:59PM +0200, Jan Stary wrote: > Would you please recommend a card that has one of the radio chips > that support 5G, fits into the ALIX, and is known to work well? In my experience AR9280 chips work well. Cards with this chip exist in MiniPCI format as well as PCIe.

Re: iwm0: could not initiate scan

2017-05-14 Thread Stefan Sperling
On Sun, May 14, 2017 at 03:24:34PM +0200, Jan Stary wrote: > > But please show me your hostname.iwm0 file. > dhcp So you're not setting a network name (and perhaps a WPA password) before bringing the interface up. Does the message go away if you do that? > > It's possible that you're running a

Re: iwm0: could not initiate scan

2017-05-14 Thread Jan Stary
On May 14 15:31:12, s...@stsp.name wrote: > On Sun, May 14, 2017 at 04:00:02PM +0300, G wrote: > > I noticed that wifi after a while becomes really slow and i have to restart > > sh /etc/netstart > > in order for the speed to improve. > > Try a 5 GHz channel. Works great here. Hm, my athn has

Re: iwm0: could not initiate scan

2017-05-14 Thread Stefan Sperling
On Sun, May 14, 2017 at 04:00:02PM +0300, G wrote: > I noticed that wifi after a while becomes really slow and i have to restart > sh /etc/netstart > in order for the speed to improve. Try a 5 GHz channel. Works great here.

Re: iwm0: could not initiate scan

2017-05-14 Thread Jan Stary
t sequence ends with > > > > iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:40:21:08 > > iwm0: could not initiate scan > > > > This particular message is not in iwm(4) DIAGNOSTICS. > > Is it anything to worry about? > > This is nothing to w

Re: iwm0: could not initiate scan

2017-05-14 Thread G
nt/amdd64 on a Dell Latitude E5570 (dmesg below). >> The "device timeouts" of iwm have mostly disappeared, > > Great! > >> but the boot sequence ends with >> >> iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:40:21:08 >> iwm0: could not i

Re: iwm0: could not initiate scan

2017-05-14 Thread Stefan Sperling
address e4:a4:71:40:21:08 > iwm0: could not initiate scan > > This particular message is not in iwm(4) DIAGNOSTICS. > Is it anything to worry about? This is nothing to worry about if it works eventually. But please show me your hostname.iwm0 file. It's possible that you're running

iwm0: could not initiate scan

2017-05-14 Thread Jan Stary
This is current/amdd64 on a Dell Latitude E5570 (dmesg below). The "device timeouts" of iwm have mostly disappeared, but the boot sequence ends with iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:40:21:08 iwm0: could not initiate scan This particular message is no