Re: [qubes-users] Re: YouTube Sound & Video

[Pmonf]

Thanks for the tip on /boo/efi/EFI/qubes. I will remember that.  I am still 
reading logs and have not found anything blatantly relevant yet. Still 
looking! 

On Friday, July 24, 2020 at 10:33:03 PM UTC-4, awokd wrote:
>
> Pmonf: 
> > Thanks for the help. I don't know what I am looking at but here is the 
> > whole ball of wax down to the software rendering line: cat Xorg.0.log 
> > [   159.890] 
> > X.Org X Server 1.19.3 
> > Release Date: 2017-03-15 
> > [   159.890] X Protocol Version 11, Revision 0 
> > [   159.890] Build Operating System:  4.9.3-200.fc25.x86_64 
> > [   159.890] Current Operating System: Linux dom0 
> > 4.19.128-1.pvops.qubes.x86_64 #1 SMP Sun Jun 28 06:19:18 UTC 2020 x86_64 
> > [   159.890] Kernel command line: root=/dev/mapper/qubes_dom0-root 
> > rd.luks.uuid=luks-cc9a361d-df73-48c7-bccb-e6f389932480 
> > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap 
> i915.alpha_support=1 
> > rhgb quiet rd.qubes.hide_all_usb plymouth.ignore-serial-consoles 
> > [   159.890] Build Date: 15 March 2017  06:37:12PM 
> > [   159.890] Build ID: xorg-x11-server 1.19.3-1.fc25 
> > [   159.890] Current version of pixman: 0.34.0 
> > [   159.890] Before reporting problems, check http://wiki.x.org 
> > to make sure that you have the latest version. 
> > [   159.890] Markers: (--) probed, (**) from config file, (==) default 
> > setting, 
> > (++) from command line, (!!) notice, (II) informational, 
> > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 
> > [   159.890] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 24 
> > 15:40:39 2020 
> > [   159.891] (==) Using config directory: "/etc/X11/xorg.conf.d" 
> > [   159.891] (==) Using system config directory 
> "/usr/share/X11/xorg.conf.d" 
> > [   159.893] (==) No Layout section.  Using the first Screen section. 
> > [   159.893] (==) No screen section available. Using defaults. 
> > [   159.893] (**) |-->Screen "Default Screen Section" (0) 
> > [   159.893] (**) |   |-->Monitor "" 
> > [   159.893] (==) No monitor specified for screen "Default Screen 
> Section". 
> > Using a default monitor configuration. 
> > [   159.893] (==) Automatically adding devices 
> > [   159.893] (==) Automatically enabling devices 
> > [   159.893] (==) Automatically adding GPU devices 
> > [   159.894] (==) Automatically binding GPU devices 
> > [   159.894] (==) Max clients allowed: 256, resource mask: 0x1f 
> > [   159.894] (==) FontPath set to: 
> > catalogue:/etc/X11/fontpath.d, 
> > built-ins 
> > [   159.894] (==) ModulePath set to "/usr/lib64/xorg/modules" 
> > [   159.894] (II) The server relies on udev to provide the list of input 
> > devices. 
> > If no devices become available, reconfigure udev or disable 
> > AutoAddDevices. 
> > [   159.894] (II) Loader magic: 0x825e00 
> > [   159.894] (II) Module ABI versions: 
> > [   159.894] X.Org ANSI C Emulation: 0.4 
> > [   159.894] X.Org Video Driver: 23.0 
> > [   159.894] X.Org XInput driver : 24.1 
> > [   159.894] X.Org Server Extension : 10.0 
> > [   159.895] (++) using VT number 1 
> > 
> > [   159.895] (II) systemd-logind: logind integration requires -keeptty 
> and 
> > -keeptty was not provided, disabling logind integration 
> > [   159.897] (--) PCI:*(0:0:2:0) 8086:9b41:17aa:5079 rev 2, Mem @ 
> > 0xb000/16777216, 0xa000/268435456, I/O @ 0x3000/64, BIOS @ 
> > 0x/131072 
> > [   159.898] (II) LoadModule: "glx" 
> > [   159.898] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so 
> > [   159.911] (II) Module glx: vendor="X.Org Foundation" 
> > [   159.911] compiled for 1.19.3, module version = 1.0.0 
> > [   159.911] ABI class: X.Org Server Extension, version 10.0 
> > [   159.911] (==) Matched intel as autoconfigured driver 0 
> > [   159.911] (==) Matched modesetting as autoconfigured driver 1 
> > [   159.911] (==) Matched fbdev as autoconfigured driver 2 
> > [   159.911] (==) Matched vesa as autoconfigured driver 3 
> > [   159.911] (==) Assigned the driver to the xf86ConfigLayout 
> > [   159.911] (II) LoadModule: "intel" 
> > [   159.911] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so 
> > [   159.914] (II) Module intel: vendor="X.Org Foundation" 
> > [   159.914] compiled for 1.19.3, module version = 2.99.917 
> > [   159.914] Module class: X.Org Video Driver 
> > [   159.914] ABI class: X.Org Video Driver, version 23.0 
> > [   159.914] (II) LoadModule: "modesetting" 
> > [   159.914] (II) Loading 
> /usr/lib64/xorg/modules/drivers/modesetting_drv.so 
> > [   159.915] (II) Module modesetting: vendor="X.Org Foundation" 
> > [   159.915] compiled for 1.19.3, module version = 1.19.3 
> > [   159.915] Module class: X.Org Video Driver 
> > [   159.915] ABI class: X.Org Video Driver, version 23.0 
> > [   159.915] (II) LoadModule: "fbdev" 
> > [   159.915] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so 
> > [   159.917] (II) Module fbdev: vendor="X.O

