Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-05 Thread John DiMarco
In message <20170505091608.gd17...@sci.irofti.net>you write: >> 0:6:0: Cirrus Logic CS4610 SoundFusion >> 0x: Vendor ID: 1013 Product ID: 6001 >> 0x0004: Command: 0106 Status: 0200 >> 0x0008: Class: 04 Subclass: 01 Interface: 00 Revision: 01 > >This says you do have clcs(4)

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-05 Thread Paul Irofti
> 0:6:0: Cirrus Logic CS4610 SoundFusion > 0x: Vendor ID: 1013 Product ID: 6001 > 0x0004: Command: 0106 Status: 0200 > 0x0008: Class: 04 Subclass: 01 Interface: 00 Revision: 01 This says you do have clcs(4) hardware on your laptop. What is the exact error you are seeing

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-04 Thread Theo de Raadt
> >In message <20170504150753.GH72850@t430s.bluhm.invalid>you write: > >>On Thu, May 04, 2017 at 09:43:07AM -0400, j...@cs.toronto.edu wrote: > >>> However in OpenBSD 6.1, attempting to run config in this way fails, > >>> with the message: > >>> config: kvm_openfiles: /dev/mem: Operation not

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-04 Thread John DiMarco
>In message <20170504150753.GH72850@t430s.bluhm.invalid>you write: >>On Thu, May 04, 2017 at 09:43:07AM -0400, j...@cs.toronto.edu wrote: >>> However in OpenBSD 6.1, attempting to run config in this way fails, >>> with the message: >>> config: kvm_openfiles: /dev/mem: Operation not

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-04 Thread John DiMarco
In message <20170504150753.GH72850@t430s.bluhm.invalid>you write: >On Thu, May 04, 2017 at 09:43:07AM -0400, j...@cs.toronto.edu wrote: >> However in OpenBSD 6.1, attempting to run config in this way fails, >> with the message: >> config: kvm_openfiles: /dev/mem: Operation not

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-04 Thread Theo Buehler
> The problem here is config(8) -u needs kvm(3) to access the changes made > during boot in UKC, with OpenBSD 6.1 access to /dev/{,k}mem was disabled > at securelevel > 0. Right, and we should probably add the usual text to the description of the -u flag (text taken from tcpbench -k): Index:

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-04 Thread Bryan Steele
On Thu, May 04, 2017 at 09:43:07AM -0400, j...@cs.toronto.edu wrote: > > >Synopsis:On 6.1/i386, config -e -u -o bsd.new bsd reports > >"kvm_openfiles: /dev/mem: Operation not permitted > >Category:system > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1

Re: config in 6.1 reports /dev/mem: Operation not permitted

2017-05-04 Thread Alexander Bluhm
On Thu, May 04, 2017 at 09:43:07AM -0400, j...@cs.toronto.edu wrote: > However in OpenBSD 6.1, attempting to run config in this way fails, > with the message: > config: kvm_openfiles: /dev/mem: Operation not permitted Putting kern.allowkmem=1 into /etc/sysctl.conf and reboot