From owner-freebsd-questions@FreeBSD.ORG Thu Mar 24 22:12:18 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E346106564A for ; Thu, 24 Mar 2011 22:12:18 +0000 (UTC) (envelope-from mailing@alokat.org) Received: from smtp.alokat.org (smtp.alokat.org [46.4.186.11]) by mx1.freebsd.org (Postfix) with ESMTP id 3476A8FC18 for ; Thu, 24 Mar 2011 22:12:18 +0000 (UTC) Received: from smtp.alokat.org (localhost.localdomain [127.0.0.1]) by smtp.alokat.org (Postfix) with ESMTP id 4D78F112500A0 for ; Thu, 24 Mar 2011 23:12:17 +0100 (CET) Received: from Mugin.fritz.box (188-192-38-254-dynip.superkabel.de [188.192.38.254]) by smtp.alokat.org (Postfix) with ESMTPSA id 2CE5311250079 for ; Thu, 24 Mar 2011 23:12:16 +0100 (CET) Message-ID: <4D8BC1A8.8030509@alokat.org> Date: Thu, 24 Mar 2011 23:11:52 +0100 From: Alokat User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110324 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4D8BA955.3090506@alokat.org> <20110324215257.4da534c4.freebsd@edvax.de> <4D8BBD03.4010909@alokat.org> <20110324230459.3f5f56c6.freebsd@edvax.de> In-Reply-To: <20110324230459.3f5f56c6.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV using ClamSMTP Subject: Re: Sound with FN Button X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2011 22:12:18 -0000 On 03/24/11 23:04, Polytropon wrote: > On Thu, 24 Mar 2011 22:52:03 +0100, Alokat wrote: >> On 03/24/11 21:52, Polytropon wrote: >>> On Thu, 24 Mar 2011 21:28:05 +0100, Alokat wrote: >>>> Hi, >>>> >>>> how can I use the FN Buttons to regular the sound? >>>> I'm using fluxbox. >>> Use the "xev" program to check which keysymbols (or at >>> least codes) are output by those keys. For example, on >>> my Sun keyboard I have those for audio: >>> >>> 141 >>> 142 >>> 143 >>> >> I get an output like this: >> >> FocusOut event, serial 31, synthetic NO, window 0x1800001, >> mode NotifyGrab, detail NotifyAncestor >> >> FocusIn event, serial 31, synthetic NO, window 0x1800001, >> mode NotifyUngrab, detail NotifyAncestor >> >> KeymapNotify event, serial 31, synthetic NO, window 0x0, >> keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 >> >> FocusOut event, serial 31, synthetic NO, window 0x1800001, >> mode NotifyGrab, detail NotifyAncestor >> >> FocusIn event, serial 31, synthetic NO, window 0x1800001, >> mode NotifyUngrab, detail NotifyAncestor >> >> KeymapNotify event, serial 31, synthetic NO, window 0x0, >> keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > You need to look for those events: > > KeyPress event, serial 27, synthetic NO, window 0x2000001, > root 0x73, subw 0x0, time 3923776537, (162,2), root:(271,490), > state 0x10, keycode 154 (keysym 0xffd4, F23), same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False > > KeyRelease event, serial 27, synthetic NO, window 0x2000001, > root 0x73, subw 0x0, time 3923776635, (162,2), root:(271,490), > state 0x10, keycode 154 (keysym 0xffd4, F23), same_screen YES, > XLookupString gives 0 bytes: > XFilterEvent returns: False > > The 2nd line, the information in the middle is important: > "keycode 154 (keysym 0xffd4, F23)": It indicates that the > keycode generated has been identified with the code 154, > and this code is already mapped to the symbol F23. This > is (just for completeness) the "Cut" key of the 2x5 field > to the left. > > Erm... just a side question... you're refering to pressing > the Fn key with a function key (e. g. Fn+F1) for volume > control, or are there other special keys for volume? I'm > asking this as in the past, volume control was managed by > the BIOS (I think), but NOT by the operating system or > application programs. This means it was possible to change > the volume INDEPENDENTLY from any driver. I'm not sure if > this is still the case. Maybe - just MAYBE - you need a > hardware and software (!) specific driver to do those > basic things... history teaches that all the "simple things" > that worked in the past are a high mountain to climb today... > thanks to YOU, hardware manufacturers! :-) > > Please understand the paragraph as follows: MAYBE (!!!) it's > not even possible to do what you're intending. > > No I don't .. I thought it, but the volume buttons are extra buttons - without FN.