6.3 amd64 in VirtualBox - keyboard

2018-04-04 Thread Will Backman
Anyone else seeing an unresponsive keyboard with 6.3 release amd64 when 
running in VirtualBox?
bsd.rd installer works. After install, cannot log in because keyboard 
won't accept input.

6.2 works fine.
Installed current (as of 4/4) and keyboard works.



Re: Status of X i386 openbsd 6.2 on x200

2018-04-04 Thread flipchan
The amd64 fs file for 6.2 is working good i know got it running with libreboot 
which is cool, libreboot doesnt support full disk encryption  which sucks but i 
am glad that it works .

On April 2, 2018 7:26:58 PM UTC, Markus Lude  wrote:
>On Sun, Apr 01, 2018 at 09:41:07PM +, flipchan wrote:
>> Hello all,
>> 
>> I have tried to installed 6.1 and 6.2 on a thinkpad x200 it works but
>X does work ...
>> 
>> Its works great with 6.0 but then i dont get the good 6.2 packages
>and features such as syspatch. 
>> 
>> 
>> It seems lika well known problem:
>> https://marc.info/?l=openbsd-bugs=150506076421862=2
>> 
>> 
>> Does anyone know the status of this/ if anyone is working on this ?
> 
>The problem still exists. The drm diff back then was quite huge and I
>am
>unable to break it down in smaller chunks to see where the cause
>therein
>is.
>The T61 is quite old and still runs with 6.1.
>It is new for me that newer Thinkpads do have the same problem. Could
>you please post a trace of your crash?
>
>Regards,
>Markus

-- 
Take Care Sincerely flipchan layerprox dev


Did OpenBSD just go green?

2018-04-04 Thread Jesper Wallin
Hi all,

For once, I thought I'd go for a fresh install and copy as few configs
as possible from my old backups.  Once my machine was up and running,
I was a bit confused as I didn't remember OpenBSD being this slow and
watching top I noticed programs like firefox was using about 20% CPU
even if I only had a blank page opened.

Took me a while to figure out what was wrong.  Apparantly, apmd isn't
started by default and for some reason, hw.setperf seems to default to
zero.  The output of apm read:

Performance adjustment mode: manual (800 MHz)

Meaning the machine won't ever adjust the performance and it's stuck at
a whooping 800Mhz. ;-)

I also had a chat with abieber@ and it seems he had the same "issue".
So, as the subject says, did OpenBSD go green with 6.3, or has it always
been like this and I've always started apmd right after the installation
was complete?


Regards,
Jesper Wallin



iwi(4) fatal firmware error

2018-04-04 Thread Ax0n
I have a Motorola ML900 which seems to be running OpenBSD with X and
WindowMaker just fine. Every few hours it gets a group of errors within the
span of a few seconds (about 1 second between them in /var/log/messages)

Apr  4 04:30:01 luggy /bsd: iwi0: fatal firmware error
Apr  4 05:17:37 luggy /bsd: iwi0: fatal firmware error
Apr  4 05:17:39 luggy /bsd: iwi0: unknown authentication state 1
Apr  4 05:17:40 luggy /bsd: iwi0: reused group key update received from
60:38:e0:89:9b:dc
Apr  4 06:51:05 luggy /bsd: iwi0: fatal firmware error
Apr  4 06:51:06 luggy /bsd: iwi0: unknown authentication state 1
Apr  4 06:51:07 luggy /bsd: iwi0: reused group key update received from
60:38:e0:89:9b:dc
Apr  4 10:11:48 luggy /bsd: iwi0: fatal firmware error
Apr  4 10:11:51 luggy /bsd: iwi0: unknown authentication state 1
Apr  4 10:11:52 luggy /bsd: iwi0: reused group key update received from
60:38:e0:89:9b:dc

I was seeing this same behavior with 6.2-STABLE, which I just installed a
few weeks ago.

Full dmesg (before any of the above errors) is below.

