Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread Rama McIntosh 
I think your dell has different wifi and I think audio.   The wifi driver
for the xps 9310 is iwlwifi.   Here is some firmware info:
https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
and here is some qubes specific info on your wifi driver:
https://github.com/QubesOS/qubes-issues/issues/5615

I think the audio is different too, as the xps 9700 needs the 5.10 kernel
to work, but the base-config patch above does enable
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.

To patch the kernel you must build it from source with qubes-builder
https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  Then
change kernel to master branch in builer.conf.after the "make
get-sources"  is when you would patch with config-base in
qubes-builder/qubes-src/linux-kernel.

fedora 33 5.10 kernel supports much more devices and audio works in the
upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a
patch into qubes the upstream kernel modules which fedora has added or at
the minimum the SOF stuff in the patch.   Then all our audio will just work
with qubes.





On Sat, Feb 6, 2021 at 11:34 AM Fabrizio Romano Genovese <
fabri...@statebox.io> wrote:

>
> I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
> was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
> have both wifi and sound not working :D
>
> It seems that the sound issues are due to a problem with driver
> sof-audio-pci.
> In this thread: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it
> turns out another user was having a similar problem with a dell 9700, which
> was apparently solved. Indeed in the thread it is said:
>
> 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 ).
>
> Unfortunately, I am not technically skilled enough to really understand
> the fix. Does it mean that I have to download kernel 5.10 (from were?),
> apply the patch provided in the thread (how?), include firmware and config
> files (how?) and then compile and install?
> As you can see I don't really have a specific question, and I'm more in
> search of a few clarifications to understand how to apply an apparently
> already available solution. :)
>
> Fab
>
> --
> 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/5bde992b-ea73-499f-bcd1-38a0a2f0028fn%40googlegroups.com
> 
> .
>


-- 
http://myutil.com

-- 
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/CAPVWjyMc-1iZoJ0GfJv%2B0fohDOUVk4dXe5Yp%3D15b%3Duy%3DFgH2og%40mail.gmail.com.

[qubes-users] HCL - Dell_Inc_-XPS_17_9700

2021-01-09 Thread 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