From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7E6CB1396D0 for ; Mon, 14 Aug 2017 16:31:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E84C3E0DFC; Mon, 14 Aug 2017 16:30:56 +0000 (UTC) Received: from cwt-smtp-11.totbb.com (cwt-smtp-11.totbb.com [118.175.47.77]) by pigeon.gentoo.org (Postfix) with ESMTP id E2B53E0DA7 for ; Mon, 14 Aug 2017 16:30:55 +0000 (UTC) Received: from opal.binro.org (node-1kx.pool-101-108.dynamic.totbb.net [101.108.8.1]) by cwt-smtp-11.totbb.com (Postfix) with ESMTP id 7C7F41ACC for ; Mon, 14 Aug 2017 23:30:46 +0700 (ICT) Received: from opal.binro.org (localhost.localdomain [127.0.0.1]) by opal.binro.org (8.14.9/8.14.9) with ESMTP id v7EGUkBs010724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 14 Aug 2017 23:30:46 +0700 Received: (from robin@localhost) by opal.binro.org (8.14.9/8.14.9/Submit) id v7EGUkHh010721 for gentoo-user@lists.gentoo.org; Mon, 14 Aug 2017 23:30:46 +0700 From: Robin Atwood To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Something started muting the sound Date: Mon, 14 Aug 2017 23:30:45 +0700 User-Agent: KMail/1.13.7 (Linux/4.3.3-gentoo; KDE/4.14.33; x86_64; ; ) References: <201708122049.48700.robin@binro.org> <201708141931.48664.robin@binro.org> <1873478.rr6Sr3T1y7@dell_xps> In-Reply-To: <1873478.rr6Sr3T1y7@dell_xps> X-Face: .c^^1Tm5bSr;@/t2T;-0HM`{~wj)F]2C]Zr#!Ig5fi&$LV1E^;5jL{]08F@tj{f3,U(I[9 ;7R4jB8A7|mw7{K\OYFzCL_e/tAb)0_@07[e.}H`OE*na@7m=Op1.s0v3_3*|?#l|XD}n* ARBV@IdaVd!V&bo;Z/TEb}oJi_(}3VOa^tj;$zlk96>K*hb>PYbe6J`'7qh`?m!!/k]ezl _VIifMR#4kg*"'n/S&^4@4: 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 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_1AdkZcOn6nFxRmp" Content-Transfer-Encoding: 7bit Message-Id: <201708142330.45920.robin@binro.org> X-TOTBB-NET-MailScanner-Information: Please contact the ISP for more information X-TOTBB-NET-MailScanner-ID: 7C7F41ACC.A6B33 X-TOTBB-NET-MailScanner: Found to be clean X-TOTBB-NET-MailScanner-SpamScore: s X-TOTBB-NET-MailScanner-From: robin@binro.org X-Spam-Status: No X-Archives-Salt: 68585c89-86de-434e-b9ca-425cd54c3875 X-Archives-Hash: cc10630c8237a5b89d432c98cc35b152 --Boundary-01=_1AdkZcOn6nFxRmp Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit On Monday 14 August 2017, Mick wrote: > On Monday 14 Aug 2017 19:31:48 Robin Atwood wrote: > > That's very interesting and would explain a lot except that I don't have > > a dock! So does anybody have an idea as to why the TP has decided it's > > been docked when it hasn't? There are not currently any other output > > devices to select (AFAICT). > > It could be a hardware problem. Check the docking port has not been > unlocked accidentally for some reason, no debris is shorting its > connectors and that the BIOS menu does not report it being docked. I > think the audio output device symptom is controlled by ACPI, but before > blaming bugs in ACPI I'd start by looking at the hardware in the first > instance. The docking slot is clear, there is nothing in the BIOS about docking and acpitool doesn't report anything about the docking state. The Dock option is on in the ACPI section of the kernel config. Robin -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ---------------------------------------------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary-01=_1AdkZcOn6nFxRmp Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: 7bit

On Monday 14 August 2017, Mick wrote:

> On Monday 14 Aug 2017 19:31:48 Robin Atwood wrote:

> > That's very interesting and would explain a lot except that I don't have

> > a dock! So does anybody have an idea as to why the TP has decided it's

> > been docked when it hasn't? There are not currently any other output

> > devices to select (AFAICT).

>

> It could be a hardware problem. Check the docking port has not been

> unlocked accidentally for some reason, no debris is shorting its

> connectors and that the BIOS menu does not report it being docked. I

> think the audio output device symptom is controlled by ACPI, but before

> blaming bugs in ACPI I'd start by looking at the hardware in the first

> instance.

 

The docking slot is clear, there is nothing in the BIOS about docking and acpitool doesn't report anything about the docking state. The Dock option is on in the ACPI section of the kernel config.

 

Robin

 

--

----------------------------------------------------------------------

Robin Atwood.

 

"Ship me somewheres east of Suez, where the best is like the worst,

Where there ain't no Ten Commandments an' a man can raise a thirst"

from "Mandalay" by Rudyard Kipling

----------------------------------------------------------------------

 

 

 

 

 

 

 

 

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary-01=_1AdkZcOn6nFxRmp--