[qubes-users] Re: Can' install qubes 4.0.1 -4.0.3 msi alpha 15 amd ryzen 7 3750h

[Foppe de Haan]

try this qubes 4.1 
installer? 
https://openqa.qubes-os.org/tests/8587/asset/iso/Qubes-4.1-20200528-x86_64.iso

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e90b9a62-7c45-4834-8ccd-0c791cfd162c%40googlegroups.com.

[qubes-users] Re: Updating sys-usb template

[Foppe de Haan]

On Thursday, May 28, 2020 at 8:34:40 PM UTC+2, Zbigniew Łukasiak wrote:
>
> My sys-usb uses a very old template. I tried some googling - but 
> failed to find any advice about update it without locking me out of 
> the system. 
> I guess I could remove it - there is a description on how to do that 
> in https://www.qubes-os.org/doc/usb-qubes/ - and then add it again 
> with a new template. But it is kind of complicated and looks 
> dangerous. 
>
> -- 
> Zbigniew Lukasiak 
> https://medium.com/@zby 
> http://brudnopis.blogspot.com/ 
>

What are you hoping to do? Change the template to a newer one, while your 
mouse & keyboard are USB-connected?

If so, the only way to do so is via the CLI: e.g. 'qvm-shutdown sys-usb && 
sleep 20 && qvm-prefs sys-usb template NEWTEMPLATE && qvm-start sys-usb'

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6cab7ca6-eeb6-4401-9c75-2d516613be45%40googlegroups.com.

[qubes-users] Re: Qubes awarded MOSS Mission Partners grant!

[Foppe de Haan]

Nice, congratulations. to all involved :)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bf833670-f91f-408d-8aab-0c02dd441e6e%40googlegroups.com.

[qubes-users] Re: Qubes awarded MOSS Mission Partners grant!

[Foppe de Haan]

oh wow, nice, congrats. :) 


On Friday, May 22, 2020 at 11:49:50 AM UTC+2, Andrew David Wong wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA512 
>
> Dear Qubes Community, 
>
> We're proud to announce that the Qubes OS Project has been awarded a 
> Mozilla Open Source Support (MOSS) [1] awards program grant in the 
> amount of 128,000 USD. This generous one-year grant will fund the work 
> of Frédéric Pierret [2] on making Qubes more robust and stable, as 
> well as several key parts of Nina Alter's [3] extensive work on making 
> Qubes more user-friendly. 
>
> There are three separate tracks for MOSS awards. Qubes has been awarded 
> a grant in the Mission Partners [4] track. As Mozilla explains, "The 
> Mission Partners track supports open source projects that significantly 
> advance Mozilla's mission." It is a great honor for Qubes to be 
> recognized as such a project, and we're thrilled by the important work 
> that this grant will enable. 
>
>
> [1] https://www.mozilla.org/en-US/moss/ 
> [2] https://www.qubes-os.org/team/#frédéric-pierret 
> [3] https://www.qubes-os.org/team/#nina-eleanor-alter 
> [4] https://www.mozilla.org/en-US/moss/mission-partners/ 
>
> This announcement is also available on the Qubes website: 
> https://www.qubes-os.org/news/2020/05/22/moss-mission-partners-grant/ 
>
> - -- 
> Andrew David Wong (Axon) 
> Community Manager, Qubes OS 
> https://www.qubes-os.org 
>
> -BEGIN PGP SIGNATURE- 
>
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl7HoC0ACgkQ203TvDlQ 
> MDAnTxAAxOL/x+PzJPZCceiprWyIaKRydGOlvfZgU01ki8Y2TjQgs3HTTTdpERNB 
> 96gFbazsboJWelbi3Gah1eYjJU0Dkw8gYiF5rnaVkntmzzN8Un1u5+F1oIksx7Ku 
> EkhI44iE/m7/pIletm6kXu6O6RqqLfrmQfSiEL95HX4Y/JH4dEwOBQ0mPrSSkrGi 
> y85tiZXIADWIVPlLUHlrtlSrK7HJYr5VBI8K6GMgW4wOEiCfYW9eU8AWvcFK/3us 
> E/UPyE/6UY2sy83a4MyPDbP59GyWIEQmQRjFdAaPVB+xb04x8ibmSK2ScpNpqnTu 
> aMjD1TbOZ+wLYeDcK7fjB4QOEGNu/slG8JTqs7L0pmecYvscv/WprEzMBXmnQBeC 
> pnliCtzb3aeUHcE9SKmxpIv975sEoU139WK1FTgE+KyQY/5ruzzwqr1SuhCPCl10 
> LFhuuw+qYY3zgkoNr2eh/1STnywM+75pFQtJHaWrd3wFbLbN/nj2T/nDECPLyLkw 
> 5JsHHVANtTgHqXPEhbQWmKUgp6cbQkAOKDvJLMFaeM2bmNrVNEeKaH1WtWwEcfuT 
> d+pv5rn7M7XFlHXDiKupC25e5EA47R/eUVsaZvK0Ld12QT5lG9uSBHLdiK5KGPni 
> bwkpVLCkaQb/GNrVx4nj9u6YoSt2yNtycOTKeNkRySW06vlLOaU= 
> =MXNG 
> -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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f6d42f2f-0fda-473b-84c3-af131f00105d%40googlegroups.com.

Re: [EXT] Re: [qubes-users] Constant firefox crashes because of Qubes shared memory

[Foppe de Haan]

On Monday, May 4, 2020 at 10:00:02 PM UTC+2, Ulrich Windl wrote:
>
> >>> Zbigniew Lukasiak > schrieb am 
> 04.05.2020 um 14:34 in 
> Nachricht 
> <25184_1588595663_5EB00BCE_25184_83_1_CAGL_UUtUxkCeqF2xj8Fud5Fwj7dfT5GanOYhxmRx6
>  
>
> sonb...@mail.gmail.com >: 
> > marmarek advised me on irc to add more shared memory: 
> > 
> > mount /dev/shm -o remount,size=10G 
> > 
> > and it seems to work. 10G is close to half of that VM's RAM. Qubes was 
> > assigning only 1G previously. 
>
> Personally I think once your browser uses more than 1GB of memory, it's 
> time 
> to restart it or to restrict scripts from collecting so much information 
> in 
> RAM. 
>
> > 
> > Cheers, 
> > Zbigniew 
>

that sounds nice, but it would mean restarting my browser as soon as I've 
opened it. :p

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7e113615-4f34-403e-a84c-9e504a1df51f%40googlegroups.com.

Re: [qubes-users] Constant firefox crashes because of Qubes shared memory

[Foppe de Haan]

Firefox crashes a lot for me too, with 7GB ram assigned, mostly on reddit, 
youtube pages. Makes it nearly unusable.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e44b6d65-e33a-4ea2-b203-847999085e7e%40googlegroups.com.

Re: [qubes-users] Re: "Qubes Architecture Next Steps: The GUI Domain" by Marek Marczykowski-G??recki & Marta Marczykowska-G??recka

[Foppe de Haan]

On Saturday, April 11, 2020 at 2:01:46 PM UTC, unman wrote:
>
> On Sat, Apr 11, 2020 at 12:03:42AM -0700, Foppe de Haan wrote: 
> > 
> > 
> > On Saturday, April 11, 2020 at 2:01:05 AM UTC, Sven Semmler wrote: 
> > > 
> > > On Fri, Apr 10, 2020 at 02:54:01AM -0700, Foppe de Haan wrote: 
> > > > I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 
> until 
> > > > it's clear under which circumstances GPU virtualization works 
> properly. 
> > > 
> > > Forgive me from taking this off-topic from the original thread. I have 
> > > tried and failed to make KDE work in dom0. 
> > > 
> > > sudo qubes-dom0-update @kde-desktop-qubes 
> > > 
> > > While I can login to KDE, there are clearly issues. The Launcher 
> freezes 
> > > frequently and search doesn't work. There are weired delays all over 
> the 
> > > place (GUI reacts much later or not at all). 
> > > 
> > > I have no such issues with XFCE or i3. Have you done anything beyond 
> the 
> > > above command to get KDE running well on your machine? 
> > > 
> > > /Sven 
> > > 
> > > 
> > I'm running Qubes 4.1. My experience with the KDE version (and display 
> > stack) included with Qubes 4.0 /fedora 25 wasn't that great either. :) 
> > 
>
> Interesting. My experience is the opposite. I run KDE in 4.0, and find 
> it greatly enhances the Qubes experience. 
> Menus are easily customisable, it's simple to force separation of qubes 
> in different domains on to separate Activities, ease of creating custom 
> launcher shortcuts, etc etc. Far better than Xfce for Qubes, and in my 
> experience it just works. And this is on x220 and x230 machines of 
> relatively low spec. 
> If you want to open a separate topic, perhaps we could troubleshoot your 
> problems? 
>
>
is this in response to sven? I quite like KDE 5.17 in Q4.1, for the reasons 
you mention. :) 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/887e8f5b-6ef6-4572-b9e5-239a334d848f%40googlegroups.com.

Re: [qubes-users] Re: "Qubes Architecture Next Steps: The GUI Domain" by Marek Marczykowski-Górecki & Marta Marczykowska-Górecka

[Foppe de Haan]

On Saturday, April 11, 2020 at 2:01:05 AM UTC, Sven Semmler wrote:
>
> On Fri, Apr 10, 2020 at 02:54:01AM -0700, Foppe de Haan wrote: 
> > I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until 
> > it's clear under which circumstances GPU virtualization works properly. 
>
> Forgive me from taking this off-topic from the original thread. I have 
> tried and failed to make KDE work in dom0. 
>
> sudo qubes-dom0-update @kde-desktop-qubes 
>
> While I can login to KDE, there are clearly issues. The Launcher freezes 
> frequently and search doesn't work. There are weired delays all over the 
> place (GUI reacts much later or not at all). 
>
> I have no such issues with XFCE or i3. Have you done anything beyond the 
> above command to get KDE running well on your machine? 
>
> /Sven 
>
>
I'm running Qubes 4.1. My experience with the KDE version (and display 
stack) included with Qubes 4.0 /fedora 25 wasn't that great either. :) 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b394875d-eee8-4e7f-ad94-6908765dc0ba%40googlegroups.com.

[qubes-users] Re: "Qubes Architecture Next Steps: The GUI Domain" by Marek Marczykowski-Górecki & Marta Marczykowska-Górecka

[Foppe de Haan]

sounds promising. :) 
One question: (when) will the gui-domain be made 'mandatory' in qubes 4.1? 
I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until 
it's clear under which circumstances GPU virtualization works properly.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1c074e18-9a87-4c3d-ac26-d7ee26f9d9ff%40googlegroups.com.

[qubes-users] Re: Install Qubes in Odroid H2,

[Foppe de Haan]

what he means is install Qubes the same way you installed Ubuntu Mate, on 
its own drive.
That said, did you check in the bios if IOMMU and VT-X and VT-D support 
were all enabled?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/122b22a1-3aaa-4fb7-8ac5-7973f34175fc%40googlegroups.com.

Re: [qubes-users] How many CPU threads is recommended for Qubes OS ?

[Foppe de Haan]

anywhere up from 4 should be fine, 4 cores is more than what most intel 
laptops had to offer for ages. 
WRT the 3200g not working, you mean the iGPU? Kinda surprising to hear, 
would expect it to be supported by the kernel already. What error were you 
running into?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/db539b73-89c0-46e6-ad7c-66c253c89b13%40googlegroups.com.

[qubes-users] Re: Unsure How and If I Can Install Qubes

[Foppe de Haan]

using something connected to a sata or m.2 connector would be safer than 
using a USB-connected drive due to how Qubes recommends isolating all USB 
connectors. Looking at the specs, it should be possible to add a second 
internal drive. If you want to seriously use Qubes, you'll want to have at 
least 16GB ram, though, and your laptop CPU will likely be a bit of a 
bottleneck, due to the likely to be low core/thread count. Aside from that, 
you should be fine though.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/874103a6-4a30-4ba7-b6f1-500d3245bd0a%40googlegroups.com.

[qubes-users] Re: I need help with IOMMU issues

[Foppe de Haan]

there's also a IOMMU bios option that needs to be enabled. "should" is 
something you and bios makers seem to differ on, and I think they win. ;)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/de63d116-1060-4321-923f-6e2a9107b03d%40googlegroups.com.

[qubes-users] Re: hybrid graphics laptop over m2 sata egpu good idea or not?

[Foppe de Haan]

On Thursday, March 5, 2020 at 6:04:59 PM UTC+1, john redneck wrote:
>
> I am owner twicked Acer Aspire. (100% Qubes OS compatibility).
> So, that laptop has 32gb ram ddr4, i7-6500, 520 intel hd + nvidia 950m, 
> also 1TB m2 sata samsung EVO and intel iommu support.
> I can remove m2 wifi module card and replace it with m2 EGPU (for example, 
> nvidia 1060 GTX PCI-E card).
> Is it possible to gpu passthrouth dedicated eGPU card to debian/fedora 
> AppVM or HVM?
> Anyone has success or Qubes bad with gpu passthrouth on laptops?
>

it is or will be possible, but I'd highly recommend against using nvidia 
cards for this, as they're much more likely to refuse to work when passed 
through (because nvidia blocks this in drivers). 
Aside from that, it won't be easy to do generally. May also depend on which 
iommu group the m.2 connector currently connected to the wifi module is in. 
More importantly, it will probably be highly bandwidth constrained because 
intel motherboards will route m.2 through the chipset, which has a pcie3 x4 
connection with the CPU (while connecting all of the peripherals, so usb, 
m.2, sata ports..).
All in all, if you want to do this, I'd either try a desktop (with a 
dedicated pcie3 x8 connector available for the GPU), or a ryzen 4000 series 
laptop, after checking out how the usb or other ports connect to the CPU.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9b9048b2-d0d0-45d9-9738-d43a990a2175%40googlegroups.com.

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

[Foppe de Haan]

