From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D5AD81581F0 for ; Sat, 25 Jan 2025 15:30:05 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id C1707343574 for ; Sat, 25 Jan 2025 15:30:05 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id F20DA11043B; Sat, 25 Jan 2025 15:28:54 +0000 (UTC) Received: from mail.muc.de (mail.muc.de [193.149.48.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id 221BB11042D for ; Sat, 25 Jan 2025 15:28:52 +0000 (UTC) Received: (qmail 97659 invoked by uid 3782); 25 Jan 2025 16:28:50 +0100 Received: from muc.de (p4fe15779.dip0.t-ipconnect.de [79.225.87.121]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 25 Jan 2025 16:28:50 +0100 Received: (qmail 15204 invoked by uid 1000); 25 Jan 2025 15:28:49 -0000 Date: Sat, 25 Jan 2025 15:28:49 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Help getting my new loudspeakers working, please! Message-ID: References: <7a7091b4-b331-1616-4701-03bdfe89a3de@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7a7091b4-b331-1616-4701-03bdfe89a3de@gmail.com> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: 89dac67b-8aa2-4e6f-86ef-9b8e46abc1d7 X-Archives-Hash: 517b99404a6b334c4c54a7e2750ac326 Hello, Dale. On Fri, Jan 24, 2025 at 14:53:30 -0600, Dale wrote: > Alan Mackenzie wrote: > > Hello, Gentoo. > > I've finally got around to buying a pair of new loadspeakers for my new > > (as of 2024-08) PC. The experience has not been relaxed and obvious. > > I have connected the speakers up physically. I have made the necessary > > settings in the kernel configuration, rebuilt and rebooted into it. So > > far, so good. > > Then I attempt to use alsamixer to unmute the speakers and, hopefully get > > some sound out of them. This is where my problems start. > > alsamixer displays just one object, labelled S/PDIF in the middle of the > > screen. I don't have an S/PDIF connection, just an ordinary audio cable > > with a green 3.5 mm jack plug at each end. > > How do I configure alsamixer to show me appropriate things, such as > > volume settings and so on. > > I've tried following https://wiki.gentoo.org/wiki/ALSA, but it is most > > unhelpful. It describes in detail a few complicated setups, presumably > > for those who understand the basics and want such a setup. It doesn't > > say how to get a simple configuration, such as my own, working. > > I have a /etc/asound.conf file set up, as suggested in the above doc, as: > > defaults.pcm.!card Generic > > defaults.pcm.!device 0 > > defaults.pcm.!ctl Generic > > .. > > Before I spend hours reading documentation, could some kind person > > familiar with these things perhaps give me a tip to getting my speakers > > working. > > Setting up loudspeakers shouldn't be this difficult. > > Thanks in advance for any help! > I have a similar setup.  I made my speakers from a spare set that didn't > fit my car and wasn't worth sending back.  Made a nice little box for > them.  My monitor sits on it.  :-D  Anyway, I use KDE and the new > pipewire thingy.  To be fair, pipewire does work better, mostly.  Still, > you have to unmute in alsa, kmix and all that before using pipewire.  > If the devices are not showing up, either you didn't load the modules if > you use those or didn't enable the right drivers in the kernel.  > Otherwise, they should show up.  I don't think there is any magic to > this.  It never has been for me anyway.  You're absolutely right. I was missing CONFIG_SND_USB_AUDIO, a setting that builds in the USB sound driver. I'm not sure how I worked that out, but probably somewhere on my Internet searches the concept USB sound chip came up. It doesn't mean a setup where you plugh the loudspeakers into a USB socket; it's to do with the internal communication inside the chip set, or something like that. So now it "works". My new speakers are fine on my old box, but on the new one, an MSI Tomahawk board, there's a constant crackling, and a sound something like somebody playing the bongos added in for good measure. In short, utterly unusable. This seems to have been a problem with this make of board for many months, but MSI have failed to fix it. I can see my still shiny new machine (from August) going back to its seller as a guarantee case. > Even if you don't use KDE and pipewire, it should still show up if the > right drivers are being used.  I'd double or triple check my drivers > first thing.  Using the command lspci -k might help.  Make sure > something is loaded then make sure it is the correct drivers.  If > unsure, booting media from CD/DVD/USB stick and doing a lspci -k there > should help, if sound works.  I find Knoppix works well with this.  > Every system that can have sound, has it with Knoppix.  > Hope that helps.  It did, thanks! > Dale > :-)  :-)  -- Alan Mackenzie (Nuremberg, Germany).