Re: FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

2021-11-16 Thread Alan Somers
Thanks!  That's just what I was looking for.

On Tue, Nov 16, 2021 at 9:20 PM Li-Wen Hsu  wrote:
>
> On Wed, Nov 17, 2021 at 11:56 AM Alan Somers  wrote:
> >
> > Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
> > 13.0-RELEASE.  Are there any images for current snapshots, and if so
> > what are their names?
> > -Alan
>
> You can use this command to list all the images built by re:
>
> gcloud compute images list --no-standard-images
> --project=freebsd-org-cloud-dev
>
> gcloud is from net/google-cloud-sdk
>
> Li-Wen



Re: FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

2021-11-16 Thread Li-Wen Hsu
On Wed, Nov 17, 2021 at 11:56 AM Alan Somers  wrote:
>
> Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
> 13.0-RELEASE.  Are there any images for current snapshots, and if so
> what are their names?
> -Alan

You can use this command to list all the images built by re:

gcloud compute images list --no-standard-images
--project=freebsd-org-cloud-dev

gcloud is from net/google-cloud-sdk

Li-Wen



FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

2021-11-16 Thread Alan Somers
Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
13.0-RELEASE.  Are there any images for current snapshots, and if so
what are their names?
-Alan



HEADS-UP: ASLR for 64-bit executables enabled by default on main

2021-11-16 Thread Marcin Wojtas
As of b014e0f15bc7 the ASLR (Address Space Layout
Randomization) feature becomes enabled for the all 64-bit
binaries by default.

Address Space Layout Randomization (ASLR) is an exploit mitigation
technique implemented in the majority of modern operating systems.
It involves randomly positioning the base address of an executable
and the position of libraries, heap, and stack, in a process's address
space. Although over the years ASLR proved to not guarantee full OS
security on its own, this mechanism can make exploitation more difficult
(especially when combined with other methods, such as W^X).