On Sunday, February 16, 2020 at 12:07:51 PM UTC+1, aihey wrote:
>
> > Looks like your Dell is a Ryzen with integrated AMD graphics, correct? 
>
> that's right: it's a AMD Ryzen 5 3500U with Radeon Vega Mobile 
>
> > Don't think the kernel included Qubes 4.0.3 has video drivers for it. To 
> confirm, you could try to install in text mode and see if you get further. 
> You should be able to switch to a terminal session (ctrl-alt-F2?) during 
> install to see the temporary logs. 
>
> I'm only able to get a bit further with a bunch of different tricks which 
> I've described in my original post. The ctrl-alt-F2 during install has not 
> worked for me. 
>
> > If text mode does get further, you might need to build a custom ISO with 
> the latest 5.x kernel to get the video drivers. There are also test builds 
> of Qubes 4.1 you can try. Believe they include 5.x as well. 
>
> I spent a yesterday afternoon looking into this. I built Qubes 4.1 (stable 
> version) following the instructions in 
> https://www.qubes-os.org/doc/qubes-builder/. I did this on the actual 
> machine and had to re-install the OS with Fedora 31 as the building tool 
> didn't support my original OS (Linux Mint 19.3, debian based). I was able 
> to build and generate the ISO file successfully using the standard 
> configuration. Loaded the ISO file into an USB using dd and it booted fine 
> up to GRUB. 
> Unfortunately, I was not able to go further from GRUB and got identical 
> behaviour as before. Tried standard install, USB testing and 
> troubleshooting mode but non of these worked. 
>
> You mention that the video drivers might be included in Qubes 5.x- would 
> you be able to point me to building instructions for this? I was not able 
> to find any information on how to configure the building tool for version 
> 5. I've only followed the standard+stable configuration- do you know how to 
> add the necessary drivers as part of the building process? 
>
> I came across this post 
> https://www.qubes-os.org/doc/install-nvidia-driver/ which suggests a fix 
> to issues with NVIDIA/AMD video drivers. I was hoping to use this to 
> built-in the necessary drivers into the Qubes 4.1 OS build but was not able 
> to get that far. Any ideas on how to do this? 
>
> Many thanks for your suggestions! 
>
>
> ‐‐‐ Original Message ‐‐‐ 
> On Wednesday, 12 February 2020 15:58, 'awokd' via qubes-users <
> qubes...@googlegroups.com > wrote: 
>
> > 'aihey' via qubes-users: 
> > 
> > > Unfortunately this has not worked for me but thanks for your 
> suggestion. 
> > > Does anyone happen to know if the installation messages are saved 
> somewhere? I would like to find out what triggers the installation to 
> freeze (it all happens very quickly before it goes blank). 
> > > ‐‐‐ Original Message ‐‐‐ 
> > > On Tuesday, 11 February 2020 13:11, fiftyfour...@gmail.com 
>  wrote: 
> > > 
> > > > My Dell is newer and simply doesn't have legacy boot. I know that 
> the altered parameter is used during boot because it was the only thing I 
> changed to make my installations turn from failures to successes. 
>
> you can download a build from here 
-> 
https://openqa.qubes-os.org/tests/6161/asset/iso/Qubes-4.1-20200214-x86_64.iso 
btw, you're sure that iommu, svm are both enabled in the bios?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a81e8d53-844e-4913-84f4-7f4bbfe542a6%40googlegroups.com.

Re: [qubes-users] feature request

[Foppe de Haan]

On Saturday, January 25, 2020 at 2:53:53 PM UTC+1, Chris Laprise wrote:
>
> On 1/25/20 7:15 AM, haaber wrote: 
> > Hello, I have several virtual screens; I guess many user have. Is it 
> > possible to reserve one of them exclusively for dom0 and templateVM 
> > terminals -sort of a separated "admin screen"-  to avoid other 
> > appVM-windows popping up and being able to capture input from keyboard? 
> >Bernhard 
> > 
>
> KDE lets you confine windows to certain screens or virtual desktops 
> under System Settings / Desktop Management / Window Rules. You can 
> specify how it matches the window, such as pattern matching on the 
> window title. 
>
> For example, if you set Window Title to 'Regular expression' and the 
> text to '^\[personal', then under Size/Position select 'Desktop', 'Apply 
> Initially' and 'Desktop 2' ... that will make windows from any VM 
> beginning with "personal" open only on Desktop 2. You can also use 
> 'Force' instead of 'Apply Initially' and that will prevent you from 
> moving those windows to a different desktop. 
>
> I think the regular expression matching is probably powerful enough to 
> do what you want. For example, a rule for any window title NOT beginning 
> with '[' and NOT having also ']' would be a dom0 window. Another rule 
> could have the names of all your templates. 
>
> -- 
> Chris Laprise, tas...@posteo.net  
> https://github.com/tasket 
> https://twitter.com/ttaskett 
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886 
>
Thanks for pointing that out. Currently trying KDE in Qubes 4.1 beta, and 
it's quite a change from xfce 4.14 even (which was already preferable to 
previous iterations). 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/de32ccc0-ca2c-4c52-8479-153731e060aa%40googlegroups.com.

Re: [qubes-users] Re: VLC gets black when maximized

[Foppe de Haan]

Is this in fedora-based AppVMs or in debian-based ones as well?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2f8cb65a-31a3-4219-94f2-1ebe269160b7%40googlegroups.com.

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

[Foppe de Haan]

On Sunday, February 16, 2020 at 11:55:40 PM UTC+1, A wrote:
>
> søn. 16. feb. 2020 kl. 19.01 skrev Chris Laprise  >:
>
>> On 2/16/20 10:32 AM, A E wrote:
>> > søn. 16. feb. 2020 kl. 16.18 skrev Chris Laprise >  
>> > >:
>> > 
>> > On 2/15/20 10:20 AM, A E wrote:
>> >  > If it isn’t possible to change the settings of the screensaver 
>> that
>> >  > Qubes OS is actually using, then I would like to hear how I can
>> > either
>> >  > disable or delete it in Qubes ?
>> > 
>> > The setting to disable screensaver does work for KDE in dom0. 
>> Switching
>> > to KDE has fixed a number of GUI problems for me.
>> > 
>> > -- 
>> > Chris Laprise, tas...@posteo.net  > tas...@posteo.net >
>> > https://github.com/tasket
>> > https://twitter.com/ttaskett
>> > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>> > 
>> > 
>> > Okay, how do I switch to KDE ?
>> > 
>> > And what are the cons with switching to KDE... ?
>> > 
>> > I shall probably mention that I’m a Linux and Qubes newbie.
>>
>> This guide only requires a few steps in the dom0 terminal:
>>
>> https://www.qubes-os.org/doc/kde/
>>
>> Make sure you also do the lightdm->sddm changes because lightdm is where 
>> some of the problems originate.
>>
>> The downsides to KDE are that it uses about 200MB more RAM (IMO, very 
>> much worth it) and the Network Manager applet icon appears blank (its 
>> still easy to use once you know its there in the systray).
>>
>> -- 
>> Chris Laprise, tas...@posteo.net 
>> https://github.com/tasket
>> https://twitter.com/ttaskett
>> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>>
>
> Okay, I have seen here (link: https://m.youtube.com/watch?v=fo45bo1jvZI ) 
> that new versions of KDE uses less ram than XFCE.
>
> Which version of KDE do you use in Qubes OS ?
>
 
if you're interested in that version of KDE, you'll need to run the Qubes 
4.1 beta, as Qubes 4.0's fedora 25 won't receive that update. :)
(And you'll need to install the packages manually, as the meta package 
@kde-desktop-qubes doesn't work (yet).)
you'll probably need at least:
plasma-breeze plasma-workspace kdelibs kde-settings-plasma sddm dolphin 
kwin kscreen

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/78d2e636-d6cb-4cac-a939-87ca205760c6%40googlegroups.com.

[qubes-users] Re: Is CentOS in Qubes Broken?

[Foppe de Haan]

there are a few prebuilt templates to pick from in 
https://yum.qubes-os.org/r4.0/templates-community-testing/rpm/

On Saturday, February 1, 2020 at 1:59:41 AM UTC+1, mike wrote:
>
> Hi,
>
> I'm trying to install the CentOS template, and cannot.  I failed both with 
> getting the community template and trying to build one with 
> qubes-builder.  I'm using Qubes V4.0.  I've had no trouble building Debian 
> based templates (bionic, buster). 
>
> First, I tried to get the community template using the instructions from 
> the docs here:  https://www.qubes-os.org/doc/templates/centos/
>
> The result was:
> *[user@dom0 ~]$ sudo qubes-dom0-update 
> --enablerepo=qubes-templates-community qubes-template-centos-7*
> *Using sys-firewall as UpdateVM to download updates for Dom0; this may 
> take some time...*
> *Last metadata expiration check: 22:12:59 ago on Thu Jan 30 17:43:53 2020.*
> *No match for argument: qubes-template-centos-7*
> *Error: Unable to find a match*
>
> Has the centos template been removed?  Are there any pointers on how to 
> search the *qubes-templates-community *repo?  I can't seem to find any 
> links to that repo.
>
>
> I then tried to building the template with qubes-builder, and failed 
> during make-template:
> *--> Finished Dependency Resolution*
> *Error: Package: qubes-core-agent-4.0.52-1.centos7.x86_64 
> (template-builder-repo)*
> *   Requires: python3-daemon*
> *Error: Package: qubes-core-agent-4.0.52-1.centos7.x86_64 
> (template-builder-repo)*
> *   Requires: python3-dbus*
> *Error: Package: qubes-vm-recommended-4.0.6-1.centos7.noarch 
> (template-builder-repo)*
> *   Requires: thunderbird-qubes*
> *Error: Package: qubes-core-agent-4.0.52-1.centos7.x86_64 
> (template-builder-repo)*
> *   Requires: python3-pyxdg*
> *You could try using --skip-broken to work around the problem*
> *You could try running: rpm -Va --nofiles --nodigest*
> *make[1]: *** [Makefile:64: rootimg-build] Error 1*
>
> Am I doing something wrong here?  I don't know enough about what is going 
> on in this build process, but this feels like some packages aren't getting 
> installed properly at some point upstream.
>
> Has support for CentOS in Qubes been discontinued or broken in a recent 
> update?  
> Is this a bug?  It is not clear to me where I should report the bug - 
> community or Qubes.
>
>
>
> Thanks,
> Mike
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/24d721b7-f590-4c15-8158-1e27b8bdc44a%40googlegroups.com.

Re: [qubes-users] How to connect to internet by using a mobile broadband USB modem ?

[Foppe de Haan]

I searched a little because the whole TF_Card_reader seemed a really 
strange identifier to me for a wifi dongle, and I found 
https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9 . is for 
a different model, but the same principle may well apply. If so, you'll 
need to tell the dongle to switch to wifi connection mode before it'll 
work. To make triaging easier, it may be handy to use a fedora live boot 
USB.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a57f24a6-82ef-4c62-b5ea-cae851b39a3f%40googlegroups.com.

[qubes-users] Re: Which Graphic cards work perfect in Qubes

[Foppe de Haan]

AMD cards are far and away the easiest to get working, especially the 
polaris series (there are still some toothing issues with navi support, 
afaik) or before.
Nouveau support for new Nvidia cards is spotty at best.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ab8fd0ae-d0b1-4a4d-848e-52862a6a69db%40googlegroups.com.

[qubes-users] Re: Qubes ISO with different Xen version

[Foppe de Haan]

idk if this helps, 
but 
https://openqa.qubes-os.org/tests/5110/asset/iso/Qubes-4.1-20191223-x86_64.iso 
ships with xen 4.13. Or you can try 4.0.2rc2, which is 4.8-based.

On Tuesday, December 24, 2019 at 5:32:04 PM UTC+1, qube...@gmail.com wrote:
>
> It appears that the current version of Qubes OS ships with Xen 4.12. I 
> have an AMD Threadripper and this version of Xen has issues detecting 
> virtualization on my CPU. There is a patch for this in the qubes-vmm-xen 
> repo on the xen-4.8 branch. Are there ISO's with this branch readily 
> available? I've tried building my own ISO with this branch in it for the 
> last few days and the build keeps failing. I'm hoping someone knows of an 
> easier way?
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b08dc424-10eb-42e1-871f-1a5c0f13762b%40googlegroups.com.

[qubes-users] Re: Removing Thunderbird from fedora-29 removes 68 packages (of which 11 qubes packages)

[Foppe de Haan]

On Friday, April 19, 2019 at 10:28:15 PM UTC, tom...@gmail.com wrote:
> Hi guys,
> 
>   I installed Q4.0.1 on USB HDD to see changes from 3.2.
> As I've decided to use fedora-29 for system-related VMs, I wanted to remove 
> large apps like Firefox and Thunderbird from it.
> But running 'dnf remove thunderbird' on f29 template resulted in removal of 
> 67 other packages, which seems important.
> 
> Any idea what's wrong?
> I used latest Qubes ISO and updated dom0 and fedora-29 template before this 
> removal.
> 
> Remove  68 Packages
> {code}
> 
> regards,
>   tom

try dnf remove thunderbird --noautoremove

-- 
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/60d07299-a902-4be0-b197-f18884a1d0ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes-mirage-firewall 0.5

[Foppe de Haan]

On Sunday, April 7, 2019 at 8:23:13 PM UTC, 799 wrote:
> Hello Thomas,
> 
> 
> 
> Thomas Leonard  schrieb am Do., 4. Apr. 2019, 12:27:
> I'd like to announce the release of qubes-mirage-firewall 0.5:
> 
> https://github.com/mirage/qubes-mirage-firewall/releases/tag/v0.5
> (...)
> 
> For installation instructions, see:
> 
> https://github.com/mirage/qubes-mirage-firewall/blob/master/README.md,
> 
> 
> thanks for the work you put into your mirage-firewall, as I have read your 
> announcement several times in the past, I'd like to give it a try, but I 
> would like to see some more information which is targeted towards newbies.
> To me it is not clear how I can setup the mirage-firewall.
> It seems that your suggestion is to build a docker image and while this 
> covered in the installation howto 
> (https://github.com/mirage/qubes-mirage-firewall/blob/master/README.md) the 
> docker building must be started within an AppVM ... should this be a template 
> VM? a dedicated HVM? And should it be debian or fedora?
> I'd like to have a step for step instruction which takes a standard Qubes 
> Installation as baseline and then ends in a working mirage firewall.
> As mentioned I would be more than happy o contribute to the documentation, 
> but can you clarify the starting point?
> 
> 
> So in which VM (and VM type) should I run those first steps:
> 
> 
> [...]
> Build from source
> Clone this Git repository and run the build-with-docker.sh script:
> sudo ln -s /var/lib/docker /home/user/docker
> sudo dnf install docker
> sudo systemctl start docker
> git clone https://github.com/mirage/qubes-mirage-firewall.git
> cd qubes-mirage-firewall
> sudo ./build-with-docker.sh
> [...]
> 
> - O

Run from any recent fedora-based AppVM (standalone or not). 

-- 
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/f0815853-5948-4622-b853-12c8b7380433%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Hyperthreading on or off?

[Foppe de Haan]

On Thursday, April 4, 2019 at 11:05:09 AM UTC, brend...@gmail.com wrote:
> On Thursday, April 4, 2019 at 5:10:39 AM UTC-4, donoban wrote:
> > On 4/3/19 11:54 PM, jr...@gmail.com wrote:
> > > Looking for guidance on best practices for Qubes configuration:
> > > given the vulnerabilities that have been reported with
> > > Hyperthreading, it would seem to be a no-brainer that it should be
> > > disabled, but I don’t see anyone coming right out and saying so.
> > > Curious what this group thinks.
> > 
> > If you mean that disabling it could be too drastic solution or the
> > risk in real-world conditions is too low, you could be right.
> > 
> > I read a paper about this where the attacker needed a lot of time
> > while other VM was running an infinite loop using a SSL key (no real
> > world behavior). So probably, in real conditions this is very very
> > hard to exploit.
> > 
> > On the other side, Qubes security model and sense of existence is to
> > guarantee that some compromised VM can not compromise other VMs or the
> > whole system so just disabling could be reasonable too.
> 
> Makes sense to me: Qubes policy is to enforce safer defaults. User can 
> modify, at their own risk.
> 
> Layperson's thought: perhaps there could be a CPU allocation strategy in Xen 
> that allocates cores instead of logical CPUs? That may mitigate the security 
> issue if the workload would benefit from Hyperthreading (aka SMT).
> 
> Whether this is significantly safer than the default logical CPU allocation 
> w/ hyperthreading really depends upon the CPU cache strategies in effect, 
> perhaps. E.g. contemporary Intel CPUs (packages?) have three or more levels 
> of cache and some interesting cache topologies including cross-core caches...
> 
> Some support software-selectable caching strategies as well for parts of the 
> cache.
> 
> Brendan

would that work, without static allocation? I'd assume Xen regulates time 
slices, so that there's always a chance that the cache will still contain stuff 
from activity generated in/by another VM. I guess you could flush that every 
time, but I'm sure that generates more than a little overhead.

-- 
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/b1efe6ed-bdde-4f1c-94e3-6bf4c4cd9353%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: debian 10 ?

[Foppe de Haan]

On Thursday, March 28, 2019 at 1:05:57 AM UTC, haaber wrote:
> Hi fellows, I tried to qvm-clone & upgrade a debian-9 to debian-10
> (buster). In a reproducible way, the apt-get dist-upgrade will fail
> while installing (so: after download is finished) with the terminal
> crashing surprisingly. So NO output is available.
> I then (again: reproducibly) try to get access to the half-upgraded
> system by running   qvm-run -v -u root debian-10 xterm  - which fails as
> well saying "command failed with code 1" -- thereby not even unveiling a
> minor hint where the error might sit. I have no idea how I could
> possibly get to re-animate  this half-dead install, if I cannot even get
> an xterm. If I shutdown it, it will maybe start (or hang, who knows)
> since it remains inaccessible. My last try is still running in hope for
> some help from you.
> 
> Cheers, Bernhard

tried 'sudo xl console debian-10'?

-- 
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/f0fa4a6f-f4c6-4531-bd91-91595463b99d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590

[Foppe de Haan]

On Friday, March 22, 2019 at 11:41:12 PM UTC, CooSee wrote:
> how to compile rpms on Qubes - maybe i can use the current available 
> xorg-x11-drv-amdgpu and mybe xorg and mesa too.
if you want to play around with this, it's probably easier to change the fedora 
(updates?) distro from fc25 to fc29 in /etc/yum.repos.d/, input the correct 
signing key, and try installing the new xorg-x11-drv-amdgpu using 
qubes-dom0-update. 

> after login with new kernels, the desktop is loading just for 1 sec.

> there must be an error in the system, because i also tried KDE and Awesome - 
> same behaviour, e.g. Lightdm backround is scrambled with glitches at login 
> screen and it always kicks me back to login screen - using Dual Monitor Setup.
yeah, sounds like there's a driver issue
> 4.14.103 is working fine, but only with ' amdgpu.dpm=0 ' <<< is this bad for 
> the device ?
why did you try that option, specifically? phoronix guide? anyway, as he 
writes, it's not harmful, it just won't game very well. ;)

-- 
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/2753e7d6-d4aa-4e7c-b2bc-8f41bbe7a690%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590

[Foppe de Haan]

On Saturday, March 23, 2019 at 2:18:52 AM UTC, CooSee wrote:
> i found this Error in Xorg.0.log - only with newer Kernel.
> 
> [   123.712] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
> [   123.719] (WW) glamor: Failed to allocate 200x200 FBO due to 
> GL_OUT_OF_MEMORY.
> [   123.719] (WW) glamor: Expect reduced performance.
> 
> why 4.14.103-1 Kernel can handle the login and newer Kernels not ?
> 
> thx

is there a difference in which driver it loads (lspci -nnk | grep -i vga -A 3)?

-- 
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/d5babfee-f2f7-4f9a-8694-84a2a7dcd5fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590

[Foppe de Haan]

what's ~/.local/share/xorg/Xorg.0.log telling you?

-- 
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/208b7b3a-6acf-4c72-a2cc-46116b779050%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590

[Foppe de Haan]

On Thursday, March 21, 2019 at 5:33:36 AM UTC, CooSee wrote:
> hello,
> 
> i'am a long time FunToo (GenToo) User.
> 
> I bought a Sapphire Nitro + RX590 and thought this will work perfect with 
> Qubes OS.
> 
> But there were some hiccups, because the kernel is to old including very old 
> Firmware files.
> 
> I could only start installer with ' amdgpu.dpm=0 ' and everything went fine.
> 
> After playing around with the System, i decided to reinstall and choose XFS 
> Filesystem (the System is noticeably faster) and just a little SWAP file 
> (1024MB), because my System RAM is 32GB.
> 
> After some research i somehow managed the Problem regarding not included ' 
> amdgpu' Driver - just installed it from an old Fedora 25 Repository - and i 
> also downloaded current available Firmware files from Fedora 31 Repository 
> and copied to dom0 ;-).
> 
> I was happy to see new Kernels, but none of them are working !
> 
> On the Lightdm login screen, there are some graphic glitches, just the 
> backround and after typing my user Password, Lightdm crashs and toss me back 
> to Login menu.
> 
> Only working Kernel without glitches are 4.14.74 and 4.14.103 with 
> 'amdgpu.dpm=0 and plymouth.ignore-serial-consoles' grub option.
> 
> I also tried to compile a kernel with the config from my Funtoo System, but 
> the behaviour is the same, no login possible or the Desktop just crashs after 
> some time and i'am back to login screen.
> 
> I must admit that RPM based System are PITA including SystemD and XFCE is a 
> ugly Desktop Environment - i hope MATE will be available in the Future.
> 
> And i also hope you switch to Debian (or maybe to GenToo) for dom0, because 
> it is uncomplicated and APT is very easy to handle.
> 
> I'am wondering why all new Kernels don't work on my System - is dom0 just to 
> old?
> 
> here's my System:
> 
> ---
> 
> bequiet! Silent Base 800 Black
> 
> MSI C236A Workstation - Intel Xeon E3-1245v5 - 32GB RAM Kingston - Sapphire 
> Nitro+ Radeon RX590 8G
> 
> Samsung SSD PM961 M.2 128GB - Samsung SSD 840 EVO 120GB - Crucial m4 SSD 128GB
> 
> Creative Sound Blaster RX PCIe - Logitech Speaker System Z623 2.1
> 
> Logitech G110 Keyboard - Optical Gaming Mouse G400 
> 
> ---
> 
> thx

