Re: Problem with WireGuard on OpenBSD 7.3
On Sat, 6 May 2023 02:18:30 +0200 Odd Martin Baanrud wrote: > Hello Stuart, > > Thanks for a detailed and good explenation! > > I choosed the WireGuard-tools solution, because I understood how it works, > and it is easy to configure. > I*ve read a bit in the wg(4) manual, and I get confused of how things > actually works. > Is it possible to use wireguard-tools*s private/public key e.g? > If not, is the actual configuration using the included tools easy to do? > > I*m blind, so reading lots of documentation, when not knowing what to look > for, can be pritty time consuming. > So, if it is an easy way to set up a wireguard-tools style vpn using tools > from the base system, please let me know. > > Regarding pf, thanks for good advice regarding how to use NAT rules. > > Regards, Martin. Hello Martin. I just recently started using WireGuard, as a client only, using commercial VPN service. I did not have to use wireguard-tools. In addition to the manual pages for wireguard and rdomain, I also consulted several online guides that helped clarify how everything should work (DNS is the tricky part). 1. Solene Rapenne - "Full WireGuard setup with OpenBSD" Solene explains how to setup both wireguard server and client on OpenBSD without using wireguard-tools. She uses openssl to generate private keys. Note: page has one ASCII network diagram. https://dataswamp.org/~solene/2021-10-09-openbsd-wireguard-exit.html 2. Matthieu Herrb - "Setting up a WireGuard client with routing domains on OpenBSD". Matthieu explains step-by-step how to setup OpenBSD as wireguard client for 3rd party VPN. He uses wireguard-tools, but only to generate the private key initially. Note: page includes one long output of ps command. https://md.laas.fr/s/NMc3qt5PQ Since both of the above guides use rdomains for their setup, I found this writeup about rdomains and rtables useful: 3. Joel Knight - "Virtualizing the OpenBSD Routing Table" Note: page has four images of network diagramms. https://www.packetmischief.ca/2011/09/20/virtualizing-the-openbsd-routing-table/ It is a lot of reading, and I apologize for that. I can see, but it still took me couple days to figure out how to get just the client part working right, and you are trying to do both server and client at once. I hope you succeed. -- Andre
Re: sndio and bit perfect playback
On Tue, 25 Oct 2022 16:44:59 +0200 Christian Weisgerber wrote: > Andre Smagin: > > > There is possibly one more use case for "bit-perfect". I have a small > > collection of surround sound (5.1, 4.1, quad, etc) recordings extracted > > from various DVDs, SACDs, and other sources. > > Yup. > I even have a commercially released DTS-CD lying around somewhere, > which is basically an ordinary CD except that the audio is encoded > as DTS and not PCM. > > > My desktop is connected to a receiver via optical SPDIF cable. To get > > the surround sound, I use mpd with 'device "snd/0"' option and Ario to > > control the mpd daemon. > > I'm curious, what's the actual audio hardware? azalia(4) or uaudio(4)? It is azalia, built-in on the motherboard (dmesg at the end). > > Bit depth does not seem to matter. I don't care about "bit-perfect", but > > only about sending the dts stream to the receiver as-is, which works. > > S/PDIF actually has a native depth of 20 bits per sample. There > are also 4 spare bits in the frame, which can optionally be used > to transport 24 bits. If an audio source provides only 16 bits per > sample, those are fit into the 20 bit frame with the remaining bits > unused. DTS and AC3 encodings for S/PDIF only use 16 bits. Ah, thank you for the explanation! I tried reading the DTS specification once, but it is way over my head. -- Andre Smagin OpenBSD 7.2-current (GENERIC.MP) #778: Mon Oct 10 22:34:04 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68596912128 (65419MB) avail mem = 66500554752 (63419MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (59 entries) bios0: vendor American Megatrends International, LLC. version "A.I0" date 08/10/2022 bios0: Micro-Star International Co., Ltd. MS-7C37 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT MCFG HPET SSDT IVRS FPDT 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 5950X 16-Core Processor, 3400.06 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 2 (application processor) cpu1: AMD Ryzen 9 5950X 16-Core Processor, 3400.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 4 (application processor) cpu2: AMD Ryzen 9 5950X 16-Core Processor, 3400.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
Re: sndio and bit perfect playback
On Thu, 13 Oct 2022 22:14:33 +0200 Alexandre Ratchov wrote: > On Thu, Oct 13, 2022 at 03:11:50AM +, s...@skolma.com wrote: > > in summary, audio works.. just not bit-perfectly :) > > does anyone know if SNDIO supports such mode ? and how i might configure it. > > bit-perfect is practical for one thing only: avoid questionings about > whether the processing adds audible noise & distortion. I've tryed > various hacks, including bypassing sndiod and neither was very > practical. > > IMHO, the sndiod resampler covers 99% of the cases. To handle the > remaining 1%, I just resample the files off-line. audio/sox is > excellent for that. > > So, I'd suggest you to add "-e s24" to sndiod_flags and resample > off-line when needed. > > HTH There is possibly one more use case for "bit-perfect". I have a small collection of surround sound (5.1, 4.1, quad, etc) recordings extracted from various DVDs, SACDs, and other sources. They are encoded in DTS and Dolby Digital formats, as plain WAV files, and "compressed" to flac format to prevent "smart" applications, such as ffmpeg, mpd, etc. from trying to decode them and convert to stereo. My desktop is connected to a receiver via optical SPDIF cable. To get the surround sound, I use mpd with 'device "snd/0"' option and Ario to control the mpd daemon. mpd decodes the top layer (flac), but stops there and sends DTS-wav to the sndiod without mangling it further. However, if sndiod's sample rate does not match that of the recording, it resamples the stream, which ruins the DTS and results in white noise. I found out that I have to restart sndiod with either 'sndiod_flags="-m play -r 44100"' or 'sndiod_flags="-m play -r 48000"' flags in /etc/rc.conf.local depending on the files I am playing, and then it gets to the receiver without issues. I have each music directory annotated with the sample rate used, like so: HAMLET: /storage $ ls music/dts/Pink\ Floyd/ (1970) Atom Heart Mother (Quadrophonic Vinyl Conversion) (Dolby Digital Quad 16-48) (1973) Dark Side of the Moon (Alan Parson's Mix) (DVD-Audio) (DTS 4.1 24-48) (1971) Echoes (Original 4.0 Quad Mix) (From Pink Floyd the Early Years 1965-1972, Volume 5) (DTS Quad 16-48) (1973) Dark Side of the Moon (Analogue Transfer From SACD) (DTS 5.1 16-44.1) (1971) Meddle (From Pink Floyd the Early Years 1965-1972, Volume 5) (DTS 5.1 16-48) (1994) The Division Bell (2014, Warner Music Group, 20th Anniversary Edition) (DTS 5.1 16-48) Live: (1974) Live at Pompeii (DTS Quad 24-48) For '16-48' and '24-48' (bit depth-samplerate), I start sndiod with sndiod_flags="-m play -r 48000" for '16-44.1', I restart sndiod with sndiod_flags="-m play -r 44100" Bit depth does not seem to matter. I don't care about "bit-perfect", but only about sending the dts stream to the receiver as-is, which works. -- Andre
Re: New desktop CPU/chipset recommendation
On Sun, 13 Feb 2022 21:46:30 -0700 Thomas Frohwein wrote: > On Thu, 3 Feb 2022 19:16:55 -0500 > Andre Smagin wrote: > > ... > > Ryzen 9 5950x on x570 chipset motherboard, should last ten years at > > least. Everything "just works" - NVMe hard drives, SPDIF audio, video, > > etc. > > Does the audio work? No audio hangs/wedging anymore on more than just > a few minutes of usage? I have a machine like this, too, but audio would > hang with MSI on like previous Ryzen generations. Unlike previous Ryzen > generations, patching to switch to legacy interrupts didn't work. That > was about 1.5 years ago; it currently serves as a Windows box ... > > It would be good to know if that issue went away... I wouldn't mind > putting a better OS on my machine again *cough*. Thomas, I play music all day long on the desktop on weekends, going out via SPDIF (optic fiber) to a receiver. I have not tried direct speakers or headphones. The only change to configuration I made was setting outputs.mode=digital in /etc/mixerctl.conf I play audio with mpd (local network files and internet streams), and sometimes audacious and vlc for local files, and web audio with chrome. Had couple strange lock-ups when streaming web-radio with mpd. In fact, one happened just now - internet radio stream via mpd/Ario started stattering and stopped as I was typing this email - restarting sndiod and mpd did not help, had to reboot. So, overall, little bit less reliable than my old pre-Ryzen desktop, but not too bad - does not happen very often, may be once a week. Not sure how to troubleshoot it. -- Andre
Re: New desktop CPU/chipset recommendation
On Sun, 13 Feb 2022 20:55:26 +0200 Mihai Popescu wrote: > > ... Ryzen 9 5950x on x570 chipset motherboard ... > > Can you post the output of > sysctl | grep hw. > please? Here, with smt disabled and smt enabled: HAMLET: /home/andre $ sysctl | grep hw hw.machine=amd64 hw.model=AMD Ryzen 9 5950X 16-Core Processor hw.ncpu=32 hw.byteorder=1234 hw.pagesize=4096 hw.disknames=sd0:,sd1:2c4f0a976c44c833,cd0: hw.diskcount=3 hw.sensors.ksmn0.temp0=36.62 degC hw.cpuspeed=3400 hw.setperf=100 hw.vendor=Micro-Star International Co., Ltd. hw.product=MS-7C37 hw.version=2.0 hw.uuid=c9bca978-eca9-1a51-aece-2cf05d9a5218 hw.physmem=68596871168 hw.usermem=68596854784 hw.ncpufound=32 hw.allowpowerdown=1 hw.perfpolicy=auto hw.smt=0 hw.ncpuonline=16 hw.power=1 HAMLET: /home/andre $ doas sysctl hw.smt=1 hw.smt: 0 -> 1 HAMLET: /home/andre $ sysctl | grep hw hw.machine=amd64 hw.model=AMD Ryzen 9 5950X 16-Core Processor hw.ncpu=32 hw.byteorder=1234 hw.pagesize=4096 hw.disknames=sd0:,sd1:2c4f0a976c44c833,cd0: hw.diskcount=3 hw.sensors.ksmn0.temp0=36.50 degC hw.cpuspeed=3400 hw.setperf=100 hw.vendor=Micro-Star International Co., Ltd. hw.product=MS-7C37 hw.version=2.0 hw.uuid=c9bca978-eca9-1a51-aece-2cf05d9a5218 hw.physmem=68596871168 hw.usermem=68596854784 hw.ncpufound=32 hw.allowpowerdown=1 hw.perfpolicy=auto hw.smt=1 hw.ncpuonline=32 hw.power=1
Re: New desktop CPU/chipset recommendation
On Mon, 20 Sep 2021 14:56:31 -0400 Andre Smagin wrote: > I am looking for a hardware advice. > I don't upgrade my desktop very often - last one was about ten > years ago (AMD FX-8350 CPU), which I recently made my home server > running -current, no issues. Now I am looking for a new desktop that > will last another ten years, hence the question: if I buy the latest > available AMD chipset (X570 I think) and Ryzen 9 CPU - are there any > current issues with using it for OpenBSD desktop? I would like to > overkill it with the choice of hardware now, so I don't have to worry > about it for a while. Replying to my own thread from months ago. Took some time to get this done, buying one part per paycheck, but I have a new desktop now. Ryzen 9 5950x on x570 chipset motherboard, should last ten years at least. Everything "just works" - NVMe hard drives, SPDIF audio, video, etc. Big thanks to OpenBSD developers! No issues to complain about, fresh install, copied my configuration files from old desktop, was up and running in 30 minutes. Day 3 to configure Windows 11 on a second hard drive (to run 3d CAD software mostly) and now I have to reinstall - broke something completely while trying to set it up to be usable... Dmesg: OpenBSD 7.0-current (GENERIC.MP) #303: Wed Feb 2 13:26:47 MST 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68596871168 (65419MB) avail mem = 66500714496 (63420MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (60 entries) bios0: vendor American Megatrends International, LLC. version "A.F0" date 12/16/2021 bios0: Micro-Star International Co., Ltd. MS-7C37 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT MCFG HPET SSDT IVRS TPM2 PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT FPDT 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 5950X 16-Core Processor, 3400.48 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 I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: 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 2 (application processor) cpu1: AMD Ryzen 9 5950X 16-Core Processor, 3400.02 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 I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 5950X 16-Core Processor, 3400.02 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 I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 6
Re: Should 80MB of RAM be enough for kernel relinking on i386?
On Wed, 22 Sep 2021 17:27:30 +0100
"Patrick Harper" wrote:
> 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
Hello.
I have Soekris net4801 gateway/firewall and it only has 128Mb of RAM.
I usually upgrade to -current by putting the CF card into a different
machine, since writing to CF card is slow on Soekris, but tonight I
upgraded to -current using the box itself and timed how long it took to
relink the kernel - 25 minutes.
It has 256Mb of swap. Eh, 259.9M apparently.
After-reboot relinking is currently disabled until I figure out
what to put in the new bsd.re-config to change flags for
wd to 0x0ff0 automatically, no luck yet.
Soekris dmesg:
OpenBSD 7.0 (GENERIC) #203: Wed Sep 22 19:24:38 MDT 2021
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 133709824 (127MB)
avail mem = 114921472 (109MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 20/80/03, BIOS32 rev. 0 @ 0xf7840
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0x9000
cpu0 at mainbus0: (uniprocessor)
cpu0: Geode(TM) Integrated Processor by National Semi ("Geode by NSC"
586-class) 267 MHz, 05-04-00
cpu0: FPU,TSC,MSR,CX8,CMOV,MMX
cpu0: TSC disabled
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Cyrix GXm PCI" rev 0x00
sis0 at pci0 dev 6 function 0 "NS DP83815" rev 0x00, DP83816A: irq 10, address
00:00:24:c3:54:68
nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1
sis1 at pci0 dev 7 function 0 "NS DP83815" rev 0x00, DP83816A: irq 10, address
00:00:24:c3:54:69
nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1
sis2 at pci0 dev 8 function 0 "NS DP83815" rev 0x00, DP83816A: irq 10, address
00:00:24:c3:54:6a
nsphyter2 at sis2 phy 0: DP83815 10/100 PHY, rev. 1
ral0 at pci0 dev 10 function 0 "Ralink RT2860" rev 0x00: irq 11, address
00:1d:6a:0e:80:cd
ral0: MAC/BBP RT2860 (rev 0x0101), RF RT2820 (MIMO 2T3R)
ral1 at pci0 dev 14 function 0 "Ralink RT2560" rev 0x01: irq 5, address
00:13:d3:00:9f:7a
ral1: MAC/BBP RT2560 (rev 0x04), RF RT2525
gscpcib0 at pci0 dev 18 function 0 "NS SC1100 ISA" rev 0x00
gpio0 at gscpcib0: 64 pins
"NS SC1100 SMI" rev 0x00 at pci0 dev 18 function 1 not configured
pciide0 at pci0 dev 18 function 2 "NS SCx200 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA48, 3811MB, 7806960 sectors
wd0(pciide0:0:0): using PIO mode 4
geodesc0 at pci0 dev 18 function 5 "NS SC1100 X-Bus" rev 0x00: iid 6 revision 3
wdstatus 0
ohci0 at pci0 dev 19 function 0 "Compaq USB OpenHost" rev 0x08: irq 9, version
1.0, legacy support
isa0 at gscpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
gscsio0 at isa0 port 0x15c/2: SC1100 SIO rev 1:
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Compaq OHCI root hub" rev 1.00/1.00
addr 1
dt: 445 probes
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (1f081011692bae0c.a) swap on wd0b dump on wd0b
Re: New desktop CPU/chipset recommendation
On Mon, 20 Sep 2021 18:59:11 -0400 Daniel Wilkins wrote: > On Mon, Sep 20, 2021 at 02:56:31PM -0400, Andre Smagin wrote: > > Good day. > > > > I am looking for a hardware advice. > > I don't upgrade my desktop very often - last one was about ten > > years ago (AMD FX-8350 CPU), which I recently made my home server > > running -current, no issues. Now I am looking for a new desktop that > > will last another ten years, hence the question: if I buy the latest > > available AMD chipset (X570 I think) and Ryzen 9 CPU - are there any > > current issues with using it for OpenBSD desktop? I would like to > > overkill it with the choice of hardware now, so I don't have to worry > > about it for a while. > > > > I am ten years out of touch with hardware development progress, so will > > appreciate any input you may have. > > > > -- > > Andre > > > You got me curious, so I went ahead and installed OpenBSD on the desktop > I rebuilt this year. > I've got a Ryzen R9 3900X with an MSI MAG B550 TOMAHAWK for the motherboard, > and an R9 380 for the graphics card. > > Works totally fine from my initial impressions. Sound works, USB works, > plays full HD videos fine over DP, drives the 1440p display with no issues, > etc. > > The only thing "wrong" is that I don't think Audio-over-HDMI works. > > Hope this might help a bit, > Danny > Thank you very much for the test! I feel more comfortable now, will probably get the B550 chipset motherboard and CPU like yours. And if there are issues with sound as others mentioned, I can always use an external USB card, have one somewhere I think. Only need SPDIF output going to a receiver on my desk. Thank you all for the replies! -- Andre
New desktop CPU/chipset recommendation
Good day. I am looking for a hardware advice. I don't upgrade my desktop very often - last one was about ten years ago (AMD FX-8350 CPU), which I recently made my home server running -current, no issues. Now I am looking for a new desktop that will last another ten years, hence the question: if I buy the latest available AMD chipset (X570 I think) and Ryzen 9 CPU - are there any current issues with using it for OpenBSD desktop? I would like to overkill it with the choice of hardware now, so I don't have to worry about it for a while. I am ten years out of touch with hardware development progress, so will appreciate any input you may have. -- Andre
"not MAP_STACK" message in dmesg / system message buffer
Hello.
While prototyping something in C, I made a mistake with
pre-processor macros, which I narrowed down to this:
int
main()
{
char *test[10][2097152] = { { 0 } };
}
Running it results in
$ ./a.out
Segmentation fault (core dumped)
and it also logs it in dmesg as
Feb 25 20:05:49 hamlet /bsd: [a.out]52048/372328 sp=7f7ff5fd4150 inside
7f7fff7d5000-7f7d5000: not MAP_STACK
Feb 25 20:06:49 hamlet /bsd: [a.out]94530/186499 sp=7f7ff5fe58c0 inside
7f7fff7e7000-7f7e6000: not MAP_STACK
Feb 25 20:07:09 hamlet /bsd: [a.out]9523/344960 sp=7f7ff5fd9fd0 inside
7f7fff7db000-7f7db000: not MAP_STACK
I have not seen a segfaulting program being logged in system
message buffer before. Is it expected behaviour?
Just curious, the message was a bit confusing.
The system is amd64-current.
--
Andre
Re: A stupid question, re: xargs(1)
On Fri, 13 Oct 2017 18:03:59 -0400 Raul Miller wrote: > "Because then you don't need xargs, normal tooling seperates each line > into a seperate argv entry regardless of other spacing." > > If there's some existing way (portable or not) to build this kind of > argv in a shell script - using newline separation and nothing else - I > would really appreciate another hint. I wish you would have given an exact problem you are having difficulties with... I've been using ls | while read i; do echo "$i"; done or cat /tmp/tmp_file | while read i; do echo "$i"; done type of constructs for years and have never even needed xargs... -- Andre
Re: GUI desktop autologin options
On Tue, 18 Apr 2017 20:44:05 -0700 "Sha'ul" wrote: > I'm trying to figure how setup an auto login from boot to some kind of GUI > desktop interface. What are my options? I'm not interested in Gnome 3, but > I will use anything else like Lumina, KDE, XFCE, etc. as long as it can > load straight into desktop environment when I turn on computer. Which > ones, besides Gnome 3, support autologin? Just add to /etc/X11/xenodm/xenodm-config DisplayManager.*.autoLogin: your_user_name enable xenodm in /etc/rc.conf.local with xenodm_flags= and add the startup command for your window manager to ~/.xsession If I remember correctly, it's something like xfce4-session || startkde || gnome-session || xterm to start those DEs. Other window managers are more straightforward and usually use their name as the main executable.
OpenBSD on a Chuwi hi12 tablet - dmesg
Hello. Occasionally it is asked if OpenBSD can run on a tablet, so I wanted to share a dmesg showing what it looks like on one. It is a dual-boot (Windows 10 and Android), Chinese designed and made Chuwi Hi12 tablet with attachable keyboard: http://en.chuwi.com/product/items/Chuwi-Hi12.html (Very affordable tablet considering the screen size and resolution, pretty happy with it, even though it has some rough edges and bugs.) I installed OpenBSD on a usb flash drive and can boot it from there. It is mostly a "not configured" galore, no X, net, or audio, but dockable keyboard works. dmesg, usbdevs, and pcidump: OpenBSD 6.0-beta (GENERIC.MP) #2165: Thu Jun 2 08:37:59 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 3f real mem = 4179439616 (3985MB) avail mem = 4048146432 (3860MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7b76e000 (51 entries) bios0: vendor American Megatrends Inc. version "5.11" date 04/28/2016 bios0: Default string Default string acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MSDM MCFG SSDT SSDT SSDT UEFI SSDT HPET SSDT SSDT SSDT LPIT BCFG PRAM CSRT BCFG OEM0 OEM1 PIDV RSCI WDAT acpi0: wakeup devices XHC1(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz, 1440.29 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 79MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz, 1439.95 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz, 1439.95 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz, 1439.95 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpicpu0 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu1 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu2 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu3 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: ID3C, resource for ISP3 acpipwrres1 at acpi0: WWPR, resource for HS03, MDM1 acpipwrres2 at acpi0: WWPR, resource for HS13, MDM1 acpipwrres3 at acpi0: WWPR, resource for SSC1, MDM3 acpipwrres4 at acpi0: WWPR, resource for SSCW, MDM3 acpipwrres5 at acpi0: WWPR, resource for HSC1, MDM2 acpipwrres6 at acpi0: WWPR, resource for HSC3, MDM4 acpipwrres7 at acpi0: CLK2, resource for CAM7, CAM3 acpipwrres8 at acpi0: CLK4, resource for CAM4, CAM8 acpipwrres9 at acpi0: CLK3, resource for RTEK, ESSX, RTK1 acpipwrres10 at acpi0: CLK4 acpipwrres11 at acpi0: CLK2 acpipwrres12 at acpi0: CLK1 acpipwrres13 at acpi0: CLK0 acpipwrres14 at acpi0: CLK1 acpipwrres15 at acpi0: CLK5 acpipwrres16 at acpi0: USBC, resource for XHC1, OTG1 acpipwrres17 at acpi0: P28X acpipwrres18 at acpi0: P18X acpipwrres19 at acpi0: P12X acpipwrres20 at
Re: dpb build box performance suggestions.
On Wed, 16 Dec 2015 23:15:29 + Tati Chevron wrote: > Really, have a look at the dependencies for ImageMagick, and ask yourself > who really uses djvu, for example. Removing it and ghostscript reduces > the dependencies from: Plenty of people read books in djvu format and use ImageMagick to work with it. There are many old and valuable, but long out of print books that were scanned and encoded to djvu format a decade or more ago. Converting such books to pdf format using open source tools is usually difficult without drastically reducing the quality or increasing the file size two- or threefold. And when you do decide to convert, you need the ImageMagick or similar software. I am grateful to OpenBSD developers and porters for supporting various seemingly obscure dependencies and software packages, even though they may seem to be useless to the majority of the users. -- Andre
Re: USB external floppy
On Sun, 13 Dec 2015 18:11:07 -0500 "Bryan C. Everly" wrote: > Hi, > > I'm wanting to create a boot floppy for a Vaxstation. Could someone > recommend a USB floppy that I could plug into my amd64 laptop that would > allow me to create a boot floppy for a VAX? > > Thanks, > Bryan Hi. I don't know anything about VAXes, but I do use USB floppy drive often. The drive I have is a bit flaky, equally so under OpenBSD and Windows, and needs the disk to be ejected and reinserted, or the drive unplugged and reconnected sometimes, but, generally speaking, it works. A bit slow under OpenBSD when mounting and using FAT disks. Sold by Amazon as "Nippon Labs" USB floppy drive: umass0 at uhub7 port 1 configuration 1 interface 0 "TEAC TEAC FD-05PUB" rev 2.00/0.00 addr 2 umass0: using UFI over CBI with CCI scsibus2 at umass0: 2 targets, initiator 0 sd3 at scsibus2 targ 1 lun 0: ATAPI 0/direct removable Just tried dd'ing the vax image onto a disk using that drive: $ time sudo dd if=/tmp/floppy58.fs of=/dev/rsd3c bs=1m 1+1 records in 1+1 records out 1474560 bytes transferred in 51.998 secs (28358 bytes/sec) 0m53.58s real 0m00.00s user 0m00.01s system -- Andre
