On Monday, December 16, 2019 at 5:33:52 PM UTC-5, Claudia wrote:
>
> brend...@gmail.com :
> > Disposable VMs were not developed with anti-forensics in mind (e.g. no
> protection in jurisdictions where you can be forced to hand over your drive
> password
> Never thought about it, but that makes
I'm trying to install Qubes 4.0 on laptop that has UEFI firmware (without the
Legacy option)
But I cannot get to the blue boot screen.
The official "Troubleshooting UEFI related problems", requires me to switch
to tty2 (Ctrl+Alt+F2) . But seems that there is no combination of keys that
eduzw...@gmail.com:
> And dmenu doesn't work. $mod+d does nothing. Typing "i3-dmenu-desktop" gives
> an error message "invalid input: "" doesn't match any application. Your
> command: exec --no startup-id ""
> Error: expected one of these tokens: '--no-startup-id',
>
>
> On xfce everything
Hi Claudia, thanks for your response
aplay -l responds this:
card 0: PCH HDA INTEL PCH device 0 ALC255 analog
the other command does work, but i dont know how to export those from dom 0
and its like 2 pages long, i hope it works without these infos.
gain was already 0
where do i set these
We have this same problem as here:
https://github.com/trezor/trezord-go/issues/163#issuecomment-552288220
The trezor devs reopened the issue, but looks like they have more important
problems to work.
Is anyone using Trezor 1 with Qubes 4 successfully?
What's the setup or at least
Hello All,
What is the general procedure in Qubes 4, if we can open the Luks, but then
pool00 seems inaccessible with rdsosreport message:
Check of pool qubes_dom0/pool00 failed (status:1). Manual repair required!
Thank you for your time.
Crypto Carabao Group
---
#Plow_with_Carabao!
> [ 4.776112] iwlwifi :00:06.0: Detected Killer(R) Wi-Fi 6 AX1650x
Not a solution but I believe the above line might help. Iwlwifi is
picking up the wrong device. I have another machine doing the same but
haven't got a solution. All I can say is that it came about with Kernel
5.3.x and
