Re: spurious synproxy warning from pfctl

2022-10-24 Thread dirk coetzee
 
  pass *in* proto tcp from any to mail.example.com \
                port { 25 80 110 143 443 587 993 } synproxy state

How hard can that be?
A message saying synproxy is applied inbound and not outbound is necessary for 
those which might assume that synproxy is being applied eitherbound. 

You are not a victim of being "barked at". 


On Tuesday, 25 October 2022 at 03:08:01 am AWST, Lyndon Nerenberg 
(VE7TFX/VE6BBM)  wrote:  
 
 Given the rule

  pass proto tcp from any to mail.example.com \
                port { 25 80 110 143 443 587 993 } synproxy state

pfctl barks

 /etc/pf.conf:586: warning: synproxy used for inbound rules only, ignored for 
outbound

It's pretty obvious from reading pf.conf(5) that the above is the
default behaviour, and it seems perfectly reasonable to apply
'synproxy state' to pass rule that implies 'in'.  So I don't see
the reason for pfctl to nag at me like that,

It would be nice if simple pass rules like the above did not provoke
that warning message.

--lyndon

  


sysupdate and space check

2022-10-24 Thread Peter Fraser
I make a stupid mistake; I didn't check partition sizes before doing a 
sysupgrade.
sysupgrade ran out of space or /usr in the middle of the upgrade.
I know I should have checked first but it would be nice if sysupgrade did warn 
me.
The site was a 20-minute drive away, and their down time was a lot longer then 
I expected.



spurious synproxy warning from pfctl

2022-10-24 Thread Lyndon Nerenberg (VE7TFX/VE6BBM)
Given the rule

  pass proto tcp from any to mail.example.com \
port { 25 80 110 143 443 587 993 } synproxy state

pfctl barks

 /etc/pf.conf:586: warning: synproxy used for inbound rules only, ignored for 
outbound

It's pretty obvious from reading pf.conf(5) that the above is the
default behaviour, and it seems perfectly reasonable to apply
'synproxy state' to pass rule that implies 'in'.  So I don't see
the reason for pfctl to nag at me like that,

It would be nice if simple pass rules like the above did not provoke
that warning message.

--lyndon



Re: Re-enable trackpad after resuming from hibernate

2022-10-24 Thread Marcus MERIGHI
srira...@berkeley.edu (Sriranga Veeraraghavan), 2022.10.24 (Mon) 10:18 (CEST):
> I just installed OpenBSD 7.2 on my Surface Go 3, and everything seems
> to work as well as it did with OpenBSD 7.1 on my Surface Go 2, except
> for one thing - the trackpad is not enabled after resuming from
> hibernate (the keyboard and the touch screen are enabled).  I can 
> re-enable the trackpad manually with:
>
> xinput --enable /dev/wsmouse2
> 
> I have tried putting this in /etc/apm/resume, but it doesn’t seem to
> work.

When running X.Org things from hotplugd or apmd, remember these run as
root and aren't allowed to run commands in your X environment.

/usr/bin/su -l -s /bin/sh  \
-c "xinput --enable /dev/wsmouse2"

That might do the job. Possibly you have to use xhost(1) too, 
I do not remember atm. 

Marcus
 
> Has anyone experienced something similar?  If so, are there any
> recommendations on how to automatically re-enabled a trackpad after
> resuming from hibernate?



Re: Unimplemented httpd socket? (/var/run/httpd.sock)

