Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Aug 2002 02:20:03 -0700 (PDT)
From:      Jens Schweikhardt <schweikh@schweikhardt.net>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: misc/41772: can't disable keybell
Message-ID:  <200208210920.g7L9K3he057114@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/41772; it has been noted by GNATS.

From: Jens Schweikhardt <schweikh@schweikhardt.net>
To: soralx@cydem.zp.ua
Cc: GNATS Bug Followup <bug-followup@FreeBSD.org>
Subject: Re: misc/41772: can't disable keybell
Date: Wed, 21 Aug 2002 11:03:57 +0200

 [Please Cc: answers to bug-followup@freebsd.org with the subject intact]
 
 On Tue, Aug 20, 2002 at 11:24:05PM -0600, soralx@cydem.zp.ua wrote:
 # > Synopsis: can't disable keybell
 # 
 # > The proper way to turn off the bell is keybell=off in rc.conf.
 # that's right, I tried this first
 # in '/etc/defaults/rc.conf' it's 'keybell=NO'
 
 Just to make my statement clear:
 keybell=NO   means "Do not run any kbdcontrol -b command at boot time"
              it does NOT mean to turn it off.
 keybell=off  means "Run kbdcontrol -b off" at boot time.
 
 # Well, that doesn't really matter - it's all the same and is not
 # working properly for me 8)
 # 
 # > If you do this on the command line, you need to redirect the tty,
 # > kbdcontrol -b off < /dev/tty
 # does the same thing, as supposed to
 # 
 # > does the trick for me on 4-STABLE.
 # as I remember, in RELEASE-2.2.7 it worked fine (or it just was
 # because of a different machine), and as I moved to FreeBSD-4.?.?,
 #  it never works for me
 # 
 # > Please confirm if it works for you as well.
 # not as I expect it to work
 
 So you have keybell=off in /etc/rc.conf and it does the following:
 # I expect the beeper to be absolutely quiet, but it just sets the
 # frequency low (about 30Hz)
 
 Hmm. I've got seven disks and a bunch of fans in my case, so I'll
 never hear anything that low and short.
 
 # As I understand it: when the 'keybell=off' is used, and terminal
 # recieves 07h, the kernel shouldn't touch the timer and send anything
 # to port 61h, but it [sets the timer(I can hear some
 # sounds) and OUTs to the port?]
 # 
 # I'll check '/usr/src/sys/isa/syscons_isa.c' (right?) for how it actually works
 # [and will learn some more C :)]
 
 Try to understand what kbdcontrol does. It writes an escape sequence
 to the stderr stream which you can capture with (bourne shell, not csh)
 
 $ kbdcontrol -b off 2>esc
 $ od -bc esc
 0000000  033 133 075 060 073 060 102                                    
          033   [   =   0   ;   0   B                                    
 0000007
 
 Investigate how the syscons driver interprets this escape sequence
 and you should be on the right track. Good luck!
 
 # > PS: This is more appropriately asked on questions@ mailing
 # >     list than in a PR.
 # well, I thought I tested it enough to report a PR
 
 Well, if you had given all that extra information about using keybell=off
 and 30Hz stuff... better give too much details that too little. We can
 always ignore what is not relevant, but if something relevant is missing
 like in your case, we are guided in the wrong direction.
 
 
 Regards,
 
 	Jens
 -- 
 Jens Schweikhardt http://www.schweikhardt.net/
 SIGSIG -- signature too long (core dumped)

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?200208210920.g7L9K3he057114>