Bug 228589 - Sound problems on 965 Chipset (Intel HD Audio)
Sound problems on 965 Chipset (Intel HD Audio)
Product: Fedora
Classification: Fedora
Component: system-config-soundcard (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Stransky
Depends On:
  Show dependency treegraph
Reported: 2007-02-13 16:33 EST by Chad Poe
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-19 04:31:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
scsconfig.log file that was asked to be attached (50.66 KB, application/octet-stream)
2007-03-08 16:52 EST, Chad Poe
no flags Details

  None (edit)
Description Chad Poe 2007-02-13 16:33:43 EST
Description of problem:
Sound device on my Gigabyte 965P-S3(rev1) is on the fritz. On fresh boot, I'll 
have no sound whatsoever, and the soundcard detection GUI correctly displays 
my current sound card.  However, it doesn't load the Default PCM devices; it's 
completely blank and shows no options.  I select reload audio drivers, and I 
reboot when prompted.  Upon startup, sometimes the PCM device will be listed 
as it's supposed to and I'll have sound.  Other times, there will still be no 
devices listed under PCM device and no sound.

I'm running the most recent FC6 Kernel with all updates.
Comment 1 Martin Stransky 2007-03-08 04:35:31 EST
Can you please attach /root/scsconfig.log? I should be created by
Comment 2 Chad Poe 2007-03-08 16:52:21 EST
Created attachment 149644 [details]
scsconfig.log file that was asked to be attached
Comment 3 Martin Stransky 2007-03-09 07:47:03 EST
You can try to:

remove these lines from /etc/modprobe.conf

alias snd-card-0 snd-hda-intel
options snd-hda-intel index=0

install new drivers - http://people.redhat.com/stransky/alsa/
Comment 4 Chad Poe 2007-03-17 17:33:09 EDT
Removed lines from /etc/modprobe.conf and everything seems to be working!


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