net-firewall (they all depend on f24)
did not come up again. I thought that this will resolve with a second
clean reboot. But nope. So, the state is that I cannot start any appVM
(they close immediately), and I have no network. Worse: I have no idea
how to fix it, so I ask you for help.
Bernhard
On 24/01/2017 23:30, Ángel wrote:
> Bernhard wrote:
>> Hello, I bricked my system a bit. Yesterady I decided to follow the
>> ..onion update procedure. For dom0 all went well (after reading that I
>> must change to whonix-net),but I had to modify the debian-8 and
>> fe
On 25/01/2017 22:37, Ángel wrote:
> Bernhard wrote:
>> Thank you Angel, for helping me.
>>
> You're welcome, Bernhard.
>
>
>> and, as I said, nothing starts. I start thinking of a disaster-mode data
>> recovery since I do not know how I could possibly unb
install the hardware firmware
needed (try 'sudo lspci' to find out the chipset you have, try 'sudo dnf
search chipset-keyword' ). Bernhard
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group a
ks correctly cryptsetup luksClose
ALIAS and shutdown live-linux
samefor backup !
Good luck, Bernhard
--
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 qub
6G /swap and the rest/home
Thank you, Bernhard
> Hello,
>
> thank you for all help I got so far. The qubes adventure continues for
> me :) I do need
>
> a rather complete texlive installation, and when doing this with dnf I
> run out of space.
>
> Can someone gi
Hello,
thank you for all help I got so far. The qubes adventure continues for
me :) I do need
a rather complete texlive installation, and when doing this with dnf I
run out of space.
Can someone give me a hint what to do?
Thanks, Bernhard
--
You received this message because you
> Hello All,
>
> Does anyone use an alternate net-vm and have any notes on setting it
> up as I am having problems with internet connection? I am going to try
> getting it going but wondered if there was an alternative!
>
Hello, I used a debian-9 by the mentioned clone & update process and
also a
IP basis not a DNS basis
> (dns basis is sketchy anyways).
I perfectly agree that this 'phone home' business is inaccaptable. If
you consider that this type of firewall is easy to set up within qubes I
invite you to write a small tutorial on the subject for 'normal users'
.... thank you! Bernha
ebian-8-dvm' already
>> exists with uuid 61320a0c2-1e2a-4bff-b064-29fe587619b8
>>
>> Bernhard
> Look here:
> www.qubes-os.org/doc/remove-vm-manually
>
> That libvirt error sghows that you have a redundant entry in the db,
> which you need to remove.
> Then try creat
edora system, but fail in fedora-minimal? I have
no clue how too fix that. Anyone might help?
Bernhard
--
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
t
;2015" is
not completely re-assuring. Is there a newer one? Even if it were
up-to-date, what do I do with this file? Could someone give me a brief
summary (or give diff's to the well documented archlinux building process)?
Thank you! Bernhard
--
You received this message because you are subscribed to
VM ?
- did someone set up his filtering that way and give some hints / errors
to avoid?
Thanks, Bernhard
--
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
crypt-setuped by luks in a
standard tutorial way. Mount it, and move your data in.
Bernhard
--
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-use
e time
in the appvm are wrong (sometimes even in the future) - although dom0 is
accurately set up. If you have a cure to that (especially for debian) I
am interested ... maybe you experience the same problem? Bernhard
--
You received this message because you are subscribed to the Google Groups
"
; in rc.local
that I copied after some hardening discussion here in the forum 2 months
ago. I don't see how, but since I am lost I look for any possibility.
May you help me? Thx, Bernhard
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
Any hints? Or is there
good reason not to torify mail-fetching? Or never via IMAP?
thank you, Bernhard
--
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
for some help. Bernhard
--
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 qube
by your value)
(c) modify bad config files
(d) umount /mnt
(2) restart template-vm
and we're back! Bernhard
--
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
time. Either way, quick way to
find out whether a full restart works or not.
>> YES! So I guess things are linked to hilbernation problems when I close
>> the lid. Is there another cure than full reboot? Bernhard
> aha, this should narrow it down to possible suspects indeed.
>
:
>>>>> I freshly installed debian-9 ; when installing packages, apt-get
>>>>> hangs
>>>>> for days(!) with
>>>>>
>>>>> 81% [waiting for headers] ...
>>>>> followed by Err:XX Connection failed.
>>>>
.
>> So I am confused ... qubes-hcl-report says "HVM not active", same for
>> "I/O MMU" and further "no HAP". Is this a maybe BIOS setting I have to
>> change? Or another (non-cpu) hardware incompatibility? Thank you,
>> Bernhard
> Y
ching "qvm-start personal" in the neighbour terminal).
I hope I can get some help here, since I will have to reinstall 3.2
otherwise :(
Thank you, Bernhard
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
e it, attach its private.img
to sys-usb and follow then the above procedure as root in sys-usb (this
is how I made the backups, since I prefer doing them by hand).
Is there some flaw in my procedure? Thank you, Bernhard
--
You received this message because you are subscribed to the Google Groups
&
Thank you!
Bernhard
P.S: First, I thought that this is the annoying but harmless
"after-tempate-change-xfce-menu-messy" bug (which forces to go to VM
settings, remove all Applications, save, go there again, put them back &
save again to get all symlinks right). But the problem is
protected from usb-based attacks.
Overkill?
Bernhard
--
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.co
ould help many people in many
situations. I am not a bash hero, and before losing half a day on this
useful script, I prefer asking if someone did it already :) Thank you,
Bernhard
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To uns
On 02/02/2018 11:58 AM, Ilpo Järvinen wrote:
> On Fri, 2 Feb 2018, Bernhard wrote:
>
>> Did by chance someone write a dom0-script that
>>
>> a) fetches a list of all (running) appvm's that use sys-net.
>>
>> b) setting their net-vm to "none"
&
the loop device (you never mount a
disc, but a partition!). Instead, have to read the offset of the
partition start using fdisk or similar, and provide this offset to the
mount command. A quick google reveals the details on this procedure :)
Bernhard
--
You received this message because you are subscr
On 04/18/2018 03:58 PM, anon432 wrote:
I am getting the same error in dom0 and also getting "No New Updates" - which I
know is not true.
Does anyone have a link to a github issue where this has been filed?
https://github.com/QubesOS/qubes-issues/issues/3737
--
You received this message
the header
there ). Some experience with that? Cheers, Bernhard
--
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
By default network cards are assigned to sys-net and are not visible
in dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM
settings -> Devices tab, and make sure your network card is assigned
to it. So you need to run lsusb or lspci from within sys-net, not
dom0. You should also
However, I am stuck on how to determine how many days it has actually
been since the last backup.
What you are looking for is this command:
qvm-prefs --get $vm backup_timestamp
Nice. In case of a "manual backup", can you also set the variable that
way? Like
qvm-prefs --set $vm
That's the document I was referencing, but it doesn't mention using the
clipboard, only files. It seemed to me that passing plain text by the
clipboard to dom0 was going to be more secure than passing a complete
file, so assumed that would be the preferred method. Does such a
mechanism not
'Wyng' is a backup program I've been working on for a while that can
quickly backup "thin LVM" storage, the kind Qubes uses by default:
Link https://github.com/tasket/wyng-backup
I like your other scripts, so I had a look. That seems so damn complex
at first glance! Maybe you want to
destroying debian ... the trick is
maybe to keep them, but disabled? Cheers, Bernhard
--
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-user
ia apt-get). Also look the "UEFI troubleshooting" qubes
webpage! You can re-do the qubes boot entry with efibootmgr (please read
the man page, syntax is not memorisable for me). Good luck, Bernhard
--
You received this message because you are subscribed to the Google Groups
On 3/3/21 3:29 PM, frag face wrote:
Hi all,
I'm running Qubes 4.0
My dom0 doesn't boot anymore (following an aborted Fedora update it
seems...).
Boot runs to kernel panic, see attached image.
From a newly installed Qubes on a different disk, I can mount my
crashed disk, decrypt it and access
ted. After a few hours I could not figure out
limitations having the limits in place.
very good news, thank you. Bernhard
--
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
I tried a new install on a new disc, but
that fails even before finishing install, freezing as well :-(
Even a plain "live debian" freezes from time to time with i915 errors,
which gives a clue where the problem comes from.
Is there maybe a way to tweak the installer? Thanks,
best, Be
suspicion was early on the i915 driver. Also, i915
seems known problematic from 5.x kernels onwards any kind of other
linuxes (google it).
cheers, Bernhard
P.S: my chipset is an intel 620 [8086:5917] rev 07.
--
You received this message because you are subscribed to the Google Groups
"qubes-
you for your help,
Bernhard
--
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
always use 'sudo apt autoremove' afterwards and never run into problems.
So you probably can follow, what the upgrade function told you.
Cheers :)
Ulrich Windl schrieb am Dienstag, 5. Oktober 2021 um 23:53:02 UTC+2:
Following the instructions, my upgrade ended with this message:
The
how to include (e.g. by unpacking & repacking
the ISO) an additional 4.19 LTS kernel in the installer and boot it:
that would probably do the job. Alas, I got no help on this, yet. So I
launch my question again.
best, Bernhard
--
You received this message because you are subscribed to the
t as far as my dell hardware is concerned, 5.4 kernels are already
unstable. I expect no gain from this! I guess adding the 4.19
(extra)kernel to the iso is the least painful way to go.
Bernhard
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
really appreciate help of the dev's on that single point: an
explication of how to sneak in an extrakernel in the iso. They do not
need to explain iso packing & unpacking (that is easy), only how to
twiggle the iso boot procedure.
Thank you so much! Bernhard
--
You received this message bec
a hint on that? Cheers, Bernhard
--
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
47 matches
Mail list logo
