![]() |
|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
![]() |
|
Thread Tools | Display Modes |
|
||||
![]()
According to the 6.7 upgrade faq:
Quote:
Quote:
Quote:
Quote:
I've read both the sndioctl and mixerctl man pages and have no idea where to go from here. Any assistance will be appreciated. Thanks |
|
|||
![]()
Add yourself to staff and operator groups.
|
|
|||
![]()
I was already in staff. I added myself to operator and everything works fine.
Thanks very much. |
|
|||
![]()
jggimi - I wouldn't even begin to know how to provision sndiod, altho I would appreciate a hint.
I will say that I spent most of yesterday working with mpd and ncmpcpp trying to convince it that there really was a ~/Music directory and it did contain files. But all i touched were those 2 config files. Is it possible I messed something up there? I think I found it. In ~/.mpdconf in the audio output section for sndio I changed mixer_type from hardware to software. Now it works running mpv but not with ncmpcpp (I guess because ncmpcpp has it's own way of adjusting volume). Last edited by stanl; 22nd May 2020 at 05:01 PM. Reason: additional details |
|
||||
![]()
Audio applications that use the sndio(7) library don't need access to audio hardware (/dev/audio0, /dev/audio1, ...). By default, OpenBSD runs the sndiod(8) sound server (with no provisioning options) in order to serve this hardware to these audio applications. Device names used in sndio(7) are not device files found in /dev, and so are not managed by user/group. With a default configuraiton, sndiod(8) will automatically "own" all your audio devices and dole them out to sndio applications when requested.
There are exceptions. 1) Non-default configurations of sndiod or sndiod not running, and 2) two different users attempting to use the same audio device at the same time. If the default audio device is requested by an application, the sndio(7) library will first attempt to connect with snd/0, the first device managed by sndiod(8). If the device is not available through sndiod(8), the library will then try to connect to the raw audio device -- rsnd/0. This will then translate into access to the appropriate device special file such as /dev/audio0. These device special files are owner:group root:_sndiop, and have no world access, so I'm not clear why adding your userid to the operator group made a difference. I could guess that there was a reboot, under the assumption that sndiod was not running or the audio device was in use by another userid. If you have multiple users trying to use the same device, you must share sndio(7) cookies as noted in the AUTHENTICATION section of the sndio(7) man page. You can check your sndiod(8) provisioning with $ grep sndiod /etc/rc.conf* . The default is without options, so a default configuration would be an empty sndiod_flags= field. You can check to see if sndiod(8) is running with $ pgrep -lf sndiod .
|
|
|||
![]()
Thanks, jggimi. A person could learn a lot just reading your posts,
|
![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
root on ZFS | gkontos | FreeBSD Installation and Upgrading | 12 | 18th December 2009 09:43 AM |
ZFS root and linproc 7.2-RC1 | wnsi | FreeBSD Installation and Upgrading | 0 | 20th April 2009 06:54 PM |
ssh root | Nk2Network | OpenBSD Security | 22 | 8th April 2009 06:59 PM |
NTOP as root | sniper007 | FreeBSD Security | 0 | 27th January 2009 07:42 PM |
Wheel Can't su root | MetalHead | OpenBSD General | 2 | 22nd November 2008 12:44 AM |