[qubes-users] Re: XScreensaver randomly popping up

[fiftyfourthparallel]

On Tuesday, 28 July 2020 00:13:16 UTC+8, ludwig...@gmail.com wrote:
>
> Hi I had/had the problem with qubes 3.2, which is very annoying.
> Funny thing: you can trick xscreensaver by switching the desktop 
> if you have multiple desktops, which leads to odd/funny user
> experience of locked screen, that shows desktop and is usable,
> if you force it to redraw windows by moving windows and the like
>
> Does ist feel the same?
>
>
Not quite, but multiple desktops might possibly have something to do with 
it.

In my situation I'm actively using whatever desktop is on the screen and 
the screensaver pops up or the screen locks (can't tell, since both are the 
same)

Just earlier it did it again--this time when I was reading the output of 
xentop maximized with another terminal on top of it (i.e. not typing 
anything)

-- 
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/3fe08b0d-1b8c-47a1-a1fd-df92dc797d5fo%40googlegroups.com.

[qubes-users] Re: XScreensaver randomly popping up

[ludwig...@gmail.com]

Hi I had/had the problem with qubes 3.2, which is very annoying.
Funny thing: you can trick xscreensaver by switching the desktop 
if you have multiple desktops, which leads to odd/funny user
experience of locked screen, that shows desktop and is usable,
if you force it to redraw windows by moving windows and the like

Does ist feel the same?

On Monday, July 27, 2020 at 2:27:03 AM UTC fiftyfour...@gmail.com wrote:

> Also, since I started a thread, I also want to ask whether SHA1 or other 
> deprecated algorithms are used in the PGP verification of dom0 and domu 
> updates. This is somewhat related to my original question.
>
>
> https://arstechnica.com/information-technology/2020/01/pgp-keys-software-security-and-much-more-threatened-by-new-sha1-exploit/
>

-- 
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/4b0df715-8cb1-4c2d-8985-1fa4129edc3an%40googlegroups.com.

[qubes-users] Re: Bullseye and Kali templates // MANY THANKS!

[ludwig...@gmail.com]

MANY THANKS!

On Wednesday, July 22, 2020 at 4:49:39 PM UTC unman wrote:

> Hello All,
>
> I've uploaded new builds of the bullseye and Kali templates to
> https://qubes.3isec.org/Templates for any one who is interested.
>
> These packages are signed with my Qubes Signing key - you can find this
> on keyservers, in this list, and at GitHub. Verify the key, and then check
> the signature on the template package.
>
> If you are satisfied, copy the package in to dom0, and then install it
> with `dnf install`.
>
> The Kali template has all the packages of a standard Kali install,except
> for amass and cherrytree which are currently broken. (Problems of using
> a rolling distro based on a testing Debian - things will just break.)
> Otherwise all your favourite tools are there.
>
> As always, any one can dig in and examine the packages - comments always
> welcome.
>
> unman
>

-- 
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/9e309b4f-966a-4131-b10f-3af7eaef2133n%40googlegroups.com.

[qubes-users] Re: Fwd: Audio not working: "snd_hda_intel: No response from codec, resetting bus"