2022-10-24 Thread Jason McIntyre
On Sun, Oct 23, 2022 at 10:17:20PM -0400, Dante Catalfamo wrote:
> Hey,
> 
> I was reading the httpd(8) and noticed that there's a reference to a
> socket located at `/var/run/httpd.sock'. It says it's a "UNIX-domain
> socket used for communication with httpd". I was hoping maybe it would
> be used to provide live statistics about httpd, but it's not present
> when httpd is running and I can't find any reference to it anywhere in
> the code other than where the constant is defined in `httpd.h`
> https://github.com/openbsd/src/blob/cfac8e34c1bf89a9feaa77cc4f2e409c3ee998b3/usr.sbin/httpd/httpd.h#L47.
> 
> Is this a leftover from a planned feature that never got implemented?
> 
> Thanks,
> Dante
> 

hi.

they're unused, and we've just removed the references to them.

jmc



Re: Running/Contributing to OpenBSD on Core/Libreboot

2022-10-24 Thread Stuart Henderson
On 2022-10-23, AJ  wrote:
> Hello. I'd like to ask two questions about running OpenBSD on
> Core/Librebooted machines:
>
> (1) I know there's been compatibility issues in the past. Is it still
> the case?

AFAIK it depends on how well coreboot supports the machine.

It's not so much about coreboot itself but whether the configuration
for that machine sets things up properly for a general purpose OS.
In some cases shortcuts might have been taken and people didn't go
further than "linux boots, that's good enough".

I would think that machines supplied with coreboot in the first place
are generally likely to do better than ones where it's been hacked
into place.

For example PC Engines APU boards use coreboot natively and they're
usually fine. The places we've seen more problems with coreboot
are where people have replaced existing laptop BIOS/UEFI with
coreboot and sometimes that doesn't go so well.

-- 
Please keep replies on the mailing list.



Re: rrdtool fails to install on 7.2 due to freetype.30.2 not found for cairo

2022-10-24 Thread Jim Anderson
Been living too long in RedHat world; installing xbase72 fixed it.

Thanks to you both!



--- Original Message ---
On Monday, October 24th, 2022 at 04:32, Stuart Henderson 
 wrote:


> On 2022-10-24, Jim Anderson thesemicol...@protonmail.com wrote:
> 
> > Installed 7.2 and rrdtool will not install due to an error
> > installing freetype for cairo.
> > 
> > # pkg_add rrdtool
> 
> ..
> 
> > Can't install cairo-1.17.6 because of libraries
> > |library freetype.30.2 not found
> > | /usr/X11R6/lib/libfreetype.so.30.0 (system): minor is too small
> > | /usr/X11R6/lib/libfreetype.so.30.1 (system): minor is too small
> 
> 
> You didn't update xbase when you updated to 7.2. Re-run the 7.2
> installer (probably "boot /bsd.rd" at the boot loader prompt) and do
> another upgrade install to 7.2 selecting all sets, then run pkg_add -u,
> before installing new packages.
> 
> --
> Please keep replies on the mailing list.



Re: X/DRM freeze on 7.2

2022-10-24 Thread Patrick Harper
Hi,

https://docs.mesa3d.org/envvars.html#radeonsi-driver-environment-variables

For me freezes happen only when hardware acceleration is enabled so this
might be a good place to start.

-- 
  Patrick Harper
  paia...@fastmail.com

On Fri, 21 Oct 2022, at 19:56, Mickael Torres wrote:
> Hello,
>
> Since upgrading to 7.2, I have X/DRM freezes on one computer (dmesg below).
>
> When it happens, the screen is completely frozen, but I can still ssh 
> to the machine.
> It only happened when starting firefox or VLC, for now. Once they are 
> started I didn't have any
> problem.
> When the machine is in that state, the X and firefox processes are in 
> the DRM wait state:
> 87821 _x11 -200   97M  110M idle  DRM   0:01  0.00% Xorg
> 76467 mike -200   12M   28M idle  DRM   0:00  0.00% 
> firefox
> 51234 mike -200 5972K   49M idle  DRM   0:00  0.00% 
> firefox
> Nothing in dmesg or Xorg.0.log.
>
> As far as I can remember, it never happened with 7.1.
>
> Is there anything I can do to further debug this?
>
> Best,
> Mickael
>
> OpenBSD 7.2 (GENERIC.MP) #758: Tue Sep 27 11:57:54 MDT 2022
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 68598935552 (65421MB)
> avail mem = 66502520832 (63421MB)
> random: good seed from bootblocks
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xbda23000 (49 entries)
> bios0: vendor American Megatrends International, LLC. version "F37d" 
> date 07/27/2022
> bios0: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
> acpi0 at bios0: ACPI 6.2
> acpi0: sleep states S0 S4 S5
> acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT FIDT MCFG HPET SSDT IVRS 
> FPDT VFCT BGRT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT
> acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) 
> GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) 
> GPPE(S4) GPPF(S4) GP10(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 32 bits
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xf000, bus 0-127
> acpihpet0 at acpi0: 14318180 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.08 MHz, 19-21-00
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 
> 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 100MHz
> cpu0: mwait min=64, max=64, C-substates=1.1, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 
> 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00
> cpu2: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 
> 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache
> cpu2: smt 0, core 2, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00
> cpu3: 
> 

Re: Re-enable trackpad after resuming from hibernate

2022-10-24 Thread Stuart Henderson
On 2022-10-24, Sriranga Veeraraghavan  wrote:
> Hi,
>
> I just installed OpenBSD 7.2 on my Surface Go 3, and everything seems
> to work as well as it did with OpenBSD 7.1 on my Surface Go 2, except
> for one thing - the trackpad is not enabled after resuming from
> hibernate (the keyboard and the touch screen are enabled).  I can 
> re-enable the trackpad manually with:
>
> xinput --enable /dev/wsmouse2
>
> I have tried putting this in /etc/apm/resume, but it doesn’t seem to
> work.
> 
> Has anyone experienced something similar?  If so, are there any
> recommendations on how to automatically re-enabled a trackpad after
> resuming from hibernate?

X clients need to have DISPLAY set, plus access to whatever auth is needed
to connect to your X session, neither of which are usually the case from
/etc/apm/resume.

You can try "su $your_username -c 'env DISPLAY=:0 xinput [...]'".

As for the problem in the first place, a good start would be to make a
bug report that includes dmesg from boot and after resuming, plus the
rest of information that sendbug(1) populates in the template.

-- 
Please keep replies on the mailing list.



Re: sysmerge: what is [leave it for later] good for, actually?

2022-10-24 Thread Harald Dunkel

Hi Amit,

On 2022-10-22 18:29:35, Amit Kulkarni wrote:

You chose later, so now do a "doas sysmerge", and merge it now?



Ah, sorry, my bad. Apparently I wasn't root.

Thank you for the hint
Harri



Re: rrdtool fails to install on 7.2 due to freetype.30.2 not found for cairo

2022-10-24 Thread Joel Carnat
Did you install x* packages?

> Le 24 oct. 2022 à 05:12, Jim Anderson  a écrit :
> 
> Installed 7.2 and rrdtool will not install due to an error
> installing freetype for cairo.
> 
> # pkg_add rrdtool
> quirks-6.42 signed on 2022-10-23T09:59:17Z
> rrdtool-1.7.2p1:pcre-8.44: ok
> rrdtool-1.7.2p1:libffi-3.4.2: ok
> rrdtool-1.7.2p1:sqlite3-3.39.3: ok
> rrdtool-1.7.2p1:xz-5.2.5p2: ok
> rrdtool-1.7.2p1:bzip2-1.0.8p0: ok
> rrdtool-1.7.2p1:libiconv-1.17: ok
> rrdtool-1.7.2p1:gettext-runtime-0.21p1: ok
> rrdtool-1.7.2p1:python-3.9.15p0: ok
> rrdtool-1.7.2p1:glib2-2.72.4: ok
> rrdtool-1.7.2p1:png-1.6.37p0: ok
> rrdtool-1.7.2p1:lzo2-2.10p2: ok
> Can't install cairo-1.17.6 because of libraries
> |library freetype.30.2 not found
> | /usr/X11R6/lib/libfreetype.so.30.0 (system): minor is too small
> | /usr/X11R6/lib/libfreetype.so.30.1 (system): minor is too small
> Direct dependencies for cairo-1.17.6 resolve to png-1.6.37p0
> glib2-2.72.4 lzo2-2.10p2
> 
> Full dependency tree is png-1.6.37p0 xz-5.2.5p2 gettext-runtime-0.21p1
> pcre-8.44 bzip2-1.0.8p0 libiconv-1.17 sqlite3-3.39.3 glib2-2.72.4
> python-3.9.15p0 lzo2-2.10p2 libffi-3.4.2
> 
> rrdtool-1.7.2p1:graphite2-1.3.14: ok
> Can't install harfbuzz-5.2.0: can't resolve cairo-1.17.6
> rrdtool-1.7.2p1:fribidi-1.0.12: ok
> Can't install pango-1.50.10: can't resolve harfbuzz-5.2.0
> rrdtool-1.7.2p1:rrdupdate-1.7.2p1: ok
> rrdtool-1.7.2p1:libxml-2.10.3: ok
> Can't install rrdtool-1.7.2p1: can't resolve pango-1.50.10
> Running tags: ok
> New and changed readme(s):
>/usr/local/share/doc/pkg-readmes/glib2
> Couldn't install cairo-1.17.6 harfbuzz-5.2.0 pango-1.50.10
> rrdtool-1.7.2p1
> 
> # pkg_info
> base64-1.5p0
> curl-7.85.0
> intel-firmware-20220809v0
> kcgi-0.13.0
> nghttp2-1.49.0
> quirks-6.42
> rsync-3.2.5pl0
> 



Re: What happened to www/art on CVSWeb? Why is it empty?

2022-10-24 Thread Dante Catalfamo
I'm curious about this too. I was looking for an image of puffy for a
presentation I'm giving. Without those art pages, I can't find any non-
release-specific versions of it on the site.


On Thu, 2022-02-10 at 12:34 +0100, Kacper Wilgus wrote:
> I tried to download some artwork from these pages:
> 
> https://www.openbsd.org/art1.html
> https://www.openbsd.org/art2.html
> https://www.openbsd.org/art3.html
> 
> But only the first one has an image, the rest of them give me 404
> errors and I swear they used to be there just a year ago. And the
> wayback machine proves this. Was it an error, or copyright issues?
> It seems wierd it was just snapped out of existence without any
> warning.
> 



Re: Running/Contributing to OpenBSD on Core/Libreboot

2022-10-24 Thread Stefan Hagen
AJ wrote (2022-10-23 21:04 CEST):
> Hello. I'd like to ask two questions about running OpenBSD on
> Core/Librebooted machines:

Why don't you try it and report?

I'm running a coreboot machine since 7.0. It works including audio,
suspend, hibernate, video(2d/3d).

OpenBSD 7.2-current (GENERIC.MP) #808: Sun Oct 23 22:38:15 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 33762762752 (32198MB)
avail mem = 32722087936 (31206MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x5ea99040 (18 entries)
bios0: vendor coreboot version "4.13-2504-g656fa56a22-dirty" date 03/08/2021
bios0: 51NB X210
efi0 at bios0: UEFI 2.7
efi0: EDK II rev 0x1
acpi0 at bios0: ACPI 6.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT MCFG LPIT APIC DMAR HPET BGRT
acpi0: wakeup devices XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 3686.55 MHz, 06-8e-0a
cpu0: 
FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 8MB 64b/line 16-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 3686.19 MHz, 06-8e-0a
cpu1: 
FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 8MB 64b/line 16-way L3 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 3690.85 MHz, 06-8e-0a
cpu2: 
FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 8MB 64b/line 16-way L3 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 3690.85 MHz, 06-8e-0a
cpu3: 
FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 
4-way L2 cache, 8MB 64b/line 16-way L3 cache
cpu3: smt 1, core 1, package 0
cpu4 at mainbus0: apid 4 (application processor)
cpu4: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 3690.85 MHz, 06-8e-0a
cpu4: 

Re: rrdtool fails to install on 7.2 due to freetype.30.2 not found for cairo

2022-10-24 Thread Stuart Henderson
On 2022-10-24, Jim Anderson  wrote:
> Installed 7.2 and rrdtool will not install due to an error
> installing freetype for cairo.
>
> # pkg_add rrdtool
..
> Can't install cairo-1.17.6 because of libraries
>|library freetype.30.2 not found
>| /usr/X11R6/lib/libfreetype.so.30.0 (system): minor is too small
>| /usr/X11R6/lib/libfreetype.so.30.1 (system): minor is too small

You didn't update xbase when you updated to 7.2. Re-run the 7.2
installer (probably "boot /bsd.rd" at the boot loader prompt) and do
another upgrade install to 7.2 selecting all sets, then run pkg_add -u,
before installing new packages.

-- 
Please keep replies on the mailing list.



Re-enable trackpad after resuming from hibernate

2022-10-24 Thread Sriranga Veeraraghavan
Hi,

I just installed OpenBSD 7.2 on my Surface Go 3, and everything seems
to work as well as it did with OpenBSD 7.1 on my Surface Go 2, except
for one thing - the trackpad is not enabled after resuming from
hibernate (the keyboard and the touch screen are enabled).  I can 
re-enable the trackpad manually with:

xinput --enable /dev/wsmouse2

I have tried putting this in /etc/apm/resume, but it doesn’t seem to
work.

Has anyone experienced something similar?  If so, are there any
recommendations on how to automatically re-enabled a trackpad after
resuming from hibernate?

Thanks,

-ranga