Bug 771506 - my nvidia sound card keeps flipping its card ID after reboot
Summary: my nvidia sound card keeps flipping its card ID after reboot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-utils
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-03 22:32 UTC by Don Zickus
Modified: 2013-02-13 15:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 15:04:07 UTC
Type: ---


Attachments (Terms of Use)

Description Don Zickus 2012-01-03 22:32:27 UTC
Description of problem:
I am trying to get pulseaudio to work with surround sound on my xbmc setup.  However everytime I think I have it configured, I reboot to make sure everything continues to work. 

I notice when I reboot sound device stops working. The reason is the card ID as shown in the 'aplay -l' output keeps switching from 0 to 1 and vice versa.

My current workaround is to keep rebooting until the card ID goes back to 0, so my hardcoded 'hw=0,3' in my ~/.asoundrc works.

This is annoying.  The reason I believe it is flipping is because I have a usb video camera plugged in (for skype).

I also believe the problem goes away when I disable pulseaudio (though my alsa and pulseaudio knowledge is small), but I am not entirely sure.

Version-Release number of selected component (if applicable):
This has been happening to me since F15.  But currently I have the latest from yum updates installed on my machine (since new year's).

How reproducible:
Fairly.  It can usually flip after about 10 reboots or so.

Steps to Reproduce:
1. boot up
2. aplay -l
3. reboot
4. aplay -l
  
Actual results:
sometimes the sound card id is 0, sometimes it is 1.  The device id stays the same.

Expected results:


Additional info:

This is one of those Acer Revo machines with an NVidia ION chipset (and Intel Atom 32-bit cpu).

Yeah, I am using the binary NVidia blob. :-(

Comment 1 Fedora End Of Life 2013-01-16 14:05:14 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 Fedora version prior to Fedora 16'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 Fedora 16 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 Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 15:04:09 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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 
Fedora please feel free to reopen this bug against that version.

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


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