[REGRESSION] Mobo Asus P5Q * needs newer Alsa to work again SPDIF

Bug #352556 reported by Luigi Maselli
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Jaunty by Luigi Maselli
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Jaunty by Luigi Maselli

Bug Description

I upgraded to Jaunty and the alsa provided doesn't work with the integrated chip:

82801JI (ICH10 Family) HD Audio

The fix is to compile by yourself alsa and force "options snd-hda-intel model=6stack-dig" in
/etc/modprobe.d/alsa-base.conf

please see: http://ubuntuforums.org/showthread.php?t=1100747

Revision history for this message
Jim Perkins (jimperkins) wrote :

i can verify this bug.

i also can verify that the default configuration is set to utilize the spdif header on the midpoint of the mobo.
newer alsa kernel modules can handle mobo's with multiple spdif's

Revision history for this message
Jim Perkins (jimperkins) wrote :

i would like to to comment on the OP message here.

he wrote you need to compile alsa and force the model within the alsa-base.conf file.
this is incorrect.

if you compile the newer alsa kernel drivers and install those drivers into /lib/$(uname -r)/
it is not necessary to force the model.

if you force the model it is not necessary to compile the alsa kernel drivers.

in the post linked to by the OP i have provided links to when various commits occurred within the alsa kernel driver.

this all got off track when a user was using the spdif header on the midpoint of the mobo and got the output nid changed to 0x10 from 0x06.

I am on vacation this week so am I am away from the mobo in discussion, but will be willing to help whatever I can from memory. next week I can provide log outputs . etc.

affects: ubuntu → alsa-driver (Ubuntu)
Revision history for this message
Luke Yelavich (themuso) wrote :

Using the default drivers that came with Jaunty, and without your modprobe options in /etc/modprobe.d, are you able to get sound if you kill PulseAudio, or load pavucontrol to adjust the pulseaudio default device?

affects: alsa-driver (Ubuntu) → linux (Ubuntu)
Changed in alsa-driver (Ubuntu):
assignee: nobody → ubuntu-audio
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Luke Yelavich (themuso) wrote :

Ah, its a digital audio issue.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Krakapuk (krakapuk) wrote :

I confirm the problem with the integrated chip Intel Corporation 82801JI (ICH10 Family) HD Audio Controller of an Asus P5LD2 motherboard. The S/PDIF (IEC958) output doesn't work.
Adding the line "options snd-hda-intel model=6stack-dig" at bottom of /etc/modprobe.d/alsa-base.conf solved the problem for me.
I don't try to compile the newer alsa kernel drivers (1.0.19)

Thanks Randy !

Revision history for this message
Andy Whitcroft (apw) wrote : Re: [Bug 352556] Re: [REGRESSION] Mobo Asus P5Q * needs newer Alsa to work again SPDIF

On Sat, Apr 25, 2009 at 03:53:09PM -0000, Krakapuk wrote:
> I confirm the problem with the integrated chip Intel Corporation 82801JI (ICH10 Family) HD Audio Controller of an Asus P5LD2 motherboard. The S/PDIF (IEC958) output doesn't work.
> Adding the line "options snd-hda-intel model=6stack-dig" at bottom of /etc/modprobe.d/alsa-base.conf solved the problem for me.
> I don't try to compile the newer alsa kernel drivers (1.0.19)

If a specific model= quirk works for you then we are likely missing a
codec selection quirk for your hardware. Could you attach dmidcode and
lspci -vvnn output to the bug for your machine. We can then look see if
that one is missing.

-apw

Revision history for this message
Luigi Maselli (grigio) wrote :

00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e]
 Subsystem: ASUSTeK Computer Inc. Device [1043:82fe]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 22
 Region 0: Memory at fe8f8000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
   ExtTag- RBE- FLReset+
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
  LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Virtual Channel <?>
 Capabilities: [130] Root Complex Link <?>
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

Revision history for this message
Krakapuk (krakapuk) wrote :

here is lspci -vvnn
00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e]
 Subsystem: ASUSTeK Computer Inc. Device [1043:82fe]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 22
 Region 0: Memory at f7ff8000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
   ExtTag- RBE- FLReset+
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
  LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Virtual Channel <?>
 Capabilities: [130] Root Complex Link <?>
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

Do you want a specific part of the DMIdecode result?

Revision history for this message
Jim Perkins (jimperkins) wrote :

Andy W said...

If a specific model= quirk works for you then we are likely missing a
codec selection quirk for your hardware. Could you attach dmidcode and
lspci -vvnn output to the bug for your machine. We can then look see if
that one is missing.

