Re: [qubes-users] Re: Lenovo G505s with Coreboot and Qubes R4-rc3 fails to boot

2018-11-03 Thread Matt B
Very nice!

It sounds to this newb as if it's hacky as hell, but it's nice to finally
know what the problem was! Have you also dropped a line to the coreboot
mailing list?

Even though I ordered a dGPU G505s I got shipped one without, so sadly I
can't add this to the ifixit I plan to finish this winter. (hey, what's
this giant void in my laptop!?)
Hopefully when this gets upstreamed it'll "just work" like it does on the
factory bios though.
If it proves to enhance performance enough I might consider a board-swap.
(anyone know how to get minecraft to use crossfire on this thing? :P)

Thanks,
-Matthew Bradley

On Thu, Nov 1, 2018 at 1:39 PM  wrote:

> Hi All,
>
> I thought that I share with the g505s+Coreboot+QubesOS users that I
> finally managed to enable and use the dGPUs on the g505s boards.  When
> mentioning boards, I mean, that both variants  with its respective VBIOSes:
> dGPU=1002,6663 (ATI HD 8570M, Sun-Pro) and the dGPU=1002,6665 (ATI R5 M230,
> Jet-Pro) are working under Ubuntu Linux or Qubes 4.0 (no Windows testing
> was done or planned). I can now use the DRI_PRIME env. variable to offload
> rendering to the dGPU.  In Qubes  as far as I know - the dom0 X driver can
> only provide 2D acceleration to the AppVMs, also the dGPU seems slower than
> the APU GPU (glxgears in its original window size: ca. 1500 vs. ca. 2500
> fps), but it is still better to use the dedicated 2GB Ram of the dGPU...
>
> One remark: SI_support is not enabled by default in the amdgpu module in
> the latest stock 4.14-74 dom0 kernel, therefore you will have to create a
> custom kernel with this feature enabled, if you intended to use the radeon
> module for the APU GPU (no amdgpu support...) and the newer amdgpu for the
> dGPU.
>
> Problem statement: the dGPU was not initiated correctly and was not
> enabled by the radeon or amdgpu kernel module, VFCT header was
> corrupt/truncated (effectively was not corrupt, but only VFCT for the
> APU/iGPU was only present). Trying to init the dGPU device through Oprom
> initialization failed all my attempts. This was true whether using
> Coreboot+GRUB or using Coreboot+Seabios, regardless of kernel version 4.x.
>
> Solution in short: Modify Coreboot, that the VFCT table is only created
> for the dGPU so it can be used by either the radeon or amdgpu KMS driver.
>
> Solution in more details:
>  CB 4.8 latest, with SB latest 1.11.2
>  I modified the IO address & the pci device ID in APU GPU Vbios file
> (even though IO address change to 0x3000 might not required).
>  I modified the IO address in the dGPU VBIOS files to the actual
> Coreboot/kernel provided (0x1000) address
>  both prepared VBIOSes were put into CBFS
>  for Coreboot config: std g505s build, but both run oprom & load oprom
> was enabled (native mode), also display was FB 1024x768 16.8M color 8:8:8,
> legacy VGA → this provides console output even if eg. GRUB is the payload).
>  Main payload Seabios (compiled as elf separately)
>  I had to add my SPI chip driver  for EN25QH32=0x7016 to CB
>  I patched CB with version 0600111F AMD Fam 15h microcode (even though
> this was later recalled by AMD to n-1 version 06001119).  Nevertheless,
> Spectre V2 RSB and IBPB mitigations are thus enabled.
>  I enabled pci 00:02.0 for dGPU in devicetree → this causes pci
> resource allocation problems, because the 256M address window of the dGPU
> conficts with the APU GPU VRAM memory window (originally 512M).  Solution:
> I decreased the UMA size in buildopts.c to 256M (0x1000) and patched
> amd_mtrr.c, function setup_bsp_ramtop, to bring TOM down by 256M
> (0x1000).  So now the APU GPU has 256 M @0xd000 and the dGPU has
> 256M from 0xe000. → there could be other solutions, but I’m not expert
> in rearranging the memory layout used by CB
>  I modified pci_device.c, function pci_dev_init to only enable
> pci_rom_probe and pci_rom load for the dGPU pci device  (no oprom exec
> needed for PCI_CLASS_DISPLAY_OTHER).
>  I modified pci_rom.c,
> ◦ so the VBIOS of the dGPU is copied to 0xd from CBFS
> (..check_initialized..)
> ◦ and pci_rom_write_acpi_tables only run for
> PCI_CLASS_DEVICE_OTHER → dGPU (ACPI fill is done from the previously
> prepared 0xd address)
>
> Remark1: there could be one VFCT table with both VBIOSes present, but the
> APU GPU VBIOS is fully working via Oprom exec only (there are kernel
> warnings)
> Remark2: in the stock bios additional ACPI tables are present (SSDT, DSDT)
> which contain VGA related methods and descriptions therefore, the VFCT
> table itself (in EFI mode) is a lot smaller ca. 20K (vs. 65k).  These
> additional ACPI extentions allow eg. vga_switcheroo to work under Ubuntu in
> stock BIOS.  For CB currently only offloading seems to work...
>
> Well, I’m not a coding expert, this is the reason I didn’t include
> patches. My goal was to describe a working solution, and someone with
> proper coding skills and the possibility to 

