Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Mar 2003 23:58:24 -0700
From:      <soralx@cydem.org.ua>
To:        freebsd-bugs@FreeBSD.org
Cc:        keramida@FreeBSD.org
Subject:   Re: misc/41772: can't disable keybell
Message-ID:  <200303032358.24855.soralx@cydem.org.ua>
In-Reply-To: <200302282209.h1SM97rk041499@freefall.freebsd.org>
References:  <200302282209.h1SM97rk041499@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> http://www.freebsd.org/cgi/query-pr.cgi?pr=41772

> Synopsis: can't disable keybell
> State-Changed-From-To: feedback->closed
> State-Changed-By: keramida
> State-Changed-When: Fri Feb 28 14:07:44 PST 2003
> State-Changed-Why:

> Pilot error.
No, the CVR reveals that the pilot is not guilty -
from my previous message you can see that I just
mistakely wrote 'NO' instead of 'OFF' in the first
message. I also wrote that I'll try to find the
problem, but when I got new case, I forgot about
the PR, 'cause I just didn't connect the
beepers [stereo! :)]

> Setting keybell to NO doesn't disable beeping.
correct
It should be set to 'OFF', right?
I also tried playing with 'kbdcontrol', i.e.:
`kbdcontrol -b off`, `kbdcontrol -b quiet.off`. It all
leads to the same result: short clicking noises. I tested
this on many x86 platforms by now, even through a sound card
to headphones - the same result.
'kbdcontrol' seems to operate properly. For example:
`kbdcontrol 2048.400` gives proper 400Hz sound for ~2s.
It just seems like 'off' option doesn't prevent syscons
completely from touching the timer and/or sending anything to
port 61h

> Hopefully similar misunderstandings will be avoided in the
> future
OK, I'll be sending more clear and proper PRs ;)

I wonder why people haven't noticed such KB behavior before?
Maybe, I'm really doing something wrong?

03.03.2003; 23:51:04
[SorAlx]  http://cydem.org.ua/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303032358.24855.soralx>