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

[CooSee]

On Saturday, April 13, 2019 at 12:15:18 PM UTC+2, qubes123 wrote:
> For the Qubes R4.1 KDE compilation issue: you can kill the relevant KDE 
> testing process, when the build reaches to that point with eg. htop.  Then 
> the builder will continue and eventually will provide an iso.  
> 
> On the artifacts: I have an AMD APU with an older dGPU (HD-7000 series) and 
> since Qubes kernel 4.19.x the radeon (amdgpu) module have some issues with 
> swiotlb buffer overflow (Xen-4.8).  Newer kernel versions improved (at least 
> xserver now can start with the APU drivers), but I still see some errors even 
> in the latest 5.x versions.  I see no artifacts under xfce, however when I 
> switch to KDE (to achieve GPU offloading), sometimes I have horizontal lines 
> in the background windows, looking really messy
> 
> I plan to do more testing with fc29-dom0 and Xen-4.12 and we'll see if 
> there's already improvement

i assume this has something to do with 'mesa-libwayland-egl' in combination 
with 'amdgpu' + xen + fc25 and newer kernels.

> https://bugzilla.redhat.com/show_bug.cgi?id=1648475
>
> Olivier Fourdan:
>*But* AFAICS, `glamor_get_pixmap_texture()` is used by Xwayland *only* with 
>EGLStream in `xwl_glamor_eglstream_post_damage()`
>

removing the mesa-libwayland-egl package didn't work - dnf then remove 
Xorg+Xfce4 etc.

weird package manager - how you can deal with this - dnf is awful just awful, 
imo!


Qubes R4.1 KDE compilation - i'll try get at least an ISO - is this even 
possible atm ?

i think one of important packages is not available, therefore no 4.1 ISO for 
non-developers.

can you maybe provide one?

i'll even install an Alpha Version of 4.1 to get the best of my new RX590  :-)

greetings


-- 
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/cea8fafe-f33f-404c-a369-f1765d1999f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Spontaneous rebooting

[Michael Siepmann]

 

On 4/13/19 12:28 PM, Chris wrote:
> Hello Michael,
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, April 12, 2019 3:24 PM, Michael Siepmann
>  wrote:
>
>> On 8/10/18 12:37 PM, Kelly Dean wrote:
>>
>>> Am I the only one having a problem with Qubes spontaneously rebooting on 
>>> Intel hardware? Only other reports I see are about AMD problems, but I'm 
>>> using an Intel Core i3.
>>>
>>> Happens every few weeks. Sometimes just 1 or 2 weeks, sometimes 5 or 6. Got 
>>> it on Qubes 3.2, and now 4.0 too (new installation, not upgrade), multiple 
>>> times.
>>>
>>> Unlikely to be a hardware problem. The system passed both memtest86 and a 
>>> multi-day mersenne prime stress test. And other OSes tested on this 
>>> hardware before I switched to Qubes, including Debian and Windows, never 
>>> had a problem.
>>>
>>> The rebooting seems completely random. No apparent trigger, and no warning. 
>>> Acts like an instant hard reset. Sometimes even when the system is idle, 
>>> and I haven't touched the console for hours.
>>>
>>> It's wearingly inevitable enough that I don't even bother intentionally 
>>> rebooting after system updates anymore, in order to minimize how many 
>>> reboots I have to deal with (setting my workspace back up is an ordeal), 
>>> because I know the system will end up spontaneously rebooting a week or two 
>>> later anyway.
>>>
>> I'm having this problem too. I hadn't had it for a while but in the
>> past week or so it's happened a few times. I have a Lenovo ThinkPad
>> T440p with Intel Core i7, and Qubes 4.0 which I keep updated.
>>
>
> I had this problem which was due to Intel AMT Control being enabled in
> the BIOS. Since turning this off my system has not rebooted.
>
> Regards,
>
> Chris
>
> -
> Chris Willard
> ch...@meliser.co.uk 


Thanks for the suggestion, Chris. I appreciate it. I checked and Intel
AMT was already disabled so I guess something else must be causing it in
my case.


-- 
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/c95ae02f-9981-3306-82c5-c7f83b13329e%40TechDesignPsych.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Spontaneous rebooting

[David Hobach]

On 4/13/19 8:29 PM, brendan.h...@gmail.com wrote:

There are some discussions in qubes-issues on github about torbrowser causing 
100% cpu while idle, yet appearing to mostly work ok. Running a couple VMs with 
that bug might cause an overheat reboot on some systems...


No Intel AMT (coreboot), no overheating (~50-60 degrees when idle), no 
torbrowser here... But thanks for the hints anyway, maybe it'll help 
someone!


I was referring to [1] earlier on. I didn't observe any log entries though.

I'll keep you posted if I ever find the root cause.