[qubes-users] Disk Manager does not start

2018-11-03 Thread William Fisher
I just installed qubes 4.0 and the disk manager doesn’t start and show any disk 
drives. It just shows the settings for the mAnager. I can’t get the manager to 
start. I try to install or back-up vms and when I try to select a destination I 
get the error: whoops a Critical error has occurred. This is most likely a bug 
in Qubes Restore VMs application. Qubes VM Error. Cannot start Dom0 fake domain 
at line 102 of file base.py

-- 
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/79293c68-0d6c-4f11-8b3d-7723c85dac9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: off topic - invite codes to 'riseup'

2018-11-03 Thread johndiesel0897
On Saturday, September 29, 2018 at 12:36:53 PM UTC, cits...@gmail.com wrote:
> On Tuesday, October 28, 2014 at 7:26:49 PM UTC+1, 
> bm-2cu9wcijafoqtf6...@bitmessage.ch wrote:
> > Dear qubes-users,
> > 
> > I am long time qubes follower and user. I apologize in advance if anyone 
> > feels this request is spam.
> > 
> > I am looking for two invite codes needed to sign up to anonymous 
> > riseup.net email service.
> > 
> > I am hoping there are some qubes users who are riseup.net account 
> > holders.
> > 
> > Can anyone please send me a couple of invite codes that I might be able 
> > to sign up?
> > 
> > Thank you in advance.
> 
> Hello, I'm looking for one or two riseup ivite codes, I would greatly 
> appreciate 
> your help, greetings from Berlin everybody !

I'm looking for riseup.net invites too! 

-- 
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/400e3afb-ab36-4466-911a-3b646a819df9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] how do I check Tor & Whonix version?

2018-11-03 Thread qubenix
qubes123...@gmail.com:
> Thanks a lot for your tips and advice, my Tor version in Qubes4.0 - Whonix is 
> ​​0.3.2.9. Which Tor version is currently the most current and the safest? I 
> do not know the goal is 1000% safe but which is the best and safest version 
> currently? However, I could not figure out my Whonix version, how can I find 
> out which Whonix version I have? And if my Tor version is not backed up at 
> the moment, how can I upgrade this? Thank you for everything in advance. ;)
> 

Sounds like you're on Whonix 13. That would explain why you aren't able
to easily find your version number. Another giveaway is your Tor
version. On Whonix 14 I have Tor version 0.3.4.8.

If you want to upgrade to Whonix 14 see here:
https://www.whonix.org/wiki/Upgrading_Whonix_13_to_Whonix_14.

-- 
qubenix

CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765

-- 
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/7b5c295e-19dc-db69-ca95-26a1e0381082%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] how do I check Tor & Whonix version?

2018-11-03 Thread qubes123456
Thanks a lot for your tips and advice, my Tor version in Qubes4.0 - Whonix is 
​​0.3.2.9. Which Tor version is currently the most current and the safest? I do 
not know the goal is 1000% safe but which is the best and safest version 
currently? However, I could not figure out my Whonix version, how can I find 
out which Whonix version I have? And if my Tor version is not backed up at the 
moment, how can I upgrade this? Thank you for everything in advance. ;)