[fiftyfourthparallel]

On Monday, 16 December 2019 01:11:25 UTC+8, Claudia wrote:
>
> Claudia: 
> > [...] 
> > So, to recap what I've found so far: 
> > Fedora 25 live cd: works 
> > Qubes without Xen: works 
> > Qubes with Xen: codec probe error 
> > Qubes with Xen, VT-x & VT-d disabled: codec probe error 
> > Qubes with Xen, single_cmd=1: codec detected, but no sound 
> > 
> > [...] 
>
> Just following up. Audio works flawlessly out of the box in 
> R4.1-20181013 with kernel 4.19.76-1. Didn't work in R4.0.2 with 4.19 or 
> even 5.0 kernels even after days of tinkering with it. So it could be 
> due to the Xen version (4.8 -> 4.12), Fedora userland version (25 -> 
> 29), or changes to qubes-specific code/config (4.0 -> 4.1). I was hoping 
> to get it working in stable, but I'll probably just keep using 4.1 for 
> now. 
>
> - 
> This free account was provided by VFEmail.net - report spam to 
> ab...@vfemail.net  
>   
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of 
> the NSA's hands! 
> $24.95 ONETIME Lifetime accounts with Privacy Features!   
> 15GB disk! No bandwidth quotas! 
> Commercial and Bulk Mail Options!   
>

Hi Claudia,

I'm suffering from the same problem as you, and 'dmesg | grep -i 
snd_hda_intel' brought me to this thread. 

My sound was originally working fine after I updated dom0 and domus (tested 
via Youtube) but somewhere along the line something broke and the next time 
I did the same thing, no sound. I did everything in my non-technical power 
but it's dead, bub. No idea what caused it.

dmesg output in short:

snd_hda_intel [Audio device PCI code thing]: azx_get_response timeout, 
switching to polling mode: last cmd=0xX

snd_hda_intel [Audio device PCI code thing]: No response from codec, 
resetting bus: last cmd=0xX(this line keeps repeating)

snd_hda_intel [Audio device PCI code thing]: azx_get_response timeout, 
switching to single_cmd mode: last cmd=0xX

snd_hda_codec_realtek hdaudioC0D0: Unable to sync to register 0xXXX. -5
snd_hda_codc_hdmi hdaudioC0D2: HDMI: invalid ELD buf size   (note I'm not 
using HDMI)


-- 
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/ab53b185-c661-4493-bb16-8a126fed1b99o%40googlegroups.com.

Re: [qubes-users] Re: qubes template centos-8? 693M Updates

[Frédéric Pierret]

On 2020-07-27 16:27, ludwig...@gmail.com wrote:
> 
> Hi all,
> regarding templates. Is it possible to have rolling updates with the 
> templates, so all the users downloading templates
> dont need to update them.
> So once a week an update for the templetes would be nice. I am sure this can 
> be automated.
> 
> Installing the updates at the source of the templates scales better compared 
> to everyone installing updates.
> 

That's mostly a problem of limited ressources of infrastructure we have which 
are already heavily loaded.

Regards,

-- 
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/4306c97d-093a-c942-3585-6a548f3bed68%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: qubes template centos-8? 693M Updates

[ludwig...@gmail.com]

Hi all, 
regarding templates. Is it possible to have rolling updates with the 
templates, so all the users downloading templates
dont need to update them.
So once a week an update for the templetes would be nice. I am sure this 
can be automated.

Installing the updates at the source of the templates scales better 
compared to everyone installing updates.


Cheers,

Ludwig

On Monday, July 27, 2020 at 1:08:36 PM UTC ludwig...@gmail.com wrote:

>
> Hi all, I tried to download a centos8-template, but it seems to be 
> unavailable.
>
> xxx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community 
> qubes-template-centos-8
> Using xxx-vm as UpdateVM to download updates for Dom0; this may take some 
> time...
> Fedora 25 - x86_64 - Updates2.3 MB/s |  24 MB 
> 00:10
> Fedora 25 - x86_64  2.4 MB/s |  50 MB 
> 00:21
> Qubes Dom0 Repository (updates) 2.1 MB/s |  19 MB 
> 00:09
> determining the fastest mirror (15 hosts).. done.--  B/s |   0  B 
> --:-- ETA
> Qubes Templates repository  4.1 kB/s |  17 kB 
> 00:03
> Qubes Community Templates repository 13 kB/s | 5.7 kB 
> 00:00
> Last metadata expiration check: 0:00:01 ago on Mon Jul 27 13:04:40 2020.
> No match for argument: qubes-template-centos-8
> Error: Unable to find a match: qubes-template-centos-8
> [xxx@dom0 ~]$ 
> Any thoughts?
>
> Cheers,
>
> Ludwig
>
>

