[qubes-users] HCL - Dell_Inc_-XPS_17_9700

[Rama Mcintosh]

4.0.4 or 4.0.4rc1 would not install (tried all the workarounds).   4.1
alpha installed no problems, no special boot options it just worked.

Upgraded to kernel latest, which fixed bluetooth and some performance.
Needed to give sys-usb more RAM to function properly (otherwise
keyboard/mouse would lag when started usb network).

I built a custom kernel for latest intel sound drivers and Qualcomm wifi6
(linux-kernel.patch attached).

Works:
Everything except wifi works.
Touchscreen sort of works (acts like a tablet input)
Bluetooth works.
Audio works (with kernel 5.10 and attached kernel base-config patch  +
latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin and
alsa-ucm-config files.   see
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
for alsa ucm config ).

Does not work:
Qualcomm AX500 wifi.   I have the latest firmware and it works fine on bare
metal fedora 33.   However, with Qubes, the xen pci passthrough is not
working.   Here is the error from the sys-net qube dmesg:
[5.706045] ath11k_pci :00:06.0: WARNING: ath11k PCI support is
experimental!
[5.706448] ath11k_pci :00:06.0: BAR 0: assigned [mem
0xf200-0xf20f 64bit]
[5.734248] ath11k_pci :00:06.0: failed to get 32 MSI vectors, only
-28 available
[5.734289] ath11k_pci :00:06.0: failed to enable msi: -28
[5.736589] ath11k_pci: probe of :00:06.0 failed with error -28
I have tried permissive, no reset etc.   I even tried the latest ath11k
driver from the 5.11 kernel but no luck getting it to work with xen pci
passthrough.

There is a TPM 2.0 module which the kernel appears to see but HCL report
doesn't?

-- 
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/CAPVWjyO_0fxhztK2kV4qXS1T357LaLq5vFu_dB%2B%2B94OkeXyw0A%40mail.gmail.com.


Qubes-HCL-Dell_Inc_-XPS_17_9700-20210109-183429.yml
Description: application/yaml
diff --git a/config-base b/config-base
index 4d48c83..1c0e7f4 100644
--- a/config-base
+++ b/config-base
@@ -3327,6 +3327,13 @@ CONFIG_ATH10K_DEBUGFS=y
 # CONFIG_ATH10K_TRACING is not set
 CONFIG_WCN36XX=m
 # CONFIG_WCN36XX_DEBUGFS is not set
+CONFIG_ATH11K=m
+CONFIG_ATH11K_AHB=m
+CONFIG_ATH11K_PCI=m
+# CONFIG_ATH11K_DEBUG=y
+# CONFIG_ATH11K_DEBUGFS=y
+CONFIG_ATH11K_TRACING=y
+CONFIG_ATH11K_SPECTRAL=y
 # CONFIG_WLAN_VENDOR_ATMEL is not set
 CONFIG_WLAN_VENDOR_BROADCOM=y
 CONFIG_B43=m
@@ -6094,6 +6101,7 @@ CONFIG_SND_SOC_INTEL_SST_ACPI=m
 CONFIG_SND_SOC_INTEL_SST=m
 CONFIG_SND_SOC_INTEL_SST_FIRMWARE=m
 CONFIG_SND_SOC_INTEL_HASWELL=m
+CONFIG_SND_SOC_INTEL_CATPT=m
 CONFIG_SND_SST_ATOM_HIFI2_PLATFORM=m
 CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_PCI=m
 CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI=m
@@ -6149,6 +6157,7 @@ CONFIG_SND_SOC_INTEL_CML_LP_DA7219_MAX98357A_MACH=m
 CONFIG_SND_SOC_INTEL_SOF_CML_RT1011_RT5682_MACH=m
 CONFIG_SND_SOC_INTEL_SOF_DA7219_MAX98373_MACH=m
 CONFIG_SND_SOC_INTEL_EHL_RT5660_MACH=m
+CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
 # CONFIG_SND_SOC_MTK_BTCVSD is not set
 CONFIG_SND_SOC_SOF_TOPLEVEL=y
 CONFIG_SND_SOC_SOF_PCI=m
@@ -6189,6 +6198,9 @@ CONFIG_SND_SOC_SOF_HDA_AUDIO_CODEC=y
 # CONFIG_SND_SOC_SOF_HDA_ALWAYS_ENABLE_DMI_L1 is not set
 CONFIG_SND_SOC_SOF_HDA_LINK_BASELINE=m
 CONFIG_SND_SOC_SOF_HDA=m
+CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK=y
+CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK_BASELINE=m
+CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE=m
 CONFIG_SND_SOC_SOF_XTENSA=m
 
 #
@@ -6312,9 +6324,12 @@ CONFIG_SND_SOC_RT5677_SPI=m
 CONFIG_SND_SOC_RT5682=m
 CONFIG_SND_SOC_RT5682_I2C=m
 CONFIG_SND_SOC_RT5682_SDW=m
-# CONFIG_SND_SOC_RT700_SDW is not set
-# CONFIG_SND_SOC_RT711_SDW is not set
-# CONFIG_SND_SOC_RT715_SDW is not set
+CONFIG_SND_SOC_RT700=m
+CONFIG_SND_SOC_RT700_SDW=m
+CONFIG_SND_SOC_RT711=m
+CONFIG_SND_SOC_RT711_SDW=m
+CONFIG_SND_SOC_RT715=m
+CONFIG_SND_SOC_RT715_SDW=m
 # CONFIG_SND_SOC_SGTL5000 is not set
 CONFIG_SND_SOC_SIGMADSP=m
 CONFIG_SND_SOC_SIGMADSP_REGMAP=m