-- 
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/e623c832-ed61-4500-9983-bb727b52c5d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes 4: Unable to get any DVM app to ever launch

2018-11-03 Thread Otto Kratik
On Thursday, November 1, 2018 at 10:13:36 AM UTC-4, unman wrote:
> On Wed, Oct 31, 2018 at 12:27:06PM -0700, Otto Kratik wrote:
> > On Wednesday, October 31, 2018 at 7:49:43 AM UTC-4, awokd wrote:
> > > Otto Kratik wrote on 10/31/18 2:28 AM:
> > > > Qubes 4.0
> > > > 
> > > > 
> > > > Whenever attempting to launch an app in a DVM, the result is always the 
> > > > same. The popup message comes up saying "Disp1234 has started", and 
> > > > then nothing happens. Then about two minutes later, another popup says 
> > > > "Disp1234 has halted". No app ever launches.
> > > > 
> > > > It doesn't matter what app I try.. xterm, konsole, firefox, dolphin, 
> > > > thunar, tor browser, gedit, kwrite etc. Always the same behavior. Also 
> > > > doesn't matter if I try from Q Menu shortcuts, command line in dom0, 
> > > > command line in another AppVM.. no difference. Just the same type of 
> > > > message in the terminal, says it's launching, then shuts down two 
> > > > minutes later with no output.
> > > > 
> > > > Doesn't make a difference either if I try to open a file in a DVM or 
> > > > just straight launching an app. Nothing ever opens. Launching apps 
> > > > regularly from normal AppVM's works perfectly all the time, just not 
> > > > DVM's.
> > > > 
> > > > Slight correction: About 1 in 10 times, launching Firefox from a 
> > > > Fedora-template-based DVM succeeds. The other 9 times it fails. All 
> > > > other apps fail 10 out of 10 times. And launching any app (including 
> > > > Firefox) from a Whonix-ws-14-template-based DVM also fails 100% of the 
> > > > time as described above.
> > > > 
> > > > How is this issue best investigated and resolved?
> > > > 
> > > 
> > > Have you upgraded to Whonix 14 or customized the DVM? Try removing it 
> > > completely (you might have to temporarily change DVM defaults to a 
> > > different template), then recreating it with `sudo qubesctl state.sls 
> > > qvm.whonix-ws-14-dvm`. If that doesn't work, see 
> > > https://www.whonix.org/wiki/Qubes/Uninstall and 
> > > https://www.whonix.org/wiki/Qubes/Install to completely uninstall and 
> > > reinstall the workstation template and DVM. You can skip the gateway 
> > > steps if you've already upgraded it to 14 since it sounds like that's 
> > > still working.
> > 
> > It's a fresh install of Qubes 4 with freshly downloaded/installed Whonix 
> > 14/DVM templates using the salt/qubesctl command mentioned above and in the 
> > documentation. No customisations. So I doubt reinstalling would have any 
> > effect. 
> > 
> > Whonix-ws-14 template works perfectly fine for running apps the normal way, 
> > from AppVMs based upon it. No issue whatsoever. Only running them from 
> > whonix-ws-14-dvm causes trouble.
> > 
> > However as I said, even trying to run apps from Fedora-26-dvm also fails 
> > the majority of the time, so I'm not even convinced it's a whonix specific 
> > issue. Rather a DVM one in general.
> > 
> > Any other things to try?
> > 
> 
> I would try this:
> Install all updates in dom0 and qubes.
> Create a new Fedora based qube.
> Confirm you can run programs as expected.
> Make it a template for dispvms, using qvm-prefs.
> Close all unnecessary qubes.
> Then , at command line, start to test running programs in dispvms based
> on the qube.
> 
> Generally , the command should be:
> qvm-run --dispvm  
> 
> That's the most basic form.
> Anything you can run using qvm-run   should work in
> disposableVM based on qube (except gnome-terminal)
> 
> That will test the basic infrastructure.
> 
> If all is good, start testing a more complex form:
> qvm-run -a  --service  --dispvm= --qubes.StartApp+
> 
>  here should have an associated desktop file.
> Again, anything you can run using qvm-run --service   should 
> work in
> disposableVM based on the qube (except gnome-terminal)
> 
> That will test the more complex infrastructure.
> 
> If all's good, you can start testing different template based qubes,
> including Whonix. If it's not good there's something fundamentally
> broken.
> 
> qvm-run *does* have -v option, but it doesn't generate verbose output.
> 
> Check back when you have some results from testing.
> 
> unman