-- 
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/2297fa2f-58ca-4c3b-9866-4399afd450e6n%40googlegroups.com.

[qubes-users] Re: qubes template centos-8?

[ludwig...@gmail.com]

Thanks! now it works!


On Monday, July 27, 2020 at 1:08:36 PM UTC ludwig...@gmail.com wrote:

>
> Hi all, I tried to download a centos8-template, but it seems to be 
> unavailable.
>
> xxx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community 
> qubes-template-centos-8
> Using xxx-vm as UpdateVM to download updates for Dom0; this may take some 
> time...
> Fedora 25 - x86_64 - Updates2.3 MB/s |  24 MB 
> 00:10
> Fedora 25 - x86_64  2.4 MB/s |  50 MB 
> 00:21
> Qubes Dom0 Repository (updates) 2.1 MB/s |  19 MB 
> 00:09
> determining the fastest mirror (15 hosts).. done.--  B/s |   0  B 
> --:-- ETA
> Qubes Templates repository  4.1 kB/s |  17 kB 
> 00:03
> Qubes Community Templates repository 13 kB/s | 5.7 kB 
> 00:00
> Last metadata expiration check: 0:00:01 ago on Mon Jul 27 13:04:40 2020.
> No match for argument: qubes-template-centos-8
> Error: Unable to find a match: qubes-template-centos-8
> [xxx@dom0 ~]$ 
> Any thoughts?
>
> Cheers,
>
> Ludwig
>
>

-- 
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/9bfb5c4a-8225-4b20-a15b-f147689e2cd9n%40googlegroups.com.

Re: [qubes-users] qubes template centos-8?

[Frédéric Pierret]

On 2020-07-27 15:08, ludwig...@gmail.com wrote:
> 
> Hi all, I tried to download a centos8-template, but it seems to be 
> unavailable.
> 
> xxx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community 
> qubes-template-centos-8
> Using xxx-vm as UpdateVM to download updates for Dom0; this may take some 
> time...
> Fedora 25 - x86_64 - Updates    2.3 MB/s |  24 MB 00:10   
> Fedora 25 - x86_64  2.4 MB/s |  50 MB 00:21   
> Qubes Dom0 Repository (updates) 2.1 MB/s |  19 MB 00:09   
> determining the fastest mirror (15 hosts).. done.--  B/s |   0  B --:-- 
> ETA
> Qubes Templates repository  4.1 kB/s |  17 kB 00:03   
> Qubes Community Templates repository 13 kB/s | 5.7 kB 00:00   
> Last metadata expiration check: 0:00:01 ago on Mon Jul 27 13:04:40 2020.
> No match for argument: qubes-template-centos-8
> Error: Unable to find a match: qubes-template-centos-8
> [xxx@dom0 ~]$
> Any thoughts?

sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing 
qubes-template-centos-8

-- 
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/67433971-73c5-5683-2cb3-a9aaf0a3659a%40qubes-os.org.


signature.asc
Description: OpenPGP digital signature

[qubes-users] qubes template centos-8?

[ludwig...@gmail.com]

Hi all, I tried to download a centos8-template, but it seems to be 
unavailable.

xxx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community 
qubes-template-centos-8
Using xxx-vm as UpdateVM to download updates for Dom0; this may take some 
time...
Fedora 25 - x86_64 - Updates2.3 MB/s |  24 MB 
00:10
Fedora 25 - x86_64  2.4 MB/s |  50 MB 
00:21
Qubes Dom0 Repository (updates) 2.1 MB/s |  19 MB 
00:09
determining the fastest mirror (15 hosts).. done.--  B/s |   0  B --:-- 
ETA
Qubes Templates repository  4.1 kB/s |  17 kB 
00:03
Qubes Community Templates repository 13 kB/s | 5.7 kB 
00:00
Last metadata expiration check: 0:00:01 ago on Mon Jul 27 13:04:40 2020.
No match for argument: qubes-template-centos-8
Error: Unable to find a match: qubes-template-centos-8
[xxx@dom0 ~]$ 
Any thoughts?

Cheers,

Ludwig