That seems strange. There was an issue with the firmware not supporting the rx 
590 properly due to some last-minute changes, but kernels 4.19 and up should 
support it just fine, so long as you have the newer one.

-- 
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/06418773-5921-4e60-a760-0853b77eeaa9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: i9-9980XE or i9-7980XE on Gigabyte X299 DESIGNARE EX or AMD 2990WX TR on Gigabyte X399 DESIGNARE EX?

[Foppe de Haan]

On Tuesday, March 19, 2019 at 3:46:22 AM UTC, jrsm...@gmail.com wrote:
> I knew that I get more cores per $ with AMD but hadn’t heard that IO would be 
> better too.  Can you paste a link?

well, you get 64 pcie lanes rather than the maximum of 44 intel offers (they 
sometimes like to write x299 offers "68", but 24 of those are hugely 
bottlenecked by the fact that the chipset only has a pcie gen3 x4 connection 
with the CPU).

-- 
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/e38c4909-be34-4562-acc8-e6921ec283b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: i9-9980XE or i9-7980XE on Gigabyte X299 DESIGNARE EX or AMD 2990WX TR on Gigabyte X399 DESIGNARE EX?

[Foppe de Haan]

On Saturday, March 16, 2019 at 12:11:13 AM UTC+1, jrsm...@gmail.com wrote:
> There's nothing even close to these on the HCL, but would like to know if 
> anyone has attempted either of these with 4.0.1 and succeeded.  These are 
> essentially the same base hardware as given in the BoM for the recently 
> announced System76 Thelio Major open source hardware desktop systems.

other TR-based systems have been used (see 
https://github.com/QubesOS/qubes-issues/issues/4309), and beyond that you just 
need kernel support, which there is. So you should be fine (with either, though 
the former will ofc set you back well over a grand more, for less i/o, threads).

-- 
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/4166ca92-87c5-477f-b953-310e78a1731d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

[Foppe de Haan]

On Monday, February 25, 2019 at 8:49:11 AM UTC+1, 799 wrote:
> Would you mind sharing your ISO, so that I can use it for testing? I want to 
> know before what is working before going through the hazzle and build an own 
> ISO.
I'd appreciate this as well. :) 

-- 
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/ba06888a-0a17-4ccd-83d8-df90c3894b7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: thunderbird address book corrupted

[Foppe de Haan]

On Sunday, February 24, 2019 at 10:04:30 PM UTC+1, Jon deps wrote:
> Hello, I realize it's not exactly a qubes thing.
> but, does anybody else unable to save any new entries in thunderbird 
> address book

try updating tb, looks like it's a bug in 60.5.

-- 
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/f0e9ee8d-f9d4-4c3f-aa00-387cdb0dacdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: hcl for qubes 4.0 or 4.0.1 is it good?

[Foppe de Haan]

On Thursday, January 31, 2019 at 11:45:29 AM UTC+1, Panini Panini wrote:
> joi, 31 ianuarie 2019, 02:32:03 UTC-8, Panini Panini a scris:
> > nJoy Titan 600, 600W Real Power, PFC Activ, 80 Plus Bronze
> >  Seagate Barracuda, 2TB, 3,5'', 256MB
> >  ASUS PRIME H270-PLUS, LGA1151, H270, TPM, M.2
> >  Intel Core™ i5-7400, 3.00Ghz, Kaby Lake, 6MB, Socket 1151, BOX
> > Corsair Vengeance LPX 8GB DIMM, DDR4, 2400 MHz, CL 16, 1.2V, X2
> 
> 16GB RAM doesnt work fine? and a ssd with 500gb instead of hdd will be more 
> good?

ah, I didn't understand the "x2" as such.

-- 
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/cd29d109-020e-4374-a1cf-3ed19b63d13f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: hcl for qubes 4.0 or 4.0.1 is it good?

[Foppe de Haan]

On Thursday, January 31, 2019 at 11:32:03 AM UTC+1, gabia...@gmail.com wrote:
> nJoy Titan 600, 600W Real Power, PFC Activ, 80 Plus Bronze
>  Seagate Barracuda, 2TB, 3,5'', 256MB
>  ASUS PRIME H270-PLUS, LGA1151, H270, TPM, M.2
>  Intel Core™ i5-7400, 3.00Ghz, Kaby Lake, 6MB, Socket 1151, BOX
> Corsair Vengeance LPX 8GB DIMM, DDR4, 2400 MHz, CL 16, 1.2V, X2

should work fine, though once you decide whether you want to move to qubes 
permanently, you'll probably want more RAM, and an SSD.

-- 
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/e127fe15-ed61-456b-8406-5f629ec3ec9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Archlinux template for Qubes R4 build is working

[Foppe de Haan]

For me, the template builds just fine, but thunderbird-qubes and the GUI )file 
transfer agent integrated with thunar are missing. (invoking these via the CLI 
works fine, though.)

-- 
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/e6d450f3-6b3f-4a5f-b715-53b043c059fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] last qubes-dom0-update brings kernel 4.19 and crashs login

[Foppe de Haan]

On Wednesday, January 23, 2019 at 9:11:31 PM UTC+1, Sergio Matta wrote:
> > Do you see text login available? Maybe on tty2 (alt+ctrl+f2)? You can
> > login there and see lightdm service status (`sudo systemctl status
> > lightdm`), which is responsible for the graphical login. If it's failed,
> > what it says there (you should have few log lines there)?
> 
> 
> Yes, It fails because the video driver. My card is a radeon rx-560 but there 
> was no radeon driver installed. It was working with vesa driver. 
> Now I already installed it but the error continues when I choose kernel-4-19 
> on grub.
> The testing repository was enabled in my yum repo cfg.
> 
> Don't worry, it is working fine with kernel-4.14. If you need, there is some 
> log files bellow.
> 
> 
> > It would be also useful to check X server log - /var/log/Xorg.0.log -
> > especially if you see any error message at the end.
> > 
> > You should be able to choose older version in grub menu.
> 
> Yes, that was what I did and I change to automatically boot the kernel-4.14.
> 
> I love Qubes! Thank you!!

rx 560? Have you tried adding 'amdgpu.dc=1' to the kernel parameters?
hd7790 should work fine using the old radeon driver though.

-- 
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/ed23da2f-7b72-4770-93e4-d4ab81e578ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Which parts of qubes-builder are guaranteed to work/supported?

[Foppe de Haan]

On Wednesday, January 2, 2019 at 10:35:37 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le mercredi 2 janvier 2019 21:49:22 UTC+1, Achim Patzner a écrit :
> > Hi!
> > 
> > 
> > Is it worth creating issues if certain parts of the Builder tools do not 
> > work (e. g. template-local-centos7 or template-local-fc29+xfce) which would 
> > be creating things not in the Qubes distribution?
> > 
> > 
> > 
> > 
> > Achim
> 
> What do you mean by 'parts'? The build of CentOS 7 and Fedora 29 with XFCE 
> flavor works well. I did a build last week for both of them. Can you be more 
> precise please?
> 
> Frédéric

OT, but could you briefly clarify the benefit of running the xfce flavor over 
the generic f29 template?

-- 
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/12123786-7672-48ed-aab6-7e443df5ac76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: More information needed about Qubes security

[Foppe de Haan]

On Monday, January 14, 2019 at 12:17:21 PM UTC+1, Alexandre Belgrand wrote:
> Hello,
> 
> I am still brooding over before installing Qubes.
> 
> My first thinking is that since Intel ME backdoors provide full access
> to authorities, there is no way we can stop government agencies. Recent
> research (read 1) shows that Intel ME has access to all parts of a
> computer, even switched-off. 
> 
> This is not an NSA problem. If the NSA can do it, then any government
> agency including the Chinese, the Russians, the Germans, the French,
> India, etc .. can break into anyone's computer.
> 
> Intel ME even includes a VNC server (VNC is crap), which should be able
> to display dom0. Intel ME has direct access to network cards and
> connections are routed to the Intel ME before they reach the network
> stack. Therefore, network connections from intruders should be
> invisible to dom0 and other cubes.
> 
> There is also the alternative to switch to Coreboot and try to disable
> Intel ME. But I read that on my laptop, a Lenovo Thinkpad X230, it was
> impossible to completely remove Intel ME. Intel ME is constantly
> monitoring hardware and if it is removed, the computer will reboot
> after 30 minutes. In the X230 legacy bios, I disabled Intel ME
> completely, but a test in Gnu/linux shows it is still active.
> 
> Also, when installing Coreboot, I loose Lenovo's frequent BIOS updates,
> and I am not very sure to be protected against Intel meltdown and
> Spectre.
> 
> So a reasonable approach to me is to rely on a firewall and monitor
> incoming and outgoing packets. Network surveillance is IMHO the only
> way to discover an attack. I am using PC Engines APU with coreboot and
> open hardware, which is the best I can find in my price range.
> 
> Network surveillance is how I discovered last time that my computer had
> been hacked, when I saw packets flowing to China. 
> 
> Since then, now I keep no personal document on a computer. 
> 
> When I discovered Qubes, it caught my eye but ...
> (a) It does not protect from Intel ME backdoors.
> (b) Has a Linux firewall running on a normal Fedora kernel, not even
> compiled statically with a limited number of modules. This firewall can
> be replaced with OpenBSD as discussed on the mailing list.
> (c) Using Coreboot might be an alternative, but I don't know how secure
> is Coreboot against other attacks.
> 
> So my first opinion would be that Qubes can only protect against a
> simple software attack, not a complex hardware attack.
> 
> What's interesting in Qubes is that :
> (d) It has reasonable defense in depth, at the scale of today's
> hardware.
> (e) It has good privacy protection. For example, it can protect me and
> my family when surfing on Internet and keep my data private.
> 
> If you can tell me anything more about Qubes security, I am really
> interested. I am still waiting for more information before stepping on.
> 
> (1) What we have learned about Intel ME
> http://blog.ptsecurity.com/2018/11/what-we-have-learned-about-intel-me.html

