Bug 896164 - Fedora 18 installed guest in VirtualBox windows 7 host no sound
Summary: Fedora 18 installed guest in VirtualBox windows 7 host no sound
Keywords:
Status: CLOSED DUPLICATE of bug 905643
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-16 18:47 UTC by brucedirector
Modified: 2013-03-20 10:20 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-20 10:20:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description brucedirector 2013-01-16 18:47:07 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier: 

I installed Fedora 18 KDE as a guest in VirtualBox 4.2.6 in a Windows7 host and there is no sound.  Fedora 17 in the same setup on the same machine has fine sound.  On the Fedora 18 install the sound card is recognized and everything else seems to work, just no sound.  I don't know how to diagnose this further.

Reproducible: Always

Comment 1 Jeremy Petersen 2013-01-29 20:27:13 UTC
I have the same issue and opened another case before seeing this one. (#905643 - https://bugzilla.redhat.com/show_bug.cgi?id=905643)

Try running the following command in a terminal window immediately after logging in...

alsactl init

You should see a message similar to this...

Found hardware: "ICH" "SigmaTel STAC9700,83,84" "AC97a:83847600" "0x8086" "0x0000"
Hardware is initialized using a generic method

... and then sound should work for you - until you reboot at least, that is. Then you'll have to run that command again.

Comment 2 brucedirector 2013-01-30 00:07:17 UTC
(In reply to comment #1)
> I have the same issue and opened another case before seeing this one.
> (#905643 - https://bugzilla.redhat.com/show_bug.cgi?id=905643)
> 
> Try running the following command in a terminal window immediately after
> logging in...
> 
> alsactl init
> 
> You should see a message similar to this...
> 
> Found hardware: "ICH" "SigmaTel STAC9700,83,84" "AC97a:83847600" "0x8086"
> "0x0000"
> Hardware is initialized using a generic method
> 
> ... and then sound should work for you - until you reboot at least, that is.
> Then you'll have to run that command again.

thanks that worked.  Hope there's a more permanent fix, as I don't want to completely switch over from f17 until this is fixed.

Comment 3 Jaroslav Kysela 2013-03-20 10:20:45 UTC

*** This bug has been marked as a duplicate of bug 905643 ***


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