Quote:
Originally Posted by jggimi
I use it on all my VPS platforms also, but hd77 was specifically asking about personal workstation uses. For workstations, its the same reason for me as for my servers: simplicity of operation, code and documentation correctness, and the Project's goals.Start a thread, post your dmesg and audio details, and maybe one of the forum members can help with that.
|
My mistake, I should have been more focused on my reading. For the audio issue, I will at one point try to use sniodctl/sndiod.conf to solve my issue but I didn't want to try to solve it here. I just wanted to point that I find some edges of OpenBSD are still rough and it may not suit everyone to have to configure their sound through the CLI.
Quote:
Originally Posted by shep
In chorus with the previous replies with an emphasis on the non-working audio:
The project essentially wrote their own audio server. It is much simpler than pulseaudio/wireplumber. A good starting point is the succinct and up-to-date Multimedia section in the FAQ. The FAQ also has links to the man pages for sndioctl(1). If you are luckly, the sound is just muted (possiblely a Fn key on the laptop).
Further down FAQ13 there are additional sections on choosing the default audio device and debugging. |
I did read this page and this is my main appeal in using OpenBSD: the very good documentation. I'm certain I will be able to make it work but the steps to do so are not as easy as using pavucontrol on a linux/PulseAudio (linux+PulseAudio?) setup. This is not something which blocks me from using OpenBSD but one something should be aware of when trying OpenBSD, be prepared you will have to read documentation to manipulate this OS.
I think this reading aspect is clearly beneficial since when I first started using Linux I would mostly scourge the forums to find a solution mostly copy/pasting ready-made answers. Nowadays I read the man pages (or Info manual) and I will find my solution by understanding the software I'm manipulating.