Hi, thanks for your detailed reply and suggestions. Here is what I have found:

I created a new qube/AppVM based on the fedora26 template, and called it 
'fedoratest'. I also enabled it as a DVM template using qvm=prefs. Running all 
of the following commands from dom0 worked perfectly:

qvm-run fedoratest firefox
qvm-run fedoratest nautilus
qvm-run fedoratest gedit
qvm-run --dispvm fedoratest firefox
qvm-run --dispvm fedoratest nautilus
qvm-run --dispvm fedoratest gedit

However, as soon as I introduced the '--service' argument into the picture, 
everything stopped working. All of the following commands fail silently:

qvm-run -a --service fedoratest firefox
qvm-run -a --service fedoratest nautilus
qvm-run -a --service fedoratest gedit
qvm-run -a --dispvm --service fedoratest firefox
qvm-run -a 

Re: [qubes-users] libxen-lowlevel

2018-11-03 Thread 'awokd' via qubes-users

'Andrzej Andrzej' via qubes-users:

What do you think about it? I do not know if this is only my sensitivity or 
actual problem. I do not know if this is the developers 'decision to use a 
newer version or maybe some problem with packages or other developers' 
decision. The entire update generally went smoothly and the machine was running 
smoothly without problems. Console logs are in the link. The updated machine is 
kali linux (kali is based on debian testing (buster)). The case concerns day 
before yesterday update. Day before yesterday I also updated dom0.

https://0bin.net/paste/SSgIy-TJK1A9Vl6D#VDYrhrUnKrALijMAz4UzC7yEXqP9gp3sqnu4eL8fa9P

How do you think? Any action is needed from the user?

Hint, including the full log like you did is good, but it usually helps 
people review your issue more quickly/easily if you include the snippet 
you are concerned about directly in the email to the list. In this case, 
it looks like this part:


Unpacking xen-utils-common (2001:4.8.4-5+deb10u1) over 
(2001:4.8.4-2+deb10u1) ...
dpkg: libxen-lowlevel1.0: dependency problems, but removing anyway as 
you requested:

 libxen-4.8 depends on libxen-lowlevel1.0.

I noticed this too on my Debian based templates. It removed 
libxen-lowlevel1.0, but same as you I haven't noticed any problems. Not 
sure it's necessarily a Qubes issue. Don't try to reinstall it; it looks 
like trying it will cause all the Qubes packages to get removed!


--
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/c0b102f2-d881-1a1c-fbbf-65e46a7ca088%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] No VMs after installation

2018-11-03 Thread 'awokd' via qubes-users

razvan.cioa...@gmail.com:

I have just installed Qubes-OS 4.0 on my Dell Latitude 7490 on a external USB 3 
enclosure containing a Samsung SSD. I had to copy the /boot/efi/EFI/qubes 
directory to BOOT and do the other steps in the Troubleshooting section. I 
managed to boot to qubes-os.
  
The only thing which is starting is dom0:mic, qvm-ls lists only dom0, qubes.log reports “Required property ‘default_template’ not set on qubes.app.Qubes object”. I can see the list of installed templates on /var/lib/qubes/vm-templates/, but nothing appears in the start menu, or in qubes-manager.


What can I do?


Did you see this recent thread? 
https://groups.google.com/d/msg/qubes-users/aojqaTI4pvY/mHquPWU7BgAJ


--
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/e4574c5b-89cb-5417-cba4-c5b555e1ed0c%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-03 Thread 'awokd' via qubes-users

LMiller M:

Ok doing some research about this as much as I can learn about. I’m redoing
the os 4.0 install. I got the warning that my machine doesn’t have
HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with
anything. Can you help explain how I’m supposed virt-type to PV? Or should
I just install the os 3.2?


