Color emojis
I have a little issue with my system (OpenBSD 6.9 amd64 with XFCE) and that is that emojis aren't showing. I read fonts-conf(5) and created with some help one for my own configuration but I haven't had luck so far. I installed Noto Emoji font and the powerline ones from packages but it didn't cause any effect. I need to be able to see emojis across the system, some people tend to think that I wanna see them only on Firefox and they suggest stuff to do in a specific system but I need to i.e. see color emojis in the terminal. What else do I need to check or is there some kind of incompatibility? Thanks -- ~ffuentes sysadmin texto-plano.xyz
Re: umb0 broke in 6.9
On 6/14/2021 4:54 PM, Stuart Henderson wrote: find when the problem started .. with 6.9 userland you can probably get away with just booting the relevant older kernel for a test for probably most/maybe all of the way back to 6.8. So I booted the 6.8 kernel, and everything seemed to be mostly working, but the umb interface still wasn't initialized properly :(. I was thinking I'd have to do a fresh install of 6.8 and start the test from there, but then I considered that one thing I still hadn't done was a cold power cycle. I have a remote console on the serial port of the system, but it doesn't have built-in remote power control and it's not hooked up to a remote control power switch, so it's not that convenient to deal with power. I coordinated a cold power cycle and booted up the 6.8 kernel, and the umb interface worked :). I then booted the 6.9 kernel, and it also worked? By default the kernel allocates the device to the umsm driver (it would be nice if the umb driver took priority instead), so the first 6.9 boot after the install used that driver until I disabled it and rebooted. I thought perhaps the 6.9 version of that driver put the card in a bad state, so I tried booting the 6.9 kernel with it enabled, and then booting it again with it disabled. But the umb interface was still working after that test. So it seems that somehow the upgrade process put the hardware in a bad state where it would not initialize, and a cold power cycle seems to have sorted that out. I wasn't able to reproduce the issue doing some testing, so I guess I will write it off as "that's odd" and just be happy it seems to be working reliably now :). Thanks much for your assistance looking at it…
Re: Machine age and OpenBSD - Thinkpad R51e
Hi I have a R51e and OpenBSD i386 works great on it. I upgraded memory its from 1 to 2gig, but 1gig is plenty. John On Tue, Jun 15, 2021 at 08:14:14PM -0400, Thomas Vetere wrote: Hello everyone, I was looking to get a laptop to run OpenBSD. The one I am looking at in particular is the Thinkpad R51e (2005). I like this particular model because it does not come with any extra hardware that OpenBSD does not support in the first place (bluetooth, camera, etc.) My main concern is the longevity that this model would have going forward. I already have a '94 Thinkpad that cannot run the latest OpenBSD well because hardware support was gradually dropped during code cleanups, etc (i.e. newer versions of X11 removed support for my ancient graphics chip because it just wasn't worth the time to maintain the code). Does anyone know, given the age of that model, how many years I might get out of it with OpenBSD and its packaged software before hardware support starts to drop? What is a good rule of thumb for selecting a machine to run OpenBSD with respect to its age? Thank you for your help!
Re: Machine age and OpenBSD - Thinkpad R51e
On 2021-06-16, Thomas Vetere wrote: > Hello everyone, > > I was looking to get a laptop to run OpenBSD. The one I am looking at in > particular is the Thinkpad R51e (2005). I like this particular model > because it does not come with any extra hardware that OpenBSD does not > support in the first place (bluetooth, camera, etc.) My main concern is the > longevity that this model would have going forward. I already have a '94 > Thinkpad that cannot run the latest OpenBSD well because hardware support > was gradually dropped during code cleanups, etc (i.e. newer versions of X11 > removed support for my ancient graphics chip because it just wasn't worth > the time to maintain the code). Does anyone know, given the age of that > model, how many years I might get out of it with OpenBSD and its packaged > software before hardware support starts to drop? What is a good rule of > thumb for selecting a machine to run OpenBSD with respect to its age? > > Thank you for your help! > If you want to run some common packages like chromium or firefox on a current version of OpenBSD: 0 years. (To be honest i386 hasn't really been a great choice for running packages for probably 5+ years now). You *really* want hardware with a CPU that can use an amd64 kernel. Check the cpu model and look it up on intel's spec pages, check for 64-bit support. On some laptop ranges there are both 32-bit-only and 64-bit-capable CPUs in the same range, but none of the CPUs used on R51e are 64-bit. I wouldn't suggest anything older than the X220/T420/T520 generation, and those would be a bit of a push now. By this point they're old enough you might need to do some hardware maintenance; maybe replace things like fans, heatsink compound, etc. By the way, the cameras do usually work, though if you particularly want to avoid a camera there are some models that don't include them. Probably getting hard to find now though, I think "no camera" was usually a configure-to-order option rather than a standard spec. Although OpenBSD doesn't support bluetooth, it doesn't get in the way of anything. On X220 and maybe others if you particularly don't want to have the hardware, you could just remove the daughtercard that runs it (some people do this anyway to gain an additional USB interface); maybe swap the wifi interface too, as some of them are combined wifi+BT.
panic when xenodm is enabled (uvm_fault, pool_do_get), -current #75
Hi I just installed -current #75 and I can't enable xenodm because the system panics 90% of the time. I'm including below basic info and pictures of messages - any pointing to the right direction would be welcomed. Images of error messages: https://1drv.ms/u/s!Al64DwRfhnFCas821xILYsNzEuk?e=XKUC3H dmesg; usbdevs; pcidump OpenBSD 6.9-current (GENERIC.MP) #75: Mon Jun 14 08:51:05 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34111942656 (32531MB) avail mem = 33062649856 (31531MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x429e1000 (54 entries) bios0: vendor INSYDE Corp. version "1.07.01LS1" date 09/07/2020 bios0: Notebook NV4XMZ acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI SSDT SSDT SSDT SSDT SSDT TPM2 SSDT NHLT SSDT LPIT WSMT SSDT SSDT DBGP DBG2 HPET APIC MCFG SSDT DMAR SSDT FPDT PTDT BGRT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEGP(S4) PEGP(S4) XHCI(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S3) RP02(S4) PXSX(S3) RP03(S4) PXSX(S3) RP04(S4) PXSX(S3) RP05(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 29492.48 MHz, 06-8c-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 256KB 64b/line disabled 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 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.1.2.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 4190.36 MHz, 06-8c-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 256KB 64b/line disabled L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 3791.27 MHz, 06-8c-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 256KB 64b/line disabled L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 3791.27 MHz, 06-8c-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 256KB 64b/line disabled L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 3791.26 MHz, 06-8c-01 cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX5
