Bug 750020 - Sound gone in Fedora 16 beta -- only get dummy output device
Summary: Sound gone in Fedora 16 beta -- only get dummy output device
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-firmware
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tim Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-30 01:11 UTC by William Oliver
Modified: 2011-10-31 19:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-31 19:24:06 UTC
Type: ---


Attachments (Terms of Use)

Description William Oliver 2011-10-30 01:11:49 UTC
Description of problem: Sound
 disappeared in Fedora 16 bets

Version-Release number of selected component (if applicable):
alsa-firmware 1.0.14.1-2.fc15
alsa-lib 1.0.24.2-fc15

How reproducible:

Twice...

Steps to Reproduce:
1. Install Fedora 16 betas 
2. Do suggested updates
3. Sound goes away
  
Actual results:
No sound. Kmix shows "Dummy Output"

Expected results:

Sound

Additional info:

On intitial install, I get sound -- I haven't checked Kmix, but I get the arpeggio that normally sounds when KDE comes up.  I then go to the software manager and see that there are something like 741 pending updates.  I choose all of them and go to bed.  The next morning, all updates are successfully done but there's no sound.

Configuration:  Asus G74sx-3de laptop, Nvidia 560m graphics, On board nvidia sound.  Recently had Mint installed, and sound worked fine. I run KDE.

Also, when I tried to run alsa-info.sh, I get the error "This script requires lspci. Please install it, and re-run this script."  However, lscpi is installed.  When I checked out the alsa-info script, it seems that the sed command that the script uses returns blank.  i.e.

$lscpi
[root@localhost dev]# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation Device 1251 (rev a1)
01:00.1 Audio device: nVidia Corporation Device 0bee (rev a1)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 USB Controller: Fresco Logic FL1000G USB 3.0 Host Controller (rev 04)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)


% which lspci 2> /dev/null
/sbin/lspci

% which lspci 2>/dev/null| sed 's|^[^/]*||' 2>/dev/null
%
(nothing)

Comment 1 Tim Jackson 2011-10-31 19:24:06 UTC
Sorry but this doesn't sound like a problem with alsa-firmware.
alsa-firmware contains firmware drivers for a very small number of specialist 
sound cards only.

Please be aware that problems with sound can be caused by many different
software components within a Fedora system (including ALSA kernel modules,
PulseAudio, desktop volume controls, individual applications and more) and
you may find it easier to get some informal help to track down the problem 
before filing bugs (if necessary), so that you can file them against the 
right component and the appropriate person can help.

Help resources are listed here:
http://fedoraproject.org/en/get-help

If you still believe that your problem is with alsa-firmware, please re-open this bug with further details. Alternatively, if you identify the software causing the problem, you could change the Component accordingly and re-open it. 

Also, if you think there is a problem with alsa-info.sh, please consider that a separate issue to your sound problem.


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