Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Mon, March 5, 2018 10:18 pm, Allen Larocque wrote: > OK, we've made progress. However, I'm not sure why this change has > happened. > > Now aplay -l sees two audio devices - one built-in, one HDMI. > > > Dom[0] volume control now sees a 'built in audio Analog Stereo' > (hardware) and 'Simultaneous output to built-in Audio' (virtual?). > > > When sound is playing , the volume bars fluctuate as expected, but still > no sound coming out. > > - A > > > > On Sunday, 4 March 2018 18:43:51 UTC-8, awokd wrote: > >> On Mon, March 5, 2018 2:34 am, Allen Larocque wrote: >> >> >> >>> 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family >>> High >>> Definition Audio Controller (rev 04) >>> >> >>> Kernel driver in use: snd_hda_intel >>> Kernel modules: snd_hda_intel >>> >> >> Looks like it loaded fine. In Dom0 volume control, is it selected as >> your Output Device? Can't think of any other reason why it wouldn't show >> in aplay -l. My R3.2 system has similar issues with multiple HDMI audio devices. In my case, I think it's sending it over DP to one of the monitors' headphone jacks; haven't figured out a way to steer it where I want it to go. In your case, again in dom0 volume control, scroll all the way to the right to the Configuration tab and try setting it to different Profiles. You may also need to assign individual VMs under Playback to the correct audio adapter if it doesn't default to it. If that still doesn't fix it, you might be running into the same thing as me. Maybe there's some command line magic. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3cc4a133a84e4f45ecfe93058f37f598.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
OK, we've made progress. However, I'm not sure why this change has happened. Now aplay -l sees two audio devices - one built-in, one HDMI. Dom[0] volume control now sees a 'built in audio Analog Stereo' (hardware) and 'Simultaneous output to built-in Audio' (virtual?). When sound is playing , the volume bars fluctuate as expected, but still no sound coming out. - A On Sunday, 4 March 2018 18:43:51 UTC-8, awokd wrote: > On Mon, March 5, 2018 2:34 am, Allen Larocque wrote: > > > > 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High > > Definition Audio Controller (rev 04) > > > Kernel driver in use: snd_hda_intel > > Kernel modules: snd_hda_intel > > Looks like it loaded fine. In Dom0 volume control, is it selected as your > Output Device? Can't think of any other reason why it wouldn't show in > aplay -l. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4ad8ed11-7a9d-46b5-aad9-636f0763fe40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Mon, March 5, 2018 2:34 am, Allen Larocque wrote: > 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High > Definition Audio Controller (rev 04) > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel Looks like it loaded fine. In Dom0 volume control, is it selected as your Output Device? Can't think of any other reason why it wouldn't show in aplay -l. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/03deb0d4801cd026b7a924969fb36d94.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Sunday, 4 March 2018 17:56:27 UTC-8, awokd wrote: > On Mon, March 5, 2018 1:23 am, Allen Larocque wrote: > > Thanks Awokd, > > Wow, a lot of output in journalctl! > > > > > > There was an audio related error in "journalctl - b": > > [Pulseaudio]pid.c:Daemon already runninge > > > > > > Nothing referring to alsa however. > > Was expecting there'd be some indication why the driver didn't load. Can > you do a "sudo lspci -vvv", look for your audio device, and what it says > for "kernel driver in use" or if that line is missing? Hm, here's the output from sudo lspci -vvv: 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://groups.google.com/d/msgid/qubes-users/dad2a118-67df-47d9-b744-8cce1ce5c2ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Mon, March 5, 2018 1:23 am, Allen Larocque wrote: > Thanks Awokd, > Wow, a lot of output in journalctl! > > > There was an audio related error in "journalctl - b": > [Pulseaudio]pid.c:Daemon already running > > > Nothing referring to alsa however. Was expecting there'd be some indication why the driver didn't load. Can you do a "sudo lspci -vvv", look for your audio device, and what it says for "kernel driver in use" or if that line is missing? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4e3711b5926e2dcee450a1c3e3be1282.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
Thanks Awokd, Wow, a lot of output in journalctl! There was an audio related error in "journalctl - b": [Pulseaudio]pid.c:Daemon already running Nothing referring to alsa however. - A On Saturday, 3 March 2018 03:57:31 UTC-8, awokd wrote: > On Fri, March 2, 2018 4:00 am, Allen Larocque wrote: > > > I checked the qvm-pci lists and the audio driver isn't assigned to any > > VMs. This is a fresh install with the sys-USB VM on. > > You wrote "driver" here- you meant "device", right? Double check your VM > settings > Devices and make sure it's not assigned to any VM. If that > results in unassigning it from one or more, reboot afterwards. > > > As far as I can summarize the problem now: > > 1. lspci shows the audio device. > > 2. aplay-l shows 'no audio device' > > It should, if dom0 recognizes it. Look through "sudo journalctl -b" for > errors related to your audio device. > > > 3. Pulseaudio output and config tabs show no audio devices (except the > > virtual one 'simultaneous output'). > > > > I've been interpreting this as a driver issue? But unsure how to fix/ get > > the appropriate drivers > > Journalctl should give you more information to review. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f3757a04-a0e4-4bcb-a9c1-5dc06b3cf945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Fri, March 2, 2018 4:00 am, Allen Larocque wrote: > I checked the qvm-pci lists and the audio driver isn't assigned to any > VMs. This is a fresh install with the sys-USB VM on. You wrote "driver" here- you meant "device", right? Double check your VM settings > Devices and make sure it's not assigned to any VM. If that results in unassigning it from one or more, reboot afterwards. > As far as I can summarize the problem now: > 1. lspci shows the audio device. > 2. aplay-l shows 'no audio device' It should, if dom0 recognizes it. Look through "sudo journalctl -b" for errors related to your audio device. > 3. Pulseaudio output and config tabs show no audio devices (except the > virtual one 'simultaneous output'). > > I've been interpreting this as a driver issue? But unsure how to fix/ get > the appropriate drivers Journalctl should give you more information to review. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8db587b36629138ee28e771ab6ec18c9.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Thursday, 1 March 2018 19:04:01 UTC-8, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > > > > > > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen > > > > > > > Larocque wrote: > > > > > > > > Hi Qubes, > > > > > > > > First time installer here, trying to get my sound to work. > > > > > > > > Strangely, speakers are broken, but headphones work fine. > > > > > > > > > > > > > > > > Anytime I move my sound device from 'available' to 'selected' > > > > > > > > in a given VM, the VM won't load and I get the 'qeexec demon' > > > > > > > > error. Same thing when I move various other devices over > > > > > > > > (tested with USB ones). I should need the audio device moved > > > > > > > > over in order for it to work in a given VM, right? > > > > > > > > > > > > > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > On Thu, Mar 01, 2018 at 03:31:22PM -0800, Allen Larocque wrote: > > Hi Yuraeitha, > > Thanks for your continued help! > > > > Ah, I think there is a misunderstanding: there is no USB soundcard as far > > as I understand it; only what is on the mainboard. So there should only be > > one soundcard. > > > > I am currently running a sys-usb VM however! > > > > Under DOM0 pauvaudio volume control, under the 'output devices' tab, there > > is no 'hardware' devices listed, only the 'simultaneous output' virtual > > device. The virtual device however is still showing fluctuating volume bar, > > so it's 'hearing' things correctly. > > > > Strangely too, now my headphones don't seem to work (they did previously). > > Generally you shouldn't need to attach sound card to specific VM - > that's what "devices" tab in VM settings is. If you do that, only that > VM will have access to it and none of others. > > What should should do instead, is to leave sound card in dom0 (unassign > from any VM you've assigned to - see qvm-pci list output), then you need > to reboot to get dom0 driver attached to the device. After this, > headphones should work again. > > Then, lets debug speakers issue - open pulseaudio volume control - now > you should have 'Output Devices' and 'Configuration' tabs. In both of > them you'll see settings related to what output should be used - try > changing it there. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqYvuoACgkQ24/THMrX > 1ywAyAf/Q2s3oe/pmBIFBWDPphvErTY9hYjMGN8wXIcDIEqfPcB7mxk2rzrL67x3 > ZgPoviJVT0QW0yr/ZtdBnGZtK/Z9J/0/3cdEqpJekvazZL0mYz5k8PmCQaaeP7yL > gGrHw7e30M+AZvA/AW5fQkGkEaJUizSdP1GgDe2FpMtkj7v3dbvCPpLTse6csd6r > JJNBXxEkoD3PdNaCJGrDm65iNW1GJy/pSrbVeUBKouFSZUPcpVhYfUpKgA/Y+xR0 > xmub02qCMcT/qp2a5wRbIYZ8zTVPHq2eFCs0wcAZpsT83uG3lunrAtr2fCjPMiO3 > VC3PIbai+zJ0bC6dYPmCHKANI5nY7A== > =v5Nw > -END PGP SIGNATURE- Thanks Marek. I checked the qvm-pci lists and the audio driver isn't assigned to any VMs. This is a fresh install with the sys-USB VM on. As far as I can summarize the problem now: 1. lspci shows the audio device. 2. aplay-l shows 'no audio device' 3. Pulseaudio output and config tabs show no audio devices (except the virtual one 'simultaneous output'). I've been interpreting this as a driver issue? But unsure how to fix/ get the appropriate drivers - A -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dbd166cf-ad76-4f1a-b265-0f4b1f5f6be0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > > > > > > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque > > > > > > wrote: > > > > > > > Hi Qubes, > > > > > > > First time installer here, trying to get my sound to work. > > > > > > > Strangely, speakers are broken, but headphones work fine. > > > > > > > > > > > > > > Anytime I move my sound device from 'available' to 'selected' in > > > > > > > a given VM, the VM won't load and I get the 'qeexec demon' error. > > > > > > > Same thing when I move various other devices over (tested with > > > > > > > USB ones). I should need the audio device moved over in order for > > > > > > > it to work in a given VM, right? > > > > > > > > > > > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. On Thu, Mar 01, 2018 at 03:31:22PM -0800, Allen Larocque wrote: > Hi Yuraeitha, > Thanks for your continued help! > > Ah, I think there is a misunderstanding: there is no USB soundcard as far as > I understand it; only what is on the mainboard. So there should only be one > soundcard. > > I am currently running a sys-usb VM however! > > Under DOM0 pauvaudio volume control, under the 'output devices' tab, there is > no 'hardware' devices listed, only the 'simultaneous output' virtual device. > The virtual device however is still showing fluctuating volume bar, so it's > 'hearing' things correctly. > > Strangely too, now my headphones don't seem to work (they did previously). Generally you shouldn't need to attach sound card to specific VM - that's what "devices" tab in VM settings is. If you do that, only that VM will have access to it and none of others. What should should do instead, is to leave sound card in dom0 (unassign from any VM you've assigned to - see qvm-pci list output), then you need to reboot to get dom0 driver attached to the device. After this, headphones should work again. Then, lets debug speakers issue - open pulseaudio volume control - now you should have 'Output Devices' and 'Configuration' tabs. In both of them you'll see settings related to what output should be used - try changing it there. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqYvuoACgkQ24/THMrX 1ywAyAf/Q2s3oe/pmBIFBWDPphvErTY9hYjMGN8wXIcDIEqfPcB7mxk2rzrL67x3 ZgPoviJVT0QW0yr/ZtdBnGZtK/Z9J/0/3cdEqpJekvazZL0mYz5k8PmCQaaeP7yL gGrHw7e30M+AZvA/AW5fQkGkEaJUizSdP1GgDe2FpMtkj7v3dbvCPpLTse6csd6r JJNBXxEkoD3PdNaCJGrDm65iNW1GJy/pSrbVeUBKouFSZUPcpVhYfUpKgA/Y+xR0 xmub02qCMcT/qp2a5wRbIYZ8zTVPHq2eFCs0wcAZpsT83uG3lunrAtr2fCjPMiO3 VC3PIbai+zJ0bC6dYPmCHKANI5nY7A== =v5Nw -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180302030241.GA8712%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
Hi Yuraeitha, Thanks for your continued help! Ah, I think there is a misunderstanding: there is no USB soundcard as far as I understand it; only what is on the mainboard. So there should only be one soundcard. I am currently running a sys-usb VM however! Under DOM0 pauvaudio volume control, under the 'output devices' tab, there is no 'hardware' devices listed, only the 'simultaneous output' virtual device. The virtual device however is still showing fluctuating volume bar, so it's 'hearing' things correctly. Strangely too, now my headphones don't seem to work (they did previously). Cheers, - A On Wednesday, 28 February 2018 11:28:49 UTC-8, Yuraeitha wrote: > On Tuesday, February 27, 2018 at 7:55:09 PM UTC+1, Allen Larocque wrote: > > Thanks for the help. > > > > The intel audio pci device is indeed listed in the qvm-pci list, and the > > pulseaudio manager is 'connected', However, under 'devices' there's nothing > > about the intel device - just 'combined monitor' as the source > > > > > > On Tuesday, 27 February 2018 10:09:37 UTC-8, Yuraeitha wrote: > > > On Tuesday, February 27, 2018 at 6:58:11 PM UTC+1, Allen Larocque wrote: > > > > Thanks Yuraeitha for the thoughtful reply! > > > > > > > > Hm. It doesn't seem to work in the other templates. I think it is a > > > > driver issue. I've tried volume etc.; and switching through the > > > > pulseaudio menus shows only 'simultaneous output' devices (which DO > > > > have actively fluctuating 'volume bars' when playback is happening!). > > > > Under 'config' there is 'no sound cards available for configuration'. > > > > I've been trying some things and let me try to clarify: > > > > > > > > 'lspci' lists '00:1b:0 Audio device: Intel Corporation 7 Serices/c210 > > > > Series Chipset Family High Definition Audio Controller (rev04)' > > > > I interpret that as the audio card being on the chipset (hence 'plugged > > > > in' automatically). > > > > > > > > 'aplay -l' however lists "no soundcards found". So alsa doesn't see it? > > > > > > > > Alsa is a deeper level than pulseaudio generally, right? So if alsa > > > > doesn't see it then it makes sense that pulseaudio doesn't either. > > > > > > > > So: how to get alsa/pulseaudio to see it? > > > > > > > > Thanks again for the gracious help! > > > > - Allen > > > > > > > > On Tuesday, 27 February 2018 04:16:15 UTC-8, Yuraeitha wrote: > > > > > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque > > > > > wrote: > > > > > > Hi Qubes, > > > > > > First time installer here, trying to get my sound to work. > > > > > > Strangely, speakers are broken, but headphones work fine. > > > > > > > > > > > > Anytime I move my sound device from 'available' to 'selected' in a > > > > > > given VM, the VM won't load and I get the 'qeexec demon' error. > > > > > > Same thing when I move various other devices over (tested with USB > > > > > > ones). I should need the audio device moved over in order for it to > > > > > > work in a given VM, right? > > > > > > > > > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > > > > > > > > > > > Thanks, > > > > > > Allen > > > > > > > > > > Also if you moved the soundcard to a direct pass-through, and the > > > > > soundcard hardware does not support the PCI pass-through feature. > > > > > Then you need to make a full restart of Qubes OS (fully power down > > > > > power in order to clean hardware memory). This is due to security > > > > > reasons. If this is hitting you, then you may want to first undo the > > > > > pass-through you made of your soundcard, and then make a full restart > > > > > before trying the above suggestions. > > > > > > np's :) > > > > > > Try compare "qvm-pci list" with lspci, it's the same list, but it'll show > > > you if the Qubes tools register the sound card. Also try look in the > > > Qubes menu --> Systems Tools --> Pulseaudio Manager. See if the sound > > > server is connected or disconnected here. > > > > > > I can't write much more right now as I'm on the road and need to close > > > the lid and move now, but checking these might get us a little closer > > > with more information. > > > > > > I can confirm I see my own soundcards with "aplay -l", so this command > > > should indeed be working in Qubes it seems? > > > > > > It sounds like a problem that is out of my league though, but I'll try to > > > help where I can. > > I apologies for the delay. I divided this post into two sections, one if you > got USB controller in dom0, and the other if you got the USB controller in an > AppVM. You'll need the link if you got your USB controller anywhere else but > your dom0. If you got a sys-usb, then your USB controller is likely tied to > that VM. If you don't have a sys-usb, and you didn't move the USB controller > yourself, then the USB controller is still likely tied to dom0. The Qubes > installer can automatically make a sys-usb at first system boot, but it won't > always
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Tuesday, February 27, 2018 at 7:55:09 PM UTC+1, Allen Larocque wrote: > Thanks for the help. > > The intel audio pci device is indeed listed in the qvm-pci list, and the > pulseaudio manager is 'connected', However, under 'devices' there's nothing > about the intel device - just 'combined monitor' as the source > > > On Tuesday, 27 February 2018 10:09:37 UTC-8, Yuraeitha wrote: > > On Tuesday, February 27, 2018 at 6:58:11 PM UTC+1, Allen Larocque wrote: > > > Thanks Yuraeitha for the thoughtful reply! > > > > > > Hm. It doesn't seem to work in the other templates. I think it is a > > > driver issue. I've tried volume etc.; and switching through the > > > pulseaudio menus shows only 'simultaneous output' devices (which DO have > > > actively fluctuating 'volume bars' when playback is happening!). Under > > > 'config' there is 'no sound cards available for configuration'. > > > I've been trying some things and let me try to clarify: > > > > > > 'lspci' lists '00:1b:0 Audio device: Intel Corporation 7 Serices/c210 > > > Series Chipset Family High Definition Audio Controller (rev04)' > > > I interpret that as the audio card being on the chipset (hence 'plugged > > > in' automatically). > > > > > > 'aplay -l' however lists "no soundcards found". So alsa doesn't see it? > > > > > > Alsa is a deeper level than pulseaudio generally, right? So if alsa > > > doesn't see it then it makes sense that pulseaudio doesn't either. > > > > > > So: how to get alsa/pulseaudio to see it? > > > > > > Thanks again for the gracious help! > > > - Allen > > > > > > On Tuesday, 27 February 2018 04:16:15 UTC-8, Yuraeitha wrote: > > > > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque > > > > wrote: > > > > > Hi Qubes, > > > > > First time installer here, trying to get my sound to work. Strangely, > > > > > speakers are broken, but headphones work fine. > > > > > > > > > > Anytime I move my sound device from 'available' to 'selected' in a > > > > > given VM, the VM won't load and I get the 'qeexec demon' error. Same > > > > > thing when I move various other devices over (tested with USB ones). > > > > > I should need the audio device moved over in order for it to work in > > > > > a given VM, right? > > > > > > > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > > > > > > > > > Thanks, > > > > > Allen > > > > > > > > Also if you moved the soundcard to a direct pass-through, and the > > > > soundcard hardware does not support the PCI pass-through feature. Then > > > > you need to make a full restart of Qubes OS (fully power down power in > > > > order to clean hardware memory). This is due to security reasons. If > > > > this is hitting you, then you may want to first undo the pass-through > > > > you made of your soundcard, and then make a full restart before trying > > > > the above suggestions. > > > > np's :) > > > > Try compare "qvm-pci list" with lspci, it's the same list, but it'll show > > you if the Qubes tools register the sound card. Also try look in the Qubes > > menu --> Systems Tools --> Pulseaudio Manager. See if the sound server is > > connected or disconnected here. > > > > I can't write much more right now as I'm on the road and need to close the > > lid and move now, but checking these might get us a little closer with more > > information. > > > > I can confirm I see my own soundcards with "aplay -l", so this command > > should indeed be working in Qubes it seems? > > > > It sounds like a problem that is out of my league though, but I'll try to > > help where I can. I apologies for the delay. I divided this post into two sections, one if you got USB controller in dom0, and the other if you got the USB controller in an AppVM. You'll need the link if you got your USB controller anywhere else but your dom0. If you got a sys-usb, then your USB controller is likely tied to that VM. If you don't have a sys-usb, and you didn't move the USB controller yourself, then the USB controller is still likely tied to dom0. The Qubes installer can automatically make a sys-usb at first system boot, but it won't always do it, for example if the USB controller can't be pass-through or if something important is tied to it, like touch devices often are. Assuming your USB controller is indeed not located in dom0, then I believe your issue is actually a split two-part issue. It might be that system sound isn't working as you also suggested by being a driver issue, but your second issue is that your other soundcard, which is based on USB, won't work because you got your USB controller in sys-sub, and if the sound is passed to the sys-usb from your USB soundcard, then it can't communicate with your speakers since it's cut off from dom0. There is a small adjustment, which I haven't tried my self, that can make this work. See the link below for the official method to do this. https://www.qubes-os.org/doc/external-audio/ I'm not 100% sure, but this
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
Thanks for the help. The intel audio pci device is indeed listed in the qvm-pci list, and the pulseaudio manager is 'connected', However, under 'devices' there's nothing about the intel device - just 'combined monitor' as the source On Tuesday, 27 February 2018 10:09:37 UTC-8, Yuraeitha wrote: > On Tuesday, February 27, 2018 at 6:58:11 PM UTC+1, Allen Larocque wrote: > > Thanks Yuraeitha for the thoughtful reply! > > > > Hm. It doesn't seem to work in the other templates. I think it is a driver > > issue. I've tried volume etc.; and switching through the pulseaudio menus > > shows only 'simultaneous output' devices (which DO have actively > > fluctuating 'volume bars' when playback is happening!). Under 'config' > > there is 'no sound cards available for configuration'. > > I've been trying some things and let me try to clarify: > > > > 'lspci' lists '00:1b:0 Audio device: Intel Corporation 7 Serices/c210 > > Series Chipset Family High Definition Audio Controller (rev04)' > > I interpret that as the audio card being on the chipset (hence 'plugged in' > > automatically). > > > > 'aplay -l' however lists "no soundcards found". So alsa doesn't see it? > > > > Alsa is a deeper level than pulseaudio generally, right? So if alsa doesn't > > see it then it makes sense that pulseaudio doesn't either. > > > > So: how to get alsa/pulseaudio to see it? > > > > Thanks again for the gracious help! > > - Allen > > > > On Tuesday, 27 February 2018 04:16:15 UTC-8, Yuraeitha wrote: > > > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque wrote: > > > > Hi Qubes, > > > > First time installer here, trying to get my sound to work. Strangely, > > > > speakers are broken, but headphones work fine. > > > > > > > > Anytime I move my sound device from 'available' to 'selected' in a > > > > given VM, the VM won't load and I get the 'qeexec demon' error. Same > > > > thing when I move various other devices over (tested with USB ones). I > > > > should need the audio device moved over in order for it to work in a > > > > given VM, right? > > > > > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > > > > > > > Thanks, > > > > Allen > > > > > > Also if you moved the soundcard to a direct pass-through, and the > > > soundcard hardware does not support the PCI pass-through feature. Then > > > you need to make a full restart of Qubes OS (fully power down power in > > > order to clean hardware memory). This is due to security reasons. If this > > > is hitting you, then you may want to first undo the pass-through you made > > > of your soundcard, and then make a full restart before trying the above > > > suggestions. > > np's :) > > Try compare "qvm-pci list" with lspci, it's the same list, but it'll show you > if the Qubes tools register the sound card. Also try look in the Qubes menu > --> Systems Tools --> Pulseaudio Manager. See if the sound server is > connected or disconnected here. > > I can't write much more right now as I'm on the road and need to close the > lid and move now, but checking these might get us a little closer with more > information. > > I can confirm I see my own soundcards with "aplay -l", so this command should > indeed be working in Qubes it seems? > > It sounds like a problem that is out of my league though, but I'll try to > help where I can. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a2e3120e-34a5-4c0e-981b-6e5a71121930%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Tuesday, February 27, 2018 at 6:58:11 PM UTC+1, Allen Larocque wrote: > Thanks Yuraeitha for the thoughtful reply! > > Hm. It doesn't seem to work in the other templates. I think it is a driver > issue. I've tried volume etc.; and switching through the pulseaudio menus > shows only 'simultaneous output' devices (which DO have actively fluctuating > 'volume bars' when playback is happening!). Under 'config' there is 'no sound > cards available for configuration'. > I've been trying some things and let me try to clarify: > > 'lspci' lists '00:1b:0 Audio device: Intel Corporation 7 Serices/c210 Series > Chipset Family High Definition Audio Controller (rev04)' > I interpret that as the audio card being on the chipset (hence 'plugged in' > automatically). > > 'aplay -l' however lists "no soundcards found". So alsa doesn't see it? > > Alsa is a deeper level than pulseaudio generally, right? So if alsa doesn't > see it then it makes sense that pulseaudio doesn't either. > > So: how to get alsa/pulseaudio to see it? > > Thanks again for the gracious help! > - Allen > > On Tuesday, 27 February 2018 04:16:15 UTC-8, Yuraeitha wrote: > > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque wrote: > > > Hi Qubes, > > > First time installer here, trying to get my sound to work. Strangely, > > > speakers are broken, but headphones work fine. > > > > > > Anytime I move my sound device from 'available' to 'selected' in a given > > > VM, the VM won't load and I get the 'qeexec demon' error. Same thing when > > > I move various other devices over (tested with USB ones). I should need > > > the audio device moved over in order for it to work in a given VM, right? > > > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > > > > > Thanks, > > > Allen > > > > Also if you moved the soundcard to a direct pass-through, and the soundcard > > hardware does not support the PCI pass-through feature. Then you need to > > make a full restart of Qubes OS (fully power down power in order to clean > > hardware memory). This is due to security reasons. If this is hitting you, > > then you may want to first undo the pass-through you made of your > > soundcard, and then make a full restart before trying the above suggestions. np's :) Try compare "qvm-pci list" with lspci, it's the same list, but it'll show you if the Qubes tools register the sound card. Also try look in the Qubes menu --> Systems Tools --> Pulseaudio Manager. See if the sound server is connected or disconnected here. I can't write much more right now as I'm on the road and need to close the lid and move now, but checking these might get us a little closer with more information. I can confirm I see my own soundcards with "aplay -l", so this command should indeed be working in Qubes it seems? It sounds like a problem that is out of my league though, but I'll try to help where I can. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/feaba198-afe7-4d06-b012-e5ca155f9149%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
Thanks Yuraeitha for the thoughtful reply! Hm. It doesn't seem to work in the other templates. I think it is a driver issue. I've tried volume etc.; and switching through the pulseaudio menus shows only 'simultaneous output' devices (which DO have actively fluctuating 'volume bars' when playback is happening!). Under 'config' there is 'no sound cards available for configuration'. I've been trying some things and let me try to clarify: 'lspci' lists '00:1b:0 Audio device: Intel Corporation 7 Serices/c210 Series Chipset Family High Definition Audio Controller (rev04)' I interpret that as the audio card being on the chipset (hence 'plugged in' automatically). 'aplay -l' however lists "no soundcards found". So alsa doesn't see it? Alsa is a deeper level than pulseaudio generally, right? So if alsa doesn't see it then it makes sense that pulseaudio doesn't either. So: how to get alsa/pulseaudio to see it? Thanks again for the gracious help! - Allen On Tuesday, 27 February 2018 04:16:15 UTC-8, Yuraeitha wrote: > On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque wrote: > > Hi Qubes, > > First time installer here, trying to get my sound to work. Strangely, > > speakers are broken, but headphones work fine. > > > > Anytime I move my sound device from 'available' to 'selected' in a given > > VM, the VM won't load and I get the 'qeexec demon' error. Same thing when I > > move various other devices over (tested with USB ones). I should need the > > audio device moved over in order for it to work in a given VM, right? > > > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > > > Thanks, > > Allen > > Also if you moved the soundcard to a direct pass-through, and the soundcard > hardware does not support the PCI pass-through feature. Then you need to make > a full restart of Qubes OS (fully power down power in order to clean hardware > memory). This is due to security reasons. If this is hitting you, then you > may want to first undo the pass-through you made of your soundcard, and then > make a full restart before trying the above suggestions. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7659bd70-21fb-44a3-a349-bcde532a5cb5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque wrote: > Hi Qubes, > First time installer here, trying to get my sound to work. Strangely, > speakers are broken, but headphones work fine. > > Anytime I move my sound device from 'available' to 'selected' in a given VM, > the VM won't load and I get the 'qeexec demon' error. Same thing when I move > various other devices over (tested with USB ones). I should need the audio > device moved over in order for it to work in a given VM, right? > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > Thanks, > Allen Also if you moved the soundcard to a direct pass-through, and the soundcard hardware does not support the PCI pass-through feature. Then you need to make a full restart of Qubes OS (fully power down power in order to clean hardware memory). This is due to security reasons. If this is hitting you, then you may want to first undo the pass-through you made of your soundcard, and then make a full restart before trying the above suggestions. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b70c8306-6d50-4850-a435-0a5dceb9ae48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qrexec demon fails to load any VM when I attach any device
On Tuesday, February 27, 2018 at 10:42:30 AM UTC+1, Allen Larocque wrote: > Hi Qubes, > First time installer here, trying to get my sound to work. Strangely, > speakers are broken, but headphones work fine. > > Anytime I move my sound device from 'available' to 'selected' in a given VM, > the VM won't load and I get the 'qeexec demon' error. Same thing when I move > various other devices over (tested with USB ones). I should need the audio > device moved over in order for it to work in a given VM, right? > > Any thoughts? Running 3.2 on a Zenbook UX31A. > > Thanks, > Allen I'm not sure if we're on the same page here, but being a new Qubes user, have you seen that sound will automatically be passed from different VM's to the speakers/headphones without doing much or anything at all? From your choice of words, it seems you both are aware and not at the same time, I'm not sure which is the case. I'll start with the less likely issues, like driver issue or broken template issue. If sound in a template is broken (and thereby any AppVM based on the template), then generally sound should work in another template (typically). So if its broken on fedora VM's, then chances are good that it will work on debian templates (and vice versa). I never got hit by this issue, but I believe it's relatively rare issue too. Incompatible drivers is probably more likely, and even that may be rare if you got common hardware, especially if sound works on other Linux distro's running on that hardware. So if it works on other Linux distro's, then it is less likely to be a driver issue, and if it doesn't work in all templates (fedora/debian/whonix), then it's also less likely to be an issue in the template. Of course it could be an issue in the dom0 sound server (off-topic mention, it sounds insecure that its run in dom0, but I believe it's planned to be secured in the near future). However I think the dom0 sound issues is even more rare, I've actually never seen one of those, usually only seen less than a handful cases of single template issues. Which leaves me with the question, could it be that you need to change the output in the sound settings? Did you try click on the sound icon on the XFCE4 panel and click "Audio mixer..." and then in the first tab, "Playback" change the soundcard for each individual VM? Note that if only one soundcard is available, that it won't give you a choice to pick between them in the first tab. But if there are multiple of soundcards available, then you should be able to pick between them. If you want to change between headphones/speakers within the same soundcard, then you need to pick the "Output Devices" tab instead and click on the soundcard with the two outputs and change it. Though normally this switch is done automatically if a jackstick is pressent in the soundcard. If a jackstick is sticked in your soundcard, like your headphones for example, then only your headhphones will give sound (unless you manually change it yourself like described here). Also, if you use USB based headset, then it might be defined as a soundcard instead, which you need to go back to the first tab again and pick between the speakers/USB-headset. Note also that if you use a soundcard, like the USB based soundcard you have, that you can pass it directly to any VM's you like. But if you want to use that soundcard on other VM's, then the dom0 sound server need to be changed to address it somehow. Which means your soundcard probably need to be placed in dom0, as far as I know? But if soundcards are passed directly into VM's then it should work in individual VM's at least. I'm not sure if qvm-usb can handle it, but direct pass-through should work just fine. A bit of different perspectives, does any this work for you? Did I misunderstand your issue? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9f68acf8-acc1-4fea-b9b0-2d16009070af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
