[qubes-users] Re: Lenovo T480/T480s anyone got power management working properly?

2019-08-04 Thread rec wins
On 8/4/19 8:37 AM, mmoris-dg3qef7t2pdafugrpc6...@public.gmane.org wrote:
> Hello,
> 
> I'm struggling to get my T480s working on resume as it displays a blank
> screen that doesn't allow me to do anything.
> All problematic modules are already part of the suspend blacklist:
> 
> ehci_pci
> xhci_pci
> iwldvm
> iwlmvm
> 
> Nonetheless the resume only works when I shutdown the sys-usb before the
> suspend, which is a bit painful to do on every suspend.
> Power management also doesn't work, when I press the power off button
> nothing happens nor the laptop enters the suspend state.
> The battery also get hot very quickly and drains very fast it seems its
> not optimized.
> 
> Did anyone managed to fix these issues with the T480s or the T480?
> 
> Any recommendations are really appreciate.
> 
> Thank 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+unsubscribe-/jypxa39uh5tlh3mboc...@public.gmane.org
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/6d955b4251a377fd6607926a01f818d4%40disroot.org
> .


???
This is a long-standing issue for some, resolved for some but not for
others at different times. See
https://github.com/QubesOS/qubes-issues/issues/4042

The situation has improved for me by getting kernel 4.19.43-1 from
qubes-dom0-security-testing. You could try the new kernel. (But note
that our problems might be a bit different, I never had a qrexec problem
when restarting sys-usb after resume.)

If you need to automate restarting of sys-usb because you can't avoid
this problem, you can add commands in
/usr/lib64/pm-utils/sleep.d/52qubes-pause-vms for suspend and resume,
e.g., qvm-shutdown sys-usb and qvm-start sys-usb. You might need to
qvm-kill sys-usb before suspend to get this to work reliably.

Daniel

-- 
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/4720d109-d5b9-20ad-300b-96dfbed304b3%40riseup.net.


[qubes-users] Runing qubes on macbook air (11 ince) mid 2012

2019-08-04 Thread ljul8047
If you have it already, you could give it a try and see how it goes 

-- 
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/bda159b9-01ea-4eec-9a40-33c1967f4b21%40googlegroups.com.


[qubes-users] Lenovo T480/T480s anyone got power management working properly?

2019-08-04 Thread mmoris
Hello,

I'm struggling to get my T480s working on resume as it displays a blank screen 
that doesn't allow me to do anything.
All problematic modules are already part of the suspend blacklist:

ehci_pci
xhci_pci
iwldvm
iwlmvm

Nonetheless the resume only works when I shutdown the sys-usb before the 
suspend, which is a bit painful to do on every suspend.
Power management also doesn't work, when I press the power off button nothing 
happens nor the laptop enters the suspend state.
The battery also get hot very quickly and drains very fast it seems its not 
optimized.

Did anyone managed to fix these issues with the T480s or the T480?

Any recommendations are really appreciate.

Thank 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/6d955b4251a377fd6607926a01f818d4%40disroot.org.


[qubes-users] Runing qubes on macbook air (11 ince) mid 2012

2019-08-04 Thread 27casanova27
seriously hasent any one atemted 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cf1b107d-d535-4428-ae9c-ca9f21fdb8a9%40googlegroups.com.


Re: [qubes-users] Are used laptops safe to use?

2019-08-04 Thread 'awokd' via qubes-users
ljul8...@gmail.com:
> Hello everyone, does anybody know if used laptops are safe to use for Qubes 
> or not since they might have malware (that could take over dom0) in them 
> already?
> 
Format the hard drive and you'll wipe most third party malware. The odds
of you finding a used laptop with one of the exceptions that survives a
format is slim. There is also a chance a new laptop could come
compromised. Up to you to determine what is "safe" for 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/5056b602-23df-e863-4dfc-6335ac701e67%40danwin1210.me.


Re: [qubes-users] Re: USB Controller passthru to HVM on Qubes 3.1

2019-08-04 Thread 'awokd' via qubes-users
Pete Howell:
> Has anyone ever gotten passthroughs to work?
> 
> On Tuesday, July 30, 2019 at 9:51:45 PM UTC-6, Pete Howell wrote:
>>
>> I'm trying to passthrough a StarTech 2-Port USB 3.1 Card (#PEXUSB312A2) to 
>> an HVM running Windows 7, and the device does not show up.  The device 
>> shows up in an lspci as:
>>
>> 01:00.0 USB controller: ASMedia Technology Inc. Device 2142
>>
>> $ xl pci-assignable-list
>> :01:00.0
>> :03:00.0
>> $ xl pci-assignable-add 01:00.0
>> libxl: warning: libxl_pci.c:636:libxl__device_pci_assignable_add: 
>> :01:00.0 already assigned to pciback
>>
>> I have tried attaching it from the VM manager and from the command line:
>>
>> $ qvm-pci -a win7 01:00.0
>> $ qvm-start win7
>> (no errors)
>> $ qvm-pci -l win7
>> ['01:00.0']
>>
>> What I don't understand is why the device doesn't show up in the device 
>> manager on Windows.  The driver software for Windows also doesn't see the 
>> device.
>>
>> Is there something that I'm missing to get the passthrough to work on a 
>> Windows HVM??
>>
> 
I've heard of people getting USB controller passthrough to Windows
working on 3.2+, but 3.1 is before my 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/40cf0485-d752-658b-7979-8ad7d5cfb9ca%40danwin1210.me.


