Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-09 Thread reggelo

>
> I've got the same exact setup and same issues with suspend/resume :(
>
> Haven't found any solution so far, have you?
>

I have tried with 4.1 (Build4.1-20200131) 
 but the result is the same: 
suspend/resume not working :(
With Debian (Bullseye) works! But after i install the xen, same suspend 
issue appear again...
Related lines from dmesg:
'
[4.957422] kfd kfd: Allocated 3969056 bytes on gart
[4.957512] kfd kfd: error getting iommu info. is the iommu enabled?
[4.957514] kfd kfd: Error initializing iommuv2
[4.961211] kfd kfd: device 1002:15d8 NOT added due to errors
'
@Michael Andersson: Could you please tell us which configuration works to 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c8e237d5-084d-45af-9749-5bb3a55d7132%40googlegroups.com.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-07 Thread reggelo


>  
> I've got the same exact setup and same issues with suspend/resume :(
>
> Haven't found any solution so far, have you?
>

Not yet, but i think the key is the xen upgrade. Could somebody tell me how 
can i upgrade it?

-- 
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/c6894571-19c6-439d-bf22-a1a76d364a79%40googlegroups.com.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-06 Thread zachm1996
On Tuesday, February 4, 2020 at 4:01:46 AM UTC-6, reg...@gmail.com wrote:
>
> > Do you have a link or could you please write me few lines about the T495 
> installation description?
> Meanwhile i have found the solution how can i install, maybe could helps 
> if somebody stuck like me...
>
> Firstly i try with the 'legacy boot', but the GUI could not worked 
> (probably because of the new VGA). The text installer could not worked too, 
> because of the autopart problem with encrypted volume.
> But with EFI the installation worked! Only few problem appeared:
> - sys-net (and sys-firewall) could not started because of a network 
> interface (bus 03:maybe the IPMI?!?), but when i removed, sys-net (and 
> sys-firewall) started without problem.
> - Could not adjust the backlight
> - After the system went to suspend state, can not come back. It shows only 
> blank screen
> - When the system reboot or shutdown the watchdog delays the process 
> (~0.5-2 min!), because it is not stop.
>
> The first two problem solved by kernel upgrade (5.4.10), but the second 
> two still exists...
> ---
> Lenovo T495 Version: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx
>
>  
I've got the same exact setup and same issues with suspend/resume :(

Haven't found any solution so far, have 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/57cfa7ba-7ee7-4e6c-bd65-3e6d3a62c551%40googlegroups.com.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-04 Thread reggelo
> Do you have a link or could you please write me few lines about the T495 
installation description?
Meanwhile i have found the solution how can i install, maybe could helps if 
somebody stuck like me...

Firstly i try with the 'legacy boot', but the GUI could not worked 
(probably because of the new VGA). The text installer could not worked too, 
because of the autopart problem with encrypted volume.
But with EFI the installation worked! Only few problem appeared:
- sys-net (and sys-firewall) could not started because of a network 
interface (bus 03:maybe the IPMI?!?), but when i removed, sys-net (and 
sys-firewall) started without problem.
- Could not adjust the backlight
- After the system went to suspend state, can not come back. It shows only 
blank screen
- When the system reboot or shutdown the watchdog delays the process 
(~0.5-2 min!), because it is not stop.

The first two problem solved by kernel upgrade (5.4.10), but the second two 
still exists...
---
Lenovo T495 Version: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx

-- 
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/e51fbd45-48ac-43dc-b623-da36d946cbaf%40googlegroups.com.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-04 Thread reggelo

> Do you have a link or could you please write me few lines about the T495 
installation description?
Meanwhile i have found the solution how can i install, maybe could helps if 
somebody stuck like me...

Firstly i try with the 'legacy boot', but the GUI could not worked 
(probably because of the new VGA). The text installer could not worked too, 
because of the autopart problem with encrypted volume.
But with EFI the installation worked! Only few problem appeared:
- sys-net (and sys-firewall) could not started because of a network 
interface (bus 03:maybe the IPMI?!?), but when i removed, sys-net (and 
sys-firewall) started without problem.
- Could not adjust the backlight
- After the system went to suspend state, can not come back. It shows only 
blank screen
- When the system reboot or shutdown the watchdog delays the process 
(~0.5-2 min!), because it is not stop.

The first two problem solved by kernel upgrade (5.4.10), but the second two 
still exists...
---
Lenovo T495 Firstly i try with the 'legacy boot', but the GUI could not 
worked (probably because of the new VGA). The text installer could not 
worked too, because of the autopart problem with encrypted volume.
But with EFI the installation worked! Only few problem appeared:
- sys-net (and sys-firewall) could not started because of a network 
interface (bus 03:maybe the IPMI?!?), but when i removed, sys-net (and 
sys-firewall) started without problem.
- Could not adjust the backlight
- After the system went to suspend state, can not come back. It shows only 
blank screen
- When the system reboot or shutdown the watchdog delays the process 
(~0.5-2 min!), because it is not stop.

The first two problem solved by kernel upgrade (5.4.10), but the second two 
still exists...

Firstly i try with the 'legacy boot', but the GUI could not worked 
(probably because of the new VGA). The text installer could not worked too, 
because of the autopart problem with encrypted volume.
But with EFI the installation worked! Only few problem appeared:
- sys-net (and sys-firewall) could not started because of a network 
interface (bus 03:maybe the IPMI?!?), but when i removed, sys-net (and 
sys-firewall) started without problem.
- Could not adjust the backlight
- After the system went to suspend state, can not come back. It shows only 
blank screen
- When the system reboot or shutdown the watchdog delays the process 
(~0.5-2 min!), because it is not stop.

The first two problem solved by kernel upgrade (5.4.10), but the second two 
still exists...
---
Lenovo T495 Version: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx

-- 
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/ecf70d9a-d568-4c6b-9870-15b6651cab19%40googlegroups.com.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-03 Thread reggelo


2020. február 3., hétfő 16:52:16 UTC időpontban Anac a következőt írta:
>
>
> On 2/3/20 8:31 PM, unman wrote: 
> > On Mon, Feb 03, 2020 at 05:13:55AM -0800, reg...@gmail.com  
> wrote: 
> > The convention here is not to top-post. 
>
 

> Yes. And please, reggelo, remove the text areas that you are not 
> referring to. This can save a lot of people a lot of time. 
>

Thanks for the info! I will keep that in mind!
If somebody else could help with this too, please don't be shy! ;)

-- 
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/41f27a0a-bf90-4f75-9ab6-ee0dcc631601%40googlegroups.com.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-03 Thread Anac



On 2/3/20 8:31 PM, unman wrote:
> On Mon, Feb 03, 2020 at 05:13:55AM -0800, regg...@gmail.com wrote:
>> [a lot of text, quotes and blah]
> Hi
> The convention here is not to top-post.
> Please scroll to the bottom of the message before you start typing. Or
> reply inline.
> It only takes you seconds, and makes it much easier to follow threads.
> Thanks.
> unman
>
Yes. And please, reggelo, remove the text areas that you are not
referring to. This can save a lot of people a lot of time.

-- 
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/bc385441-6d9d-ade9-e56d-9c2e1fb397ba%40rbox.co.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-03 Thread unman
On Mon, Feb 03, 2020 at 05:13:55AM -0800, regg...@gmail.com wrote:
> Hi Michael!
> 
> Do you have a link or could you please write me few lines about the T495 
> installation description?
> I have stuck in the encryption settings after the GUI installer did not 
> started.
> 
> Thanks in advance!
> 
> 2019. november 17., vas??rnap 8:37:06 UTC id??pontban Michael Andersson a 
> k??vetkez??t ??rta:
> >
> > Yes we are running qubes R4.0.1-RC2 on  thinkpad T495 with AMD Ryzen pro 
> > Needs ???R4.1-testing kernel and xen but otherwise works flawless 
> >
> > L??hetetty Jolla Sailfish -??lypuhelimestani. 
> >   Alkuper??inen viesti   
> > L??hett??j??: rec wins 
> > L??hetetty: lauantaina 16. marraskuuta 2019 23.51 
> > Pttymisaika: qubes...@googlegroups.com  
> > Aihe: [qubes-users] Re: 2 new Intel vulnerabilites 
> >
> > On 11/14/19 2:55 AM, Chris Laprise wrote: 
> > > On 11/14/19 7:28 AM, Andrew David Wong wrote: 
> > >> -BEGIN PGP SIGNED MESSAGE- 
> > >> Hash: SHA512 
> > >> 
> > >> On 2019-11-13 12:40 PM, Lorenzo Lamas wrote: 
> > >>> There are 2 new vulnerabilities in Intel CPU's, also affecting Xen. 
> > >>> Xen has issued XSA-304(CVE-2018-12207) and XSA 305(CVE-2019-11135). 
> > >>> Is the Qubes team aware yet? I haven't seen a new QSB. 
> > >>> 
> > >> 
> > >> Yes, we're aware. We're currently in the process of preparing 
> > >> announcements about these XSAs. 
> > >> 
> > >> Typically, XSAs have a predisclosure period, during which the XSA is 
> > >> embargoed, and the Qubes Security Team has time to analyze it and 
> > >> prepare patches and an announcement. However, these XSAs had no 
> > >> embargo period, so the Qubes Security Team had no advance notice of 
> > >> them before they were publicly announced. 
> > > 
> > > The researchers behind these MDS vuln disclosures were being strung 
> > > along by Intel, who kept changing embargo dates. Eventually they decided 
> > > to simply publish because the proposed patches from Intel were not 
> > > addressing a large number of possible attacks. 
> > > 
> > > I have summary, links and some advice here: 
> > > 
> > https://groups.google.com/d/msgid/qubes-users/85c426f7-7e17-b1ab-87c3-71f92d169955%40posteo.net
> >  
> > > 
> > > 
> > > In short, Intel have played a monopolist's game and delivered products 
> > > that match; Its much better (and simpler) for people to move to AMD at 
> > > least for the time being. It would help if the Qubes community had some 
> > > clear AMD choices. 
> > > 
> >
> > so, are there people running Q4.x on AMD machines? if so which ones? 
> >
> >

Hi
The convention here is not to top-post.
Please scroll to the bottom of the message before you start typing. Or
reply inline.
It only takes you seconds, and makes it much easier to follow threads.
Thanks.
unman

-- 
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/20200203133102.GB8789%40thirdeyesecurity.org.


Re: VS: [qubes-users] Re: 2 new Intel vulnerabilites

2020-02-03 Thread reggelo
Hi Michael!

Do you have a link or could you please write me few lines about the T495 
installation description?
I have stuck in the encryption settings after the GUI installer did not 
started.

Thanks in advance!

2019. november 17., vasárnap 8:37:06 UTC időpontban Michael Andersson a 
következőt írta:
>
> Yes we are running qubes R4.0.1-RC2 on  thinkpad T495 with AMD Ryzen pro 
> Needs ‎R4.1-testing kernel and xen but otherwise works flawless 
>
> Lähetetty Jolla Sailfish -älypuhelimestani. 
>   Alkuperäinen viesti   
> Lähettäjä: rec wins 
> Lähetetty: lauantaina 16. marraskuuta 2019 23.51 
> Päättymisaika: qubes...@googlegroups.com  
> Aihe: [qubes-users] Re: 2 new Intel vulnerabilites 
>
> On 11/14/19 2:55 AM, Chris Laprise wrote: 
> > On 11/14/19 7:28 AM, Andrew David Wong wrote: 
> >> -BEGIN PGP SIGNED MESSAGE- 
> >> Hash: SHA512 
> >> 
> >> On 2019-11-13 12:40 PM, Lorenzo Lamas wrote: 
> >>> There are 2 new vulnerabilities in Intel CPU's, also affecting Xen. 
> >>> Xen has issued XSA-304(CVE-2018-12207) and XSA 305(CVE-2019-11135). 
> >>> Is the Qubes team aware yet? I haven't seen a new QSB. 
> >>> 
> >> 
> >> Yes, we're aware. We're currently in the process of preparing 
> >> announcements about these XSAs. 
> >> 
> >> Typically, XSAs have a predisclosure period, during which the XSA is 
> >> embargoed, and the Qubes Security Team has time to analyze it and 
> >> prepare patches and an announcement. However, these XSAs had no 
> >> embargo period, so the Qubes Security Team had no advance notice of 
> >> them before they were publicly announced. 
> > 
> > The researchers behind these MDS vuln disclosures were being strung 
> > along by Intel, who kept changing embargo dates. Eventually they decided 
> > to simply publish because the proposed patches from Intel were not 
> > addressing a large number of possible attacks. 
> > 
> > I have summary, links and some advice here: 
> > 
> https://groups.google.com/d/msgid/qubes-users/85c426f7-7e17-b1ab-87c3-71f92d169955%40posteo.net
>  
> > 
> > 
> > In short, Intel have played a monopolist's game and delivered products 
> > that match; Its much better (and simpler) for people to move to AMD at 
> > least for the time being. It would help if the Qubes community had some 
> > clear AMD choices. 
> > 
>
> so, are there people running Q4.x on AMD machines? if so which ones? 
>
>
> -- 
> 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...@googlegroups.com . 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/e15049ac-149f-a053-9bd5-3dbaa323931c%40riseup.net.
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b9ae39e6-5131-4a44-87e8-d8ef95e8929e%40googlegroups.com.


VS: [qubes-users] Re: 2 new Intel vulnerabilites

2019-11-17 Thread Michael Andersson
Yes we are running qubes R4.0.1-RC2 on  thinkpad T495 with AMD Ryzen pro
Needs ‎R4.1-testing kernel and xen but otherwise works flawless

Lähetetty Jolla Sailfish -älypuhelimestani.
  Alkuperäinen viesti  
Lähettäjä: rec wins
Lähetetty: lauantaina 16. marraskuuta 2019 23.51
Päättymisaika: qubes-users@googlegroups.com
Aihe: [qubes-users] Re: 2 new Intel vulnerabilites

On 11/14/19 2:55 AM, Chris Laprise wrote:
> On 11/14/19 7:28 AM, Andrew David Wong wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> On 2019-11-13 12:40 PM, Lorenzo Lamas wrote:
>>> There are 2 new vulnerabilities in Intel CPU's, also affecting Xen.
>>> Xen has issued XSA-304(CVE-2018-12207) and XSA 305(CVE-2019-11135).
>>> Is the Qubes team aware yet? I haven't seen a new QSB.
>>>
>>
>> Yes, we're aware. We're currently in the process of preparing
>> announcements about these XSAs.
>>
>> Typically, XSAs have a predisclosure period, during which the XSA is
>> embargoed, and the Qubes Security Team has time to analyze it and
>> prepare patches and an announcement. However, these XSAs had no
>> embargo period, so the Qubes Security Team had no advance notice of
>> them before they were publicly announced.
> 
> The researchers behind these MDS vuln disclosures were being strung
> along by Intel, who kept changing embargo dates. Eventually they decided
> to simply publish because the proposed patches from Intel were not
> addressing a large number of possible attacks.
> 
> I have summary, links and some advice here:
> https://groups.google.com/d/msgid/qubes-users/85c426f7-7e17-b1ab-87c3-71f92d169955%40posteo.net
> 
> 
> In short, Intel have played a monopolist's game and delivered products
> that match; Its much better (and simpler) for people to move to AMD at
> least for the time being. It would help if the Qubes community had some
> clear AMD choices.
> 

so, are there people running Q4.x on AMD machines? if so which ones?


-- 
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/e15049ac-149f-a053-9bd5-3dbaa323931c%40riseup.net.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191117083659.4644947.20989.14017%40gmail.com.


[qubes-users] Re: 2 new Intel vulnerabilites

2019-11-16 Thread rec wins
On 11/14/19 2:55 AM, Chris Laprise wrote:
> On 11/14/19 7:28 AM, Andrew David Wong wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> On 2019-11-13 12:40 PM, Lorenzo Lamas wrote:
>>> There are 2 new vulnerabilities in Intel CPU's, also affecting Xen.
>>> Xen has issued XSA-304(CVE-2018-12207) and XSA 305(CVE-2019-11135).
>>> Is the Qubes team aware yet? I haven't seen a new QSB.
>>>
>>
>> Yes, we're aware. We're currently in the process of preparing
>> announcements about these XSAs.
>>
>> Typically, XSAs have a predisclosure period, during which the XSA is
>> embargoed, and the Qubes Security Team has time to analyze it and
>> prepare patches and an announcement. However, these XSAs had no
>> embargo period, so the Qubes Security Team had no advance notice of
>> them before they were publicly announced.
> 
> The researchers behind these MDS vuln disclosures were being strung
> along by Intel, who kept changing embargo dates. Eventually they decided
> to simply publish because the proposed patches from Intel were not
> addressing a large number of possible attacks.
> 
> I have summary, links and some advice here:
> https://groups.google.com/d/msgid/qubes-users/85c426f7-7e17-b1ab-87c3-71f92d169955%40posteo.net
> 
> 
> In short, Intel have played a monopolist's game and delivered products
> that match; Its much better (and simpler) for people to move to AMD at
> least for the time being. It would help if the Qubes community had some
> clear AMD choices.
> 

so, are there people running Q4.x  on AMD machines?  if so which ones?


-- 
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/e15049ac-149f-a053-9bd5-3dbaa323931c%40riseup.net.