[qubes-users] Can someone help me---again?

2020-07-31 Thread bob ruff
Someone helped me install Qubes a couple of years ago. I just started
learning it when I was interrupted--for 2 years. Now dom0 is reporting
update expired 455 days ago. Do I need to reinstall Qubes to do updates
etc.?

bob

-- 
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/CA%2BnE4cyV%3DEJEPLUuv8nv3C5nHfjme2dXtGnBgF4uGmwjket6HA%40mail.gmail.com.


Re: [qubes-users] Re: Available Templates

2020-07-31 Thread Qubes

On 7/31/20 6:50 PM, fiftyfourthparal...@gmail.com wrote:


On Friday, 31 July 2020 07:36:22 UTC+8, 54th Parallel wrote:


In dom0:

sudo qubes-dom0-updates --enablerepo=qubes-templates-community --action=list
qubes-template-*

or

sudo qubes-dom0-updates --enablerepo=qubes-templates-community-testing --
action=list qubes-template-*

Can't remember if there's a development repo off the top of my head



Also, remove "--enablerepo=qubes-templates-community"  for a list of
official templates (and mind the typo in 'qubes-dom0-update*s*')


Thank you that is exactly what I was looking for.

--
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/dcdc599f-f1fa-7ded-c1a9-33f7f86a103f%40ak47.co.za.


Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128

2020-07-31 Thread Rafael Reis
Quick update: Just ran the latest dom0 updates, kernel 4.19.132-1 booted 
normally. Still haven't tried the 5.6.x kernels again.

Em sexta-feira, 31 de julho de 2020 às 12:44:00 UTC-3, Rafael Reis escreveu:

> Hey, 
>
> Just want to register I've suffered from the same bug. After latest 
> update, got stuck on a single cursor on top of a black screen right before 
> the GUI login box.
> *Got around it by rolling back all the way to kernel 4.19.107-1.* Did it 
> by editing xen.cfg and setting default.
>
> I've been running kernel-latest very steadily for the past few months, and 
> Qubes for almost 2 years now. This was the first time I got a bad update. I 
> had even GPU IOMMU enabled with success. 
> I've share my HCL here before, I run a very well supported Dell Latitude 
> e5470 6th gen quad core 16GB ram.
>
> Hope to hear from Qubes team when it's safe again to go back to newer 
> kernels.
>
> Rafael
> Em quarta-feira, 29 de julho de 2020 às 16:44:11 UTC-3, qu...@ixls.eu 
> escreveu:
>
>> On 7/26/20 12:56 PM, Frédéric Pierret wrote: 
>> > 
>> > 
>> > On 2020-07-26 12:50, qubes via qubes-users wrote: 
>> >> On 6/27/20 6:55 AM, qubes via qubes-users wrote: 
>> >>> On 6/26/20 10:14 PM, Qubes wrote: 
>>  On 6/26/20 9:49 PM, qubes via qubes-users wrote: 
>> > On 6/13/20 5:36 PM, pudding wrote: 
>> >> I updated dom0 from the security-testing repo today due to the new 
>> CPU 
>> >> hardware bug. After finishing update and rebooting my laptop, it 
>> is 
>> >> stuck on the black screen forever, and will not load the LUKS 
>> decryption 
>> >> screen. 
>> >> .. 
>> > 
>> > Same problem on Lenovo t460 but "standard" repo/update. 
>> > 
>> > 
>> > 
>>  That is a real problem. I guess it is game over without a backup. 
>>  
>> >>> 
>> >>> As pudding said, you can boot the old kernel, thank spaghettimonster. 
>> >>> But what is the real cause of the problem? 
>> >>> Can I do something about it or will the next Dom0-Update fix this 
>> >>> problem? Shall I reinstall the .125-Kernel? 
>> >>> Or - worst case scenario - will newer kernels stop working on this 
>> >>> laptop in the future anyway? 
>> >> 
>> >> 
>> >> The newest kernel (128) won't boot neither :-( 
>> >> So I am still using 4.19.107. 
>> >> But on next update I will be out. (unless I can "preserve" the old 
>> kernel) 
>> >> 
>> > 
>> > In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher 
>> number to keep more kernel versions installed. Have you tried also 
>> kernel-latest? It's 5.7.X version. 
>> > 
>>
>> Thanks for the advice. Or simply I don't do an update :-) 
>>
>> > You say that you have black screen since kernel 4.19.125? 
>>
>> True. Just a blinking cursor. 
>>
>>
>>
>>
>>
>>