[1] https://github.com/QubesOS/qubes-issues/issues/3079

--
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/62109593-6b21-f372-5487-644e568329a9%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qubes-users] Spontaneous rebooting

[brendan . hoar]

There are some discussions in qubes-issues on github about torbrowser causing 
100% cpu while idle, yet appearing to mostly work ok. Running a couple VMs with 
that bug might cause an overheat reboot on some systems...

-- 
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/34a1d631-6511-4f3f-baa9-259e0b77a0f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Spontaneous rebooting

[Chris]

Hello Michael,

‐‐‐ Original Message ‐‐‐
On Friday, April 12, 2019 3:24 PM, Michael Siepmann  
wrote:

> On 8/10/18 12:37 PM, Kelly Dean wrote:
>
>> Am I the only one having a problem with Qubes spontaneously rebooting on 
>> Intel hardware? Only other reports I see are about AMD problems, but I'm 
>> using an Intel Core i3.
>>
>> Happens every few weeks. Sometimes just 1 or 2 weeks, sometimes 5 or 6. Got 
>> it on Qubes 3.2, and now 4.0 too (new installation, not upgrade), multiple 
>> times.
>>
>> Unlikely to be a hardware problem. The system passed both memtest86 and a 
>> multi-day mersenne prime stress test. And other OSes tested on this hardware 
>> before I switched to Qubes, including Debian and Windows, never had a 
>> problem.
>>
>> The rebooting seems completely random. No apparent trigger, and no warning. 
>> Acts like an instant hard reset. Sometimes even when the system is idle, and 
>> I haven't touched the console for hours.
>>
>> It's wearingly inevitable enough that I don't even bother intentionally 
>> rebooting after system updates anymore, in order to minimize how many 
>> reboots I have to deal with (setting my workspace back up is an ordeal), 
>> because I know the system will end up spontaneously rebooting a week or two 
>> later anyway.
>
> I'm having this problem too. I hadn't had it for a while but in the past week 
> or so it's happened a few times. I have a Lenovo ThinkPad T440p with Intel 
> Core i7, and Qubes 4.0 which I keep updated.

I had this problem which was due to Intel AMT Control being enabled in the 
BIOS. Since turning this off my system has not rebooted.

Regards,

Chris

-
Chris Willard
ch...@meliser.co.uk

