NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/54243: beeping woes with -current
>Number: 54243
>Category: kern
>Synopsis: beeping woes with -current
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed May 29 00:05:00 +0000 2019
>Originator: David Holland
>Release: NetBSD 8.99.41 (20190528)
>Organization:
>Environment:
System: NetBSD macaran 8.99.41 NetBSD 8.99.41 (MACARAN) #54: Tue May 28 18:10:56 EDT 2019 dholland@macaran:/usr/src/sys/arch/amd64/compile/MACARAN amd64
Architecture: x86_64
Machine: amd64
>Description:
I updated the kernel today and beeps in X, which have been loud and
obnoxious since nat-audio was merged, are now even worse -- they are
very loud by default, and also they're now staticky/not rendered
right, which is quite abrasive.
>How-To-Repeat:
startx; echo ^G.
I'm not sure to what extent beeps on the console share the problem.
Ability to experiment is somewhat limited when people are around.
I have "wsbell* at spkr?" in my kernel config because otherwise beeps
don't work at all (a comment says "module by default", against the
modules policy, which I assume is why), and get these attachments:
pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
spkr0 at pcppi1: PC Speaker
wsbell0 at spkr0 mux 1
hdaudio0 at pci0 dev 27 function 0: HD Audio Controller
hdaudio0: interrupting at msi1 vec 0
hdafg1 at hdaudio0: vendor 10ec product 0662
hdafg1: DAC00 2ch: Speaker [Jack], HP Out [Jack]
hdafg1: DIG01 2ch: SPDIF Out [Jack]
hdafg1: ADC02 2ch: Line In [Jack], Mic In [Jack]
hdafg1: 2ch/2ch 44100Hz 48000Hz 96000Hz PCM16 PCM20 PCM24 AC3
audio0 at hdafg1: full duplex, playback, capture, mmap, independent
audio0: slinear_le:16 2ch 48000Hz, blk 40ms for playback
audio0: slinear_le:16 2ch 48000Hz, blk 40ms for recording
spkr1 at audio0: PC Speaker (synthesized)
wsbell1 at spkr1 mux 1
The overt problem is spkr1; I can hear that the PC speaker is also
beeping but can't hear it clearly over the other, so I can't tell if
it's also messed up.
>Fix:
No idea.
Home |
Main Index |
Thread Index |
Old Index