There was no sound from the start.
After that I begin experimenting (I don't know was it necessary, or sound from all AppVMs should work as is).
I created a StandaloneVM (with the command "qvm-create mystandvm --standalone --label orange").
In the Qubes VM Manager I clicked "Show/Hide inactive VMs".
Then I select mystandvm and choose "VM settings" from context menu.
On the "Devices" tab I moved "00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller" to the right list.
Then I started VM with "Start/Resume VM".
After notification about successfull start I choose Firefox and went to youtube.com.
I tried to view something from xterm, it shows
[root@mystandvm ~]# lspci
00:00.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
[root@mystandvm ~]#
alsamixer shows that the Master (and all other levels) are set to their maximums.
There is no sound in the movies from youtube.
There was no sound from the start.
The sound should work...
After that I begin experimenting (I don't know was it necessary, or sound from all AppVMs should work as is).
I created a StandaloneVM (with the command "qvm-create mystandvm --standalone --label orange").
In the Qubes VM Manager I clicked "Show/Hide inactive VMs".
Then I select mystandvm and choose "VM settings" from context menu.
On the "Devices" tab I moved "00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller" to the right list.
Then I started VM with "Start/Resume VM".
After notification about successfull start I choose Firefox and went to youtube.com.
I tried to view something from xterm, it shows
[root@mystandvm ~]# lspci
00:00.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
[root@mystandvm ~]#
alsamixer shows that the Master (and all other levels) are set to their maximums.
There is no sound in the movies from youtube.
Sound should work with device left in dom0. There is pulsaudio set up to
collect sound from AppVMs and play it in dom0.
So detach sound card from standalone VM and reboot the system. Then adjust
volume in dom0. There are two places for it (check both): alsa (alsamixer,
kmix) and pulseaudio (pavucontrol).
The sound should work...
it doesn't. But OS initializes sound card at boot, because I hear very specific click when sound card is resetted.
detach sound card from standalone VM and reboot the system.
I did, still no sound
There are two places for it (check both): alsa (alsamixer, kmix)
I set maximum value through kmix (and it already was at maximum)
and pulseaudio (pavucontrol).
[myuser@dom0 ~]# sudo su -
- bash - 4.1# pavucontrol
- bash: pavucontrol: command not found
- bash - 4.1# yum install pulseaudio
Loaded plugins: presto, refresh-packagekit
file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] Could not open/read file:///var/lib/qubes/updates/repodata/repomd.xml
Trying other mirror.
Error: Cannot retrieve repository metadata (repomod.xml) for repository: qubes-dom0-cached. Please verify it's path and try again
- bash - 4.1#
I read this link - http://qubes-os.org/trac/ticket/287
and decide to switch to R2-beta2.
Now I think about how to do this, see - https://groups.google.com/d/msg/qubes-devel/E7hh8dkXG8I/L3ilGi8MyXgJ
The sound should work...
it doesn't. But OS initializes sound card at boot, because I hear very specific click when sound card is resetted.
detach sound card from standalone VM and reboot the system.
I did, still no sound
There are two places for it (check both): alsa (alsamixer, kmix)
I set maximum value through kmix (and it already was at maximum)
and pulseaudio (pavucontrol).
[myuser@dom0 ~]# sudo su -
- bash - 4.1# pavucontrol
- bash: pavucontrol: command not found
- bash - 4.1# yum install pulseaudio
Loaded plugins: presto, refresh-packagekit
file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] Could not open/read file:///var/lib/qubes/updates/repodata/repomd.xml
Trying other mirror.
Error: Cannot retrieve repository metadata (repomod.xml) for repository: qubes-dom0-cached. Please verify it's path and try again
- bash - 4.1#
I read this link - http://qubes-os.org/trac/ticket/287
and decide to switch to R2-beta2.
Use qubes-dom0-update to install software in dom0, for example:
qubes-dom0-update pavucontrol
Now I think about how to do this, see - https://groups.google.com/d/msg/qubes-devel/E7hh8dkXG8I/L3ilGi8MyXgJ
I've already responded to this message.
Use qubes-dom0-update to install software in dom0, for example:
qubes-dom0-update pavucontrol
[myuser@dom0 ~]$ sudo qubes-dom0-update pavucontrol
Fri Sep 6 13:38:37 UTC 2013
connect: Connection refused
Checking for dom0 updates
Running command on VM: 'firewallvm'...
connect: Connection refused
connect: Connection refused
This means something is wrong with firewallvm... "sudo xl console firewallvm"
should give you access to its console, then you can check /var/log/messages.