[LIFEBOOK E8020, Realtek ALC260, Black SPDIF Out, Front] No sound at all

Bug #1091868 reported by Peter Golden
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi guys, I haven't had audio working from the built in speakers since installing 12.10 (it is ok on headphones). I just got this bug report come up. Regards Peter

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: alsa-base 1.0.25+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic i686
ApportVersion: 2.6.1-0ubuntu9
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: peter 26322 F.... pulseaudio
Date: Tue Dec 18 21:48:41 2012
InstallationDate: Installed on 2012-09-28 (81 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120928)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: peter 26322 F.... pulseaudio
Symptom_Jack: Black SPDIF Out, Front
Symptom_Type: No sound at all
Title: [LIFEBOOK E8020, Realtek ALC260, Black SPDIF Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2005
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.06
dmi.board.name: FJNB199
dmi.board.vendor: FUJITSU
dmi.board.version: CP242230-04
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: E8020
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd04/19/2005:svnFUJITSUSIEMENS:pnLIFEBOOKE8020:pvr:rvnFUJITSU:rnFJNB199:rvrCP242230-04:cvnFUJITSUSIEMENS:ct10:cvrE8020:
dmi.product.name: LIFEBOOK E8020
dmi.sys.vendor: FUJITSU SIEMENS
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-12-16T23:52:13.899862

Revision history for this message
Peter Golden (peter-golden) wrote :
Revision history for this message
Raymond (superquad-vortex2) wrote :

model fujitsu was removed

http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commitdiff;h=c29b3f6dd7798964d77199af4925be72a3a48349;hp=b1f58085a9c01e8ffab954fd77a45f1143edf34d

send email to the author

the previous Fujitsu model create speaker playback volume and switch at node 0x09

- HDA_CODEC_VOLUME("Speaker Playback Volume", 0x09, 0x0, HDA_OUTPUT),
- HDA_BIND_MUTE("Speaker Playback Switch", 0x09, 2, HDA_INPUT),

do pulseaudio mute pcm playback switch ?

 0x09 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Control: name="PCM Playback Volume", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals: [0x00 0x00] [0x00 0x00]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals: [0x3d 0x3d]
  Connection: 2
     0x02 0x07

Revision history for this message
Raymond (superquad-vortex2) wrote :

Node 0x10 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="PCM Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Speaker Phantom Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003f: IN OUT HP EAPD Detect Trigger ImpSense
  EAPD 0x2: EAPD
  Pin Default 0xe4011110: [Both] Line Out at Sep Right
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x09

Revision history for this message
Raymond (superquad-vortex2) wrote :

the problem is BIOS of your computer did not set the pin default of any node to [Fixed] Speaker

Node 0x0f [N/A] Speaker at Ext Rear
Node 0x10 [Both] Line Out at Sep Right
Node 0x11 [N/A] Speaker at Ext Rear
Node 0x12 [Jack] Mic at Ext Front
Node 0x13 [Jack] Line In at Sep Right
Node 0x14 [Jack] HP Out at Ext Front
Node 0x15 [N/A] Speaker at Ext Rear
Node 0x16 [Fixed] CD at Ext Drive Bar
Node 0x17 [Fixed] Aux at Oth Mobile-In

Revision history for this message
Peter Golden (peter-golden) wrote :

Hi Raymond,

Thank you for your continued support with this.

I have amended /etc/modprobe.d/alsa-base.conf so that the last line now reads

options snd-hda-intel model=generic

and this seems to have got the laptop speakers working but I have lost the headphones. If I change the model type to something else, I can get headphones back but then lose speakers.

Regards

Peter

Revision history for this message
Raymond (superquad-vortex2) wrote :

http ://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=blob_plain;f=Documentation/sound/alsa/HD-Audio.txt;hb=HEAD

if model=generic this may mean that node 0x10 is the internal speaker

use model=auto and early patching to fix the pin default of node 0x10 to 0x901701f0 [Fixed] Speaker at Int

and reboot

Revision history for this message
Raymond (superquad-vortex2) wrote :

https://launchpad.net/~diwic/+archive/hda

you can also use hda-jack-retask to fix speaker and make those pins (e.g. CD, AUX) as [N/A]

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Florian Reinhard (freinhard) wrote :

i tried the following with the information provided above, but couldn't get the speakers working:

/etc/modprobe.d/alsa-base.conf:
options snd-hda-intel model=auto,patch=snd-hda-intel-alc260-fujitsu.fw

/lib/firmware/snd-hda-intel-alc260-fujitsu.fw :
[codec]
0x10ec0260 0x10cf0000 0

[model]
auto

[pincfg]
0x10 0x901701f0

Revision history for this message
Raymond (superquad-vortex2) wrote :

http://mailman.alsa-project.org/pipermail/alsa-devel/2013-January/058146.html

you need to follow up this thread if it is a regression

the original code enable all gpio

Revision history for this message
Peter Golden (peter-golden) wrote :

Last night I tried booting from a fresh 12.04 CD - audio all works fine. Tried booting from the latest 12.10 CD and no sound from front speakers. Not sure if this helps at all? Peter

Revision history for this message
Raymond (superquad-vortex2) wrote :

> Last night I tried booting from a fresh 12.04 CD - audio all works fine.

did the speaker playback switch has any effect since node 0x09 don't support mute?

did auto mute work when you plug the headphone ?

Revision history for this message
Peter Golden (peter-golden) wrote :

On 12.04 the speakers and headphones appear in the audio control and both work at the same time unless I manually mute one or the other.

On 12.10 only the speakers appear as Digital Output (S/PDIF) built-in audio until I plug in the headphones then they are both there until I unplug the headphones again. Test Sound (Front Left/Right) only works with the headphones.

On 12.10 the headphone socket on the front of the laptop has a red light lit up which I have never seen before (have been running Ubuntu for 5 years on this machine).

Thanks

Peter

Revision history for this message
Raymond (superquad-vortex2) wrote :

[codec]
 0x10ec0260 0x10cf0000 0

[model]
 auto

[pincfg]
 0x10 0x901701f0

can you post the output of alsa-info.sh after reboot ?

does it create the speaker playback volume and speaker phantom port at node 0x09 ?

amixer -c 0 contents

did the headphone Jack kcontrol change to on when headphone is plugged ?

post of the output of hda-jack-sense-test when headphone is plugged and unplugged

or

use hda-verb to test the Jack sense or impedance with SET_PIN_SENSE and GET_PIN_SENSE

Revision history for this message
Raymond (superquad-vortex2) wrote :

> On 12.10 the headphone socket on the front of the laptop has a red light lit up which I have never seen before (have been running Ubuntu for 5 years on this machine).'

the red light is the optical output shared with headphone Jack since the previous Fujitsu model only set up the analog playback did not set up the digital playback

Revision history for this message
Raymond (superquad-vortex2) wrote :

you can turn off the red light by mute iec958 switch

Revision history for this message
Peter Golden (peter-golden) wrote :

I am attaching a copy of the alsa-info.sh output

Revision history for this message
Peter Golden (peter-golden) wrote :

and also amixer output but I do not know how to run the hda-jack-sense-test as I don't seem to have those commands

Revision history for this message
Raymond (superquad-vortex2) wrote :

https://launchpad.net/~diwic/+archive/hda

you can use hda-jack-retask to retask the node 0x10 to internal speaker

Revision history for this message
Peter Golden (peter-golden) wrote :

OK installed the additional tools but retasking 0x10 to internal speaker didn't fix it, hda-jacksense-test output below

Without Headphones plugged in
peter@LIFEBOOK-E8020:~$ sudo hda-jack-sense-test
Pin 0x12 (Black Mic): present = No
Pin 0x14 (Black HP Out): present = No
peter@LIFEBOOK-E8020:~$

With Headphones plugged in
peter@LIFEBOOK-E8020:~$ sudo hda-jack-sense-test
Pin 0x12 (Black Mic): present = No
Pin 0x14 (Black HP Out): present = Yes
peter@LIFEBOOK-E8020:~$

ATB, Peter

Revision history for this message
Raymond (superquad-vortex2) wrote :

> options snd-hda-intel model=generic

> and this seems to have got the laptop speakers working but I have lost the headphones.

can you post the output of alsa-info.sh when using model=generic ?

Revision history for this message
Peter Golden (peter-golden) wrote :

Hi Raymond, here is the output with model=generic Peter

Revision history for this message
Raymond (superquad-vortex2) wrote :

can you use hda-analyser to change the volume slider of node 0x08 for headphone when using generic model ?

amp out vale from 0x00 to 0x40

Node 0x08 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals: [0x00 0x00] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals: [0x00 0x00]
  Connection: 2
     0x02 0x07

Revision history for this message
Peter Golden (peter-golden) wrote :

When I use the generic model the Headphone is not detected when I plug it in - I only see analogue speakers which work OK. I did try adjusting the amp out value to 0x40 but it did not make any difference (I assume because the headphones weren't seen).

Node 0x08 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals: [0x00 0x00] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals: [0x40 0x40]
  Connection: 2
     0x02 0x07

The microphone was detected by the way (I have headphones with a mike as well).

Revision history for this message
Peter Golden (peter-golden) wrote :

If I set the model back to auto, the headphones work again but the speakers don't (this time they show up as Digital Output (S/PDIF).

I also noticed that the microphone does not work with model type auto

Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
Raymond (superquad-vortex2) wrote :

> When I use the generic model the Headphone is not detected when I plug it in - I only see analogue speakers which work OK. I did try adjusting the amp out value to 0x40 but it did not make any difference

you can compare the headphone with jonathan 's codec info of Kernel release: 3.3.5

http://mailman.alsa-project.org/pipermail/alsa-devel/2013-January/058148.html

Node 0x02 [Audio Output] wcaps 0x11: Stereo
  Device: name="HDA Generic", type="Audio", device=0
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM

Node 0x08 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals: [0x00 0x00] [0x80 0x80]
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals: [0x00 0x00]
  Connection: 2
     0x02 0x07

Node 0x0d [Audio Selector] wcaps 0x300101: Stereo
  Connection: 2
     0x08* 0x09

Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0000133f: IN OUT HP Detect Trigger ImpSense
    Vref caps: HIZ 50 80
  Pin Default 0x0221101f: [Jack] HP Out at Ext Front
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0xf
  Pin-ctls: 0xc0: OUT HP VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0d

Revision history for this message
Raymond (superquad-vortex2) wrote :

joanthan 's Fujitsu model has a headphone Jack mode control allow user to change the pin ctls to IN, OUT or HP

Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
  Control: name="Headphone Jack Mode", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0000133f: IN OUT HP Detect Trigger ImpSense
    Vref caps: HIZ 50 80
  Pin Default 0x0321101f: [Jack] HP Out at Ext Left
    Conn = 1/8, Color = Black
    DefAssociation = 0x1, Sequence = 0xf
  Pin-ctls: 0x40: OUT VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0d

Revision history for this message
Florian Reinhard (freinhard) wrote :

with the current drivers shipped with 12.10, is there a configuration possible that headphone and speakers work? I couldn't manage to get this working after reading through the information linked here and a lot of fiddling with hda-jack-retask.

Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]

Changed in alsa-driver (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.