can the IME really talk to any NIC? Or just the ones that it has drivers for 
(e.g., other intel products)? If the latter, wouldn't an add-in card (or USB 
dongle) solve that 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/7066e924-5548-42ef-b3b6-48bf3a7ffb25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Using OpenBSD as Qubes firewall

[Foppe de Haan]

On Sunday, January 13, 2019 at 8:29:02 PM UTC+1, alexandre...@mailbox.org wrote:
> Dear all,
>   
>   
> 
>
> 
>   
>   
> 
>Pardon my ignorance, is it possible to use OpenBSD to provide firewalling 
> to Qubes?
>   
>   
> 
>I have nearly zero confidence in GNU/Linux although I use it everyday.
>   
>   
> 
>
> 
>   
>   
> 
>Kind regards,

have you looked into Mirage?

-- 
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/222b20c7-0c08-4583-954f-c88b54229b8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] fedora-29-minimal sys-net/firewall problem

[Foppe de Haan]

On Saturday, January 12, 2019 at 6:59:38 AM UTC+1, rumsey@gmail.com wrote:
> Thanks to Ivan, I figured it out (with a bit of luck).
> 
> After comparing packages in his working template to my own, I first tried to 
> install:
> 
> dbus-glib
> ipcalc
> iproute
> iproute-tc
> iputils
> 
> That fixed it as far as I can tell. I now have a working sys-net and 
> sys-firewall with the fedora-29-minimal template. I'm assuming the ip* 
> packages were the key, but I don't really have any idea.

Thanks for taking the time to compare the installed package lists. :)

-- 
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/558e0ef1-a4bb-4f4e-9df2-9d078008c9f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Debian minimal template

[Foppe de Haan]

On Thursday, January 10, 2019 at 1:15:02 AM UTC+1, unman wrote:
> If any one is interested there's a prebuilt debian-9-minimal template
> currently available in itl-testing.
> You can install it:
> qubes-dom0-update --enablerepo=qubes-template-itl-testing 
> qubes-template-debian-9-minimal
> 
> The template is a little smaller than stock stretch, and somewhat
> leaner. To get root you'll need to use 'qvm-run -u root  xterm';
> install qubes-core-agent-passwordless-root (and polkit) if you want
> that feature.
> 
> If you have any comments or suggestions for debian minimal post them here.
> There's no documentation as yet, but the Fedora-minimal guide should come
> in handy.
> 
> Enjoy
> 
> unman

I am, thank you for your efforts. :) Working fine for sys-usb, sys-net, sys-fw.

-- 
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/b6c2c64a-4187-48e2-a5d4-9af94b8ec263%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] old version of xscreensaver

[Foppe de Haan]