Sent with [ProtonMail](https://protonmail.com) Secure Email.

-- 
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/z3U_8tVcbDSKiFM4UNhpA7mQ-KeVSAZGQvCp1ZFq029fGIMoJA8w7tm2vmNWXV-BaEGqu7pHFh3FglIUq2tPzsJgt7GPDcpsgtSLogHy0DU%3D%40meliser.co.uk.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes won't boot after installation

[Arys Andreou]

On Friday, April 12, 2019 at 8:23:56 PM UTC+3, Nicklas Williams wrote:
> On Friday, April 12, 2019 at 4:10:53 AM UTC-7, a.e@gmail.com wrote:
> > I have a Dell Precision 5530 with an i7-8850 and NVidia Quadro P2000. The 
> > hard drive is a Class 40 M.2.
> > 
> > My issue is that after installing Qubes OS on my laptop the OS does not 
> > appear when booting. The message I get is "No bootable devices found".
> > 
> > I have tried both the automatic formatting of the drive as well as several 
> > custom configurations.
> > 
> > There is no other OS on the hard drive.
> 
> The 5530 does not allow legacy boot from internal hard drives.  I have a 5530 
> with similar specs.  I can install from legacy mode off a USB to the hard 
> drive, but once I restart it wont boot.  You MUST install from UEFI as far as 
> I know.  A few people have gotten it to work but I have not gotten the 
> installer to run so far.  There is another thread with details on how to make 
> it work.  Search for precision 5520 in qubes-users and read that thread.

Thank you, I'll check it 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/c645a072-a63e-47bb-a6df-dfddc9d51d70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Spontaneous rebooting

[unman]

On Sat, Apr 13, 2019 at 08:36:19AM +0200, David Hobach wrote:
> On 4/12/19 5:24 PM, Michael Siepmann wrote:
> > On 8/10/18 12:37 PM, Kelly Dean wrote:
> > 
> > > Am I the only one having a problem with Qubes spontaneously rebooting on 
> > > Intel hardware? Only other reports I see are about AMD problems, but I'm 
> > > using an Intel Core i3.
> > > 
> > > Happens every few weeks. Sometimes just 1 or 2 weeks, sometimes 5 or 6. 
> > > Got it on Qubes 3.2, and now 4.0 too (new installation, not upgrade), 
> > > multiple times.
> > > 
> > > Unlikely to be a hardware problem. The system passed both memtest86 and a 
> > > multi-day mersenne prime stress test. And other OSes tested on this 
> > > hardware before I switched to Qubes, including Debian and Windows, never 
> > > had a problem.
> > > 
> > > The rebooting seems completely random. No apparent trigger, and no 
> > > warning. Acts like an instant hard reset. Sometimes even when the system 
> > > is idle, and I haven't touched the console for hours.
> > > 
> > > It's wearingly inevitable enough that I don't even bother intentionally 
> > > rebooting after system updates anymore, in order to minimize how many 
> > > reboots I have to deal with (setting my workspace back up is an ordeal), 
> > > because I know the system will end up spontaneously rebooting a week or 
> > > two later anyway.
> > 
> > I'm having this problem too. I hadn't had it for a while but in the past
> > week or so it's happened a few times. I have a Lenovo ThinkPad T440p
> > with Intel Core i7, and Qubes 4.0 which I keep updated.
> 
> Same here, but only since 4.0 and since coreboot & ME-cleaner on a T530.
> 
> I've always suspected that it's related to memory kills (there was an OOM
> issue on github), but there's absolutely nothing in the journal after such a
> "forced" reboot.
> 

I dont see this on any machine, including long running desktops.
Is it possible that you are suffering from over-heating? That would
account for symptoms.

-- 
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/20190413135602.np6akvj7eq5slx64%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot install cubes on Lenovo X1 Carbon 4gen

[rogertobler via qubes-users]

Am Samstag, 13. April 2019 10:21:00 UTC+2 schrieb awokd:
> rogertobler via qubes-users wrote on 4/13/19 6:47 AM:
> > Am Samstag, 13. April 2019 01:36:54 UTC+2 schrieb awokd:
> >> rogertobler via qubes-users wrote on 4/12/19 12:52 PM:
> >>> Hi there
> >>>
> >>> When booting from usb, I am always ending up in the emergency shell. I 
> >>> see lots of "dracut-initqueue timeouts" and that's it.
> >>>
> >>> I tried to create a usb stick with fedora, but the documentation does not 
> >>> match the iso file. There is no xen.cfg on the iso, which would have to 
> >>> be edited.
> >>>
> >>> However the X1 Carbon should work.. May they just used Qubes 3, and not 4?
> >>>
> >> To edit the .iso, you need to extract it to a folder, edit, then
> >> recompress back to an .iso. I'm having a hard time finding a procedure
> >> describing this, though. Anyone who has done it able to write up a
> >> friendly one?
> > 
> > My problem is not to edit the iso, the problem is, that there is xen.cfg 
> > ohn the Qubes 4 iso, so I cannot get it to run on my Lenovo.
> > 
> I don't understand what you mean, then. Can you link to the 
> documentation you're talking about? Have you tried searching this 
> mailing list for "Carbon"? I know others on it have worked through 
> install problems.

It is this one:
https://www.qubes-os.org/doc/thinkpad-troubleshooting/#instructions-to-create-usb-installation-medium-for-newer-uefi-only-thinkpads

It tells you to update references in xen.cfg, but there is no xen.cfg. I also 
tried to install the Qubes 4 on a Gen 1 now, same behaviour. Although I know it 
worked with Qubes 3.

Looks like I'll just stick with Windows on these devices. :(

-- 
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/f72027b0-936c-43be-a7ab-9872f83cc550%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[qubes123]

For the Qubes R4.1 KDE compilation issue: you can kill the relevant KDE testing 
process, when the build reaches to that point with eg. htop.  Then the builder 
will continue and eventually will provide an iso.  

On the artifacts: I have an AMD APU with an older dGPU (HD-7000 series) and 
since Qubes kernel 4.19.x the radeon (amdgpu) module have some issues with 
swiotlb buffer overflow (Xen-4.8).  Newer kernel versions improved (at least 
xserver now can start with the APU drivers), but I still see some errors even 
in the latest 5.x versions.  I see no artifacts under xfce, however when I 
switch to KDE (to achieve GPU offloading), sometimes I have horizontal lines in 
the background windows, looking really messy

I plan to do more testing with fc29-dom0 and Xen-4.12 and we'll see if there's 
already improvement

-- 
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/f7ffa99d-7503-4abc-93b6-7b8fac31cbce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: just dreaming: mirage-tor ?

[Thomas Leonard]

On Tuesday, April 9, 2019 at 1:40:29 AM UTC+1, haaber wrote:
> as you may have noticed by the mirage-firewall discussions, one
> impressive point is the size of mirage -- 32M. That is not yet the 640K
> I grew up with, but much more memory-friendly than the
> standard-sys-firewall (which took 384M in my system). Another (to me:
> inexplicably large) qube in my system is sys-whonix - it takes  almost
> 900M of memory! So I was day-dreaming if a mirage-tor is potentially
> within reach ? Or is that
> - too complex
> - too hard to keep living, since tor itself evolves quickly

See: 
https://lists.xenproject.org/archives/html/mirageos-devel/2019-04/msg00018.html

-- 
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/7f0e42fd-a0d6-42de-b716-edae8790ed74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unable to install qubes on msi gl63 8rc

['awokd' via qubes-users]

pdkambo...@gmail.com wrote on 4/13/19 5:54 AM:

I did that. I got past salt installation, but now it got stuck while installing 
kernel-qubes-vm.x86

Could it be switching to some low power mode which breaks the install? 
Maybe try hitting the shift key every 10 minutes or so while it's 
installing. Otherwise, all I can suggest is generic steps like check out 
the detail entries for "Micro Star International" on 
https://www.qubes-os.org/hcl/, searching this mailing list for MSI + 
install, etc.


--
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/d8bdd3c5-bc0d-df65-4fcd-869f6b0baef0%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

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

[Thomas Leonard]

On Monday, April 8, 2019 at 9:45:05 AM UTC+1, Sphere wrote:
> So I have briefly read README.md about this and does this thing really have 
> to run as a PV VM and cannot be a PVH VM?

See: 
https://lists.xenproject.org/archives/html/mirageos-devel/2019-04/msg00019.html

-- 
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/b12d447f-4dfb-4233-a2f9-0c5d61a45012%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Looking to edit rules.ml of my mirage-firewall VM but since I cannot run shell, IDK what to do

[Thomas Leonard]

On Saturday, April 13, 2019 at 12:24:47 AM UTC+1, 799 wrote:
> Hello Thomas.
> On Thu, 11 Apr 2019 at 14:02, Thomas Leonard  wrote:
> [...]
> 
> I've added some examples at 
> https://github.com/mirage/qubes-mirage-firewall/pull/54 (see the changes to 
> rules.ml).
> 
> Thanks a lot for your excellent work and adding more information to 
> mirage-firewall, greatly appreciated.
> Regarding the example rules:
> 
> | { src = `Client `Dev; dst = `Client `Untrusted; proto = `TCP { dport = 22 } 
> } -> `Accept
> | { dst = `External `GoogleDNS } -> `Drop "block Google DNS"
> 
> these two rules are easy to understand and will help me setting up rules 
> between the AppVms
> 
> | { src = `Client _; dst = `Client _; proto = `TCP _; packet }
> when not (is_tcp_start packet) -> `Accept
> 
> Can you add more details about this rules, its an any-to-any rule, but what 
> is "when not (is_tcp_start packet) ?

The Dev->Untrusted:ssh rule allows TCP packets from Dev to Untrusted:ssh, but 
you also need to allow packets in the other direction. There are various ways 
to do that; this example rule allows any TCP packet that isn't trying to start 
a new TCP connection to go between AppVMs, which should do the trick.

You don't need this for external sites because the `NAT action also adds a rule 
that translates the responses, and that automatically allows the responses 
through. But `Accept just lets the packet through without remembering anything 
about the new connection.

is_tcp_start is defined in packet.ml. It means the same as Packet.is_tcp_start, 
but we can leave off the module name because of the "open Packet" at the top of 
rules.ml.

(* The first message in a TCP connection has SYN set and ACK clear. *)
let is_tcp_start = function
  | `IPv4 (_ip, `TCP (hdr, _body)) -> Tcp.Tcp_packet.(hdr.syn && not hdr.ack)
  | _ -> false

People who know more than me about TCP can probably suggest better ways to do 
this.

-- 
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/9e22ca35-9d4e-40d1-beaa-ae89a3f67278%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot install cubes on Lenovo X1 Carbon 4gen

['awokd' via qubes-users]

rogertobler via qubes-users wrote on 4/13/19 6:47 AM:

Am Samstag, 13. April 2019 01:36:54 UTC+2 schrieb awokd:

rogertobler via qubes-users wrote on 4/12/19 12:52 PM:

Hi there

When booting from usb, I am always ending up in the emergency shell. I see lots of 
"dracut-initqueue timeouts" and that's it.

I tried to create a usb stick with fedora, but the documentation does not match 
the iso file. There is no xen.cfg on the iso, which would have to be edited.

However the X1 Carbon should work.. May they just used Qubes 3, and not 4?


To edit the .iso, you need to extract it to a folder, edit, then
recompress back to an .iso. I'm having a hard time finding a procedure
describing this, though. Anyone who has done it able to write up a
friendly one?


My problem is not to edit the iso, the problem is, that there is xen.cfg ohn 
the Qubes 4 iso, so I cannot get it to run on my Lenovo.

I don't understand what you mean, then. Can you link to the 
documentation you're talking about? Have you tried searching this 
mailing list for "Carbon"? I know others on it have worked through 
install problems.



--
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/18be0425-8660-c981-00e7-d2366aecb707%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.