| 1 |
On Monday 14 Aug 2017 19:31:48 Robin Atwood wrote: |
| 2 |
> On Monday 14 August 2017, Mick wrote: |
| 3 |
> > On Sunday 13 Aug 2017 20:27:12 Robin Atwood wrote: |
| 4 |
> > > On Saturday 12 August 2017, Alexander Kapshuk wrote: |
| 5 |
> > > However, grepping dmesg was interesting: |
| 6 |
> > > |
| 7 |
> > > # grep HDA /var/log/dmesg |
| 8 |
> > > [ 10.981754] input: HDA Digital PCBeep as |
| 9 |
> > > /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/inp |
| 10 |
> > > ut9 |
| 11 |
> > > [ 10.981963] input: HDA Intel MID Mic as |
| 12 |
> > > /devices/pci0000:00/0000:00:1b.0/sound/card0/input10 |
| 13 |
> > > [ 10.982033] input: HDA Intel MID Dock Mic as |
| 14 |
> > > /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 |
| 15 |
> > > [ 10.982102] input: HDA Intel MID Dock Headphone as |
| 16 |
> > > /devices/pci0000:00/0000:00:1b.0/sound/card0/input |
| 17 |
> > > 12 |
| 18 |
> > > [ 10.982171] input: HDA Intel MID Headphone as |
| 19 |
> > > /devices/pci0000:00/0000:00:1b.0/sound/card0/input13 |
| 20 |
> > |
| 21 |
> > The above shows you have your laptop docked. When docked the on board |
| 22 |
> > speakers are usually disconnected. |
| 23 |
> > |
| 24 |
> > It's been a very long time since I docked a laptop and my memory is not |
| 25 |
> > very reliable, but I recall fixing a similar problem by selecting a |
| 26 |
> > different output device. I don't know if you can do this from alsamixer, |
| 27 |
> > but you should be able to do it from pulseaudio, or from whatever GUI your |
| 28 |
> > desktop provides for managing audio devices. Switch over from |
| 29 |
> > headphones/docking station to speakers and you should be OK. |
| 30 |
> |
| 31 |
> That's very interesting and would explain a lot except that I don't have a |
| 32 |
> dock! So does anybody have an idea as to why the TP has decided it's been |
| 33 |
> docked when it hasn't? There are not currently any other output devices to |
| 34 |
> select (AFAICT). |
| 35 |
> |
| 36 |
> Thanks |
| 37 |
> Robin |
| 38 |
|
| 39 |
It could be a hardware problem. Check the docking port has not been unlocked |
| 40 |
accidentally for some reason, no debris is shorting its connectors and that |
| 41 |
the BIOS menu does not report it being docked. I think the audio output |
| 42 |
device symptom is controlled by ACPI, but before blaming bugs in ACPI I'd |
| 43 |
start by looking at the hardware in the first instance. |
| 44 |
-- |
| 45 |
Regards, |
| 46 |
Mick |
Archives