On Friday, January 4, 2019 at 1:52:01 AM UTC+1, unman wrote:
> On Fri, Jan 04, 2019 at 12:03:49AM +0100, Frédéric Pierret wrote:
> > We built the upstream package of xscreensaver in current-testing for
> > both Qubes 3.2 and 4.0.
> > 
> > Welcome back to XFCE Chris :D !
> > 
> > On 1/3/19 11:56 PM, Chris Laprise wrote:
> > > On 01/03/2019 02:00 PM, Achim Patzner wrote:
> > >> Am Mittwoch, den 02.01.2019, 20:42 -0800 schrieb pixel fairy:
> > >>> xscreensaver complains about being an old version. doubt this
> > >>> matters, but might scare some users.
> > >>
> > >> There are worse problems with it (and some of them depend on X and the
> > >> hardware you're running on) which might also warrant finding something
> > >> different. I just have to find some time for constant rebooting of my
> > >> system to create a meaningful bug report.
> > >>
> > >> (To give you an idea: Imagine a machine (let's call it Lenovo P52) with
> > >> multiple GPUs where certain output channels are connected to one of the
> > >> GPUs only starting a screen server. If you connect your second monitor
> > >> to the right port the screen saver will not blank one of them if you
> > >> start X without an appropriately xorg.conf... And to make things worse
> > >> it also depends on the GPU you are using and the phase of the moon.)
> > >
> > > The bad screensaver is one of the reasons I switched back to KDE, and
> > > why I recommend it to other Qubes users. The default environment
> > > doesn't rise to the level of an every day functional desktop.
> > >
> 
> Is this a thing now? Is Qubes going to provide updated packages for any
> other software?

nah, just xscreensaver because it's essential to the Qubes UX. ;)

-- 
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/ed2f6ee4-49fa-4916-9d1c-be2f6b2cfdad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: AMD Ryzen / ASUS Prime B350 Plus

[Foppe de Haan]

On Sunday, November 18, 2018 at 1:18:57 AM UTC+1, Gottfried F. Zojer wrote:
> Hello to everyone,
> 
> 
> Myself I am new to Qubes after reading about it in Linux-Magazine December 
> 2018 edition
> Just curios if somebody is using it on a AMD Ryzen system 
> Try to evaluate it if it can be used for memory forensics and in combination 
> with Kali Linux
> Unfortunately first boot from SanDisk Ultra Flair USB 3.0 with the follow 
> errors(screenshots)
> 
> 
> Any feedback welcome 
> 
> 
> Rgds Gottfried 

did you check the installation medium integrity? cd check failed suggests some 
kind of checksum error. There are no hw issues that would prevent you from 
using a ryzen system, aside from installation difficulties if you have an APU 
(because the regular 4.14 kernel doesn't support vega out of the box).

-- 
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/3897e2ab-58aa-4316-925a-ccc64b10976b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: B450 Pro4 + Ryzen 5 2400G installation issue

[Foppe de Haan]

On Friday, November 23, 2018 at 5:59:15 PM UTC+1, stefan neuhaus wrote:
> with stable release Qubes-R4.0-x86_64.iso i got the error "x startup failed, 
> aborting installation ... PANE IS DEAD"
> i also tried to install the new Release Candidate 4.0.1-rc1, but it did#t work
> i use a desktop system with integrated graphics - AMD Ryzen 5 2400G - ASRock 
> B450 Pro4
> a community user told me he runs qubes on this configuration smoothely, so i 
> build up the system. 
> 
> he told me later he also had the "pane is dead" problem and fixed it with the 
> thread #3340. (i wrote a comment to the thread but nobody answered for three 
> days so i deleted it and opened this new issue.)
> with "tab" i edited the command line like proposed with different bios 
> settings (legacy/uefi) but it didn#t work (-> see attachement).
> 
> also i edited with the windows program "anyburn" the config-files due to the 
> thread in the iso. i burned a usb stick wit rufus but it wasn´t possible to 
> write with dd. pane is dead was the result again.
> as far as i understand its a graphic card issue and x server is not starting. 
> so i tested with a radeon r7 370 and a AMD FirePro W2100 graphic card. the 
> installer menue loaded on both cards and i could choose the language, but 
> afterwards i got the message "This hardware lacks features required by Qubes 
> OS. Missing features: HAP/SLAT/EPT/RVI. Without these features, Qubes OS will 
> not function normally. " When i reboot the system i got a [dom0] Error 
> "...sys firewall failed... stderr: Start failed:... could not find 
> capabilities for arch=x86_64... " thread #3208 doesn`t help for 
> troubleshooting. when i remove the graphic card and boot with the integrated 
> graphic the system halted with error.
> i also tried to boot with the ssd of my working qubes laptop. but i only got 
> a black screen.
> i know only basic linux so for command line i need more detailed instruction.
> 
> 
> can anyone help?

afterwards, if you install kernel-latest in dom0, the APU should work as well.

-- 
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/c7877f5c-0988-48c2-89ad-e815edb2bc61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - Ryzen 5 1600, Asus x370 Prime Pro, RX Vega 56

[Foppe de Haan]

On Thursday, November 8, 2018 at 4:29:48 AM UTC+1, _...@lvh.cc wrote:
> On Monday, October 22, 2018 at 2:28:37 AM UTC-5, Foppe de Haan wrote:
> > Works splendidly once installation's over; installation's only an issue 
> > because the current LTS kernel supplied with the installation medium (r4.0) 
> > doesn't support the RX Vega card (and Vega-based APUs) yet.
> 
> How'd you resolve that issue? Secondary video card?

yeah. 
Alternatively, look into making a kickstart file, some hints here -> 
https://groups.google.com/forum/#!msg/qubes-users/-9qRHSkwfy8/CCx08nnTVEAJ

-- 
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/32b3e1f3-b0e6-4f42-89c5-797d913269d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Where to find the Fedora-29 Templates (Announencement Qubes 4.0.1-rc1)

[Foppe de Haan]

On Wednesday, November 7, 2018 at 7:38:45 PM UTC+1, 799 wrote:
> Hello,
> 
> 
> I've read about the new release candidate 4.0.1
> 
> https://www.qubes-os.org/news/2018/11/05/qubes-401-rc1/
> 
> 
> it was mention that it includes a fedora-29 template VM.
> As most of my AppVM are fedora-28 based and the setup is scripted, I would 
> like to reinstall the templates using the new fedora-29 template.
> 
> 
> I've updated dom0 via 'sudo qubes-dom0-update' and tried to find the new 
> fdora-29 template via 'sudo qubes-dom0-update --action=search qubes-template' 
> but I only get the normal templates back.
> 
> 
> What needs to be done to get the new fedora-29 template (I am mainly 
> interested in the fedora-xx-minimal templates).
> 
> 
> - O

try enabling templates-itl-testing

-- 
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/5cede453-a2a2-4280-b30f-61a19dc5713a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: My farewell to Qubes OS!

[Foppe de Haan]

On Thursday, October 25, 2018 at 12:21:51 PM UTC+2, Joanna Rutkowska wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hello Qubes devs and users!
> 
> It's been nearly 9 years[*] since I sent the first internal email
> within ITL to Rafał Wojtczuk and Alex Tereshkin with the original idea
> for making Qubes OS. Shortly after this, we started drafting the
> original architecture and writing some early PoC code...
> 
> Today, I've made an announcement I'm switching focus to another area
> of work and joining the Golem Project as a Chief {Strategy, Security}
> Officer:
> 
> https://www.qubes-os.org/news/2018/10/25/the-next-chapter/
> 
> https://blog.golemproject.net/joanna-rutkowska-joins-golem-as-chief-strategy-security-officer-13f12f0c11c0
> 
> I'd like to thank all the people who made Qubes OS possible, which
> includes: the whole ITL team, all the community contributors, and, of
> course, all the Qubes OS users!
> 
> Qubes OS will continue under the lead of Marek Marczykowski-Górecki,
> who have been a de-facto lead for all the day-to-day development for
> quite some time already!
> 
> Thanks, Marek! Thank you, all!
> 
> Cheers,
> joanna.
> 
> [*] FWIW, the exact date was November 11th, 2009.
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCAAdFiEEtR14vbBDAuE0X2Ly1F2dklVl1NIFAlvRmTYACgkQ1F2dklVl
> 1NIiDxAAtwm3qM1Rq3ow67q5bLu+1VnuM0NQrN/crLu+FDOdaa9XNzSsdWz97UoN
> 2VsRO+RICNttrR7MAaWSgTXtBKOMuSXYc7s5r7VVFtx4qW0xyRaxbr7vBqJRDM5n
> 6eCLdjAFf1Xh8Ju5eDnBJGx41EIywO4Jba3z9+Ww2xyBycQAYY22yRQf6ANlWfwW
> XE0HgBuaJtAEReJc7qpzlG/iwLa/de1eqVa9kOS4HrESllE9wP7qXLrnmwr/yH19
> 2twe3QVS29uVYzPOam6PiCg1PN4AjsYKvihy/Tap11bYfdr1L8OjmE9+KrDPFPek
> MaWlkl/OoiFZsQHhj1somMfFNKH82oTW3zIAZCmmOZgQHgt6T1KDzjehFTASJeFp
> WNmvmowDYfcVYEdjEXQKP78mpxlYz6fChr/A4x3TX64+KsltdZA7l266OMfpXvL4
> Mja4SUvEKqLbyEQxCaDnOwm4cV7k/dHtOXE5fREzUfi+YVu14yVNkPRxg9UpgtCa
> sV/PY7AwOe4JqxV+8VlWWmX0amNf8ZEtz51F2eH6NZZYGaRtTXxTKW6Aad0XHg7p
> 8m2gvH8YWnGPX7ckofcpL7NHR5B6EauXoHKeQZgV9Ix0NQf2CNvBv5ZxZ7IYannH
> mJEcpgRYMtG5b8+x05hBCb7CP5T/tQpt2r5jIK3eqwEzcPY//H8=
> =1ZqA
> -END PGP SIGNATURE-

thank you for your efforts on this, as well as your insights. :)

-- 
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/32391eda-9333-4cea-9584-64d3b71fadbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4 AMD Microcode

[Foppe de Haan]

On Wednesday, October 24, 2018 at 1:46:27 PM UTC+2, qube...@go-bailey.com wrote:
> What is the current status of Qubes 4 in relation to microcode updates 
> for AMD processors?
> 
> Are the latest spectre, etc. related updates for all applicable 
> processor families provided?
> 
> Thanks in advance.

iirc there was new microcode accompanying the latest xen point release 
(surrounding the latest security bulletin).

-- 
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/e0108efc-a5ac-4955-918b-cab5a70e2eef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: choosing video card Qubes "some direction, please"

[Foppe de Haan]

On Monday, October 22, 2018 at 11:24:10 AM UTC+1, bartst...@gmail.com wrote:
> Looking for a video card that is compatible with Qubes 4.
> I have read that ATI Radeon is the best choice.
> Does anyone have an advice, current model ATI Radeon? 
> Preferably a video card that is recognized by Qubes, without hassle.
> I have a budget of 100 to 150 euros.
> 
> Many thanks!
> 
> System HW:
> Gigabyte GA-270-gaming-K3
> SSD 500 BG Samsung 860 EVO sata 6
> Intel I5-7500 lga 1151
> 16 GB DDR4 2400 Team group delta red

why do you want one? The iGPU included in the i5-7500 should work fine too. 
That said, any rx 460, RX 550, RX 560, or RX 570 4gb should do the trick. 

-- 
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/03208aa5-4c43-4759-936a-38481fd4b2a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Ryzen 5 1600, Asus x370 Prime Pro, RX Vega 56

[Foppe de Haan]

Works splendidly once installation's over; installation's only an issue because 
the current LTS kernel supplied with the installation medium (r4.0) doesn't 
support the RX Vega card (and Vega-based APUs) yet.

-- 
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/69099676-e1b3-4e7c-a94f-d465b7eacf9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-System_manufacturer-System_Product_Name-20181022-091951.yml
Description: Binary data

Re: [qubes-users] qubes r4 installation no longer boots, apparent corruption. anything I can do to get at the data?

[Foppe de Haan]

On Wednesday, October 17, 2018 at 4:44:10 PM UTC+1, unman wrote:
> On Wed, Oct 17, 2018 at 03:51:57AM -0700, Foppe de Haan wrote:
> > (Note that I'm using BTRFS.)
> > 
> > When I try to mount the data volume using a Fedora 29b live image, I get 
> > "can't read superblock on 
> > /dev/mapper/luks-5047683c-2a3f-463d-8538-53701743acca."
> > 
> Ah, OK hadn't realised that.
> Is there a specific error message - if it was included in that image you
> attached can you tell me what it was? 
> 
> If there is a specific BTRFS error have you tried repairing the file
> system? Look at the manpage for btrfs-check.
> There are some dangerous options to try if all else fails:
> 'btrfs check --repair' often does what it says.
> If that doesn't work or you have a tree error, then you could try 'btrfs
> check --init-extent-tree'. I've sometimes doubled on that and recovered
> access. ymmv.
> (If you have a cloned disk you will feel much happier about trying out
> these "dangerous" options, of course.)
> 
> unman

Thank you for the advice. I managed to recover 1 private image, the rest was 
salvageable, for whatever reason. (Even VMs that hadn't been started for days, 
so there must've been another issue than the one I mentioned; because if not, 
the only other conclusion I see is that btrfs is bizarrely fragile.)

-- 
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/f3c104b3-4b64-4124-ada2-d6bbad56bc2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes r4 installation no longer boots, apparent corruption. anything I can do to get at the data?

[Foppe de Haan]

(Note that I'm using BTRFS.)

When I try to mount the data volume using a Fedora 29b live image, I get "can't 
read superblock on /dev/mapper/luks-5047683c-2a3f-463d-8538-53701743acca."

-- 
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/0b7a04f4-3f5f-45ba-9e70-516ec8bcdf0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes r4 installation no longer boots, apparent corruption. anything I can do to get at the data?

[Foppe de Haan]

On Tuesday, October 16, 2018 at 4:55:47 PM UTC+2, unman wrote:
> On Tue, Oct 16, 2018 at 12:44:45AM -0700, Foppe de Haan wrote:
> > So it appears that something went very wrong during a dom0 update.
> > The emergency mode of the regular boot process does attempt to load, but 
> > hangs or stops before it finishes, so I can't get a shell that way either.
> > Have also tried to 'rescue' the system via a qubes installation medium, but 
> > after entering the correct LUKS passphrase, it says something like 'no 
> > valid linux installation found', and stops.
> > 
> > Anyone have suggestions as to what I might try next, if anything?
> > 
> 
> Depending on how important your data is to you you might want to start
> by cloning the disk. (I'd recommend clonezilla for ease of use.)
> 
> You can check that your data is safe by booting from a live image -
> kali, knoppix etc.
> Then try to mount your Qubes partition - you'll need to use cryptsetup
> luksOpen to decrypt the disk, and you should then be able to mount the
> partition.
> You don't say whether you are using 3.2 or 4.0, and the approach to take
> will depend on that. In 4.0 individual qubes by default use thin pools
> so you will need to identify the qubes you are interested in and check
> in /dev/qubes-dom0 using 'ls -l' which of the device files in /dev
> match.
> You can then mount those devices and copy out the data.
> 
> Once you've secured all your data, you can try for recovery of the
> system. I've had some success in doing this but frankly it's almost
> always better to reinstall, particularly as you don't know *what* went
> wrong.
> If you've got recent backups or don't care about the data, I would just
> skip those steps and reinstall.
> 
> If you need specific advice give a little more detail about how you had
> the system configured and exactly what steps you've taken so far.
> 
> Best of luck
> 
> unman

Thanks, will do (wrt cloning). Last backup was from april, so I'd like to 
recover if possible. r4.0; as to what went wrong, not sure exactly; 
qubes-dom0-update finished properly, but fairly soon afterwards, I experienced 
a hard reboot, likely due to unstable memory settings, which I had been 
tinkering with a bit.
So far all I've tried is to boot and/or repair the system, but I can't get the 
volume to mount, so haven't made any progress yet.

-- 
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/f63a2f06-e98d-4bab-bb9a-b533bff810c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Purchase advice, Qubes laptop: ASUS ROG Strix GL503GE ?

[Foppe de Haan]

On Friday, September 21, 2018 at 9:13:45 AM UTC+2, Foppe de Haan wrote:
> should do okay. All Intel CPUs have an integrated GPU, so that's fine. If you 
> want a development machine, though, I'd sooner go for the Asus ROG GL702ZC 
> (Ryzen 7 1700, 8 cores, 16 threads). May be a bit harder to find, though.

(It actually doesn't have an iGPU, but the rx580 has mainstream kernel support, 
so not an issue either.)

-- 
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/02969ef7-4c44-4852-a09e-72f6b1f35840%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Purchase advice, Qubes laptop: ASUS ROG Strix GL503GE ?

[Foppe de Haan]

should do okay. All Intel CPUs have an integrated GPU, so that's fine. If you 
want a development machine, though, I'd sooner go for the Asus ROG GL702ZC 
(Ryzen 7 1700, 8 cores, 16 threads). May be a bit harder to find, though.

-- 
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/322874a7-2f45-4900-ad98-4dd58d299740%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: cpu

[Foppe de Haan]

I'm afraid so, yeah.

-- 
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/86106a1d-14a2-46b8-b6f4-a790f328f107%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: cpu

[Foppe de Haan]

On Monday, September 3, 2018 at 3:02:24 PM UTC+2, Roy Bernat wrote:
> Hi 
> 
> i have dell xps 9360 . core i7 .   until the update today i had 4 cores . 
> 
> now the dom see only two .   why ?  someone gas an idea .  strange that the 
> computer is feeling faster than ever. 
> 
> Roy

If it's a 7th-gen intel CPU, those "i7"'s only had two real cores with 
hyperthreading making it look like there were 4. HT had to be disabled because 
of https://www.qubes-os.org/news/2018/09/02/qsb-43/ (Known to affect Intel 
CPUs, doesn't look like it affects AMD.)

-- 
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/930f888f-1c67-4b7f-b295-a35911b36ca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: What CPU are you running for Q 4.0?

[Foppe de Haan]

On Monday, May 21, 2018 at 11:30:40 PM UTC+2, deusestverita...@gmail.com wrote:
> Running a i7-8750H on Qubes 4.0 and it has failed.
> 
> Problems mentioned here:
> https://groups.google.com/forum/#!topic/qubes-users/hJZLAP0kFG4
> https://groups.google.com/forum/#!topic/qubes-users/hmYxqUV7R5U
> 
> People have mentioned running i7-8700K with Qubes 4.0 and it also failed.
> 
> So.. what is the most powerful Processor that you have used with Qubes 4.0?
> 
> 
> 
> THANK YOU 
> BEST
> ERIN D.
If you're looking for a desktop replacement, 
http://www.microcenter.com/product/481879/rog_gl702zc-wb74_173_gaming_laptop_computer_-_black#tab-specs
 should serve you (battery life is not great for obvious reasons). (I have a 
ryzen CPU -- 1600x -- with older Radeon graphics card (which has kernel 
support), works splendidly.)
Your issues with q4 probably don't stem from the CL cpu though, but from 
problematic Pascal support.

-- 
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/f1b6f03a-ae24-4ebf-bd45-bd7f4daebc38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4 ISO..

[Foppe de Haan]

On Friday, April 20, 2018 at 2:14:38 AM UTC+2, Drew White wrote:
> On Thursday, 19 April 2018 18:35:12 UTC+10, Foppe de Haan  wrote:
> > On Thursday, April 19, 2018 at 3:42:18 AM UTC+2, Drew White wrote:
> > > Hi folks,
> > > 
> > > Is there anywhere I can find out what the Qubes 4 ISO contains to install?
> > > Are there any minimal install versions?
> > 
> > Hi Drew,
> > 
> > basically the same elements as the r3.2 installer contained. No, there is 
> > no minimal installer.
> 
> I just figured there may be someone that built Qubes using the minimal 
> templates, and not the large templates, or similar. Without all the bloatware 
> that Qubes has in the systems.

good luck with that.

-- 
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/b8650528-d941-4a56-bbad-dadadc7dcab7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4 ISO..

[Foppe de Haan]

On Thursday, April 19, 2018 at 3:42:18 AM UTC+2, Drew White wrote:
> Hi folks,
> 
> Is there anywhere I can find out what the Qubes 4 ISO contains to install?
> Are there any minimal install versions?

Hi Drew,

basically the same elements as the r3.2 installer contained. No, there is no 
minimal installer.

-- 
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/175fd395-0153-452c-a484-c7918fd9639b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Keyboard not working: How to make the buying decision?

[Foppe de Haan]

On Saturday, April 14, 2018 at 6:59:06 PM UTC+2, 00010...@gmail.com wrote:
> Here's the summary of outcome:
> 
> - When I use QubesOS out-of-the-box (without any special configuration), the 
> mentioned USB mouse works right away, but not the USB keyboard.
> 
> - When I follow the instructions for the USB keyboard at 
> https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard then it works 
> correctly (as advertised) already at the LUKS password input. However, 
> neither keyboard nor mouse work at the QubesOS user/session authentication 
> (once logged in, both do however work again).
> 
> Should I file a bug report?

I sometimes ran into this, when sys-usb was too slow or too fast to start, idk 
which. Reconnecting the USB plug usually worked.

-- 
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/153b7366-19f9-46f2-b13a-a3518414a27b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Keyboard not working: How to make the buying decision?

[Foppe de Haan]

On Saturday, April 14, 2018 at 3:11:37 AM UTC+2, tai...@gmx.com wrote:
> On 04/13/2018 03:01 PM, 00010age...@gmail.com wrote:
> 
> > Is there a way to know which keyboards are incompatible with QubesOS?
> >
> > Or do we just need to keep on buying keyboards until one works?
> 
> You need to enable the keyboard sys-usb forwarding permission in qubes
> settings files, there is a guide on the website for that.
> 
> > I'm asking because I bought the (IMHO best ergonomic mouse/keyboard combo; 
> > wireless) "Microsoft Sculpt Ergonomic Desktop" [0], but only the mouse 
> > works (and only once you have logged into your QubesOS session), not the 
> > keyboard.
> >
> > So based on what is one supposed to make the buying decision?
> >
> The best keyboards are made in a first world country and have firmware
> that can't be internally flashed - the unicomp keyboards fit the bill
> here and are much more secure as the firmware can't be re-written and
> they are made in usa thus more trustworthy than one that is made in china.

You've really drunk the cool-aid, haven't you? Products from the "land of the 
free", with its public-private Stasi (NSA in full cooperation with 
FAANG/Silicon Valley more generally) are inherently "more trustworthy" than 
those made in "China". 
If only the world were that simple.. 
Sadly, that was a lie even when McCarthy and the Cold War were still in full 
swing, let alone now, when everything described in 1984 is both technologically 
completely possible, and enacted (the only difference being that it's done in a 
less blatantly fascist manner than in the book).

-- 
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/84b1e331-a78d-4276-a157-8a57289b214f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Keyboard not working: How to make the buying decision?

[Foppe de Haan]

On Friday, April 13, 2018 at 9:01:23 PM UTC+2, 00010...@gmail.com wrote:
> Is there a way to know which keyboards are incompatible with QubesOS?
> 
> Or do we just need to keep on buying keyboards until one works?
> 
> I'm asking because I bought the (IMHO best ergonomic mouse/keyboard combo; 
> wireless) "Microsoft Sculpt Ergonomic Desktop" [0], but only the mouse works 
> (and only once you have logged into your QubesOS session), not the keyboard.
> 
> So based on what is one supposed to make the buying decision?
> 
> ---
> [0] 
> https://www.microsoft.com/accessories/en-us/products/keyboards/sculpt-ergonomic-desktop/l5v-1

sculpt ergonomic should work fine once you've allowed keyboard and mouse 
forwarding (see the website faq on the usb qube).

-- 
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/eb3b35a3-d1f1-4ac9-95e8-d3df3951171c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Whats the deal with kernels?

[Foppe de Haan]

On Wednesday, April 4, 2018 at 3:21:38 AM UTC+2, sevas wrote:
> Yes, thank you. I have read that entire page, as well as a few other good 
> resources:
> 
> github.com/rtiangha/qubes-linux-kernel/blob/devel-4.14-hard/README.md
> github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md
> 
> 
> Im running into a problem right at the end.
> 
> rpm --add-sign /home/user/*.rpm 
> You must set "%_gpg_name" in your macro file
> 
> I have made the missing file: ~/.rpmmarco
> %_signature gpg
> %_gpg_path /home/user/.gnupg
> %_gpg_name (b4892c28 / mypgp)
> 
> I still get the error. Can I ignore this? 
> Qubes-Builder docs suggests editing the builder.conf and changing NO_SIGN=1
> but that doesnt exactly apply to kernels, does it?
> 
> I dont need to sign my packages, do I? Im not sure if the compiler is failing 
> at
> the rpm signing or if its ignoring and finished.

yes, you can ignore this, though you can also just follow a gpg guide to create 
a signature for your own use. Not necessary, but why not? :)

-- 
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/093dd8ad-674d-45fd-b499-d252c93d784b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] GPU?

[Foppe de Haan]

On Saturday, January 20, 2018 at 2:53:38 PM UTC+1, Alex Dubois wrote:
> On Saturday, 20 January 2018 09:40:36 UTC, Foppe de Haan  wrote:
> > On Saturday, January 20, 2018 at 9:38:06 AM UTC+1, Alex Dubois wrote:
> > > On Thursday, 18 January 2018 22:56:10 UTC, Tom Zander  wrote:
> > > > On Sunday, 14 January 2018 08:12:24 CET r...@tuta.io wrote:
> > > > > Is qubes able to use the computing power of the gpu or is the type of 
> > > > > gpu
> > > > > installed a waste in this issue?
> > > > 
> > > > Relevant here is an email I wrote recently;
> > > > https://groups.google.com/forum/#!msg/qubes-devel/40ImS390sAw/Z7M0E8RiAQAJ
> > > 
> > > I'll reply in that thread about this to stay in topic.
> > > 
> > > But in few words: Not possible until GPU virtualization to have a 
> > > trustable solution.
> > > 
> > > > 
> > > > The context is a GSoC proposal proposal to modernize the painting 
> > > > pipeline of Qubes.
> > > > 
> > > > Today GL using software uses [llvmpipe] to compile and render GL inside 
> > > > of 
> > > > a Qube, completely in software and then push the 2d image to dom0.
> > > > This indeed wastes the GPU.
> > > > 
> > > > 
> > > > [llvmpipe]: 
> > > > https://groups.google.com/forum/#!msg/qubes-devel/40ImS390sAw/Z7M0E8RiAQAJ
> > > > 
> > > > -- 
> > > > Tom Zander
> > > > Blog: https://zander.github.io
> > > > Vlog: https://vimeo.com/channels/tomscryptochannel
> > 
> > Since I am unable to estimate the security aspects of any given approach, 
> > and you do, have you seen this approach? 
> > https://forum.level1techs.com/t/looking-glass-guides-help-and-support/122387
> 
> I am not member of the Qubes core team, I am an avid user/developer and 
> believer :) so my view is only mine...
> The project you mention is doing a great job (for a VMWare workstation type 
> set-up), however as far as I understood the copy is from/to the same GPU. 
> This is where I am NOT comfortable with. As explained the client VM would 
> issue processing requests to the GPU (and may abuse it).
> 
> However, using their work to copy from one GPU (assigned to ONE VM) to Dom0 
> GPU could be good. However you still have the problem with the BW on the bus 
> (luckily depending on your hardware build 2 different buses (your 2 cards are 
> on different PCIe lines). You will not get 144Hz but 60Hz is within reach. 
> Temptation to compress the stream will be there, the decompression code will 
> be in the attack surface.

Thanks for looking at it, and your thoughts. :)

To clarify: their idea indeed is to use two GPUs, since SR-IOV support simply 
isn't an option for regular users (due to artificial market segmentation), and 
according to them, any dom0 GPU that supports PCIe gen3 x4 can handle up to 
4k60 at least.

-- 
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/8d621fb6-33e9-4f19-b5e0-886bd5c759df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] GPU?

[Foppe de Haan]

On Saturday, January 20, 2018 at 9:38:06 AM UTC+1, Alex Dubois wrote:
> On Thursday, 18 January 2018 22:56:10 UTC, Tom Zander  wrote:
> > On Sunday, 14 January 2018 08:12:24 CET r...@tuta.io wrote:
> > > Is qubes able to use the computing power of the gpu or is the type of gpu
> > > installed a waste in this issue?
> > 
> > Relevant here is an email I wrote recently;
> > https://groups.google.com/forum/#!msg/qubes-devel/40ImS390sAw/Z7M0E8RiAQAJ
> 
> I'll reply in that thread about this to stay in topic.
> 
> But in few words: Not possible until GPU virtualization to have a trustable 
> solution.
> 
> > 
> > The context is a GSoC proposal proposal to modernize the painting 
> > pipeline of Qubes.
> > 
> > Today GL using software uses [llvmpipe] to compile and render GL inside of 
> > a Qube, completely in software and then push the 2d image to dom0.
> > This indeed wastes the GPU.
> > 
> > 
> > [llvmpipe]: 
> > https://groups.google.com/forum/#!msg/qubes-devel/40ImS390sAw/Z7M0E8RiAQAJ
> > 
> > -- 
> > Tom Zander
> > Blog: https://zander.github.io
> > Vlog: https://vimeo.com/channels/tomscryptochannel

Since I am unable to estimate the security aspects of any given approach, and 
you do, have you seen this approach? 
https://forum.level1techs.com/t/looking-glass-guides-help-and-support/122387

-- 
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/cdb0d122-d579-4e60-b8d2-db991efa10fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Please help with 8th Generation Intel i5

[Foppe de Haan]

On Friday, January 19, 2018 at 12:32:32 PM UTC+1, Krišjānis Gross wrote:
> On Thursday, 18 January 2018 20:56:10 UTC, donoban  wrote:
> > On 01/18/2018 11:15 AM, Krišjānis Gross wrote:> I did navigate to /tmp
> > and looked at some logs. Unfortunately I do not know what to look for
> > there. Took some screen shots (attached). Does that ring any bells?
> > 
> > I think the problem is:
> > 
> > (EE) VESA(0): V_BIOS address 0xaa7a0 out of range
> > 
> > I've searched a little but I didn't find anything useful. I hope someone
> > could help you on this.
> > 
> > > 
> > > A side question- how can I copy the logs in /tmp to a flash drive or 
> > > something in order to post those here? 
> > > 
> > > Which Linux distribution should I try to run in order to do a reasonable 
> > > comparison?
> > > 
> > 
> > Ideally same as dom0, fedora-24?? I would try to guess what kernel
> > version starts to work fine with it and compare with built-in the qubes iso.
> 
> Thank You for the suggestion! Will check that out. 
> I tried to install Debian 9 on this hardware and all went fine. Only thing 
> that I noticed when installation was finished was that there was a 
> notification that system is running a " software emulated graphics" and 
> therefore CPU usage might be considerably higher. Not sure whether that is 
> relevant though.

Most likely due to lacking hardware support (in the kernel) for the CL graphics 
chip (even though it's little more than a rebrand of KL's). Try installing a 
more recent (ideally 4.14-based) kernel. Iow, it's sort of related, because the 
issues you ran into while installing qubes were most likely also related to 
that.

-- 
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/9cf4df9f-8b0c-449f-b672-31e9b3268d80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Troubleshooting IOMMU compatibility

[Foppe de Haan]

On Tuesday, January 16, 2018 at 8:52:15 AM UTC+1, jspieg...@airmail.cc wrote:
> I cannot get HVMs with attached PCI devices to boot in Qubes 4.0-rc3. My 
> processor (AMD Phenom II X3 B75) does have IOMMU support as far as I can 
> tell from the sources I've found online, but I can't find much info 
> about whether my motherboard (HP 3047h) supports it. There is only one 
> generic "virtualization" option in the BIOS. I found a lot of statements 
> like this online about IOMMU:
> 
> > Please note that just because a motherboard uses a chipset that 
> > supports IOMMU does not mean it is able to and the bios must have an 
> > ACPI IVRS table to enable the use of it. At least one Asus board is 
> > known to have faulty BIOSes with corrupt ACPI IVRS tables; for such 
> > cases, under Linux, it is possible to specify custom mappings to 
> > override the faulty and/or missing BIOS-provided ones through the use 
> > of the ivrs_ioapic and ivrs_hpet kernel parameters.
> 
> What all specific things would I check to see if actions like above 
> would be advisable or if I could possibly get IOMMU working? How can I 
> probe my motherboard's support for it directly? And what kernel options 
> other than the above would be advisable to try for testing purposes? 
> (I'm not really sure how I'd set those kernel options either.)

run qubes-hcl-report , see what it tells you. Bios should ideally have IOMMU 
and SVM settings, SR-IOV optional (and irrelevant for this purpose). 
Which PCI devices refuse to boot?

-- 
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/06dc6176-03e2-45b3-9316-d085fa78a693%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] rc04

[Foppe de Haan]

On Wednesday, January 10, 2018 at 9:35:41 AM UTC+1, Tim W wrote:
> On Tuesday, January 9, 2018 at 2:35:28 PM UTC-5, Chris Laprise wrote:
> > On 01/09/2018 05:17 AM, Roy Bernat wrote:
> > > On Tuesday, 9 January 2018 11:12:17 UTC+2, msg...@gmail.com  wrote:
> > >> On Tuesday, January 9, 2018 at 2:11:06 PM UTC+7, Tim W wrote:
> > >>> On Tuesday, January 9, 2018 at 1:16:10 AM UTC-5, Sven Semmler wrote:
> >  -BEGIN PGP SIGNED MESSAGE-
> >  Hash: SHA256
> > 
> >  On 01/09/2018 12:07 AM, Roy Bernat wrote:
> > 
> > > What about release rc04? it should be release at 8/1 that  was
> > > yesterday .
> > 
> >  Delayed until the devs have a good workaround for SP1/SP2/Spectre.
> > 
> >  /Sven
> >  -BEGIN PGP SIGNATURE-
> > 
> >  iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlpUXggACgkQ2m4We49U
> >  H7b7cQ/9EC8aSC9vSuTNl0rVHQtK040eZIrg5sKbsXXLjQbOLkwcpXjvWCiukzj1
> >  hXvUgWvJs2JHTPd9s8Yu/8KlE9Maf+UcbKGvwTPVG6c4tNOHGFLt7C0bRjYVeCp5
> >  lW7pnb1e4rYX99aoeX5/SdWaScv6XLbx9CnRSazgBIYJ0WqfseUR8tcAE9HqKCau
> >  aVrBlbSKLMGgWDx3rRGxJaBv6wf70zGi4SPMeCPQOg2vOJIRyDVGDTEz7LDp/NlA
> >  VfU+xy6q7FlKeKfecftygpgqYmpgI4OOtsRE4OA8KQRAe9RTq+M+2/nebB8/I8tv
> >  X6kXe23s/BtD8Me958har4Wd0quioRbS/dIyhmgDpCkrrg7Afzwk+AokqBTqyFhs
> >  u2WZwoZiqRvRhlBqYp8dR076hx9zDNKSijkCcX5hPdLyX5+B39FGRuEJwz0a7G2F
> >  h3dgxdRDIM/hxf5Sp2Y9E+O0GZaeERWo1fBdjxdbSZV/5CJTTdHBJfMhQ4RUt4sv
> >  2v7/hlgFAhgSvzfXRxemH8elPERHISQ9j3nlKMsa73pnYWpUqeALVfOINbZE8DrU
> >  54j5NPZOdhSrDaTtoS8hm2bF4+KFFjAw19B8s/HvHlwZ9B5PgFwV3et7fYYDjGrS
> >  k0o3nVqKmsooD+yeR+oU/32qz4E0sOq0AxAS1PplU5Y3aMNiZBY=
> >  =59oT
> >  -END PGP SIGNATURE-
> > >>>
> > >>> Great time to be using a AMD chipset as they are not effected.
> > >>> Wonder if something like this would have been caught years ago if the 
> > >>> microcode was open?
> > >>>
> > >>> This is a big one in terms of the effects it has when mitigated at the 
> > >>> software level.  I wonder what the performance hit will be from 
> > >>> application of whatever patch route Qubes takes?  Projections of 5-30% 
> > >>> hit.
> > >>>
> > >>> As I said Great day for AMD stock LOL
> > >>
> > >> AMD is affected by the SP1/SP2/Spectre as well as Intel and ARM.
> > > 
> > > So he can not dance :)
> > > 
> > 
> >  From my recollection of AMD statements:
> > 
> > SP1: Very hard to exploit on any CPU
> > 
> > SP2: Much harder to exploit on AMD than Intel
> > 
> > SP3/Meltdown: AMD not affected
> > 
> > -- 
> > 
> > Chris Laprise, tas...@posteo.net
> > https://github.com/tasket
> > https://twitter.com/ttaskett
> > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> 
> that sounds correct based on what I have read.  At first AMD claimed it was 
> not effected but it seems as time went on and it was looked at more carefully 
> that has changed.  Still I will take more difficult.  As AMD has such a small 
> share of processor space it makes it a lower target sort of how Apple use to 
> be to windows and linux still is although not like it use to be.  So really 
> with a qubes WS the main issue would be SP2 mitigation.
> 
> Amazing this has been an issue for 10yrs.

Even funnier: Intel (as the primary actor) was warned against this back in 
1995: 
https://pdfs.semanticscholar.org/2209/42809262c17b6631c0f6536c91aaf7756857.pdf

-- 
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/277f3501-fbc9-479e-bed2-65d155fbecf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Tuesday, November 28, 2017 at 6:41:02 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> > guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
> 
> I confirm your log and the behavior. Few days ago, I tried to look on the xen 
> and kernel list to see if there were something bug we need to dig into the 
> problem...need time...

FYI: HW42: "It's an upstream Linux bug. See 
https://github.com/HW42/qubes-linux-kernel/blob/hw42/latest/patches.xen/xen-Fix-set-clear-_foreign_p2m_mapping-on-autotransl.patch
 for a patch."

https://github.com/QubesOS/qubes-issues/issues/3404#issuecomment-355724725

-- 
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/27e83baa-5d86-411f-b57b-4f2f276fe0a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

fepitre, reg, FYI: 
https://github.com/QubesOS/qubes-issues/issues/3404#issuecomment-355724725

-- 
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/a888544b-6ed7-4014-ab05-30e7e43cad54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: qubes-mirage-firewall 0.4

[Foppe de Haan]

On Tuesday, December 19, 2017 at 8:05:34 PM UTC+1, Thomas Leonard wrote:
> I'd like to announce the release of qubes-mirage-firewall 0.4:
> 
>   https://github.com/talex5/qubes-mirage-firewall/releases/tag/v0.4
> 
> This is a unikernel that can run as a QubesOS ProxyVM, replacing 
> sys-firewall. It may be useful if you want something smaller or 
> faster-to-start than the Linux-based sys-firewall, are worried about possible 
> attacks against Linux's C net-front code, or just like playing with 
> unikernels.
> 
> 
> Changes since 0.3:
> 
> - Add support for HVM guests (needed for Qubes 4). I don't use Qubes 4 myself 
> yet, but other people have said it works now for them. Note that the firewall 
> itself must still have virt_mode set to 'pv'.
> 
> - Add support for disposable VMs.
> 
> - Drop frames if an interface's queue gets too long.
> 
> - Show (log) the packet when failing to add a NAT rule. The previous message 
> was just: WRN [firewall] Failed to add NAT rewrite rule: Cannot NAT this 
> packet
> 
> 
> For installation instructions, see:
> 
>   https://github.com/talex5/qubes-mirage-firewall/blob/master/README.md
> 
> For a blog post explaining the background for this, with a walk-through of 
> the code, see:
> 
>   http://roscidus.com/blog/blog/2016/01/01/a-unikernel-firewall-for-qubesos/

Thanks, will probably try it out later this week. :)

-- 
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/c6f593de-3ff0-4aac-adea-5e27f794a6fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: USB Keyboard & Mouse Intermittent v4.0rc3

[Foppe de Haan]

On Monday, December 11, 2017 at 2:19:58 PM UTC+1, Ray Joseph wrote:
> When I execute  "qvm-prefs -s sys-usb pci_strictreset false",
> the system responds with "no such property: 'pci_strictreset' "
> 
> I can query:
> qvm-prefs -g sys-usb
> and get a long list of properties.  'pci_strictreset' is not one of them, but 
> I am guessing it can be added with the set (-s) command.
> 
> Please suggest what I may be doing wrong.
> 
> 
> BTW, the FAQ list the syntax to be:
> qvm-prefs sys-sub -g 
> but this produces the response
> unrecognized arguments: pci_strictreset false
> 
> Actually, the FAQ states the syntax
> qvm-prefs usbVM -s pci_strictreset false
> but this produces the same result as above.

qvm-pci attach --persistent -o no-strict-reset=True sys-usb dom0:00_12.3

-- 
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/f1142aaf-65d6-4f25-9ae6-6bcf5af1b338%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

Thanks, Reg. :)

On the topic of 4.14 in dom0: When I compile stuff in a VM (with 8 or 10 out of 
12 threads assigned), I am sometimes running into cursor and other sluggishness 
in dom0 and (the rendering of) other VMs, when this wasn't ever the case (to my 
recollection) in kernels <=4.12. IIRC I also had this with 4.13. Any idea what 
that might be about, or what logs or resource monitors I might check when this 
next occurs?

-- 
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/9d3296a9-b82b-4479-bce4-8bb72d303864%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Cant set kernel to none

[Foppe de Haan]

On Sunday, December 3, 2017 at 10:46:42 PM UTC+1, eminem wrote:
> Hey, im using qubes 4 RC3
> Im trying to install android on a vm but i cant do it because i need to set 
> the kernel to none. I go to the VM settings and then try to change the 
> kernel, then save it, and when i go again to vm settings kernel is set to 
> default

try qvm-prefs VMNAME kernel ''.

-- 
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/3d95590a-4734-453e-9743-0fd6186200eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Can’t Upgrade to Fedora 25

[Foppe de Haan]

On Sunday, December 3, 2017 at 6:10:37 AM UTC+1, Person wrote:
> When I try to update a Fedora 23 VM in Qubes 3.2, I get this error message:
> 
> https://imgur.com/a/nuKDG

try adding a few gb to the root volume.

-- 
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/74824f67-404b-4e5a-af4b-ed87d3d77346%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Tuesday, November 28, 2017 at 6:41:02 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> > guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
> 
> I confirm your log and the behavior. Few days ago, I tried to look on the xen 
> and kernel list to see if there were something bug we need to dig into the 
> problem...need time...

could also be feature changes, I guess, given that 4.14 received some xen 
'love' as well (to p2m, among other things): https://lkml.org/lkml/2017/9/6/487

-- 
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/e94197a2-ce11-4f25-88c5-4fa5f93cf89d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Tuesday, November 28, 2017 at 6:41:02 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> > guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
> 
> I confirm your log and the behavior. Few days ago, I tried to look on the xen 
> and kernel list to see if there were something bug we need to dig into the 
> problem...need time...

Understood; not trying to rush, of course, just thought to supply a log for a 
change. :p

-- 
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/f4106425-6f6d-463a-8e05-202d0939df85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2: 

-- 
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/1336cccf-318c-4058-91b7-31e9fb22a7df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[0.00] Linux version 4.14.2-1.pvops.qubes.x86_64 (user@kd) (gcc version 
6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Tue Nov 28 17:57:25 CET 2017
[0.00] Command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 
rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 nopat
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'compacted' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x9b3fefff] usable
[0.00] BIOS-e820: [mem 0x9b3ff000-0x9b3f] reserved
[0.00] BIOS-e820: [mem 0xfc00-0x] reserved
[0.00] x86/PAT: PAT support disabled.
[0.00] NX (Execute Disable) protection: active
[0.00] random: fast init done
[0.00] SMBIOS 2.4 present.
[0.00] DMI: Xen HVM domU, BIOS 4.8.2 11/28/2017
[0.00] Hypervisor detected: Xen HVM
[0.00] Xen version 4.8.
[0.00] Netfront and the Xen platform PCI driver have been compiled for 
this kernel: unplug emulated NICs.
[0.00] Blkfront and the Xen platform PCI driver have been compiled for 
this kernel: unplug emulated disks.
[0.00] You might have to change the root device
[0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
[0.00] in your root= kernel command line option
[0.00] tsc: Fast TSC calibration using PIT
[0.00] e820: last_pfn = 0x9b3ff max_arch_pfn = 0x4
[0.00] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC  
[0.00] found SMP MP-table at [mem 0x000f6a40-0x000f6a4f] mapped at 
[ff240a40]
[0.00] Scanning 1 areas for low memory corruption
[0.00] Using GB pages for direct mapping
[0.00] RAMDISK: [mem 0x7fa7a000-0x7fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F6990 24 (v02 Xen   )
[0.00] ACPI: XSDT 0xFC00A7B0 54 (v01 XenHVM  
 HVML )
[0.00] ACPI: FACP 0xFC00A490 F4 (v04 XenHVM  
 HVML )
[0.00] ACPI: DSDT 0xFC001460 008FAC (v02 XenHVM  
 INTL 20160831)
[0.00] ACPI: FACS 0xFC001420 40
[0.00] ACPI: FACS 0xFC001420 40
[0.00] ACPI: APIC 0xFC00A590 B0 (v02 XenHVM  
 HVML )
[0.00] ACPI: HPET 0xFC00A6C0 38 (v01 XenHVM  
 HVML )
[0.00] ACPI: WAET 0xFC00A700 28 (v01 XenHVM  
 HVML )
[0.00] ACPI: SSDT 0xFC00A730 31 (v02 XenHVM  
 INTL 20160831)
[0.00] ACPI: SSDT 0xFC00A770 31 (v02 XenHVM  
 INTL 20160831)
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0x9b3fefff]
[0.00] NODE_DATA(0) allocated [mem 0x9b3ed000-0x9b3fefff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   DMA32[mem 0x0100-0x9b3fefff]
[0.00]   Normal   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0x9b3fefff]
[0.00] Initmem setup node 0 [mem 0x1000-0x9b3fefff]
[0.00] ACPI: PM-Timer IO Port: 0xb008
[0.00] IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-47
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Friday, November 24, 2017 at 6:00:37 PM UTC+1, Foppe de Haan wrote:
> On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret (fepitre) 
> wrote:
> > Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> > > On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret 
> > > (fepitre) wrote:
> > > > Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> > > > > Now that 4.14's reached stable, does anyone plan to test it soon (or 
> > > > > have an idea when they'll have time to do so)? Since 4.13 wasn't 
> > > > > stable 'by default' in qubes, I would assume 4.14 won't be either, 
> > > > > but although I'll certainly give it a go, I'm fairly sure I am not 
> > > > > the best person to try to figure out what's wrong when I run into 
> > > > > trouble. :)
> > > > 
> > > > Ok so I'm trying kernel-4.14.1 since this morning and it seems to be 
> > > > more stable than 4.13. I have not experienced any random crash which 
> > > > normally would have occurred at least once in a day with kernel-4.13. 
> > > > You can try it if you want: 
> > > > https://github.com/fepitre/qubes-linux-kernel/tree/devel-4.14
> > > 
> > > Great. :) Which fedora version did you use to build it, though? When I 
> > > try using 25 or 26, it errors while whining about u2mfn. I've checked the 
> > > thread in the bug tracker, but it doesn't really
> > 
> > I'm using a Fedora 26 (on a Debian server with Xen, not Qubes) with a 
> > DIST_DOM0 as Fedora 23. If you want, I can upload the kernel files on 
> > sourceforge.
> 
> it may have something to do with the fact that 'dkms status u2mfn' doesn't 
> return anything, as that results in 'cp -r /usr/src/u2mfn-$u2mfn_ver 
> /home/user/qubes-linux-kernel/u2mfn' erroring out.

So when it tries to run this script prior to building the kernel: 
https://github.com/QubesOS/qubes-linux-utils/blob/master/kernel-modules/qubes-prepare-vm-kernel
 , it fails, because 'dkms status u2mfn' yields an empty string when run in a 
(fc26) VM.

-- 
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/1d87f219-1e1c-49eb-89d9-bff576604867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Friday, November 24, 2017 at 7:01:37 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le vendredi 24 novembre 2017 18:00:37 UTC+1, Foppe de Haan a écrit :
> > On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret 
> > (fepitre) wrote:
> > > Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> > > > On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret 
> > > > (fepitre) wrote:
> > > > > Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> > > > > > Now that 4.14's reached stable, does anyone plan to test it soon 
> > > > > > (or have an idea when they'll have time to do so)? Since 4.13 
> > > > > > wasn't stable 'by default' in qubes, I would assume 4.14 won't be 
> > > > > > either, but although I'll certainly give it a go, I'm fairly sure I 
> > > > > > am not the best person to try to figure out what's wrong when I run 
> > > > > > into trouble. :)
> > > > > 
> > > > > Ok so I'm trying kernel-4.14.1 since this morning and it seems to be 
> > > > > more stable than 4.13. I have not experienced any random crash which 
> > > > > normally would have occurred at least once in a day with kernel-4.13. 
> > > > > You can try it if you want: 
> > > > > https://github.com/fepitre/qubes-linux-kernel/tree/devel-4.14
> > > > 
> > > > Great. :) Which fedora version did you use to build it, though? When I 
> > > > try using 25 or 26, it errors while whining about u2mfn. I've checked 
> > > > the thread in the bug tracker, but it doesn't really
> > > 
> > > I'm using a Fedora 26 (on a Debian server with Xen, not Qubes) with a 
> > > DIST_DOM0 as Fedora 23. If you want, I can upload the kernel files on 
> > > sourceforge.
> > 
> > it may have something to do with the fact that 'dkms status u2mfn' doesn't 
> > return anything, as that results in 'cp -r /usr/src/u2mfn-$u2mfn_ver 
> > /home/user/qubes-linux-kernel/u2mfn' erroring out.
> 
> Just in case: https://sourceforge.net/projects/qubes-kernel-latest/files/
> 
> You will find fepitre-kernel-latest.repo and frederic-pierret-signing-key.asc 
> (check https://github.com/fepitre/keys). You can download the latest kernel I 
> built.

dom0 kernel boots fine, vm-kernel doesn't. (In r4.0rc2.) -- seeing 'mount: 
mounting /dev/mapper/dmroot on /sysroot failed: Invalid argument', and a kernel 
panic soon after (in /var/log/xen/console/guest-vm.log).

-- 
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/d8f2c62c-89bc-4154-9bf1-45bb1439d2b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> > On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret 
> > (fepitre) wrote:
> > > Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> > > > Now that 4.14's reached stable, does anyone plan to test it soon (or 
> > > > have an idea when they'll have time to do so)? Since 4.13 wasn't stable 
> > > > 'by default' in qubes, I would assume 4.14 won't be either, but 
> > > > although I'll certainly give it a go, I'm fairly sure I am not the best 
> > > > person to try to figure out what's wrong when I run into trouble. :)
> > > 
> > > Ok so I'm trying kernel-4.14.1 since this morning and it seems to be more 
> > > stable than 4.13. I have not experienced any random crash which normally 
> > > would have occurred at least once in a day with kernel-4.13. You can try 
> > > it if you want: 
> > > https://github.com/fepitre/qubes-linux-kernel/tree/devel-4.14
> > 
> > Great. :) Which fedora version did you use to build it, though? When I try 
> > using 25 or 26, it errors while whining about u2mfn. I've checked the 
> > thread in the bug tracker, but it doesn't really
> 
> I'm using a Fedora 26 (on a Debian server with Xen, not Qubes) with a 
> DIST_DOM0 as Fedora 23. If you want, I can upload the kernel files on 
> sourceforge.

it may have something to do with the fact that 'dkms status u2mfn' doesn't 
return anything, as that results in 'cp -r /usr/src/u2mfn-$u2mfn_ver 
/home/user/qubes-linux-kernel/u2mfn' erroring out.

-- 
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/0e39728c-8800-4793-8e76-68b3490aa460%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret (fepitre) 
wrote:
> Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> > Now that 4.14's reached stable, does anyone plan to test it soon (or have 
> > an idea when they'll have time to do so)? Since 4.13 wasn't stable 'by 
> > default' in qubes, I would assume 4.14 won't be either, but although I'll 
> > certainly give it a go, I'm fairly sure I am not the best person to try to 
> > figure out what's wrong when I run into trouble. :)
> 
> Ok so I'm trying kernel-4.14.1 since this morning and it seems to be more 
> stable than 4.13. I have not experienced any random crash which normally 
> would have occurred at least once in a day with kernel-4.13. You can try it 
> if you want: https://github.com/fepitre/qubes-linux-kernel/tree/devel-4.14

Great. :) Which fedora version did you use to build it, though? When I try 
using 25 or 26, it errors while whining about u2mfn. I've checked the thread in 
the bug tracker, but it doesn't really 

-- 
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/d33807e7-ac96-45e8-a59f-f7c92aeaf539%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO: Compiling Kernels for dom0

[Foppe de Haan]

Now that 4.14's reached stable, does anyone plan to test it soon (or have an 
idea when they'll have time to do so)? Since 4.13 wasn't stable 'by default' in 
qubes, I would assume 4.14 won't be either, but although I'll certainly give it 
a go, I'm fairly sure I am not the best person to try to figure out what's 
wrong when I run into trouble. :)

-- 
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/5322447a-5335-472c-8298-a0d2828a5acf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Creating a HVM in Qubes 4.0rc2 for Windows 7 Qube

[Foppe de Haan]

On Tuesday, November 14, 2017 at 11:24:17 PM UTC+1, car...@gmail.com wrote:
> On Monday, November 13, 2017 at 1:53:14 AM UTC-5, Foppe de Haan wrote:
> > On Monday, November 13, 2017 at 6:07:03 AM UTC+1, car...@gmail.com wrote:
> > > I am trying to create a Win7 qube with the latest version(4.0rc2). I 
> > > create the qube with the following command:
> > > 'qvm-create win7 --label green'
> > > and start the qube with the command:
> > > 'qvm-start win7 --cdrom=[qube-name]/home/user/Downloads/[File]'
> > > 
> > > Nothing happens. How do I go about creating a Win7 qube with the latest 
> > > version?
> > you need to specify you want to create a template or standalone VM, by 
> > adding  --class TemplateVM/StandaloneVM while creating the VM.
> > try running "qvm-prefs win7 kernel ''" after doing so, then booting.
> 
> It's now booting. When it get's to the blue Windows 7 install screen, it 
> crashes. Have you gotten past this?

yes, it installed fine for me.

-- 
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/b8246627-643a-43a0-b4a3-16de347d9a18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Creating a HVM in Qubes 4.0rc2 for Windows 7 Qube

[Foppe de Haan]

On Monday, November 13, 2017 at 6:07:03 AM UTC+1, car...@gmail.com wrote:
> I am trying to create a Win7 qube with the latest version(4.0rc2). I create 
> the qube with the following command:
> 'qvm-create win7 --label green'
> and start the qube with the command:
> 'qvm-start win7 --cdrom=[qube-name]/home/user/Downloads/[File]'
> 
> Nothing happens. How do I go about creating a Win7 qube with the latest 
> version?
you need to specify you want to create a template or standalone VM, by adding  
--class TemplateVM/StandaloneVM while creating the VM.
try running "qvm-prefs win7 kernel ''" after doing so, then booting.

-- 
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/38cc749a-5304-4da9-99c4-a50fc1bd8029%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - ASUS PRIME B350M-A + AMD Ryzen 7 1700X

[Foppe de Haan]

On Saturday, November 11, 2017 at 10:25:42 PM UTC+1, Foppe de Haan wrote:
> On Saturday, November 11, 2017 at 8:12:17 PM UTC+1, David Schissler wrote:
> > Does the AMD Ryzen equivalent of VT-d work properly?  It seemed that AMD 
> > setups were quite deficient before and I'm hoping that they will become 
> > first class with Zen and Ryzen.  Lenovo recently a Thinkpad with an older 
> > AMD CPU and I'm guessing that it was a warmup for a Ryzen option by the 
> > middle of next year.
> 
> As far as I'm aware (I have a ryzen 1600 as my main system), it works without 
> problems (helped by the fact that AMD actively worked with Xen to ensure Zen 
> support). There should be additional laptops coming out q1, now that raven 
> ridge is finally done.

Only issue with RR is that vega display stack support is likely only coming 
with 4.15 (assuming Linus gives the green light), which isn't very likely to 
ship with the qubes installer.

-- 
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/5021adf9-46e2-42dd-8cf6-c960cfe97619%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - ASUS PRIME B350M-A + AMD Ryzen 7 1700X

[Foppe de Haan]

On Saturday, November 11, 2017 at 8:12:17 PM UTC+1, David Schissler wrote:
> Does the AMD Ryzen equivalent of VT-d work properly?  It seemed that AMD 
> setups were quite deficient before and I'm hoping that they will become first 
> class with Zen and Ryzen.  Lenovo recently a Thinkpad with an older AMD CPU 
> and I'm guessing that it was a warmup for a Ryzen option by the middle of 
> next year.

As far as I'm aware (I have a ryzen 1600 as my main system), it works without 
problems (helped by the fact that AMD actively worked with Xen to ensure Zen 
support). There should be additional laptops coming out q1, now that raven 
ridge is finally done.

-- 
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/0d5057fb-6730-4dfb-986b-143155509f08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - ASUS PRIME B350M-A + AMD Ryzen 7 1700X

[Foppe de Haan]

On Saturday, November 11, 2017 at 12:37:58 AM UTC+1, qua terniol wrote:
> This week I installed Qubes 4.0-rc2 on my new AMD Ryzen 7 build.
> It complained during configuration after installation, but it seems to work. 
> 
> Firefox in the VMs can access internet. 
> 
> (This did not work on an AMD Athlon X4 640 or a Intel Core i7 3632QM).
> 
> 
> Maybe it complained about interrupt remapping (I was not paying attention).
> 
> 
> 
> The attached .yml file contains:
> remap:
>   'no'
> 
> 
> 
> But 'xl dmesg' in a Dom0 terminal shows:
> (XEN)  Interrupt remapping enabled

yeah that's a cosmetic/detection issue. It's supported.

-- 
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/024e9ce6-6edf-4ca6-8158-cb5891ab9fa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Foppe de Haan]

On Tuesday, October 31, 2017 at 1:56:46 PM UTC+1, Roy Bernat wrote:
> On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat  wrote:
> > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799]  wrote:
> > > Hello,
> > > 
> > > As at least one other Qubes user has the same problem, that VMs won't 
> > > start, I'll add this as special topic.
> > > 
> > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't 
> > > boot the VMs.
> > > This includes sys-net, sys-firewall, but also others.
> > > 
> > > I tried to check the logs but I don't get any valuable information.
> > > See screenshot.
> > > 
> > > I started the following command in dom0:
> > > 
> > > watch -n 1 xl list
> > > 
> > > When I try to launch a VM I can see that the VMs appears in the xl list 
> > > output, but the State is -- and the Time(s) is 0.0.
> > > After ~30sec the start is aborted with error message: Cannot execute 
> > > qrexec-daemon.
> > > 
> > > Questions:
> > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > > 2) is someone additionaly running Coreboot?
> > > 3) I am running the Qubes Installation with the default settings, any 
> > > options to tweak on the Grub command line
> > > 
> > > [799]
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Gesendet von ProtonMail mobile
> > 
> > not worked for me . 
> > 
> > until now i dont know what cause this issue ? 
> > 
> > this is a huge bug the cause us not to work .  for me 3.2 dont work so i 
> > have only one option .  By the way rc01 worked ok 
> 
> It seems that asomething with the sys-net causing the sys-firewall not 
> working 

try changing the sys-net template to debian?

-- 
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/83a385b5-bd13-4ea7-8054-736e5887da22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: really no support

[Foppe de Haan]

On Monday, October 30, 2017 at 9:43:53 PM UTC+1, Outback Dingo wrote:
> seriously still seems there is very little support ive sent multiple
> emails to the list and received no response, so let me ask again ?
> 
> how do i enlarge a vm file system with 4.0RC2
> basically my personal vm is out of space..

why not use the GUI? Every VM's menu has an entry called 'VM settings' (can 
also be called via terminal -> qubes-vm-settings VMNAME), from which you can 
increase the size of the private image.

-- 
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/291529e1-9785-4620-9b18-aee0734cc584%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Nouveau driver does not work during installation of 4.0rc2

[Foppe de Haan]

On Sunday, October 29, 2017 at 3:44:45 PM UTC+1, Mike Keehan wrote:
> Hi,
> 
> Installing 4.0rc2 fails after approx 600-700 packages.  I found
> that one of the cpus was getting "stuck after 22secs" - the reason
> seems to be that the nouveau driver does not work with the version
> of the nvidia chips on my laptop (even the git kernel does not work
> with it yet).
> 
> The same problem occurs when trying to install Fedora 26.
> 
> So I need to add "modprobe.blacklist=nouveau" to the kernel command
> line when booting the installer.  This allows Fedora to install.
> But I can't figure out a way to do that in the Qubes installer.
> Anyone have an idea?
> 
> I tried using the grub command line, but the commands available do
> not match up with the grub manual online - I'm presuming this is a 
> security measure.
> 
> Mike.

You should be able to press e and edit the kernel parameters while the xen 
choice menu is up?

-- 
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/e02b858c-9de0-4a42-be33-fa3fcd24c57d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 3.2 questions and issues.....

[Foppe de Haan]

On Sunday, October 29, 2017 at 7:46:41 PM UTC+1, Graham wrote:
> Hi
> I've not tried 4.0 yet, but I have been running 3.2 for a few weeks on my 
> main production laptop, a thinkpad t440p. And qubes has been working better 
> than I expected, but its a big learning curve going from windows to qubes, 
> with only basic linux skills.
> 
> I'm going to try 4.0 on a separate ssd, once I obtain one. But at the moment 
> I'm still playing around with 3.2.
> 
> During installation I selected luks encryption, which works fine. But my ssd 
> is encrypted using the bios, so perhaps not using luks would give me better 
> battery life, and cpu performance?
> 
> I did have trouble shutting qubes down. And, I found the best practice was to 
> shutdown all vms and system vms, first. That way I'm guaranteed a quick and 
> easy shutdown, without any issues.
> 
> The power manager on the taskbar occasionally crashes when being used, and I 
> have to go to 'system tools' and restart it. 
> 
> I upgraded debian-8 to debian-9, and deleted the dedian-8 template from qubes 
> manager but 'template: debian-8' still remains in the dom0 app menu. I've 
> tried various cli commands to remove it but nothing works.
> 
> I'm confused how to install unsigned packages, and what the best practice is.
> 
> Should I install the package inside a new and clean templatevm, then create 
> an appvm from that template? Or create a standalonevm from a clean template 
> and install package inside the appvm? 
> 
> Also, the qubes instructions says fedora minimal uses 300mb disk space, but 
> mine is currently using 1500mb. Which seems like a lot.
> 
> I've probably got more questions and issues. But so far Qubes is a great!

r3.2 has a few issues with shortcut removal; if you're bored, you can remove 
the entries manually from submenus in (iirc) .local, .gnome and shared. 
Otherwise, just ignore them, and go by what the qubes-manager (or qvm-ls) tells 
you is installed. :)

As to templates, it doesn't matter so long as you are working with AppVMs 
(Standalone is a different story, for obvious reasons). Just reboot the appvm 
after shutting down the template, and you're good to go.

1200mb for fedora-minimal is about as low as it goes, you can run 
qvm-trim-template every once in a while to shrink the image.

-- 
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/5e93ef10-1920-4317-b63f-06485f56fb49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: 4.RC2 CANT create / install VM from local iso

[Foppe de Haan]

On Saturday, October 28, 2017 at 11:27:36 AM UTC+2, Foppe de Haan wrote:
> On Saturday, October 28, 2017 at 9:49:19 AM UTC+2, Roy Bernat wrote:
> > On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
> > > So we need updated docs or somethings broken...
> > > 
> > > i copied the iso to /home/user from the AppVM tried to create an hvm
> > > appvm got a unrecognized argument... ok
> > > then tried without --hvm... seems ok however. qvm-start
> > > results in a traceback
> > > 
> > > [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
> > > usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
> > >   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
> > >   [-P POOL_NAME] [--template VALUE] [--label VALUE]
> > >   [--help-classes]
> > >   [--root-copy-from FILENAME | --root-move-from FILENAME]
> > >   [VMNAME]
> > > qvm-create: error: unrecognized arguments: --hvm
> > > [dingo@dom0 ~]$ qvm-create BSD  --label blue
> > > sudo qvm-start BSD 
> > > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > > Traceback (most recent call last):
> > >   File "/bin/qvm-start", line 9, in 
> > > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> > > 'qvm-start')()
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 160, in main
> > > drive_assignment = get_drive_assignment(args.app, args.drive)
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 98, in get_drive_assignment
> > > backend_domain_name, ident = drive_str.split(':', 1)
> > > ValueError: not enough values to unpack (expected 2, got 1)
> > > [dingo@dom0 ~]$ qvm-start BSD
> > > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > > Traceback (most recent call last):
> > >   File "/usr/bin/qvm-start", line 9, in 
> > > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> > > 'qvm-start')()
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 160, in main
> > > drive_assignment = get_drive_assignment(args.app, args.drive)
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 98, in get_drive_assignment
> > > backend_domain_name, ident = drive_str.split(':', 1)
> > > ValueError: not enough values to unpack (expected 2, got 1)
> > > [dingo@dom0 ~]$ qvm-start BSD
> > > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > > Traceback (most recent call last):
> > >   File "/usr/bin/qvm-start", line 9, in 
> > > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> > > 'qvm-start')()
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 160, in main
> > > drive_assignment = get_drive_assignment(args.app, args.drive)
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 98, in get_drive_assignment
> > > backend_domain_name, ident = drive_str.split(':', 1)
> > > ValueError: not enough values to unpack (expected 2, got 1)
> > > 
> > > [user@personal dom0]$
> > 
> > You dont need to use --hvm . it is the default in version 4. 
> > Regarding the cdrom i have also the same issue it seems that this switch 
> > has beed deprecated .
> > 
> > 
> > Roy
> 
> try qubes-vm-boot-from-device or qvm-start VMNAME --cdrom=VMNAME:/path ; or 
> use the interface from the second page of the VM settings GUI.

(Btw, if you type qvm-, or qubes-, bash spits out a list of 
commands starting with those characters; you can usually find the command you 
are looking for that way; beyond that, --help or 'man qvm-command' will also 
provide hints as to available switches, except in the case of qvm-pci 
currently.)

-- 
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/3174c27d-c46d-4326-917b-6ce7aa78768f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: 4.RC2 CANT create / install VM from local iso

[Foppe de Haan]

On Saturday, October 28, 2017 at 9:49:19 AM UTC+2, Roy Bernat wrote:
> On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
> > So we need updated docs or somethings broken...
> > 
> > i copied the iso to /home/user from the AppVM tried to create an hvm
> > appvm got a unrecognized argument... ok
> > then tried without --hvm... seems ok however. qvm-start
> > results in a traceback
> > 
> > [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
> > usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
> >   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
> >   [-P POOL_NAME] [--template VALUE] [--label VALUE]
> >   [--help-classes]
> >   [--root-copy-from FILENAME | --root-move-from FILENAME]
> >   [VMNAME]
> > qvm-create: error: unrecognized arguments: --hvm
> > [dingo@dom0 ~]$ qvm-create BSD  --label blue
> > sudo qvm-start BSD --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > Traceback (most recent call last):
> >   File "/bin/qvm-start", line 9, in 
> > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 160, in main
> > drive_assignment = get_drive_assignment(args.app, args.drive)
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 98, in get_drive_assignment
> > backend_domain_name, ident = drive_str.split(':', 1)
> > ValueError: not enough values to unpack (expected 2, got 1)
> > [dingo@dom0 ~]$ qvm-start BSD
> > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > Traceback (most recent call last):
> >   File "/usr/bin/qvm-start", line 9, in 
> > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 160, in main
> > drive_assignment = get_drive_assignment(args.app, args.drive)
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 98, in get_drive_assignment
> > backend_domain_name, ident = drive_str.split(':', 1)
> > ValueError: not enough values to unpack (expected 2, got 1)
> > [dingo@dom0 ~]$ qvm-start BSD
> > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > Traceback (most recent call last):
> >   File "/usr/bin/qvm-start", line 9, in 
> > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 160, in main
> > drive_assignment = get_drive_assignment(args.app, args.drive)
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 98, in get_drive_assignment
> > backend_domain_name, ident = drive_str.split(':', 1)
> > ValueError: not enough values to unpack (expected 2, got 1)
> > 
> > [user@personal dom0]$
> 
> You dont need to use --hvm . it is the default in version 4. 
> Regarding the cdrom i have also the same issue it seems that this switch has 
> beed deprecated .
> 
> 
> Roy

try qubes-vm-boot-from-device or qvm-start VMNAME --cdrom=VMNAME:/path ; or use 
the interface from the second page of the VM settings GUI.

-- 
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/7a2da4e4-ee69-4de3-80fc-182b65a07614%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: attaching to VM consoles for debugging purposes

[Foppe de Haan]

you can try 'qvm-start-gui --all' first, to see if that helps; otherwise, your 
best bet is 'sudo xl console -t pv VMNAME'

-- 
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/2e80f269-74d6-4864-a07e-c0b2ca56f185%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL Asrock AB350 Pro4 + Ryzen 5 1600 (Qubes R4)

[Foppe de Haan]

On Friday, October 27, 2017 at 8:24:16 AM UTC+2, Foppe de Haan wrote:
> On Friday, October 27, 2017 at 12:34:11 AM UTC+2, tjc.co...@gmail.com wrote:
> > On Friday, October 27, 2017 at 12:24:45 AM UTC+2, tjc.co...@gmail.com wrote:
> > > On Thursday, October 26, 2017 at 11:53:16 PM UTC+2, Foppe de Haan wrote:
> > > > mbt IR foutmelding: dat boeit niet, is een 'foutje', als het goed is 
> > > > binnenkort opgelost. :)
> > > > 
> > > > wat aan moet staan is IOMMU, SVM en SRIOV, de rest mag je op de 
> > > > standaardwaarden laten.
> > > 
> > > Oke,
> > > 
> > > Is nu bezig met config van Templates (meerdere)
> > > 
> > > Dank.
> > 
> > Is klaar en het werkt. Nu leren hoe het werkt.
> > 
> > Bedankt Foppe.
> 
> mooi, graag gedaan en succes. :)

Als je een kernel wilt compilen die de rx550 zou moeten ondersteunen is hier 
een handleiding; kies voor 4.12.14 (4.13 is momenteel nog instabiel ivm 
onbekend probleem): 
https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md

-- 
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/0e59e9bc-c689-4a00-bb03-dc2f0cc4efcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL Asrock AB350 Pro4 + Ryzen 5 1600 (Qubes R4)

[Foppe de Haan]

On Friday, October 27, 2017 at 12:34:11 AM UTC+2, tjc.co...@gmail.com wrote:
> On Friday, October 27, 2017 at 12:24:45 AM UTC+2, tjc.co...@gmail.com wrote:
> > On Thursday, October 26, 2017 at 11:53:16 PM UTC+2, Foppe de Haan wrote:
> > > mbt IR foutmelding: dat boeit niet, is een 'foutje', als het goed is 
> > > binnenkort opgelost. :)
> > > 
> > > wat aan moet staan is IOMMU, SVM en SRIOV, de rest mag je op de 
> > > standaardwaarden laten.
> > 
> > Oke,
> > 
> > Is nu bezig met config van Templates (meerdere)
> > 
> > Dank.
> 
> Is klaar en het werkt. Nu leren hoe het werkt.
> 
> Bedankt Foppe.

mooi, graag gedaan en succes. :)

-- 
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/4d3e2815-40f4-4fcb-a074-8e2e9e6bb0f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.