-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 10.05 AM, Stumpy wrote:
> Hi, I was trying to figure how how to install the onlykey hardware
> token program and for whatever reason thier page,
> https://docs.crp.to/qubes.html, isnt the first thing that pops up
> when I searched so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 9.17 PM, drok...@gmail.com wrote:
> On Sunday, May 26, 2019 at 6:54:40 PM UTC-7, brend...@gmail.com
> wrote:
>> Guess I lucked out by using kernel-latest this time...
>
> It's working fine now. They had a new kernel that doesn't like
On Sunday, May 26, 2019 at 6:54:40 PM UTC-7, brend...@gmail.com wrote:
> Guess I lucked out by using kernel-latest this time...
It's working fine now. They had a new kernel that doesn't like old ATI Radeon
video cards. The kernel was removed from updates.
Hopefully in the future, somebody
Guess I lucked out by using kernel-latest this 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 post to this
Thanks to everyone who helped troubleshoot the latest dom0 kernel update issue.
Everything seems to be working just fine.
Fresh install uses kernel 4.14.74-1, and a full update takes it to 4.14.119-2.
Both working fine.
I hope the next kernel update doesn't break systems that have the old
After installing Qubes, I attempted to install Windows as a dualboot option.
Unfortunately, I didn't check to make sure windows wouldn't wipe my boot
partitions, so now I have nothing under /boot other than the Linux .imgs in the
LVM partition.
Is there a way to recover the old install? I
On Sunday, May 26, 2019 at 2:55:40 PM UTC-7, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 26/05/2019 4.47 PM, Andrew David Wong wrote:
> > On 26/05/2019 3.31 PM, drok...@gmail.com wrote:
> >> Can't launch Qubes Global settings window. I get:
> >
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 5.04 PM, Andrew David Wong wrote:
>
> On 26/05/2019 3.39 PM, Eva Star wrote:
>
If 4.19 is this problematic, should the update be pulled?
>>>
>>> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 3.44 PM, Eva Star wrote:
>
>> Don't touch your existing M.2 drive. Get a spare drive (spinning rust
>> is OK) at least as large as your M.2 drive and that you can attach to
>> your machine (e.g. with a USB SATA dock).
>>
>> Download
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 25/05/2019 9.16 PM, drok...@gmail.com wrote:
> Yes, that worked. I'm back to a fresh install.
>
> I didn't know we could do that. Damn, I was a little hasty formatting my
> drive. That's okay, I didn't lose much.
>
> If I try upgrading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 3.39 PM, Eva Star wrote:
>
>>> If 4.19 is this problematic, should the update be pulled?
>>
>> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my
>> problem.
>>
>
> Yes, problems :(
> Currently, you can install
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 4.47 PM, Andrew David Wong wrote:
> On 26/05/2019 3.31 PM, drok...@gmail.com wrote:
>> Can't launch Qubes Global settings window. I get:
>
>> [Dom0] Houston, we have a problem...
>
>> Whoops. A critical error has occured. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 10.15 AM, drok...@gmail.com wrote:
> On Sunday, May 26, 2019 at 5:38:00 AM UTC-7, awokd wrote:
>> drok...@gmail.com:
>>> What is the point of backing up a qube, if you can't restore to it?
>>>
>>> I'm restoring a full backup, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 26/05/2019 3.31 PM, drok...@gmail.com wrote:
> Can't launch Qubes Global settings window. I get:
>
> [Dom0] Houston, we have a problem...
>
> Whoops. A critical error has occured. This is most likely a bug
> in Qubes Global Settings
YouTube videos of
U.S. Congress money laundering hearing
of
Saudi Billionaire " Maan Al sanea"
with *bank of America*
and The owner of Saad Hospital and Schools
in the Eastern Province in *Saudi Arabia*
and the Chairman of the Board of Directors of Awal Bank in *Bahrain*
> Don't touch your existing M.2 drive. Get a spare drive (spinning rust
> is OK) at least as large as your M.2 drive and that you can attach to
> your machine (e.g. with a USB SATA dock).
>
> Download Tails to a USB stick. Boot your machine into Tails. Connect
> your spare drive. `fdisk -l`
> > If 4.19 is this problematic, should the update be pulled?
>
> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my
> problem.
>
Yes, problems :(
Currently, you can install all dom0 updates, but before actual reboot change
kernel manually to previous that reboot and all
Can't launch Qubes Global settings window. I get:
[Dom0] Houston, we have a problem...
Whoops. A critical error has occured. This is most likely a bug in Qubes
Global Settings application.
TypeError: setChecked(self, bool): argument 1 has unexpected type 'str' at line
248 of file
drok...@gmail.com:
I agree the qubes backup/restore is easier. I learned the lesson of don't make
any changes to system templates like Debian-9, because you can't backup/restore
them. I'm trying to keep the number of qubes down to just one screen full in
Qubes Manager, which gets hard
On Sunday, May 26, 2019 at 10:15:09 AM UTC-7, awokd wrote:
> drok...@gmail.com:
> > Hi,
> >
> > I'd like to boot a usb, and do full backup/restores of a qubes install,
> > offline.
> >
> > Anyone doing this already? Some kind of qubes specific recovery usb, with
> > lots of room for backups.
On Sunday, May 26, 2019 at 10:46:51 AM UTC-7, awokd wrote:
> Eva Star:
> >
> >> Seems that the 4.19.x branch was problematic with some AMD cards.
> >>
> >
> > Maybe :) But I have problem and there is hybrid index hd + nvidia card (not
> > used). In my case this kernel have problems with CPU :)
On 5/26/19 8:04 AM, evas...@firemail.cc wrote:
Hello,
Oh no... :(
After last update (kernel) system almost dead!
It can boot and I have access to dom0 console, but mouse not work and
there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes
eating to much cpu
How to remove last
evas...@firemail.cc:
> Hello,
> Oh no... :(
> After last update (kernel) system almost dead!
> It can boot and I have access to dom0 console, but mouse not work and
> there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes
> eating to much cpu
> How to remove last update? How to
On 5/26/19 1:14 PM, Eva Star wrote:
I have secondary drive with windows 10. I never run windows, but I keep it,
because it maybe be useful(needed) some day. But now I want to use this
secondary drive as storage for some of my VMs. Maybe 1) part of this drive and
keep windows or 2) whole drive
Eva Star:
Seems that the 4.19.x branch was problematic with some AMD cards.
Maybe :) But I have problem and there is hybrid index hd + nvidia card (not
used). In my case this kernel have problems with CPU :)
For a counterpoint, I think drokmed also had a Radeon card, and their
> Seems that the 4.19.x branch was problematic with some AMD cards.
>
Maybe :) But I have problem and there is hybrid index hd + nvidia card (not
used). In my case this kernel have problems with CPU :)
--
You received this message because you are subscribed to the Google Groups
Like others have reported, I updated my Qubes system earlier today with
the 4.19.43 kernel along with the xen updates. Past updates have gone
smoothly for the duration of my running Qubes but unfortunately this one
wasn't.
The update itself installed fine with no issues or errors. I was able
drok...@gmail.com:
Hi,
I'd like to boot a usb, and do full backup/restores of a qubes install, offline.
Anyone doing this already? Some kind of qubes specific recovery usb, with lots
of room for backups.
In my opinion (others might have better ideas), Qubes isn't the right
tool for that
I have secondary drive with windows 10. I never run windows, but I keep it,
because it maybe be useful(needed) some day. But now I want to use this
secondary drive as storage for some of my VMs. Maybe 1) part of this drive and
keep windows or 2) whole drive for storage.
What are the
'Evastar' via qubes-users:
Again, what to do now? Never update or try to wait for month and then update?
Short term, continue applying template updates as usual. If you run
"sudo qubes-dom0-update", you can check for updates, but make sure to
choose not to apply them with N. Wait for the
Thanks for the note...I saw this just before my recent Dom0 and other updates.
I too had similar symptoms including: " I noticed that several qubes didn't
shutdown quite right, click on the right Q button, they were still there, but
showed zero memory usage."
I did a back up before shutting
> Did you notice any other errors around the soft lockup? Try searching
> for them; it would be good to figure out what's causing the lockup, but
> it can be hard to do.
Only one error: all system very unresponsive, :) And as I'm already note 100%
cpu usage by some processes. Also I saw strange
Hi,
I'd like to boot a usb, and do full backup/restores of a qubes install, offline.
Anyone doing this already? Some kind of qubes specific recovery usb, with lots
of room for backups.
Thanks
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
evas...@firemail.cc:
By the way, I got the idea and switched to other tty before login to the
system where Qubes Manager and other tasks start. It give me some time
to use the system. And I found the bug at std error output:
!
wachdog: BUG: soft lockup - CPU#3 stuck for 23s!
Hi, I was trying to figure how how to install the onlykey hardware token
program and for whatever reason thier page,
https://docs.crp.to/qubes.html, isnt the first thing that pops up when I
searched so I thought I'd suggest putting a link to thier qubes setup page.
--
You received this
By the way, I got the idea and switched to other tty before login to the
system where Qubes Manager and other tasks start. It give me some time
to use the system. And I found the bug at std error output:
!
wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325]
kernel
Hello,
I have two rendering issues. Maybe they are related, maybe they aren't.
## 1. screen flashbacks
I don't remember when it started.
Some parts of screen have short random flashbacks, i.e. it shows the content
shown some time ago. You can see a short video there:
Maybe it's possible to return to this emergency mode? System freeze
until Qubes Manager start. It can freeze at 45% or at 91% or at any
point. I see high cpu usage. It freeze because of this. I shutdown it
before at this point and filesystem corrupt. Need the way to access
/boot/efi without
Filesystem corruption is a different issue. In the emergency console,
"fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks,
then "reboot". If that lets you get back into Qubes, DO NOT DO
ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as
previously described.
evas...@firemail.cc:
On 2019-05-26 15:57, 'awokd' via qubes-users wrote:
Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg
it request to run fsch or e2fsck. What I must run first and how?
Then if filesystem will be fixed, how to mount boot to change it? I
guess this emergency console can help
On 2019-05-26 15:57, 'awokd' via qubes-users wrote:
Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg
it request to run fsch or e2fsck. What I must run first and how?
Then if filesystem will be fixed, how to mount boot to change it? I
guess this emergency console can help me, because dom0
On 2019-05-26 16:32, 'awokd' via qubes-users wrote:
Yes, but be aware that it may mount the boot directory you're looking
to edit underneath a different location, so watch the messages when
you do.
What is correct "mount" command to do this?
And to fix filesystem then...
--
You received
ptilden:
Hello,
I have installed Qubes 4.0.1
I need to configure a printer in the Template VM. I start fedora-29 TemplateVM and
select Template:fedora-29 -> fedora-29: Settings and after a bit of disk activity
nothing appears. I have also started Template:fedora-29 -> fedora-29: Terminal and
evas...@firemail.cc:
On 2019-05-26 15:57, awokd wrote:
First thing to try is to rollback the dom0 kernel update. If you're
using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change
the default kernel line at the top to point to the previous version
number. Save and reboot. If you're
On 2019-05-26 15:57, awokd wrote:
First thing to try is to rollback the dom0 kernel update. If you're
using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change
the default kernel line at the top to point to the previous version
number. Save and reboot. If you're not sure how to do
Hello,
I have installed Qubes 4.0.1
I need to configure a printer in the Template VM. I start fedora-29 TemplateVM
and select Template:fedora-29 -> fedora-29: Settings and after a bit of disk
activity nothing appears. I have also started Template:fedora-29 -> fedora-29:
Terminal and typed the
evas...@firemail.cc:
Okey... keep calm...
Time to time I can use dom0 console without troubles (sudo
qubes-dom0-update also still work by no fix still come :( )
I guess now need to somehow change new kernel to old one?
How to do this? I guess I'm at UEFI mode (new notebook)
1) boot from some
Okey... keep calm...
Time to time I can use dom0 console without troubles (sudo
qubes-dom0-update also still work by no fix still come :( )
I guess now need to somehow change new kernel to old one?
How to do this? I guess I'm at UEFI mode (new notebook)
1) boot from some qubes installed usb
drok...@gmail.com:
What is the point of backing up a qube, if you can't restore to it?
I'm restoring a full backup, and instead of restoring to qubes, it's creating
new ones with different names. WTF!
What the hell am I supposed to do now? Delete the original qubes, and rename
the
Hello,
Oh no... :(
After last update (kernel) system almost dead!
It can boot and I have access to dom0 console, but mouse not work and
there is 100% cpu usage by (1.xvdb-1 / 7.xvdc-1) and other processes
eating to much cpu
How to remove last update? How to recover now?
Data is urgent. I
On Saturday, May 25, 2019 at 10:55:44 PM UTC+2, dro...@gmail.com wrote:
> I just finished a fresh install of Qubes, then updated dom0, fedora template,
> debian template, whonix gw and ws templates, as per instructions on
>
> https://www.qubes-os.org/doc/installation-guide/
>
> Shutdown, boot.
51 matches
Mail list logo
