TRIM on SSD
A production obsd is serving 50GB worth of NFS shares and hourly backups on two ssds since August, and is still going strong at 550MBps over measured 550--950Mbps LAN links. The same boots and runs the OS from a pSLC SD with Phison controller. The ssds have a 5year warrantee, and we are doing our best to stay within specs. The only concern is the lack of TRIM on the SD and the NFS ssd. With TRIM, the os keeps writing on free space instead of deleting and overwriting, for faster writing and uniform wearing of disk. Can we safely enable TRIM on 6.2 now? Sent from ProtonMail Mobile
Re: GPD Pocket (world's smallest higher-specs 7" laptop) dmesg
On Tue, Dec 05, 2017 at 01:00:48AM -0500, Joseph Mayer wrote: > (Sigh, I see Proton Mail made a weird encoding. Hope I fixed this by setting > "Composer Mode" to "plaintext" in the settings.) > > Hi! > > This laptop http://www.gpd.hk/pocket.asp works fine on OpenBSD 6.1 and 6.2, > save for that the APM doesn't work - suspend doesn't work and the battery > doesn't report right, or even charge, in OpenBSD, will follow up about that > separately. > > 8GB RAM, 4x 2.56Ghz Atom x7-Z8750, 128GB eMMC, USB3, > micro-HDMI,USBC-Displayport, 480 grams. Here is the dmesg for 6.1. > > The biggest limits I see that there's no internal M.2 connector (for > NVME/SATA SSD), and also there's only one USBC (USB3) and one USB3 connector. > > This is with the 2017-06-28 "unlocked" BIOS which gives much more > configurable BIOS options (and some self-bricking options due to manufacturer > incompetence), more about that on Reddit. > > Some OpenBSD people who know much more about hardware than me, said that the > hardwired hardware configuration in this laptop is very good but I can't make > any judgement about that. > > Joseph > > You should try a -current snapshot. I think kettenis@ fixed a few things on these types of machines recently. You still won't be able to suspend though, since this machine lacks S3. (Likely it does suspend via S0ix transitions). And I don't think S4 (hibernate) will work either since I'm pretty sure nobody has written a side-effect free sdmmc(4) I/O routine yet. But some of the other devices may be implemented now, in -current. -ml > OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > RTC BIOS diagnostic error 3f> real mem = 8477364224 (8084MB) > avail mem = 8215760896 (7835MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7b8f (51 entries) > bios0: vendor American Megatrends Inc. version "5.11" date 06/28/2017 > bios0: Default string Default string > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT UEFI SSDT HPET > SSDT SSDT SSDT LPIT BCFG PRAM BGRT CSRT WDAT SSDT SSDT SSDT > acpi0: wakeup devices > 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) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1600.26 MHz > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu0: 1MB 64b/line 16-way L2 cache > cpu0: TSC frequency 1600257000 Hz > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 79MHz > cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu1: 1MB 64b/line 16-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu2: 1MB 64b/line 16-way L2 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu3: 1MB 64b/line 16-way L2 cache > cpu3: smt 0, core 3, package 0 > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (RP01) > acpiprt2 at acpi0: bus -1 (RP02) > acpiprt3 at acpi0: bus -1 (RP03) > acpiprt4 at acpi0: bus -1 (RP04) > acpicpu0 at acpi0 > C2: state 6: substate 8 >= num 3 > C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS >
Re: Chip cheaper than chips
50% on pSLC On Mon, Dec 4, 2017 at 12:41, Kevin Chadwickwrote: > On Mon, 04 Dec 2017 06:22:17 -0500 > > > > > We like booting from the SD, but > they have none. > > > > How do you manage flash wear? Set up mfs all over the > place? I much > > prefer and need SATA anyway. > > > This might have been an > issue 20 years ago. > It is not any more. > Please stop spreading FUD. I > assume SD means microSD or something other than SSD. If not I apologise. The > latest atom boards come with 16-64 GB emmc onboard. Apparently emmc may? > perform wear levelling, SD would not unless you pay a fortune for a special > SD card. There seems to be a lot of misinformation in this area which is > quite dangerous considering what some of these devices may be used for. > http://eu.mouser.com/new/Swissbit/swissbit-industrial-SD-memory/ There are > special embedded filesystems (often pay for) that do wear leveling for > standard SD, not sure if they reserve 20% of the space. I am fairly sure even > emmc does not reserve 20% like sandforce/SSD does and so a full filesytem > could fail quickly. Perhaps an unused partition could solve that??
Re: Chip cheaper than chips
Article on how to disable the management engine, if you have it and are afraid of it. http://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 Sent from ProtonMail Mobile On Sun, Dec 3, 2017 at 19:52, Brian McCaffertywrote: > On 12/03/17 03:23, Rupert Gallagher wrote: > The bug on Atom C2000 was solved > in the new C3000 series. It was a minor bug anyway. > > I have no evidence > that the management engine is part of the new chip. It is an expensive > extension that Intel would not include for free. Besides, if available, I > think I would use it! > > Sent from ProtonMail Mobile > > On Sun, Dec 3, 2017 > at 03:47, wrote: > >> https://danluu.com/cpu-bugs/ It's included in this > notice: > https://www.intel.com/content/www/us/en/support/articles/25619/software.html > And shown on the diagram in this product brief: > https://www.intel.com/content/www/us/en/design/products-and-solutions/processors-and-chipsets/denverton/ns/atom-processor-c3000-series.html > @openmailbox.org>
Re: Chip cheaper than chips
industrial SDHC with pSLC https://swissbit.com/products/nand-flash-products/cards/sd-memory-cards/ On Mon, Dec 4, 2017 at 11:05, Kevin Chadwickwrote: > On Sat, 02 Dec 2017 19:03:05 -0500 > We like booting from the SD, but they > have none. How do you manage flash wear? Set up mfs all over the place? I > much prefer and need SATA anyway.
Re: Chip cheaper than chips
Better yet, get rid of such insane rubbish in the first place. Why would you want a remote admin tool built into the CPU out of all things? On Mon, 4 Dec 2017 13:46:02 + Kevin Chadwickwrote: > Dangerous Bugs aren't new such as with core2duo but this is looking > insane. The Apollo Lake chips are really impressive, just a shame they > are intrinsically covered in #*&%. Hopefully public pressure might > cause Intel to release firmware with a proper safe mode switch.
GPD Pocket (world's smallest higher-specs 7" laptop) dmesg
(Sigh, I see Proton Mail made a weird encoding. Hope I fixed this by setting "Composer Mode" to "plaintext" in the settings.) Hi! This laptop http://www.gpd.hk/pocket.asp works fine on OpenBSD 6.1 and 6.2, save for that the APM doesn't work - suspend doesn't work and the battery doesn't report right, or even charge, in OpenBSD, will follow up about that separately. 8GB RAM, 4x 2.56Ghz Atom x7-Z8750, 128GB eMMC, USB3, micro-HDMI,USBC-Displayport, 480 grams. Here is the dmesg for 6.1. The biggest limits I see that there's no internal M.2 connector (for NVME/SATA SSD), and also there's only one USBC (USB3) and one USB3 connector. This is with the 2017-06-28 "unlocked" BIOS which gives much more configurable BIOS options (and some self-bricking options due to manufacturer incompetence), more about that on Reddit. Some OpenBSD people who know much more about hardware than me, said that the hardwired hardware configuration in this laptop is very good but I can't make any judgement about that. Joseph OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 3freal mem = 8477364224 (8084MB) avail mem = 8215760896 (7835MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7b8f (51 entries) bios0: vendor American Megatrends Inc. version "5.11" date 06/28/2017 bios0: Default string Default string acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT UEFI SSDT HPET SSDT SSDT SSDT LPIT BCFG PRAM BGRT CSRT WDAT SSDT SSDT SSDT acpi0: wakeup devices 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) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1600.26 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: TSC frequency 1600257000 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 79MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpicpu0 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu1 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu2 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu3 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: ID3C, resource for ISP3 acpipwrres1 at acpi0: WWPR, resource for HS03, MDM1 acpipwrres2 at acpi0: WWPR, resource for HS13, MDM1 acpipwrres3 at acpi0: WWPR, resource for SSC1, MDM3 acpipwrres4 at acpi0: WWPR, resource for SSCW, MDM3 acpipwrres5 at acpi0: WWPR, resource for HSC1, MDM2 acpipwrres6 at acpi0: WWPR, resource for
GPD Pocket (world's smallest higher-specs 7" laptop) dmesg
Hi! This laptop http://www.gpd.hk/pocket.asp works fine on OpenBSD 6.1 and 6.2, save for that the APM doesn't work - suspend doesn't work and the battery doesn't report right, or even charge, in OpenBSD, will follow up about that separately. 8GB RAM, 4x 2.56Ghz Atom x7-Z8750, 128GB eMMC, USB3, micro-HDMI,USBC-Displayport, 480 grams. Here is the dmesg for 6.1. The biggest limits I see that there's no internal M.2 connector (for NVME/SATA SSD), and also there's only one USBC (USB3) and one USB3 connector. This is with the 2017-06-28 "unlocked" BIOS which gives much more configurable BIOS options (and some self-bricking options due to manufacturer incompetence), more about that on Reddit. Some OpenBSD people who know much more about hardware than me, said that the hardwired hardware configuration in this laptop is very good but I can't make any judgement about that. Joseph OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 3freal mem = 8477364224 (8084MB) avail mem = 8215760896 (7835MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7b8f (51 entries) bios0: vendor American Megatrends Inc. version "5.11" date 06/28/2017 bios0: Default string Default string acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT UEFI SSDT HPET SSDT SSDT SSDT LPIT BCFG PRAM BGRT CSRT WDAT SSDT SSDT SSDT acpi0: wakeup devices 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) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1600.26 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: TSC frequency 1600257000 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 79MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1599.96 MHz 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpicpu0 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu1 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu2 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu3 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: ID3C, resource for ISP3 acpipwrres1 at acpi0: WWPR, resource for HS03, MDM1 acpipwrres2 at acpi0: WWPR, resource for HS13, MDM1 acpipwrres3 at acpi0: WWPR, resource for SSC1, MDM3 acpipwrres4 at acpi0: WWPR, resource for SSCW, MDM3 acpipwrres5 at acpi0: WWPR, resource for HSC1, MDM2 acpipwrres6 at acpi0: WWPR, resource for HSC3, MDM4 acpipwrres7 at acpi0: CLK3, resource for RTK1, RTKA acpipwrres8 at acpi0: CLK4 acpipwrres9 at acpi0: CLK2, resource for
Re: Relinking to create unique kernel... failed!
If you self-modify /bsd, the hash will disagree. That deactivates kernel relinking. That is used by developers. re-create the hash > Predrag Punosevac wrote: > > > > # uname -a > > OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64 > > > > # syspatch > > Get/Verify syspatch62-002_fktrace... 100% |*| 785 KB00:01 > > > > Installing patch 002_fktrace > > Relinking to create unique kernel... failed! > > > > > > Any hints where should I look for the reason relinking is failing? > > > > Predrag > > > > I am onto something > > # pwd > /usr/share/compile/GENERIC.MP > # more relink.log > sha256: /var/db/kernel.SHA256: no properly formatted checksum lines > found > sha256: /bsd does not exist in /var/db/kernel.SHA256 > > The kernel I am currently using was copied from the other machine when > the desktop was trashed due to pmap_flash_cache problem on Apollo Lake > > https://www.mail-archive.com/misc@openbsd.org/msg157274.html > > Cheers, > Predrag >
Re: Relinking to create unique kernel... failed!
Predrag Punosevac wrote: > > # uname -a > OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64 > > # syspatch > Get/Verify syspatch62-002_fktrace... 100% |*| 785 KB00:01 > > Installing patch 002_fktrace > Relinking to create unique kernel... failed! > > > Any hints where should I look for the reason relinking is failing? > > Predrag > I am onto something # pwd /usr/share/compile/GENERIC.MP # more relink.log sha256: /var/db/kernel.SHA256: no properly formatted checksum lines found sha256: /bsd does not exist in /var/db/kernel.SHA256 The kernel I am currently using was copied from the other machine when the desktop was trashed due to pmap_flash_cache problem on Apollo Lake https://www.mail-archive.com/misc@openbsd.org/msg157274.html Cheers, Predrag
Relinking to create unique kernel... failed!
# uname -a OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64 # syspatch Get/Verify syspatch62-002_fktrace... 100% |*| 785 KB00:01 Installing patch 002_fktrace Relinking to create unique kernel... failed! Any hints where should I look for the reason relinking is failing? Predrag
Re: EdgeRouter Lite VS Alix2D3
On Mon, Dec 4, 2017 at 7:49 AM, Ivo Chutkinwrote: > Hello list, > > When I read OpenBSD could run on EdgeRouter Lite, I give it a try (now with > 6.2 current as of 28.11.2017). > I expected closer performance to Alix, but ERL even do not respond on > console in reasonable times, for example, it takes 10-15 sec to log in. I cannot confirm this, when I: # cu -s 115200 -l cua00 to my ERL3 I can login immediately (less than <1seg after entering password) how do you measure it? > After reboot, it takes about 5 min on "reordering libraries:" vs 30 sec on > Alix. Well, it depends on your storage write speed, I'm using a memory with like 8MBps (write) and I think thats your bottleneck, maybe you could try: library_aslr=NO regards > > Is it what I should expect from ERL or I am doing something wrong here? > > Thanks for your input, > Ivo > >
Re: Chip cheaper than chips
Dear Rupert, It is well-documented that the ME hardware is built in to all Intel hardware since 2006. This may not include the "enterprise" AMT offering (hence lack of "vPro" branding), which is just a module that runs on the ME hardware. To clarify: the "vPro" branding and the Intel ME hardware (and base firmware that runs on it) are not tied together. This page gathers some information: https://github.com/corna/me_cleaner/wiki/How-does-it-work%3F Just going by the Intel page on the recent horror-show vulnerability, we see that Intel Atom C3xxx processors are indeed affected: https://security-center.intel.com/advisory.aspx?intelid=intel-sa-00086=en-fr You should make up your own mind (I think the new Intel hardware is pretty neat in many respects, actually). Maybe you should consider running the (above) me_cleaner tool, as that is thought to remove much of the network stack. All the best, Duncan Rupert Gallagher: > Do you have any reference on Intel M.E. being present on Atom C3308? > > Sent from ProtonMail Mobile >
Re: OpenBSD NFC support
Thanks Stefan, Paul. NFC is at the moment a mostly idle fancy for me, so I'm unfortunately not prepared to commit to developing it yet.
Re: Chip cheaper than chips
On Mon, Dec 04, 2017 at 11:41:56AM +, Kevin Chadwick wrote: > On Mon, 04 Dec 2017 06:22:17 -0500 > > > > > > > > > We like booting from the SD, but they have none. > > > > > > How do you manage flash wear? Set up mfs all over the place? I much > > > prefer and need SATA anyway. > > > > > This might have been an issue 20 years ago. > > It is not any more. > > Please stop spreading FUD. > > I assume SD means microSD or something other than SSD. If not I > apologise. > > The latest atom boards come with 16-64 GB emmc onboard. > Apparently emmc may? perform wear levelling, SD would not unless you > pay a fortune for a special SD card. There seems to be a lot of > misinformation in this area which is quite dangerous considering what > some of these devices may be used for. > > http://eu.mouser.com/new/Swissbit/swissbit-industrial-SD-memory/ > > There are special embedded filesystems (often pay for) that do wear > leveling for standard SD, not sure if they reserve 20% of the space. In my experience, even the cheap microsds from big brands support some type of wear leveling. The "industrial" labels in the microsds are only related to the temperature tolerance. Almost every BSD/Linux filesystem will kill your microsd pretty quickly, even in controllers/cards with support for ERASE. The exception is F2FS which allows to reserve a big part of your card as overprovision. I always prefer any type of external card instead of a emmc, because in the case of you break the card, you can simply change it. You can't change the emmc without soldering a new one in the board. > > I am fairly sure even emmc does not reserve 20% like sandforce/SSD > does and so a full filesytem could fail quickly. Perhaps an unused > partition could solve that?? > Modern SSDs don't reserve the 20%. The overprovisioning is very small. -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: pcengines apu boards
> From: Marko Cupac > Sent: Monday, December 4, 2017 3:54 AM > > I have just ordered one APU3b4, as I wanted to test mobile provider as > a backup link. I see it probably won't be any good as OpenBSD router > (yet), but at least I'll be able to test and give feedback. Assuming you're planning to use an internal Mini PCI card, unless you have more luck than me, it's not going to work :(. I'm hoping I will be able to fix the EHCI driver to be more happy with the AMD USB chipset, but this point I'm still fumbling with it :).
Re: PATCH: cwm move window to {top,bottom}{left,right} corners
Okan Demirmenwrote: > A rough cut (no manpage bits yet) would be something like the below; it > allows one to "snap" to any edge or corner. Tested and approved, thanks. See a proposal for cwmrc.5 below. I don't have idea for default keybindings so I didn't touch cwm.1 > Incidentally, I dislike we used up/down/left/right from the beginning, > not sure of the trouble changing to all to cardinal directions or not... Well, it depends on how much you dislike it … It would break everyone's ~/.cwmrc all of a sudden. Index: cwmrc.5 === RCS file: /cvs/xenocara/app/cwm/cwmrc.5,v retrieving revision 1.68 diff -u -p -r1.68 cwmrc.5 --- cwmrc.5 6 Jul 2017 17:09:17 - 1.68 +++ cwmrc.5 4 Dec 2017 20:08:50 - @@ -334,6 +334,8 @@ Other windows in its group share remaini Move current window. .It window-resize Resize current window. +.It window-snap +Snap current window to edge or corner of the screen .It window-move-up Move window .Ar moveamount @@ -398,6 +400,22 @@ pixels right. Resize window 10 times .Ar moveamount pixels left. +.It window-snap-up +Snap window to top edge +.It window-snap-down +Snap window to bottom edge +.It window-snap-right +Snap window to right edge +.It window-snap-left +Snap window to left edge +.It window-snap-up-right +Snap window to top-right corner +.It window-snap-up-left +Snap window to top-left corner +.It window-snap-down-right +Snap window to bottom-right corner +.It window-snap-down-left +Snap window to bottom-left corner .It pointer-move-up Move pointer .Ar moveamount
Re: Having a problem with sshlockout
Thank You! It worked. create doas.conf: root@openbsd-gw:~ # echo 'permit nopass _syslogd as root cmd /usr/local/sbin/sshlockout' > /etc/doas.conf modify syslog.conf: root@openbsd-gw:~ # cat /etc/syslog.conf | grep sshlockout auth.info;authpriv.info |exec /usr/bin/doas -n /usr/local/sbin/sshlockout -pf lockout check that sshlockout run as root: root@openbsd-gw:~ # ps -aux | grep sshlockout root 13074 0.0 0.2 304 1192 ?? Sp 8:52PM0:00.01 /usr/local/sbin/sshlockout -pf lockout 04.12.2017, 20:45, "Jeremie Courreges-Anglas": > On Mon, Dec 04 2017, Андрей Поляков wrote: >> Hello >> I have configured sshlockout. But it doesn't work properly. >> >> Here is auth log: >> root@openbsd-gw:~ # cat /var/log/authlog | grep sshlockout >> Dec 4 06:37:54 openbsd-gw sshlockout[27074]: Detected ssh preauth attempt >> for an invalid user, locking out 59.63.166.104 >> Dec 4 07:40:16 openbsd-gw sshlockout[27074]: Detected ssh login attempt for >> an invalid user, locking out 5.188.10.176 >> Dec 4 07:46:34 openbsd-gw sshlockout[27074]: Detected ssh login attempt for >> an invalid user, locking out 185.190.58.108 >> >> But table in pf is empty: >> root@openbsd-gw:~ # pfctl -t lockout -T show > > See the readme that comes with the sshlockout package. > > -- > jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Free OpenBSD Puffy Stickers
> Hi x9 (funny name for Rio), funny is nice. > have you an image of it? > Here in Brazil its tempting :) send name+address and you will see for yourself, its the default one. cheers. x9p
Re: Free OpenBSD Puffy Stickers
On Mon, December 4, 2017 06:58, x9p wrote: > forgot subject. > >> Hi, >> >> I ordered about 40 stickers 10x10 to see if quality is ok with local >> maker. They arrive in a week or 2. >> >> Intention isnt to make money out of it for myself, I can post via mail >> to >> the ones willing to try/see the sticker quality - maybe is crappy, who >> knows... >> >> Just send me your name+address. I will be posting from Rio de Janeiro / >> Brazil, if mail fee gets expensive to me, will ask the ones who want the >> sticker to cover it via BTC or Paypal. >> >> If project agrees, I am fine with putting them in an online store and >> forwarding the income to the project, minus expenses of the maker. >> >> cheers. >> >> x9p Hi x9 (funny name for Rio), have you an image of it? Here in Brazil its tempting :) -- "We will call you Cygnus, the God of balance you shall be."
Re: EdgeRouter Lite VS Alix2D3
On Mon, Dec 04, 2017 at 03:49:19PM +0200, Ivo Chutkin wrote: > Hello list, > > When I read OpenBSD could run on EdgeRouter Lite, I give it a try (now with > 6.2 current as of 28.11.2017). > I expected closer performance to Alix, but ERL even do not respond on > console in reasonable times, for example, it takes 10-15 sec to log in. > After reboot, it takes about 5 min on "reordering libraries:" vs 30 sec on > Alix. > > Is it what I should expect from ERL or I am doing something wrong here? > > Thanks for your input, > Ivo > Did you add 'usb reset' to the bootcmd as described in INSTALL.octeon?
Re: EdgeRouter Lite VS Alix2D3
On 12/4/17 12:12 PM, Daniel Ouellet wrote: > On 12/4/17 8:49 AM, Ivo Chutkin wrote: >> Hello list, >> >> When I read OpenBSD could run on EdgeRouter Lite, I give it a try (now >> with 6.2 current as of 28.11.2017). >> I expected closer performance to Alix, but ERL even do not respond on >> console in reasonable times, for example, it takes 10-15 sec to log in. >> After reboot, it takes about 5 min on "reordering libraries:" vs 30 sec >> on Alix. >> >> Is it what I should expect from ERL or I am doing something wrong here? >> >> Thanks for your input, >> Ivo > > Get better USB Flash Drive! > > Mine is: > > sd0 at scsibus0 targ 1 lun 0:SCSI4 0/direct > removable serial.07815571360927117103 > > When I simply ping the box to see how long the reboot is and include the > full reorder of library... > > Well here it is: > > 64 bytes from 10.0.0.13: icmp_seq=21 ttl=255 time=0.404 ms > 64 bytes from 10.0.0.13: icmp_seq=72 ttl=255 time=274.757 ms > > See 51 lost ping at 1 per/sec, so 51 sec to be out of service to be back > online ready for processing again. > > $ dmesg > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2017 OpenBSD. All rights reserved. > https://www.OpenBSD.org > > OpenBSD 6.2 (GENERIC) #0: Wed Oct 4 04:56:39 UTC 2017 > visa@octeon:/usr/src/sys/arch/octeon/compile/GENERIC > real mem = 536870912 (512MB) > avail mem = 524009472 (499MB) > mainbus0 at root > cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation > cpu0: cache L1-I 32KB 4 way D 8KB 64 way, L2 128KB 8 way > clock0 at mainbus0: int 5 > iobus0 at mainbus0 > simplebus0 at iobus0: "soc" > octciu0 at simplebus0 > cn30xxsmi0 at simplebus0 > com0 at simplebus0: ns16550a, 64 byte fifo > com0: console > dwctwo0 at iobus0 base 0x118006800 irq 56 > usb0 at dwctwo0: USB revision 2.0 > uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev > 2.00/1.00 addr 1 > octrng0 at iobus0 base 0x14000 irq 0 > cn30xxgmx0 at iobus0 base 0x118000800 > cnmac0 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:f8 > atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2 > cnmac1 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:f9 > atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2 > cnmac2 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:fa > atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2 > /dev/ksyms: Symbol table not valid. > umass0 at uhub0 port 1 configuration 1 interface 0 "SanDisk Cruzer Fit" > rev 2.00/1.27 addr 2 > umass0: using SCSI over Bulk-Only > scsibus0 at umass0: 2 targets, initiator 0 > sd0 at scsibus0 targ 1 lun 0: SCSI4 0/direct > removable serial.07815571360927117103 > sd0: 15267MB, 512 bytes/sector, 31266816 sectors > vscsi0 at root > scsibus1 at vscsi0: 256 targets > softraid0 at root > scsibus2 at softraid0: 256 targets > boot device: sd0 > root on sd0a (55072c2137c3a4e7.a) swap on sd0b dump on sd0b > WARNING: No TOD clock, believing file system. > WARNING: CHECK AND RESET THE DATE! > I was wrong for one thing. The kernel reordering happened after the reboot, not before like when you install the OS. My bad sorry about miss leading you here! The reordering time is 2 minutes 16 seconds on mine But this below is still true. I should also have added that in this very small box, the re-order of the kernel is pointless I guess as the kernel the box load is the one form the FAT partition. Look it up: mount_msdos /dev/sd0i /mnt and when you reboot and the kernel is reorder, the one that is replace is the one on /, not the one the box boot on the fat partition. SO, in this case, unless you write a script that actually mount the fat partition, copy the new kernel to it for the next reboot, then you still are NOT using a different kernel every time. So, if you don't do that then may as well disable the kernel re-link part... Just a simple thing missing in my previous observation. So, you may not get what you think your getting
Re: EdgeRouter Lite VS Alix2D3
On 12/4/17 8:49 AM, Ivo Chutkin wrote: > Hello list, > > When I read OpenBSD could run on EdgeRouter Lite, I give it a try (now > with 6.2 current as of 28.11.2017). > I expected closer performance to Alix, but ERL even do not respond on > console in reasonable times, for example, it takes 10-15 sec to log in. > After reboot, it takes about 5 min on "reordering libraries:" vs 30 sec > on Alix. > > Is it what I should expect from ERL or I am doing something wrong here? > > Thanks for your input, > Ivo Get better USB Flash Drive! Mine is: sd0 at scsibus0 targ 1 lun 0:SCSI4 0/direct removable serial.07815571360927117103 When I simply ping the box to see how long the reboot is and include the full reorder of library... Well here it is: 64 bytes from 10.0.0.13: icmp_seq=21 ttl=255 time=0.404 ms 64 bytes from 10.0.0.13: icmp_seq=72 ttl=255 time=274.757 ms See 51 lost ping at 1 per/sec, so 51 sec to be out of service to be back online ready for processing again. $ dmesg Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2017 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.2 (GENERIC) #0: Wed Oct 4 04:56:39 UTC 2017 visa@octeon:/usr/src/sys/arch/octeon/compile/GENERIC real mem = 536870912 (512MB) avail mem = 524009472 (499MB) mainbus0 at root cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu0: cache L1-I 32KB 4 way D 8KB 64 way, L2 128KB 8 way clock0 at mainbus0: int 5 iobus0 at mainbus0 simplebus0 at iobus0: "soc" octciu0 at simplebus0 cn30xxsmi0 at simplebus0 com0 at simplebus0: ns16550a, 64 byte fifo com0: console dwctwo0 at iobus0 base 0x118006800 irq 56 usb0 at dwctwo0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev 2.00/1.00 addr 1 octrng0 at iobus0 base 0x14000 irq 0 cn30xxgmx0 at iobus0 base 0x118000800 cnmac0 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:f8 atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2 cnmac1 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:f9 atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2 cnmac2 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:fa atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2 /dev/ksyms: Symbol table not valid. umass0 at uhub0 port 1 configuration 1 interface 0 "SanDisk Cruzer Fit" rev 2.00/1.27 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI4 0/direct removable serial.07815571360927117103 sd0: 15267MB, 512 bytes/sector, 31266816 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets boot device: sd0 root on sd0a (55072c2137c3a4e7.a) swap on sd0b dump on sd0b WARNING: No TOD clock, believing file system. WARNING: CHECK AND RESET THE DATE!
Re: Integrating "safe" languages into OpenBSD?
> Am 04.12.2017 um 14:45 schrieb Nick Holland: ... > > Oh yeah. > I recently discovered a very major business operations application where > rather than using the OS's FTP and SFTP functions, they wrote their own > in "safe" Java. I don't know why. ... > If the other machine is being serviced? Network broke? receiving > machine unable to recieve? Oh well. Magic doesn't work, the file is > lost, without alerting the "sending" program. > > Error reporting? Well, for a long time, I thought it was non-existent, > but I recently found they just dumped all the java runtime output to a > file. Nothing is actually done with this info in the application, but > if 100+ lines of J-crap is your favorite way to see "server timeout", > this is your tool. ... > Nick. So they wrote a program that was a) shitty and b) memory-safe? Those are two orthogonal dimensions. Also, the anecdotal evidence that safe languages attract bad programmers does not imply that using safe languages is bad: a good programmer won't suddenly commit such atrocities as you mentioned, just because they use a safe language. Finally, your example probably speaks more about business practices than about safe programming languages. If you want to compare Java to a non-memory-safe language, you should compare it to one that is also designed *for* (instead of *by*) programmers, like Cobol.
EdgeRouter Lite VS Alix2D3
Hello list, When I read OpenBSD could run on EdgeRouter Lite, I give it a try (now with 6.2 current as of 28.11.2017). I expected closer performance to Alix, but ERL even do not respond on console in reasonable times, for example, it takes 10-15 sec to log in. After reboot, it takes about 5 min on "reordering libraries:" vs 30 sec on Alix. Is it what I should expect from ERL or I am doing something wrong here? Thanks for your input, Ivo
Re: Having a problem with sshlockout
On Mon, Dec 04 2017, Андрей Поляковwrote: > Hello > I have configured sshlockout. But it doesn't work properly. > > Here is auth log: > root@openbsd-gw:~ # cat /var/log/authlog | grep sshlockout > Dec 4 06:37:54 openbsd-gw sshlockout[27074]: Detected ssh preauth attempt > for an invalid user, locking out 59.63.166.104 > Dec 4 07:40:16 openbsd-gw sshlockout[27074]: Detected ssh login attempt for > an invalid user, locking out 5.188.10.176 > Dec 4 07:46:34 openbsd-gw sshlockout[27074]: Detected ssh login attempt for > an invalid user, locking out 185.190.58.108 > > But table in pf is empty: > root@openbsd-gw:~ # pfctl -t lockout -T show See the readme that comes with the sshlockout package. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Chip cheaper than chips
On Mon, 4 Dec 2017 13:57:41 +0100 > > dealing with Intel ME or AMD Ryzens bloat. Should I wait for > > everything to be ported to RISC and hope it is as stable and secure > > or wait for an ARM CISC chip, which probably won't happen? > > I'll bite: Patches for a RISC-V port would probably be welcome. Of course but I assume that would be similar to an ARM port and quite different from amd64. I any case, way more than I could achieve in a useful time frame. Basically I have to decide if older, hotter, larger and more expensive AMD hardware is a better choice and won't be obsoleted or if mitigations will suffice. Hoping Positive Technologies BlackHat presentations over the next few days will shed more light. It is a £1400 entrance fee so will have to wait for a youtube or future info releases. Dangerous Bugs aren't new such as with core2duo but this is looking insane. The Apollo Lake chips are really impressive, just a shame they are intrinsically covered in #*&%. Hopefully public pressure might cause Intel to release firmware with a proper safe mode switch.
pf dropping fragmented UDP despite of scrub no-df
Hi all I have this at the beginning of pf.conf: match all scrub (reassemble tcp no-df ) match out all scrub (random-id) Behind that FW is a (OpenIndiana) DNS server that fragments those of its UDP replies that are too large for the local MTU (1500). (Log below is from a DNSKEY query, the failure of which results in DNSSEC validation failing.) The server also sets the DF bit on the fragmented packets ... The external IP dns1-external.domain.tld is natted on the firewall to dns1-internal.domain.tld. The fragmented replies reach the internal firewall interface, but never go out again. There is a log entry for both fragments of the reply packets (even though the rule is set to not log), and no further notice. I thought that with the no-df scrub option this should no longer happen ... I must be missing something, but what? I've bumped my head into this too long now, maybe somebody spots what I can't. (FWIW: The same query over IPv6 (no nat - the server is dual-stack) works, but then the requesting client has issues with reassembling the packets :-[) tcpdump on internal interface: 13:23:09.374991 72.13.58.105.44267 > dns1-internal.domain.tld.domain: [udp sum ok] 47368 [1au] DNSKEY? domain.tld. ar: . OPT UDPsize=4096 DO (36) (ttl 46, id 38692, len 64) 13:23:09.376370 dns1-internal.domain.tld.domain > 72.13.58.105.44267: 47368*- q: DNSKEY? domain.tld. 5/0/1 domain.tld. DNSKEY[|domain] (frag 7478:1480@0+) (DF) (ttl 255, len 1500) 13:23:09.376377 dns1-internal.domain.tld > 72.13.58.105: (frag 7478:110@1480) (DF) (ttl 255, len 130) 13:23:14.380440 72.13.58.105.44267 > dns1-internal.domain.tld.domain: [udp sum ok] 47368 [1au] DNSKEY? domain.tld. ar: . OPT UDPsize=4096 DO (36) (ttl 46, id 53971, len 64) ... tcpdump on pflog0 (the matching rule is set to not log): Dec 04 13:23:09.376397 rule def/(fragment) [uid 0, pid 0] pass in on vlan210: [uid 4294967295, pid 10] dns1-internal.domain.tld.domain > 72.13.58.105.44267: 47368*- q: DNSKEY? domain.tld. 5/0/1 domain.tld.[|domain] (frag 7478:1480@0+) (DF) (ttl 255, len 1500) Dec 04 13:23:09.376413 rule def/(fragment) [uid 0, pid 0] pass in on vlan210: [uid 4294967295, pid 10] dns1-internal.domain.tld > 72.13.58.105: (frag 7478:110@1480) (DF) (ttl 255, len 130) Dec 04 13:23:14.381860 rule def/(fragment) [uid 0, pid 0] pass in on vlan210: [uid 4294967295, pid 10] dns1-internal.domain.tld.domain > 72.13.58.105.44267: 47368*- q: DNSKEY? domain.tld. 5/0/1 domain.tld.[|domain] (frag 7491:1480@0+) (DF) (ttl 255, len 1500) ... tcpdump on external interface: 13:23:09.374546 72.13.58.105.44267 > dns1-external.domain.tld.domain: [udp sum ok] 47368 [1au] DNSKEY? domain.tld. ar: . OPT UDPsize=4096 DO (36) (ttl 46, id 38692, len 64) 13:23:14.380013 72.13.58.105.44267 > dns1-external.domain.tld.domain: [udp sum ok] 47368 [1au] DNSKEY? domain.tld. ar: . OPT UDPsize=4096 DO (36) (ttl 46, id 53971, len 64) ... Thx /markus
Re: Integrating "safe" languages into OpenBSD?
On 12/03/17 20:19, bytevolc...@safe-mail.net wrote: > I've always subscribed to the idea that too much safety results in too > may idiots, and the same is true for all these "safe" programming > languages. "Oh I don't have to write any form of bounds-checking, > because the language will do it for me." > > To add further insult to injury, if the language's bounds checking kicks > in first your program may do something worse than just corrupting its > own memory. In my experience, apps written in these "safe" languages > (usually web apps or bloatware) actually have been the most bug-ridden > and bloated. Oh yeah. I recently discovered a very major business operations application where rather than using the OS's FTP and SFTP functions, they wrote their own in "safe" Java. I don't know why. It's used as part of a file transfer system -- you "print" a file to a print queue, and it is magically transported to another machine. If the other machine is being serviced? Network broke? receiving machine unable to recieve? Oh well. Magic doesn't work, the file is lost, without alerting the "sending" program. Error reporting? Well, for a long time, I thought it was non-existent, but I recently found they just dumped all the java runtime output to a file. Nothing is actually done with this info in the application, but if 100+ lines of J-crap is your favorite way to see "server timeout", this is your tool. Idiots who shouldn't be coding, coding. "safe" languages being trusted to be safe when in the hands of idiots. Like you said. The more I see of "safe" languages, the more I love assembly. Most people who call themselves programmers...shouldn't. Nick.
Re: Do not give-up on marketing
On Sun, 3 Dec 2017 12:58:42 +0200 Mihai Popescuwrote: > I use to read lists in marc.info. > It is a little bit off topic, but I dare to ask: what combination are > you using, like email client and misc@ configuration( i.e, daily > digest, individual emails, etc.)? I am using claws-mail, redirecting (by means of server-side sieve filters) emails from each mailing list to a separate folder. I configure sieve filters from roundcube, and for mailing lists I mostly use rule similar to "list id contains -> move message to "INBOX\lists\openbsd\misc". I like to receive individual mails and set mailing lists folders to "thread view" in claws-mail. Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: no sound by "Intel 6321ESB HD Audio"
thanks for reading . fedora on mac pro 2006 can play audio file . any way i follow you . first ### # dmesg OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017 r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/ GENERIC.MP real mem = 4272590848 (4074MB) avail mem = 4136087552 (3944MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe00f0 (67 entries) bios0: vendor Apple Computer, Inc. version "MP11.88Z.005C.B08.0707021221" date 07/02/07 bios0: Apple Computer, Inc. MacPro1,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT ECDT FACP HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices P2P5(S4) P2P3(S4) ARPT(S4) RP04(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) EHCI(S3) AC9M(S4) EC__(S3) NRP4(S4) SRP1(S4) SRP3(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz, 2660.36 MHz 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,NXE,LONG,LAHF,PERF,SENSOR cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 332MHz cpu0: mwait min=64, max=64, C-substates=0.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz, 2660.00 MHz 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,NXE,LONG,LAHF,PERF,SENSOR cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 6 (application processor) cpu2: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz, 2660.00 MHz 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,NXE,LONG,LAHF,PERF,SENSOR cpu2: 4MB 64b/line 16-way L2 cache cpu2: smt 0, core 0, package 3 cpu3 at mainbus0: apid 7 (application processor) cpu3: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz, 2660.00 MHz 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,NXE,LONG,LAHF,PERF,SENSOR cpu3: 4MB 64b/line 16-way L2 cache cpu3: smt 0, core 1, package 3 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xd000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus 2 (P1P2) acpiprt3 at acpi0: bus 5 (P2P5) acpiprt4 at acpi0: bus 3 (P2P3) acpiprt5 at acpi0: bus 15 (RP04) acpiprt6 at acpi0: bus 16 (PCIB) acpiprt7 at acpi0: bus 8 (NRP4) acpiprt8 at acpi0: bus 12 (SRP1) acpiprt9 at acpi0: bus 14 (SRP3) acpicpu0 at acpi0: C1(1000@1 mwait) acpicpu1 at acpi0: C1(1000@1 mwait) acpicpu2 at acpi0: C1(1000@1 mwait) acpicpu3 at acpi0: C1(1000@1 mwait) "PNP0003" at acpi0 not configured "APP0001" at acpi0 not configured "ACPI0001" at acpi0 not configured acpibtn0 at acpi0: PWRB "APP0006" at acpi0 not configured memory map conflict 0xfff9/0x3 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 5000X Host" rev 0x30 ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE x8" rev 0x30 pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci2 at ppb1 bus 2 ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01: msi pci3 at ppb2 bus 3 ppb3 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01: msi pci4 at ppb3 bus 4 ppb4 at pci2 dev 2 function 0 "Intel 6321ESB PCIE" rev 0x01 pci5 at ppb4 bus 5 em0 at pci5 dev 0 function 0 "Intel 80003ES2" rev 0x01: msi, address 00:17:f2:03:bf:3c em1 at pci5 dev 0 function 1 "Intel 80003ES2" rev 0x01: msi, address 00:17:f2:03:bf:3d "Intel 6321ESB IOxAPIC" rev 0x01 at pci1 dev 0 function 1 not configured ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01 pci6 at ppb5 bus 6 pchb1 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0x30 ppb6 at pci0 dev 4 function 0 "Intel 5000 PCIE x16" rev 0x30: msi pci7 at ppb6 bus 8 radeondrm0 at pci7 dev 0 function 0 "ATI Radeon HD 3450" rev 0x00 drm0 at radeondrm0 radeondrm0: msi pchb2 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0x30 pchb3 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0x30 pchb4 at pci0 dev 7 function 0 "Intel 5000 PCIE" rev 0x30 "Intel I/OAT" rev 0x30 at pci0 dev 8 function 0 not configured pchb5 at pci0 dev 16 function 0 "Intel 5000 Error Reporting" rev 0x30 pchb6 at pci0 dev 16 function 1 "Intel 5000 Error Reporting" rev 0x30 pchb7 at pci0 dev 16 function 2
Re: Chip cheaper than chips
2017-12-04 11:05 GMT+01:00 Kevin Chadwick: > dealing with Intel ME or AMD Ryzens bloat. Should I wait for everything > to be ported to RISC and hope it is as stable and secure or wait for an > ARM CISC chip, which probably won't happen? I'll bite: Patches for a RISC-V port would probably be welcome.
Re: Hellos from the Lands of Norway.
Ok, I think I´ve finished up most of the philosopical part, of trying to commercialize Available Source. If you have some thing you want to make money on, on the internet you too ofcourse can be a Webtechy Of Üddüc. Üddüc is "Thé God", a reconstructed concept without the regressions, so one can be as mainstream as possible. You already know the morals of this, and I´ve also written on my youtube banner, "And a little mindfulness of the grandiose paradox, and some charitable activity". These are also needed. Basically original religious principles, that makes this work. https://www.youtube.com/channel/UCR3gmLVjHS5A702wo4bol_Q So indeed, if you are sitting there feeling like not making money on the business greatest money maker, the IT-industry, you may want to evaluate this philosophic angle. And the villain here is the GNU-Zealot. As known throughout the entire World Wide Web. So "No Gnu-Zealots" and "commercial sobriety". Peaceful Salutations Üwe Cærlyn. (reply to me with CC please)
Re: pcengines apu boards
On Sat, 2 Dec 2017 20:08:41 -0800 "Paul B. Henson"wrote: > On Sat, Dec 02, 2017 at 10:40:14PM +1000, Douglas Ray wrote: > > > On the APU3a4 the internal USB headers were broken. > > I had email from pcengines (March 2017) saying this would > > be addressed in the APU3b series., but we went for APU2. > > I have a APU3b series, they fixed the incorrect pinout on the internal > usb headers. The internal ECHI ports work fine under both linux and > freebsd connected to a USB backplate I'm testing with. It's > definitely a disagreement between the AMD EHCI USB chipset and > OpenBSD . I'm going to see if I can port some of the > workarounds and quirks for that chipset from linux/freebsd to the > openbsd driver and see if I have any luck getting it working; drivers > aren't my strong suite but we'll see what happens. In the worst case > I guess I'll use an external miniPCI to USB adapter and connect my > LTE modem to the external xHCI ports, they seem to work fine under > OpenBSD. > > Thanks... > I have a bunch of APU2c4's, they play nice with OpenBSD. Actually my complete fleet (~20) of branch office routers are based on APU2c4's running various OpenBSD versions (I think the oldest is 5.8). I have just ordered one APU3b4, as I wanted to test mobile provider as a backup link. I see it probably won't be any good as OpenBSD router (yet), but at least I'll be able to test and give feedback. Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: Chip cheaper than chips
On Mon, 04 Dec 2017 06:22:17 -0500 > > > > > We like booting from the SD, but they have none. > > > > How do you manage flash wear? Set up mfs all over the place? I much > > prefer and need SATA anyway. > > > This might have been an issue 20 years ago. > It is not any more. > Please stop spreading FUD. I assume SD means microSD or something other than SSD. If not I apologise. The latest atom boards come with 16-64 GB emmc onboard. Apparently emmc may? perform wear levelling, SD would not unless you pay a fortune for a special SD card. There seems to be a lot of misinformation in this area which is quite dangerous considering what some of these devices may be used for. http://eu.mouser.com/new/Swissbit/swissbit-industrial-SD-memory/ There are special embedded filesystems (often pay for) that do wear leveling for standard SD, not sure if they reserve 20% of the space. I am fairly sure even emmc does not reserve 20% like sandforce/SSD does and so a full filesytem could fail quickly. Perhaps an unused partition could solve that??
Re: Some hints to set up a PPTP or L2TP VPN client under OpenBSD
On 2017-12-04, Максимwrote: > Hi, Denis. > At the moment I'd like to connect to a Mikrotik router which > was set up as a VPN server. > From Ubuntu and Windows I'm able to connect > using built in solutions. > If there are some differences in MS Windows VPN Server > which I should take into account when connecting > from OpenBSD client, I'd be glad to know them as well. OpenBSD has built-in support for IPsec client and server (IKEv1: isakmpd, IKEv2: iked). L2TP and PPTP *servers* are also built in (npppd), but not clients. MikroTik do have IKEv1 and IKEv2 support. If it works, IKEv2 is likely to be the best option (I don't have an MT box to test with at the moment). Information about setting up their side: https://wiki.mikrotik.com/wiki/Manual:IP/IPsec#Road_Warrior_setup_Ikev2_RSA_auth If you are forced to use something else, there is some support for L2TP via xl2tpd (in packages), but it's a bit messy. If you need to resort to this, use the version from -current ports, and see the pkg-readme.
Re: renice and network forwarding
On 03/12/17(Sun) 21:13, Tom Smyth wrote: > Hello all, > > just wondering if anyone else has tried using renice to > de-prioritise other processes in an effort to give more cpu > time to packet forwarding in the kernel ? The thread responsible for processing packets being forwarded is 'softnet'. Like almost all others kernel threads is has a higher priority than userland processes. So renice is useless in that case. This thread already uses as much CPU time as possible. What is your problem? What do you want to achieve? > While Im certain that there significant risks to system stability > and other functionality of the system if one were to carpet bomb > the process list pids with renice 20. Perhaps the current defaults > are for general purpose systems ? Perhaps other network > Administrators have tweaked background processes where a system > was a single purpose system such as a Router, Firewall or Bridge. There's no such performance tweak. However note that if you're bridging interfaces you might suffer. That's because nobody did the work to take the bridge(4) out of the KERNEL_LOCK(). So it's a totally different issue than the forwarding path. > Also is the softnet process (as seen by command top -SH) only > interrupt handling of packets ? It's processing all incoming packets. > or does it cover processing (e.g. forwarding if enabled ) (either > bridging or routing depending on network config) All of them but some configurations work better because they don't require to grab the KERNEL_LOCK(). > any advice welcome ... What do you want to achieve? Better performances? With which setup? Cheers, Martin
Re: Chip cheaper than chips
> Kevin, the simpler answer here is, don't buy Intel (nor AMD). > > Hopefully some day we'll have open source chips akin to SiFive > Freedom U500 > ( > https://www.sifive.com/documentation/freedom-soc/freedom-u500-platform-brief/ > . > Thanks but I wouldn't call that simple. Probably more work than dealing with Intel ME or AMD Ryzens bloat. Should I wait for everything to be ported to RISC and hope it is as stable and secure or wait for an ARM CISC chip, which probably won't happen?
Re: Chip cheaper than chips
On Sat, 02 Dec 2017 19:03:05 -0500 > We like booting from the SD, but they have none. How do you manage flash wear? Set up mfs all over the place? I much prefer and need SATA anyway.
Re: ed(1) text editor issue with Spanish accents
Hello Alejandro, ed works on both binary and ASCII text, which are all individual bytes. Since ´ is an UTF-8 character, which comprises of the bytes C2 and B4, ed thinks it should only delete a single byte which results in only C2. Your terminal can't tell the meaning of just C2 which results, in this particular case, in a question mark. The reason the character disappears after the backspace is because the presentation layer gets the instruction to clear the column prior to the current position, so hence it appears deleted after the backspace. Currently there's no UTF-8 support in our ed, and I don't see how this can be done without endangering the binary editing capabilities. martijn@ On 12/04/17 00:43, Alejandro G. Peregrina wrote: > Hello, > > I've noticed something unexpected when entering an accent character > alone (´) and then deleting it in ed(1) in xterm(1). Instead of deleting > it, it creates another character which is seen as an inverted > exclamation (?) in the font 'misc-fixed'. > > How to reproduce: > $ uname -a > OpenBSD foo.my.domain 6.2 GENERIC.MP#1 amd64 > $ locale > LANG= > LC_COLLATE="C" > LC_CTYPE=en_US.UTF-8 > LC_MONETARY="C" > LC_NUMERIC="C" > LC_TIME="C" > LC_MESSAGES="C" > LC_ALL= > $ #Let's append the ´ character in ed(1) > $ ed -p"> " >> a > ´ > > Now let's delete with a backspace, return to create a newline and a dot > to stop appending, and then print: > > $ ed -p"> " >> a > > . >> p > (?) > > (The (?) is a simulation of the font character that misc-fixed shows to > the terminal.) > > Whenever I use more(1) or less(1) to view it, it shows: > > $ more test.txt > > > > > I have to add that I tested this with urxvt and ed(1) prints an  > character, but more(1) and less(1) keep printing . > > When not using X this can't be reproduced. This is reproducible with > xterm(1) and urxvt(1) in cwm(1) and fvwm(1). I've tested this in Linux > and FreeBSD and this behaviour is not reproducible. > > Thank you, > A >
Free OpenBSD Puffy Stickers
forgot subject. > Hi, > > I ordered about 40 stickers 10x10 to see if quality is ok with local > maker. They arrive in a week or 2. > > Intention isnt to make money out of it for myself, I can post via mail to > the ones willing to try/see the sticker quality - maybe is crappy, who > knows... > > Just send me your name+address. I will be posting from Rio de Janeiro / > Brazil, if mail fee gets expensive to me, will ask the ones who want the > sticker to cover it via BTC or Paypal. > > If project agrees, I am fine with putting them in an online store and > forwarding the income to the project, minus expenses of the maker. > > cheers. > > x9p > >
[no subject]
Hi, I ordered about 40 stickers 10x10 to see if quality is ok with local maker. They arrive in a week or 2. Intention isnt to make money out of it for myself, I can post via mail to the ones willing to try/see the sticker quality - maybe is crappy, who knows... Just send me your name+address. I will be posting from Rio de Janeiro / Brazil, if mail fee gets expensive to me, will ask the ones who want the sticker to cover it via BTC or Paypal. If project agrees, I am fine with putting them in an online store and forwarding the income to the project, minus expenses of the maker. cheers. x9p
Re: OpenBSD NFC support
Hi Lari, On Sun, Dec 03, 2017 at 03:48:06PM +0200, Lari Rasku wrote: | I've been thinking about getting a laptop with a Near Field Communication | module, but I'm worried if it'll work on OpenBSD. A search through the | mailing list archives, man pages and packages revealed only the the | qtconnectivity package, whose description holds the following paragraph: | | Qt NFC enables connectivity between NFC enabled devices. | Be warned that Qt NFC on OpenBSD may need some additional | components. | | Which seems to suggest that it's possible, but doesn't mention what those | "additional components" might be. Does anyone have any firm knowledge? I bought an external (USB connected) NFC reader/writer to play around with. I did get the basics to work (could read information from several cards) with libnfc, but the urgency of that particular project dropped so completing porting that dangles somewhere on the lower regions of my list of things to do. In the end, I found a dongle on ebay that attaches as: ugen2 at uhub4 port 2 "SCM Micro SCL3711-NFC" rev 2.00/2.07 addr 3 The seller seems to no longer ship them in single unit volumes, but here's the "bulk" (20-pcs) option though: https://www.ebay.nl/itm/Identiv-SCL3711-USB-NFC-Contactless-reader-Aimail-Taiwan/252493738824?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649 Currently, I don't even have it connected :-/ However, if you're interested in working on this, let me know off-list and I can dig up what little notes I still have. Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/