Re: home printer

2021-02-09 Thread Marcus MERIGHI 
rop...@gmail.com (ropers), 2021.02.08 (Mon) 21:43 (CET):
> On 08/02/2021, Pierre-Philipp Braun  wrote:
>
> Anyway, I don't suppose any of you know whether any of your
> recommended devices have printer steganography built in?

I've been told, by a local xerox technician, to never print any ransom
demand letter with a modern printer because any printout could be
attributed to the serial number of the printer.

Marcus

Re: home printer

2021-02-09 Thread Chris Cappuccio 
Marcus MERIGHI [mcmer-open...@tor.at] wrote:
> 
> I've been told, by a local xerox technician, to never print any ransom
> demand letter with a modern printer because any printout could be
> attributed to the serial number of the printer.
> 

I always email my ransom demand letters so that I can avoid the printer
ratting me out to the FBI.

Re: home printer

2021-02-09 Thread Jan Stary 
On Feb 09 10:35:21, ch...@nmedia.net wrote:
> Marcus MERIGHI [mcmer-open...@tor.at] wrote:
> > 
> > I've been told, by a local xerox technician, to never print any ransom
> > demand letter with a modern printer because any printout could be
> > attributed to the serial number of the printer.
> > 
> 
> I always email my ransom demand letters so that I can avoid the printer
> ratting me out to the FBI.

I always circle the yellow dots
on every ransom note I get
and send it back.

Re: bsd.rd ok , bsd explodes, trying to get traces

2021-02-09 Thread Sven F. 
On Tue, Feb 9, 2021 at 3:45 PM Sven F.  wrote:
>
> Dear readers,
>
> I found a computer which behaves oddly.
> Only EFI boot is supported, I usually go the MBR way.
> The bios looks like a classic AMibios Intel stuff.
> The cpu is intel and there's an intel HD5500 graphic card
> ( trying to extract proper dmesg fails so far )
>
> When booting 6.8 basic amd64 installation the video
> signal is completely lost and network too ( suspect crash )
>
> I tried to `set  db_console 1` and change video mode
> with machine video before booting, and entering
> `boot dump` blindly ( video off )
> but after rebooting in bsd.rd /var/ has no dmesg.anything
> or some log
>
> I think the last line of boot i see is 'softraid0'
>
> There's probably a few tricks I should try to get the actual
> message, I will do my best to extract the (bsd.rd) dmesg now and post it as
> a reply ( and try boot current )
>
> Is there some boot option i can use or something i can do
> to extract the errors ? ( i do not see com ports anywhere either )
>
> Thank you for reading.
> --
> --

Looks like current already solved the problem,

any chance to have this work on 'stable' ?

OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb  9 10:19:03 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8485195776 (8092MB)
avail mem = 8212697088 (7832MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xa4eef000 (81 entries)
bios0: vendor American Megatrends Inc. version "5.011" date 06/19/2019
bios0: Intel H81U
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI LPIT SSDT
ASF! SSDT SSDT SSDT DMAR
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
PEGP(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4)
RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2694.11 MHz, 06-3d-04
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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.79 MHz, 06-3d-04
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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 MHz, 06-3d-04
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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 MHz, 06-3d-04
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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179

bsd.rd ok , bsd explodes, trying to get traces

2021-02-09 Thread Sven F. 
Dear readers,

I found a computer which behaves oddly.
Only EFI boot is supported, I usually go the MBR way.
The bios looks like a classic AMibios Intel stuff.
The cpu is intel and there's an intel HD5500 graphic card
( trying to extract proper dmesg fails so far )

When booting 6.8 basic amd64 installation the video
signal is completely lost and network too ( suspect crash )

I tried to `set  db_console 1` and change video mode
with machine video before booting, and entering
`boot dump` blindly ( video off )
but after rebooting in bsd.rd /var/ has no dmesg.anything
or some log

I think the last line of boot i see is 'softraid0'

There's probably a few tricks I should try to get the actual
message, I will do my best to extract the (bsd.rd) dmesg now and post it as
a reply ( and try boot current )

Is there some boot option i can use or something i can do
to extract the errors ? ( i do not see com ports anywhere either )

Thank you for reading.
-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do

Re: bsd.rd ok , bsd explodes, trying to get traces

2021-02-09 Thread Tom Smyth 
Hey Sven,

sorry just wondering have you tried running an alternate OS  and or memtest
x86 to see if the computer CPU memory is behaving its self  ?

also if it is an intel raid controller it usually has about 3 differentnt
settings (and alters the controllers firmware to present different
hardware   to the os

(legacy--->raid--> AHCI -->Enhanced)
Hope this helps


On Tue, 9 Feb 2021 at 20:56, Sven F.  wrote:

> Dear readers,
>
> I found a computer which behaves oddly.
> Only EFI boot is supported, I usually go the MBR way.
> The bios looks like a classic AMibios Intel stuff.
> The cpu is intel and there's an intel HD5500 graphic card
> ( trying to extract proper dmesg fails so far )
>
> When booting 6.8 basic amd64 installation the video
> signal is completely lost and network too ( suspect crash )
>
> I tried to `set  db_console 1` and change video mode
> with machine video before booting, and entering
> `boot dump` blindly ( video off )
> but after rebooting in bsd.rd /var/ has no dmesg.anything
> or some log
>
> I think the last line of boot i see is 'softraid0'
>
> There's probably a few tricks I should try to get the actual
> message, I will do my best to extract the (bsd.rd) dmesg now and post it as
> a reply ( and try boot current )
>
> Is there some boot option i can use or something i can do
> to extract the errors ? ( i do not see com ports anywhere either )
>
> Thank you for reading.
> --
> --
>
> -
> Knowing is not enough; we must apply. Willing is not enough; we must do
>
>

-- 
Kindest regards,
Tom Smyth.

Latest snapshot, Logitech keyboard not working.

2021-02-09 Thread martin . quach 
On amd64, upgrading from stable to snapshot my Logitech G413 \
keyboard is not sending keypresses. i.e) Pressing the "a" key \
does nothing. There’s an error message saying \
“uhidev_intr: bad repid 48” To test that it's not a
problem with my keyboard I noticed that the function keys still work. \
(The keyboard light). Also to test it's not just my computer I \
plugged in a different keyboard and everything works as it should. \
Below is my dmesg from 6.8 stable:

OpenBSD 6.8 (RAMDISK_CD) #94: Sun Oct 4 18:21:11 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17111998464 (16319MB)
avail mem = 16589369344 (15820MB)
random: good seed from bootblocks
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (60 entries)
bios0: vendor American Megatrends Inc. version "M.60" date 04/18/2020
bios0: Micro-Star International Co., Ltd MS-7B86
acpi0 at bios0: ACPI 6.0
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET UEFI IVRS PCCT 
SSDT CRAT CDIT SSDT
SSDT WSMT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 5 3600 6-Core Processor, 3600.46 MHz, 17-71-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,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXS
,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,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,U
IP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 
8-way L2 cache, 32MB
64b/line disabled L3 cache
cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 13 pa 0xfec0, version 21, 24 pins
ioapic1 at mainbus0: apid 14 pa 0xfec01000, version 21, 32 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (GPP0)
acpiprt2 at acpi0: bus -1 (GPP1)
acpiprt3 at acpi0: bus -1 (GPP3)
acpiprt4 at acpi0: bus -1 (GPP4)
acpiprt5 at acpi0: bus -1 (GPP5)
acpiprt6 at acpi0: bus -1 (GPP6)
acpiprt7 at acpi0: bus -1 (GPP7)
acpiprt8 at acpi0: bus 38 (GPP8)
acpiprt9 at acpi0: bus -1 (GPP9)
acpiprt10 at acpi0: bus -1 (GPPA)
acpiprt11 at acpi0: bus -1 (GPPB)
acpiprt12 at acpi0: bus -1 (GPPC)
acpiprt13 at acpi0: bus -1 (GPPD)
acpiprt14 at acpi0: bus -1 (GPPE)
acpiprt15 at acpi0: bus -1 (GPPF)
acpiprt16 at acpi0: bus -1 (GP10)
acpiprt17 at acpi0: bus 39 (GP12)
acpiprt18 at acpi0: bus 40 (GP13)
acpiprt19 at acpi0: bus 48 (GP30)
acpiprt20 at acpi0: bus 49 (GP31)
acpiprt21 at acpi0: bus 3 (GPP2)
acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x
acpicmos0 at acpi0
"PNP0C0C" at acpi0 not configured
amdgpio0 at acpi0 GPIO uid 0 addr 0xfed81500/0x400 irq 7, 184 pins
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"AMDIF030" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpicpu at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD 17h/3xh Root Complex" rev 0x00
vendor "AMD", unknown product 0x1481 (class system subclass IOMMU, rev 0x00) at 
pci0 dev 0 function
2 not configured
pchb1 at pci0 dev 1 function 0 vendor "AMD", unknown product 0x1482 rev 0x00
ppb0 at pci0 dev 1 function 3 vendor "AMD", unknown product 0x1483 rev 0x00: msi
pci1 at ppb0 bus 3
xhci0 at pci1 dev 0 function 0 vendor "AMD", unknown product 0x43d5 rev 0x01: 
msi, xHCI 1.10
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "AMD xHCI root hub" rev 3.00/1.00 
addr 1
ahci0 at pci1 dev 0 function 1 "AMD 400 Series AHCI" rev 0x01: msi, AHCI 1.3.1
ahci0: port busy after first PMP probe FIS
ahci0: port busy after first PMP probe FIS
ahci0: port 0: 6.0Gb/s
ahci0: port busy after first PMP probe FIS
ahci0: port busy after first PMP probe FIS
ahci0: port 1: 6.0Gb/s
ahci0: port busy after first PMP probe FIS
ahci0: port busy after first PMP probe FIS
ahci0: port 4: 6.0Gb/s
ahci0: port busy after first PMP probe FIS
ahci0: port busy after first PMP probe FIS
ahci0: port 5: 6.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0:  naa.500a07510f0f007b
sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin
sd1 at scsibus0 targ 1 lun 0:  naa.5000c5007a61b7f5
sd1: 953869MB, 512 bytes/sector, 1953525168 sectors
sd2 at scsibus0 targ 4 lun 0:  naa.50014ee20f4b362e
sd2: 953869MB, 512

Re: bsd.rd ok , bsd explodes, trying to get traces

2021-02-09 Thread Sven F. 
On Tue, Feb 9, 2021 at 3:59 PM Sven F.  wrote:
>
> On Tue, Feb 9, 2021 at 3:45 PM Sven F.  wrote:
> >
> > Dear readers,
> >
> > I found a computer which behaves oddly.
> > Only EFI boot is supported, I usually go the MBR way.
> > The bios looks like a classic AMibios Intel stuff.
> > The cpu is intel and there's an intel HD5500 graphic card
> > ( trying to extract proper dmesg fails so far )
> >
> > When booting 6.8 basic amd64 installation the video
> > signal is completely lost and network too ( suspect crash )
> >
> > I tried to `set  db_console 1` and change video mode
> > with machine video before booting, and entering
> > `boot dump` blindly ( video off )
> > but after rebooting in bsd.rd /var/ has no dmesg.anything
> > or some log
> >
> > I think the last line of boot i see is 'softraid0'
> >
> > There's probably a few tricks I should try to get the actual
> > message, I will do my best to extract the (bsd.rd) dmesg now and post it as
> > a reply ( and try boot current )
> >
> > Is there some boot option i can use or something i can do
> > to extract the errors ? ( i do not see com ports anywhere either )
> >
> > Thank you for reading.
> > --
> > --
>
> Looks like current already solved the problem,
>
> any chance to have this work on 'stable' ?
>
> OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb  9 10:19:03 MST 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8485195776 (8092MB)
> avail mem = 8212697088 (7832MB)
> random: good seed from bootblocks
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xa4eef000 (81 entries)
> bios0: vendor American Megatrends Inc. version "5.011" date 06/19/2019
> bios0: Intel H81U
> acpi0 at bios0: ACPI 5.0
> acpi0: sleep states S0 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI LPIT SSDT
> ASF! SSDT SSDT SSDT DMAR
> acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
> PEGP(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4)
> RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2694.11 MHz, 06-3d-04
> 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.79 MHz, 06-3d-04
> 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 1 (application processor)
> cpu2: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 MHz, 06-3d-04
> 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 1, core 0, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 MHz, 06-3d-04
> 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
>

httpd, PHP7.4, phpIPAM, MariaDB

2021-02-09 Thread Jesse Barton 
Hey OpenBSD Community,

I am working on getting phpIPAM setup on a OpenBSD system but so far i'm
running into an issue with connecting the php site to the database.

I used parts of these documentation pages to get everything working.
https://www.php.net/manual/en/install.unix.openbsd.php
https://phpipam.net/documents/installation/

Here is the specific message im getting in my error.log

PHP message: PHP Fatal error:  Uncaught Exception: Could not connect to
database! SQLSTATE[HY000] [2002] No such file or directory in
/htdocs/ipam/functions/classes/class.PDO.php:159
Stack trace:
#0 /htdocs/ipam/functions/classes/class.PDO.php(1053): DB->connect()
#1 /htdocs/ipam/functions/classes/class.PDO.php(298):
Database_PDO->connect()
#2 /htdocs/ipam/functions/classes/class.Common.php(236): DB->escape()
#3 /htdocs/ipam/functions/classes/class.Common.php(411):
Common_functions->fetch_object()
#4 /htdocs/ipam/functions/classes/class.User.php(136):
Common_functions->get_settings()
#5 /htdocs/ipam/index.php(29): User->__construct()
#6 {main}
  thrown in /htdocs/ipam/functions/classes/class.PDO.php on line 159

Im able to log into the database with the desired user running
# mysql -u phpipam -p

my config.php is set
$db['host'] = 'localhost';
$db['user'] = 'username';
$db['pass'] = 'password';
$db['name'] = 'phpipam';
$db['port'] = 3306;

If there is any other information that would be helpful in troubleshooting
this i'm all ears.

Re: httpd, PHP7.4, phpIPAM, MariaDB

2021-02-09 Thread Steve Williams 

Hi,

It is running in a chroot.  No access to "standard" networking files.  
hosts, resolv.conf, etc.


Probably easiest to put the actual IP address in.  I use a socket and 
put in in the chroot folder.  Not sure which is better.


If you run into any other network type issues, suspect the lack of DNS 
resolution (hosts, resolv.conf, etc).


They can be copied into the chroot folder, but then maintenance is an 
issue (and no, symbolic link won't work).


Cheers,
Steve W.

On 09/02/2021 4:30 p.m., Jesse Barton wrote:

Hey OpenBSD Community,

I am working on getting phpIPAM setup on a OpenBSD system but so far i'm
running into an issue with connecting the php site to the database.

I used parts of these documentation pages to get everything working.
https://www.php.net/manual/en/install.unix.openbsd.php
https://phpipam.net/documents/installation/

Here is the specific message im getting in my error.log

PHP message: PHP Fatal error:  Uncaught Exception: Could not connect to
database! SQLSTATE[HY000] [2002] No such file or directory in
/htdocs/ipam/functions/classes/class.PDO.php:159
Stack trace:
#0 /htdocs/ipam/functions/classes/class.PDO.php(1053): DB->connect()
#1 /htdocs/ipam/functions/classes/class.PDO.php(298):
Database_PDO->connect()
#2 /htdocs/ipam/functions/classes/class.Common.php(236): DB->escape()
#3 /htdocs/ipam/functions/classes/class.Common.php(411):
Common_functions->fetch_object()
#4 /htdocs/ipam/functions/classes/class.User.php(136):
Common_functions->get_settings()
#5 /htdocs/ipam/index.php(29): User->__construct()
#6 {main}
   thrown in /htdocs/ipam/functions/classes/class.PDO.php on line 159

Im able to log into the database with the desired user running
# mysql -u phpipam -p

my config.php is set
$db['host'] = 'localhost';
$db['user'] = 'username';
$db['pass'] = 'password';
$db['name'] = 'phpipam';
$db['port'] = 3306;

If there is any other information that would be helpful in troubleshooting
this i'm all ears.

Re: httpd, PHP7.4, phpIPAM, MariaDB

2021-02-09 Thread Jesse Barton 
Using 127.0.0.1 did the job appreciate it.

On Tue, Feb 9, 2021 at 6:28 PM Steve Williams <
st...@williamsitconsulting.com> wrote:

> Hi,
>
> It is running in a chroot.  No access to "standard" networking files.
> hosts, resolv.conf, etc.
>
> Probably easiest to put the actual IP address in.  I use a socket and
> put in in the chroot folder.  Not sure which is better.
>
> If you run into any other network type issues, suspect the lack of DNS
> resolution (hosts, resolv.conf, etc).
>
> They can be copied into the chroot folder, but then maintenance is an
> issue (and no, symbolic link won't work).
>
> Cheers,
> Steve W.
>
> On 09/02/2021 4:30 p.m., Jesse Barton wrote:
> > Hey OpenBSD Community,
> >
> > I am working on getting phpIPAM setup on a OpenBSD system but so far i'm
> > running into an issue with connecting the php site to the database.
> >
> > I used parts of these documentation pages to get everything working.
> > https://www.php.net/manual/en/install.unix.openbsd.php
> > https://phpipam.net/documents/installation/
> >
> > Here is the specific message im getting in my error.log
> >
> > PHP message: PHP Fatal error:  Uncaught Exception: Could not connect to
> > database! SQLSTATE[HY000] [2002] No such file or directory in
> > /htdocs/ipam/functions/classes/class.PDO.php:159
> > Stack trace:
> > #0 /htdocs/ipam/functions/classes/class.PDO.php(1053): DB->connect()
> > #1 /htdocs/ipam/functions/classes/class.PDO.php(298):
> > Database_PDO->connect()
> > #2 /htdocs/ipam/functions/classes/class.Common.php(236): DB->escape()
> > #3 /htdocs/ipam/functions/classes/class.Common.php(411):
> > Common_functions->fetch_object()
> > #4 /htdocs/ipam/functions/classes/class.User.php(136):
> > Common_functions->get_settings()
> > #5 /htdocs/ipam/index.php(29): User->__construct()
> > #6 {main}
> >thrown in /htdocs/ipam/functions/classes/class.PDO.php on line 159
> >
> > Im able to log into the database with the desired user running
> > # mysql -u phpipam -p
> >
> > my config.php is set
> > $db['host'] = 'localhost';
> > $db['user'] = 'username';
> > $db['pass'] = 'password';
> > $db['name'] = 'phpipam';
> > $db['port'] = 3306;
> >
> > If there is any other information that would be helpful in
> troubleshooting
> > this i'm all ears.
>
>

Re: httpd, PHP7.4, phpIPAM, MariaDB

2021-02-09 Thread Edgar Pettijohn 
On Tue, Feb 09, 2021 at 05:30:52PM -0600, Jesse Barton wrote:
> Hey OpenBSD Community,
> 
> I am working on getting phpIPAM setup on a OpenBSD system but so far i'm
> running into an issue with connecting the php site to the database.
> 
> I used parts of these documentation pages to get everything working.
> https://www.php.net/manual/en/install.unix.openbsd.php
> https://phpipam.net/documents/installation/
> 
> Here is the specific message im getting in my error.log
> 
> PHP message: PHP Fatal error:  Uncaught Exception: Could not connect to
> database! SQLSTATE[HY000] [2002] No such file or directory in
> /htdocs/ipam/functions/classes/class.PDO.php:159
> Stack trace:
> #0 /htdocs/ipam/functions/classes/class.PDO.php(1053): DB->connect()
> #1 /htdocs/ipam/functions/classes/class.PDO.php(298):
> Database_PDO->connect()
> #2 /htdocs/ipam/functions/classes/class.Common.php(236): DB->escape()
> #3 /htdocs/ipam/functions/classes/class.Common.php(411):
> Common_functions->fetch_object()
> #4 /htdocs/ipam/functions/classes/class.User.php(136):
> Common_functions->get_settings()
> #5 /htdocs/ipam/index.php(29): User->__construct()
> #6 {main}
>   thrown in /htdocs/ipam/functions/classes/class.PDO.php on line 159
> 
> Im able to log into the database with the desired user running
> # mysql -u phpipam -p
>

> my config.php is set
> $db['host'] = 'localhost';

I would try changing the above to '127.0.0.1'

Edgar

> $db['user'] = 'username';
> $db['pass'] = 'password';
> $db['name'] = 'phpipam';
> $db['port'] = 3306;
> 
> If there is any other information that would be helpful in troubleshooting
> this i'm all ears.

C99 math functions ilogb, ilogbf fail test

2021-02-09 Thread Yuki Kimoto 
Hi,

I'm Yuki Kimoto. I'm Perl CPAN Author.

I'm currently writing a module SPVM in Perl that binds C99 math functions.

SPVM - Static Perl Virtual Machine. Fast Calculation, Fast Array Operation,
and Easy C/C++ Binding. - metacpan.org 

In CPAN testers, some tests failed. that seems like ilogb and ilogbf

CPAN Testers Reports: FAIL SPVM-0.0932 5.30.2 OpenBSD


If you have information for these function bugs, can you tell me?

Re: C99 math functions ilogb, ilogbf fail test

2021-02-09 Thread Yuki Kimoto 
Thank you. Andrew Hewus Fresh

It seems like fixed ilogb and ilogbf bugs in OpenBSD 6.8.


SPVM_Util.t test failing seem like srand.

This should be skipped in OpenBSD.


2021年2月10日(水) 14:40 Andrew Hewus Fresh :

> On Wed, Feb 10, 2021 at 01:58:37PM +0900, Yuki Kimoto wrote:
> > I'm Yuki Kimoto. I'm Perl CPAN Author.
>
> Hello, I too am a CPAN author, it's a nice group of folks to be a part
> of.  I do need to do a better job of maintaining my modules though.
>
> > I'm currently writing a module SPVM in Perl that binds C99 math
> functions.
> >
> > SPVM - Static Perl Virtual Machine. Fast Calculation, Fast Array
> Operation,
> > and Easy C/C++ Binding. - metacpan.org 
>
> Very exciting!
>
>
> > In CPAN testers, some tests failed. that seems like ilogb and ilogbf
> >
> > CPAN Testers Reports: FAIL SPVM-0.0932 5.30.2 OpenBSD
> > <
> http://www.cpantesters.org/cpan/report/1b13d240-6ad5-11eb-84bc-edd243e66a77
> >
>
> Unfortunately that test is from an out-of-support version of perl and
> the build doesn't seem to like the "-j8" that my smoker uses so I can't
> find any useful reports.
>
> http://www.cpantesters.org/cpan/report/b876eef8-6a0f-11eb-b536-bba28fda8de9
>
>
> > If you have information for these function bugs, can you tell me?
>
>
> Also with all the warning noise in that log it's hard to know quite what
> is going wrong.  A simpler and smaller snippet of what isn't working
>
> I did try running these tests again on my laptop running a recent
> snapshot of OpenBSD and there were still a few failures, but not nearly
> as many.
>
> t/default/SPVM_Util.t (Wstat: 256 Tests: 115 Failed: 1)
>   Failed test:  38
>   Non-zero exit status: 1
> t/precompile/SPVM_Util.t  (Wstat: 256 Tests: 115 Failed: 1)
>   Failed test:  38
>   Non-zero exit status: 1
> Files=193, Tests=3587, 269 wallclock secs ( 1.11 usr  1.95 sys + 203.14
> cusr 48.67 csys = 254.87 CPU)
> Result: FAIL
> Failed 2/193 test programs. 2/3587 subtests failed.
>
>
> Attached is a script(1) log of those tests, perhaps you will be able to
> pull more detail from those.
>
> l8rZ,
> --
> andrew - http://afresh1.com
>
> Software doesn't do what you want it to do, it does what you tell it do.
>   -- Stefan G. Weichinger.
>

Re: home printer

2021-02-09 Thread Stuart Longland 
On 9/2/21 6:43 am, ropers wrote:
> * Printer steganography -- which I've positively confirmed is indeed there,
>   and which I neither asked for, nor was at any time told anything about by
>   Xerox, especially not pre-purchase.

I think this is situation normal for any printer made this decade.
Don't like it?  You have three choices:

1. Find a way to coax an ancient parallel port printer to work with your
modern Unix workstation.
2. Make your own printer.
3. Don't print.

(1) could be achieved two ways:

(1a) using either a standard LPT-to- adaptor.  (e.g.
LPT-to-USB, there are also LPT print servers that present an lpd interface)
(1b) with off-the-shelf modules to interface to the Centronics interface
on the printer (which is 5V TTL IIRC) to one of the myriad of 5V-TTL
compatible microcontroller dev boards out there and doing some hacking
of the print spooler in OpenBSD along with some firmware development.

(2) has been done various ways (e.g. HomoFaciens on YouTube did a
junk-box printer using a pen, scrap motors, hand-made optical encoders
and an Arduino dev board)… admittedly resolution and print speed are
both poor in such systems unless you're very mechanically and
electronically skilled.  You may also have to forgo conveniences such as
an automatic sheet feeder or out-of-pigment notifications.

Many people are doing (3) now, having decided they don't use a printer
often enough to justify the cost of maintaining one.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Installation overwritten... Accidental disklabel and newfs

2021-02-09 Thread Ed Gray 
Hi,

So I was upgrading my box to 6.8 and managed to accidentally overwrite my
disklabel and filesystems. I ran install instead of upgrade and stopped
after the filesystem creation when I realized my mistake (see ending
paragraphs).

The new disklabel was different due to auto allocation changes and newfs
has written new data on the disk but the install went no further.

I cannot work out exactly where /usr should start because I adjusted some
of the auto allocations in the past and I don't therefore know what
positions the volumes start at.

I have backups and will probably not have lost anything important but I
just wondered if anyone had any suggestions as to whether this is fixable
and what steps to take before I give up and re-install? I followed a how-to
I found which suggested using scan_ffs to rebuild my disklabel but it's
finding some of the volumes and not all of them.

I am running testdisk as I believe it supports UFS and disklabels and might
detect the starting positions of my filesystems if not the data itself.
I have also read the FAQ on data recovery. I know this is an odd question
but it might help someone in future as well.

For background wanting to upgrade 6.7 to 6.8 I was running bsd.rd with the
intention of resizing /usr because it became full. On running disklabel sd0
I found my disk was not available and I know from past experience that the
installer picks up my SATA HDD but I can't access it until that happens.

I ran the install program intending to stop after disk detection and when
it got to the disklabel creation I forgot that pressing q results in
continuation of the install rather than cancelling the process. I know this
is by design in disklabel itself and I should have remembered to press x
instead but maybe I'm not the first to try this approach.

In my case I wanted to see the disklabel allocation for comparison.

I suppose I at least didn't run "rm -rf *"...

Regards
Ed Gray