OpenBSD 6.3 (GENERIC) #490: Sat Mar 24 14:31:33 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz ("GenuineIntel"
686-class) 1.70 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,CNXT-ID,xTPR,PERF
real mem  = 1073168384 (1023MB)
avail mem = 1039679488 (991MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 02/23/01, BIOS32 rev. 0 @ 0xe9b30, SMBIOS rev. 2.3
@ 0xecc1a (38 entries)
bios0: vendor Insyde Software version "Version R0.16" date 02/23/2001
bios0: MOTOROLA ML900
acpi0 at bios0: rev 0
acpi0: APIC checksum error
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP APIC BOOT
acpi0: wakeup devices SLPB(S3) LAN0(S3) USB3(S3) USB4(S3) USB5(S3) COM1(S4)
COM4(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
, remapped to apid 1
acpiprt0 at acpi0: bus 1 (PCI1)
acpiprt1 at acpi0: bus 2 (PCI2)
acpiprt2 at acpi0: bus 0 (PCI0)
acpiec0 at acpi0
acpicpu0 at acpi0: C1(@1 halt!), FVS, 1700, 1200 MHz
acpitz0 at acpi0: critical temperature is 100 degC
acpibat0 at acpi0: BAT0 not present
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: VID_
bios0: ROM list: 0xc/0xe000 0xe4000/0x1800 0xe6000/0x1000!
0xeb000/0x5000!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82845 Host" rev 0x04
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xa000, size 0x400
ppb0 at pci0 dev 1 function 0 "Intel 82845 AGP" rev 0x04
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M9" rev 0x02
drm0 at radeondrm0
radeondrm0: apic 1 int 16
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x42
pci2 at ppb1 bus 2
bktr0 at pci2 dev 3 function 0 "Brooktree BT878" rev 0x11: apic 1 int 23
bktr0: Warning - card vendor 0x (model 0x) unknown.
bktr0: Pinnacle/Miro TV,  tuner.
"Brooktree BT878 Audio" rev 0x11 at pci2 dev 3 function 1 not configured
uhci0 at pci2 dev 5 function 0 "VIA VT83C572 USB" rev 0x50: apic 1 int 16
uhci1 at pci2 dev 5 function 1 "VIA VT83C572 USB" rev 0x50: apic 1 int 17
ehci0 at pci2 dev 5 function 2 "VIA VT6202 USB" rev 0x51: apic 1 int 18
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "VIA EHCI root hub" rev 2.00/1.00
addr 1
iwi0 at pci2 dev 6 function 0 "Intel PRO/Wireless 2200BG" rev 0x05: apic 1
int 19, address 00:15:00:0d:b5:d6
cbb0 at pci2 dev 7 function 0 "TI PCI4451 CardBus" rev 0x00: apic 1 int 16,
CardBus support disabled
cbb1 at pci2 dev 7 function 1 "TI PCI4451 CardBus" rev 0x00: apic 1 int 16,
CardBus support disabled
"TI PCI4451 FireWire" rev 0x00 at pci2 dev 7 function 2 not configured
fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x42, i82562: apic 1
int 20, address 00:40:d0:6e:75:a0
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
puc0 at pci2 dev 9 function 0 "Oxford OX16PCI952" rev 0x00: ports: 2 com
com4 at puc0 port 0 apic 1 int 20: st16650, 32 byte fifo
com4: probed fifo depth: 16 bytes
com5 at puc0 port 1 apic 1 int 20: st16650, 32 byte fifo
com5: probed fifo depth: 16 bytes
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "VIA UHCI root hub" rev 1.00/1.00
addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 configuration 1 interface 0 "VIA UHCI root hub" rev 1.00/1.00
addr 1
cardslot0 at cbb0 slot 0 flags 0
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
pcmcia1 at cardslot1
ichpcib0 at pci0 dev 31 function 0 "Intel 82801CAM LPC" rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 82801CAM IDE" rev 0x02: DMA,
channel 0 

Re: (6.3) RTM_DELETE on lease renewal; why ?

2018-04-04 Thread sven falempin
On Wed, Apr 4, 2018 at 12:04 AM, sven falempin  wrote:
> Dear readers,
>
> For a long time now, using dhclient to renew a lease trigger a
> RTM_DELETE, then RTM_ADD,
> because it always remove everything before applying the lease (well
> the IP) ( without like checking  it s a renewal and nothing changed ).
>
> # route monitor &
> # dhclient  vio0
> got message of size 96 on Wed Apr  4 03:56:53 2018
> RTM_PROPOSAL: config proposal: len 96, source dhcp table 0, ifidx 1,
> pid: 47718, seq -1773381169, errno 0
> flags:
> fmask:
> use:0   mtu:0expire:0
> locks:  inits:
> Static Routes:
> Domain search:
> Domain Name Servers:
> vio0: bound to 100.64.1.3 from 100.64.1.2 (fe:e1:bb:d1:af:df)
> got message of size 208 on Wed Apr  4 03:56:53 2018
> RTM_DELETE: Delete Route: len 208, priority 3, table 0, ifidx 1, pid:
> 88062, seq 0, errno 0
> flags:
> fmask:
> use:4   mtu:0expire:  -14
> locks:  inits:
> sockaddrs: 
>  100.64.1.2 link#1 255.255.255.255 fe:e1:bb:d1:af:de 100.64.1.3
> got message of size 192 on Wed Apr  4 03:56:53 2018
> RTM_RESOLVE: Route created by cloning: len 192, priority 3, table 0,
> ifidx 1, pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0   mtu:0expire:0
> locks:  inits:
> sockaddrs: 
>  100.64.1.2 fe:e1:ba:d0:19:81 fe:e1:bb:d1:af:de 100.64.1.3
> got message of size 144 on Wed Apr  4 03:56:53 2018
> RTM_ADD: Add Route: len 144, priority 0, table 0, ifidx 1, pid: 88062,
> seq 0, errno 17
> flags:
> fmask:
> use:0   mtu:0expire:0
> locks:  inits:
> sockaddrs: 
>  default 100.64.1.2 default
> got message of size 192 on Wed Apr  4 03:56:55 2018
> RTM_GET: Report Metrics: len 192, priority 8, table 0, ifidx 1, pid:
> 88062, seq 512726977, errno 0
> flags:
> fmask:
> use:0   mtu:0expire:0
> locks:  inits:
> sockaddrs: 
>  default 100.64.1.2 default fe:e1:bb:d1:af:de 100.64.1.3
>
> Is there a reason behind this behavior ? is it just to set aside some
> complexity ?
>
> Can't this trigger a (UDP) packet drop ?
>
> Best.

Oh, it as been fixed too, it only do that on explicit request.

Great , thank you

-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do



Re: [Arduino] CLI serial monitor

2018-04-04 Thread Olivier Burelli
Hello Janne, CRC,

great, thanks for explanations.

A big thank you to both of you.

have a nice day.

Olivier.

On Wed, 4 Apr 2018 10:39:30 +0200
Janne Johansson  wrote:

> 2018-04-04 4:58 GMT+02:00 Olivier Burelli :
> 
> > Hello,
> >
> > i am playing with ARDUINO UNO on my 6.2 stable laptop.
> > I am trying to read the serial monitor message from the board.
> >
> > from dmesg:
> > (...)
> > umodem0 at uhub3 port 1 configuration 1 interface 0 "Arduino
> > SrlArduino Uno" rev 1.10/0.01 addr 3
> > umodem0: data interface 1, has no CM over data, has break
> > umodem0: status change notification available
> > ucom0 at umodem0  
> > --> which device is corresponding ?  
> >
> >
> >  
> ucom0 from dmesg means it is /dev/cuaU0 (and /dev/ttyU0), ucom1 ->
> cuaU1 and so on.
> Then use "cu" or something if you want to interact with it manually.
> "cu -s 9600 -l /dev/cuaU0" for 9k6 connections. (though 115200 is
> probably nicer,
> otherwise the Serial.print()s will spend too much time talking slow
> to the computer
> which also can handle lots faster speeds.
> 



Re: Using stmp auth for local account with PHP scripts

2018-04-04 Thread Markus Rosjat

Hi again,


Am 04.04.2018 um 15:34 schrieb Christophe Simon:

Yes, that should do the trick.

The only problem that you could face is the certificate validation in 
PHPMailer: if you connect to `locahost` using a TLS connection, unless 
your certificate presents `localhost` as a CN (or a SAN), there's 
chances that the client refuses to establish the connection (I don't 
remember if certificate validation is enabled by default in PHPMailer).


If you don't want to bypass certificate validation, one possible way 
to overcome this issue is to set an entry in your chroot's 
`/etc/hosts` pointing your certificate's CN to `127.0.0.1`, or include 
`localhost` in your certificate SANs. And if your certificate is self 
signed, you'll have to manually accept it.



I will give it a try , thank you for the advice

Regards

--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you 
print it, think about your responsibility and commitment to the ENVIRONMENT



Re: FAQ6 patch for Shared Address Space / VMM

2018-04-04 Thread Theo Buehler
> The FAQ6 section for VMM Networking incorrectly specified the range
> for Shared Address Space. RFC6598 section 7 calls out 100.64.0.0/10

fixed, thanks



FAQ6 patch for Shared Address Space / VMM

2018-04-04 Thread Seth Hanford
The FAQ6 section for VMM Networking incorrectly specified the range for Shared 
Address Space. RFC6598 section 7 calls out 100.64.0.0/10

As far as I can tell, it’s just the FAQ that misstates this. The vm manpages 
seem to all call out the correct range

--- faq6.html   Wed Apr  4 06:19:18 2018
+++ faq6.html.patched   Wed Apr  4 06:20:15 2018
@@ -668,7 +668,7 @@
   (https://tools.ietf.org/html/rfc6598;>RFC6598) are similar
   to private addresses in that they are not globally routable, but are
   intended to be used on equipment that can perform address translation.
-  The address space is 10.64.0.0/10.
+  The address space is 100.64.0.0/10.
 
 
 Option 1 - VMs only need to talk to the host and each other
@@ -695,7 +695,7 @@
 Network Address Translation:
 
 
-match out on egress from 10.64.0.0/10 to any nat-to (egress)
+match out on egress from 100.64.0.0/10 to any nat-to (egress)
 
 
 Reload the pf ruleset and the VM(s) can now connect to the internet.



Re: Using stmp auth for local account with PHP scripts

2018-04-04 Thread Christophe Simon

Yes, that should do the trick.

The only problem that you could face is the certificate validation in 
PHPMailer: if you connect to `locahost` using a TLS connection, unless 
your certificate presents `localhost` as a CN (or a SAN), there's 
chances that the client refuses to establish the connection (I don't 
remember if certificate validation is enabled by default in PHPMailer).


If you don't want to bypass certificate validation, one possible way to 
overcome this issue is to set an entry in your chroot's `/etc/hosts` 
pointing your certificate's CN to `127.0.0.1`, or include `localhost` in 
your certificate SANs. And if your certificate is self signed, you'll 
have to manually accept it.


Regards.

Le 04/04/18 à 14:15, Markus Rosjat a écrit :

Hi,

I will answer in the text below :)

Am 04.04.2018 um 13:52 schrieb Christophe Simon:

Hello,

I'd say that all depends on the function/library you're using in your 
PHP application to send mails.


The `mail()` command, for instance, uses the `sendmail` binary to 
directly ingest your message in your local mail spool, and thus does 
not require any authentication. The mail is sent on behalf of the 
identity your web server runs under. There's options to set the 
appropriate sender in the message headers, obviously.




no we don't want to use binary in chroot, that somehow feels just wrong :)

If you're using a library such as `PHPMailer`, you'll want to use the 
SMTP protocol, either locally (on lo0) (1), or remotely (on your mail 
provider's SMTP service) (2).




since it will be WP (i know ...) it has PHPMailer and it should be able 
to send with SMTP Protocol.



It's up to you to define if you want authentication on the loopback 
port (but that's better to do so).


If you're using your local MTA to send emails (1), either using the 
SMTP protocol on lo0 or the `sendmail` binary, there's chances you'll 
want to use a relay host to avoid being blacklisted by your recipients 
servers (or you should take care to have a resolvable public IP with 
correct SPF configured in your DNS). Such a configuration has been 
very well illustrated by Michael below.




I have set up the local smtpd to relay mails from local connections so 
it's only listen on lo0 but hey PHPMailer will connect on lo0 and can be 
abused still if the WP arround it allows it. I basically force the user 
to use something like recaptcha but even then I would like to do 
something with authentication thought.


for me I short example would be helpful for now I basically let a script 
run once an hour to check if the maillog shows somewhat strange traffic 
to the relay.


is enabling auth on lo0 simply this ?

pki hostname /path/to/cert
pki hostname /path/to/key


table aliases file:/etc/mail/aliases
table secrets file:/etc/mail/secrets

listen on lo0 port submission tls auth

accept for any relay via tls+auth://relaycred@relayhost:587 auth 


And then I can just setup the PHPMailer to use submission port on 
localhost with some credentials?


Regards





Re: Using stmp auth for local account with PHP scripts

2018-04-04 Thread Markus Rosjat

Hi,

I will answer in the text below :)

Am 04.04.2018 um 13:52 schrieb Christophe Simon:

Hello,

I'd say that all depends on the function/library you're using in your 
PHP application to send mails.


The `mail()` command, for instance, uses the `sendmail` binary to 
directly ingest your message in your local mail spool, and thus does not 
require any authentication. The mail is sent on behalf of the identity 
your web server runs under. There's options to set the appropriate 
sender in the message headers, obviously.




no we don't want to use binary in chroot, that somehow feels just wrong :)

If you're using a library such as `PHPMailer`, you'll want to use the 
SMTP protocol, either locally (on lo0) (1), or remotely (on your mail 
provider's SMTP service) (2).




since it will be WP (i know ...) it has PHPMailer and it should be able 
to send with SMTP Protocol.



It's up to you to define if you want authentication on the loopback port 
(but that's better to do so).


If you're using your local MTA to send emails (1), either using the SMTP 
protocol on lo0 or the `sendmail` binary, there's chances you'll want to 
use a relay host to avoid being blacklisted by your recipients servers 
(or you should take care to have a resolvable public IP with correct SPF 
configured in your DNS). Such a configuration has been very well 
illustrated by Michael below.




I have set up the local smtpd to relay mails from local connections so 
it's only listen on lo0 but hey PHPMailer will connect on lo0 and can be 
abused still if the WP arround it allows it. I basically force the user 
to use something like recaptcha but even then I would like to do 
something with authentication thought.


for me I short example would be helpful for now I basically let a script 
run once an hour to check if the maillog shows somewhat strange traffic 
to the relay.


is enabling auth on lo0 simply this ?

pki hostname /path/to/cert
pki hostname /path/to/key


table aliases file:/etc/mail/aliases
table secrets file:/etc/mail/secrets

listen on lo0 port submission tls auth

accept for any relay via tls+auth://relaycred@relayhost:587 auth 


And then I can just setup the PHPMailer to use submission port on 
localhost with some credentials?


Regards

--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before 
you print it, think about your responsibility and commitment to the 
ENVIRONMENT




X: WaitForSomething(): poll: Invalid argument

2018-04-04 Thread Stephane HUC "PengouinBSD"
Hi all.

How can identify what trouble X?
I run OpenBSD 6.3 - amd64 on my laptop Dell Alienware 13.
(on 6.2, I had no problem)

Something fill both logs:
- /var/log/Xorg.0.log
- /var/log/xenodm.log

with this repeated message : "WaitForSomething(): poll: Invalid argument"

I use a custom xorg.conf, to avoid Tearing with GPU Intel, as:

Section "InputDevice"
Identifier"Generic Keyboard"
Driver"kbd"
Option"CoreKeyboard"
Option"XkbRules""xorg"
Option"XkbModel""pc105"
Option"XkbLayout"   "fr"  # "fr-oss" pour Feisty et +
#Option"XkbVariant" "latin9"
EndSection

Section "InputDevice"
Identifier"Configured Mouse"
Driver"mouse"
Option"CorePointer"
Option"Device""/dev/input/mice"
Option"Protocol""ExplorerPS/2"
Option"ZAxisMapping""4 5"
Option"Emulate3Buttons""true"
EndSection

Section "Device"
Identifier  "intel" #modesetting, or Intel Graphics
Driver  "intel" #modesetting
Option  "AccelMethod"   "sna"   #sna by default
Option  "DDC"   "true"  #true by default
Option  "DRI"   "true"
Option  "HotPlug"   "true"
Option  "NoAccel"   "false" #false by default
Option  "RelaxedFencing""true"  #true if G33 Model & >
Option  "SwapbuffersWait"   "true"  #true by default (avoid
tearing)
Option  "TearFree"  "true"  #false by default
(avoid tearing)
Option  "Throttle"  "true"  #true by default
Option  "Tiling""true"  #true by default
Option  "TripleBuffer"  "true"  #true by default
#Option "VideoRAM"  ???
Option  "VSync" "true"  #true by default
EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "intel"
Monitor"Monitor0"
DefaultDepth   24 #Choose the depth (16|24)
SubSection "Display"
Depth  16
Modes  "1920x1080" "1400x1050" "1290X1024"
"1280X960" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1920x1080" "1400x1050"
"1290X1024" "1280X960" "1024x768" "800x600"
EndSubSection
EndSection

Section "ServerLayout"
Identifier"Default Layout"
Screen"Screen0"
#InputDevice   "Generic Keyboard"
#InputDevice   "Configured Mouse"
EndSection



Egual for xenodm, i use two custom files:

=> Xsetup_0:

#!/bin/sh
# $OpenBSD: Xsetup_0,v 1.1 2016/10/23 08:30:37 matthieu Exp $
if [ "$DISPLAY" = ":0" -o "$DISPLAY" = ":0.0" ]
then
/usr/local/bin/qiv -zrd7 /home/zou/Images/Wallpapers/* &
/usr/X11R6/bin/xclock -digital -update 1 -render &
echo $! > /var/run/xclock.pid
fi

#sxpm OpenBSD.xpm &

=> GiveConsole

#!/bin/sh
# Assign ownership of the console to the invoking user
# $OpenBSD: GiveConsole,v 1.1 2016/10/23 08:30:37 matthieu Exp $
#
# By convention, both xconsole and xterm -C check that the
# console is owned by the invoking user and is readable before attaching
# the console output.  This way a random user can invoke xterm -C without
# causing serious grief.
#
chown $USER /dev/console

if [ -c /dev/drm0 ]; then
chown $USER /dev/drm0
fi

/usr/X11R6/bin/sessreg -a -l $DISPLAY -u none -x
/etc/X11/xenodm/Xservers $USER

if test -r /var/run/xclock.pid; then kill $(cat /var/run/xclock.pid); fi


=> Xenodm.log:

$ head -n25 /var/log/xenodm.log


xenodm info (pid 46359): Starting
xenodm info (pid 46359): Starting X server on :0

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 6.3 amd64
Current Operating System: OpenBSD ptb-aw13zou.stephane-huc.net 6.3
GENERIC.MP#107 amd64
Build Date: 24 March 2018  02:38:24PM

Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr  3 17:06:54 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
xenodm info (pid 80557): sourcing /home/zou/.config/xenodm/Xsetup_0
xenodm info (pid 80557): sourcing /home/zou/.config/xenodm/GiveConsole
xenodm info (pid 4308): executing session /etc/X11/xenodm/Xsession
WaitForSomething(): poll: Invalid argument
WaitForSomething(): poll: Invalid argument
WaitForSomething(): poll: Invalid argument


=> 

X: WaitForSomething(): poll: Invalid argument

2018-04-04 Thread Stephane HUC "PengouinBSD"
Hi all.

How can identify what trouble X?
I run OpenBSD 6.3 - amd64 on my laptop Dell Alienware 13.
(on 6.2, I had no problem)

Something fill both logs:
- /var/log/Xorg.0.log
- /var/log/xenodm.log

with this repeated message : "WaitForSomething(): poll: Invalid argument"

I use a custom xorg.conf, to avoid Tearing with GPU Intel, as:

Section "InputDevice"
Identifier"Generic Keyboard"
Driver"kbd"
Option"CoreKeyboard"
Option"XkbRules""xorg"
Option"XkbModel""pc105"
Option"XkbLayout"   "fr"  # "fr-oss" pour Feisty et +
#Option"XkbVariant" "latin9"
EndSection

Section "InputDevice"
Identifier"Configured Mouse"
Driver"mouse"
Option"CorePointer"
Option"Device""/dev/input/mice"
Option"Protocol""ExplorerPS/2"
Option"ZAxisMapping""4 5"
Option"Emulate3Buttons""true"
EndSection

Section "Device"
Identifier  "intel" #modesetting, or Intel Graphics
Driver  "intel" #modesetting
Option  "AccelMethod"   "sna"   #sna by default
Option  "DDC"   "true"  #true by default
Option  "DRI"   "true"
Option  "HotPlug"   "true"
Option  "NoAccel"   "false" #false by default
Option  "RelaxedFencing""true"  #true if G33 Model & >
Option  "SwapbuffersWait"   "true"  #true by default (avoid
tearing)
Option  "TearFree"  "true"  #false by default
(avoid tearing)
Option  "Throttle"  "true"  #true by default
Option  "Tiling""true"  #true by default
Option  "TripleBuffer"  "true"  #true by default
#Option "VideoRAM"  ???
Option  "VSync" "true"  #true by default
EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "intel"
Monitor"Monitor0"
DefaultDepth   24 #Choose the depth (16|24)
SubSection "Display"
Depth  16
Modes  "1920x1080" "1400x1050" "1290X1024"
"1280X960" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1920x1080" "1400x1050"
"1290X1024" "1280X960" "1024x768" "800x600"
EndSubSection
EndSection

Section "ServerLayout"
Identifier"Default Layout"
Screen"Screen0"
#InputDevice   "Generic Keyboard"
#InputDevice   "Configured Mouse"
EndSection



Egual for xenodm, i use two custom files:

=> Xsetup_0:

#!/bin/sh
# $OpenBSD: Xsetup_0,v 1.1 2016/10/23 08:30:37 matthieu Exp $
if [ "$DISPLAY" = ":0" -o "$DISPLAY" = ":0.0" ]
then
/usr/local/bin/qiv -zrd7 /home/zou/Images/Wallpapers/* &
/usr/X11R6/bin/xclock -digital -update 1 -render &
echo $! > /var/run/xclock.pid
fi

#sxpm OpenBSD.xpm &


=> GiveConsole

#!/bin/sh
# Assign ownership of the console to the invoking user
# $OpenBSD: GiveConsole,v 1.1 2016/10/23 08:30:37 matthieu Exp $
#
# By convention, both xconsole and xterm -C check that the
# console is owned by the invoking user and is readable before attaching
# the console output.  This way a random user can invoke xterm -C without
# causing serious grief.
#
chown $USER /dev/console

if [ -c /dev/drm0 ]; then
chown $USER /dev/drm0
fi

/usr/X11R6/bin/sessreg -a -l $DISPLAY -u none -x
/etc/X11/xenodm/Xservers $USER

if test -r /var/run/xclock.pid; then kill $(cat /var/run/xclock.pid); fi


=> Xenodm.log:

$ head -n25 /var/log/xenodm.log


xenodm info (pid 46359): Starting
xenodm info (pid 46359): Starting X server on :0

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 6.3 amd64
Current Operating System: OpenBSD ptb-aw13zou.stephane-huc.net 6.3
GENERIC.MP#107 amd64
Build Date: 24 March 2018  02:38:24PM

Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr  3 17:06:54 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
xenodm info (pid 80557): sourcing /home/zou/.config/xenodm/Xsetup_0
xenodm info (pid 80557): sourcing /home/zou/.config/xenodm/GiveConsole
xenodm info (pid 4308): executing session /etc/X11/xenodm/Xsession
WaitForSomething(): poll: Invalid argument
WaitForSomething(): poll: Invalid argument
WaitForSomething(): poll: Invalid argument


=> 

X: WaitForSomething(): poll: Invalid argument

2018-04-04 Thread Stephane HUC "PengouinBSD"
Hi all.

How can identify what trouble X?
I run OpenBSD 6.3 - amd64 on my laptop Dell Alienware 13.

Something fill both logs:
- /var/log/Xorg.0.log
- /var/log/xenodm.log

with this repeated message : "WaitForSomething(): poll: Invalid argument"

I use a custom xorg.conf, as:


Section "InputDevice"
Identifier"Generic Keyboard"
Driver"kbd"
Option"CoreKeyboard"
Option"XkbRules""xorg"
Option"XkbModel""pc105"
Option"XkbLayout"   "fr"  # "fr-oss" pour Feisty et +
#Option"XkbVariant" "latin9"
EndSection

Section "InputDevice"
Identifier"Configured Mouse"
Driver"mouse"
Option"CorePointer"
Option"Device""/dev/input/mice"
Option"Protocol""ExplorerPS/2"
Option"ZAxisMapping""4 5"
Option"Emulate3Buttons""true"
EndSection

Section "Device"
Identifier  "intel" #modesetting, or Intel Graphics
Driver  "intel" #modesetting
Option  "AccelMethod"   "sna"   #sna by default
Option  "DDC"   "true"  #true by default
Option  "DRI"   "true"
Option  "HotPlug"   "true"
Option  "NoAccel"   "false" #false by default
Option  "RelaxedFencing""true"  #true if G33 Model & >
Option  "SwapbuffersWait"   "true"  #true by default (avoid
tearing)
Option  "TearFree"  "true"  #false by default
(avoid tearing)
Option  "Throttle"  "true"  #true by default
Option  "Tiling""true"  #true by default
Option  "TripleBuffer"  "true"  #true by default
#Option "VideoRAM"  ???
Option  "VSync" "true"  #true by default
EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "intel"
Monitor"Monitor0"
DefaultDepth   24 #Choose the depth (16|24)
SubSection "Display"
Depth  16
Modes  "1920x1080" "1400x1050" "1290X1024"
"1280X960" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1920x1080" "1400x1050"
"1290X1024" "1280X960" "1024x768" "800x600"
EndSubSection
EndSection

Section "ServerLayout"
Identifier"Default Layout"
Screen"Screen0"
#InputDevice   "Generic Keyboard"
#InputDevice   "Configured Mouse"
EndSection



Egual for xenodm, i use two custom files:

=> Xsetup_0:

#!/bin/sh
# $OpenBSD: Xsetup_0,v 1.1 2016/10/23 08:30:37 matthieu Exp $
if [ "$DISPLAY" = ":0" -o "$DISPLAY" = ":0.0" ]
then
/usr/local/bin/qiv -zrd7 /home/zou/Images/Wallpapers/* &
/usr/X11R6/bin/xclock -digital -update 1 -render &
echo $! > /var/run/xclock.pid
fi

#sxpm OpenBSD.xpm &

=> GiveConsole

#!/bin/sh
# Assign ownership of the console to the invoking user
# $OpenBSD: GiveConsole,v 1.1 2016/10/23 08:30:37 matthieu Exp $
#
# By convention, both xconsole and xterm -C check that the
# console is owned by the invoking user and is readable before attaching
# the console output.  This way a random user can invoke xterm -C without
# causing serious grief.
#
chown $USER /dev/console

if [ -c /dev/drm0 ]; then
chown $USER /dev/drm0
fi

/usr/X11R6/bin/sessreg -a -l $DISPLAY -u none -x
/etc/X11/xenodm/Xservers $USER

if test -r /var/run/xclock.pid; then kill $(cat /var/run/xclock.pid); fi


=> Xenodm.log:

$ head -n25 /var/log/xenodm.log


xenodm info (pid 46359): Starting
xenodm info (pid 46359): Starting X server on :0

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 6.3 amd64
Current Operating System: OpenBSD ptb-aw13zou.stephane-huc.net 6.3
GENERIC.MP#107 amd64
Build Date: 24 March 2018  02:38:24PM

Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr  3 17:06:54 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
xenodm info (pid 80557): sourcing /home/zou/.config/xenodm/Xsetup_0
xenodm info (pid 80557): sourcing /home/zou/.config/xenodm/GiveConsole
xenodm info (pid 4308): executing session /etc/X11/xenodm/Xsession
WaitForSomething(): poll: Invalid argument
WaitForSomething(): poll: Invalid argument
WaitForSomething(): poll: Invalid argument


=> Xorg.0.log:

$ tail -n25 /var/log/Xorg.0.log


[ 

Xorg: [ 18934.694] WaitForSomething(): poll: Invalid argument

2018-04-04 Thread Stephane HUC "PengouinBSD"
Hi all.

I run OpenBSD 6.3 with Xfce on my laptop.

Something fill the log /var/log/Xorg.0.log. with the repeted message
"WaitForSomething(): poll: Invalid argument", as :

$ tail -n25 /var/log/Xorg.0.log


[ 18934.693] WaitForSomething(): poll: Invalid argument
[ 18934.693] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument
[ 18934.694] WaitForSomething(): poll: Invalid argument

the file grow up!

$ ls -al /var/log/Xorg.0.log


-rw-r--r--  1 root  wheel  5521735640 Apr  3 22:55 /var/log/Xorg.0.log

i use a custom xorg.conf:

Section "InputDevice"
Identifier"Generic Keyboard"
Driver"kbd"
Option"CoreKeyboard"
Option"XkbRules""xorg"
Option"XkbModel""pc105"
Option"XkbLayout"   "fr"  # "fr-oss" pour Feisty et +
#Option"XkbVariant" "latin9"
EndSection

Section "InputDevice"
Identifier"Configured Mouse"
Driver"mouse"
Option"CorePointer"
Option"Device""/dev/input/mice"
Option"Protocol""ExplorerPS/2"
Option"ZAxisMapping""4 5"
Option"Emulate3Buttons""true"
EndSection

Section "Device"
Identifier  "intel" #modesetting, or Intel Graphics
Driver  "intel" #modesetting
Option  "AccelMethod"   "sna"   #sna by default
Option  "DDC"   "true"  #true by default
Option  "DRI"   "true"
Option  "HotPlug"   "true"
Option  "NoAccel"   "false" #false by default
Option  "RelaxedFencing""true"  #true if G33 Model & >
Option  "SwapbuffersWait"   "true"  #true by default (avoid
tearing)
Option  "TearFree"  "true"  #false by default
(avoid tearing)
Option  "Throttle"  "true"  #true by default
Option  "Tiling""true"  #true by default
Option  "TripleBuffer"  "true"  #true by default
#Option "VideoRAM"  ???
Option  "VSync" "true"  #true by default
(avoid tearing)
EndSection

#Section "Extensions"
# fixes tearing with vdpau/vsync
#   Option  "Composite" "Disable"
#EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "intel"
Monitor"Monitor0"
DefaultDepth   24 #Choose the depth (16|24)
SubSection "Display"
Depth  16
Modes  "1920x1080" "1400x1050" "1290X1024"
"1280X960" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1920x1080" "1400x1050"
"1290X1024" "1280X960" "1024x768" "800x600"
EndSubSection
EndSection

Section "ServerLayout"
Identifier"Default Layout"
Screen"Screen0"
#InputDevice   "Generic Keyboard"
#InputDevice   "Configured Mouse"
EndSection


How can identify where is the problem?



-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net



Re: Using stmp auth for local account with PHP scripts

2018-04-04 Thread Christophe Simon

Hello,

I'd say that all depends on the function/library you're using in your 
PHP application to send mails.


The `mail()` command, for instance, uses the `sendmail` binary to 
directly ingest your message in your local mail spool, and thus does not 
require any authentication. The mail is sent on behalf of the identity 
your web server runs under. There's options to set the appropriate 
sender in the message headers, obviously.


If you're using a library such as `PHPMailer`, you'll want to use the 
SMTP protocol, either locally (on lo0) (1), or remotely (on your mail 
provider's SMTP service) (2).


It's up to you to define if you want authentication on the loopback port 
(but that's better to do so).


If you're using your local MTA to send emails (1), either using the SMTP 
protocol on lo0 or the `sendmail` binary, there's chances you'll want to 
use a relay host to avoid being blacklisted by your recipients servers 
(or you should take care to have a resolvable public IP with correct SPF 
configured in your DNS). Such a configuration has been very well 
illustrated by Michael below.


I hope I correctly understood your question and I'm clear enough.

Regards.

Le 04/03/18 à 18:21, Michael Hekeler a écrit :

Am Sun, 01 Apr 2018 17:28:29 +0200
schrieb Markus Rosjat :


Hi there,

There are simple ways of relaying local mails(connection on lo0 on
port 25) to a other mailserver. This is oky for logs and stuff but
what's about mails created by a php on the local webserver? His do I
get smtpd to still do a auth with username and pwd on lo0? Is it
possible or do I need to configure the "external" addr too for this
purpose?



Hello Markus,

I am not sure if I understand your question...
But to relay emails on an internal webserver you have to set the
following 2 lines in /etc/mail/smtpd.conf:

   table passwd file:/etc/mail/secrets
   accept from any \
 for any \
 relay via tls+auth://foo@mailserver auth 


and in /etc/mail/secrets:

   foo  username:passwword



Thats all. Simple.






Re: wireless installation

2018-04-04 Thread Christoph R. Murauer
> misc.n...@gmx.com (misc nick), 2018.04.04 (Wed) 11:38 (CEST):
>> I would like to install OpenBSD wirelessly, but my card requires
>> additional firmware (iwn) that is not included in the installer. Is
>> there a way to overcome this obstacle?

Yes, build a custom image.
You don't tell much details so (IMHO) your options are download the
complete .iso / .fs and the firmware or, download the required sets
and the firmware to another disk and mount it during installation
using bsd.rd.

Even you have no internet connection after the first boot (lets say
you have only iwn) - IIRC - you can install the firmware using
pkg_add.

>
> I you check http://firmware.openbsd.org/firmware/ and see
> fw_update(1)'s
> -p switch then everything would be there to prepare.
>
> But I do not know from the top of my head whether fw_update is
> included
> in the RAMDISK kernels.

No, it is not included.


Regards,

Christoph




Re: wireless installation

2018-04-04 Thread Marcus MERIGHI
misc.n...@gmx.com (misc nick), 2018.04.04 (Wed) 11:38 (CEST):
> I would like to install OpenBSD wirelessly, but my card requires
> additional firmware (iwn) that is not included in the installer. Is
> there a way to overcome this obstacle?

I you check http://firmware.openbsd.org/firmware/ and see fw_update(1)'s
-p switch then everything would be there to prepare.

But I do not know from the top of my head whether fw_update is included
in the RAMDISK kernels. 

*If* it is, you can escape the installer at any prompt with "!" + enter
and run fw_update -p /your_mount_point/ your_driver.

That one usb wlan dongle I have that *does not* require a firmware... 
I keep it as one of my most important tools.

Marcus



wireless installation

2018-04-04 Thread misc nick
I would like to install OpenBSD wirelessly, but my card requires additional 
firmware (iwn) that is not included in the installer. Is there a way to 
overcome this obstacle?



Re: [Arduino] CLI serial monitor

2018-04-04 Thread Janne Johansson
2018-04-04 4:58 GMT+02:00 Olivier Burelli :

> Hello,
>
> i am playing with ARDUINO UNO on my 6.2 stable laptop.
> I am trying to read the serial monitor message from the board.
>
> from dmesg:
> (...)
> umodem0 at uhub3 port 1 configuration 1 interface 0 "Arduino SrlArduino
> Uno" rev 1.10/0.01 addr 3
> umodem0: data interface 1, has no CM over data, has break
> umodem0: status change notification available
> ucom0 at umodem0
> --> which device is corresponding ?
>
>
>
ucom0 from dmesg means it is /dev/cuaU0 (and /dev/ttyU0), ucom1 -> cuaU1
and so on.
Then use "cu" or something if you want to interact with it manually.
"cu -s 9600 -l /dev/cuaU0" for 9k6 connections. (though 115200 is probably
nicer,
otherwise the Serial.print()s will spend too much time talking slow to the
computer
which also can handle lots faster speeds.

-- 
May the most significant bit of your life be positive.


Re: httpd.conf path substitution

2018-04-04 Thread Markus Rosjat



Am 04.04.2018 um 00:05 schrieb Michael Hekeler:

Am Thu, 29 Mar 2018 17:13:10 +0200
schrieb Michael Hekeler :



Ah - I see what you try to do...

But SNI doesn´t mean one single certificate for multiple hostnames
(this you can do with multiple entries in the certificate subject alt
name).

SNI means to server multiple hostnames on ONE ip address



jepp thats what it is


SNI is an extension by which a client (e.g. a webbrowser) indicates
(hence the name: server name INDICATION) one of these multiple
hostnames to be in the TLS handshake. Then the server can choose the
right certifificate to present to the client.



I know


So if you want to serve domain1, domain2 and domain3 each on https then
you need
cert1 for domain1 and
cert2 for domain2 and
cert3 for domain3



I have that basically but some Domains belong, in a way, together and 
could be served with one cert.



If every domain has its own ip then you don´t need SNI.
But if all domains share the same ip, then the client and the server
must be SNI compatible.
When the client requests domain2 the server will be able to present
cert2.

Of course you can issue a single cert with domain1, domain2 and
domain3 in certificate´s subject name and configure the server to
present this cert on every request. But that´s no SNI.



it only presents this cert for the specific virtual hosts


Anyway I'm okay with the fact to hardcode the path to the cert into the 
virtual host definition. I was just wondering if I did something wrong 
or it's simply not supported.


Regards

--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before 
you print it, think about your responsibility and commitment to the 
ENVIRONMENT




Audio stuttering on media playback with sndiod

2018-04-04 Thread Daniel Bolgheroni
Hi,

audio is stuttering on media playback when run through sndiod. It's OK
without it.

Here is an example of audio/cmus attaching to play a mp3 file:

x250$ doas sndiod -ddd
snd0 pst=cfg.default: rec=0:1 play=0:1 vol=23170 dup
helper(helper|ini): created
worker(worker|ini): created
listen(/tmp/aucat/aucat0|ini): created
sock(sock|ini): created
helper: recv: cmd = 0, num = 0, mode = 3, fd = -1
helper: send: cmd = 3, num = 0, mode = 0, fd = 3
sock,rmsg,widl: AUTH message
sock,rmsg,widl: HELLO message
sock,rmsg,widl: hello from , mode = 1, ver 7
sock,rmsg,widl: using snd0 pst=cfg.default, mode = 1
cmus0: overwritten slot 0
snd0 pst=cfg: device requested
worker: send: cmd = 0, num = 0, mode = 3, fd = -1
worker: recv: cmd = 3, num = 0, mode = 0, fd = 6
sio(rsnd/0|ini): created
snd0 pst=ini: 48000Hz, s16le, play 0:1, rec 0:1, 8 blocks of 960 frames
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: SETPAR message
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: playback channels 0:1 -> 0:1
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 44100Hz sample rate, 882 frame blocks
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 13230 frame buffer
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: START message
cmus0 vol=127,pst=ini,mmc=off: playing s16le -> s16le
cmus0 vol=127,pst=ini,mmc=off: allocated 13230/20286 fr buffers
cmus0 vol=127,pst=sta,mmc=off: 44100Hz, s16le, play 0:1, 15 blocks of 882 frames
cmus0 vol=127,pst=sta,mmc=off,rmsg,widl: building SETVOL message, vol = 127
snd0 pst=ini: device started
snd0 pst=run: started
cmus0 vol=127,pst=run,mmc=off: attached at -7056, delta = 0
cmap: nch = 2, ostart = 0, onext = 0, istart = 0, inext = 0
resamp: 882/960
cmus0 vol=127,pst=run,mmc=off: set weight: 23170/23170
snd0 pst=run: rec hw xrun, rused = 5760/7680
snd0 pst=run: play hw xrun, pused = 1920/7680
snd0 pst=run: rec hw xrun, rused = 4800/7680
snd0 pst=run: play hw xrun, pused = 2880/7680
snd0 pst=run: rec hw xrun, rused = 3840/7680
snd0 pst=run: play hw xrun, pused = 3840/7680
snd0 pst=run: rec hw xrun, rused = 2880/7680
snd0 pst=run: play hw xrun, pused = 4800/7680
snd0 pst=run: rec hw xrun, rused = 1920/7680
snd0 pst=run: play hw xrun, pused = 5760/7680
snd0 pst=run: rec hw xrun, rused = 960/7680
snd0 pst=run: play hw xrun, pused = 6720/7680
snd0 pst=run: rec hw xrun, rused = 5760/7680
snd0 pst=run: play hw xrun, pused = 1920/7680
snd0 pst=run: rec hw xrun, rused = 4800/7680
snd0 pst=run: play hw xrun, pused = 2880/7680
snd0 pst=run: rec hw xrun, rused = 3840/7680
snd0 pst=run: play hw xrun, pused = 3840/7680
snd0 pst=run: rec hw xrun, rused = 2880/7680
snd0 pst=run: play hw xrun, pused = 4800/7680
snd0 pst=run: rec hw xrun, rused = 1920/7680
snd0 pst=run: play hw xrun, pused = 5760/7680
snd0 pst=run: rec hw xrun, rused = 960/7680
snd0 pst=run: play hw xrun, pused = 6720/7680
snd0 pst=run: rec hw xrun, rused = 5760/7680
snd0 pst=run: play hw xrun, pused = 1920/7680
snd0 pst=run: rec hw xrun, rused = 4800/7680
snd0 pst=run: play hw xrun, pused = 2880/7680
snd0 pst=run: rec hw xrun, rused = 3840/7680
snd0 pst=run: play hw xrun, pused = 3840/7680

(... flood)

The same on a X220 gives me this (it's OK here):

x220$ doas sndiod -ddd
snd0 pst=cfg.default: rec=0:1 play=0:1 vol=23170 dup
helper(helper|ini): created
worker(worker|ini): created
listen(/tmp/aucat/aucat0|ini): created
sock(sock|ini): created
helper: recv: cmd = 0, num = 0, mode = 3, fd = -1
helper: send: cmd = 3, num = 0, mode = 0, fd = 3
sock,rmsg,widl: AUTH message
sock,rmsg,widl: HELLO message
sock,rmsg,widl: hello from , mode = 1, ver 7
sock,rmsg,widl: using snd0 pst=cfg.default, mode = 1
cmus0: overwritten slot 0
snd0 pst=cfg: device requested
worker: send: cmd = 0, num = 0, mode = 3, fd = -1
worker: recv: cmd = 3, num = 0, mode = 0, fd = 6
sio(rsnd/0|ini): created
snd0 pst=ini: 48000Hz, s16le, play 0:1, rec 0:1, 8 blocks of 960 frames
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: SETPAR message
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: playback channels 0:1 -> 0:1
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 44100Hz sample rate, 882 frame blocks
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 13230 frame buffer
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: START message
cmus0 vol=127,pst=ini,mmc=off: playing s16le -> s16le
cmus0 vol=127,pst=ini,mmc=off: allocated 13230/20286 fr buffers
cmus0 vol=127,pst=sta,mmc=off: 44100Hz, s16le, play 0:1, 15 blocks of 882 frames
cmus0 vol=127,pst=sta,mmc=off,rmsg,widl: building SETVOL message, vol = 127
snd0 pst=ini: device started
snd0 pst=run: started
cmus0 vol=127,pst=run,mmc=off: attached at -7056, delta = 0
cmap: nch = 2, ostart = 0, onext = 0, istart = 0, inext = 0
resamp: 882/960
cmus0 vol=127,pst=run,mmc=off: set weight: 23170/23170

I couldn't spot any difference in the initialization, but on the run,
the former case is flooded with this pair