-- 
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/7faf5e90-b62c-4909-8b69-5a326b715c51n%40googlegroups.com.

[qubes-users] Dell T7500 and the hunt for the Intel ME Spy-Engine. // ME-Code not found in BIOS update. So where it is?

[ludwig...@gmail.com]

Hi all

If you want to play with the bios images, you can download them at 
dell dot com
with your service tag number of the box.
-
So to get the real romfile, the file that is written to the flash,
in order to do some research with it, call

wine T7500A18.exe /writeromfile

which will write  T7500A18.rom.
and wants you to click a message with OK-button.

So looking for intel-me code:
you might want to use:
https://github.com/corna/me_cleaner 


If you call

python me_cleaner.py T7500A18.rom
it says:

Unknown image

---
So there might still be me code me_cleaner does not know, or the bios
is ME_free.
--
Or is the bios update just a delta-update, and the ME-firmware is still 
there, not 
beeing modified.

--
I tried with A13 to A18 and me_cleaner did not find me_code, as it
reported "Unknown image".
---

Any thoughts where the ME-firmware could be hidden, or to make sure,
that the T7500 is really ME-free, as it seems to be?

-- 
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/700c8d05-8e15-4e68-bf65-5248a61d0a63n%40googlegroups.com.

[qubes-users] Re: HCL - Intel NUC10i7FNK

[zhao...@gmail.com]

I've tried booting the NUC10 in UEFI mode ,then it worked!

在2020年4月14日星期二 UTC+8 上午2:07:16 写道：

> Hi everyone,
>
> NUC's are promising. 64GB memory with 1TB NVMe is acceptable for a Qubes 
> installation and takes up zero space.
>
> Got 800x600 with the 4.19 kernel. no wifi. Upgraded kernel to 5.5.13-1 and 
> got my 4K monitor working. no wifi. wifi device flapping for a few minutes, 
> then stop. Hoping for some upgrades at some point.
>
> Runs current-testing repo.
>
> Sincerely
>
> Max
>

-- 
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/d95647c8-27f4-46a2-bb0f-8fd23e5305c5n%40googlegroups.com.

[qubes-users] Re: HCL - intel NUC10i7FNK

[zhao...@gmail.com]

Thanks a lot!
I  tried just as you mentioned. Now it's working!
The problem was that I didnot use "UEFI" booting mode.
Thanks again!

在2020年7月27日星期一 UTC+8 上午12:47:02 写道：

> [Note: sorry for not replying directly to the original thread, but I 
> wasn't yet registered to the mailing-list, so I can't do a reply with my 
> MUA]
>
> Original copy-paste mail from zhaojx88  (see : 
> https://groups.google.com/d/msg/qubes-users/vRKrs5ZIg9c/WUepmWP9BwAJ):
>
> > Thanks for the guidance!
> > I also have nuc 10i7fnk. but I have problems installing qubes OS 
> 4.0.  I hope I can get answers from you.
> > I Set legecy mode, security booting off, use USB stick to install OS.
> > The following warning maseges&error is displayed when booting.
> > "WARN anaconda: 
> /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
>  
>
> add_option is deprecated and will be removed in
>
> > pykickstart-3.  Use add_argument instead.
> >op.add.option("--minlen",type="int")
> > ..
> > WARN anaconda.stdout:Not asking for VNC because we don't have a network
> > ..
> > WARN anaconda:X startup failed: Xorg exited with status 1
> > WARN anaconda.stdout:X startup failed,aborting installation
> > ERR anaconda.stdout:X startup failed, aboting installation"
> >
> > Do I miss setting something in bios or do I need to install the OS 
> with DVD?
> > Thanks a lot!
>
> zhaojx88,
>
> you got a *network error*, so may be, you should follow my steps 
> with a USB Network Interface Controller (aka USB ethernet), because the 
> internal ethernet card isn't recognized by the default 4.9 linux kernel.
>
> My BIOS setting:
>
> Boot (section)
>
>   Secure BootDisabled
>
>   UEFI BootEnabled
>
>   Legacy BootEnabled
>
>   > Secure Boot (sub-section)
>
> System ModeUser
>
> Secure Boot  Disabled
>
> Not Active (title)
>
> Secure Boot Mode   Standard
>
>   > Boot Priority
>
> UEFI Boot   x (i.e. checked)
>
> Legacy Boot   x (i.e. checked)
>
> USBx (i.e. checked)
>
> I used the 4.0.3 ISO from https://www.qubes-os.org/downloads/  on a 
> USB storage stick. On boot I used the F10 key for choosing the *UEFI* 
> USB device stick. And I installed Qubes-OS on my SSD with the help of 
> the Qubes-OS documentation.
>
> Note also than my first 4GB USB stick was too small for the iso, 
> finally I used a 32GB stick (but 8GB will be fine).
>
> If this doesn't resolve your problem, give more information (BIOS 
> screenshots, when you got the above error message, ...)
>
> -- 
>
> Ludovic
>
>

