Bug 1651 - No soundcards found using a VIA Technologies, Inc.|VT1708/A [Azalia HDAC] audio chip
Summary: No soundcards found using a VIA Technologies, Inc.|VT1708/A [Azalia HDAC] aud...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 21:21 CEST by Greg Shifler
Modified: 2012-12-02 14:32 CET (History)
2 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments
output of dmidecode (14.23 KB, text/plain)
2011-10-03 17:38 CEST, Greg Shifler
Details

Description Greg Shifler 2011-06-06 21:21:57 CEST
Description of problem:

When using an MSI mobo with a  VIA Technologies, Inc.|VT1708/A [Azalia HDAC] audio chip, the Mageia 1 release can not find the audio chip. I have tried to set up my sound card with the MCC gui using pulseaudio, I have also disabled pulseaudio and tried using alsaconf with alsamixer. I should note here that I have used this audio card without any problems on Mandriva 2009.0 > 2010.0.


Version-Release number of selected component (if applicable):

Here is some more info:

[greg@halfway ~]$ uname -a
Linux halfway 2.6.38.7-desktop-1.mga #1 SMP Sun May 22 12:29:42 UTC 2011 i686 i686 i386 GNU/Linux
[greg@halfway ~]$ lspcidrake -v | fgrep -i AUDIO
snd_hda_intel   : VIA Technologies, Inc.|VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (vendor:1106 device:3288 subv:1462 subd:7253) (rev: 10)
[greg@halfway ~]$ grep sound-slot /etc/modprobe.conf
alias sound-slot-0 snd_hda_intel
[greg@halfway ~]$ /sbin/lsmod | egrep snd_hda_intel
snd_hda_intel          32093  0 
snd_hda_codec          90505  1 snd_hda_intel
snd_pcm                88011  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_page_alloc         14036  2 snd_hda_intel,snd_pcm
snd                    60934  11 snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
[greg@halfway ~]$ /sbin/chkconfig --list alsa
alsa            0:off   1:off   2:on    3:on    4:on    5:on    6:off   7:off
[greg@halfway ~]$ /sbin/chkconfig --list sound
sound           0:off   1:off   2:on    3:on    4:on    5:on    6:off   7:off
[greg@halfway ~]$ cat /proc/asound/cards
--- no soundcards ---
[greg@halfway ~]$ aplay -l
aplay: device_list:240: no soundcards found...


Do you need more info?
Comment 1 Greg Shifler 2011-07-11 15:54:11 CEST
(In reply to comment #0)


I have found that the problem is the way the newer Linux kernels use ACPI to enumerate all the PCI host bridges, and part of the host bridge description is the â_CRSâ (current resource settings) property, which lists the address space used by the bridge.

I found this information here:
http://article.gmane.org/gmane.linux.kernel/947909

I have added 'pci=use_csr' as a kernel boot parameter on my system and this has resolved the issue. I now have sound.


[greg@halfway ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: VT82xx [HDA VIA VT82xx], device 0: ALC883 Analog [ALC883 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: VT82xx [HDA VIA VT82xx], device 1: ALC883 Digital [ALC883 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
Comment 2 Greg Shifler 2011-07-11 17:06:05 CEST
I can't seem to edit my comment. 

This is a typo: (I have added 'pci=use_csr' as a kernel boot parameter)

It should be  'pci=use_crs'
Comment 3 Manuel Hiebel 2011-10-03 01:23:09 CEST
Thomas, is that something related to the kernel ?

CC: (none) => tmb

Comment 4 Thomas Backlund 2011-10-03 01:30:06 CEST
yep.

please attach output of dmidecode to this bugreport, so we can add it to kernel auto-detection

Source RPM: (none) => kernel

Comment 5 Greg Shifler 2011-10-03 17:38:20 CEST
Created attachment 889 [details]
output of dmidecode

Here's the output of dmidecode:
Manuel Hiebel 2011-10-29 15:57:02 CEST

Assignee: bugsquad => tmb

Comment 6 Marja Van Waes 2012-02-01 07:33:59 CET
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.


@ tmb
Please set status to ASSIGNED, if possible. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me in this report again ;)

CC: (none) => marja11

Comment 7 Marja Van Waes 2012-05-09 15:25:30 CEST
3-monthly ping
Comment 8 Marja Van Waes 2012-07-06 15:05:04 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 9 Manuel Hiebel 2012-11-05 16:52:57 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 10 Manuel Hiebel 2012-12-02 14:32:23 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.