Re: [qubes-users] cron.daily kills backups

2019-08-04 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 04/08/2019 12.38 AM, D. J. Bernstein wrote:
> The logs below seem self-explanatory. qubes-qube-manager printed
> 
>Connection to qubesd terminated, reconnecting in 1.0 seconds
> 
> on the terminal but this reconnection wasn't enough for recovery.
> 
> ---Dan
> 
> 
> Aug 04 03:51:01 dom0 anacron[31486]: Job `cron.daily' started
> Aug 04 03:51:01 dom0 run-parts[32608]: (/etc/cron.daily) starting logrotate
> ...
> Aug 04 03:51:02 dom0 systemd[1]: Stopping Qubes OS daemon...
> ...
> Aug 04 03:51:02 dom0 qubesd[2584]: caught SIGTERM, exiting
> ...
> Aug 04 03:51:02 dom0 widget-wrapper[5133]: Connection to qubesd terminated, 
> reconnecting in 1.0 seconds
> ...
> Aug 04 03:51:02 dom0 libvirtd[2291]: ... End of file while reading data: 
> Input/output error
> Aug 04 03:51:02 dom0 qubesd[2584]: Traceback (most recent call last):
> Aug 04 03:51:02 dom0 qubesd[2584]:   File "/usr/lib64/python3.5/runpy.py", 
> line 193, in _run_module_as_main
> Aug 04 03:51:02 dom0 qubesd[2584]: "__main__", mod_spec)
> Aug 04 03:51:02 dom0 qubesd[2584]:   File "/usr/lib64/python3.5/runpy.py", 
> line 85, in _run_code
> Aug 04 03:51:02 dom0 qubesd[2584]: exec(code, run_globals)
> Aug 04 03:51:02 dom0 qubesd[2584]:   File 
> "/usr/lib/python3.5/site-packages/qubes/tarwriter.py", line 179, in 
> Aug 04 03:51:02 dom0 qubesd[2584]: main()
> Aug 04 03:51:02 dom0 qubesd[2584]:   File 
> "/usr/lib/python3.5/site-packages/qubes/tarwriter.py", line 169, in main
> Aug 04 03:51:02 dom0 qubesd[2584]: copy_sparse_data(input_file, output, 
> sparse_map)
> Aug 04 03:51:02 dom0 qubesd[2584]:   File 
> "/usr/lib/python3.5/site-packages/qubes/tarwriter.py", line 130, in 
> copy_sparse_data
> Aug 04 03:51:02 dom0 qubesd[2584]: output_stream.write(buf_trailer)
> Aug 04 03:51:02 dom0 qubesd[2584]: BrokenPipeError: [Errno 32] Broken pipe
> 

Yes, I've experienced the same bug. We're tracking it here:

https://github.com/QubesOS/qubes-issues/issues/5004

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl1Geh0ACgkQ203TvDlQ
MDBKrQ/9H/Z6lEt/kQlsWgzmOQ1kUSzDIx9likOqFiTQb1Y7JurRXjfyEMI8/2RD
8inGGpvkSsSt5/c39zBs0TBgdwBofqmUCBJCVKv6cfluzG+If78SjKoTcDwS+3w1
kzGQE4HOs1w/KeccnXRISiHmcKSG1Pa8UZP0LJ8XvLUXIE4XLuduCJGZBON7itba
Cv/4Cx4yZ/8NYSPrVW7/GXLLBR4OxYxTF+zZ2PNHWej88N2EJ5wQjjNmOqpO/Pf0
1Ep7dw+LK0+3dODw1sxs+YFPhH1/D5quLlZbq8HnM6m27okM7huaVI1sLnssldk+
PuTxLbWHWdDBnn7a6jNY6zI0VUhmjYRgVcr8RtA4Xy6JYvztI2kcpKsHK76MzvVF
YIrjxsO5F9WlmqQK7BTfCaiETBwINQNpLEmoKhdtpsML1th+wLzN2XQqnvygidkW
JVMUHnQDfCr6fmXgZ1mR0HYho5W3p2NJ0YP379HUbLJxW1cEabo/6jkhKoEqvhff
CrMadGboCPNxuYC75Td47o9lAfxdzm9yPQB8XtA439VD/Sl6FZvus7AUoxiaHXk5
utS7VmAfaZYQc4cj4XBjh+LNNAcxNyWm8A4mHOgs7D5iGKii/otRaF6yKL//dYHo
JKKZOlFsRTr55LNz5RF3KJzuTpyBs8GaW9TM+yrpmUIuFwsRe2g=
=wXUg
-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/9db4b83e-ab7d-6b62-6815-3234686b1e46%40qubes-os.org.