..

the model specific quirk was already in place. Then someone requested that the output nid was changed to 0x10 from 0x06, so they could utilize the spdif on the mobo header.

my research and comments regarding this are here. links to the above mentioned change and how newer versions of the alsa module can handle multiple spdif are also listed there.

http://ubuntuforums.org/showthread.php?p=6989493#post6989493

I was surprised that jaunty was released without even a mention of this in the release notes, but probably not many people are using the spdif.

thanks for taking the time to investigate this issue

randy perkins

Revision history for this message
js84 (js84) wrote :

Hello,

I'm also curious about the status of this bug. I've read your thread but am not sure where to go forward on fixing this myself. Sorry for the trouble.

Revision history for this message
Omega (atrauzzi) wrote :

Would like to add that I have an ASUS P5Q motherboard.

I added the line to /etc/modprobe/alsa-base.conf and sound started working for me -- but only for a bit into each playback attempt. Eventually sound tanks and I have to quit/terminate all applications that emit sound.

Also doesn't seem to handle multiple sources of playback simultaneously.

Any tricks to getting this going cleanly?

Revision history for this message
Jim Perkins (jimperkins) wrote : Re: [Bug 352556] Re: [REGRESSION] Mobo Asus P5Q * needs newer Alsa to work again SPDIF

Hello
Sorry I dont have any suggestions for you.
I never had the sound stop, but I really only used rhythmbox to play
local flac files. that worked well for me.
never tried multiple sources either.

during my initial investigation newer version of the alsa kernel driver
worked with this mobo. hopefully the ubuntu team will update the asla
kernel driver during the next development cycle. I oughta check to see
if this has been done :)

randy

On Mon, 2009-05-18 at 00:06 +0000, Omega wrote:
> Would like to add that I have an ASUS P5Q motherboard.
>
> I added the line to /etc/modprobe/alsa-base.conf and sound started
> working for me -- but only for a bit into each playback attempt.
> Eventually sound tanks and I have to quit/terminate all applications
> that emit sound.
>
> Also doesn't seem to handle multiple sources of playback simultaneously.
>
> Any tricks to getting this going cleanly?
>

Revision history for this message
Omega (atrauzzi) wrote :

It would be nice if control over the various outputs, combinations of outputs and output types was abstracted more clearly.

I'm still experiencing issues while running a WINE app where if Pidgin plays any sound, it kills sound entirely on the machine until reboot.

Revision history for this message
Jim Perkins (jimperkins) wrote :

I looked over the current alsa-driver source for Ubuntu Karmic and this issue is not resolved.
https://launchpad.net/ubuntu/karmic/+source/alsa-driver/1.0.19.dfsg-3ubuntu1

this is from my memory and reviewing the current code. It should be used as a guide to solving this issue,
not a step by step fix.

the quick fix is in file /alsa-driver-1.0.19.dfsg/alsa-kernel/pci/hda/patch_realtek.c

around line 7118 is as follows #define ALC1200_DIGOUT_NID 0x10
change the 0x10 to 0x06 and compile and install
this will disable the mid board spdif and enable the rear spdif

the permanent fix is to update the alsa-driver
the latest snapshots of the alsa driver ,alsa-driver-1.0.20.0.g75fc7.0.gfb064
should work out of the box as definitions have been added to the patch_realtek.c
to define "slave_dig_outs"

How do I go about getting this bug assigned to Karmic ??

thanks
rperkins

Jim Perkins (jimperkins)
Changed in alsa-driver (Ubuntu):
assignee: nobody → Ubuntu Audio Team (ubuntu-audio)
status: New → Confirmed
Changed in linux (Ubuntu):
assignee: Ubuntu Audio Team (ubuntu-audio) → nobody
Revision history for this message
Brad Figg (brad-figg) wrote :

The latest development release of Ubuntu is entering Beta. Please
consider taking the time to download the latest live-image from
http://cdimage.ubuntu.com/releases/lucid and see if this issue still
exists.

If the issue does still exist; in a terminal (Applications->Accessories->Terminal)
please execute the following command:
    apport-collect -p alsa-driver 352556

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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 linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Paul White (paulw2u) wrote :

alsa-driver task did not expire due to assignment
Last comment re issue was in 2009
No reply to comment #16 after over two years so closing

Changed in alsa-driver (Ubuntu):
assignee: Ubuntu Audio Team (ubuntu-audio) → nobody
status: Incomplete → Invalid
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.