-- 
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/3c15e3da-92d2-47c7-a3b1-acd72c15b29en%40googlegroups.com.


[qubes-users] qvm-usb does not see any usb devices

2020-07-31 Thread Cranix
Hello,
I'v just installed qubes os on my desktop.(i used to have qubes
installed on it and it worked well, i had to reinstall it due to disk
issues).

I'm using fedora-32 as template for all appvms.
I have setted up sys-usb via saltstack.

After plugging in usb devices to ports in MOBO(tried usb memory stick,
usb mouse and usb audio interface) nothing is detected.
Only twice between a few reboots usb key was detected but only on
one(random) physical usb port.

All USB controllers are properly assigned to sys-usb..
I have usb mouse that has to be visible  to dom0,
/etc/qubes-rpc/qubes.InputMouse is properly set.

Both dom0 and fedora-32 template are up to date.
I will be gratefull for any tips how i can debug this issue,
i can attach system logs just please tell me what i should attach.

-- 
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/20200731180611.GA17976%40hackerspace.pl.


[qubes-users] Re: Available Templates

2020-07-31 Thread fiftyfourthparallel

On Friday, 31 July 2020 07:36:22 UTC+8, 54th Parallel wrote:
>
> In dom0:
>
> sudo qubes-dom0-updates --enablerepo=qubes-templates-community --action=list 
> qubes-template-*
>
> or
>
> sudo qubes-dom0-updates --enablerepo=qubes-templates-community-testing --
> action=list qubes-template-*
>
> Can't remember if there's a development repo off the top of my head
>

Also, remove "--enablerepo=qubes-templates-community"  for a list of 
official templates (and mind the typo in 'qubes-dom0-update*s*')

-- 
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/220834a1-2165-403c-ac94-eeb820df1882o%40googlegroups.com.


Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128

2020-07-31 Thread Rafael Reis
Hey, 

Just want to register I've suffered from the same bug. After latest update, 
got stuck on a single cursor on top of a black screen right before the GUI 
login box.
*Got around it by rolling back all the way to kernel 4.19.107-1.* Did it by 
editing xen.cfg and setting default.

I've been running kernel-latest very steadily for the past few months, and 
Qubes for almost 2 years now. This was the first time I got a bad update. I 
had even GPU IOMMU enabled with success. 
I've share my HCL here before, I run a very well supported Dell Latitude 
e5470 6th gen quad core 16GB ram.

Hope to hear from Qubes team when it's safe again to go back to newer 
kernels.

Rafael
Em quarta-feira, 29 de julho de 2020 às 16:44:11 UTC-3, qu...@ixls.eu 
escreveu:

> On 7/26/20 12:56 PM, Frédéric Pierret wrote:
> > 
> > 
> > On 2020-07-26 12:50, qubes via qubes-users wrote:
> >> On 6/27/20 6:55 AM, qubes via qubes-users wrote:
> >>> On 6/26/20 10:14 PM, Qubes wrote:
>  On 6/26/20 9:49 PM, qubes via qubes-users wrote:
> > On 6/13/20 5:36 PM, pudding wrote:
> >> I updated dom0 from the security-testing repo today due to the new 
> CPU
> >> hardware bug. After finishing update and rebooting my laptop, it is
> >> stuck on the black screen forever, and will not load the LUKS 
> decryption
> >> screen.
> >> ..
> >
> > Same problem on Lenovo t460 but "standard" repo/update.
> >
> >
> >
>  That is a real problem. I guess it is game over without a backup.
> 
> >>>
> >>> As pudding said, you can boot the old kernel, thank spaghettimonster.
> >>> But what is the real cause of the problem?
> >>> Can I do something about it or will the next Dom0-Update fix this
> >>> problem? Shall I reinstall the .125-Kernel?
> >>> Or - worst case scenario - will newer kernels stop working on this
> >>> laptop in the future anyway?
> >>
> >>
> >> The newest kernel (128) won't boot neither :-(
> >> So I am still using 4.19.107.
> >> But on next update I will be out. (unless I can "preserve" the old 
> kernel)
> >>
> > 
> > In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher 
> number to keep more kernel versions installed. Have you tried also 
> kernel-latest? It's 5.7.X version.
> > 
>
> Thanks for the advice. Or simply I don't do an update :-)
>
> > You say that you have black screen since kernel 4.19.125?
>
> True. Just a blinking cursor.
>
>
>
>
>
>

-- 
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/dde2b994-0180-4341-b2d7-36916d772cb4n%40googlegroups.com.