toledano

[Log in to get rid of this advertisement]

hi,

I just installed openBSD on my laptop.
how do i disable the pcspeaker without the GUI?
thanks,

danny.

ocicat

Study Section 5.9 of the FAQ:

http://openbsd.org/faq/faq5.html#BootConfig

...as this explains how drivers can be disabled. Of course, you will also need to study the output of dmesg(8) to find what driver is associated with your speaker.

custangro

I did this on Linux...it may work on BSD

-C

ocicat

It won't. OpenBSD does not have a rmmod command.

custangro

Well then I'm all out of ideas

toledano

hi,

by using the dmesg I see:
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0

I used the command "sudo config -e /bsd" (and also "sudo config -e -u -o bsd.new /bsd")
and disabled midi,spkr and pcppi(i am not sure which one to disable so I disabled all).
the pc speaker still works..
what else could I try?

ocicat

Given that this is turning into a fishing expedition, you may want to made a copy of /bsd which has not been altered. Although I don't see that the disabling the drivers discussed may be problematic later, it is good to have the insurance that you can easily return to a default configuration if necessary.

In the dmesg(8) output, I suspect you will also see audio(4) drivers listed. You may want to disable all of these as well.

If this does not disable speaker output, you will need to post the output of dmesg(8). The drivers discussed thus far are generic, but without knowledge of your exact hardware, I will not be able to help you further.

GazL

Is "mixerctl outputs.spkr_mute=on" not suitable?

bigearsbilly

wirecutters?

:-)

why?

X: xset -b
vim: set visualbell

personally I love morse -p

ocicat

This is actually a good question to raise.

I guess I had dismissed this in my own mind is because some beeps go directly to the speaker; somehow the audio subsystem is bypassed, but I may be vaguely recalling hardware-specific information. I don't routinely gut the system.

But the OP should try this suggestion. It may very well be a viable answer for the hardware used.

toledano

hey,

@GazL : you are half right thanks for the suggestion.
@ocicat : thanks for your help.

the command : "mixerctl inputs.spkr.mute=on" WORKS!

GazL

You're welcome. My hardware doesn't create mixerctl entries under inputs for spkr only under outputs. Sounds (forgive the pun) like your sound hardware is layed out differently to mine.

Anyway, Glad you resolved it.