Re: X/DRM freeze on 7.2
Hi, https://docs.mesa3d.org/envvars.html#radeonsi-driver-environment-variables For me freezes happen only when hardware acceleration is enabled so this might be a good place to start. -- Patrick Harper paia...@fastmail.com On Fri, 21 Oct 2022, at 19:56, Mickael Torres wrote: > Hello, > > Since upgrading to 7.2, I have X/DRM freezes on one computer (dmesg below). > > When it happens, the screen is completely frozen, but I can still ssh > to the machine. > It only happened when starting firefox or VLC, for now. Once they are > started I didn't have any > problem. > When the machine is in that state, the X and firefox processes are in > the DRM wait state: > 87821 _x11 -200 97M 110M idle DRM 0:01 0.00% Xorg > 76467 mike -200 12M 28M idle DRM 0:00 0.00% > firefox > 51234 mike -200 5972K 49M idle DRM 0:00 0.00% > firefox > Nothing in dmesg or Xorg.0.log. > > As far as I can remember, it never happened with 7.1. > > Is there anything I can do to further debug this? > > Best, > Mickael > > OpenBSD 7.2 (GENERIC.MP) #758: Tue Sep 27 11:57:54 MDT 2022 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 68598935552 (65421MB) > avail mem = 66502520832 (63421MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xbda23000 (49 entries) > bios0: vendor American Megatrends International, LLC. version "F37d" > date 07/27/2022 > bios0: Gigabyte Technology Co., Ltd. X570 AORUS ELITE > acpi0 at bios0: ACPI 6.2 > acpi0: sleep states S0 S4 S5 > acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT FIDT MCFG HPET SSDT IVRS > FPDT VFCT BGRT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT > acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) > GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) > GPPE(S4) GPPF(S4) GP10(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimcfg0 at acpi0 > acpimcfg0: addr 0xf000, bus 0-127 > acpihpet0 at acpi0: 14318180 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.08 MHz, 19-21-00 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 100MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 2 (application processor) > cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00
Re: radeondrm / radeon 8570
In Chrome, try logging on to chrome://flags and enable #ignore-gpu-blocklist. Make sure hardware acceleration is enabled in the settings as well. -- Patrick Harper paia...@fastmail.com On Fri, 28 Jan 2022, at 23:46, Chris Cappuccio wrote: > is anyone trying to use an older radeondrm card with current? > > i just moved my SSDs into an amd64 box with a radeon 8570 card and > everything seems to work, glxgears works fast... > > ...until i start firefox or chrome, and pull up, say, youtube's > video-image-laden front page, then the browser window mostly freezes up > and responds extremely slowly, also after this point glxgears barely > runs at all, it claims a 4 frames per second but is more like 4 seconds > per frame, even after firefox is stopped > > OpenBSD 7.0-current (GENERIC.MP) #287: Tue Jan 25 01:38:55 MST 2022 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 137342574592 (130980MB) > avail mem = 133162971136 (126994MB) > random: boothowto does not indicate good seed > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcbacc018 (128 entries) > bios0: vendor Hewlett-Packard version "J63 v03.50" date 08/14/2013 > bios0: Hewlett-Packard HP Z820 Workstation > acpi0 at bios0: ACPI 5.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT MCFG SRAT SLIT HPET SSDT SLIC SSDT > SSDT ASF! TCPA IFEU > acpi0: wakeup devices PS2K(S3) UAR1(S3) BR20(S4) EUSB(S4) USBE(S4) > GBE_(S4) NP1B(S4) NPE2(S4) NPE3(S4 > ) PEX1(S4) PEX2(S4) PEX4(S4) NPE2(S4) NPE3(S4) PWRB(S3) > 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) Xeon(R) CPU E5-2667 0 @ 2.90GHz, 2893.42 MHz, 06-2d-07 > 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,CX16,xTPR,PDCM,PCID,DCA > ,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,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.1.2, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz, 2893.04 MHz, 06-2d-07 > 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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz, 2893.04 MHz, 06-2d-07 > 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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz, 2893.04 MHz, 06-2d-07 > 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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 0, core 3, package 0 > cpu4 at mainbus0: apid 8 (application processor) > cpu4: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz, 2893.04 MHz, 06-2d-07 > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu4: 256KB 64b/line 8-way L2 cache > cpu4: smt 0, core 4, package 0 > cpu5 at mainbus0: apid 10 (application processor) > cpu5: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz, 2893.04 MHz, 06-2d-07 > cpu5: > 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,C
Re: can't get fonts to show up
I would read the fonts(7) man page first. Specifically the 'Installing fonts in Xft' section. -- Patrick Harper paia...@fastmail.com On Tue, 30 Nov 2021, at 23:38, Carson Chittom wrote: > I have purchased some fonts that I like, and I want to use them > throughout my OpenBSD 7.0 system. I have both TTF and OTF versions of > the fonts. > > I created a new port in /usr/ports/mystuff/myfonts and copied over the > Makefile from fonts/ibm-plex to use as a model, edited it *only* > (AFAICR) to adjust for font names and paths, did the minimum possible to > actually create a package, and installed it. That worked fine. > > I may have run mkfontscale and mkfontdir manually in each font's > directory as well; I don't remember. In any case, the fonts are > available to GTK and Qt. > > As part of ~/.xsession, I also have: > > if [ -d /usr/local/share/fonts ]; then > for i in /usr/local/share/fonts/*; do > xset fp+ $i > done > xset fp rehash > fi > > But the fonts still do not show up in xfontsel (unlike, for example, if > I install fonts/ibm-plex), and I don't seem to be able to use them in > Fvwm either, even if I copy a font description directly from > /usr/local/share/fonts/myfonts/fonts.dir > > So, I'm guessing either my fonts are missing something, or I'm missing > something. I've tried to search and mostly just turned up Arch Linux > wiki pages telling me to do the things I'd already done with > mkfontscale, mkfontdir, and xset. Can anyone point me in the right > direction?
Re: RTL8852AE wifi driver
You need to get the authors to change the license to an acceptable one first, as GPL won't cut it. https://www.openbsd.org/policy.html -- Patrick Harper paia...@fastmail.com On Fri, 19 Nov 2021, at 15:24, Moritz Messner wrote: > Hello, > > there seems to be a working driver for this wifi chip which works under > Linux (https://github.com/lwfinger/rtw89) and I have it in my laptop > (will probably replace it with a intel ax200/201 so I can use it at school). > > How much work would be needed to port the driver to OpenBSD?
Re: Should 80MB of RAM be enough for kernel relinking on i386?
If the situation isn't going to change anytime soon then I have some diffs for INSTALL.i386 and INSTALL.amd64. The latter has not specified disk requirements, I guess since anyone who owns an amd64 system will very likely be using a disk big enough for X, so I figured that the same would apply to any user of an i386 system that meets the proposed minimum RAM. These are based on the 2021-09-21 snapshot versions. --- INSTALL.i386.txtWed Sep 22 16:52:38 2021 +++ INSTALL.i386_newWed Sep 22 16:51:17 2021 @@ -201,10 +201,7 @@ OpenBSD/i386 7.0 supports most SMP (Symmetrical MultiP systems. To support SMP operation, a separate SMP kernel (bsd.mp) is included with the installation file sets. -The minimal configuration to install the system is 32MB of RAM and -at least 250MB of disk space to accommodate the `base' set. -To install the entire system, at least 600MB of disk are required, -and to run X or compile the system, more RAM is recommended. +The minimal configuration to install the system is 512MB of RAM. Please refer to the website for a full list of supported hardware: https://www.openbsd.org/i386.html --- INSTALL.amd64.txt Wed Sep 22 16:52:48 2021 +++ INSTALL.amd64_new Wed Sep 22 16:51:12 2021 @@ -202,6 +202,8 @@ is included with the installation file sets. OpenBSD/amd64 7.0 supports both UEFI/GPT booting and BIOS/MBR booting. +The minimal configuration to install the system is 512MB of RAM. + Please refer to the website for a full list of supported hardware. https://www.openbsd.org/amd64.html Patrick Harper
Re: Should 80MB of RAM be enough for kernel relinking on i386?
> Your swap is only 256MB. That seem too low. (We have walked away > from making it correspond to physical memory, but still, it seems > uncomfortably low). > > As well, /usr seems a bit large, leaving not much for /home. > > The autoallocation scheme might have made a less than perfect > decision here. I tried the same thing except for editing the partition layout to allow for 512M of swap: wd1*> p m OpenBSD area: 64-15662304; size: 7647.6M; free: 955.0M #size offset fstype [fsize bsize cpg] a: 1060.6M 64 4.2BSD 2048 16384 1 # / b: 512.0M 2172128swap c: 7647.6M0 unused d: 3072.0M 3220704 4.2BSD 2048 16384 1 # /usr e: 2048.0M 9512128 4.2BSD 2048 16384 1 # /home and 768M: wd1*> p m OpenBSD area: 64-15662304; size: 7647.6M; free: 699.0M #size offset fstype [fsize bsize cpg] a: 1060.6M 64 4.2BSD 2048 16384 1 # / b: 768.0M 2172128swap c: 7647.6M0 unused d: 3072.0M 3744992 4.2BSD 2048 16384 1 # /usr e: 2048.0M 10036416 4.2BSD 2048 16384 1 # /home ...and there's no practical difference, the system will just sit for half an hour, print one or two seg faults in that time and then reboot. memtest86 didn't print any errors so I'm assuming my memory is fine. I'd say x86 computers without INT 13h Extensions support in the BIOS are pretty much obsolete at this point given that nearly all of them are going to be a combo of very small memory (>128MB was very rare before 1998) and small disk (8.4GB limit).
Should 80MB of RAM be enough for kernel relinking on i386?
Hi All,
The installation program on my Intel P5/80MB RAM machine works fine up
to 'Relinking to create unique kernel...', during which the system
either reboots or eventually prints a kernel panic message. If 80MB is
not enough under normal circumstances then it's not worth debugging.
Apparently 64MB was enough for 6.7
(https://www.uninformativ.de/blog/postings/2020-06-21/0/POSTING-en.html)
but that was then, e.t.c.
paianni$ doas cu
Connected to /dev/cua00 (speed 9600)
>> OpenBSD/i386 BOOT 3.44
boot> machine mem
Region 0: type 1 at 0x0 for 639KB
Region 1: type 1 at 0x10 for 80896KB
Low ram: 639KB High ram: 15360KB
Total free memory: 81535KB
boot> wd0a:/bsd.rd
boot> boot wd0a:/bsd.rd
cannot open wd0a:/etc/random.seed: No such file or directory
booting wd0a:/bsd.rd: 3213847+1405952+3358728+0+421888
[88+160+28]=0x805300
entry point at 0x201000
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights
reserved.
Copyright (c) 1995-2021 OpenBSD. All rights reserved.
https://www.OpenBSD.org
OpenBSD 6.9 (RAMDISK_CD) #768: Sat Apr 17 22:27:31 MDT 2021
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
real mem = 83423232 (79MB)
avail mem = 7228 (69MB)
random: good seed from bootblocks
mainbus0 at root
bios0 at mainbus0: date 11/15/96
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc/0xc000 0xef000/0x1000!
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium (P54C) ("GenuineIntel" 586-class) 134 MHz, 05-02-0c
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MELTDOWN
cpu0: F00F bug workaround installed
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Opti 82C557 Host" rev 0x00
pcib0 at pci0 dev 1 function 0 "Opti 82C558 ISA" rev 0x00
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD7543" rev 0x00
vga1: aperture needed
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com2 at isa0 port 0x3e8/8 irq 5: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
wdc0 at isa0 port 0x1f0/8 irq 14
wd0 at wdc0 channel 0 drive 0:
wd0: 1-sector PIO, LBA48, 7647MB, 15662304 sectors
wd0(wdc0:0:0): using BIOS timings
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pcic0 at isa0 port 0x3e0/2 iomem 0xd/16384
pcic0 controller 0: has sockets A and B
pcmcia0 at pcic0 controller 0 socket 0
wdc2 at pcmcia0 function 0 "TRANSCEND, TS8GCF133, " port 0x340/16: irq 3
wd1 at wdc2 channel 0 drive 0:
wd1: 1-sector PIO, LBA48, 7647MB, 15662304 sectors
wd1(wdc2:0:0): using BIOS timings
pcmcia1 at pcic0 controller 0 socket 1
ne3 at pcmcia1 function 0 "D-Link, DE-660, 118B6603" port 0x300/32, irq
9, address 00:80:c8:8b:ec:8e
pcic0: irq 10, polling enabled
softraid0 at root
scsibus0 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
WARNING: CHECK AND RESET THE DATE!
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
erase ^?, werase ^W, kill ^U, intr ^C, status ^T
Welcome to the OpenBSD/i386 6.9 installation program.
WARNING: /mnt was not properly unmounted
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? i
At any prompt except password prompts you can escape to a shell by
typing '!'. Default answers are shown in []'s and are selected by
pressing RETURN. You can exit this program at any time by pressing
Control-C, but this can leave your system in an inconsistent state.
Terminal type? [vt220]
System hostname? (short form, e.g. 'foo') paipaq
Available network interfaces are: ne3 vlan0.
Which network interface do you wish to configure? (or 'done') [ne3]
IPv4 address for ne3? (or 'dhcp' or 'none') [dhcp]
ne3: no lease..sleeping
IPv6 address for ne3? (or 'autoconf' or 'none') [none]
Available network interfaces are: ne3 vlan0.
Which network interface do you wish to configure? (or 'done') [done]
DNS domain name? (e.g. 'example.com') [my.domain] home
DNS nameservers? (IP address list or 'none') [none]
Password for root account? (will not echo)
Password for root account? (again)
Start sshd(8) by default? [yes]
Do you expect to run the X Window System? [yes] no
Change the default console to com0? [yes] no
Setup a user? (enter a lower-case loginname, or 'no') [no] paianni
Full name for user paianni? [paianni] Patrick Harper
Password for user paianni? (will not echo)
Password for user paianni? (again)
WARNING: root is targeted by password guessing attacks, pubkeys are
safer.
Allow root ssh login? (yes, no, prohibit-password) [no]
Available disks are: wd0 wd1.
Which disk is the root disk? ('?' for details) [wd0] wd1
Disk: wd1 geometry: 15538/16/63 [15662304 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
Re: USB speakers
Can you post your /etc/rc.conf.local ? -- Patrick Harper paia...@fastmail.com On Fri, 14 Aug 2020, at 17:21, Justin Muir wrote: > Wondering whether anyone has experience with Logitech USB speakers? > > Plugged in mine, did the rcctl rsnd/0 thingi from multimedia FAQ: > # rcctl set sndiod flags -f rsnd/0 -F rsnd/1 > # rcctl restart sndiod > > It doesn't work. As a matter of fact, the speaker light doesn't even come > on now. > > Any suggestions? > > > tia! > > J > > Dmesg output below: > > uaudio0 at uhub4 port 2 configuration 1 interface 1 "Logitech Logitech USB > Speaker" rev 1.10/0.07 addr 3 > uaudio0: class v1, full-speed, sync, channels: 2 play, 0 rec, 7 ctls > audio1 at uaudio0 > uhidev2 at uhub4 port 2 configuration 1 interface 2 "Logitech Logitech USB > Speaker" rev 1.10/0.07 addr 3 > uhidev2: iclass 3/0 > uhid3 at uhidev2: input=2, output=0, feature=0 >
Re: Realtek Edimax AC1750 USB gets properly detected but not configurable in ifconfig
Judging by the dmesg there is at least one unoccupied PCIe slot that could accommodate an adapter such as a Silverstone ECWA2-LITE. This would allow you to use Mini-PCIe cards that normally go in laptops, including all of the iwm(4) devices. -- Patrick Harper paia...@fastmail.com On Sat, 6 Jun 2020, at 19:44, Tristan wrote: > Oh sorry, my mistake, I might need some sleep :) > > Thanks for the list of USB adapters, that helps a lot. > > > On Jun 6, 2020, at 9:35 PM, Stuart Henderson wrote: > > > > On 2020/06/06 19:14, Tristan wrote: > >> Ok thanks. Yes I’m looking for just using 11n. > > > > You already replied saying that! > > > > It doesn't matter if you only want to use 11n, OpenBSD does not have a > > driver for the controller used in that adapter. > > > > For USB adapters look for a device using one of these: > > > > bwfm(4) - Broadcom and Cypress IEEE 802.11a/ac/b/g/n wireless network device > > otus(4) - Atheros USB IEEE 802.11a/b/g/n wireless network device > > rsu(4) - Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network > > device > > run(4) - Ralink Technology/MediaTek USB IEEE 802.11a/b/g/n wireless network > > device > > urtwn(4) - Realtek RTL8188CU/RTL8188EU/RTL8192CU/RTL8192EU USB IEEE > > 802.11b/g/n wireless network device > > > > (or there are some 11g-only ones but not much point looking for them). > > > > > >> > >>>> On Jun 6, 2020, at 5:55 AM, Stuart Henderson > >>>> wrote: > >>> > >>> On 2020-06-05, Tristan wrote: > >>>> Just plugged in a Realtek Edimax AC1750 USB card into a ASRock B450M > >>>> board. > >>>> I can see the card being detected and registered properly in dmesg and > >>>> usbdevs, but cannot configure it. > >>>> Is this card supported? > >>> > >>> No. The only supported 11ac USB devices are the limited and fairly hard > >>> to get > >>> hold of bwfm(4) devices. (Some PCIe 11ac are supported but not in 11ac > >>> mode.) > >>> > >>> > >>> > >> > > > >
Re: More than 16 partitions
> Medoesn't a care a flying fsck about what is "trendy". Is this the most ironic sentence ever posted on here? Dubiously censoring an expletive with a common 'Unix' utility isn't motivated by some sort of desire to feel like a part of the righteous ones? Come on.
Re: More than 16 partitions
If you didn't make any of this up, you dumbed it down to the point where there's no useful info left. You seem to operate on the assumption that merely dissing the work of companies and from ecosystems you don't like, as though it's the 'trendy' thing to do, is enough for you to get by on this forum without scrutiny. -- Patrick Harper paia...@fastmail.com On Thu, 23 Apr 2020, at 18:06, zeurk...@volny.cz wrote: > "Groot" wrote: > > I've tried and failed to create more than 16 > > partitions on OpenBSD. First of all I don't > > understand the difference between the operations > > performed by fdisk and disklabel. Is it that > > OpenBSD sees partitions differently? First we > > create an OpenBSD partition with fdisk and then > > with disklabel we can create at the most 16 more > > filesystem partitions within it. > > Traditionally, BSD has used only its own disklabel(5). Unfortunately, > mess-dos on the IBM pee-cee set a competing standard, the "Master Boot > Record", with a separate partition table (and a lot of kludging to > support more than 4 partitions). While it was (and AFAIK remains) > possible to use the whole disk the traditional way (only a BSD > disklabel, as on e.g. sparc64), it has become common practice to wrap > the BSD stuff in a mess-dos partition, with the caveat that some of the > mess-dos partition entries are duplicated in the BSD label. > > Thus, the BSD label is essentially OpenBSD's version of the structure of > things on the disk. But is an imperfect version: 16 partitions *is* the > limit for an OpenBSD label, and, of course, mess-dos partition > identifiers (which are more *ahem* fine-grained) are not used. To top it > off, partitions which rest within the mess-dos OpenBSD partition are not > necessarily represented on the mess-dos level (this would count, from > the mess-dos perspective, as overlap between partitions and thus confuse > a great many tools). > > Then GPT entered the story to make the mess complete. But me'll remain > blissfully unaware of the inner workings of that particular clusterfsck, > if you don't mind ;) > > It's no shame to be confused by this garbage. Almost all of us'd like > better, but for the above hysterical raisins, it's not so easy to make > it so. > > --zeurkous. > > -- > Friggin' Machines! > >
Re: Iridium vs Chromium
I'm puzzled that you thought my statements were a complaint. -- Patrick Harper paia...@fastmail.com On Sun, 12 Apr 2020, at 22:30, Theo de Raadt wrote: > Patrick Harper wrote: > > > I mean that all Chromium releases are made available for OpenBSD-stable > > (excluding the previous release at any given time, as with all existing > > port maintenance). > > So you want constant Chromium updates in -stable. > > Who's going to do that? > > Are you going to do it? > > And why pick only on Chromium. Should the same policy be to update all > *all* packages to -stable, all the time, continuously? > > Who's going to do that? > > Won't we need twice as many people, so that -current ports are maintained, > as well as -stable ports? Or if we can't find more people, won't that mean > a reduction in development of packages in the next release? Which means > that -current won't get updated, which means -stable will fall behind > even further? > > You don't seem to know this: -stable is done by *one person* > > > My understanding of -current is that it is meant for testing, not usage. > > -current turns into a -release. So if you don't want good -release, > which will be followed by good -stable, then how do you think this is > going to work? > > You don't think. You just believe deliverable-product you can conceive > of being possible, should be delivered to you. Probably on a silver > plate? > > I believe I've identified the problem precisely. It is not a software > problem, it is a people with out-of-touch expectation problem. It may be > connected to "the less people pay, the more they expect". It might also > be connected to "wow this group looks open, I can participate by demanding > they do things for me". > > >
Re: Iridium vs Chromium
I mean that all Chromium releases are made available for OpenBSD-stable (excluding the previous release at any given time, as with all existing port maintenance). My understanding of -current is that it is meant for testing, not usage. -- Patrick Harper paia...@fastmail.com On Sun, 12 Apr 2020, at 21:38, Kevin Chadwick wrote: > On April 12, 2020 7:07:01 PM UTC, Patrick Harper wrote: > >The effort to support Chromium and Firefox (sans ESR) on OpenBSD akin > >to Windows/macOS/'Linux' has not happened. > > On atleast current as Theo showed, Chromium is just as well if not > better supported on OpenBSD than on Linux, these days. > > I assume you are judging by a while ago. Or perhaps you mean Chrome > where pre-built binaries for Linux are released by Google? I used to > install chrome on debian/ubuntu to get the extra days. > >
Re: Iridium vs Chromium
The effort to support Chromium and Firefox (sans ESR) on OpenBSD akin to Windows/macOS/'Linux' has not happened. -- Patrick Harper paia...@fastmail.com On Sun, 12 Apr 2020, at 16:49, Raymond, David wrote: > My problem with iridium is that it is based on an older version of > chromium and I am not sure that they keep up with inevitable flow of > security fixes. That said, I am a bit nervous about OpenBSD's lags in > keeping up with browser security fixes. (I'm not criticizing -- I > understand that OpenBSD is a small operation without the people needed > to keep track of non-core packages. And I just converted from Arch > Linux, in which the storm of updates and resulting incompatibilities > drove me crazy and contributed to my shift to OpenBSD. Still, I am a > bit nervous about even slightly out-of-date browsers at this point and > I am not sure that iridium is an improvement in this regard.) > > Dave > > On 4/12/20, Elias M. Mariani wrote: > > I'm not much of a browser savy guy. > > Is Iridium really safer than Chromium? > > Leaving aside the "Google is tracking you!". > > > > Any recommendations on the browser front on performance, security and > > compatibility? > > I've been using Chrome and Chromium for years, but maybe there are > > better alternatives that I'm unaware of... > > > > Cheers. > > Elias. > > > > > > > -- > David J. Raymond > david.raym...@nmt.edu > http://physics.nmt.edu/~raymond > >
Re: Issues with X and Gnome on OpenBSD new install
Did you follow /usr/local/share/doc/pkg-readmes/gnome ? -- Patrick Harper paia...@fastmail.com On Tue, 7 Jan 2020, at 23:05, Michael G Workman wrote: > Hello, > > OpenBSD is a great operating system, glad to have been to installed it > successfully. > > I installed OpenBSD on a Dell Vostro 1500 laptop with dual core 2ghz intel > processor, 2 GB of RAM, and 120 GB hard drive (circa 2008 laptop) > > I had problems with firefox, but installed Chromium instead and Chrome > works great for web browsing. > > I also installed bash and nano, and also installed Gnome. Hoping to use > Gnome instead of the default window manager. > > But encountered a fatal error, the X server could not be found, and also a > driver called xf86OpenConsole was missing, causing a fatal server error. > > When I installed it, I chose openbsd-dell for the hostname, and then > OpenBSD tacked on attlocal.net to it to make it openbsd-dell.attlocal.net, > but not sure how that happened, an nslookup on attlocal.net says it is an > invalid domain. > > I am sure it must be a simple fix, here is my Xorg.1.log file: > > Thanks. > > [ 6760.324] > X.Org X Server 1.20.5 > X Protocol Version 11, Revision 0 > [ 6760.324] Build Operating System: OpenBSD 6.6 amd64 > [ 6760.324] Current Operating System: OpenBSD openbsd-dell.attlocal.net > 6.6 GENERIC.MP#372 amd64 > [ 6760.324] Build Date: 12 October 2019 11:22:22AM > [ 6760.324] > [ 6760.325] Current version of pixman: 0.38.4 > [ 6760.325] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 6760.325] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 6760.325] (==) Log file: > "/home/mworkman72/.local/share/xorg/Xorg.1.log", Time: Tue Jan 7 15:01:09 > 2020 > [ 6760.341] (==) Using system config directory > "/usr/X11R6/share/X11/xorg.conf.d" > [ 6760.351] (==) No Layout section. Using the first Screen section. > [ 6760.351] (==) No screen section available. Using defaults. > [ 6760.351] (**) |-->Screen "Default Screen Section" (0) > [ 6760.351] (**) | |-->Monitor "" > [ 6760.352] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 6760.352] (==) Automatically adding devices > [ 6760.352] (==) Automatically enabling devices > [ 6760.352] (==) Not automatically adding GPU devices > [ 6760.352] (==) Max clients allowed: 256, resource mask: 0x1f > [ 6760.401] (==) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > [ 6760.401] (==) ModulePath set to "/usr/X11R6/lib/modules" > [ 6760.401] (II) The server relies on wscons to provide the list of input > devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [ 6760.401] (II) Loader magic: 0xef025473000 > [ 6760.402] (II) Module ABI versions: > [ 6760.402] X.Org ANSI C Emulation: 0.4 > [ 6760.402] X.Org Video Driver: 24.0 > [ 6760.402] X.Org XInput driver : 24.1 > [ 6760.404] X.Org Server Extension : 10.0 > [ 6760.404] (EE) > Fatal server error: > [ 6760.404] (EE) xf86OpenConsole: No console driver found > Supported drivers: wscons > Check your kernel's console driver configuration and /dev entries(EE) > [ 6760.404] (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > [ 6760.404] (EE) Please also check the log file at > "/home/mworkman72/.local/share/xorg/Xorg.1.log" for additional information. > [ 6760.405] (EE) > [ 6760.406] (EE) Server terminated with error (1). Closing log file. > > *Michael G. Workman* > (321) 432-9295 > michael.g.work...@gmail.com >
Re: What happened to 6.6/sgi?
https://marc.info/?l=openbsd-cvs=156941089510768=2 -- Patrick Harper paia...@fastmail.com On Sun, 8 Dec 2019, at 16:29, Stefan Hagen wrote: > Hello * > > I was browsing around and noticed that there are no files for the SGI > platform on the mirrors. SGI is mentioned in the 6.6/README, so I assume > it is supported. Did it get lost somehow? (snapshot/sgi exists) > > Bye, > Stefan > > >
Re: Display flickers after upgrade to 6.6
I can confirm that switching to EXA made GNOME usable. This'll only work up to Northern Islands cards/IGPs though. Guess I'll be holding off of a GPU upgrade for a while longer. -- Patrick Harper paia...@fastmail.com On Thu, 31 Oct 2019, at 13:47, Patrick Harper wrote: > I haven't tried those settings yet (in my case GNOME Shell and > Xfdashboard cause the display to corrupt and seize up except the > cursor) but ShadowPrimary is a glamor option that should be irrelevant > if EXA is used. > > For years I've also observed text flickering in the console after drm > is loaded, but in 6.5 and prior 3D-accelerated stuff was usable. Cayman > should be fine with 8 million pixels. > > -- > Patrick Harper > paia...@fastmail.com > > On Wed, 30 Oct 2019, at 13:12, Jeff wrote: > > On Sat, 19 Oct 2019 17:59:41 +0200 > > Federico Giannici wrote: > > > > > On 2019-10-19 16:17, Andre Stoebe wrote: > > > > Hi, > > > > > > > > I ran into the same issue this morning. Disabling the compositor > > > > worked for me, but I noticed later that this is also documented in > > > > the package readme: > > > > > > > > Screen compositor > > > > = > > > > If you're using the modesetting X driver and experience window > > > > flickering when > > > > the compositor is enabled, you should force the window manager to > > > > use the XPresent method for vblank: > > > > > > > > $xfwm4 --vblank=xpresent --replace & > > > > > > I tried that command but it screwed all my windows (no more window > > > decorations and buttons, I cannot operate on windows)! > > > Now I had to came back to KDE... > > > :-( > > > > > > Regards > > > > > > > > > > This is documented upstream at > > > > https://git.xfce.org/xfce/xfwm4/tree/COMPOSITOR#n114 > > > > > > > > Haven't tested that yet and left the compositor disabled, but I > > > > guess this will fix your issues. If it does, that's probably a good > > > > reminder to first look in the readme next time (me included). ;) > > > > > > > > Regards, > > > > André > > > > > > > > Hi, I thought I'd relate my experience: I also experienced this issue on > > a machine recently upgraded to OpenBSD 6.6 which uses the aruba > > chipset and also running xfce. My workaround > > (which was based on 'try stuff to see what works') involved turning off > > compositing and > > (via xorg.conf.d): > > > > ... > > Option "AccelMethod" "EXA" > > Option "ShadowPrimary" "on" > > Option "SwapbuffersWait" "off" > > Option "EnablePageFlip" "off" > > ... > > > > This resolved issues with flickering, the mouse pointer vanishing and > > re-appearing depending on which window is below the pointer (enabling > > software mouse pointer for this was worse as garbage was rendered in a > > rect surrounding the pointer), and also *some* issues with logging > > in-out of an X session via xenodm. > > > > I still experience problems with the machine going to sleep and waking > > up, as sometimes, upon wake-up, the graphics go wonky, or don't update > > at all, or the mouse pointer goes wonky. > > > > Beyond the aforementioned, this set-up seems to allow me to use the > > machine as before, however, I am not an X11 expert nor a radeondrm > > driver expert; your mileage may very. > > > > If I ever try Andre's hint in the future (thank-you), I might report on > > success/failure. > > > > regards, > > > > Jeff > > > > > >
Re: Display flickers after upgrade to 6.6
I haven't tried those settings yet (in my case GNOME Shell and Xfdashboard cause the display to corrupt and seize up except the cursor) but ShadowPrimary is a glamor option that should be irrelevant if EXA is used. For years I've also observed text flickering in the console after drm is loaded, but in 6.5 and prior 3D-accelerated stuff was usable. Cayman should be fine with 8 million pixels. -- Patrick Harper paia...@fastmail.com On Wed, 30 Oct 2019, at 13:12, Jeff wrote: > On Sat, 19 Oct 2019 17:59:41 +0200 > Federico Giannici wrote: > > > On 2019-10-19 16:17, Andre Stoebe wrote: > > > Hi, > > > > > > I ran into the same issue this morning. Disabling the compositor > > > worked for me, but I noticed later that this is also documented in > > > the package readme: > > > > > > Screen compositor > > > = > > > If you're using the modesetting X driver and experience window > > > flickering when > > > the compositor is enabled, you should force the window manager to > > > use the XPresent method for vblank: > > > > > > $xfwm4 --vblank=xpresent --replace & > > > > I tried that command but it screwed all my windows (no more window > > decorations and buttons, I cannot operate on windows)! > > Now I had to came back to KDE... > > :-( > > > > Regards > > > > > > > This is documented upstream at > > > https://git.xfce.org/xfce/xfwm4/tree/COMPOSITOR#n114 > > > > > > Haven't tested that yet and left the compositor disabled, but I > > > guess this will fix your issues. If it does, that's probably a good > > > reminder to first look in the readme next time (me included). ;) > > > > > > Regards, > > > André > > > > > Hi, I thought I'd relate my experience: I also experienced this issue on > a machine recently upgraded to OpenBSD 6.6 which uses the aruba > chipset and also running xfce. My workaround > (which was based on 'try stuff to see what works') involved turning off > compositing and > (via xorg.conf.d): > > ... > Option "AccelMethod" "EXA" > Option "ShadowPrimary" "on" > Option "SwapbuffersWait" "off" > Option "EnablePageFlip" "off" > ... > > This resolved issues with flickering, the mouse pointer vanishing and > re-appearing depending on which window is below the pointer (enabling > software mouse pointer for this was worse as garbage was rendered in a > rect surrounding the pointer), and also *some* issues with logging > in-out of an X session via xenodm. > > I still experience problems with the machine going to sleep and waking > up, as sometimes, upon wake-up, the graphics go wonky, or don't update > at all, or the mouse pointer goes wonky. > > Beyond the aforementioned, this set-up seems to allow me to use the > machine as before, however, I am not an X11 expert nor a radeondrm > driver expert; your mileage may very. > > If I ever try Andre's hint in the future (thank-you), I might report on > success/failure. > > regards, > > Jeff > >
Re: Cannot add login class (ports/meta/gnome/pkg/README-main)
Adding an empty line at the end of login.conf fixed my problem. -- Patrick Harper paia...@fastmail.com On Tue, 17 Sep 2019, at 14:21, Patrick Harper wrote: > Hi All, > > For a while this file has instructed a new login class to be added to > the end of /etc/login.conf, as per below. > > gnome:\ > :datasize-cur=1024M:\ > :tc=default: > > On both my amd64 machines, this does not effectuate following a reboot. > If I try to create a new user in the class with adduser and try to > specify gnome, > > gnome: is not allowed! > > is printed. gnome is not listed in the 'Default login class list' > either. If I use the usermod command as written in the readme, > > usermod: No such login class `gnome' > > is printed. > > If I try to force the gnome class by editing the chpass database for > the user and rebooting, users will appear on the gdm greeter but it is > impossible to login to them. Users created through the GNOME Settings > are added to the default class and are also impossible to login to, I > think because the password encoding is different. > > My workaround for now is to use the 'staff' login class, which seems to > have resource limits high enough for gnome to work, although it is "not > recommended". With this setup there is a functionality issue - logging > out through the UI causes gdm to exit to the console (although the > daemon seems to continue running), whereas it should display the gdm > greeter. Whether or not this is a byproduct of the staff class settings > I don't know. > > -- > Patrick Harper > paia...@fastmail.com > >
Re: Cannot add login class (ports/meta/gnome/pkg/README-main)
I'm using 6.5-stable including the binary package updates. -- Patrick Harper paia...@fastmail.com On Tue, 17 Sep 2019, at 14:21, Patrick Harper wrote: > Hi All, > > For a while this file has instructed a new login class to be added to > the end of /etc/login.conf, as per below. > > gnome:\ > :datasize-cur=1024M:\ > :tc=default: > > On both my amd64 machines, this does not effectuate following a reboot. > If I try to create a new user in the class with adduser and try to > specify gnome, > > gnome: is not allowed! > > is printed. gnome is not listed in the 'Default login class list' > either. If I use the usermod command as written in the readme, > > usermod: No such login class `gnome' > > is printed. > > If I try to force the gnome class by editing the chpass database for > the user and rebooting, users will appear on the gdm greeter but it is > impossible to login to them. Users created through the GNOME Settings > are added to the default class and are also impossible to login to, I > think because the password encoding is different. > > My workaround for now is to use the 'staff' login class, which seems to > have resource limits high enough for gnome to work, although it is "not > recommended". With this setup there is a functionality issue - logging > out through the UI causes gdm to exit to the console (although the > daemon seems to continue running), whereas it should display the gdm > greeter. Whether or not this is a byproduct of the staff class settings > I don't know. > > -- > Patrick Harper > paia...@fastmail.com
Cannot add login class (ports/meta/gnome/pkg/README-main)
Hi All, For a while this file has instructed a new login class to be added to the end of /etc/login.conf, as per below. gnome:\ :datasize-cur=1024M:\ :tc=default: On both my amd64 machines, this does not effectuate following a reboot. If I try to create a new user in the class with adduser and try to specify gnome, gnome: is not allowed! is printed. gnome is not listed in the 'Default login class list' either. If I use the usermod command as written in the readme, usermod: No such login class `gnome' is printed. If I try to force the gnome class by editing the chpass database for the user and rebooting, users will appear on the gdm greeter but it is impossible to login to them. Users created through the GNOME Settings are added to the default class and are also impossible to login to, I think because the password encoding is different. My workaround for now is to use the 'staff' login class, which seems to have resource limits high enough for gnome to work, although it is "not recommended". With this setup there is a functionality issue - logging out through the UI causes gdm to exit to the console (although the daemon seems to continue running), whereas it should display the gdm greeter. Whether or not this is a byproduct of the staff class settings I don't know. -- Patrick Harper paia...@fastmail.com
Re: What is you motivational to use OpenBSD
What motivates me to stay on OpenBSD is that I want the free desktop concept to work. This system + Arcan + GNOME-like interface seems, to me, like an compelling way to get there. I hope I can shoehorn this project into my life and then reality in some fashion. -- Patrick Harper paia...@fastmail.com On Wed, 28 Aug 2019, at 15:32, Mohamed salah wrote: > I wanna put something in discussion, what's your motivational to use > OPENBSD what not other bsd's what not gnu/Linux, if something doesn't work > fine on openbsd and you love this os so much what will do? >
Re: Puffy — format SVG
An SVG with the textual logo exists at https://upload.wikimedia.org/wikipedia/en/8/83/OpenBSD_Logo_-_Cartoon_Puffy_with_textual_logo_below.svg -- Patrick Harper paia...@fastmail.com On Thu, 13 Jun 2019, at 19:37, Stephane HUC "PengouinBSD" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > For a little project to promote, I had the idea to convert the gif image > about Puffy, into svg with Inkscape. > > Some will consider it a bad idea ... ! > At least, the image in SVG format exists. > > it is available on my server: > https://stephane-huc.net/img/EBNH/OBSD/Puffy.svg > > Voilà! :D > > PS: If someone wants to put it on the openbsd www, it's up to you! ;) > > - -- > ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<< > - > Stephane HUC as PengouinBSD or CIOTBSD > b...@stephane-huc.net > -BEGIN PGP SIGNATURE- > > iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXQKXrgAKCRATq98t3AMG > 755TAQCe6mlsM7iYoYlYQSdE7nh7uaxR7C/xTOP19l5lk6+YVQD/fgqPutl2dm4s > 2XpB5OhLUZp4GM4MSz/Xw8qPY+UyPwk= > =FjrT > -END PGP SIGNATURE- > >
Re: OpenBSD runs only in RAM from a USB Flash Drive
FFS isn't a journaling filesystem so any 'wear', even on primitive flash storage, won't be enough to worry about. -- Patrick Harper paia...@fastmail.com On Fri, 31 May 2019, at 03:41, sove...@vivaldi.net wrote: > 30 May, 2019 > > Greetings OpenBSD aficionados, > > As a newbie to OpenBSD, I am delighted to have the chance to interact > with the OpenBSD Mailing Lists community. > Since I am about to install OpenBSD 6.5 (amd64) on a USB Flash Drive for > the first time, I was wondering if anyone has a solution to the > following conundrum. > > In order to minimize wear on the USB Flash memory, is there a way to > command OpenBSD to always run in RAM, and at shutdown to either save or > not save the session to the USB Flash Drive. > > For instance, Precise Puppy Linux 5.7.1 has a package called Puppy Event > Manager. Since Precise Puppy is programmed to run in RAM, you can select > the 'Save Session' tab and enter the span of minutes for everything in > RAM to be saved to the Precise Puppy SaveFile. > > Best of all, you can enter 0 minutes to only do a save at shutdown. > Perfect for minimizing wear on a USB Flash Drive. > > Please accept my apologies if this issue has already been solved. My > search so far in sites like https://marc.info has come up empty. > > I thank you for your support. > > Best regards, > Hugh > >
Re: Missing file and Man page for out-of-date
It was renamed to pkg_outdated. -- Patrick Harper paia...@fastmail.com On Sat, 25 May 2019, at 22:17, Michael Alaimo wrote: > The /usr/ports/infrastructure/bin/out-of-date program is missing. > > I remember it being in OpenBSD 6.3. > > It is still referenced in /usr/ports/infrastructure/README in OpenBSD 6.5. > > It is listed with description: > bin/out-of-date > Compare installed registered packages with INDEX, try to find out > of date ports. > > Is it possible to get the script back into ports for OpenBSD 6.5? > > Does anyone know what happened with it? > > Regards, > > Michael > > http://quantum-foam.org/ > >
Re: Modern browser for OpenBSD powerpc
Binaries stopped being committed to the Mozilla archive after 52.0.2 but the port seems to be active. I assume 60esr is supposed to work on sparc (still) as some recent patches refer to it in the filenames. -- Patrick Harper paia...@fastmail.com On Sat, 25 May 2019, at 18:54, john o goyo wrote: > On 05/25/19 11:41, Patrick Harper wrote: > > Oracle's Beijing Team maintains a port of FF60esr for Solaris/sparc that > > might be useful (another mostly big-endian arch). > > > > https://github.com/oracle/solaris-userland/tree/master/components/desktop/firefox > Excuse my ignorance but is it really Sparc? When Oracle laid off Ginn > Chen, who contributed the Sparc build to Mozilla, I thought that was the > end of Firefox on Sparc. > > jog > >
Re: Modern browser for OpenBSD powerpc
Oracle's Beijing Team maintains a port of FF60esr for Solaris/sparc that might be useful (another mostly big-endian arch). https://github.com/oracle/solaris-userland/tree/master/components/desktop/firefox -- Patrick Harper paia...@fastmail.com On Sat, 25 May 2019, at 12:54, Riccardo Mottola wrote: > Hi, > > On 5/23/19 8:19 AM, John Gould wrote: > > Can someone suggest a modern graphical browser for OpenBSD PowerPC? > > I'm trying to run > > several G5's and g4 mini's on 6.5 as desktop machines. The basic > > install works really well but there doesn't seem to be an up to date > > graphically browser. > > > > It's thanks to all the work the devs have put into OpenBSD powerpc > > that these machine are still very usable. They are hopelessly out of > > date as far as the Mac OS are concerned! > > > you might try ArcticFox, it has a decent success on Linux PowerPC. > Several endianness fixes were imported. > > It is not "totally" modern, but still more modern than Dillo. Beware > that you need at least 1G of RAM to be of decent use with modern > websites, 2GB is better. > > Although it is of PaleMoon heritage and thus Linux/Mac heritage, I fixed > compilation on NetBSD, OpenBSD and lately even FreeBSD compiles out of > the box. > > > Beware however, that while perfectly usable on older x86, it has no > working JIT, so JS intensive websites will be slow on PowerPC. Also > compilation on OpenBSD/ppc was never attempted by me, only on Linux/PPC. > OpenBSD amd64 however does work. > > > Riccardo > > [1] : Official Repo: https://github.com/wicknix/Arctic-Fox > > [2] : My current working fork, which gets regularly pulled into main: > https://github.com/rmottola/Arctic-Fox > > > > >
Re: When will be created a great desktop experience for OpenBSD?
So you think everyone replying to this thread is an idiot? -- Patrick Harper paia...@fastmail.com On Fri, 24 May 2019, at 18:38, Jordan Geoghegan wrote: > > On 5/24/19 10:26 AM, Patrick Harper wrote: > > Is it acceptable for third-parties to produce and distribute physical > > copies of releases, using official logos, similar to those made for 6.0 and > > prior by the project? > > > Can you please stop replying to this thread, I'm so tired of receiving > emails from you idiots. > >
Re: When will be created a great desktop experience for OpenBSD?
Is it acceptable for third-parties to produce and distribute physical copies of releases, using official logos, similar to those made for 6.0 and prior by the project? -- Patrick Harper paia...@fastmail.com
Re: When will be created a great desktop experience for OpenBSD?
Thank you for helping me keep this thread going. -- Patrick Harper paia...@fastmail.com On Thu, 23 May 2019, at 20:04, Daniel Jakots wrote: > On Thu, 23 May 2019 19:51:45 +, "Patrick Harper" > wrote: > > > Our ideas of the setup process aren't equal so I disagree. > > Can you please stop answering to this useless thread? >
Re: When will be created a great desktop experience for OpenBSD?
Our ideas of the setup process aren't equal so I disagree. -- Patrick Harper paia...@fastmail.com On Thu, 23 May 2019, at 18:16, Raul Miller wrote: > This looks like violent agreement. (It's perhaps worth noting that if > you change the first word here from "No" to "Yes" that the idea being > expressed does not change.) > > Thanks, > > -- > Raul > > On Thu, May 23, 2019 at 1:35 PM Patrick Harper wrote: > > > > No, the installation program should make setup as easy as possible. The > > idea of a common development platform for X being suited only for circa > > 100dpi screens in 2019 is ludicrous. Making users pore through > > half-a-dozen man pages and config files to make their X systems usable on > > hidpi screens is ludicrous. > > > > -- > > Patrick Harper > > paia...@fastmail.com > > > > On Thu, 23 May 2019, at 16:58, Ingo Schwarze wrote: > > > Hi, > > > > > > Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100: > > > > > > > I think OpenBSD could be made easier to set up for GUI applications > > > > if some configuration that is currently done in files could be moved > > > > to the install program. > > > > > > I very strongly oppose the idea. > > > > > > > These questions (or similar) could be shown > > > > > > Absolutely not. The installer should ask as few questions as possible, > > > ideally none whatsoever. *That* is a way to simplify setup. > > > > > > The topics you mention have nothing to do with installation. > > > They are merely low-importance user configuration that can be done > > > at any time if desired. But almost no user will ever have to consider > > > any of those; i certainly didn't, ever, and i have been using many > > > OpenBSD computers for almost two decades now, including with a wide > > > variety of GUI applications. > > > > > > Yours, > > > Ingo > > > > > >
Re: When will be created a great desktop experience for OpenBSD?
No, the installation program should make setup as easy as possible. The idea of a common development platform for X being suited only for circa 100dpi screens in 2019 is ludicrous. Making users pore through half-a-dozen man pages and config files to make their X systems usable on hidpi screens is ludicrous. -- Patrick Harper paia...@fastmail.com On Thu, 23 May 2019, at 16:58, Ingo Schwarze wrote: > Hi, > > Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100: > > > I think OpenBSD could be made easier to set up for GUI applications > > if some configuration that is currently done in files could be moved > > to the install program. > > I very strongly oppose the idea. > > > These questions (or similar) could be shown > > Absolutely not. The installer should ask as few questions as possible, > ideally none whatsoever. *That* is a way to simplify setup. > > The topics you mention have nothing to do with installation. > They are merely low-importance user configuration that can be done > at any time if desired. But almost no user will ever have to consider > any of those; i certainly didn't, ever, and i have been using many > OpenBSD computers for almost two decades now, including with a wide > variety of GUI applications. > > Yours, > Ingo >
Re: When will be created a great desktop experience for OpenBSD?
I think OpenBSD could be made easier to set up for GUI applications if some
configuration that is currently done in files could be moved to the install
program.
These questions (or similar) could be shown after the one about xenodm:
'Select a resolution for all screens in dots per inch ('?' for list) [96]'
The options would be 96, 120, 144, 192 and 284. The changes made for a
different value would not only be the Xserver dpi setting, but also for the
sizes of fonts and graphical elements in the default configuration files of
window managers (fvwmrc, cwmrc, twmrc), xclock, xterm, xconsole, xcalc and xman.
'Choose a window manager for X ('cwm' or 'fvwm' or 'twm') [fvwm]'
If cwm is entered here, this question could be shown:
'Do you want cwm key bindings to use the Mod4 (windows) key in place of the
Meta key? [no]'
There might be a reason for cwm key bindings to not use Mod4, but those who
have the key available might appreciate not having to create a custom cwmrc so
they can avoid conflicts with default keyboard shortcuts in some ports.
--
Patrick Harper
paia...@fastmail.com
Re: Modern browser for OpenBSD powerpc
Epiphany/GNOME Web is fine, but make sure you have the ports tree loaded for stable updates, WebKit is not the safest code base in the world. -- Patrick Harper paia...@fastmail.com On Thu, 23 May 2019, at 07:21, John Gould wrote: > Can someone suggest a modern graphical browser for OpenBSD PowerPC? > I'm trying to run > several G5's and g4 mini's on 6.5 as desktop machines. The basic > install works really well but there doesn't seem to be an up to date > graphically browser. > > It's thanks to all the work the devs have put into OpenBSD powerpc > that these machine are still very usable. They are hopelessly out of > date as far as the Mac OS are concerned! > > Kind regards John. > >
Re: USB sound card not playing
See Errata 6 of this paper: https://www.mouser.com/pdfdocs/5chipset3400chipsetspecupdate.PDF If you have a B2 stepping of the Intel 3400 chipset then the only way you can get around it is with a PCI(e) USB card with a good chipset. -- Patrick Harper paia...@fastmail.com On Mon, 20 May 2019, at 03:23, Tuyosi T wrote: > Hi, Alexandre Ratchov > > this PC is old(about 10 yeas old) hitachi server (HA-8000) . > > > the full dmesg is > > # dmesg > OpenBSD 6.5-current (GENERIC.MP) #17: Sun May 12 00:53:38 MDT 2019 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8564375552 (8167MB) > avail mem = 8294731776 (7910MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf0d90 (25 entries) > bios0: vendor Phoenix Technologies LTD version "F4" date 10/18/2010 > bios0: HITACHI HA8000/TS10 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S1 S4 S5 > acpi0: tables DSDT FACP TCPA SSDT DMAR APIC SLIC MCFG HPET SPCR EINJ > HEST BERT SSDT ERST > acpi0: wakeup devices PEG_(S4) PEG2(S4) P0P3(S4) P0P5(S4) PEX1(S4) > PEX3(S4) PEX4(S4) PEX5(S4) EHI1(S1) EHI2(S1) LAN_(S5) PCIB(S1) > 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) Xeon(R) CPU X3430 @ 2.40GHz, 2527.37 MHz, 06-1e-05 > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,MELTDOWN > cpu0: 256KB 64b/line 8-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 132MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2526.99 MHz, 06-1e-05 > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2526.99 MHz, 06-1e-05 > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2526.99 MHz, 06-1e-05 > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,MELTDOWN > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 0, core 3, package 0 > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 > acpimcfg0: addr 0xe000, bus 0-16 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus -1 (PEG_) > acpiprt1 at acpi0: bus -1 (PEG2) > acpiprt2 at acpi0: bus 1 (P0P3) > acpiprt3 at acpi0: bus 2 (P0P5) > acpiprt4 at acpi0: bus 0 (PCI0) > acpiprt5 at acpi0: bus 5 (PEX1) > acpiprt6 at acpi0: bus 9 (PEX3) > acpiprt7 at acpi0: bus 11 (PEX4) > acpiprt8 at acpi0: bus 13 (PEX5) > acpicpu0 at acpi0: !C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS > acpicpu1 at acpi0: !C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS > acpicpu2 at acpi0: !C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS > acpicpu3 at acpi0: !C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpicmos0 at acpi0 > "PNP0A05" at acpi0 not configured > acpibtn0 at acpi0: PWRB > ipmi at mainbus0 not configured > cpu0: Enhanced SpeedStep 2527 MHz: speeds: 2395, 2394, 2261, 2128, > 1995, 1862, 1729, 1596, 1463, 1330, 1197 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel Core DMI" rev 0x11 > ppb0 at pci0 dev 3 function 0 "Intel Core PCIE" rev 0x11: msi > pci1 at ppb0 bus 1 > ppb1 at pci0 dev 5 function 0 "Intel Core PCIE" rev 0x11: msi > pci2 at ppb1 bus 2 > mfi0 at pci2 dev 0 function 0 "Symb
Re: When will be created a great desktop experience for OpenBSD?
On Tue, 14 May 2019, at 09:09, ULF wrote: > If from one side is true that many modern interfaces (mostly M$, though) > are made for people who know nothing about computing, from one another is > clear that some good ones (in terms of usability) help the user to keep > concentrated on his work. > > On a mac, on a recent gnome, on a kde, etc. it's easier for a user to keep > track of multiple jobs without thinking about the OS, but rather thinking > about contents. It's a matter of fact that computers are mostly used to do > things that have nothing to do with programming and sysadmin, and also > developers here must, while programming/administering the machine, maybe > write a letter to the insurance, browse 20+ pages while looking at a > calendar (maybe shared) during a phone call, opening the accounting program > for taxes and so on... > > In 2019, doing all of the above with fvwm, twm, (whatever-tiny)wm not only > feels awkward, but also time consuming and less flexible. The argument that > one just has to type "command &" is not as valid as just clicking an icon > when one of your hands is busy holding the phone or a document. If one's window manager's configuration file is set up to provide shortcuts to all relevant applications, then there's no need to use a terminal for that. > > And, btw, let's say it: fvwm looks like 70s/80s, it's full of charm for > retrocomputing but it's pretty ugly to see in 2019. And many people prefer > just right clicking on a picture to change background rather than finding > which config file they gotta change and then change it. Because config > files are good, but total lack of automatization > for basic activies is just time consuming, not sexy. Not to speak about > fonts, icons and, especially, different languages (I mean alphabets) > managing just shifting to a non-latin keyboard becomes hell. I think you have a point in there somewhere but I can't find it.
Re: When will be created a great desktop experience for OpenBSD?
Aren't new users forced to use fvwm already since that's the default? Removing the options won't stop those inclined from finding one they like in packages (unless alt. DEs and WMs are set to be culled from ports as well O_O). However, there is an opportunity for all GUI ports to include a mechanism to add a shortcut to executables in a given WM's menu, that would be made more practicable with a forced default. None of the Xlib window managers are resolution independent from what I can tell. Making fvwm comfortable to use on my 4K screen involved doubling the sizes of fonts, titlebars, borders, icons and the viewport window in .fvwmrc. I didn't bother trying to do the same with all the other fvwm modules and I don't think anyone should be expected to. Until the day comes when all of this, plus the X11 utilities (xterm et. al) can be configured automatically based on the Xserver dpi setting, cwm is the easiest to set up as only the border and font sizes need changing. -- Patrick Harper paia...@fastmail.com
Re: New laptop recommendations
X200 is a bad idea, Core 2 Duos will never get microcode updates for Spectre bugs. -- Patrick Harper paia...@fastmail.com On Thu, 21 Jun 2018, at 08:30, flipchan wrote: > I got the x200 with libreboot and openbsd > > On June 19, 2018 10:47:24 AM UTC, Kaya Saman wrote: > >I couldn't say for the compatibility with OpenBSD though I have read > >other people running on them, but how about Lenovo?? > > > > > >I've got an X220 which I run a Linux distro on which I'm really happy > >with though the i7 CPU does seem to overheat for some reason, though I > >seem to have this issue with all laptops I've gone through?? Must be me > >:-S > > > >- only system that never overheated was my old PowerBook G3 Firewire > >running Mac OS 9 > > > > > >I might be remembering wrong but I'm sure I've seen people on the list > >running OBSD on X-series Lenovo's so it might be worth a shot unless > >anyone else has better suggestions :-) > > > > > >Regards, > > > > > >Kaya > > > > > >On 06/19/18 11:37, Rupert Gallagher wrote: > >> I'm done with my 10 years old 1200EUR MacBookPro. It served me well, > >every day, but is now falling apart, finally. > >> > >> I would buy a new one if only Steve Jobs would be alive and keeping > >Apple inspired. The new models are meticulously designed to make you > >suffer: expensive, slow cpu, soldered ram, soldered disk, small disk, > >bad keyboard keys, wifi only, must pay extra for standard connectors. > >> > >> I have 1500EUR for a new laptop. What would you buy with it? > > -- > Take Care Sincerely flipchan layerprox dev
Re: New laptop recommendations
No drm support for Kaveri in OpenBSD 6.3. There is support in current now so 6.4 should work better when it arrives. -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 14:03, Johan Mellberg wrote: > Hmm. I have that one and there’s something fishy with the graphics, when > I boot the installer (6.3) I just get “static” on the built in screen. > No problem with any other OS. I just tried booting OpenBSD as a test so > have not investigated further, but consider it a potential issue, it > might be just my specimen but then again, maybe not. > > Mvh, Johan > — > Smartphone. Ja... just det. > > > 20 juni 2018 kl. 21:36 skrev Patrick Harper : > > > > HP EliteBook 745 G2? > > > > -- > > Patrick Harper > > paia...@fastmail.com > > > >> On Wed, 20 Jun 2018, at 09:01, Thomas Frohwein wrote: > >> No AMD laptop recommendations in this day and age? Also buying used or > >> refurbished laptops on eBay is a security risk from the outset - ask > >> yourself how well you would be at spotting if someone had tampered e.g. > >> with the webcam or the firmware? With new hardware, you have at least a > >> reasonable expectation that the package hasn't been opened between > >> manufacturer and you... > >> > >
Re: New laptop recommendations
HP EliteBook 745 G2? -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 09:01, Thomas Frohwein wrote: > No AMD laptop recommendations in this day and age? Also buying used or > refurbished laptops on eBay is a security risk from the outset - ask > yourself how well you would be at spotting if someone had tampered e.g. > with the webcam or the firmware? With new hardware, you have at least a > reasonable expectation that the package hasn't been opened between > manufacturer and you... >
Re: Poor browser performance in OpenBSD
FvwmButtons + "Pager" Module FvwmPager 0 0 + "Pager (2 desks)" Module FvwmPager 0 1 + "WinList" Module FvwmWinList + "" Nop + "Banner"Module FvwmBanner + "ScrollBar" Module FvwmScroll 50 50 + "Background" Module FvwmBacker + "AutoRaise" Module FvwmAuto 200 Raise Nop + "Stop AutoRaise" KillModule FvwmAuto + "" Nop + "IconBox" Module FvwmIconBox + "IconMan" Module FvwmIconMan + "" Nop + "Form - Rlogin" Module FvwmForm Rlogin + "Form - MyFvwmTalk" Module FvwmForm MyFvwmTalk + "Form - QuitVerify" Module FvwmForm QuitVerify AddToMenu Quit-Verify + "Restart Fvwm%mini.refresh.xpm%"Restart fvwm + "" Nop + "Start cwm" Restart cwm + "Start wm2" Restart wm2 + "Start twm" Restart twm + "Start ctwm"Restart ctwm + "Start flwm"Restart flwm + "Start mwm" Restart mwm + "Start openbox" Restart openbox + "Start tvtwm" Restart tvtwm + "" Nop + "Start dummy%mini.xterm.xpm%" Restart xterm + "" Nop + "No, Don't Quit"Nop Sample Functions ## AddToFunc MailFunction "I" Next [$0] Iconify -1 + "I" Next [$0] Focus + "I" None [$0] Exec $0 $1 AddToFunc Move-or-Raise "I" Raise + "M" Move + "D" Lower AddToFunc Move-or-Raise2"M" Raise + "M" Move + "D" Lower AddToFunc Maximize-Func "M" Maximize 0 100 + "C" Maximize 0 80 + "D" Maximize 100 100 Screenshot: https://i.imgur.com/AqWyN79.png -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 09:41, David Coppa wrote: > Il mer 20 giu 2018, 16:39 Patrick Harper ha scritto: > > > I beg to differ, on my setup at least, the full GMaps in Chromium runs > > silky smooth as intended. This is a Cayman (radeon) graphics card driving a > > 4K monitor through dual 1920x2160 signals (hooray xrandr). > > > > Interesting! Can you provide more infos about your setup? Exact model names > of your card and your monitor and the xrandr cmdline you're using. > > Thanks a lot, > David
Re: Poor browser performance in OpenBSD
I beg to differ, on my setup at least, the full GMaps in Chromium runs silky smooth as intended. This is a Cayman (radeon) graphics card driving a 4K monitor through dual 1920x2160 signals (hooray xrandr). I've never tried Intel graphics though. -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 05:15, Solene Rapenne wrote: > > Максим writes: > > > Hello. > > I'm using Firefox and Chromium (from packages) to browse the internet on > > OpenBSD 6.3 (amd64). > > The problem is that their performance in OpenBSD is very poor compared to > > other OSes. > > Loading pages is slow, watching online video is possible but the > > responsiveness of the browser becomes awful. > > > > Do I need additional settings to fix this? > > > > In my opinion this is normal on OpenBSD >
Re: Poor browser performance in OpenBSD
It's using the framebuffer driver in EFI mode, so you're getting a resolution native to the monitor but no acceleration. Try making an xorg.conf file in /etc/X11/ with the following contents: Section "Device" Identifier "drm" Driver "intel" EndSection (reboot) -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 01:36, Максим wrote: > cat /var/log/Xorg.0.log > > [17.555] (--) checkDevMem: using aperture driver /dev/xf86 > [17.603] (--) Using wscons driver on /dev/ttyC4 > [17.639] > X.Org X Server 1.19.6 > Release Date: 2017-12-20 > [17.639] X Protocol Version 11, Revision 0 > [17.639] Build Operating System: OpenBSD 6.3 amd64 > [17.639] Current Operating System: OpenBSD ws-it-a13.ancor.ru 6.3 > GENERIC.MP#13 amd64 > [17.639] Build Date: 14 June 2018 05:54:55PM > [17.639] > [17.639] Current version of pixman: 0.34.0 > [17.639] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [17.639] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [17.639] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 19 > 11:12:07 2018 > [17.642] (==) Using system config directory "/usr/X11R6/share/X11/ > xorg.conf.d" > [17.643] (==) No Layout section. Using the first Screen section. > [17.644] (==) No screen section available. Using defaults. > [17.644] (**) |-->Screen "Default Screen Section" (0) > [17.644] (**) | |-->Monitor "" > [17.645] (==) No monitor specified for screen "Default Screen > Section". > Using a default monitor configuration. > [17.645] (==) Automatically adding devices > [17.645] (==) Automatically enabling devices > [17.645] (==) Not automatically adding GPU devices > [17.645] (==) Max clients allowed: 256, resource mask: 0x1f > [17.653] (==) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > [17.653] (==) ModulePath set to "/usr/X11R6/lib/modules" > [17.653] (II) The server relies on wscons to provide the list of > input devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [17.653] (II) Loader magic: 0x1c51c426e000 > [17.653] (II) Module ABI versions: > [17.653] X.Org ANSI C Emulation: 0.4 > [17.654] X.Org Video Driver: 23.0 > [17.654] X.Org XInput driver : 24.1 > [17.654] X.Org Server Extension : 10.0 > [17.654] (--) PCI:*(0:0:2:0) 8086:0152:103c:339b rev 9, Mem @ > 0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64 > [17.655] (II) LoadModule: "glx" > [17.659] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so > [17.672] (II) Module glx: vendor="X.Org Foundation" > [17.672] compiled for 1.19.6, module version = 1.0.0 > [17.672] ABI class: X.Org Server Extension, version 10.0 > [17.673] (==) Matched modesetting as autoconfigured driver 0 > [17.673] (==) Assigned the driver to the xf86ConfigLayout > [17.673] (II) LoadModule: "modesetting" > [17.673] (II) Loading /usr/X11R6/lib/modules/drivers/ > modesetting_drv.so > [17.674] (II) Module modesetting: vendor="X.Org Foundation" > [17.674] compiled for 1.19.6, module version = 1.19.6 > [17.674] Module class: X.Org Video Driver > [17.674] ABI class: X.Org Video Driver, version 23.0 > [17.674] (II) modesetting: Driver for Modesetting Kernel Drivers: > kms > [17.675] (**) modeset(0): claimed PCI slot 0@0:2:0 > [17.675] (II) modeset(0): using default device > [17.676] (II) modeset(0): Creating default Display subsection in > Screen section > "Default Screen Section" for depth/fbbpp 24/32 > [17.676] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 > [17.676] (==) modeset(0): RGB weight 888 > [17.676] (==) modeset(0): Default visual is TrueColor > [17.676] (II) Loading sub module "glamoregl" > [17.676] (II) LoadModule: "glamoregl" > [17.678] (II) Loading /usr/X11R6/lib/modules/libglamoregl.so > [17.692] (II) Module glamoregl: vendor="X.Org Foundation" > [17.692] compiled for 1.19.6, module version = 1.0.0 > [17.692] ABI class: X.Org ANSI C Emulation, ver
Re: Poor browser performance in OpenBSD
Also, in the about:flags page in Chromium, try enabling the 'Override software rendering list' (#ignore-gpu-blacklist) setting. -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 01:28, Patrick Harper wrote: > Post the contents of /var/log/Xorg.0.log > > -- > Patrick Harper > paia...@fastmail.com > > On Wed, 20 Jun 2018, at 00:20, Максим wrote: > > fw_update was among the first commands after the install process :-) > > hardware acceleration definitely works. > > > > -- > > > > > > 20.06.2018, 10:04, "Maurice McCarthy" : > > > Can only suggest reading man intel and/or running > > > $ doas fw_update > > > > > > beyond that you'd need someone more knowledgeable. > > > Good Luck > >
Re: Poor browser performance in OpenBSD
Post the contents of /var/log/Xorg.0.log -- Patrick Harper paia...@fastmail.com On Wed, 20 Jun 2018, at 00:20, Максим wrote: > fw_update was among the first commands after the install process :-) > hardware acceleration definitely works. > > -- > > > 20.06.2018, 10:04, "Maurice McCarthy" : > > Can only suggest reading man intel and/or running > > $ doas fw_update > > > > beyond that you'd need someone more knowledgeable. > > Good Luck >
Re: The wireless card TL-WN725N version 3 works fine
Not to put too finer point on it but the FAQ asks you to send the dmesg output as plain text in the body of an email to @dmesg, with some comments in the subject. External links are not very helpful. -- Patrick Harper paia...@fastmail.com On Fri, 15 Jun 2018, at 07:33, Guillaume DUALÉ wrote: > Hello, > Yes no problem, here is my dmesg : https://pastebin.com/iB4X5T9M > Regards, > Guillaume. > > Le ven. 15 juin 2018 à 15:24, Stephane HUC "PengouinBSD" < > b...@stephane-huc.net> a écrit : > > > Please, add your dmesg as explain into FAQ: > > > > https://www.openbsd.org/faq/faq4.html#SendDmesg > > > > ;) > > > > Le 06/15/18 à 15:12, Guillaume DUALÉ a écrit : > > > Hello, > > > I just bought this card : TP-LINK TL-WN725N(EU) Ver:3.0 > > > And it works fine ! > > > > > > In the man of the used driver «urtwn» : http://man.openbsd.org/urtwn > > only > > > the version 2 is listed. > > > So you can add this new version in the list. > > > > > > If you want I do tests, I can, just ask. > > > > > > Regards, > > > Guillaume. > > > > > > > -- > > ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<< > > > > Stephane HUC as PengouinBSD or CIOTBSD > > b...@stephane-huc.net > > > >
Re: chromium and firefox - myths and facts?
In that case, are the Chromium updates in current worth attempting to backport to stable? Or are the stable builds safer than the backported Firefox builds throughout the six months or so that they remain frozen? -- Patrick Harper paia...@fastmail.com On Mon, 11 Jun 2018, at 06:56, Theo de Raadt wrote: > Marc Espie wrote: > > > Chrome is a relative newcomer to browser land, and it was designed from > > the start from a security point of view, so it got a headstart there. > > In a browser, there are 2 main security components you want: The main > security advantage is privsep. The other is W^X jit. Other security > effects will follow from those design choices, especially if you have > privsep. For instance, the chrome privsep is nicely refined and pledge > enforcements could be added. > > chrome was designed to be privsep. sshd was the first major privsep > program on everyone's machine, and chrome was second. For instance, > smtpd had it designed-in from the start, and it is very strong. > > We have added privsep to software after the fact, but it isn't always a > success. As an example of this, privsep was added to dhclient and > probably isn't as strong. Only because it is difficult pasting the > concept in afterwards. > > > It's been my understanding that firefox is finally catching up. Namely, > > they've put a reasonably secure architecture in place. And they are getting > > rid of their old large extension language to try and use the same > > architecture as chrome. > > It is my understanding that firefox says they are catching but, but all > I see is lipstick on a pig. It now has multiple processes. That does > not mean it has a well-designed privsep model. Landry's attempt to add > pledge to firefox, shows that pretty much all processes need all > pledges. > > From where I stand, I think it fails to be privsep because the various > process initializations still need way too much, and tasks aren't being > done in the right process. I think firefox is still only 2 process > classes, whereas chrome is 6 or 7. > > > The gap is much smaller than it was a year ago. > > I don't think so. > > > In short, I feel that most of chrome's focus is on making things reasonably > > secure (as far as confidentiality and attacks go) so that people trust the > > browser, whereas firefox's focus is waaay more dispersed. > > I doubt firefox will ever focus on security. The security mechanisms we > are talking about require breaking compatibility or performance. This > isn't the stuff one rearranges deck chairs for. > > BTW, the jit in chrome isn't W^X. So chrome is behind in one sense, > because the jit in firefox is W^X [well not truly, it uses two mappings > of the same object, and if the attacker can find the shadow he can play, > but it is still raising the bar] > > I'm replying becuase I think the picture is being painted too rosy. > I think firefox is YEARS behind, unless they change their strategy. >
Re: Beg for Atheros wifi driver
Is this a laptop you're dealing with? Vendor firmwares tend to enforce a whitelist of permitted cards for the internal mini-PCI(e) slot. -- Patrick Harper paia...@fastmail.com On Wed, 23 May 2018, at 13:46, Chris Bennett wrote: > On Mon, Apr 16, 2018 at 07:43:09AM +, Antal Ispanovity wrote: > > By the way, you just need to have a look at this page, click on a driver > > and you can see a list of supported devices: > > https://man.openbsd.org/?query=wireless=1 > > > > This DOES NOT always work. I have bought several supported model numbers > that had been replaced with new chipsets. > I'm having the same problem and I am going to order one online today. > Pretty frustrating buying one after the next only to fail. > > Chris Bennett > > P.S. > I'm installing a snapshot first to see if that solves the problem since > I have one to return to the store with me > >
Re: Plans to port the amdgpu(4) driver? (=to support Radeons made 2014/2015 and after.) Hardware/other donations needed?
I have a FirePro V5900 (Cayman part from the Northern Islands family) which I run with EXA acceleration on 6.2. H264 video with a resolution of 3840x2160 and 25fps play flawlessly with the OpenGL acceleration in mpv (on a WSXGA+ display). Ostensibly this card can drive UHD monitors at their native refresh rate that support the MST mode (two virtual panels at 1920x2160), while its longer brother, the V7900, can do SST mode. -- Patrick Harper paia...@fastmail.com On Sat, 28 Apr 2018, at 11:00, Joe Gidi wrote: > > On Wed, Apr 25, 2018 at 10:49:53AM -0400, Joe Gidi wrote: > >> > >> > On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote: > >> >> drivers/gpu/drm/amd in linux has over 1.5 million lines of code. > >> Which > >> >> is multiple times larger than the complete OpenBSD kernel source... > >> > >> Thanks for this update! > >> > >> Just to clarify, before I spend a bunch of money on new hardware, should > >> I > >> be able to use a Radeon R7 250 to drive a 4k monitor via DisplayPort > >> with > >> this updated driver? > >> > >> Thanks again, > > > > It appears that 'R7 250' can mean either a cape verde or oland radeon > > depending on the model. Both are GCN parts. > > > > 4k 30Hz should be possible with HDMI, 4k 60Hz on HDMI requires HDMI 2.0 > > Both claim support for displayport 1.2 which should be able to do > > 4k 60Hz. HDMI 2.0 seems to only be on later hardware with DCE >= 11 > > carrizo (not carrizo-l which is mullins), polaris etc. > > > > With the low end radeons displayport is sometimes only available on > > oem models of cards sold as options for systems marketed as business > > desktops or workstations. > > > > And as mentioned earlier for acceleration you'll currently have to build > > a different version of Mesa than what OpenBSD releases/snapshots ship > > with. > > Hi Jonathan, > > Thanks for the detailed answer! > > As best I can tell from wading through the mess of marketing names and > specifications, accelerated 4k video is currently not an option with > Radeon cards; the older cards don't support high-enough resolutions, and > the newer ones don't have acceleration support yet due to the Mesa > problem. Looks like I might need to buy an Intel machine or wait for the > Mesa issues to get resolved. > > Thanks again, > Joe > > > -- > > Joe Gidi > j...@entropicblur.com > > "You cannot buy skill." -- Ross Seyfried >
Re: Plans to port the amdgpu(4) driver? (=to support Radeons made 2014/2015 and after.) Hardware/other donations needed?
I have a response from an anon poster on the Linux sub on Reddit that may or may not be well informed (take it with a pinch of salt), but their posts were ostensibly more popular than my queries about amdgpu's mooted bloat, is there anyone here who can make sense of their points as to their legitimacy? >That's nothing. First of all, majority of it is in header files as >initialization data and various tables, and the second thing is that > it's >more compartmentalized as compared to radeon (read: there is a lot of >duplication). > >Memory wise, the cost of the 'bloat' is laughable. And code path wise it's >quite comparable to radeon. You don't execute every > single byte of code >just because it's there. You hit some code paths often, some rarely, and some >never. Critical paths are the > ones you want to optimize the hell out of. > >Code bloat is a different thing. Usually it refers to layers upon layers of >abstraction and crufty interfaces that no longer really > fit, but are kept >for various compatibility/legacy reasons. And even then, it doesn't >necessarily translate to performance > penalties. Usually bloat is >something that hits developers rather than users, since large messy codebase >is difficult to> maintain. > >P.S. There is nothing in modern AMD GPUs that makes them unsupportable by >older radeon driver per se, specs are > completely open, >nothing prevents you from coming up with your own 'slim' driver. It's just >that it has been decided that, > moving on, new hardware support will be >added to amdgpu only. The size of amdgpu results from deliberate architectural >> approaches. > >First rule of any optimization every dev should know: profile, profile, >profile! Without careful measurements you cannot make > proper assessment of >performance, even very experienced devs get bit by that when making casual >assessments. > >If you feel you can trim it down, you're welcome to remove code you deem >unnecessary and submit patches to the tree. Those of us who have a bloaty mainstream browser with Javascript enabled can read the whole exchange at https://www.reddit.com/r/Amd/comments/7u54d3/lisa_su_we_are_ramping_production_of_gpus/dtkcysq/?context=3 -- Patrick Harper paia...@fastmail.com
Re: Regarding latest errata
I agree. Your initial response was all I needed, I thought I needed more because I'm an absolutist. -- Patrick Harper paia...@fastmail.com On Tue, 17 Apr 2018, at 10:28, Theo de Raadt wrote: > What a futile and pointless discussion. > > > Assuming that is the case, was it 6.3 or 6.1 that was not 'active' > > from the 2nd to the 15th? Conveniently the original 6.3 release dates > > are now censored on the website, but if it had been built for the > > projected date then it would not have needed the 14th patches. > > > > > > -- > > Patrick Harper > > paia...@fastmail.com > > > > On Tue, 17 Apr 2018, at 08:57, Theo de Raadt wrote: > > > > What changed was that there was a period after 6.3 was pushed out the > > > > door (2-15 April) in which there were effectively three active > > > > releases and the project felt obliged to support 6.1 until 6.3's > > > > projected release date. My previous post attempted to review a > > > > possible workaround, though I suspect this sort of anomaly might not > > > > be practically avoidable. > > > > > > You are making stuff up. > > > > >
Re: Regarding latest errata
Assuming that is the case, was it 6.3 or 6.1 that was not 'active' from the 2nd to the 15th? Conveniently the original 6.3 release dates are now censored on the website, but if it had been built for the projected date then it would not have needed the 14th patches. -- Patrick Harper paia...@fastmail.com On Tue, 17 Apr 2018, at 08:57, Theo de Raadt wrote: > > What changed was that there was a period after 6.3 was pushed out the > > door (2-15 April) in which there were effectively three active > > releases and the project felt obliged to support 6.1 until 6.3's > > projected release date. My previous post attempted to review a > > possible workaround, though I suspect this sort of anomaly might not > > be practically avoidable. > > You are making stuff up. >
Re: Regarding latest errata
What changed was that there was a period after 6.3 was pushed out the door (2-15 April) in which there were effectively three active releases and the project felt obliged to support 6.1 until 6.3's projected release date. My previous post attempted to review a possible workaround, though I suspect this sort of anomaly might not be practically avoidable. (Theo received this twice, sorry) -- Patrick Harper paia...@fastmail.com On Tue, 17 Apr 2018, at 08:19, Theo de Raadt wrote: > Huh? We've told everyone 2 releases maintained with errata/syspatches, > 6 months apart, only. Nothing changed here. We don't need to > change a single word about EOL. It is exactly the same as before. > > > The best solution I can think of is planning, announcing and > > implementing oldstable EOLs in advance, but I'm not sure this would > > kill enough time in building patches to be worth a process change, and > > users would have to trade patches for contingency. Make of this > > whatever you will, I don't know what is more important. > > > > -- > > Patrick Harper > > paia...@fastmail.com > > > > On Sun, 15 Apr 2018, at 12:02, Theo de Raadt wrote: > > > Patrick Harper <paia...@fastmail.com> wrote: > > > > > > > Unless I am mistaken, the errata posted on the 14th April is the first > > > > that has been applied to more than two releases, implying that > > > > 6.1-stable is still supported. Does this signify a change to the > > > > lifecycle process? > > > > > > No it does not indicate that. > > > > > > Official release date of 6.3 is April 15. Yes, the release went out > > > the door early, but the *official* date is April 15. > > > > > > Therefore we made it for 6.1 also, since 6.1 people may still be > > > running on the day before the *official* release day. > > > > > > We only support 2 active releases. Pulling this trick out of our hat > > > was extra effort, and hopefully won't be repeated again. Thanks to > > > robert and tb. > > > > > >
Re: Regarding latest errata
The best solution I can think of is planning, announcing and implementing oldstable EOLs in advance, but I'm not sure this would kill enough time in building patches to be worth a process change, and users would have to trade patches for contingency. Make of this whatever you will, I don't know what is more important. -- Patrick Harper paia...@fastmail.com On Sun, 15 Apr 2018, at 12:02, Theo de Raadt wrote: > Patrick Harper <paia...@fastmail.com> wrote: > > > Unless I am mistaken, the errata posted on the 14th April is the first > > that has been applied to more than two releases, implying that > > 6.1-stable is still supported. Does this signify a change to the > > lifecycle process? > > No it does not indicate that. > > Official release date of 6.3 is April 15. Yes, the release went out > the door early, but the *official* date is April 15. > > Therefore we made it for 6.1 also, since 6.1 people may still be > running on the day before the *official* release day. > > We only support 2 active releases. Pulling this trick out of our hat > was extra effort, and hopefully won't be repeated again. Thanks to > robert and tb. >
Regarding latest errata
Hi All, Unless I am mistaken, the errata posted on the 14th April is the first that has been applied to more than two releases, implying that 6.1-stable is still supported. Does this signify a change to the lifecycle process? Regards, -- Patrick Harper paia...@fastmail.com
Re: Why are so many people running and writing about current snapshots
Distros like RHEL have longer release cycles because the industry they service demands them. The fact that the kernel project maintains releases as far back as 2012 only re-enforces the business. There's no need for 'puffangelism' on this subject as OBSD is by no means alone in six-month release cycles. Ubuntu is the obvious one. -- Patrick Harper paia...@fastmail.com On Tue, 27 Mar 2018, at 07:09, Consus wrote: > On 14:46 Tue 27 Mar, Niels Kobschaetzki wrote: > > CentOS 5 is EOL since March 31st 2017 ;) > > CentOS 6 should be on extended support now which is going EOL in > > November 2020. > > Yep. And Centos7 will be around until 2024. So 4/5 of Linux distros in > production (e.g. Alpine is different in this regard) are affected by > this awful megafreeze strategy when you're stuck with an old kernel and > tools (not everything gets backported) for years. > > That's why I love OpenBSD's 6 month release cycles so much :3 >
Re: Has anyone got OpenBSD Arm to run on the Marvel Espresso Bin?
Armada 3700LP chipset not supported at present. -- Patrick Harper paia...@fastmail.com On Sun, 25 Mar 2018, at 22:11, Z Ero wrote: > If yes is the on board ethernet switch supported? What wifi cards are > supported in the miniPCIe slot? >
Can't build new base system on HP 2133
73a150c.a) swap on wd0b dump on wd0b umass1 at uhub0 port 6 configuration 1 interface 0 "Generic Mass Storage Device" rev 2.00/1.00 addr 7 umass1: using SCSI over Bulk-Only scsibus4 at umass1: 2 targets, initiator 0 sd0 at scsibus4 targ 1 lun 0: <Multi, Flash Reader, 1.00> SCSI0 0/direct removable serial.058f6366058F0OB1 sd0 detached scsibus4 detached umass1 detached umass1 at uhub0 port 6 configuration 1 interface 0 "Generic Mass Storage Device" rev 2.00/1.00 addr 7 umass1: using SCSI over Bulk-Only scsibus4 at umass1: 2 targets, initiator 0 sd0 at scsibus4 targ 1 lun 0: <Multi, Flash Reader, 1.00> SCSI0 0/direct removable serial.058f6366058F0OB1 sd0: 7695MB, 512 bytes/sector, 15759360 sectors hw.sensors.cpu0.temp0=55.00 degC hw.sensors.acpitz0.temp0=57.00 degC (zone temperature) hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpibtn0.indicator0=On (lid open) hw.sensors.lisa0.raw0=3 (OUT_X) hw.sensors.lisa0.raw1=1 (OUT_Y) hw.sensors.lisa0.raw2=53 (OUT_Z) Regards, -- Patrick Harper paia...@fastmail.com
Re: Using OpenBSD on a thinkpad?
As long as your Libreboot firmware uses SeaBIOS and not something exotic, you shouldn't have any problems. -- Patrick Harper paia...@fastmail.com On Mon, 19 Feb 2018, at 01:00, crimeangot...@nigge.rs wrote: > > Hey everyone, I am pretty stupid when it comes to less user friendly > operating systems. I currently use slackware/windows and am thinking of > using OpenBSD on either my thinkpad e420 or my libreboot t400. Are > either supported(or at least possible to install on?) I’m sorry if this > question has already been asked but I can’t really find any answers and > the mailing list archive is barren as well. > Thanks!
