Bug 797248

Summary: Creative X-Fi HD USB Sound Card fails to work.
Product: [Fedora] Fedora Reporter: abyss.7
Component: alsa-libAssignee: Lennart Poettering <lpoetter>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: brendan.jones.it, jkysela, lkundrak, lpoetter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 11:54:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description abyss.7 2012-02-24 16:54:48 UTC
Description of problem:
Sometimes after wake up from suspend or power up of PC, the mentioned sound doesn't work at all, or only volume control works.

Version-Release number of selected component (if applicable):
alsa-lib 1.0.25-1
pulseaudio 0.9.23-1

How reproducible:
Very often.

Steps to Reproduce:
1. Suspend PC.
2. Wake up PC.
3. Try to play some sound.
  
Actual results:
Sound card is not detected (Dummy output is used instead in Pulseaudio) or is detected but gives no sound.

Expected results:
Card is detected and sound can be heard.

Additional info:
dmesg show following when card is detected, but without sound:

[  549.954464] usb 1-1.4.1: new full-speed USB device number 10 using ehci_hcd
[  550.042416] usb 1-1.4.1: New USB device found, idVendor=041e, idProduct=30d7
[  550.042421] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  550.042424] usb 1-1.4.1: Product: USB Sound Blaster HD
[  550.042426] usb 1-1.4.1: Manufacturer: Creative Technology
[  550.042429] usb 1-1.4.1: SerialNumber: 000000aU
[  550.065422] ALSA sound/usb/mixer.c:846 2:0: cannot get min/max values for control 2 (id 2)
[  550.067890] input: Creative Technology USB Sound Blaster HD as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.5/input/input12
[  550.068219] generic-usb 0003:041E:30D7.000A: input,hidraw0: USB HID v1.11 Device [Creative Technology USB Sound Blaster HD] on usb-0000:00:1a.0-1.4.1/input5

dmesg show following when card is not detected at all:

[   60.675201] ALSA sound/usb/pcm.c:250 5:1:1: usb_set_interface failed
[   60.675827] ALSA sound/usb/pcm.c:250 5:1:1: usb_set_interface failed
...
(about 100 similar lines)
...
[   60.676074] ALSA sound/usb/pcm.c:250 5:1:1: usb_set_interface failed

Comment 1 obsid 2012-09-23 17:10:56 UTC
I had exactly the same problem as I've upgraded to the 3.5.4 kernel. No USB sound anymore (Altec Lansing FX5051 : ID 04d2:5051 Altec Lansing Technologies)

Someone on Archlinux experienced the same thing and made the sound back by retro-applying a patch and reverting the recent modifications added to endpoint.c and some other files.

It turned out that it worked fine for me as well. Check these links out :


https://bugs.archlinux.org/task/31646
http://www.gossamer-threads.com/lists/linux/kernel/1599995


This would probably affect a lot of USB sound systems and concern many opened bugs here.

Hope it will help.

Comment 2 Fedora End Of Life 2013-01-16 15:01:42 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 3 abyss.7 2013-01-17 04:58:56 UTC
The problem still persists - in Fedora 18.

Comment 4 Fedora End Of Life 2013-12-21 08:33:37 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 5 Fedora End Of Life 2014-02-05 11:54:49 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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