Content AWOL in Musescore 3.5.0 left side palette.
Can anyone else confirm that there is no content in the Musescore 3.5.0 left hand palette? System info: OS: OpenBSD 7.2, Arch.: x86_64, MuseScore version (64-bit): 3.5.0, revision: github-musescore-musescore-43c5553 Any idea how to get some of the items (as per default) to display that can be found in the master palette?
Re: Script launcher and a suite of basic scripts for music production?
On 1/18/23 18:35, Luke A. Call wrote: On 2023-01-18 16:51:28+0100, Brian Durant wrote: On 1/18/23 11:46, Abhishek Chakravarti wrote: Brian Durant writes: The only disadvantage that I can see at this point, is that what I am describing would require a number of open terminals on the desktop, which can be confusing to sort through, particularly during a live performance. Although not a direct answer to your question, perhaps tmux(1) might be helpful here? You could have one tmux session window split into several panes. Cycling through the panes is quite simple with PREFIX + o (the default PREFIX being CTRL+b; in my case it's mapped to CTRL+o Thanks for that. I haven't played around with tmux for ages, but you are correct that could potentially help with terminal clutter. Below are a few [] FWIW I have my tmux set up to use Alt+# (alt+1, alt+2...) key combinations to switch among tmux panes more easily under X than using Ctrl+b every time, which might be helpful if efficiency is important. It is also easier for me to put in muscle memory. I can provide details off-list if desired. Thank you for that generous offer. However, before we go there, I think that there is a need to be more specific (to the extent that I can) at this point, regarding my use case scenario. This can be divided between audio (baritone saxophone, bass and singing) and MIDI (a class compliant launchpad type controller and a class compliant MIDI keyboard). midish looks like a very strong contender, but there are two issues that I am unclear about: 1) Can Fluidsynth instruments be changed on the fly when using midish? 2) Can MIDI events be used to trigger sndio and ffmpeg actions on the system? Here I am thinking of the possibility of using my controller pad as an alternative to a script launcher. The audio side is in many ways more clear cut. I need to be able to record saxophone, voice and bass (I am unfortunately limited to two of these at a time with my current hardware.). The input through the sound card would need to be monitored (when live) and be recorded to file for use as loops with basic sound effects (ffmpeg?). Sooo the big question with relevance to tmux, is how many terminal instances do I need for this scenario? I know my instruments, but as stated, I am a new user to OpenBSD, so I am trying to wrap my head around this scenario. I am cautiously optimistic, as (to my understanding) Ableton Live and Launchpads use scripts (hidden behind proprietary mumbo jumbo and GUI) so it should be possible to do this in OpenBSD as well. Any input on how many terminal instances I will need, particularly with reference to audio, but also the MIDI in my scenario will be very much appreciated, as this will help me nail down my need for using tmux, a script editor, or something completely different to test this scenario in action on OpenBSD.
Re: Script launcher and a suite of basic scripts for music production?
On 1/18/23 11:46, Abhishek Chakravarti wrote: Hello! Brian Durant writes: The only disadvantage that I can see at this point, is that what I am describing would require a number of open terminals on the desktop, which can be confusing to sort through, particularly during a live performance. Although not a direct answer to your question, perhaps tmux(1) might be helpful here? You could have one tmux session window split into several panes. Cycling through the panes is quite simple with PREFIX + o (the default PREFIX being CTRL+b; in my case it's mapped to CTRL+o Thanks for that. I haven't played around with tmux for ages, but you are correct that could potentially help with terminal clutter. Below are a few thoughts about scripts for music. I will avoid flooding the list with all of my ideas but will simply provide a couple of basic ones. Note that I am new to OpenBSD and have little experience with scripting: OpenBSD music scripts Scan midi/ values (from dmesg or...) and route them to midithru/0 similar to manual commands below: (Is there a use case scenario for rerouting midi/1 - ? by use of midithru/1 -?) $ midicat -d -q midi/0 -q midithru/0 $ midicat -d -q midi/1 -q midithru/0 Record audio from USB sound card: $ aucat -o /home/user/Music/set/1 - ?.wav Playback audio file: $ aucat -i /home/user/Music/set/1 - ?.wav To my knowledge, most USB sound cards have at least two inputs (for microphone and guitar / bass as examples). Important that any script is input sensitive and can automatically number files for each input in order for possible playback with effects by using a simple alias created automatically for the purpose, for the session (?) Also important that monitoring is possible during file creation to avoid pauses while performing a set.
Script launcher and a suite of basic scripts for music production?
Is there a script launcher that can be used for basic scripts to facilitate live (or close to live) music performances with OpenBSD? One of the reasons that I am a proponent of using OpenBSD with music, is the fact that much can be done simply, from the command line. Recording audio from a USB sound card, using ffmpeg to add reverb and basic effects, rerouting MIDI, switching instruments in Fluidsynth (still working on that one), potentially replaying audio files as clips, etc. There are a lot of possibilities that could be facilitated by a script launcher (and a suite of basic scripts) for new music creators trying out OpenBSD, would definitely be an asset. The only disadvantage that I can see at this point, is that what I am describing would require a number of open terminals on the desktop, which can be confusing to sort through, particularly during a live performance. Which is part of the reason that a script launcher would be useful. The advantages are many, first and foremost fitting in with the Unix philosophy of combining existing programs for new purposes, providing an open source alternative to commercial DAWs such as Ableton and Bitwig, while at the same time removing the frustration for some users that the only DAW available on OpenBSD is LMMS, as well as the temptation for some to try to compile Zrythm or another DAW to OpenBSD. Ideas or suggestions?
Re: sndiod and midicat routing issue.
On 1/15/23 12:26, Alexandre Ratchov wrote: On Sun, Jan 15, 2023 at 09:38:38AM +0100, Brian Durant wrote: The following command will connect a USB MIDI device: $ midicat -d -q midi/0 -q midithru/0 & A second device can be connected as follows: $ midicat -d -q midi/1 -q midithru/1 & Both output MIDI code in the terminal. (Note that redirecting both MIDI devices to midithru/0 doesn’t seem to pipe both devices through, but rather only midi/0.) Adding the following command provides a way to convert MIDI code to sound using Fluidsynth: Redirecting two ports to midithru/0 is supposed to work: $ midicat -d -q midi/0 -q midithru/0 # in one terminal $ midicat -d -q midi/1 -q midithru/0 # in another terminal should merge the two inputs. Both terminals should show the events of the corresponding input. If there's a synth on midithru/0 (ex. fluidsynth command below is running) it will produice sounds for both inputs. Hmm. Seems to be working now. However, this just means that MIDI signals go from both MIDI devices to one instance of fluidsynth. This of course means that both devices are sending MIDI code to one soundfont instrument. If run as: $ midicat -d -q midi/0 -q midithru/0 and $ midicat -d -q midi/1 -q midithru/1 MIDI input could be used to play different soundfont instruments - one for midi/0 and one for midi/1. Possibly something with the Fluidsynth "-L" option? The problem is the same for LMMS. However, only one MIDI input is ever available. Enabling MIDI input and choosing different channels for SF2 Player and Kicker do not provide a second MIDI input to choose from when the clicking the relevant plugin's gear icon in the "song editor" window. Not even when running midicat as I have suggested above. Hopefully this won't raise any hackles me writing this, but what I am describing is the normal expectation for using MIDI under Windows, Mac and Linux... I realize that this is achieved in various ways depending on the OS, but particularly the expected use case scenario that I describe for LMMS provides some challenges in OpenBSD. $ fluidsynth /usr/local/share/generaluser-gs/GeneralUser_GS.sf2 However, this only works for midi/0. The same is the case when using LMMS with SF2 Player and Kicker. I can get sound with SF2 Player or Kicker, but there again appears no way to connect the second device to the second plugin. Connecting two MIDI devices (or one device with keys and pads on two channels) is not an unusual use case scenario, so I am assuming that there is a solution without having to resort to midish.
sndiod and midicat routing issue.
The following command will connect a USB MIDI device: $ midicat -d -q midi/0 -q midithru/0 & A second device can be connected as follows: $ midicat -d -q midi/1 -q midithru/1 & Both output MIDI code in the terminal. (Note that redirecting both MIDI devices to midithru/0 doesn’t seem to pipe both devices through, but rather only midi/0.) Adding the following command provides a way to convert MIDI code to sound using Fluidsynth: $ fluidsynth /usr/local/share/generaluser-gs/GeneralUser_GS.sf2 However, this only works for midi/0. The same is the case when using LMMS with SF2 Player and Kicker. I can get sound with SF2 Player or Kicker, but there again appears no way to connect the second device to the second plugin. Connecting two MIDI devices (or one device with keys and pads on two channels) is not an unusual use case scenario, so I am assuming that there is a solution without having to resort to midish. I am using a Keith McMillen K-Board and a KORG nanoPAD2, as they are both class compliant, however any class compliant devices at hand should work... Cheers, Brian
Re: OpenBSD 7.2 amd64, MIDI error "midi/0: couldn't open port".
On 1/6/23 13:42, Alexandre Ratchov wrote: could you post the output of dmesg (at least the midi-related lines). I haven't been able to find any. I should add that this is a fresh install of OpenBSD 7.2. For thoroughness, The entire dmesg is available Here: https://pastebin.com/McSXuvu9
Re: OpenBSD 7.2 amd64, MIDI error "midi/0: couldn't open port".
On 1/6/23 18:40, Alexandre Ratchov wrote: On Fri, Jan 06, 2023 at 10:18:37AM +0100, Brian Durant wrote: Hi, Completely lost as to the cause for the error. I have read the relevant man pages as well as searching the mail archive. System info: OpenBSD 7.2 amd64, GNOME 42.5, Huawei MateStation S with AMD Ryzen 5 4600G and Radeon Graphics. Error messages: $ midicat -d -q midi/0 -q midithru/0 midi/0: couldn't open port $ midicat -d -q midi/1 -q midithru/0 midi/1: couldn't open port according to your dmesg (other mail), you don't any MIDI ports on your machine. Relevant output: $ dmesg ... uaudio0: sync play xfer, err = 6 uaudio0: sync play xfer, err = 6 uaudio0: sync play xfer, err = 6 ugen2 at uhub2 port 2 "Roland A-PRO" rev 1.10/1.20 addr 3 Do you know if this is class-compliant (aka "driverless")? OpenBSD supports only class-compliant MIDI devices. Interesting question. I know that it works with various Linux distributions, which to my understanding also work with class compliant devices as a point of reference. However, the Roland A-800 Pro also has an "ACT" mode which requires a Windows driver if used. I have never used it in "ACT" mode and never needed a special driver. Unfortunately, I will probably have to assume that OpenBSD at least, doesn't consider this device class compliant. A pity as it is difficult to find MIDI keyboards with better than average keys... Not all old devices are class-compliant because in the 2000's, Windows used to have a bug that hardware designers tried to workaround. Certain devices from the 2000's have a switch (or configuration parameter) to switch between vendor-specific and class-compliant modes. Try to dig in the manual. If you can't switch the device to class-compliant mode, get a USB-MIDI interface, they are cheap nowadays and just work. $ cat /etc/rc.conf.local pkg_scripts=avahi_daemon messagebus gdm cups_browsed sndiod_flags=-z 128 -f rsnd/1 $ cat /etc/sysctl.conf kern.audio.record=1 sndiod flags are for reduced latency and for audio to work properly on my Huawei MateStation. seems correct Thanks for your time.
OpenBSD 7.2 amd64, MIDI error "midi/0: couldn't open port".
Hi, Completely lost as to the cause for the error. I have read the relevant man pages as well as searching the mail archive. System info: OpenBSD 7.2 amd64, GNOME 42.5, Huawei MateStation S with AMD Ryzen 5 4600G and Radeon Graphics. Error messages: $ midicat -d -q midi/0 -q midithru/0 midi/0: couldn't open port $ midicat -d -q midi/1 -q midithru/0 midi/1: couldn't open port Relevant output: $ dmesg ... uaudio0: sync play xfer, err = 6 uaudio0: sync play xfer, err = 6 uaudio0: sync play xfer, err = 6 ugen2 at uhub2 port 2 "Roland A-PRO" rev 1.10/1.20 addr 3 $ cat /etc/rc.conf.local pkg_scripts=avahi_daemon messagebus gdm cups_browsed sndiod_flags=-z 128 -f rsnd/1 $ cat /etc/sysctl.conf kern.audio.record=1 sndiod flags are for reduced latency and for audio to work properly on my Huawei MateStation. Brian
Re: Xiaomi Mi Air, Synaptic trackpad and OpenBSD 7.2.
On 11/12/22 19:04, Marcus MERIGHI wrote: Hello, cont...@anarchosaxophonist.org (Brian Durant), 2022.11.12 (Sat) 10:49 (CET): I am trying to get the Synaptic trackpad (12C?) on a Xiaomi Mi Air laptop working. I have found several references in the OpenBSD man pages, so I believe something has been worked on, but at what stage the development is currently at, I am a bit unsure. Usually, if something is included in OpenBSD, it often just works, but sometimes configuration is needed. As I have seen no references to this in the mailing list archive, I thought that I would ask here - do I just need to configure something, or is development still working on this? this sounds like you have OpenBSD running on that hardware with only the trackpad not working. What machine is this? I cannot find it at a local retailer and looking for "Xiaomi Mi Air" on am?zon makes me wonder if this thing really runs OpenBSD :-) https://www.amazon.com/Xiaomi-Purifier-Efficiency-Eliminate-Coverage/dp/B094NST3N8 dmesg please! Marcus Thank you for the reply. Here is a lot of information about the Xiaomi Mi Air 12.5": https://jcs.org/2017/05/22/xiaomiair I purchased mine used on EBay. Dmesg: 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 = 4186648576 (3992MB) avail mem = 4042362880 (3855MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x8c4fd000 (69 entries) bios0: vendor INSYDE Corp. version "A04" date 08/06/2016 bios0: Timi TM1612 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA UEFI UEFI SSDT SSDT TPM2 MSDM SSDT SSDT DBGP DBG2 ASF! ASPT BOOT DBGP HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT DMAR FPDT WPBT BGRT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) PWRB(S4) LID0(S3) GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz, 1197.21 MHz, 06-4e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 4MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz, 1075.63 MHz, 06-4e-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 4MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz, 997.68 MHz, 06-4e-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 4MB 64b/line 16-way L3 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz, 997.68 MHz, 06-4e-03 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,VM
Xiaomi Mi Air, Synaptic trackpad and OpenBSD 7.2.
I am trying to get the Synaptic trackpad (12C?) on a Xiaomi Mi Air laptop working. I have found several references in the OpenBSD man pages, so I believe something has been worked on, but at what stage the development is currently at, I am a bit unsure. Usually, if something is included in OpenBSD, it often just works, but sometimes configuration is needed. As I have seen no references to this in the mailing list archive, I thought that I would ask here - do I just need to configure something, or is development still working on this?
Re: Connect MIDI keyboard to SF2 player in LMMS - OpenBSD 7.2.
On 11/8/22 17:15, Alexandre Ratchov wrote: If you've multiple MIDI controllers, you could assign a MIDI channel to each (most MIDI controllers have a knob to do so) and then route them all to "midithru/0" so lmms or fluidsynth see them as a single port. For instance: midicat -d -q midi/0 -q midithru/0 midicat -d -q midi/1 -q midithru/0 Then, in lmms (or fluidsynth), configure each track's "Input channel" setting to the corresponding input (click on the "keyboard" icon, then the "enable midi input" button, then select the channel number). If you need a more complex MIDI routing, you could try the audio/midish port. Note that certain programs count channel numbers from 0 other from 1. Hi again Alexandre, OK, many thanks for that. I have tried to make this a little simpler by just using one device, that has both keys and pads. Here is the dmesg section: umidi0 at uhub0 port 5 configuration 1 interface 1 "Nektar Impact LX25+" rev 1.10/0.32 addr 3 umidi0: (genuine USB-MIDI) umidi0: out=1, in=2 midi0 at umidi0: midi1 at umidi0: ugen2 at uhub0 port 5 configuration 1 "Nektar Impact LX25+" rev 1.10/0.32 addr 3 I ran the following: $ midicat -d -q midi/0 -q midithru/0 $ midicat -d -q midi/1 -q midithru/0 It appears that it is necessary to use two terminals for this... As suggested, I configured LMMS' Sf2 Player input channel to "1" and then enabled the midi input. I did the same with the Kicker plugin input channel, set it to "2" and enabled the midi input. I then set the action gear for each plugin to receive MIDI input on each. The Sf2 plugin input can be seen in the piano roll, where notes and velocity can be adjusted after the fact. The terminal running the $ midicat -d -q midi/0 -q midithru/0 command has MIDI output scrolling down the terminal. While the pads produce the correct (drum) sounds when the Kicker plugin is open, when closed (and only the Sf2 and Kicker plugins are in the song editor panel) I only get grand piano sounds. Likewise, there is no scrolling output in the second terminal with the command $ midicat -d -q midi/1 -q midithru/0. Nothing appears in the piano roll either, when I chose "record". Not sure what is going on here...
Connect MIDI keyboard to SF2 player in LMMS - OpenBSD 7.2.
I am trying to connect my MIDI keyboard to the Sf2 Player, in LMMS. sndio MIDI is set under MIDI interface in the MIDI settings section of the LMMS preferences. DMESG gives me the following when I plug my MIDI keyboard into the computer: umidi0 at uhub0 port 5 configuration 1 interface 0 "KORG INC. microKEY2" rev 1.10/1.02 addr 3 umidi0: (genuine USB-MIDI) umidi0: out=1, in=1 midi0 at umidi0: I have read the three bits of LMMS documentation on MIDI, and I am familiar with how to use fluidsynth to connect directly with my MIDI keyboard to the default soundfont: $ fluidsynth /usr/local/share/generaluser-gs/GeneralUser_GS.sf2 $ midicat -d -q midi/0 -q midithru/0 Unfortunately, none of this seems to work in LMMS. Clicking on the action gear for the Sf2 Player plugin shows MIDI input and output, but does not list my MIDI keyboard (as in Linux or Windows) so that I can bind it to the Sf2 Player. There is very little information about using MIDI instruments in the OpenBSD FAQ, and my knowledge of sdiod and jack are limited. The only way that I have found that I can get this to work, is if I run $ midicat -d -q midi/0 -q midithru/0 from the command line, before I open LMMS and I then select MIDI input in the Sf2 Player action gear. However, this allows only for one MIDI instrument at a time. If I also want to connect a drumpad like the Akai MPK 218, would I run $ midicat -d -q midi/1 -q midithru/1 and how do I set MIDI input in the Kicker plugin to only get the MIDI signals from the drumpad and not the keyboard? Perhaps LMMS and sndio are only setup for something like the Akai MPK Mini MKIII? Any help trying to wrap my head around how MIDI, sndio and jack work in this context is appreciated.
Recently acquired Ryzen 5 computer lacks sound with OpenBSD 7.1.
The computer has a Ryzen 5 4600G processor, as well as AMD High Def and Realtek audio. I have tried unsuccessfully to get audio through the HDMI connection as well as a Behringer UMC20HD USB sound card. I have looked at the relevant man pages and tried to solve this on Reddit. It has been suggested that I try the fount of all OpenBSD wisdom, so I am posting here. The relevant outputs (thanks to Reddit feedback) can be found here: https://pastebin.com/2rvjWuD7 https://pastebin.com/W26cMyMZ My Reddit post can be found here: https://www.reddit.com/r/openbsd/comments/ydsgo2/recently_acquired_ryzen_5_computer_lacks_sound/ I really like this computer, as OpenBSD appears to run well from it so far, so I am hoping the audio issue can be solved...
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On Fri, 5 Aug 2022, Alexander Hall wrote: > > > On August 5, 2022 8:32:25 AM GMT+02:00, Brian Durant > wrote: > > > > > >On Thu, 4 Aug 2022, Alexander Hall wrote: > > > >> > >> > >> On August 4, 2022 5:42:13 PM GMT+02:00, Brian Durant > >> wrote: > >> > > >> > > >> >On Thu, 4 Aug 2022, Lucas wrote: > >> > > >> >> Brian Durant wrote: > >> >> > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am > >> >> > experiencing a > >> >> > couple of issues. The first is related to the following addition that > >> >> > I > >> >> > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 > >> >> > installs, > >> >> > but not with the OpenBSD 7.1 i386 install on my Lenovo T60: > >> >> > XTerm*VT100.Translations: #override\ > >> >> > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > >> >> > Ctrl Shift V: insert-selection(CLIPBOARD) > >> >> > Any ideas how to get copy and paste working in Xterm with an i386 > >> >> > install? > >> >> > >> >> I don't know if it's relevant, but my Xdefaults looks like this > >> >> > >> >> XTerm.VT100.translations: #override \n\ > >> >> Ctrl Alt C:copy-selection(CLIPBOARD) \n\ > >> >> Ctrl Alt V:insert-selection(CLIPBOARD) \n\ > >> >> [...other stuff...] > >> >> > >> >> In particular, do note the "\n" after #override, which isn't present in > >> >> your snippet. This works fine for me. > >> >> > >> >> Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know > >> >> if it's product of your MUA or if it's actually part of the file (it's > >> >> a non-breaking space, aka in XML/HTML), do double-check the > >> >> whitespaces in there. > >> >> > >> >> -Lucas > >> > > >> >Thanks for the reply. Trying a different MUA. Not sure where the extra > >> >characters that you mention crept in, however they weren't in the > >> >.Xdefaults file as far as I could see. I added the extra "\n\" in the > >> >last > >> >line as suggested, but weirdly this had no effect. Still no copy-paste in > >> >i386. > >> > >> It wasn't the last line that potentially lacked "\n\", it was the first > >> one, "#override\n\". > >> > >> I suspect paste actually might already work. Did you try copying from, > >> say, Firefox, and then paste into an xterm? > >> > >> I strongly believe this has nothing to do with the platform. > >> > >> /Alexander > > > >Hmm. Thanks for the inspiration, but no, paste wasn't already working. I > >have however, now got copy to work. Unfortunately, nothing I do seems to > >sort paste out. Currently my snippet looks like this: > >xterm.VT100.translations:#override \ > > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > > Ctrl Shift V: insert-selection(CLIPBOARD) > > > >The "n\" that you have in he first line shouldn't make a difference as it > >is a comment "#", isn't it? What causes me some concern, is the apparent > >lack of consistent behavior between architectures on this minor, but > >irritating issue. > > Every example from the xterm man page uses sth like: > > *VT100*translations: #override \n\ > > , and it makes sense, as # is not a comment in the resource file itself. So > your resource value above effectively becomes > > "#override Ctrl Shift C: copy-selection(CLIPBOARD) > Ctrl Shift V: insert-selection(CLIPBOARD)" > > instead of > > "#override > Ctrl Shift C: copy-selection(CLIPBOARD) > Ctrl Shift V: insert-selection(CLIPBOARD)" > > Also, while being at the edge of my confidence level here, generally > > XTerm*VT100*translations: > > With all them asterisks, usually kicks in better. YMMV though. > > Also, I assume the proper xrdb commands are issued to set these resource > values. > > /Alexander OK. I tried your suggestions with the "*" and "\n\" now everything is working fine. I corrected my .Xdefaults list on my amd64 install to match, and that works fine as well. Many thanks. Brian
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On Thu, 4 Aug 2022, Alexander Hall wrote: > > > On August 4, 2022 5:42:13 PM GMT+02:00, Brian Durant > wrote: > > > > > >On Thu, 4 Aug 2022, Lucas wrote: > > > >> Brian Durant wrote: > >> > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am experiencing a > >> > couple of issues. The first is related to the following addition that I > >> > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 installs, > >> > but not with the OpenBSD 7.1 i386 install on my Lenovo T60: > >> > XTerm*VT100.Translations: #override\ > >> > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > >> > Ctrl Shift V: insert-selection(CLIPBOARD) > >> > Any ideas how to get copy and paste working in Xterm with an i386 > >> > install? > >> > >> I don't know if it's relevant, but my Xdefaults looks like this > >> > >> XTerm.VT100.translations: #override \n\ > >> Ctrl Alt C:copy-selection(CLIPBOARD) \n\ > >> Ctrl Alt V:insert-selection(CLIPBOARD) \n\ > >> [...other stuff...] > >> > >> In particular, do note the "\n" after #override, which isn't present in > >> your snippet. This works fine for me. > >> > >> Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know > >> if it's product of your MUA or if it's actually part of the file (it's > >> a non-breaking space, aka in XML/HTML), do double-check the > >> whitespaces in there. > >> > >> -Lucas > > > >Thanks for the reply. Trying a different MUA. Not sure where the extra > >characters that you mention crept in, however they weren't in the > >.Xdefaults file as far as I could see. I added the extra "\n\" in the last > >line as suggested, but weirdly this had no effect. Still no copy-paste in > >i386. > > It wasn't the last line that potentially lacked "\n\", it was the first one, > "#override\n\". > > I suspect paste actually might already work. Did you try copying from, say, > Firefox, and then paste into an xterm? > > I strongly believe this has nothing to do with the platform. > > /Alexander Hmm. Thanks for the inspiration, but no, paste wasn't already working. I have however, now got copy to work. Unfortunately, nothing I do seems to sort paste out. Currently my snippet looks like this: xterm.VT100.translations: #override \ Ctrl Shift C: copy-selection(CLIPBOARD) \n\ Ctrl Shift V: insert-selection(CLIPBOARD) The "n\" that you have in he first line shouldn't make a difference as it is a comment "#", isn't it? What causes me some concern, is the apparent lack of consistent behavior between architectures on this minor, but irritating issue.
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On Thursday, August 4, 2022, Michael Hekeler wrote: > Am 04.08.22 15:27 schrieb Brian Durant: > > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am experiencing a > > couple of issues. The first is related to the following addition that I made > > to my .Xdefaults file, which works with OpenBSD 7.1 amd64 installs, but not > > with the OpenBSD 7.1 i386 install on my Lenovo T60: > > XTerm*VT100.Translations: #override\ > > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > > Ctrl Shift V: insert-selection(CLIPBOARD) > > Any ideas how to get copy and paste working in Xterm with an i386 install? > > > I understand that you want to map these keys but just to mention: there > is support for PRIMARY in xterm(1) and this means selected text is in > primary without any explicit copy action taking place. > see Inter-Client Communication Coventions Manual for X Thank you for the information. Seen from my perspective, the override that I am using is more convenient on a laptop, but more importantly, expected behavior should be the same regardless of architecture. There shouldn't be different behavior on amd64 architecture compared to i386 architecture.
Re: Xterm copy-paste not happening on OpenBSD 7.1 i386.
On Thu, 4 Aug 2022, Lucas wrote: > Brian Durant wrote: > > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am experiencing a > > couple of issues. The first is related to the following addition that I > > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 installs, > > but not with the OpenBSD 7.1 i386 install on my Lenovo T60: > > XTerm*VT100.Translations: #override\ > > Ctrl Shift C: copy-selection(CLIPBOARD) \n\ > > Ctrl Shift V: insert-selection(CLIPBOARD) > > Any ideas how to get copy and paste working in Xterm with an i386 install? > > I don't know if it's relevant, but my Xdefaults looks like this > > XTerm.VT100.translations: #override \n\ > Ctrl Alt C:copy-selection(CLIPBOARD) \n\ > Ctrl Alt V:insert-selection(CLIPBOARD) \n\ > [...other stuff...] > > In particular, do note the "\n" after #override, which isn't present in > your snippet. This works fine for me. > > Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know > if it's product of your MUA or if it's actually part of the file (it's > a non-breaking space, aka in XML/HTML), do double-check the > whitespaces in there. > > -Lucas Thanks for the reply. Trying a different MUA. Not sure where the extra characters that you mention crept in, however they weren't in the .Xdefaults file as far as I could see. I added the extra "\n\" in the last line as suggested, but weirdly this had no effect. Still no copy-paste in i386.
Xterm copy-paste not happening on OpenBSD 7.1 i386.
I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am experiencing a couple of issues. The first is related to the following addition that I made to my .Xdefaults file, which works with OpenBSD 7.1 amd64 installs, but not with the OpenBSD 7.1 i386 install on my Lenovo T60: XTerm*VT100.Translations: #override\ Ctrl Shift C: copy-selection(CLIPBOARD) \n\ Ctrl Shift V: insert-selection(CLIPBOARD) Any ideas how to get copy and paste working in Xterm with an i386 install?
Multiple OpenBSD mirror issues for i386.
I am trying to download and install the i386 verion of OpenBSD 7.1 to an IBM/Lenovo T60. https://cdn.openbsd.org/pub/OpenBSD/7.1/i386/install71.img (and .iso) give me the following message: Error 503 Backend is unhealthy Backend is unhealthy Error 54113 Details: cache-cph2320057-CPH 1658065549 3028862290 Varnish cache server" I have also downloaded both the 7.1 .iso and .img file from alternative mirrors. The files have passed muster with SHA256 and signify. However, when booting the USB pen drive that the images have been burned to, the lead is >> OpenBSD/amd64 BOOT 3.53 - and then a few lines down, after boot> I get the following: hd0a:/7.1/amd64/bsd.rd It looks to me as if someone uploaded the wrong files in under the wrong architecture directory, and that it has propagated through the OpenBSD mirrors. I have tried this a number of times, so I know that I haven't just pressed the wrong link. I have gone into the mirrors manually under the correct architecture directory and downloaded the files... Brian
Re: Behringer UMC404HD USB soundcard with OpenBSD 7.1.
On 7/16/22 6:26 PM, Alexandre Ratchov wrote: On Sat, Jul 16, 2022 at 05:37:35PM +0200, Brian Durant wrote: On 7/16/22 3:54 PM, Alexandre Ratchov wrote: On Sat, Jul 16, 2022 at 03:36:18PM +0200, Brian Durant wrote: # mixerctl -f /dev/audioctl1 mixerctl: /dev/audioctl1: Device not configured # dmesg forgot to mention: connect and power on the audio interface first ;-) It was. This time I waited until boot was complete, before connecting the USB cable... ... uhub3: port 1, set config 0 at addr 6 failed uhub3: device problem, disabling port 1 sorry, I missed these lines, this is when you connected the device, right? The device doesn't even attach, so not surprising it doesn't work. I don't know what could cause this maybe weak power? Do you have an external power source, if not could you try with it? I think so, I was multitasking at the time... Interesting and even more interesting. Yes, the power supply that came with the unit is plugged in and functioning on the UMC404HD. I had a UMC202HD lying around the house, that I just tried, which is powered through the USB cable and that works fine with OpenBSD. Only the powered UMC404HD had issues.
Re: Behringer UMC404HD USB soundcard with OpenBSD 7.1.
On Sat, 16 Jul 2022 11:23:16 +0200 Alexandre Ratchov wrote: > On Sat, Jul 16, 2022 at 08:26:49AM +0200, Brian Durant wrote: > > I have thus far been using an audio direct out to my speakers, but would > > like to get my USB soundcard working in OpenBSD. Without the soundcard, > > (direct connection) everything works fine. With the soundcard, no audio at > > all. I have tried the following as per the OpenBSD FAQ: > > > > # rcctl set sndiod flags -f rsnd/0 -F rsnd/1 > > # rcctl restart sndiod > > sndiod(ok) > > sndiod(ok) > > > > I have rebooted the system, tried Cmixer and adjusted output gradually to > > 100%, but did not get any sound. I have consulted the list archive, but > > nothing, except to note what I already knew, that Behringer soundcards are > > class compliant. I use this card on Windows 11, Linux and FreeBSD, so I know > > that it works. I have made no major adjustments to the unit itself. Sooo, I > > have hit a bit of a dead end. Anyone out there that can provide some help? I > > am trying to get this to work by testing YouTube in Firefox, both of which > > work with a direct audio connection (midi jack cable)... > > could you send the output of: > > mixerctl -f /dev/audioctl1 > and: > dmesg I just tried connecting the soundcard to a Dell Vostro 3350 laptop running the same version of the OpenBSD system, just a week or two older. Things look pretty much the same on this computer as far as I can tell: # mixerctl -f /dev/audioctl1 mixerctl: /dev/audioctl1: Device not configured # dmesg OpenBSD 7.1 (GENERIC.MP) #0: Sun Apr 24 09:30:43 MDT 2022 r...@syspatch-71-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8471326720 (8078MB) avail mem = 8197312512 (7817MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeb850 (57 entries) bios0: vendor Dell Inc. version "A07" date 09/30/2011 bios0: Dell Inc. Vostro 3350 acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG SSDT SLIC HPET SSDT SSDT DMAR SSDT SSDT OSFR acpi0: wakeup devices USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(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) Core(TM) i7-2640M CPU @ 2.80GHz, 2794.05 MHz, 06-2a-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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,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) Core(TM) i7-2640M CPU @ 2.80GHz, 2793.66 MHz, 06-2a-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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2793.66 MHz, 06-2a-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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2793.66 MHz, 06-2a-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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 H
Re: Behringer UMC404HD USB soundcard with OpenBSD 7.1.
On 7/16/22 3:54 PM, Alexandre Ratchov wrote: On Sat, Jul 16, 2022 at 03:36:18PM +0200, Brian Durant wrote: # mixerctl -f /dev/audioctl1 mixerctl: /dev/audioctl1: Device not configured # dmesg forgot to mention: connect and power on the audio interface first ;-) It was. This time I waited until boot was complete, before connecting the USB cable... # mixerctl -f /dev/audioctl1 mixerctl: /dev/audioctl1: Device not configured OpenBSD 7.1 (GENERIC.MP) #0: Sun Apr 24 09:30:43 MDT 2022 r...@syspatch-71-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8471175168 (8078MB) avail mem = 8197136384 (7817MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6e20 (66 entries) bios0: vendor LENOVO version "EZKT22AUS" date 10/15/2013 bios0: LENOVO 10115 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI HPET APIC MCFG WDAT BOOT ASPT DBGP FPDT MSDM SSDT SSDT acpi0: wakeup devices P0P1(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1796.18 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,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 1 (application processor) cpu1: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1795.93 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1795.93 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1795.93 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 4 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpipci0 at acpi0 PCI0: 0x0004 0x0011 0x0001 acpicmos0 at acpi0 "PNP0A05" at acpi0 not configured com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo acpibtn0 at acpi0: PWRB acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 106 degC acpitz1 at acpi0: critical temperature is 106 degC acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02
Re: Behringer UMC404HD USB soundcard with OpenBSD 7.1.
On 7/16/22 11:23 AM, Alexandre Ratchov wrote: On Sat, Jul 16, 2022 at 08:26:49AM +0200, Brian Durant wrote: I have thus far been using an audio direct out to my speakers, but would like to get my USB soundcard working in OpenBSD. Without the soundcard, (direct connection) everything works fine. With the soundcard, no audio at all. I have tried the following as per the OpenBSD FAQ: # rcctl set sndiod flags -f rsnd/0 -F rsnd/1 # rcctl restart sndiod sndiod(ok) sndiod(ok) I have rebooted the system, tried Cmixer and adjusted output gradually to 100%, but did not get any sound. I have consulted the list archive, but nothing, except to note what I already knew, that Behringer soundcards are class compliant. I use this card on Windows 11, Linux and FreeBSD, so I know that it works. I have made no major adjustments to the unit itself. Sooo, I have hit a bit of a dead end. Anyone out there that can provide some help? I am trying to get this to work by testing YouTube in Firefox, both of which work with a direct audio connection (midi jack cable)... could you send the output of: mixerctl -f /dev/audioctl1 and: dmesg # mixerctl -f /dev/audioctl1 mixerctl: /dev/audioctl1: Device not configured # dmesg OpenBSD 7.1 (GENERIC.MP) #0: Sun Apr 24 09:30:43 MDT 2022 r...@syspatch-71-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8471175168 (8078MB) avail mem = 8197160960 (7817MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6e20 (66 entries) bios0: vendor LENOVO version "EZKT22AUS" date 10/15/2013 bios0: LENOVO 10115 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI HPET APIC MCFG WDAT BOOT ASPT DBGP FPDT MSDM SSDT SSDT acpi0: wakeup devices P0P1(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1796.23 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,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 1 (application processor) cpu1: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1795.92 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1795.93 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1795.93 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 4 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bu
Behringer UMC404HD USB soundcard with OpenBSD 7.1.
I have thus far been using an audio direct out to my speakers, but would like to get my USB soundcard working in OpenBSD. Without the soundcard, (direct connection) everything works fine. With the soundcard, no audio at all. I have tried the following as per the OpenBSD FAQ: # rcctl set sndiod flags -f rsnd/0 -F rsnd/1 # rcctl restart sndiod sndiod(ok) sndiod(ok) I have rebooted the system, tried Cmixer and adjusted output gradually to 100%, but did not get any sound. I have consulted the list archive, but nothing, except to note what I already knew, that Behringer soundcards are class compliant. I use this card on Windows 11, Linux and FreeBSD, so I know that it works. I have made no major adjustments to the unit itself. Sooo, I have hit a bit of a dead end. Anyone out there that can provide some help? I am trying to get this to work by testing YouTube in Firefox, both of which work with a direct audio connection (midi jack cable)... Brian
Re: Web MIDI, Firefox, OpenBSD.
On 7/15/22 2:53 PM, Alexandre Ratchov wrote: On Fri, Jul 15, 2022 at 02:28:37PM +0200, Brian Durant wrote: On 7/15/22 12:54 PM, Alexandre Ratchov wrote: On Thu, Jul 14, 2022 at 10:05:43AM +0200, Brian Durant wrote: On a possibly related issue to my browser access to file system problem, has anyone been able to get Web MIDI working with Firefox on OpenBSD 7.1? Here I am referring to bandcamp.com and flowkey.com in particular. Neither site appears to be receiving any MIDI signal despite an Akai LPK25 (for testing) being registered by the system at umidi0. Flowkey requires ffmpeg to be installed, as well as prompting for the Jazz MIDI extension to be installed. Flowkey tabs crash and never make a MIDI connection. This has never happened to me with Win 11, Linux, of FreeBSD. The Bandcamp site simply doesn't register a MIDI device connected to the system, but doesn't crash the tab. Again, any constructive advice is welcomed. OpenBSD ports has no MIDI support. A quick look at firefox sources suggest it's using is library: https://github.com/boddlnagg/midir which doesn't have sndio backend. Many thanks about the information regarding Web MIDI, Firefox and midir. No wonder this has been driving me mad. I had yet to look systematically at ports to see what programs using MIDI were available, as I have been so busy with the browser issues, so it is interesting that you state that MIDI programs are lacking in ports. What do other users do? To my mind, OpenBSD has excellent support for recognizing MIDI devices, and excellent audio support (sndio) as well, which would make it an excellent OS for music production... At the very least, it should be feasible to get a USB MIDI keyboard working with fluidsynth (Qsynth) according to the OpenBSD FAQ (Multimedia), but I admittedly have yet to be successful at getting that working either... To make fluidsynth work (applies to any real-time softsynth), first lower sndio latency, example: doas rcctl set sndiod flags "-z 128" doas rcctl restart sndiod Install fluidsynth and generaluser-gs-soundfont pacakges. In one terminal start fluidsynth: fluidsynth /usr/local/share/generaluser-gs/GeneralUser_GS.sf2 At this point, fluidsynth listens for incoming MIDI messages on the default "midithru/0" port. To send MIDI messages from your keyboard (probably "midi/0") to it, try: midicat -d -q midi/0 -q midithru/0 Cool. My two problems had been that I could only figure out to use Qsynth to get the path to the soundfont. The second was that I was trying to use umidi/0 rather than midi/0, as I almost exclusively have USB MIDI keyboards. Many thanks. Anyone that uses a DAW with OpenBSD is welcome to jump in here as well. As I mainly work with MIDI, I guess that the best I can hope for is getting LMMS working, as Ardour doesn't handle MIDI very well, from my limited experience...
Re: Web MIDI, Firefox, OpenBSD.
On 7/15/22 12:54 PM, Alexandre Ratchov wrote: On Thu, Jul 14, 2022 at 10:05:43AM +0200, Brian Durant wrote: On a possibly related issue to my browser access to file system problem, has anyone been able to get Web MIDI working with Firefox on OpenBSD 7.1? Here I am referring to bandcamp.com and flowkey.com in particular. Neither site appears to be receiving any MIDI signal despite an Akai LPK25 (for testing) being registered by the system at umidi0. Flowkey requires ffmpeg to be installed, as well as prompting for the Jazz MIDI extension to be installed. Flowkey tabs crash and never make a MIDI connection. This has never happened to me with Win 11, Linux, of FreeBSD. The Bandcamp site simply doesn't register a MIDI device connected to the system, but doesn't crash the tab. Again, any constructive advice is welcomed. OpenBSD ports has no MIDI support. A quick look at firefox sources suggest it's using is library: https://github.com/boddlnagg/midir which doesn't have sndio backend. Many thanks about the information regarding Web MIDI, Firefox and midir. No wonder this has been driving me mad. I had yet to look systematically at ports to see what programs using MIDI were available, as I have been so busy with the browser issues, so it is interesting that you state that MIDI programs are lacking in ports. What do other users do? To my mind, OpenBSD has excellent support for recognizing MIDI devices, and excellent audio support (sndio) as well, which would make it an excellent OS for music production... At the very least, it should be feasible to get a USB MIDI keyboard working with fluidsynth (Qsynth) according to the OpenBSD FAQ (Multimedia), but I admittedly have yet to be successful at getting that working either... Brian
Re: Browser access to file system on new install OpenBSD missing.
On 7/14/22 12:09 PM, Zé Loff wrote: On Thu, Jul 14, 2022 at 09:44:20AM +0200, Brian Durant wrote: The browser issue has returned. An open dialog window to upload a file or to open a file cannot find the downloads directory and it is impossible to access by using "recents" or "computer" in the open dialog window. Not sure what is going on, but it sure is irritating. Add /tmp and/or other unveil'ed folders to your GTK3 bookmarks. That way there is always an accessible folder on the sidebar on which to click: echo "file:///tmp" >> ~/.config/gtk-3.0/bookmarks Many thanks for the tip. Interestingly, thanks to you I started digging around in the two systems to compare differences between them. I found what appears to at present be a solution. The system with the browser file dialog issues did not have a ~/.config/user-dirs.dirs file for some reason. This appears to have solved the problem for now, but I will keep your suggestion on the back burner should I need that as an alternative...
Web MIDI, Firefox, OpenBSD.
On a possibly related issue to my browser access to file system problem, has anyone been able to get Web MIDI working with Firefox on OpenBSD 7.1? Here I am referring to bandcamp.com and flowkey.com in particular. Neither site appears to be receiving any MIDI signal despite an Akai LPK25 (for testing) being registered by the system at umidi0. Flowkey requires ffmpeg to be installed, as well as prompting for the Jazz MIDI extension to be installed. Flowkey tabs crash and never make a MIDI connection. This has never happened to me with Win 11, Linux, of FreeBSD. The Bandcamp site simply doesn't register a MIDI device connected to the system, but doesn't crash the tab. Again, any constructive advice is welcomed.
Re: Browser access to file system on new install OpenBSD missing.
The browser issue has returned. An open dialog window to upload a file or to open a file cannot find the downloads directory and it is impossible to access by using "recents" or "computer" in the open dialog window. Not sure what is going on, but it sure is irritating.
Re: Browser access to file system on new install OpenBSD missing.
On 7/13/22 12:05 AM, Courtney wrote: This is definitely an unveil issue. Not an issue though, it's by design. If you try to download a file both Firefox and Chromium won't know where to save it. By default, they can read/write to ~/Downloads like others have said. However, I think I know the issue you are encountering. I recall at first use it is a bit persnickety, so when presented with the window so save a file to a location you will see nothing. However, in the top bar if you type ~/Downloads and hit enter it will draw you immediately to the Downloads folder, and there you can hit save. Also as others have said, Midori and Thunderbird don't have this issue because neither of them use unveil. It would be really cool if one day at least Thunderbird did. Courtney On 7/10/22 23:46, Brian Durant wrote: I have a problem with both Firefox and Chromium being unable to access the file system using the "open" dialog. The dialog appears, but no files or directories appear regardless of path. Things function normally however, with both Midori and Thunderbird. I assume that Firefox and Chromium are experiencing a permissions issue, but what causes it and how to rectify it is beyond my capabilities as a new OpenBSD user. Anyone out there that could help me out? Thanks in advance. I have reinstalled the system. It appears to be an issue that depends on which file manager is used to create the directories within the home directory. This time (as with my other computer) I used Xfe to create the directories. Last time, I used PCmanFM and experienced the problem. Firefox works as expected now. Thanks. Brian
Re: Browser access to file system on new install OpenBSD missing.
Actually, there is one major difference between the two systems that I had forgotten about. While both use the Calm window manager, the system that is experiencing problems with the browser file dialogs, uses PCManFM...
Re: Browser access to file system on new install OpenBSD missing.
On 7/11/22 17:53, Stuart Henderson wrote:
> I guess your locate database was last generated when firefox was
> installed but chromium was not
>
>> Wondering if something else is at play here...
> grep unveil /usr/local/share/doc/pkg-readmes/*
>
> ls /etc/*/*unveil*
$ grep unveil /usr/local/share/doc/pkg-readmes/*
/usr/local/share/doc/pkg-readmes/chromium:- each category of process
uses unveil(2) to limit filesystem access.
/usr/local/share/doc/pkg-readmes/chromium:Disabling pledge() or unveil()
is not recommended!
/usr/local/share/doc/pkg-readmes/chromium:- global unveil knob: invoke
chromium with --disable-unveil
/usr/local/share/doc/pkg-readmes/chromium:- specific unveil for specific
processes:
/usr/local/share/doc/pkg-readmes/chromium:/etc/chromium/unveil.*
/usr/local/share/doc/pkg-readmes/chromium:to /etc/chromium/unveil.main
and merge with changes in files in
/usr/local/share/doc/pkg-readmes/firefox:pledge(2) and unveil(2) Support
/usr/local/share/doc/pkg-readmes/firefox:Firefox on OpenBSD is secured
with pledge(2) and unveil(2) to limit
/usr/local/share/doc/pkg-readmes/firefox:following files to change the
pledge promises, unveil paths, and
/usr/local/share/doc/pkg-readmes/firefox:/etc/firefox/{unveil,pledge}.{main,content,gpu}
/usr/local/share/doc/pkg-readmes/firefox:As unveil() can't show
non-existing dirs, it is recommended to manually
/usr/local/share/doc/pkg-readmes/firefox:Due to unveil(2) limiting
filesystem access, special care has to be
/usr/local/share/doc/pkg-readmes/firefox:taken to unveil MIME handlers.
For example, to use the mupdf package
/usr/local/share/doc/pkg-readmes/firefox:And the corresponding binary
must be unveiled for it to appear as an
/usr/local/share/doc/pkg-readmes/firefox:line to /etc/firefox/unveil.main:
/usr/local/share/doc/pkg-readmes/firefox:/etc/firefox/unveil.main.
/usr/local/share/doc/pkg-readmes/firefox:To disable pledge and/or unveil
support when troubleshooting, set the
/usr/local/share/doc/pkg-readmes/firefox:corresponding pledge or unveil
file in
/usr/local/share/doc/pkg-readmes/firefox:/etc/firefox/{unveil,pledge}.{main,content,gpu}
to contain
$ ls /etc/*/*unveil*
/etc/chromium/unveil.gpu /etc/chromium/unveil.utility_audio
/etc/firefox/unveil.main
/etc/chromium/unveil.main
/etc/chromium/unveil.utility_network /etc/firefox/unveil.rdd
/etc/chromium/unveil.plugin /etc/chromium/unveil.utility_video
/etc/firefox/unveil.socket
/etc/chromium/unveil.renderer/etc/firefox/unveil.content
/etc/chromium/unveil.utility /etc/firefox/unveil.gpu
Re: Browser access to file system on new install OpenBSD missing.
On 7/11/22 15:25, Stuart Henderson wrote: > On 2022-07-11, Björn Gohla wrote: >> >> Brian Durant writes: >> >>> I have a problem with both Firefox and Chromium being unable to access >>> the file system using the "open" dialog. The dialog appears, but no >>> files or directories appear regardless of path. Things function >> [...] >> >> This sounds like an unveil(2) issue. Only white-listed paths are >> accessible, they are configured in /etc/firefox/unveil.* . >> >> ~/Downloads should be enabled by default though. > > only if present before the browser was started, also the file dialog boxes > will often be blank and you need to either type a path by hand, or pick > one of the predefined entries in the left-hand side; browsing the whole > computer won't work with the default unveil restrictions > > ~/Downloads is indeed in /etc/firefox/unveil.main and /etc/chromium/unveil.main. Interestingly, it doesn't appear that either Thunderbird nor Midori have a similar unveil file. Interestingly (or not) When running the following, Chromium doesn't appear at all: $ doas locate unveil.main /etc/firefox/unveil.main /usr/local/lib/firefox/browser/defaults/preferences/unveil.main Nor does it in: $ doas locate unveil /etc/firefox/unveil.content /etc/firefox/unveil.gpu /etc/firefox/unveil.main /etc/firefox/unveil.rdd /etc/firefox/unveil.socket /usr/local/lib/firefox/browser/defaults/preferences/unveil.content /usr/local/lib/firefox/browser/defaults/preferences/unveil.gpu /usr/local/lib/firefox/browser/defaults/preferences/unveil.main /usr/local/lib/firefox/browser/defaults/preferences/unveil.rdd /usr/local/lib/firefox/browser/defaults/preferences/unveil.socket /usr/share/man/man2/unveil.2 /usr/share/relink/kernel/GENERIC.MP/kern_unveil.o Wondering if something else is at play here...
Re: Browser access to file system on new install OpenBSD missing.
On 7/11/22 14:40, Björn Gohla wrote: > > Brian Durant writes: > >> I have a problem with both Firefox and Chromium being unable to access >> the file system using the "open" dialog. The dialog appears, but no >> files or directories appear regardless of path. Things function > [...] > > This sounds like an unveil(2) issue. Only white-listed paths are > accessible, they are configured in /etc/firefox/unveil.* . > > ~/Downloads should be enabled by default though. > > Read /usr/local/share/doc/pkg-readmes/firefox for all the details. Nothing in readmes that hit a note, except possibly dbus not running? I have two computers running the latest stable, but this problem is only on the one... The other thing that I have noticed is that $ uname -v returns GENERIC.MP#465 on the one, while the other responds GENERIC.MP#0. Otherwise, to my knowledge, both computer installs are exactly the same and of recent date (within two weeks) of each other. Thanks for your replies, but I am still confused... Brian
Browser access to file system on new install OpenBSD missing.
I have a problem with both Firefox and Chromium being unable to access the file system using the "open" dialog. The dialog appears, but no files or directories appear regardless of path. Things function normally however, with both Midori and Thunderbird. I assume that Firefox and Chromium are experiencing a permissions issue, but what causes it and how to rectify it is beyond my capabilities as a new OpenBSD user. Anyone out there that could help me out? Thanks in advance.
