Strange beep from motherboard

[noobToLinux]

Hello developers.

As the title says there is some strange beep coming from motherboard (at least from inside the box of the PC).
The topic is similar to this one:

Motherboard(?) makes weird beeping sound when using Ctrl+F

Hello, when I use Ctrl+F in websites, I can hear a weird beep coming from inside my PC, kinda like the one you hear when entering BIOS but lower pitched. It only happens as soon as Ctrl+F can’t find the word I’m looking for and I can pretty succesfully replicate it. Should I be concerned? I’m running KDE Plasma

I have tried what they comment on that topic with the command echo -e "\a" but I hear no sound from motherboard, but it is true that I see nothing related to terminal bell in konsole neither in Yakuake.

In my case I only hear the sound when I press delete key if I am typing on the browse option (the lens) on the pamac gui (Add/Remove software) and there is nothing written on it.

For example, if I browse the package ink, when I type ink I hear no beep, If I press delete 3 times, I hear no beep either, if I press it more times I hear the beep on each press (it is as fast as my finger, doesn’t seem to have any cool-down).

I don’t think this should happen and I don’t think any software should interfere with the motherboard beeps, just the BIOS.

The beep is hard to describe. The boot beep is high pitched and penetrating, but the one I am experiencing is more like an error.

In this video, despite being continuous and being some error about something, the pitch is like the boot beep, this strange one is not like this.

https://www.reddit.com/r/pcmasterrace/comments/pp6coc/motherboard_makes_loud_beeping_sound_when/

Thanks in advance.

inxi -Aazy

Audio:
  Device-1: Intel vendor: Gigabyte driver: snd_hda_intel v: kernel
    alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:f0c8 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228b
    class-ID: 0403
  Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.10.6-10-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: jack_control,qjackctl
  Server-2: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl

Maybe you see this post duplicated, I misclicked and delete my previous, sorry.

[cscs]

Maybe we are talking about the pcspkr module?

It can be useful for certain things.

But some implementations make it … really annoying.

You can test this theory by unloading the module:

sudo rmmod pcspkr

Does it still happen after that?

If not, and you are happy … then we can make it permanent by blacklisting the module.

That means creating a file such as

/etc/modprobe.d/blacklist_beep.conf

With content

# annoying beep
blacklist pcspkr

If you arent comfortable doing that yourself, or you just want something easy … you can copy+paste the following command:

printf '# annoying beep\nblacklist pcspkr' | sudo tee /etc/modprobe.d/blacklist_beep.conf

After creating the file reboot.

See the module not automatically loaded, and if it was the culprit, then no more beep.

[noobToLinux]

This worked perfectly.

Thank you very much.