-- 
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/5526756b-14b3-4f51-b9b8-bb18246f2e9cn%40googlegroups.com.

[qubes-users] Re: wired problems with 4 screens and 2 graphics boards: ps/2 mouse and kbd lock up, machine still running, but not usable.

[ludwig jaffe]

On Sunday, July 19, 2020 at 5:39:14 PM UTC, ludwig jaffe wrote:
>
> wired problems with 4 screens and 2 graphics boards: ps/2 mouse and kbd 
> lock up, machine still running, but not usable.
>
>
> I have this machine:
>
>  qubes-hcl-report 
> Qubes release 4.0 (R4.0)
>
> Brand:Dell Inc.
> Model:Precision WorkStation T7500  
> BIOS:A17
>
> Xen:4.8.5-19.fc25
> Kernel:4.19.128-1
>
> RAM:98301 Mb
>
> CPU:
>   Intel(R) Xeon(R) CPU   L5638  @ 2.00GHz
> Chipset:
>   Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22)
> VGA:
>   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 7350/8350 / R5 
> 220] [1002:68fa] (prog-if 00 [VGA controller])
>   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 7350/8350 / R5 
> 220] [1002:68fa] (prog-if 00 [VGA controller])
>
> Net:
>   Intel Corporation 82546EB Gigabit Ethernet Controller (rev 01)
>   Intel Corporation 82546EB Gigabit Ethernet Controller (rev 01)
>   Intel Corporation 82546EB Gigabit Ethernet Controller (rev 01)
>   Intel Corporation 82546EB Gigabit Ethernet Controller (rev 01)
>   Broadcom Limited NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)
>
> SCSI:
>   Samsung SSD 860  Rev: 1B6Q
>   DVD+-RW DH-16ABS Rev: PD11
>
> HVM:Active
> I/O MMU:Active
> HAP/SLAT:Yes
> TPM:Device present
> Remapping:yes
>
> Qubes HCL Files are copied to: 'dom0'
> 
> Qubes-HCL-Dell_Inc_-Precision_WorkStation_T7500__-20200719-172829.yml- 
> HCL Info
>
> ///
> lspci
> 00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22)
> 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
> Root Port 1 (rev 22)
> 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
> Root Port 3 (rev 22)
> 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
> Root Port 7 (rev 22)
> 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System 
> Management Registers (rev 22)
> 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch 
> Pad Registers (rev 22)
> 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status 
> and RAS Registers (rev 22)
> 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
> Controller #4
> 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
> Controller #5
> 00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
> Controller #6
> 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI 
> Controller #2
> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio 
> Controller
> 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express 
> Root Port 1
> 00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express 
> Root Port 6
> 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
> Controller #1
> 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
> Controller #2
> 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
> Controller #3
> 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI 
> Controller #1
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
> 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface 
> Controller
> 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA 
> AHCI Controller
> 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
> 01:00.0 PCI bridge: Pericom Semiconductor PCI Express to PCI-XPI7C9X130 
> PCI-X Bridge (rev 04)
> 02:00.0 PCI bridge: IBM PCI-X to PCI-X Bridge (rev 02)
> 03:04.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (rev 01)
> 03:04.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (rev 01)
> 03:06.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (rev 01)
> 03:06.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (rev 01)
> 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> Cedar [Radeon HD 7350/8350 / R5 220]
> 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI 
> Audio [Radeon HD 5400/6300/7300 Series]
> 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> Cedar [Radeon HD 7350/8350 / R5 220]
> 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI 
> Audio [Radeon HD 5400/6300/7300 Series]
> 06:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E 
> PCI-Express Fusion-MPT SAS (rev 08)
> 07:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5761 Gigabit 
> Ethernet PCIe (rev 10)
> 08:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 
> Controller (PHY/Link) [iOHCI-Lynx]
> 20:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
> Root Port 3 (rev 22)
> 20:07.0 PCI bridge: Intel C