Re: iwm0: could not initiate scan
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 you do that?
Yes it does.
> > > > Running against a current/i364 AP
> > > > seems to work fine with 11g (less so with 11n).
> > >
> > > It's an athn(4) AP?
> >
> > Yes. It's an ALIX (dmesg below) with
> >
> > athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9
> > athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 2, address
> > 00:1d:6a:6b:03:07
>
> > I was having problems using 11n (with various clients) and
> > was advised here to use 11g for now, which indeed seems more reliable.
>
> You have a device with unequal numbers of Tx and Rx streams.
> There was a bug in 6.1 which affects those. I believe a commit I made on
> the 23rd of April has fixed 11n mode for your athn device but you're still
> running a snap from April 9. So please upgrade and try again!
I just upgraded the ALIX (dmesg below); the 11n problems seem to be gone.
The OpenBSD laptop (the iwm Dell Latitude of the original post),
an ath(4) MacBook, an ipad and the android phones connect fine.
Thanks!
Jan
OpenBSD 6.1-current (GENERIC) #51: Sat May 13 19:48:25 MDT 2017
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 432
MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
real mem = 133713920 (127MB)
avail mem = 118468608 (112MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 12/10/07, BIOS32 rev. 0 @ 0xfceb2
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xe/0xa800
cpu0 at mainbus0: (uniprocessor)
mtrr: K6-family MTRR support (2 registers)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10, address
00:0d:b9:12:9f:2c
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
00:0d:b9:12:9f:2d
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address
00:0d:b9:12:9f:2e
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9
athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 2, address 00:1d:6a:6b:03:07
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
3579545Hz timer, watchdog, gpio, i2c
gpio0 at glxpcib0: 32 pins
iic0 at glxpcib0
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA, 7279MB, 14909328 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 15, version 1.0,
legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev 2.00/1.00
addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev 1.00/1.00
addr 1
nvram: invalid checksum
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (bf940e6c7aaf2c50.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout
Re: iwm0: could not initiate scan
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 https://en.wikipedia.org/wiki/WLAN_channels 5GHz channels are usually a lot less crowded than 2GHz so performance is much better. Of course, your AP needs to support it, too.
Re: iwm0: could not initiate scan
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 > > 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 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
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 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
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. I am using a 9280 MiniPCI card in my ALIX which shows up as: athn0 at pci0 dev 14 function 0 "Atheros AR9280" rev 0x01: irq 11 athn0: AR9280 rev 2 (2T2R), ROM rev 16, address xx:xx:xx:xx:xx:xx 0:14:0: Atheros AR9280 0x: Vendor ID: 168c Product ID: 0029 I forgot where I got it from. A good site to search is https://wikidevi.com/wiki/Atheros It looks like you want one of the 22 adapters linked at 'AR9220' which is noted to be a "AR9280 w/ PCI IF". Note that you'll need 2 antennas to use 11n mode. My ALIX case does not have a second hole drilled yet so I'm running it in 11a mode for now.
Re: iwm0: could not initiate scan
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 specific sequence of commands which > > triggers this. If I knew what those are I could try to reproduce it. > > I move between different SSIDs and never got around to automatize it > (btw, what do people use for that?), so I do it manually, like this: > > $ doas ifconfig iwm0 up nwid stare.cz wpakey XXXPASSWORDXXX -nwkey No need for 'up' in this line. 'up' triggers a scan because the interface will try to find an AP when it goes UP. The following commands on this line then set additional parameters and because of that the device must be reset. So with this single line you bounce the device up and down several times. It works, but it may cause a scan to be aborted midway and then you'll see the 'could not initiate scan' message. It is really just a cosmetic problem. You're pushing the configuration through various states before things eventually settle down. I am not blaming you -- this is a problem with how the ifconfig->kernel interfaces and scanning logic were designed. There is no way for the driver to tell whether ifconfig is looking for a list of APs or a specific AP to connect to, for example. The commands 'ifconfig scan' and 'ifconfig up' are the same from the driver's perspective. Changing this would be a lot of work so we'd need another wifi developer to do that. Any volunteers? > $ doas sh /etc/netstart iwm0 You could just run 'dhclient iwm0' here. > > > Running against a current/i364 AP > > > seems to work fine with 11g (less so with 11n). > > > > It's an athn(4) AP? > > Yes. It's an ALIX (dmesg below) with > > athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9 > athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 2, address > 00:1d:6a:6b:03:07 > I was having problems using 11n (with various clients) and > was advised here to use 11g for now, which indeed seems more reliable. You have a device with unequal numbers of Tx and Rx streams. There was a bug in 6.1 which affects those. I believe a commit I made on the 23rd of April has fixed 11n mode for your athn device but you're still running a snap from April 9. So please upgrade and try again! > OpenBSD 6.1-current (GENERIC) #304: Sun Apr 9 20:21:01 MDT 2017 > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
Re: iwm0: could not initiate scan
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 the AR2133 radio athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 2, address 00:1d:6a:6b:03:07 and The AR2133 chip operates in the 2GHz spectrum 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? Thank you Jan
Re: iwm0: could not initiate scan
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
On May 14 13:10:17, s...@stsp.name wrote:
> On Sun, May 14, 2017 at 12:16:55PM +0200, Jan Stary wrote:
> > This is current/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 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.
dhcp
> It's possible that you're running a specific sequence of commands which
> triggers this. If I knew what those are I could try to reproduce it.
I move between different SSIDs and never got around to automatize it
(btw, what do people use for that?), so I do it manually, like this:
$ doas ifconfig iwm0 up nwid stare.cz wpakey XXXPASSWORDXXX -nwkey
$ doas sh /etc/netstart iwm0
> > Running against a current/i364 AP
> > seems to work fine with 11g (less so with 11n).
>
> It's an athn(4) AP?
Yes. It's an ALIX (dmesg below) with
athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9
athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 2, address 00:1d:6a:6b:03:07
configured as
inet 192.168.33.1 255.255.255.0 NONE
media autoselect mediaopt hostap mode 11g chan 11
nwid stare.cz wpakey XXX
I was having problems using 11n (with various clients) and
was advised here to use 11g for now, which indeed seems more reliable.
Jan
OpenBSD 6.1-current (GENERIC) #304: Sun Apr 9 20:21:01 MDT 2017
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 432
MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
real mem = 133713920 (127MB)
avail mem = 118476800 (112MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 12/10/07, BIOS32 rev. 0 @ 0xfceb2
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xe/0xa800
cpu0 at mainbus0: (uniprocessor)
mtrr: K6-family MTRR support (2 registers)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10, address
00:0d:b9:12:9f:2c
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
00:0d:b9:12:9f:2d
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address
00:0d:b9:12:9f:2e
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9
athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 2, address 00:1d:6a:6b:03:07
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
3579545Hz timer, watchdog, gpio, i2c
gpio0 at glxpcib0: 32 pins
iic0 at glxpcib0
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA, 7279MB, 14909328 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 15, version 1.0,
legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev 2.00/1.00
addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev 1.00/1.00
addr 1
nvram: invalid checksum
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (bf940e6c7aaf2c50.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout
Re: iwm0: could not initiate scan
I got similar messages on my dmesg. 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. On 05/14/17 14:10, Stefan Sperling wrote: > On Sun, May 14, 2017 at 12:16:55PM +0200, Jan Stary wrote: >> This is current/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 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 a specific sequence of commands which > triggers this. If I knew what those are I could try to reproduce it. > >> Running against a current/i364 AP >> seems to work fine with 11g (less so with 11n). > > It's an athn(4) AP? >
Re: iwm0: could not initiate scan
On Sun, May 14, 2017 at 12:16:55PM +0200, Jan Stary wrote: > This is current/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 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 a specific sequence of commands which triggers this. If I knew what those are I could try to reproduce it. > Running against a current/i364 AP > seems to work fine with 11g (less so with 11n). It's an athn(4) AP?