Enable the virtualization options in your BIOS setup.


The main problem I was having was. After running lookup qvm-pci I see my
devices fine. The nic card shows up in the listing. In the network
connections add connection. Everything is grayed out can’t add anything no
vms work


1) Enabling virtualization may fix your sys-net issue.
2) You shouldn't have to add connections manually in most cases. What 
does connection info say?
3) Like unman said, switch sys-net to use the Debian template (shut 
sys-net down and change in Qube Setting/General tab).
4) If that doesn't fix it, see if your NIC needs additional firmware, 
then install that to the template you use for sys-net.


--
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/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Move pulseaudio to sys-usb

2018-11-03 Thread tfm853 via qubes-users
> I guess it should be possible to move the pulseaudio server from
> dom0 to sys-usb, shouldn't it?

Found a thread on qubes-devel regarding this [1] and also an open
ticket [2].

[1] https://groups.google.com/forum/#!topic/qubes-devel/kmAjYCP8K_4/discussion
[2] https://github.com/QubesOS/qubes-issues/issues/1590

-- 
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/fd8da219-3a92-4029-bf4f-1a0f9b596595%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Running a single appVM off another volume

2018-11-03 Thread 'awokd' via qubes-users

Achim Patzner:

Hi!

Is there an easier way of storing a single VM on an external device
(assume it to be an USB conneted medium) without doing elaborate dances
around it or having to backup and restore? One of our customers got the
bright idea to store a VM containing their CA on an USB flash and
connecting it to "an appropriate machine" (Yes! "Appropriate! Imagine
the fun I'm having *now*) for key signing ("Guys, have you ever heard
of a device called HSM?" "No, and please don't tell us.").

$appropriate was considered to be VMware without a virtual network
interface, running the machine off a USB flash. Securely stored on a
hook besides the door, "because if it is physically disconected it is
safe".

Ok, may not be TAILS (because that's used by criminals) but using Qubes
is an option. Getting off the VM-on-external-media-only trip not. Is it
possible to get these guys on Qubes without "changing the documented
process"?


There's https://www.qubes-os.org/doc/secondary-storage/ but not sure how 
well either approach works with drives appearing and disappearing. Think 
there's been some earlier discussion in this mailing list too.


--
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/c331108f-fdb0-e6c8-d35a-cd0436f7bd18%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Two VPN questions and one Qube Manager question.

2018-11-03 Thread 'awokd' via qubes-users

donoban:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11/1/18 10:58 AM, 'awokd' via qubes-users wrote:

Chris Laprise wrote on 11/1/18 1:59 AM:

On 10/31/2018 03:06 PM, entiosis via qubes-users wrote:




3) The “Autorefresh” button in Qube Manager have magically
disappeared from the tool bar. Its supposed to be located in
Dom0 Qube Manager, to the right of the three icons; Global
Setting → Backup Qubes → Restore Qubes From Backup → “Missing”
Qube Refresh. Is there any fairy dust I can sprinkle on the
terminal in dom0 to make that button reappear?


Wish I could help you there. QM has been in a lot of flux for the
past year.


It's gone from updated versions of QM since the switch to DBUS
because the theory is it's no longer needed. However, I have
noticed sometimes I still need to force it to refresh by closing
and re-opening QM.


Currently it uses internal Qubes API events. Do you remember sync
problems recently?


It's infrequent, but still happened recently. Think it was an HVM crash 
that the manager missed. I'll try to keep better tabs on it for a more 
actionable problem report, but the workaround of closing and re-opening 
isn't hard.


--
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/c1e93adb-4e34-2119-58e6-6ce6ac858175%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] libxen-lowlevel

2018-11-03 Thread 'Andrzej Andrzej' via qubes-users
What do you think about it? I do not know if this is only my sensitivity or 
actual problem. I do not know if this is the developers 'decision to use a 
newer version or maybe some problem with packages or other developers' 
decision. The entire update generally went smoothly and the machine was running 
smoothly without problems. Console logs are in the link. The updated machine is 
kali linux (kali is based on debian testing (buster)). The case concerns day 
before yesterday update. Day before yesterday I also updated dom0.