Tests on the tier 1 64-bit architectures demonstrated that the ASLR is
stable and does not result in noticeable performance degradation,
therefore it is considered safe to enable this mechanism by default.
Moreover its effectiveness is increased for PIE (Position Independent
Executable) binaries. Thanks to commit 9a227a2fd642 ("Enable PIE by
default on 64-bit architectures"), building from src is not necessary
to have PIE binaries and it is enough to control usage of ASLR in the
OS solely by setting the appropriate sysctls. The defaults were toggled
for the 64-bit PIE and non-PIE executables.

As for the drawbacks, a consequence of using the ASLR is more
significant VM fragmentation, hence the issues may be encountered
in the systems with a limited address space in high memory consumption
cases, such as buildworld. As a result, although the tests on 32-bit
architectures with ASLR enabled were mostly on par with what was
observed on 64-bit ones, the defaults for the former are not changed
at this time. Also, for the sake of safety the feature remains disabled
for 32-bit executables on 64-bit machines, too.

The committed change affects the overall OS operation, so the
following should be taken into consideration:
* Address space fragmentation.
* A changed ABI due to modified layout of address space.
* More complicated debugging due to:
  * Non-reproducible address space layout between runs.
  * Some debuggers automatically disable ASLR for spawned processes,
making target's environment different between debug and
non-debug runs.

The known issues (such as PR239873 or PR253208) have been fixed in
HEAD up front, however please pay attention to the system behavior after
upgrading the kernel to the newest revisions.
In order to confirm/rule-out the dependency of any encountered issue
on ASLR it is strongly advised to re-run the test with the feature
disabled - it can be done by setting the following sysctls
in the /etc/sysctl.conf file:
kern.elf64.aslr.enable=0
kern.elf64.aslr.pie_enable=0

The change is a result of combined efforts under the auspices
of the FreeBSD Foundation and the Semihalf team sponsored
by Stormshield.

Best regards,
Marcin



Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Ludovit Koren
> Hans Petter Selasky  writes:

> On 11/16/21 20:59, Ludovit Koren wrote:
>>> Hans Petter Selasky  writes:
>> > Hi,
>> >> It is not working...
>> >> Just a thought... Could not be the problem how are the apps built
>> >> (chromium, firefox), i.e. which options are set on?
>> > No, the default should work out of the box.
>> > What does "which virtual_oss_cmd" output?
>> which virtual_oss_cmd
>> /usr/local/sbin/virtual_oss_cmd
>> > Maybe /usr/local/bin is not in your PATH?
>> env
>> SHELL=/usr/local/bin/bash
>> WORDLIST=/usr/home/koren/ispell.words
>> crt=24
>> EDITOR=vi
>> ENV=/usr/home/koren/.shrc
>> PWD=/usr/home/koren
>> LOGNAME=koren
>> 
TEXINPUTS=.:/usr/local/lib/texmf/tex//:/usr/local/share/texmf/tex//:/usr/local/share/texmf-dist/tex//:/usr/home/koren/others:/usr/home/koren/mytex:/usr/home/koren/projects/interpre/manual/english
>> MANPATH=/usr/share/man:/usr/X11R6/man:/usr/local/man:/usr/local/pgsql/man
>> HOME=/usr/home/koren
>> LANG=C.UTF-8
>> EXINIT=set redraw wm=8
>> TEXEDIT=/usr/local/bin/emacs +%d %s
>> SSH_CONNECTION=192.168.2.16 15340 192.168.2.19 22
>> PGLIB=/usr/local/pgsql/lib
>> TERM=xterm
>> USER=koren
>> MORE=-cei
>> mail=/usr/spool/mail/koren
>> DISPLAY=localhost:11.0
>> SHLVL=1
>> PAGER=more
>> MM_CHARSET=UTF-8
>> PS1=\! \h|\w>
>> SSH_CLIENT=192.168.2.16 15340 22
>> PGDATA=/usr/local/pgsql/data
>> host=jedi
>> 
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/home/koren/bin
>> BLOCKSIZE=K
>> MAIL=/usr/spool/mail/koren
>> SSH_TTY=/dev/pts/11
>> _=/usr/bin/env
>> >> regards,
>> >>
>> > Can you show the commands you are running and the result
>> printed in
>> > the terminal.
>> virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp1.0
>> virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp2.0
>> virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp1
>> virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp2
>> no output
>> 

> Hi,

> Maybe the output and input are two different DSP devices.

> Try using the -P /dev/dsp1 and -R /dev/dsp0 options instead to
> sepecify each device separately.


Still the same result...

lk



Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Hans Petter Selasky

On 11/16/21 20:59, Ludovit Koren wrote:

Hans Petter Selasky  writes:


 > Hi,
 >> It is not working...
 >> Just a thought... Could not be the problem how are the apps built
 >> (chromium, firefox), i.e. which options are set on?

 > No, the default should work out of the box.

 > What does "which virtual_oss_cmd" output?

which virtual_oss_cmd
/usr/local/sbin/virtual_oss_cmd

 > Maybe /usr/local/bin is not in your PATH?

env
SHELL=/usr/local/bin/bash
WORDLIST=/usr/home/koren/ispell.words
crt=24
EDITOR=vi
ENV=/usr/home/koren/.shrc
PWD=/usr/home/koren
LOGNAME=koren
TEXINPUTS=.:/usr/local/lib/texmf/tex//:/usr/local/share/texmf/tex//:/usr/local/share/texmf-dist/tex//:/usr/home/koren/others:/usr/home/koren/mytex:/usr/home/koren/projects/interpre/manual/english
MANPATH=/usr/share/man:/usr/X11R6/man:/usr/local/man:/usr/local/pgsql/man
HOME=/usr/home/koren
LANG=C.UTF-8
EXINIT=set redraw wm=8
TEXEDIT=/usr/local/bin/emacs +%d %s
SSH_CONNECTION=192.168.2.16 15340 192.168.2.19 22
PGLIB=/usr/local/pgsql/lib
TERM=xterm
USER=koren
MORE=-cei
mail=/usr/spool/mail/koren
DISPLAY=localhost:11.0
SHLVL=1
PAGER=more
MM_CHARSET=UTF-8
PS1=\! \h|\w>
SSH_CLIENT=192.168.2.16 15340 22
PGDATA=/usr/local/pgsql/data
host=jedi
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/home/koren/bin
BLOCKSIZE=K
MAIL=/usr/spool/mail/koren
SSH_TTY=/dev/pts/11
_=/usr/bin/env

 >> regards,
 >>

 > Can you show the commands you are running and the result printed in
 > the terminal.

virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp1.0
virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp2.0
virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp1
virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp2

no output



Hi,

Maybe the output and input are two different DSP devices.

Try using the -P /dev/dsp1 and -R /dev/dsp0 options instead to sepecify 
each device separately.


--HPS




Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Ludovit Koren
> Hans Petter Selasky  writes:

> Hi,
>> It is not working...
>> Just a thought... Could not be the problem how are the apps built
>> (chromium, firefox), i.e. which options are set on?

> No, the default should work out of the box.

> What does "which virtual_oss_cmd" output?

which virtual_oss_cmd
/usr/local/sbin/virtual_oss_cmd

> Maybe /usr/local/bin is not in your PATH?

env
SHELL=/usr/local/bin/bash
WORDLIST=/usr/home/koren/ispell.words
crt=24
EDITOR=vi
ENV=/usr/home/koren/.shrc
PWD=/usr/home/koren
LOGNAME=koren
TEXINPUTS=.:/usr/local/lib/texmf/tex//:/usr/local/share/texmf/tex//:/usr/local/share/texmf-dist/tex//:/usr/home/koren/others:/usr/home/koren/mytex:/usr/home/koren/projects/interpre/manual/english
MANPATH=/usr/share/man:/usr/X11R6/man:/usr/local/man:/usr/local/pgsql/man
HOME=/usr/home/koren
LANG=C.UTF-8
EXINIT=set redraw wm=8
TEXEDIT=/usr/local/bin/emacs +%d %s
SSH_CONNECTION=192.168.2.16 15340 192.168.2.19 22
PGLIB=/usr/local/pgsql/lib
TERM=xterm
USER=koren
MORE=-cei
mail=/usr/spool/mail/koren
DISPLAY=localhost:11.0
SHLVL=1
PAGER=more
MM_CHARSET=UTF-8
PS1=\! \h|\w>
SSH_CLIENT=192.168.2.16 15340 22
PGDATA=/usr/local/pgsql/data
host=jedi
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/home/koren/bin
BLOCKSIZE=K
MAIL=/usr/spool/mail/koren
SSH_TTY=/dev/pts/11
_=/usr/bin/env

>> regards,
>> 

> Can you show the commands you are running and the result printed in
> the terminal.

virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp1.0
virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp2.0
virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp1
virtual_oss_cmd /dev/dsp.ctl -f /dev/dsp2

no output

and trying to switch to the jack headphones  and listening output from
firefox of chrome. the sound is coming only from speakers...

lk



Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Ludovit Koren
> Goran Mekić  writes:

> On Tue, Nov 16, 2021 at 10:40:37AM +0100, Ludovit Koren wrote:
>> 
>> Hi,
>> 
>> I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty: Sat 
Nov 13 16:42:44 CET 2021
>> Here is the output from:
>> cat /dev/sndstat 
>> Installed devices:
>> pcm0:  (play/rec) default
>> pcm1:  (play)
>> pcm2:  (play)
>> Installed devices from userspace:
>> dsp:  (play/rec)
>> vdsp:  (play/rec)
>> 
>> I am running:
>> /usr/local/sbin/virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T
>> /dev/sndstat -S -i 8 -C 18 -c 18 -r 48000 -b 32 -s 512 -f /dev/dsp0
>> -c 2 -d dsp -c 18 -d vdsp -t vdsp.ctl
> This suspiciously looks like my config. For example, you're creating
> 18ch /dev/vdsp which I'm sure is not the channel count on your device.
> For start remove "-c 18 -d vdsp", that part is what you don't need.
> Anyway, why not using rc.conf and virtual_oss service? For start, it
> will create /var/run/virtual_oss which does not exist by default.

>> 
>> I am not able to redirect to different output even if I try for example:
> Be aware that something being pcm0 doesn't mean it will be parrent of
> dsp0. I'm not sure how to check which dsp device you need to use,
> though. Do ls -l /dev/dsp* and try them all.

That is exactly what I did before I tried mailing list...


lk


signature.asc
Description: PGP signature


Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Hans Petter Selasky

Hi,



It is not working...

Just a thought... Could not be the problem how are the apps built
(chromium, firefox), i.e. which options are set on?


No, the default should work out of the box.

What does "which virtual_oss_cmd" output?

Maybe /usr/local/bin is not in your PATH?



regards,



Can you show the commands you are running and the result printed in the 
terminal.


--HPS



Re: cross-compiling for i386 on amd64 fails

2021-11-16 Thread John Baldwin

On 11/15/21 8:34 PM, Michael Butler via freebsd-current wrote:

Haven't had time to identify which change caused this yet but I now get ..

===> lib/libsbuf (obj,all,install)
===> cddl/lib/libumem (obj,all,install)
===> cddl/lib/libnvpair (obj,all,install)
===> cddl/lib/libavl (obj,all,install)
ld: error: /usr/obj/usr/src/i386.i386/tmp/usr/lib/libspl.a(assert.o) is
incompatible with elf_i386_fbsd
===> cddl/lib/libspl (obj,all,install)
cc: error: linker command failed with exit code 1 (use -v to see invocation)
--- libavl.so.2 ---
*** [libavl.so.2] Error code 1

make[4]: stopped in /usr/src/cddl/lib/libavl


My guess is that this was fixed by
git: 9e9c651caceb - main - cddl: fix missing ZFS library dependencies

--
John Baldwin



Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Ludovit Koren
> Hans Petter Selasky  writes:

> On 11/16/21 11:26, Ludovit Koren wrote:
>>> Hans Petter Selasky  writes:
>> > On 11/16/21 10:40, Ludovit Koren wrote:
>> >> Hi,
>> >> I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty:
>> >> Sat Nov 13 16:42:44 CET 2021
>> >> Here is the output from:
>> >> cat /dev/sndstat
>> >> Installed devices:
>> >> pcm0:  (play/rec) default
>> >> pcm1:  (play)
>> >> pcm2:  (play)
>> >> Installed devices from userspace:
>> >> dsp:  (play/rec)
>> >> vdsp:  (play/rec)
>> >> I am running:
>> >> /usr/local/sbin/virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T
>> >> /dev/sndstat -S -i 8 -C 18 -c 18 -r 48000 -b 32 -s 512 -f /dev/dsp0
>> >> -c 2 -d dsp -c 18 -d vdsp -t vdsp.ctl
>> >> I am not able to redirect to different output even if I try for
>> >> example:
>> >> sysctl hw.snd.default_unit=1
>> >> Please see the attached output from: sysctl dev.pcm, sysctl hw.snd
>> >> and
>> >> dmesg.
>> >> I did not find any hint how to redirect the sound output to the
>> >> different
>> >> device except hw.snd.default_unit. The output remains in the default
>> >> output. Am I missing something or doing something wrong?
>> >>
>> > Hi,
>> > When you are using virtual_oss , hw.snd.default_unit is not
>> used.
>> > man virtual_oss_cmd
>> > Try this instead:
>> > virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp1
>> Unfortunately, even the command is not working.
>> 

> Maybe your virtual_oss installation needs to be upgraded then? It
> should be supported.

>pkg info virtual_oss
virtual_oss-1.2.15
Name   : virtual_oss
Version: 1.2.15
Installed on   : Tue Nov 16 12:39:14 2021 CET
Origin : audio/virtual_oss
Architecture   : FreeBSD:14:amd64
Prefix : /usr/local
Categories : audio
Licenses   : BSD2CLAUSE
Maintainer : hsela...@freebsd.org
WWW: https://github.com/hselasky/virtual_oss
Comment: Virtual OSS multi device mixer application
Options:
BLUETOOTH  : on
BT_SPEAKER : on
COMMAND: on
DEBUG  : off
EQUALIZER  : on
HTTPD  : on
Shared Libs required:
libfftw3.so.3
libsamplerate.so.0
Annotations:
FreeBSD_version: 1400041
Flat size  : 140KiB
Description:
Virtual OSS is an audio mixing application that multiplexes and
demultiplexes a single OSS device into multiple customizable OSS
compatible devices using character devices in userspace. These devices
can be used to record played back audio and mix the individual
channels in multiple ways.

Virtual OSS also supports playback and recording through bluetooth
audio devices.

WWW: https://github.com/hselasky/virtual_oss



It is not working...

Just a thought... Could not be the problem how are the apps built
(chromium, firefox), i.e. which options are set on?

regards,

lk



Re: cross-compiling for i386 on amd64 fails

2021-11-16 Thread Michael Butler via freebsd-current

I should have been more specific ..

I'm observing that "/usr/src/release/release.sh -c release-i386.conf" 
fails when targeting a i386 build on an amd64 host :-(



On 11/16/21 02:33, Warner Losh wrote:

A meta-build worked for me just now...

Warner

On Mon, Nov 15, 2021 at 9:35 PM Michael Butler via freebsd-current <
freebsd-current@freebsd.org> wrote:


Haven't had time to identify which change caused this yet but I now get ..

===> lib/libsbuf (obj,all,install)
===> cddl/lib/libumem (obj,all,install)
===> cddl/lib/libnvpair (obj,all,install)
===> cddl/lib/libavl (obj,all,install)
ld: error: /usr/obj/usr/src/i386.i386/tmp/usr/lib/libspl.a(assert.o) is
incompatible with elf_i386_fbsd
===> cddl/lib/libspl (obj,all,install)
cc: error: linker command failed with exit code 1 (use -v to see
invocation)
--- libavl.so.2 ---
*** [libavl.so.2] Error code 1

make[4]: stopped in /usr/src/cddl/lib/libavl

 imb









Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Hans Petter Selasky

On 11/16/21 11:26, Ludovit Koren wrote:

Hans Petter Selasky  writes:


 > On 11/16/21 10:40, Ludovit Koren wrote:
 >> Hi,
 >> I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty:
 >> Sat Nov 13 16:42:44 CET 2021
 >> Here is the output from:
 >> cat /dev/sndstat
 >> Installed devices:
 >> pcm0:  (play/rec) default
 >> pcm1:  (play)
 >> pcm2:  (play)
 >> Installed devices from userspace:
 >> dsp:  (play/rec)
 >> vdsp:  (play/rec)
 >> I am running:
 >> /usr/local/sbin/virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T
 >> /dev/sndstat -S -i 8 -C 18 -c 18 -r 48000 -b 32 -s 512 -f /dev/dsp0
 >> -c 2 -d dsp -c 18 -d vdsp -t vdsp.ctl
 >> I am not able to redirect to different output even if I try for
 >> example:
 >> sysctl hw.snd.default_unit=1
 >> Please see the attached output from: sysctl dev.pcm, sysctl hw.snd
 >> and
 >> dmesg.
 >> I did not find any hint how to redirect the sound output to the
 >> different
 >> device except hw.snd.default_unit. The output remains in the default
 >> output. Am I missing something or doing something wrong?
 >>

 > Hi,

 > When you are using virtual_oss , hw.snd.default_unit is not used.

 > man virtual_oss_cmd

 > Try this instead:
 > virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp1

Unfortunately, even the command is not working.



Maybe your virtual_oss installation needs to be upgraded then? It should 
be supported.


--HPS




Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Ludovit Koren
> Hans Petter Selasky  writes:

> On 11/16/21 10:40, Ludovit Koren wrote:
>> Hi,
>> I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty:
>> Sat Nov 13 16:42:44 CET 2021
>> Here is the output from:
>> cat /dev/sndstat
>> Installed devices:
>> pcm0:  (play/rec) default
>> pcm1:  (play)
>> pcm2:  (play)
>> Installed devices from userspace:
>> dsp:  (play/rec)
>> vdsp:  (play/rec)
>> I am running:
>> /usr/local/sbin/virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T
>> /dev/sndstat -S -i 8 -C 18 -c 18 -r 48000 -b 32 -s 512 -f /dev/dsp0
>> -c 2 -d dsp -c 18 -d vdsp -t vdsp.ctl
>> I am not able to redirect to different output even if I try for
>> example:
>> sysctl hw.snd.default_unit=1
>> Please see the attached output from: sysctl dev.pcm, sysctl hw.snd
>> and
>> dmesg.
>> I did not find any hint how to redirect the sound output to the
>> different
>> device except hw.snd.default_unit. The output remains in the default
>> output. Am I missing something or doing something wrong?
>> 

> Hi,

> When you are using virtual_oss , hw.snd.default_unit is not used.

> man virtual_oss_cmd

> Try this instead:
> virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp1

Unfortunately, even the command is not working.

lk



Re: sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Hans Petter Selasky

On 11/16/21 10:40, Ludovit Koren wrote:


Hi,

I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty: Sat Nov 13 
16:42:44 CET 2021
Here is the output from:
cat /dev/sndstat
Installed devices:
pcm0:  (play/rec) default
pcm1:  (play)
pcm2:  (play)
Installed devices from userspace:
dsp:  (play/rec)
vdsp:  (play/rec)

I am running:
/usr/local/sbin/virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T /dev/sndstat 
-S -i 8 -C 18 -c 18 -r 48000 -b 32 -s 512 -f /dev/dsp0 -c 2 -d dsp -c 18 -d 
vdsp -t vdsp.ctl

I am not able to redirect to different output even if I try for example:

sysctl hw.snd.default_unit=1


Please see the attached output from: sysctl dev.pcm, sysctl hw.snd and
dmesg.

I did not find any hint how to redirect the sound output to the different
device except hw.snd.default_unit. The output remains in the default
output. Am I missing something or doing something wrong?



Hi,

When you are using virtual_oss , hw.snd.default_unit is not used.

man virtual_oss_cmd

Try this instead:
virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp1

--HPS



sound on FreeBSD 14.0-CURRENT

2021-11-16 Thread Ludovit Koren

Hi,

I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty: Sat Nov 13 
16:42:44 CET 2021
Here is the output from:
cat /dev/sndstat 
Installed devices:
pcm0:  (play/rec) default
pcm1:  (play)
pcm2:  (play)
Installed devices from userspace:
dsp:  (play/rec)
vdsp:  (play/rec)

I am running:
/usr/local/sbin/virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T /dev/sndstat 
-S -i 8 -C 18 -c 18 -r 48000 -b 32 -s 512 -f /dev/dsp0 -c 2 -d dsp -c 18 -d 
vdsp -t vdsp.ctl

I am not able to redirect to different output even if I try for example:

sysctl hw.snd.default_unit=1


Please see the attached output from: sysctl dev.pcm, sysctl hw.snd and
dmesg.

I did not find any hint how to redirect the sound output to the different
device except hw.snd.default_unit. The output remains in the default
output. Am I missing something or doing something wrong?

Regards,

lk