Re: htop install fails on -current
Louis Brauer(lo...@emacs.ch) on 2024.01.28 20:54:17 +: > I've just installed 7.4-current on an ARM64 machine and tried to pkg_add the > "htop" package. It fails and this is the output of pkg_add: > > # pkg_add htop > quirks-7.0:updatedb-0p0: ok > quirks-7.0 signed on 2024-01-21T11:57:22Z > quirks-7.0: ok > htop-3.2.2:bzip2-1.0.8p0: ok > htop-3.2.2:pcre2-10.37p1: ok > htop-3.2.2:libiconv-1.17: ok > Can't install gettext-runtime-0.22.4 because of libraries > |library c++.9.0 not found > | /usr/lib/libc++.so.10.0 (system): bad major > |library c++abi.6.0 not found > | /usr/lib/libc++abi.so.7.0 (system): bad major > Direct dependencies for gettext-runtime-0.22.4 resolve to libiconv-1.17 > Full dependency tree is libiconv-1.17 > htop-3.2.2:libffi-3.4.4p0: ok > htop-3.2.2:sqlite3-3.44.2: ok > htop-3.2.2:xz-5.4.5: ok > Can't install python-3.10.13p0: can't resolve gettext-runtime-0.22.4 > Can't install glib2-2.78.3: can't resolve > python-3.10.13p0,gettext-runtime-0.22.4 > Can't install desktop-file-utils-0.27: can't resolve glib2-2.78.3 > Can't install htop-3.2.2: can't resolve desktop-file-utils-0.27 > Couldn't install desktop-file-utils-0.27 gettext-runtime-0.22.4 glib2-2.78.3 > htop-3.2.2 python-3.10.13p0 > > It works fine on -stable. Since I do not have much experience with > -current or the package system, I'm not sure if that is a bug in the > -current tree or if there is anything I missed? libc++ and libc++abi were updated on the 26th. The changes were incompatible with the previous version so they got newer version numbers. This can happen on -current. On OpenBSD, there is no guarantee for binary backward compatibility of libaries, so when the version changes, binaries need to be recompiled. Now, packages are build independent from the base. This means that there is a time lag between such a library bump and the packages catching up. Wait a few hours or a day and try pkg_add again. The same can happen when you upgrade to a newer -current. If you run current, you have to live with this. /B. > > Any advice would be much appreciated. > > - Louis > --
htop install fails on -current
I've just installed 7.4-current on an ARM64 machine and tried to pkg_add the "htop" package. It fails and this is the output of pkg_add: # pkg_add htop quirks-7.0:updatedb-0p0: ok quirks-7.0 signed on 2024-01-21T11:57:22Z quirks-7.0: ok htop-3.2.2:bzip2-1.0.8p0: ok htop-3.2.2:pcre2-10.37p1: ok htop-3.2.2:libiconv-1.17: ok Can't install gettext-runtime-0.22.4 because of libraries |library c++.9.0 not found | /usr/lib/libc++.so.10.0 (system): bad major |library c++abi.6.0 not found | /usr/lib/libc++abi.so.7.0 (system): bad major Direct dependencies for gettext-runtime-0.22.4 resolve to libiconv-1.17 Full dependency tree is libiconv-1.17 htop-3.2.2:libffi-3.4.4p0: ok htop-3.2.2:sqlite3-3.44.2: ok htop-3.2.2:xz-5.4.5: ok Can't install python-3.10.13p0: can't resolve gettext-runtime-0.22.4 Can't install glib2-2.78.3: can't resolve python-3.10.13p0,gettext-runtime-0.22.4 Can't install desktop-file-utils-0.27: can't resolve glib2-2.78.3 Can't install htop-3.2.2: can't resolve desktop-file-utils-0.27 Couldn't install desktop-file-utils-0.27 gettext-runtime-0.22.4 glib2-2.78.3 htop-3.2.2 python-3.10.13p0 It works fine on -stable. Since I do not have much experience with -current or the package system, I'm not sure if that is a bug in the -current tree or if there is anything I missed? Any advice would be much appreciated. - Louis
Dell Latitude 7490 with Samsung 980 m.2 drive, doesnt wake after screensaver
I had problem getting the disk to work during installation. ended up creating partitions on a windows computer to make installation work. OpenBSD 7.4 (GENERIC.MP) #1397: Tue Oct 10 09:02:37 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17032695808 (16243MB) avail mem = 16496754688 (15732MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.1 @ 0xe7430 (109 entries) bios0: vendor Dell Inc. version "1.31.1" date 02/02/2023 bios0: Dell Inc. Latitude 7490 efi0 at bios0: UEFI 2.6 efi0: American Megatrends rev 0x5000b acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SSDT HPET SSDT UEFI SSDT LPIT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT SSDT MSDM SLIC NHLT ASF! DMAR BGRT acpi0: wakeup devices RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(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-8350U CPU @ 1.70GHz, 1795.82 MHz, 06-8e-0a, patch 00f4 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1795.82 MHz, 06-8e-0a, patch 00f4 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1795.82 MHz, 06-8e-0a, patch 00f4 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1795.82 MHz, 06-8e-0a, patch 00f4 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1795.82 MHz, 06-8e-0a, patch 00f4 cpu4:
Re: Clock stops working on OpenBSD qemu/kvm guest
On Friday, January 26th, 2024 at 13:40, Dave Voutila wrote: > > Lévai, Dániel l...@ecentrum.hu writes: > > > Hi all! > > > > I have this OpenBSD 7.4 qemu/kvm VM managed by libvirt on an Ubuntu 22.04 > > host. [...] > > Anyway, the symptoms are funny, it always involves the clock stopping/not > > working after some period of time. > > What is your Linux kernel version? It's at 6.5.0-15-generic atm, like the upgrade log showed, that was the latest update to date. > > This has been set on the guest, though (defaults): > > kern.timecounter.tick=1 > > kern.timecounter.timestepwarnings=0 > > kern.timecounter.hardware=pvclock0 > > kern.timecounter.choice=i8254(0) pvclock0(1500) acpitimer0(1000) > > > So pvclock should be relying on KVM to properly deal with TSC > paravirtualzation. Do you see this issue with Linux guests using > kvmclock? (Or do your Linux guests decide on a different clocksource?) Nowhere else, and even this has been working fine until I think the beginning of this January. There's a bunch of OSs running there, Fedora, Ubuntu, Arch, all using 'kvm-clock' as their clock source, they work fine. No problem with FreeBSD (using kvmclock0) and Win11 (no clue what it's using) either.