https://0bin.net/paste/SSgIy-TJK1A9Vl6D#VDYrhrUnKrALijMAz4UzC7yEXqP9gp3sqnu4eL8fa9P

How do you think? Any action is needed from the user?

-- 
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/661652793.353670.1541244147099%40ichabod.co-bxl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Move pulseaudio to sys-usb

2018-11-03 Thread tfm853 via qubes-users
I want to use an external USB sound card. With all USB devices in
dom0 this wasn't an issue, but now I have sys-usb and USB forwarding
seems to not agree with my audio device.

I guess it should be possible to move the pulseaudio server from
dom0 to sys-usb, shouldn't it?

Or even better: Have another pulseaudio server in sys-usb and have
an additional sink in dom0 that connects to the server in sys-usb.

Looking at module-vchan-sink.c[1]:

/* FIXME: 0 is remote domain ID */
u->play_ctrl = libvchan_server_init(0, QUBES_PA_SINK_VCHAN_PORT, 128, 2048);

Does this mean that the vchan sink is currently hard-wired to send
to dom0?


[1] 
https://github.com/QubesOS/qubes-gui-agent-linux/blobk/4427218dc382c66a98e22d5e67bdef5a87a5b3ba/pulse/module-vchan-sink.c#L431-L432

-- 
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/495779fe-9fa9-4664-b692-f39dff20461a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] No VMs after installation

2018-11-03 Thread razvan . cioarga
I have just installed Qubes-OS 4.0 on my Dell Latitude 7490 on a external USB 3 
enclosure containing a Samsung SSD. I had to copy the /boot/efi/EFI/qubes 
directory to BOOT and do the other steps in the Troubleshooting section. I 
managed to boot to qubes-os.
 
The only thing which is starting is dom0:mic, qvm-ls lists only dom0, qubes.log 
reports “Required property ‘default_template’ not set on qubes.app.Qubes 
object”. I can see the list of installed templates on 
/var/lib/qubes/vm-templates/, but nothing appears in the start menu, or in 
qubes-manager.

What can I do?


Thanks


-- 
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/7225c307-72bb-4a59-b046-df7a55ac7d6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] USB webcam forwarding

2018-11-03 Thread tfm853 via qubes-users
On Wednesday, October 31, 2018 at 8:53:14 PM UTC+1, awokd wrote:
> tfm853 via qubes-users wrote on 10/31/18 2:08 PM:
> > On Wednesday, October 31, 2018 at 12:35:27 PM UTC+1, awokd wrote:
> >> tfm853 via qubes-users wrote on 10/30/18 8:30 PM:
> >>> I'm trying to use a C920 USB camera on a Thinkpad X1 Carbon 6gen, latest 
> >>> Qubes4. The VM is running debian-9, but i also tried fedora-26. I tried 
> >>> both connecting the camera directly to a USB port of the Thinkpad and via 
> >>> a powered USB hub.
> >>
> >>>
> >>> Qubes shows the device as still being attached to the VM. I can detach 
> >>> and reattach without problems.
> >>>
> >>> Forwarding the Thinkpad's internal camera works fine.
> >>>
> >>> Are failures with particular USB devices to be expected? Does anyone know 
> >>> a good external webcam that works?
> >>>
> >>
> >> Yes, some devices don't work well through redirect. If you have a spare
> >> USB controller (not in use for your mouse & keyboard) you can assign it
> >> directly to the VM and then connect the webcam, but you lose isolation
> >> between that controller and the VM.
> > 
> > dom0:00_14.0  USB controller: Intel Corporation Sunrise Point-LP USB 3.0 
> > xHCI Controllersys-usb 
> > (no-strict-reset=True)
> > dom0:3b_00.0  USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB 
> > Controller (C step) [Alpine Ridge 4C 2016]
> > 
> > Would it be possible to use the thunderbolt controller for that purpose? It 
> > doesn't seem to be used right now.
> > 
> Possibly! Shouldn't hurt to try. You'll need to switch that AppVM to HVM 
> mode and disable memory balancing to attach a device to it. Can always 
> switch it back to PVH if it doesn't work.

Thanks! I'll try that. But I need to get an adapter to connect to USB-C first.

-- 
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/2b65c7ed-0c0e-42c9-af5d-f13d54a9e7e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.