Bug 711572

Summary: Kernel update break [some] hardware correct detection
Product: [Fedora] Fedora Reporter: TheDuke <thedukevip>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
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: 2011-06-20 19:51:28 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 TheDuke 2011-06-07 19:22:42 UTC 
Description of problem:
I am using two distinct machines, one at work and one at home,
The one at work is equipped with a Hauppage WinTV-HVR 4000
The one at home is equipped with a VIA VT2020 sound codec (hda intel)
Both detected and worked correctly with kernel "2.6.38.6-26.rc1.fc15.x86_64",
after a kernel update to "2.6.38.6-27.fc15.x86_64" and "2.6.38.6-27.fc15.x86_64" they both stopped working. 

Version-Release number of selected component (if applicable):
"2.6.38.6-27.fc15.x86_64" and "2.6.38.6-27.fc15.x86_64"

How reproducible:
Every time

Steps to Reproduce:
1. Boot into one of the mentioned kernels
2. Play sound file
3. ls "/dev/dvb"
  
Actual results:
2-> No sound is heard, pavucontrol shows sound being "played"
3-> ls: cannot access /dev/dvb: No such file or directory

Expected results:
Sound plays OK
DVB-S/DVB-T adapter0 is shown under /dev/dvb

Additional info:
alsa-info.sh output: http://www.alsa-project.org/db/?f=34efa3454a24d601ab7556a6ea907abc8ad4ec7f
Comment 1 TheDuke 2011-06-20 19:51:28 UTC 
Found the solution, it was obvious/stupid
launch alsamixer,
choose the correct sound card,
turn the "independant hp" option off,
Sound works again

But still don't know why the kernel update turned on this option.