Recent posts

Quote..I'm not sure what hardware brand or version of OPNSense you're running, but this also happened to me. I was just tinkering with it today. I have a Lenovo M720q Tiny as well as a M715q Tiny. The beep can be heard on the M715q but not on the M720q..

I'm running a Lenovo® M90n-1 Nano and encountered the same problem: No friendly OPNsense beeps on startup/shutdown. Definitely mission-critical, couldn't let it go unaddressed.

After some poking around I got it fixed. There were three separate problems:

Two different versions of the "beep" binary, one of which doesn't work on my system.
The opnsense-beep shell script calling the wrong (non-functional) version of "beep."
The opnsense start / stop beep sound definition files contain beep durations in bare integers that are interpreted as "centiseconds" by one version of beep, but as "milliseconds" in another version of beep.

There are for whatever reason multiple versions of the "beep" binary on my system. (25.7.8.) (As best I can tell it looks like one might use /dev/speaker and another version uses /dev/dsp instead? )

Each of these versions has different command-line options, and only one of them (/usr/bin/beep) actually makes sounds on my system.

Code Select

root@router:~ # ls -al /usr/bin/beep
-rwsr-xr-x  1 root wheel 10088 Nov 24 23:26 /usr/bin/beep
# This version interprets tone-length integers as millisecond values, and it
# works (makes beep noises) on my system.

root@router:~ # ls -al /usr/local/bin/beep
-r-xr-xr-x  1 root wheel 7584 Jul 21 16:21 /usr/local/bin/beep
# This version interpretes tone-length integers as centi-second values, and it 
# DOESN'T work (no sounds) on my system.

The /usr/local/sbin/opnsense-beep script, as-shipped, calls /usr/local/bin/beep.

So I altered the script it to call the other version of beep instead. I also altering the command-line flags as-required.

Code Select

root@router:/usr/local/sbin # diff opnsense-beep opnsense-beep-ORIGINAL
69c69
<      /usr/bin/beep  -F "${NOTE}" -D "${DURATION}" -g 100
---
>         /usr/local/bin/beep -p "${NOTE}" "${DURATION}"

#  The -g 100 argument optionally boosts the output volume to 100%, which is necessary
#  for the tiny speaker in this system.

But after doing this, while I could type, say, /usr/bin/beep -F 1000 -D 100 from the command line and it would work fine, the opnsense-beep script still wasn't working.

I finally checked the beep-sound definition files in /usr/local/etc/opensense-beep.d/* and found them to have DURATION lengths of "25." Those lengths were meant for the (non-working, on my system)
/usr/local/bin/beep, which takes tone lengths in units of centi-seconds. (Hundredths of a second.)

But /usr/bin/beep takes tone lengths in units of milliseconds, with 50 ms the lowest-valid value. Once I changed the beep definitions in the /usr/local/etc/opensense-beep.d/* tune definition files from "25" to "250," my modified version of /usr/local/sbin/opnsense-beep started producing the usual friendly beep sounds.

FWIW, here are the audio devices as-reported on my system:

Code Select

root@router:~ # cat /dev/sndstat
Installed devices:
pcm0: <Realtek ALC235 (Analog 2.0+HP/2.0)> (play/rec) default
pcm1: <Intel Kaby Lake (HDMI/DP 8ch)> (play)
No devices installed from userspace.

#89

25.7, 25.10 Series / Re: Dropdown Menu Error on Viv...

Last post by charles.adams - Today at 03:52:26 AM

For others who run into this issue. It is caused by setting a chromium flag:

You cannot view this attachment.

If you set it wrong you will get this problem on selection boxes that the browser can't guess at the autofill.

#90

25.7, 25.10 Series / Re: Dropdown Menu Error on Viv...

Last post by charles.adams - Today at 03:45:22 AM

They are from 25.10

Pages 1 ... 7 8 9 10