On 10/14/20 3:11 AM, mj.jos...@gmail.com wrote:
Hi, im aware that the answer to this question might be the whole
reason qubes compartmentalizes everything into virtual
machinesor just 'no', but I was wondering is there a way to
give a single qube read-only permission over all qubes on t
> Add rd.break at the end of kernel options
> mount -o remount,rw /sysroot
> chroot /sysroot
> qvm-prefs sys-usb autostart False
> exit
> exit
This is the first half, which will stop the VM from starting. The other
half is to remove `rd.qubes.hide_all_usb` from the kernel Commandline.
For UEFI,
Hi all,
I faced a wifi-related issue on Nitropad X230. Wifi used to work properly
at the beginning, but after update it stopped functioning.
After entering the following commands (according to the documentation here:
https://www.qubes-os.org/doc/wireless-troubleshooting/)
`sudo rmmod iwldvm`
Oct 14, 2020 14:44:38 Stumpy :
> I have recently had to reinstall qubes and I am at the point for making a
> sys-usb. I have a desktop and a usb keyboard so I thought I had previously
> just created one via sudo qubesctl state.sls qvm.sys-usb made it so it would
> NOT start on boot up and I wou
I have recently had to reinstall qubes and I am at the point for making
a sys-usb. I have a desktop and a usb keyboard so I thought I had
previously just created one via sudo qubesctl state.sls qvm.sys-usb made
it so it would NOT start on boot up and I would manually start it after
logging in..
I can open the .iso with "nano vim" but ultimately that doesn't get me to
the config file /EFI/BOOT/BOOTX64.cfg that is described but not named in
the following post.
I'm also rather concerned why there are two "Original Installer ISO" files
described here. Why doesn't he just list the filena
Try to follow my guide in my last post here:
https://groups.google.com/g/qubes-users/c/78DgmWxZf80
mandag den 5. oktober 2020 kl. 16.04.31 UTC+2 skrev awokd:
> Qubes:
> > On 10/5/20 10:21 AM, Knut von Walter wrote:
> >> Hi,
> >>
> >> at the moment I am trying to install Windows 10 following this
Try to follow my guide in my last post here:
https://groups.google.com/g/qubes-users/c/78DgmWxZf80
mandag den 12. oktober 2020 kl. 11.59.58 UTC+2 skrev Knut von Walter:
> Hi,
> I have read the documentation on this page,link:
> https://github.com/deeplow/qubes-doc/blob/gweck/patch-1/external/os
I have also tried to restart both the router and the Win 10 HVM and start
the Win 10 -HVM after the router is connected to the internet with the same
result.
When I use my other Win 10 HVM and start it after my router is connected to
the internet, it show internet access already on the Win 10 l
Suddenly I can't get internet access from within one of my Win 10 HVM's,
but I can from another one.
I have compared the internet settings under "Qube Settings". And it says
sys-whonix in both HVM's.
What can be the reason for not being able to get internet access from
within one of my Win 10
Hi, im aware that the answer to this question might be the whole reason
qubes compartmentalizes everything into virtual machinesor just
'no', but I was wondering is there a way to give a single qube read-only
permission over all qubes on the computer? so I can run something like
htop o
11 matches
Mail list logo