@@ -7536,6 +7551,7 @@ CONFIG_SOUNDWIRE=y
 #
 CONFIG_SOUNDWIRE_CADENCE=m
 CONFIG_SOUNDWIRE_INTEL=m
+CONFIG_SOUNDWIRE_GENERIC_ALLOCATION=m
 
 #
 # SOC (System On Chip) specific Drivers
diff --git a/kernel.spec.in b/kernel.spec.in
index 4bab885..ce32014 100644
--- a/kernel.spec.in
+++ b/kernel.spec.in
@@ -15,7 +15,7 @@
 %define rel %{plainrel}.%{variant}
 %endif
 
-%define name_suffix -latest
+%define name_suffix -face
 
 %define _buildshell /bin/bash
 %define build_xen   1
diff --git a/rel b/rel
index d00491f..7f8f011 100644
--- a/rel
+++ b/rel
@@ -1 +1 @@
-1
+7

[qubes-users] Boot hold after update

['A E' via qubes-users]

I've been trying to install Qubes on an external hard drive to test it 
out but I've ran into an issue. I've followed this guide 
 
since it's the same laptop I have (System76 Darter Pro).


I changed out the wifi card and was able to run the updates in dom0:

sudo qubes-dom0-update kernel-latest

sudo qubes-dom0-update kernel-latest-qubes-vm

After each update, I restart my computer and then set the new kernel to 
current (5.9.14-1 in both the kernel and vm). However, after I update 
the vm I'm prompted for another update to dom0 and the whonix gateway 
template. I run those, and restart my computer and that's where I run 
into problems.


I'm prompted to input my decryption password in a GUI that's showing a 
progress bar for the boot process, and then it takes me out of the GUI 
into a "Started Accounts Services" list and continues to try and boot 
until it says "Starting Hold until boot proce
ss finishes up..." and it 
will just sit there for as long as I'll let it. I'm unable to 
Ctrl+Alt+F2 or Ctrl+Alt+F1 into a terminal or GUI, or interact with it 
in any way (no cursor, typing, etc.). Reboots don't fix it.


I tried a fresh install after the first time this happened and followed 
the same steps, and the same thing happened. I tried searching but 
couldn't find anything to try. Any help is greatly appreciated!


--
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/9cefcf3d-de68-d465-8add-3dabcd320065%40protonmail.com.


publickey - alternate_empire@protonmail.com - 49e70c72.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Qubes boots to grey screen, mouse frozen

[TheCrispyToast]

On Sunday, January 10, 2021 at 12:18:54 AM UTC awokd wrote:

> This seems like it could be a hardware or disk corruption issue. Try 
> hitting ctrl-alt-F5 to switch to a text terminal when you are at the 
> grey screen. Should hopefully be able to login there and pull logs. If 
> your disk was close to filling up, that could point more towards drive 
> corruption. 
>
> My disk was definitley not close to filling up, but it may have been one 
of the VM partitions that was close to filling up. I have managed to get 
into the dom0 terminal upon bootup. Excuse my ignorance, but could you 
asssit with the proper commands for pulling logs and/or turning certain VMs 
off from startup? I think itd be better to start a boot with only dom0 
running. As I said before, sometimes it will let me even get logged in and 
then once whonix appears to start the whole system freezes.

-- 
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/f35b548c-15fa-44e1-953e-909dfebb9ed4n%40googlegroups.com.

Re: [qubes-users] How do you think about the clipboard inter-VMs

['awokd' via qubes-users]

pillule:


Hello,

I wonder how do you manage your computing life with the problem of the 
clipboard / file sharing.


For example, the seemingly-innocent link that we 
copy from an untrusted qube could turn out to be a large buffer of junk 
that, when pasted into the target qube’s word processor, could exploit a 
hypothetical bug in the undo buffer.


Qubes does show the number of bytes copied to the buffer when you 
perform a shift-ctrl-c. If this is the same as the (small) number of 
characters you are copying, chances of a successful attack fitting in 20 
bytes or whatever is pretty slim. File sharing is a different matter, 
can address somewhat by keeping your archive VM not network connected.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/f29928d9-7057-b2c5-3fc7-efd43ea3b1d4%40danwin1210.me.

Re: [qubes-users] Qubes boots to grey screen, mouse frozen

['awokd' via qubes-users]

TheCrispyToast:


Aloha generous qubes-users group. I've been getting used to qubes for the
past 6months or so and have found lots of helpful conversations in this
group. Have had no problems with my thinkpad T580.

The issues arose when I first tried to update with the GUI. Fedora and
qubes itself updated just fine but whonix came back with a failed update. I
shutdown laptop and tried again. When I tried updating whonix that go
around, the computer froze, i let it sit for 10minutes and then did a hard
shutdown. After reboot, it will let me now put my password and disk pw in,
but then boots to a grey screen and a frozen mouse. I would suspect from
the attempt at starting the whonix VM.

Two questions:
1. How do I enable debugging or logs so I can bring them here?
2. Can I enable some sort of advanced startup options? Disable the startup
of specific VMs?

This seems like it could be a hardware or disk corruption issue. Try 
hitting ctrl-alt-F5 to switch to a text terminal when you are at the 
grey screen. Should hopefully be able to login there and pull logs. If 
your disk was close to filling up, that could point more towards drive 
corruption.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/5464481e-26d7-d2b1-acb5-7147107c033b%40danwin1210.me.