From owner-freebsd-questions@freebsd.org Wed Aug 8 21:16:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0236A106B709 for ; Wed, 8 Aug 2018 21:16:56 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 66F85948A9 for ; Wed, 8 Aug 2018 21:16:56 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.64.203]) by mrelayeu.kundenserver.de (mreue105 [212.227.15.183]) with ESMTPA (Nemesis) id 0MKZOx-1fnmfQ1ubv-001y08; Wed, 08 Aug 2018 23:16:39 +0200 Date: Wed, 8 Aug 2018 23:16:37 +0200 From: Polytropon To: Victor Sudakov Cc: sergio lenzi , freebsd-questions@freebsd.org Subject: Re: Alternative to x11/gnome3 ? Message-Id: <20180808231637.1be9d4e6.freebsd@edvax.de> In-Reply-To: <20180808163315.GB66626@admin.sibptus.transneft.ru> References: <20180511090813.GA21919@admin.sibptus.transneft.ru> <1526039986.18202.5.camel@k1.com.br> <20180731014358.GA925@admin.sibptus.transneft.ru> <20180731195608.40cee639.freebsd@edvax.de> <20180801024324.GA20419@admin.sibptus.transneft.ru> <20180801162045.f3653b7d.freebsd@edvax.de> <20180808163315.GB66626@admin.sibptus.transneft.ru> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:++Fz6uoN8gt3fCy+sTq9w7uMkkImXC7gfp1bGBiUZke1INf1gni O9qO/tIbLePPvWGgQe5GRpw5PzDPEq5RgQuFr30UsqtGEXw6sEDmQ2Hkz1eg8zQ+6gudf/M hpd2xCquKfxbO6/cGp4qSHS/hzgfp6AytTW04VecwjyMya18PEsU5WF0qyaqAJmBf7fS+05 oCvVJ7ZFZTqdK6hlDB2Zg== X-UI-Out-Filterresults: notjunk:1;V01:K0:v93F8qMBoEA=:3OkmDNLOpBK4o+LnNLsKzK atmazY1lR2+66vUuPhilsBKcV+j802W63DYC6KJRnfRtUEvU6EBe3kiPZXWzXPpbwWyZWQ6mr vx4oT+skTBDBv8FtaJITstSsSJX42aEQWZ8BrSePQkmgV6CBov6UnlsWTCFVSI1ebSn78KoKq 09qPMbjZv3fkU8hrYH6B+gFqj5qL5PVIV1rJtUICl4ifrEsaN24ZYrH/aK8l81wPCFTo83T3W koOchMFONZM2oq05gtXnMkz5gHeFfTRgXZad4wVlr5/f443AlTlt0FyFSXb4M2PmZ/T6ZMu9x UAXH4m31DZpwYRBS3A9cRB6jN+tOsCuUn0KgjnG4nwIXt8T2inJNMdhp9B9uCNDfirz/bitYw VJWxQardz/eYKDoeOi9bHxJLKPoB/oXCSuD/WR7zEbQ2FaxtTmYDRkEywSdxfTP7qtmmdu3sx BqcErq6ZTDyZuqL1rH8/vB42Jnkwq2CKzei1MQSYXhJxZdsrYxJZCXBrLjql9DeqeBnGWlHht o4wqsp3znUxttx9pIWOUuzMaBP7dn5n+IQHNuLRezHQ3vCY2TzPU8teANIsBc0UpqImv633Wu UNM/WnQY/t8UJnAm8+VWfiGHeWaTLt6KLJmgtNzoDsawol89vL2LYkdprqPBsOA5ts9giq5J4 6Yb9ei2sePHLrQXbOBUwhHt/GlYgTnhTLJSfomuJr4Leggoq4dbRPZMyxvgKRFOZJTgla/dB+ /NgvAiA9JUi+MAHm X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2018 21:16:57 -0000 On Wed, 8 Aug 2018 23:33:15 +0700, Victor Sudakov wrote: > Polytropon wrote: > > [dd] > > > > > > 2. The sound control app in Mate is completely unrelated to the real > > > > > sound system of FreeBSD (as of 11.2 and mate-1.18.0). The volume and > > > > > input/output controls do nothing. I have to use the good old > > > > > /usr/sbin/mixer and "sysctl hw.snd.default_unit" to manipulate with > > > > > sound. Is this my misconfiguration or Mate's fault? > > > > > > > > Is it using the wrong mixer? Can you select a different mixer > > > > device for the Gnome / Mate mixer control? > > > > > > What's "Mate mixer control" ? The Mate sound app lists all my > > > soundcards correctly (maybe it just takes them from /dev/sndstat) but > > > selecting any of the devices and trying to set parameters (set volume > > > or test speakers) does exactly nothing. > > > > Okay, so you've already checked that more than one mixer > > can be present in the system (/dev/mixer*), and none can > > be manipulated. > > Yes, I have 5 mixers: /dev/mixer{0,1,2,3,4} > > /dev/mixer0 is manipulated by the volume control at the top bar. > I actually had to write a script to figure it out: > > #!/bin/sh > mv ~/tmp/mix1 ~/tmp/mix0 > for i in 0 1 2 3 4 > do > echo mixer$i >> ~/tmp/mix1 > mixer -f /dev/mixer$i >> ~/tmp/mix1 > done > diff -u ~/tmp/mix0 ~/tmp/mix1 My assumption is: The first mixer device it finds (usually /dev/mixer0) will be used. But how to change this? a) Check if there is a command line switch (like -f to the mixer program) to select the mixer which should be manipulated. But how to check? With "man ", the question arises how the mixer control is actually called. From a bit of googling I found "mate-mixer" and "mate-volume-control-applet" as possible names. There probably won't be a manpage for them, because documentation is often considered "not needed" over there in GUI Linux land... :-( Maybe this is a possible starting point: https://www.linuxquestions.org/questions/slackware-14/mate-1-10-sound-mixer-4175545660/ b) Use FreeBSD's sysctl facility to change the mixer order. With the device.hints file, this could be possible (so /dev/mixer1 assigned to the front connectors becomes /dev/mixer0 which is then controlled by the Mate volume control slider). It's all nice and fine if the defaults work for you. But if you have a slightly different requirement, it seems you're doomed. A little sidenote for the script: For "for i in 0 1 2 3 4", you could use "for i in `seq 0 4`". :-) > > > > I fully understand that most GUI software is ported from Linux, > > > > it's not a native BSD development result, so maybe it expects > > > > some ALSA instead of the standard OSS... > > > > > > A question to you as you said you are a Mate user. Does this sound app > > > work personally for you? Can you at least set the volume and run the > > > speaker test from it? > > > > I can only talk about the normal volume control accessed > > from the top bar: It works. The one slider present changes > > the master volume. The result can be checked from a terminal > > with the system's "mixer" command afterwards. > > I have 5 mixers: /dev/mixer{0,1,2,3,4} > > How do you select which mixer would be connected to the volume slider > in the top bar? In my configuration, moving this slider changes the > volume on /dev/mixer0 (Rear Analog), and I'd prefer to associate it > with /dev/mixer1 (Front Analog). Hve you considered using a different mixer program? I've just tried ye olden xmixer: it has both "man xmixer" and a way to select the mixer via "xmixer -m ". There's still something that I just thought of: What if inside Mate, ALSA is being used? L stands for Linux. Could that be a reason why there is the narrowminded assumption that "only one mixer in the system" seems the way the mixer works? > > Sidenote: I'm not a Mate user, but I have a few Mate users. > > I'm primarily a WindowMaker user myself. :-) > > Oh, but WindowMaker is not a DE, it's just a WM. Exactly! :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...