No Audio out through Internal Speakers for OneXPlayer2 Pro

The driver says Family 17/19 HD Audio Controller Pro
Wired headphones and bluetooth speakers work but no audio out through internal speakers

It's possible this device uses an amplifier. It's likely we'll need a device in hand to add functionality.

Is there anything i can do to help you guys test it/fix it?
Please let me know. Thanks!

Is there anything i can do to help you guys test it/fix it? Please let me know. Thanks!

Can you get me an alsa dump? You'll need to unlock the filesystem and install some packages.
sudo frzr-unlock
sudo pacman -S alsa-tools tree
/usr/bin/alsa-info.sh

Here it is:
http://alsa-project.org/db/?f=280c56830a60868346995b41309f663c5fe7510b
Thanks for looking into this.

Here it is: http://alsa-project.org/db/?f=280c56830a60868346995b41309f663c5fe7510b
Thanks for looking into this.

Thanks for the info. Any chance I could get a dmesg as well?
sudo dmesg > oxp2pro-dmesg.log

Ofcourse.
oxp2pro-dmesg.log
Please let me know anything you need.

Ofcourse. oxp2pro-dmesg.log
Please let me know anything you need.

Thanks! It looks like we might need a dump from Windows to verify the pins and verbs.
Are you able to boot Windows with audio drivers installed and working and run this utility?
RtHDDump_V236.zip

Here it is:
RtHDDump.txt

Here it is: RtHDDump.txt
Here's one with scan all PCI devices selected
RtHDDump w PCI Scan.txt

Thanks. I think I got the information I need. I'll need to make a kernel patch for you to try. It's late here now ATM so I'll start working on this tomorrow.

That's amazing!! Thank you so much 🙏😊.

Here we go. I have a patch for you to try. Are you able to build the kernel with a patch on your own or would you like me to compile it?
oxp2-pro-audio-patch-test-patch.txt
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 44fccfb93cff..a4858a6409af 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -6501,6 +6501,23 @@ static void alc295_fixup_chromebook(struct hda_codec *codec,
 	}
 }

+static void alc245_fixup_oxp2pro_pins(struct hda_codec *codec,
+				     const struct hda_fixup *fix,
+				     int action)
+{
+	static const hda_nid_t conn1[] = { 0x02 };
+	static const hda_nid_t conn2[] = { 0x03 };
+
+	if (action != HDA_FIXUP_ACT_PRE_PROBE)
+		return;
+
+	/* It appears as though the OXP2 Pro has 0x17 connected to 0x02
+	 * and 0x21 connected to 0x03 on Windows
+	 */
+	snd_hda_override_conn_list(codec, 0x17, ARRAY_SIZE(conn1), conn1);
+	snd_hda_override_conn_list(codec, 0x21, ARRAY_SIZE(conn2), conn2);
+}
+
 static void alc_fixup_disable_mic_vref(struct hda_codec *codec,
 				  const struct hda_fixup *fix, int action)
 {
@@ -7219,6 +7236,7 @@ enum {
 	ALC287_FIXUP_LEGION_16ACHG6,
 	ALC287_FIXUP_CS35L41_I2C_2,
 	ALC287_FIXUP_CS35L41_I2C_2_HP_GPIO_LED,
+	ALC245_FIXUP_OXP2PRO,
 	ALC245_FIXUP_CS35L41_SPI_2,
 	ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED,
 	ALC245_FIXUP_CS35L41_SPI_4,
@@ -7580,6 +7598,10 @@ static const struct hda_fixup alc269_fixups[] = {
 		.type = HDA_FIXUP_FUNC,
 		.v.func = alc269_fixup_x101_headset_mic,
 	},
+	[ALC245_FIXUP_OXP2PRO] = {
+		.type = HDA_FIXUP_FUNC,
+		.v.func = alc245_fixup_oxp2pro_pin,
+	},
 	[ALC269_FIXUP_ASUS_X101_VERB] = {
 		.type = HDA_FIXUP_VERBS,
 		.v.verbs = (const struct hda_verb[]) {
@@ -9934,6 +9956,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
 	SND_PCI_QUIRK(0x1d72, 0x1901, "RedmiBook 14", ALC256_FIXUP_ASUS_HEADSET_MIC),
 	SND_PCI_QUIRK(0x1d72, 0x1945, "Redmi G", ALC256_FIXUP_ASUS_HEADSET_MIC),
 	SND_PCI_QUIRK(0x1d72, 0x1947, "RedmiBook Air", ALC255_FIXUP_XIAOMI_HEADSET_MIC),
+	SND_PCI_QUIRK(0x1f75, 0x1602, "ONEXPLAYER 2 PRO ARP23P", ALC245_FIXUP_OXP2PRO),
 	SND_PCI_QUIRK(0x8086, 0x2074, "Intel NUC 8", ALC233_FIXUP_INTEL_NUC8_DMIC),
 	SND_PCI_QUIRK(0x8086, 0x2080, "Intel NUC 8 Rugged", ALC256_FIXUP_INTEL_NUC8_RUGGED),
 	SND_PCI_QUIRK(0x8086, 0x2081, "Intel NUC 10", ALC256_FIXUP_INTEL_NUC10),

Thank you so much!
Unfortunately, I do not know how to build a kernel with the patch.
If you can send me the instructions, I can try it out.
If its easier for you to build the patch than telling me how, that would be great too.
Anything works.

Thank you so much!
Unfortunately, I do not know how to build a kernel with the patch. If you can send me the instructions, I can try it out. If its easier for you to build the patch than telling me how, that would be great too. Anything works.
EDIT: I think I figured out how to build the kernel with makepkg. I will try it out.

I have it building on my end as well just in case.

I am getting this error after adding this patch
==> Starting prepare()...
Setting version...
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  LEX     scripts/kconfig/lexer.lex.c
  YACC    scripts/kconfig/parser.tab.[ch]
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/menu.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
*** Default configuration is based on 'x86_64_defconfig'
#
# configuration written to .config
#
  CLEAN   scripts/basic
  CLEAN   scripts/kconfig
  CLEAN   include/config include/generated .config
Applying patch 0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch...
patching file include/linux/user_namespace.h
patching file init/Kconfig
patching file kernel/fork.c
patching file kernel/sysctl.c
patching file kernel/user_namespace.c
Applying patch 0002-drivers-firmware-skip-simpledrm-if-nvidia-drm.modese.patch...
patching file drivers/firmware/sysfb.c
Applying patch 0003-tpm-dont-make-vendor-check-required-for-probe.patch...
Applying patch 0001-mm-Support-soft-dirty-flag-reset-for-VA-range.patch...
patching file fs/proc/task_mmu.c
Hunk #1 succeeded at 1079 (offset 47 lines).
Hunk #2 succeeded at 1172 (offset 45 lines).
Hunk #3 succeeded at 1230 (offset 45 lines).
Hunk #4 succeeded at 1257 (offset 45 lines).
Hunk #5 succeeded at 1271 (offset 45 lines).
Hunk #6 succeeded at 1311 (offset 46 lines).
Hunk #7 succeeded at 1422 (offset 45 lines).
Hunk #8 succeeded at 1497 (offset 47 lines).
Hunk #9 succeeded at 1563 (offset -14 lines).
Hunk #10 succeeded at 1587 (offset 68 lines).
Applying patch 0001-drm-panel-orientation-quirks-Add-quirk-for-AYA-NEO-2.patch...
patching file drivers/gpu/drm/drm_panel_orientation_quirks.c
Applying patch 0002-drm-panel-orientation-quirks-Add-quirk-for-AYA-NEO-F.patch...
patching file drivers/gpu/drm/drm_panel_orientation_quirks.c
Applying patch 0003-drm-panel-orientation-quirks-Add-quirk-for-AYA-NEO-G.patch...
patching file drivers/gpu/drm/drm_panel_orientation_quirks.c
Applying patch 0003-asus-ally-asus-hid-6.3-v2.patch...
patching file drivers/hid/hid-asus.c
Hunk #1 succeeded at 911 (offset 1 line).
Hunk #2 succeeded at 1278 (offset 1 line).
patching file drivers/hid/hid-ids.h
Applying patch 0001-hwmon-oxp-sensors-staged-changes-for-v6.5.patch...
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
Applying patch 0001-Cirrus-no-dsdt.patch...
patching file sound/pci/hda/Makefile
Hunk #1 succeeded at 28 with fuzz 1.
patching file sound/pci/hda/cs35l41_hda.c
Hunk #2 succeeded at 1161 (offset -155 lines).
Hunk #3 succeeded at 1215 (offset -155 lines).
Hunk #4 succeeded at 1240 (offset -155 lines).
Hunk #5 succeeded at 1340 (offset -155 lines).
patching file sound/pci/hda/cs35l41_hda.h
patching file sound/pci/hda/cs35l41_hda_property.c
patching file sound/pci/hda/cs35l41_hda_property.h
Applying patch 0001-ALSA-hda-cs35l41-Support-ASUS-2023-laptops-with-miss.patch...
patching file sound/pci/hda/cs35l41_hda_property.c
Applying patch 0001-ayaneo-geek-headset-fix.patch...
patching file sound/pci/hda/patch_realtek.c
Hunk #2 succeeded at 7028 (offset -3 lines).
Hunk #3 succeeded at 8452 (offset -3 lines).
Hunk #4 succeeded at 9948 (offset -3 lines).
Applying patch 0002-ayaneo-2-headphone-fix.patch...
patching file sound/pci/hda/patch_realtek.c
Hunk #1 succeeded at 7028 (offset -3 lines).
Hunk #2 succeeded at 8453 (offset -3 lines).
Hunk #3 succeeded at 9953 (offset -3 lines).
Applying patch 0001-GPU-reset.patch...
patching file drivers/gpu/drm/drm_sysfs.c
Hunk #1 succeeded at 435 (offset 1 line).
patching file include/drm/drm_sysfs.h
patching file drivers/gpu/drm/amd/amdgpu/amdgpu.h
Hunk #1 succeeded at 58 (offset -2 lines).
Hunk #2 succeeded at 993 (offset -10 lines).
Hunk #3 succeeded at 1026 (offset -11 lines).
patching file drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
Hunk #1 succeeded at 80 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 3465 (offset 109 lines).
Hunk #3 succeeded at 3728 (offset 110 lines).
patching file drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
Hunk #1 succeeded at 5065 (offset 141 lines).
Applying patch 0001-ALSA-cs35l41-Use-mbox-command-to-enable-speaker-outp.patch...
patching file include/sound/cs35l41.h
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 515 (offset 1 line).
Hunk #2 succeeded at 675 (offset 1 line).
patching file sound/soc/codecs/cs35l41-lib.c
patching file sound/soc/codecs/cs35l41.c
Applying patch 0002-ALSA-cs35l41-Poll-for-Power-Up-Down-rather-than-wait.patch...
patching file sound/soc/codecs/cs35l41-lib.c
patching file sound/soc/codecs/cs35l41.c
Applying patch 0003-ALSA-hda-cs35l41-Check-mailbox-status-of-pause-comma.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 782 (offset 1 line).
Applying patch 0004-ALSA-hda-cs35l41-Ensure-we-correctly-re-sync-regmap-.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 575 (offset 1 line).
Applying patch 0005-ALSA-hda-cs35l41-Ensure-we-pass-up-any-errors-during.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 627 (offset 1 line).
Hunk #2 succeeded at 665 (offset 1 line).
Applying patch 0006-ALSA-hda-cs35l41-Move-Play-and-Pause-into-separate-f.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 484 (offset 1 line).
Hunk #2 succeeded at 590 (offset 1 line).
Hunk #3 succeeded at 741 (offset 1 line).
Applying patch 0007-ALSA-hda-hda_component-Add-pre-and-post-playback-hoo.patch...
patching file sound/pci/hda/hda_component.h
patching file sound/pci/hda/patch_realtek.c
Hunk #1 succeeded at 6730 (offset 14 lines).
Applying patch 0008-ALSA-hda-cs35l41-Use-pre-and-post-playback-hooks.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 557 (offset 1 line).
Hunk #2 succeeded at 1073 (offset 5 lines).
Applying patch 0009-ALSA-hda-cs35l41-Rework-System-Suspend-to-ensure-cor.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 596 (offset 1 line).
Hunk #2 succeeded at 691 (offset 1 line).
Hunk #3 succeeded at 722 (offset 1 line).
Hunk #4 succeeded at 772 (offset 1 line).
Hunk #5 succeeded at 805 (offset 1 line).
Hunk #6 succeeded at 1639 (offset -31 lines).
Applying patch 0010-ALSA-hda-cs35l41-Add-device_link-between-HDA-and-cs3.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 1068 (offset 5 lines).
Hunk #2 succeeded at 1108 (offset 5 lines).
Hunk #3 succeeded at 1123 (offset 5 lines).
Applying patch 0011-ALSA-hda-cs35l41-Ensure-amp-is-only-unmuted-during-p.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 59 (offset 1 line).
Hunk #2 succeeded at 81 (offset 1 line).
Hunk #3 succeeded at 529 (offset 1 line).
Hunk #4 succeeded at 1598 (offset -31 lines).
Applying patch oxp2-pro-audio-patch-test-patch.patch...
patching file sound/pci/hda/patch_realtek.c
Hunk #2 succeeded at 7257 (offset 21 lines).
Hunk #3 succeeded at 7619 (offset 21 lines).
Hunk #4 FAILED at 9956.
1 out of 4 hunks FAILED -- saving rejects to file sound/pci/hda/patch_realtek.c.rej
==> ERROR: A failure occurred in prepare().
    Aborting...

I am getting this error after adding this patch
==> Starting prepare()...
Setting version...
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  LEX     scripts/kconfig/lexer.lex.c
  YACC    scripts/kconfig/parser.tab.[ch]
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/menu.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
*** Default configuration is based on 'x86_64_defconfig'
#
# configuration written to .config
#
  CLEAN   scripts/basic
  CLEAN   scripts/kconfig
  CLEAN   include/config include/generated .config
Applying patch 0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch...
patching file include/linux/user_namespace.h
patching file init/Kconfig
patching file kernel/fork.c
patching file kernel/sysctl.c
patching file kernel/user_namespace.c
Applying patch 0002-drivers-firmware-skip-simpledrm-if-nvidia-drm.modese.patch...
patching file drivers/firmware/sysfb.c
Applying patch 0003-tpm-dont-make-vendor-check-required-for-probe.patch...
Applying patch 0001-mm-Support-soft-dirty-flag-reset-for-VA-range.patch...
patching file fs/proc/task_mmu.c
Hunk #1 succeeded at 1079 (offset 47 lines).
Hunk #2 succeeded at 1172 (offset 45 lines).
Hunk #3 succeeded at 1230 (offset 45 lines).
Hunk #4 succeeded at 1257 (offset 45 lines).
Hunk #5 succeeded at 1271 (offset 45 lines).
Hunk #6 succeeded at 1311 (offset 46 lines).
Hunk #7 succeeded at 1422 (offset 45 lines).
Hunk #8 succeeded at 1497 (offset 47 lines).
Hunk #9 succeeded at 1563 (offset -14 lines).
Hunk #10 succeeded at 1587 (offset 68 lines).
Applying patch 0001-drm-panel-orientation-quirks-Add-quirk-for-AYA-NEO-2.patch...
patching file drivers/gpu/drm/drm_panel_orientation_quirks.c
Applying patch 0002-drm-panel-orientation-quirks-Add-quirk-for-AYA-NEO-F.patch...
patching file drivers/gpu/drm/drm_panel_orientation_quirks.c
Applying patch 0003-drm-panel-orientation-quirks-Add-quirk-for-AYA-NEO-G.patch...
patching file drivers/gpu/drm/drm_panel_orientation_quirks.c
Applying patch 0003-asus-ally-asus-hid-6.3-v2.patch...
patching file drivers/hid/hid-asus.c
Hunk #1 succeeded at 911 (offset 1 line).
Hunk #2 succeeded at 1278 (offset 1 line).
patching file drivers/hid/hid-ids.h
Applying patch 0001-hwmon-oxp-sensors-staged-changes-for-v6.5.patch...
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
patching file drivers/hwmon/oxp-sensors.c
Applying patch 0001-Cirrus-no-dsdt.patch...
patching file sound/pci/hda/Makefile
Hunk #1 succeeded at 28 with fuzz 1.
patching file sound/pci/hda/cs35l41_hda.c
Hunk #2 succeeded at 1161 (offset -155 lines).
Hunk #3 succeeded at 1215 (offset -155 lines).
Hunk #4 succeeded at 1240 (offset -155 lines).
Hunk #5 succeeded at 1340 (offset -155 lines).
patching file sound/pci/hda/cs35l41_hda.h
patching file sound/pci/hda/cs35l41_hda_property.c
patching file sound/pci/hda/cs35l41_hda_property.h
Applying patch 0001-ALSA-hda-cs35l41-Support-ASUS-2023-laptops-with-miss.patch...
patching file sound/pci/hda/cs35l41_hda_property.c
Applying patch 0001-ayaneo-geek-headset-fix.patch...
patching file sound/pci/hda/patch_realtek.c
Hunk #2 succeeded at 7028 (offset -3 lines).
Hunk #3 succeeded at 8452 (offset -3 lines).
Hunk #4 succeeded at 9948 (offset -3 lines).
Applying patch 0002-ayaneo-2-headphone-fix.patch...
patching file sound/pci/hda/patch_realtek.c
Hunk #1 succeeded at 7028 (offset -3 lines).
Hunk #2 succeeded at 8453 (offset -3 lines).
Hunk #3 succeeded at 9953 (offset -3 lines).
Applying patch 0001-GPU-reset.patch...
patching file drivers/gpu/drm/drm_sysfs.c
Hunk #1 succeeded at 435 (offset 1 line).
patching file include/drm/drm_sysfs.h
patching file drivers/gpu/drm/amd/amdgpu/amdgpu.h
Hunk #1 succeeded at 58 (offset -2 lines).
Hunk #2 succeeded at 993 (offset -10 lines).
Hunk #3 succeeded at 1026 (offset -11 lines).
patching file drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
Hunk #1 succeeded at 80 with fuzz 2 (offset 4 lines).
Hunk #2 succeeded at 3465 (offset 109 lines).
Hunk #3 succeeded at 3728 (offset 110 lines).
patching file drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
Hunk #1 succeeded at 5065 (offset 141 lines).
Applying patch 0001-ALSA-cs35l41-Use-mbox-command-to-enable-speaker-outp.patch...
patching file include/sound/cs35l41.h
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 515 (offset 1 line).
Hunk #2 succeeded at 675 (offset 1 line).
patching file sound/soc/codecs/cs35l41-lib.c
patching file sound/soc/codecs/cs35l41.c
Applying patch 0002-ALSA-cs35l41-Poll-for-Power-Up-Down-rather-than-wait.patch...
patching file sound/soc/codecs/cs35l41-lib.c
patching file sound/soc/codecs/cs35l41.c
Applying patch 0003-ALSA-hda-cs35l41-Check-mailbox-status-of-pause-comma.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 782 (offset 1 line).
Applying patch 0004-ALSA-hda-cs35l41-Ensure-we-correctly-re-sync-regmap-.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 575 (offset 1 line).
Applying patch 0005-ALSA-hda-cs35l41-Ensure-we-pass-up-any-errors-during.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 627 (offset 1 line).
Hunk #2 succeeded at 665 (offset 1 line).
Applying patch 0006-ALSA-hda-cs35l41-Move-Play-and-Pause-into-separate-f.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 484 (offset 1 line).
Hunk #2 succeeded at 590 (offset 1 line).
Hunk #3 succeeded at 741 (offset 1 line).
Applying patch 0007-ALSA-hda-hda_component-Add-pre-and-post-playback-hoo.patch...
patching file sound/pci/hda/hda_component.h
patching file sound/pci/hda/patch_realtek.c
Hunk #1 succeeded at 6730 (offset 14 lines).
Applying patch 0008-ALSA-hda-cs35l41-Use-pre-and-post-playback-hooks.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 557 (offset 1 line).
Hunk #2 succeeded at 1073 (offset 5 lines).
Applying patch 0009-ALSA-hda-cs35l41-Rework-System-Suspend-to-ensure-cor.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 596 (offset 1 line).
Hunk #2 succeeded at 691 (offset 1 line).
Hunk #3 succeeded at 722 (offset 1 line).
Hunk #4 succeeded at 772 (offset 1 line).
Hunk #5 succeeded at 805 (offset 1 line).
Hunk #6 succeeded at 1639 (offset -31 lines).
Applying patch 0010-ALSA-hda-cs35l41-Add-device_link-between-HDA-and-cs3.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 1068 (offset 5 lines).
Hunk #2 succeeded at 1108 (offset 5 lines).
Hunk #3 succeeded at 1123 (offset 5 lines).
Applying patch 0011-ALSA-hda-cs35l41-Ensure-amp-is-only-unmuted-during-p.patch...
patching file sound/pci/hda/cs35l41_hda.c
Hunk #1 succeeded at 59 (offset 1 line).
Hunk #2 succeeded at 81 (offset 1 line).
Hunk #3 succeeded at 529 (offset 1 line).
Hunk #4 succeeded at 1598 (offset -31 lines).
Applying patch oxp2-pro-audio-patch-test-patch.patch...
patching file sound/pci/hda/patch_realtek.c
Hunk #2 succeeded at 7257 (offset 21 lines).
Hunk #3 succeeded at 7619 (offset 21 lines).
Hunk #4 FAILED at 9956.
1 out of 4 hunks FAILED -- saving rejects to file sound/pci/hda/patch_realtek.c.rej
==> ERROR: A failure occurred in prepare().
    Aborting...

It's conflicting with another patch and I had a typo in the patch as well. I'll have a built kernel here in a bit.

Contributor

Thank you. I'll wait for the built kernel.

Contributor

Thank you. I'll wait for the built kernel.

Here you go!
https://drive.google.com/file/d/1iyWUxBoAq1UDs8EvEOBegndUGnGZsImN/view?usp=sharing
https://drive.google.com/file/d/1j1zJ91pk_B0IMbvcXJJ7BwFiN0o7UVMH/view?usp=sharing

Contributor

Thank you. I'll wait for the built kernel.

Here you go! https://drive.google.com/file/d/1iyWUxBoAq1UDs8EvEOBegndUGnGZsImN/view?usp=sharing https://drive.google.com/file/d/1j1zJ91pk_B0IMbvcXJJ7BwFiN0o7UVMH/view?usp=sharing

I installed both using
sudo pacman -U --noconfirm
and after reboot, almost everything stopped working. I don't have network, bluetooth, sound, etc.
Was this the wrong command?

Contributor

Thank you. I'll wait for the built kernel.

Here you go! https://drive.google.com/file/d/1iyWUxBoAq1UDs8EvEOBegndUGnGZsImN/view?usp=sharing https://drive.google.com/file/d/1j1zJ91pk_B0IMbvcXJJ7BwFiN0o7UVMH/view?usp=sharing

I installed both using sudo pacman -U --noconfirm
and after reboot, almost everything stopped working. I don't have network, bluetooth, sound, etc.
Was this the wrong command?

Did you have DKMS installed? Strangely enough I had this issue with a different kernel the other day myself.

Contributor

Thank you. I'll wait for the built kernel.

Here you go! https://drive.google.com/file/d/1iyWUxBoAq1UDs8EvEOBegndUGnGZsImN/view?usp=sharing https://drive.google.com/file/d/1j1zJ91pk_B0IMbvcXJJ7BwFiN0o7UVMH/view?usp=sharing

I installed both using sudo pacman -U --noconfirm
and after reboot, almost everything stopped working. I don't have network, bluetooth, sound, etc.
Was this the wrong command?

Did you have DKMS installed? Strangely enough I had this issue with a different kernel the other day myself.

Ah, It looks like i did not have DKMS installed. I'll reinstall the OS and try again with DKMS installed.

After installing DKMS, the header install gives this error.
`[gamer@chimeraos ~]$ sudo pacman -U --noconfirm Downloads/linux-chimeraos-headers-6.5.rc6.chos1-1-x86_64.pkg.tar.zst
loading packages...
warning: linux-chimeraos-headers-6.5.rc6.chos1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) linux-chimeraos-headers-6.5.rc6.chos1-1
Total Installed Size:  123.53 MiB
Net Upgrade Size:        0.00 MiB
:: Proceed with installation?  Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64)
Consult /var/lib/dkms/hid-xpadneo/v0.9.5/build/make.log for more information.
==> WARNING: dkms install --no-depmod hid-xpadneo/v0.9.5 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10 ==> dkms install --no-depmod xpad-noone/1.0 -k 6.5.0-chos1-rc6-chimeraos-1 Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64) Consult /var/lib/dkms/xpad-noone/1.0/build/make.log for more information. ==> WARNING: dkms install --no-depmod xpad-noone/1.0 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10
==> dkms install --no-depmod r8168/8.051.02 -k 6.5.0-chos1-rc6-chimeraos-1
Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64)
Consult /var/lib/dkms/r8168/8.051.02/build/make.log for more information.
==> WARNING: dkms install --no-depmod r8168/8.051.02 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10 ==> dkms install --no-depmod rtl8812au/5.13.6.r168.gb5f4e6e -k 6.5.0-chos1-rc6-chimeraos-1 Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64) Consult /var/lib/dkms/rtl8812au/5.13.6.r168.gb5f4e6e/build/make.log for more information. ==> WARNING: dkms install --no-depmod rtl8812au/5.13.6.r168.gb5f4e6e -k 6.5.0-chos1-rc6-chimeraos-1' exited 10
==> dkms install --no-depmod nvidia/530.41.03 -k 6.5.0-chos1-rc6-chimeraos-1
Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64)
Consult /var/lib/dkms/nvidia/530.41.03/build/make.log for more information.
==> WARNING: dkms install --no-depmod nvidia/530.41.03 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10 ==> dkms install --no-depmod rtl88x2bu/5.13.1.r189.12cfcd8 -k 6.5.0-chos1-rc6-chimeraos-1 Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.13.1.r189.12cfcd8/build/make.log for more information. ==> WARNING: dkms install --no-depmod rtl88x2bu/5.13.1.r189.12cfcd8 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10
==> dkms install --no-depmod xone/0.3.r2.gbbf0dcc -k 6.5.0-chos1-rc6-chimeraos-1
Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64)
Consult /var/lib/dkms/xone/0.3.r2.gbbf0dcc/build/make.log for more information.
==> WARNING: dkms install --no-depmod xone/0.3.r2.gbbf0dcc -k 6.5.0-chos1-rc6-chimeraos-1' exited 10 ==> dkms install --no-depmod rtl8814au/<IP_ADDRESS>.r170.g8a1908d -k 6.5.0-chos1-rc6-chimeraos-1 Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64) Consult /var/lib/dkms/rtl8814au/<IP_ADDRESS>.r170.g8a1908d/build/make.log for more information. ==> WARNING: dkms install --no-depmod rtl8814au/<IP_ADDRESS>.r170.g8a1908d -k 6.5.0-chos1-rc6-chimeraos-1' exited 10
==> dkms install --no-depmod 8821au/<IP_ADDRESS>.r208.g50c3332 -k 6.5.0-chos1-rc6-chimeraos-1
Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64)
Consult /var/lib/dkms/8821au/<IP_ADDRESS>.r208.g50c3332/build/make.log for more information.
==> WARNING: dkms install --no-depmod 8821au/<IP_ADDRESS>.r208.g50c3332 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10 ==> dkms install --no-depmod rtw89/r529.8f8efa6 -k 6.5.0-chos1-rc6-chimeraos-1 Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64) Consult /var/lib/dkms/rtw89/r529.8f8efa6/build/make.log for more information. ==> WARNING: dkms install --no-depmod rtw89/r529.8f8efa6 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10
==> dkms install --no-depmod broadcom-wl/<IP_ADDRESS>1 -k 6.5.0-chos1-rc6-chimeraos-1
/usr/bin/dkms: line 106: patch: command not found
Error! Application of patch 001-null-pointer-fix.patch failed.
Check /var/lib/dkms/broadcom-wl/<IP_ADDRESS>1/build for more information.
==> WARNING: dkms install --no-depmod broadcom-wl/<IP_ADDRESS>1 -k 6.5.0-chos1-rc6-chimeraos-1' exited 6 ==> dkms install --no-depmod oxp-sensors/v0.9.r0.gf75d844 -k 6.5.0-chos1-rc6-chimeraos-1 Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64) Consult /var/lib/dkms/oxp-sensors/v0.9.r0.gf75d844/build/make.log for more information. ==> WARNING: dkms install --no-depmod oxp-sensors/v0.9.r0.gf75d844 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10
==> dkms install --no-depmod r8152/<IP_ADDRESS>21209 -k 6.5.0-chos1-rc6-chimeraos-1
Error! Bad return status for module build on kernel: 6.5.0-chos1-rc6-chimeraos-1 (x86_64)
Consult /var/lib/dkms/r8152/<IP_ADDRESS>21209/build/make.log for more information.
==> WARNING: dkms install --no-depmod r8152/<IP_ADDRESS>21209 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10

==> WARNING: `dkms install --no-depmod r8152/<IP_ADDRESS>21209 -k 6.5.0-chos1-rc6-chimeraos-1' exited 10

Hmm, I'll try installing it on a Chimera box here.

Works on the Aya Neo Air Plus running ChimeraOS.

Works on the Aya Neo Air Plus running ChimeraOS.

I was going through the log files from the above failures and it looks like I am missing a bunch of dependencies needed for make.
I am trying to sort them out and reinstall the kernel.

Works on the Aya Neo Air Plus running ChimeraOS.

I was going through the log files from the above failures and it looks like I am missing a bunch of dependencies needed for make. I am trying to sort them out and reinstall the kernel.

You can try installing the base-devel package to bring in a lot of those dependencies most likely.

Works on the Aya Neo Air Plus running ChimeraOS.

I was going through the log files from the above failures and it looks like I am missing a bunch of dependencies needed for make. I am trying to sort them out and reinstall the kernel.

You can try installing the base-devel package to bring in a lot of those dependencies most likely.

I'm also trying out a fresh install.
Just so that I don't miss out on any steps.
Step 1: sudo frzr-unlock
Step 2: sudo pacman -S DMKS
Step 3: sudo pacman -S base-devel
Step 4: sudo pacman -U --noconfirm linux-chimeraos-6.5.rc6.chos1-1-x86_64.pkg.tar.zst
Step 5: sudo pacman -U --noconfirm linux-chimeraos-headers-6.5.rc6.chos1-1-x86_64.pkg.tar.zst
Thanks so much!

If you are using chimeraos be sure to update your kernel lines in /boot/loader/entries/frzr.conf
It'll be vmlinuz-linux-chimeraos and initramfs-linux-chimeraos.img
title chimeraos-44_98e8284
linux /vmlinuz-linux-chimeraos
initrd /amd-ucode.img
initrd /intel-ucode.img
initrd /initramfs-linux-chimeraos.img

I also remove the blacklist for xpad because it'll cause weird issues when switching out the kernel on chimeraos. This config is located at /etc/modprobe.d/xone-blacklist.conf

Apologies for not providing this information. I looked at your dmesg again..I must have been tired when I was looking at it last night, I thought I saw that you was using chimera packages on an Arch Linux install.

When I switched back to 6.4 from the 6.5 kernel I ran into the issue where I have no sound, no wifi, no ethernet, no nothing. I'll look into what's causing this. I had this issue when I went from 6.4 to 6.3.9 and back to 6.4 the other day as well.

Apologies for not providing this information. I looked at your dmesg again..I must have been tired when I was looking at it last night, I thought I saw that you was using chimera packages on an Arch Linux install.

No worries, thank you so much.
I'll try the above lines and reinstall.

When I switched back to 6.4 from the 6.5 kernel I ran into the issue where I have no sound, no wifi, no ethernet, no nothing. I'll look into what's causing this. I had this issue when I went from 6.4 to 6.3.9 and back to 6.4 the other day as well.

Awesome, thanks. I though it was just sound that was missing but it turns out all the devices were down.
It started working again when I chose "repair" option when reinstalling ChimeraOS

I tried it again with a fresh reinstall. One thing I noticed is that my chimeraOS version in /boot/loader/entries/frzr.conf  is chimeraos-43-1_788f4bb.
This is the version I got from https://github.com/ChimeraOS/install-media/releases/download/2023-07-06_69ce628/chimeraos-2023.07.06-x86_64.iso
I've uploaded the full steps I took
steps.txt
These are the 'cat' outs of each of the error logs from the above run.
errorlogs.txt
It looks like a version issue? Is it because I am on v43?

I tried it again with a fresh reinstall. One thing I noticed is that my chimeraOS version in /boot/loader/entries/frzr.conf is chimeraos-43-1_788f4bb. This is the version I got from https://github.com/ChimeraOS/install-media/releases/download/2023-07-06_69ce628/chimeraos-2023.07.06-x86_64.iso
I've uploaded the full steps I took steps.txt
These are the 'cat' outs of each of the error logs from the above run. errorlogs.txt
It looks like a version issue? Is it because I am on v43?

We're looking into the issue caused when switching out the kernel. I'll report back once we get that situation resolved. Previously we've been able to change kernels in this way and it looks like something changed.

I tried it again with a fresh reinstall. One thing I noticed is that my chimeraOS version in /boot/loader/entries/frzr.conf is chimeraos-43-1_788f4bb. This is the version I got from https://github.com/ChimeraOS/install-media/releases/download/2023-07-06_69ce628/chimeraos-2023.07.06-x86_64.iso
I've uploaded the full steps I took steps.txt
These are the 'cat' outs of each of the error logs from the above run. errorlogs.txt
It looks like a version issue? Is it because I am on v43?

We're looking into the issue caused when switching out the kernel. I'll report back once we get that situation resolved. Previously we've been able to change kernels in this way and it looks like something changed.

Sure, thanks again. Cheers!

Hello,
I pulled the linux-chimeraos git and added this patch file
onexplayer2pro_audio.patch.txt
Built the kernal and tried install but I kept getting these errors when installing the header file.
error.txt
Tried restart but the sound still did not work unfortunately.

what are the contents of /var/lib/dkms/nvidia/530.41.03/build/make.log

/var/lib/dkms/r8168/8.051.02/build/make.log
DKMS make.log for r8168-8.051.02 for kernel 6.4.12-chos1-chimeraos-1 (x86_64)
Sun Aug 27 08:59:41 PM IST 2023
  CC [M]  /var/lib/dkms/r8168/8.051.02/build/src/r8168_n.o
  CC [M]  /var/lib/dkms/r8168/8.051.02/build/src/r8168_asf.o
  CC [M]  /var/lib/dkms/r8168/8.051.02/build/src/rtl_eeprom.o
  CC [M]  /var/lib/dkms/r8168/8.051.02/build/src/rtltool.o
/var/lib/dkms/r8168/8.051.02/build/src/r8168_n.c: In function ‘r8168_csum_workaround’:
/var/lib/dkms/r8168/8.051.02/build/src/r8168_n.c:29208:24: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘skb_gso_reset’?  [-Werror=implicit-function-declaration]
 2074 |                 segs = skb_gso_segment(skb, features);
      |                        ^~~~~~~~~~~~~~~
      |                        skb_gso_reset
/var/lib/dkms/r8152/<IP_ADDRESS>21209/build/src/r8152.c:2074:22: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
 2074 |                 segs = skb_gso_segment(skb, features);
      |                      ^
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:252: /var/lib/dkms/r8152/<IP_ADDRESS>21209/build/src/r8152.o] Error 1
make: *** [Makefile:2032: /var/lib/dkms/r8152/<IP_ADDRESS>21209/build/src] Error 2

It didn't make a lot of sense to me.
I checked the r8152.c file and it does have #include<net.gso>

@ruineka is it possible to build and test the OS image from scratch with this change?
That way we don't need to test or try dynamic kernel swapping.
I really want to replace my Windows 11 with ChimeraOS.
I miss the pause/resume feature for games running on the SteamDeck which Windows doesn't have but ChimeraOS does.

@ruineka is it possible to test the OS image by building it from scratch with this change in it?
That way we don't need to  try dynamic kernel swapping.
I really want to replace my Windows 11 with ChimeraOS.
I miss the pause/resume feature for games running on the SteamDeck which Windows doesn't have but ChimeraOS does.

It would be easier to test on another distro like Manjaro most likely. You shouldn't run into the issues created by how ChimeraOS manages the initramfs and kernel. Once the fix is confirmed to work we can get another unstable build going that will include the patch.

I'll try to test the patch in Manjaro.
Thanks.

@ruineka I tried the change on Manjaro but it did not work.
These are the steps i took:

Install Manjaro
Download the kernel, create a diff patch from scratch with the changes above
patch_realtek.c.txt
0414-oxp2pro.patch.txt
Build and install the kernel
Files: https://drive.google.com/drive/folders/1x1N2peWtkj2_phWErtvcFvKojVznCtgD?usp=sharing

The audio did not work after restart. I tried it a couple of times.
I also tried hdajackretask but 0x02 and 0x03 pins did not show up on it on any linux distro.

It looks like that patch has the typo. Look at the function where it says ox2pro_pin. I put pin instead of pins so it's not called properly. I'm on my phone ATM so I can't look at it in a clean way.

It looks like that patch has the typo. Look at the function where it says ox2pro_pin. I put pin instead of pins so it's not called properly. I'm on my phone ATM so I can't look at it in a clean way.

I noticed the typo and fixed it in my patch. Its still not working, not sure why.
All the patches I've tried so far, i had fixed the "pin" -> "pins" issue.

alc245_fixup_oxp2pro_pin should be alc245_fixup_oxp2pro_pins

It looks like that patch has the typo. Look at the function where it says ox2pro_pin. I put pin instead of pins so it's not called properly. I'm on my phone ATM so I can't look at it in a clean way.

I noticed the typo and fixed it in my patch. Its still not working, not sure why.
All the patches I've tried so far, i had fixed the "pin" -> "pins" issue.

Ah okay thanks. I'll take a look at it again later.

It looks like that patch has the typo. Look at the function where it says ox2pro_pin. I put pin instead of pins so it's not called properly. I'm on my phone ATM so I can't look at it in a clean way.

I noticed the typo and fixed it in my patch. Its still not working, not sure why.
All the patches I've tried so far, i had fixed the "pin" -> "pins" issue.

Ah okay thanks. I'll take a look at it again later.

Thanks a mil!
Please let me know if you need help to test anything.
I have windows, chimeraOS, holoISO and manjaro installed in separate SSDs. I can boot swap to test whenever you need me to.
Thanks again

Hi @ruineka,
I tried steps from this post i found
https://wiki.darkremix.net/en/aokzoe/ChimeraOS-Guide
which did not work but while testing, i accidentally booted into Windows then restarted into ChimeraOS and the audio started working.
But on fresh boot, it doesn't work again.
It works if i boot into windows, play some sound then boot into ChimeraOS. Not sure why.

Hey team,
Any updates on this?

0012-oxp2pro.patch.txt

RtHDDump_realtek_driver.txt
This is a Windows 11 Dump of an OXP2Pro. If that can help anyone!

oxp2-dmesg.log
This is a dump of my oxp2 (not Pro)

Can someone assist in providing the right patch and the new kernel to make and with command. I am a bit confused about what to do... There are multiple files and explanation.

This is for an OXP2

The current patch doesn't work. We'll look at the new data you provided and hopefully we can find a clue for the next step.

Can someone assist in providing the right patch and the new kernel to make and with command. I am a bit confused about what to do... There are multiple files and explanation.

Hi,
Step 1: Unlock the filesystem using "sudo frzr-unlock"
Step 2: install packages for build "sudo pacman -S base-devel pahole dkms"
Step 3: Download or git clone the ChimeraOS kernel repo
https://github.com/ChimeraOS/linux-chimeraos
Step 4: the above patch file starting with 0012 should work unless the kernel version changed since then.
Step 5: put the file into the linux-chimeraos/linux folder
Step 6: put the file name in PKGBUILD file after the 0011 patch entry
Step 7: run "updpkgsums"
Step 8: run "makepkg --si"  to build and install the kernel. It will take an hour or two maybe. After build it will ask for sudo password to install it.

will wait for an eventual new patch, Anything i can do please let me know!

@ruineka  found that 0x1b was also connected to 0x02 pin.
I updated the patch with the change and tested it on 6.5.4 kernel.
It still did not work but here is the patch file:
0012-oxp2.patch.txt

Ok, I will boot my Oxp2 to windows, do a dump, then restart in chimera,
check that sound works and a new dump. Keep you posted.
Tx for all you do for us!!
On Fri, Sep 22, 2023, 7:54 PM Parth Menon @.***> wrote:

@ruineka https://github.com/ruineka found that 0x1b was also connected
to 0x02 pin.
I updated the patch with the change and tested it on 6.5.4 kernel.
It still did not work but here is the patch file:
0012-oxp2.patch.txt
https://github.com/ChimeraOS/chimeraos/files/12703391/0012-oxp2.patch.txt
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1731824574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2MLQ4SHSYHF6DQ55YDX3XGGFANCNFSM6AAAAAA36LQKDA
.
You are receiving this because you commented.Message ID:
@.***>

Some people are saying that after booting on Windows and then back the sound is working. So I guess that turning off the OXP2 and borring it to Chim would make the sound to stop. So if I am lucky I can get 2 dump.. one when it works and one when it stop working. Crossed fingers

Some people are saying that after booting on Windows and then back the sound is working. So I guess that turning off the OXP2 and borring it to Chim would make the sound to stop. So if I am lucky I can get 2 dump.. one when it works and one when it stop working. Crossed fingers

I tried this a couple of times but it didn't work for me.

OK i did an interesting test. I boot my OXP2 on Windows and check the sound. then i reboot in Chimera and i could hear sound on the Steam UI while scrolling left and right. I havent installed any patch or whatever. Then i switch to desktop mode and sound stopped  working. So switching from the steam OS UI to Chim seems to disable the sound. When i got back to Steam UI, the sound was gone. If that gives some idea to you...

OK i did an interesting test. I boot my OXP2 on Windows and check the sound. then i reboot in Chimera and i could hear sound on the Steam UI while scrolling left and right. I havent installed any patch or whatever. Then i switch to desktop mode and sound stopped working. So switching from the steam OS UI to Chim seems to disable the sound. When i got back to Steam UI, the sound was gone. If that gives some idea to you...

Is this reproducible? As in, does it happen everytime you not into windows and then ChimeraOS?
Also does the same thing happen on the pro version?

OK i did an interesting test. I boot my OXP2 on Windows and check the sound. then i reboot in Chimera and i could hear sound on the Steam UI while scrolling left and right. I havent installed any patch or whatever. Then i switch to desktop mode and sound stopped working. So switching from the steam OS UI to Chim seems to disable the sound. When i got back to Steam UI, the sound was gone. If that gives some idea to you...

instead of going to the desktop you can use a keyboard and type ctrl+alt+f3 to get to a TTY to do the dump when sound is working.

Perfect. Tx. Let me try again!
On Sat, Sep 23, 2023, 5:17 PM Derek J. Clark @.***>
wrote:

OK i did an interesting test. I boot my OXP2 on Windows and check the
sound. then i reboot in Chimera and i could hear sound on the Steam UI
while scrolling left and right. I havent installed any patch or whatever.
Then i switch to desktop mode and sound stopped working. So switching from
the steam OS UI to Chim seems to disable the sound. When i got back to
Steam UI, the sound was gone. If that gives some idea to you...
instead of going to the desktop you can use a keyboard and type
ctrl+alt+f3 to get to a TTY to do the dump when sound is working.
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1732340426,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2L5TWDTXUIR67RM4ALX334QXANCNFSM6AAAAAA36LQKDA
.
You are receiving this because you commented.Message ID:
@.***>

i confirm sound working. I went to TTY but the screen is so small. i run the alsa-tools.sh. it got uploaded to the alsa project but i just cant read the URL :( will try to take a pic with my phone..

So hopefully we have a dump with sound working...
uploading the phone pic soon

Extracted link:
https://alsa-project.org/db/?f=fab9dc220becabb07752e78ce451d8fa21f17c74

Sound still working after i come back to Steam UI

First, it seems to me that audio is working perfectly on the ONEXplayer2.
Now, the issue is on the ONEXPlayer 2 Pro.
i installed windows 11 and i had no audio. i created a dump for it. Then i installed the RT driver and after a reboot (still) in
windows, audio is now working. I created a dump for it. now i will reboot in Chimera to see what is going on.

I am now in steamOS UI in Chimera and i have sound. Here is a pic of the link to the dump

I have shutdown my 2PRo and wait 3 mn. When I restart Chimera, the sound is now gone. Her is a pic of the link with the dump

Here is the difference between @cedricju 's working vs non working alsa infos: https://www.diffchecker.com/OC6PNOGR/
This one is the difference between @cedricju 's working and my non working alsa infos
https://www.diffchecker.com/TurZ4N7T/
You can see in mine i got the pin reconnection done but still no audio
The main differences I'm seeing between working and non working is
Working -> Amp-Out vals:  [0x3a 0x3a]
Non working -> Amp-Out vals:  [0x4d 0x4d]
Working -> PCM: rates [0x2e0]: 44100 48000 88200 176400
Not working -> PCM:    rates [0x40]: 48000
Unfortunately idk what these mean or how to set them.
Can someone from ChimeraOS team help us please?

ok i extracted the URL:
Chim OS not working:
https://www.alsa-project.org/db/?f=e25d9c277dbc7a3d8e099b51595748771da77007
Chim OS working:
https://www.alsa-project.org/db/?f=e8662fba7c46922cb7e853977071073cb855e90a5

lost the sound as well on my non pro version. it did works for days and even resists a shutdown/restart... here is the dump for the nonpro version when sounds is NOT working http://alsa-project.org/db/?f=40c000e2f82d35ec990c4e77d2a9149ce241231c

The previous dump was performed with the HDMI output (Sounds works fine). Here is another dump with speaker activated in dekstop mode. (Still not working)

Non working sound OXP2 (Not Pro)
[gamer@chimeraos ~]$ journalctl -k | grep -Ei "ALSA|HDA|sof[-]|HDMI|snd[-]|sournd|hda.codec|hda.intel"**
Aug 09 16:07:26 chimeraos kernel: ACPI: _SB.PCI0.GP17.HDAU.PWRS: New power resource
Aug 09 16:07:26 chimeraos kernel: [drm] DP-HDMI FRL PCON supported
Aug 09 16:07:26 chimeraos kernel: snd_pci_acp6x 0000:74:00.5: enabling device (0000 -> 0002)
Aug 09 16:07:26 chimeraos kernel: snd_hda_intel 0000:74:00.1: enabling device (0000 -> 0002)
Aug 09 16:07:26 chimeraos kernel: snd_hda_intel 0000:74:00.1: Handle vga_switcheroo audio client
Aug 09 16:07:26 chimeraos kernel: snd_hda_intel 0000:74:00.6: enabling device (0000 -> 0002)
Aug 09 16:07:26 chimeraos kernel: snd_hda_intel 0000:74:00.1: bound 0000:74:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Aug 09 16:07:26 chimeraos kernel: input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:74:00.1/sound/card0/input16
Aug 09 16:07:26 chimeraos kernel: input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:74:00.1/sound/card0/input17
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19
Aug 09 16:07:26 chimeraos kernel: snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x12

https://www.diffchecker.com/6pHIxaO3/
Looks like the "Amp value" is diffferent

Some Progress on the Audio Front
Got Audio to work consistently. Microphone, Built-In Speakers and Audio Jack.
Volume really only starts at ~15% tho. But it works!
Heres the modprobe file i use:
/etc/modprobe.d/alsa-base.conf
options snd_intel_dspcfg dsp_driver=1
options snd_hda_intel power_save=0
options snd-hda-intel model=laptop-dmic enable=yes
dsp_driver=1 made it appear in the first place.
power_save=0 keeps it from vanishing.
model=laptop-dmic makes Microphone, Audio Jack and Built-In speakers work Reliably.
Hope this helps
Tested on CachyOS
Kernel: 6.5.9-1
sof-firmware  2023.09-1.1
alsa-utils  1.2.10-1.1

I tried it but didn't work for me :(

The way it works for me is on the OXP2 (non Pro) is

disable Fast start on Windows
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power
HiberbootEnabled DWORD
0 = Turn off fast startup
1 = Turn on fast startup

have you magic conf file (TX by the way)

force Shutdown Winodws once.

Still sound. (I will run the battery out and wait like a few days as last
time, i lost the sound after this!)
C
On Mon, Oct 30, 2023 at 3:14 PM Parth Menon @.***>
wrote:

I tried it but didn't work for me :(
[image: Screenshot_20231027_151605_Gallery]
https://user-images.githubusercontent.com/15328397/279085100-bb9e8318-0728-4550-ab4c-da40905335de.jpg
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1785309888,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2O3UXBM5FUT4JGS3DLYB6Y33AVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGMYDSOBYHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

The way it works for me is on the OXP2 (non Pro) is 1) disable Fast start on Windows (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power HiberbootEnabled DWORD 0 = Turn off fast startup 1 = Turn on fast startup 2) have you magic conf file (TX by the way) 3) force Shutdown Winodws once. Still sound. (I will run the battery out and wait like a few days as last time, i lost the sound after this!) C
…
On Mon, Oct 30, 2023 at 3:14 PM Parth Menon @.> wrote: I tried it but didn't work for me :( [image: Screenshot_20231027_151605_Gallery] https://user-images.githubusercontent.com/15328397/279085100-bb9e8318-0728-4550-ab4c-da40905335de.jpg — Reply to this email directly, view it on GitHub <#742 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO5HO2O3UXBM5FUT4JGS3DLYB6Y33AVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGMYDSOBYHA . You are receiving this because you were mentioned.Message ID: @.>

Does it work without ever booting into Windows?

Been only using Chin since yesterday. I can sleep mode, and cold start. I
belive there is something like DEEP DEEP Shutdown that is resetting
everythign. SO i will wait until battery runs out and wait a night, then i
will report back
C
On Tue, Oct 31, 2023 at 10:31 AM Parth Menon @.***>
wrote:

The way it works for me is on the OXP2 (non Pro) is 1) disable Fast start
on Windows (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Power HiberbootEnabled DWORD 0 = Turn off fast startup 1 = Turn on
fast startup 2) have you magic conf file (TX by the way) 3) force Shutdown
Winodws once. Still sound. (I will run the battery out and wait like a few
days as last time, i lost the sound after this!) C
… <#m_6417425157393488331_>
On Mon, Oct 30, 2023 at 3:14 PM Parth Menon @.> wrote: I tried it but
didn't work for me :( [image: Screenshot_20231027_151605_Gallery]
https://user-images.githubusercontent.com/15328397/279085100-bb9e8318-0728-4550-ab4c-da40905335de.jpg
https://user-images.githubusercontent.com/15328397/279085100-bb9e8318-0728-4550-ab4c-da40905335de.jpg
— Reply to this email directly, view it on GitHub <#742 (comment)
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1785309888>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2O3UXBM5FUT4JGS3DLYB6Y33AVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGMYDSOBYHA
https://github.com/notifications/unsubscribe-auth/AO5HO2O3UXBM5FUT4JGS3DLYB6Y33AVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGMYDSOBYHA
. You are receiving this because you were mentioned.Message ID: @.>
Does it work without ever booting into Windows?
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1786836554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2PUZNVA2KIZYM32CFLYCDANZAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBWHAZTMNJVGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Seems like an BIOS issue at that Point. Now that I ran out of Battery Once its gone again.
And if its really BIOS we are fucked. I contacted OneX about this already and they show NO interest at all to get this sorted out.
They just told me to use Windows.

Seems like an BIOS issue at that Point. Now that I ran out of Battery Once its gone again.
And if its really BIOS we are fucked. I contacted OneX about this already and they show NO interest at all to get this sorted out. They just told me to use Windows.

Yeah, i had the same experience from OneX.
In my GPD, whenever i boots, the speaker does a pop sound, which i believe is initialising the audio from BIOS.
OneX has left that upto Windows so i don't think there is a way to get it working without them releasing a new bios which initialises the speakers.

I dont even think its the Sound Chip.
That one gets detected just fine. It seems like the AMP Values are the ones that are missing or get lost on deep discharge.
And without the AMPs we simply hear nothing.
I think this because while testing a lot of things, the Handheld screeched at me like a Banshee once I came back into Windows.
I told OneX all that. But yeah.
"Just use Windows" -.-

When we manage to find out the AMP Values we probably could patch them in. But that's way above what I am able to do.

Have you guys seen what I added in discord. There is a windows utility
called Microsoft HDA utility. I used it once and post some screenshot.
There are pin connection and such. Maybe someone with more knowledge than
me could check it.
To get it straight, a fresh windows installation died not install the
realtek driver and while the hda driver are loaded, there is no sound.
So may be using the tool before and after driver install may give us some
info?
Just trying to be creative here.
On Thu, Nov 2, 2023, 5:48 PM N1GHT @.***> wrote:

I dont even think its the Sound Chip.
That one gets detected just fine. It seems like the AMP Values are the
ones that are missing or get lost on deep discharge.
And without the AMPs we simply hear nothing.
I think this because while testing a lot of things, the Handheld screeched
at me like a Banshee once I came back into Windows.
I told OneX all that. But yeah.
"Just use Windows" -.-
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1790994649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2MDIE4MUHOEJINCBFLYCO6EVAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQHE4TINRUHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Have you guys seen what I added in discord. There is a windows utility called Microsoft HDA utility. I used it once and post some screenshot. There are pin connection and such. Maybe someone with more knowledge than me could check it. To get it straight, a fresh windows installation died not install the realtek driver and while the hda driver are loaded, there is no sound. So may be using the tool before and after driver install may give us some info? Just trying to be creative here.
…
On Thu, Nov 2, 2023, 5:48 PM N1GHT @.> wrote: I dont even think its the Sound Chip. That one gets detected just fine. It seems like the AMP Values are the ones that are missing or get lost on deep discharge. And without the AMPs we simply hear nothing. I think this because while testing a lot of things, the Handheld screeched at me like a Banshee once I came back into Windows. I told OneX all that. But yeah. "Just use Windows" -.- — Reply to this email directly, view it on GitHub <#742 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO5HO2MDIE4MUHOEJINCBFLYCO6EVAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQHE4TINRUHE . You are receiving this because you were mentioned.Message ID: @.>

This maybe promising but i don't have the knowledge to do it

Can you Post a Dump/Output/Screenshot of that here for the Wizards?
I am not on Windows atm on my Device.

On chimera discord, under onexplayer channel, I put some of them.
Can do it again before the realtek driver are installed
On Thu, Nov 2, 2023, 5:56 PM N1GHT @.***> wrote:

Can you Post a Dump/Output/Screenshot of that here for the Wizards?
I am not on Windows atm on my Device.
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1791009914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2KQFWUTJOQFSRGDZ3TYCO7EDAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGAYDSOJRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

There is all pin connection.
Need to do a compare before and after.
On Thu, Nov 2, 2023, 6:02 PM Cedric Jucker @.***> wrote:

On chimera discord, under onexplayer channel, I put some of them.
Can do it again before the realtek driver are installed
On Thu, Nov 2, 2023, 5:56 PM N1GHT @.***> wrote:

Can you Post a Dump/Output/Screenshot of that here for the Wizards?
I am not on Windows atm on my Device.
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1791009914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2KQFWUTJOQFSRGDZ3TYCO7EDAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGAYDSOJRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Would be better to also post them here. Kernel Developer are rarely in Discord^^

Will do for sure. Sorry for that!!
On Thu, Nov 2, 2023, 6:06 PM N1GHT @.***> wrote:

Would be better to also post them here. Kernel Developer are rarely in
Discord^^
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1791028344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2IPRQ2THHGKBNMT7OTYCPAIFAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGAZDQMZUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

NP. I am sure this will help a lot if some of those Wizards actually manage to stumble across this Issue.
Maybe we should also raise this General Issue with the Kernel itself.

For the meantime there is the Possibility of Early Patching:
https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#early-patching
Maybe I can figure that out on the Weekend.

For the meantime there is the Possibility of Early Patching: https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#early-patching
or this: https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#hd-audio-reconfiguration
Maybe I can figure that out on the Weekend.

I tried re-pinning the system with kernel builds before.
I think we tested this and the pins are correct.
Its just some AMP value or AMP initialization is wrong.

In a plane right now. But maybe we get more info about the PIN tools. I
will forward those when home in the morning
On Thu, Nov 2, 2023, 6:04 PM Parth Menon @.***> wrote:

For the meantime there is the Possibility of Early Patching:
https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#early-patching
or this:
https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#hd-audio-reconfiguration
Maybe I can figure that out on the Weekend.
I tried re-pinning the system with kernel builds before.
I think we tested this and the pins are correct.
Its just some AMP value or AMP initialization is wrong.
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1791133465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2IH5XQPKHJYJH6N7UDYCPHBTAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGEZTGNBWGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

For the meantime there is the Possibility of Early Patching: https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#early-patching
or this: https://www.kernel.org/doc/html/v5.9/sound/hd-audio/notes.html#hd-audio-reconfiguration
Maybe I can figure that out on the Weekend.

I tried re-pinning the system with kernel builds before. I think we tested this and the pins are correct. Its just some AMP value or AMP initialization is wrong.

Good to know.
Then I will try playing around with hda-verb if the Pins are already correct.

Playing around a bit more I got another alsa-info DIFF.
AMP Values are the Same working and non Working. The Only thing that differs are PCM Rates...
https://www.diffchecker.com/XrEiuZnL/

Also got 2 Identical alsa-info files...
One working. One not Working.
Both are the same.
I dont get it...

Well. Windows without the realtek driver does not enable sound even with th
default Microsoft driver.
There is a realtek dump utility on wi does as well we have done it before
but can do it again
On Fri, Nov 3, 2023, 4:48 AM N1GHT @.***> wrote:

Also got 2 Identical alsa-info files...
One working. One not Working.
Both are the same.
I dont get it...
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1791860230,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2KFVG6QEEOJ4HKFC4DYCRSPJAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRHA3DAMRTGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

https://bugzilla.kernel.org/show_bug.cgi?id=218097
To spread the reach of this Issue a bit.

https://bugzilla.kernel.org/show_bug.cgi?id=218097
To spread the reach of this Issue a bit.

Thanks for creating the bug.
I reached out to OneXPlayer and this is their response
`Dear customer,
The ONEXPLAYER 2/ 2 PRO and ONEXFLY all compatible with Windows 11 Home system, which can't work for linus system.

Yeah. Got the Same response. And Told them mine goes straight back to the Retailer as I am still in the 30 Days Money back timeframe.
This weekend I will still try to help out here, but after that, someone else has to figure this out.
Sorry.
OneX really is the worst and I think I get myself something else.

Yeah. Got the Same response. And Told them mine goes straight back to the Retailer as I am still in the 30 Days Money back timeframe. This weekend I will still try to help out here, but after that, someone else has to figure this out.
Sorry. OneX really is the worst and I think I get myself something else.

In highly recommend the GPD Win4 if you like PSP style or the Win Mini/Max if you like flip form factor.
Win4 is simply amazing. Love the device and GPD service is super fast. They take requests for bugs and try to help.

Would someone be up to doing whats descriped here and send over the dumps?
https://github.com/Conmanx360/QemuHDADump/wiki/Setup-and-usage-of-the-program

Would someone be up to doing whats descriped here and send over the dumps? https://github.com/Conmanx360/QemuHDADump/wiki/Setup-and-usage-of-the-program
This should dump everything the Windows Driver does to HDA for us to analyze and possibly reproduce.

Do you still need ? I just got the device and got it working dualbooting windows/chimeraos and can help dumping

I do believe it is not working anymore...
Someone tried it already.
We have an ongoing process with the onex team but never got answers..
On Tue, Mar 5, 2024, 11:21 PM Sergio Solorzano @.***>
wrote:

Would someone be up to doing whats descriped here and send over the dumps?
https://github.com/Conmanx360/QemuHDADump/wiki/Setup-and-usage-of-the-program
This should dump everything the Windows Driver does to HDA for us to
analyze and possibly reproduce.
Do you still need ? I just got the device and got it working dualbooting
windows/chimeraos and can help dumping
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/742#issuecomment-1979655593,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO5HO2LQMMGEPWGLOOWN6LLYWYZNFAVCNFSM6AAAAAA36LQKDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZZGY2TKNJZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have a workaround.
By booting into Windows and then forcing a shutdown, I use QEMU to boot the Windows OS that came with the machine. In the meantime, I passthrough the audio card with IOMMU to the Windows VM. The amp can be initialized this way too. After the sound comes out at the Windows login UI, I kill QEMU. Now the speaker works.

I suggest looking into the Legion Go and staying away from those Chinese manufacturers.

FWIW Lenovo is also a Chinese manufacturer.

But one that actually gives a damn.

But one that actually gives a damn.

 I fiddled with these Issues back in November.
In the Meanwhile, Lenovo pretty much addressed every Issue we threw at them in BIOS.
But I hope for you guys they figure it out some day. But I would not hold my hopes up.
Im out.

I have a workaround.
By booting into Windows and then forcing a shutdown, I use QEMU to boot the Windows OS that came with the machine. In the meantime, I passthrough the audio card with IOMMU to the Windows VM. The amp can be initialized this way too. After the sound comes out at the Windows login UI, I kill QEMU. Now the speaker works.

I dumped the CORB and got a list of verbs. The speaker can work with this list of verbs without starting windows.
Here is the script: hda-verbs-testing.txt, the sound came out before this line:
00280972: hda-verb /dev/snd/hwC1D0 0x20 0x400 0x78

I'm not sure if these verbs has any side effect. USE AT YOUR OWN RISK.
I will try if I can reduce verbs from this script.

I have a workaround.
By booting into Windows and then forcing a shutdown, I use QEMU to boot the Windows OS that came with the machine. In the meantime, I passthrough the audio card with IOMMU to the Windows VM. The amp can be initialized this way too. After the sound comes out at the Windows login UI, I kill QEMU. Now the speaker works.

I dumped the CORB and got a list of verbs. The speaker can work with this list of verbs without starting windows.
Here is the script: hda-verbs-testing.txt, the sound came out before this line:
00280972: hda-verb /dev/snd/hwC1D0 0x20 0x400 0x78

I'm not sure if these verbs has any side effect. USE AT YOUR OWN RISK.
I will try if I can reduce verbs from this script.

Good progress, my friend.
Let me know if I can help test.

Good progress, my friend. Let me know if I can help test.

My model is OneXPlayer 2 Pro(8840u). I am not sure if my verbs can run on your model. Also, I am not sure if wrong verbs will harm your hardware.
My OS is Arch Linux.
Btw, if anyone want to make accelerometer work, try bmi260-dkms in AUR.

The fix for this exists, as a BIOS update, but it's up to OneXPlayer to release. I think the only way that happens is if they get enough pressure from users. I highly encourage everyone to email OXP support to release the BIOS with the fix.


Add icons for social buttons

This is an enhancement. I want to replace the text with their social icons, it will give a good look.
Please assign this issue to me.

@MightyJoeW may I do this part?

Resolved by https://github.com/MightyJoeW/OpenSourceDevs/pull/35


Crash while opening project due to failure to compile Metal shader

Tested versions
Crashes in v4.4.dev.custom_build [3b3d622]
It says custom due to my spotty internet not being able to successfully git clone the repository. I used the ZIP download which doesn't include the .git folder. This is just a normal build using 3b3d622.
Works in v4.3.stable.official [77dcf97d8]
System information
Godot v4.4.dev unknown - macOS 14.3.1 - Metal (Mobile) - integrated Apple M1 (Apple7) - Apple M1 (8 Threads)
Issue description
I am attempting to update the ARKit plugin. To test do this I use an old Godot 3 ARKit sample project which I updated to work with 4.3, but that crashes when loaded using 4.4 dev with Metal. I have removed the ARKit plugin part and it still crashes, so this is just the project itself.
Trace:
Godot Engine v4.4.dev.custom_build - https://godotengine.org
OpenGL API 4.1 Metal - 88 - Compatibility - Using Device: Apple - Apple M1

2024-08-21 11:10:30.675 godot.macos.editor.arm64[97112:2608326] WARNING: AVCaptureDeviceTypeExternal is deprecated for Continuity Cameras. Please use AVCaptureDeviceTypeContinuityCamera and add NSCameraUseContinuityCameraDeviceType to your Info.plist.
Project is missing: /Users/asgeir/Godot/project.godot
Project is missing: /Users/asgeir/Godot/Arkit test/project.godot
Project is missing: /Users/asgeir/Godot/godot_ios_plugins/godot-4/godot3_test_projects/ARKit/project.godot
Project is missing: /Users/asgeir/Godot/GDExtension/GDExtension-Project/new-game-project/project.godot
Project is missing: /Users/asgeir/Godot/godot3_test_projects/ARKit/project.godot
Editing project: /Users/asgeir/Godot/Godot-Metal-Test/godot3_test_projects/ARKit-Godot-Crash-MRP-4.4
Godot Engine v4.4.dev.custom_build - https://godotengine.org
Metal 3.1 - Forward+ - Using Device #0: Apple - Apple M1 (Apple7)
program_source:542:14: warning: unused variable 'inv_view_matrix' [-Wunused-variable]
    float4x4 inv_view_matrix = scene_data.inv_view_matrix;
             ^
program_source:604:14: warning: unused variable 'inv_projection_matrix' [-Wunused-variable]
    float4x4 inv_projection_matrix = scene_data.inv_projection_matrix_view[int(gl_ViewIndex)];
             ^
program_source:605:12: warning: unused variable 'eye_offset' [-Wunused-variable]
    float3 eye_offset = scene_data.eye_offset[int(gl_ViewIndex)].xyz;
           ^
program_source:608:14: warning: unused variable 'modelview_normal' [-Wunused-variable]
    float3x3 modelview_normal = float3x3(scene_data.view_matrix[0].xyz, scene_data.view_matrix[1].xyz, scene_data.view_matrix[2].xyz) * model_normal_matrix;
             ^
program_source:609:14: warning: unused variable 'read_view_matrix' [-Wunused-variable]
    float4x4 read_view_matrix = scene_data.view_matrix;
             ^
program_source:610:12: warning: unused variable 'read_viewport_size' [-Wunused-variable]
    float2 read_viewport_size = scene_data.viewport_size;
           ^
program_source:846:5: error: no matching function for call to 'vertex_shader'
    vertex_shader(param_4, param_5, param_6, param_7, param_8, param_9, param_10, (*spvDescriptorSet1.instances), gl_InstanceIndex, (*spvDescriptorSet2.transforms), gl_ViewIndex, out.vertex_interp, out.gl_Position, out.combined_projected);
    ^~~~~~~~~~~~~
program_source:539:6: note: candidate function not viable: 11th argument ('const uint' (aka 'const unsigned int')) would lose const qualifier
void vertex_shader(thread const float3& vertex_input, thread const uint& instance_index, thread const bool& is_multimesh, thread const uint& multimesh_offset, thread const SceneData& scene_data, thread float4x4& model_matrix, thread const float4& screen_pos, const device InstanceDataBuffer& instances, thread uint& gl_InstanceIndex, const device Transforms& transforms, thread uint& gl_ViewIndex, thread float3& vertex_interp, thread float4& gl_Position, thread float4& combined_projected)
     ^

ERROR: failed to compile Metal source
   at: shader_create_from_bytecode (drivers/metal/rendering_device_driver_metal.mm:2298)
ERROR: Condition "!shader_id" is true.    Returning: RID()
   at: shader_create_from_bytecode (servers/rendering/rendering_device.cpp:2668)
ERROR: Parameter "p_version->variants" is null.
   at: _allocate_placeholders (servers/rendering/renderer_rd/shader_rd.cpp:492)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.4.dev.custom_build
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] 1   libsystem_platform.dylib            0x000000018a319a24 _sigtramp + 56
[2] RendererSceneRenderImplementation::SceneShaderForwardClustered::ShaderData::set_code(String const&) (in godot.macos.editor.arm64) + 5424
[3] RendererRD::MaterialStorage::shader_set_code(RID, String const&) (in godot.macos.editor.arm64) + 512
[4] RendererSceneRenderImplementation::SceneShaderForwardClustered::init(String) (in godot.macos.editor.arm64) + 14488
[5] RendererSceneRenderImplementation::RenderForwardClustered::RenderForwardClustered() (in godot.macos.editor.arm64) + 2244
[6] RendererCompositorRD::RendererCompositorRD() (in godot.macos.editor.arm64) + 2120
[7] RenderingServerDefault::_init() (in godot.macos.editor.arm64) + 156
[8] Main::setup2(bool) (in godot.macos.editor.arm64) + 7700
[9] Main::setup(char const*, int, char**, bool) (in godot.macos.editor.arm64) + 71384
[10] main (in godot.macos.editor.arm64) + 300
[11] 11  dyld                                0x0000000189f690e0 start + 2360
-- END OF BACKTRACE --
================================================================

Steps to reproduce

Use an editor build with Metal on MacOS (3b3d622 in my case)
Open the MRP project
Observe the crash

Minimal reproduction project (MRP)
ARKit-Godot-Crash-MRP-4.4.zip

The issue was that the Metal rendering driver returns true for the SUPPORTS_MULTIVIEW query, whereas the driver has not implemented it yet.
I can open the project once it returns the correct value.


Using a photo set to test frame processor plugins❓

Question
How to test the accuracy of frames processor?
What I tried
I would like to be able to measure the accuracy of frame processor plugins QR code reader and OCR.
To do this I would like to be able to give to the two frame processor plugins a photo set and observe the results for each photo of the set and measure the accuracy ? To sum up, I would like to be able to test frame processor plugins alone with a photo set.
Ideas ? Thanks in advance :)
VisionCamera Version
latest
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Well you can just count the successful reads yourself:
const successfulReads = useSharedValue(0)

const frameProcessor = useFrameProcessor((frame) => {
  'worklet'

  const textInImage = scanTextInImageOCR(frame)
  if (textInImage.length > 0)
    successfulReads.value += 1
}, [])

Hi, I have similar use case where I'd like to pass an image to frameProcessor. Is it possible to map Image to Frame?

Did you find something ?

@Easy47 @wojteklembryk any updates on this? I am facing the same problem in which I want to be able to test the plugin using a static image.

@Easy47 @wojteklembryk any updates on this? I am facing the same problem in which I want to be able to test the plugin using a static image.

I made a frame processor plugin in which I load an image. I did not succeed in directly returning the frame so I test in the same plugin

@Easy47 @wojteklembryk any updates on this? I am facing the same problem in which I want to be able to test the plugin using a static image.

I made a frame processor plugin in which I load an image. I did not succeed in directly returning the frame so I test in the same plugin

I changed approach and instead of reusing frame processor I extracted it's logic into separate component.
My case was Google MLKit based so I use image picker that's pass data to MLKit bridge and then apply shared frame processor logic.

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.


:wrench: cassandra multi host hostname fix

Expecting this will fix the cassandra provisioning issue when there is only one node cassandra
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change
Please choose appropriate options.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Enhancement (additive changes to improve performance)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes in the below checkboxes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Ran Test A
[ ] Ran Test B

Test Configuration:

Software versions:
Hardware versions:

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

The build job is getting failed due to changes.


Add support for taints and spot instances for node groups

What resource do you need?
Support for taints and spot instances in EKS node group.
What is your use case?
Simple EKS deployment with Taints for my database layer and Spot instances for cost saving.
Relevant links:
AWS:
https://docs.aws.amazon.com/eks/latest/userguide/node-taints-managed-node-groups.html
https://aws.amazon.com/getting-started/hands-on/amazon-eks-with-spot-instances/
Terraform:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_node_group#taint-configuration-block
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_node_group#capacity_type

this depends on #383 as the eks controller is not yet code generated


Add back onSuccess and onError handlers to Form

I actually didn't realize these were gone until I tried to use them 😆
So, from reading the docs, I figure the rationale was that the onSuccess/onError callbacks were used to update state to show some message in the UI. The useFormSubmit state works fine in that case. But when I need to fire some side effect, the hook state feels more cumbersome.
Here's an example and comparison. The modal accepts a render prop for a close function.
Without the onSuccess callback, I need to use a useEffect that relies on the hook state, which also requires making a new component in which to use the hook:
export function EditBucketButton({ bucket }) {
  return (
    <Modal
      title="edit bucket"
      renderContent={({ close }) => (
        <EditBucketForm bucket={bucket} onSuccess={close} />
      )}
    />
  )
}

function EditBucketForm({ bucket, onSuccess }) {
  const { isSuccess } = useFormSubmit("edit-bucket")

  useEffect(() => {
    if (isSuccess) onSuccess()
  }, [isSuccess, onSuccess])

  return (
    <Form name="edit-bucket" action={`/buckets/${bucket.id}`} method="patch">
      {/* form stuff */}
    </Form>
  )
}

With the callback, I don't need a new component. I can write the form inline, and pass the close callback to onSuccess:
export function EditBucketButton({ bucket }) {
  return (
    <Modal
      title="edit bucket"
      renderContent={({ close }) => (
        <Form name="edit-bucket" action={`/buckets/${bucket.id}`} method="patch" onSuccess={close}>
          {/* form stuff */}
        </Form>
      )}
    />
  )
}

Summary: the callbacks seem valuable as a convenient way to run side effects in response to a form submission.
In this specific case, I could refactor Modal to just accept props, then I could have all of the state + the effect in one component, but writing an effect for each instance of this still doesn't sound like fun 😅 That, and there are other APIs that work like this, as a point of reference.

Fine by me. We can simply put the effects in Form instead, and pass the full state as param to the callback.

I have some free time, so I'll add this one in 🙂


DEP Bump framework dependency

Backport cherry-pick of https://github.com/silverstripe/silverstripe-elemental/pull/1193
We've decided to release this in 5.2 so as to fix the broken --prefer-lowest build

Not needed


ciao-deploy: cleanup/ciao.yml playbook breaks when deploying from a target host

I ran the cleanup/ciao.yml playbook from the ciao-deploy container, running on the node I designated as controller. As part of the cleanup, the playbook apparently stopped the docker service on the controller node itself, killing the container from which I was running the playbook. We could document this as a limitation, but it would be nice to be able to deploy a cluster from one of the machines that will eventually be a part of it.

@bwarden if you were using the ciao-deploy container based on some instance of current docu, can you let us know so we can fix it?

Until the patch is pushed, the container is still in the public-facing documentation: https://clearlinux.org/documentation/ciao-deploy.html

Ansible removed.


Setup the Authentication Framework

Update views.py and connect functionality from the login module/registration module to the db.

Complete


Timber stetho

This adds ability to use the Stetho console for logging output from Jasonette.
Currently only console.* output from JS with expression templates is using this.
The setting is controlled via a bool resource and is defaulted to on.

@gliechtenstein I've rebased now onto develop so the PR should be good to go.

@maks awesome, thanks! 💥
Is this on the documentation as well?

@gliechtenstein yes it is, though its just a single line atm:

...and see output from any uses of console.log in your template expressions.

Do you think it needs to be a bit more prominent in the docs?

@maks yes I think that would make a lot of difference, maybe adding an example as a code format. I totally missed that part the first time and this sounds like a very useful feature and deserves more prominent coverage IMO

sorry for the delay, I made the console usage a bit more prominent: https://github.com/Jasonette/documentation/pull/70


Rebuild stdlib-list 0.8.0 for py311

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_e582kx86ue/clone/recipe/meta.yaml:1: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_e582kx86ue/clone/recipe/meta.yaml:1: missing_python: For pypi packages, python should be present in the host and run sections. Missing in host
ERROR: /tmp/abs_e582kx86ue/clone/recipe/meta.yaml:1: missing_python_build_tool: Python packages require a python build tool such as setuptools.
ERROR: /tmp/abs_e582kx86ue/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: /tmp/abs_e582kx86ue/clone/recipe/meta.yaml:46: http_url: http://github.com/jackmaney/python-stdlib-list is not https
INFO: /tmp/abs_e582kx86ue/clone/recipe/meta.yaml:46: invalid_url: https://jackmaney.github.io/python-stdlib-list : URL domain redirect jackmaney.github.io ->  www.jackmaney.com
Errors were found

Details

This build will create artifacts only for python 3.11 that's why I'm not bumping the build number. It won't affect other artifacts

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6fvi2xi6qq/clone/recipe/meta.yaml:1: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_6fvi2xi6qq/clone/recipe/meta.yaml:1: missing_python_build_tool: Python packages require a python build tool such as setuptools.
ERROR: /tmp/abs_6fvi2xi6qq/clone/recipe/meta.yaml:1: missing_python: For pypi packages, python should be present in the host and run sections. Missing in host
ERROR: /tmp/abs_6fvi2xi6qq/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: /tmp/abs_6fvi2xi6qq/clone/recipe/meta.yaml:46: http_url: http://github.com/jackmaney/python-stdlib-list is not https
INFO: /tmp/abs_6fvi2xi6qq/clone/recipe/meta.yaml:46: invalid_url: https://jackmaney.github.io/python-stdlib-list : URL domain redirect jackmaney.github.io ->  www.jackmaney.com
Errors were found


[SvgIcon] Allow viewBox to inherit from Component through inheritViewBox prop

[X] I have followed (at least) the PR section of the contributing guide.

Fix #18782

Implemented the solution suggested in Olivier's comment.
Based on suggested implementation in #27110

I only updated the SvgIcon API docs with the new logic implemented here. Do you think that this deserves to be mentioned in the SvgIcon docs?

In great need of this feature!

Closing in favor of https://github.com/mui-org/material-ui/pull/29954 The later seems more complete.


Support official way to include Qt Headers

It seems that the official documentation has ways of including stuff that is not supported by rules_qt6 https://doc.qt.io/qt-6/qtwidgets-tutorials-notepad-example.html
For instance, for the QSettings class, we need to include #include "QtCore/QSettings" where the official Qt documentation says #include <QSettings> is sufficient.
Expected fix: Add a demo to the test folder that uses for instance #include <QSettings>. Fix the rules to make this working an all platforms (Windows, macOS, Linux).

This should be a one-liner (at least for linux):
diff --git qt_linux_x86_64.BUILD qt_linux_x86_64.BUILD
index ffa968a..e52b8ae 100644
--- qt_linux_x86_64.BUILD
+++ qt_linux_x86_64.BUILD
@@ -7,7 +7,7 @@ load("@rules_qt//:qt_libraries.bzl", "QT_LIBRARIES")
             "lib/lib%s.so*" % library_name,
         ]),
         hdrs = glob(["include/%s/**" % include_folder]),
-        includes = ["include"],
+        includes = ["include", "include/%s" % include_folder],
         target_compatible_with = ["@platforms//os:linux"],
         visibility = ["//visibility:public"],
     )

Fixed by https://github.com/Vertexwahn/rules_qt6/pull/16
Thanks @ankit-agarwal1999 and @dieortin!


Invalid proj results from rasterio CRS in pyproj > 2.0

Code Sample, a copy-pastable example if possible
import pyproj
import rasterio
print('Pyproj version: ', pyproj.__version__)
print('rasterio version: ', rasterio.__version__)

p1 = pyproj.Proj({'init': 'epsg:4326'})
p2 = pyproj.Proj(rasterio.crs.CRS({'init': 'epsg:4326'}))

pout = pyproj.Proj({'init': 'epsg:32632'})

print('Expected: ', pyproj.transform(p1, pout, 10., 46.))
print('With rio CRS: ', pyproj.transform(p2, pout, 10., 46.))

Problem description
Output with pyproj < 2:
Pyproj version:  1.9.6
rasterio version:  1.0.24
Expected:<PHONE_NUMBER>690205, 5094533.591105094)
With rio CRS:<PHONE_NUMBER>690205, 5094533.591105094)

With latest pyproj:
Pyproj version:  2.2.0
rasterio version:  1.0.24
Expected:<PHONE_NUMBER>690205, 5094533.591105094)
With rio CRS:  (4849477.3819811465, 1378793.4460353532)

Expected Output
This is a bad bug... I took me ages to debug, because we initialize Proj instances from rasterio Dataset objects.
Environment Information

pyproj version 2.2.0
PROJ version 6.1.0
PROJ data directory /home/mowglie/.pyvirtualenvs/py3/lib/python3.5/site-packages/pyproj/proj_dir/share/proj
Python version 3.5.2
Operation System Information Linux-4.15.0-50-generic-x86_64-with-LinuxMint-18.3-sylvia

Installation method

pip

Hi @fmaussion, you have run into the axis swapping changes in PROJ 6+. When you initialized from the rasterio CRS, it has the axis order swapped, so latitude comes first in the transformation.
>>> from pyproj import Transformer, CRS
>>> from rasterio.crs import CRS as RCRS
>>> pcrs = CRS("+init=epsg:4326")
>>> pcrs
<Geographic 2D CRS: +init=epsg:4326 +type=crs>
Name: WGS 84
Axis Info [ellipsoidal]:
- lon[east]: Longitude (degree)
- lat[north]: Latitude (degree)
Area of Use:
- name: World
- bounds: (-180.0, -90.0, 180.0, 90.0)
Datum: World Geodetic System 1984
- Ellipsoid: WGS 84
- Prime Meridian: Greenwich
>>> rcrs = CRS(RCRS(init="epsg:4326"))
>>> rcrs
<Geographic 2D CRS: EPSG:4326>
Name: WGS 84
Axis Info [ellipsoidal]:
- Lat[north]: Geodetic latitude (degree)
- Lon[east]: Geodetic longitude (degree)
Area of Use:
- undefined
Datum: World Geodetic System 1984
- Ellipsoid: WGS 84
- Prime Meridian: Greenwich

>>> transformer = Transformer.from_crs(RCRS(init="epsg:4326"), 'epsg:32632')
>>> transformer.transform(46, 10)
(577432.1825690205, 5094533.591105094)

You can make it so longitude comes first by passing in always_xy=True.
>>> transformer = Transformer.from_crs(RCRS(init="epsg:4326"), 'epsg:32632', always_xy=True)
>>> transformer.transform(10, 46)
(577432.1825690205, 5094533.591105094)

There are many things that might throw you off in the transition, so I would recommend reading:
https://pyproj4.github.io/pyproj/latest/examples.html
https://pyproj4.github.io/pyproj/latest/gotchas.html
https://proj.org/faq.html#why-is-the-axis-ordering-in-proj-not-consistent
https://pyproj4.github.io/pyproj/latest/api/transformer.html

There are many things that might throw you off in the transition

OK, but from a user's point of view this is quite a silent backwards incompatible change on valid code (making a pyproj Proj from a rio file). (similarly, yesterday I noticed that Proj.is_latlong disappeared, which I believe was silent  - or I missed the deprecation cycle, also possible).
What was the rationale for not keeping Proj backwards compatible and introduce a deprecation cycle? This would've brought me to use CRS much earlier...

We are definitely doing our best to help with this transition and understand that it will be a little rocky :).

OK, but from a user's point of view this is quite a silent backwards incompatible change on valid code (making a pyproj Proj from a rio file)

The reason for not raising warnings or errors on the axis order swapping is that pyproj chose to follow PROJ in defaulting to the axis order of the CRS (so the behavior is now correct and we don't want to raise errors on correct behavior). Additionally, since the always_xy=True option was just barely introduced in 2.2.0 (https://pyproj4.github.io/pyproj/stable/history.html) with the support being added in PROJ 6.1.0, the default behavior is consistent with pyproj 2+. This will indeed cause troubles for many who are upgrading and we are attempting to address this by documentation.

I noticed that Proj.is_latlong disappeared

This has been deprecated since pyproj 2.0.0
https://github.com/pyproj4/pyproj/blob/58b4f49da12794989fc8cb397dc0cd2ecd221a6d/pyproj/__init__.py#L375-L382
and was recently removed in pyproj 2.2.0.


Ignore the case when parsing Epub2NcxPageTargetType from NCX file

I've fixed issue with parsing Epub2NcxPageTargetType from NCX file. Previously it wasn't ignoring attribute case and all page targets were created with UNKNOWN type.

Good catch, thank you! I'll release a new version of the Nuget package within a day.

Nuget package has been published.


Allow embedding of products web services with security headers

Is your feature request related to a problem? Please describe.
For example, I can't embed a website like Klipper Fluidd to manage a 3D printer within Thinger.io, receiving the following response:
502 Bad Gateway
Referrer Policy: strict-origin-when-cross-origin
Describe the solution you'd like
The website should be visible.
Describe alternatives you've considered
None
Additional context
None

Fixed on 5.3.0


Update init cli-command and deployment and test templates

Codecov Report

Merging #222 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #222      +/-   ##
==========================================
- Coverage   97.48%   97.48%   -0.01%
==========================================
  Files          77       77
  Lines        3021     3019       -2
==========================================
- Hits         2945     2943       -2
  Misses         76       76

Impacted Files
Coverage Δ

...i-commands/debugger/etherlime-debug-utils/index.js
100% <ø> (ø)
:arrow_up:

...commands/compiler/vyper-compiler/vyper-compiler.js
100% <ø> (ø)
:arrow_up:

packages/etherlime/cli-commands/init/init.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17ed62a...bd8fef3. Read the comment docs.


I had a problem in vs

Who know how to fix this? Declaration or statement expected.ts(1128)

I don't know what happened...

LINK TO MY NEW PROJECTS FIREBASE IF U WANT TO WORK WITH IT FOR A SOCIAL WEBSITE APP:
apiKey: "AIzaSyC-LVQT1Z90FIrxAS5Cm-9JFSyWP8nBz0U",
authDomain: "kwitter-fed19.firebaseapp.com",
databaseURL: "https://kwitter-fed19-default-rtdb.firebaseio.com",
projectId: "kwitter-fed19",
storageBucket: "kwitter-fed19.appspot.com",
messagingSenderId: "958918182502",
appId: "1:958918182502:web:d1edcf63f4c822d11d4fa7"v

@GitHubBoy88 This is not the appropriate place to ask about his.
You may ask on Stack Overflow
Also, never share your API keys anywhere.
@diegohaz / @GitHubBoy88  Delete his/your last comment


Create Employee management system

Describe the feature and motivation
Motivation
Although we are going to have only one Employee(Bluey) we still need
a management system.
Requirements

<<Employee>>

id

Manager class

id
the ability to add/remove new menu items
the ability to update prices
the ability to handle reservations

Additional context
#14 is a dependency

I'm going to start working on this issue, if anyone has already started working on it please let me know.


Installing WasiEnv requires pip

This should be mentioned on the README in the installation section 😄

on a side note pip has now been removed from Debian and Ubuntu (20.04).
Moving to Python3 and Pip3 is needed now 😃

Bump.

@syrusakbary maybe you could take a look?

Thank you @syrusakbary ! :smile:


error yo meanjs:crud-module properties     when generating yo meanjs:crud-module name

It always gives this error
Unknown provider: menuServiceProvider <- menuService
which is easy to fix but can you make this as known issue and fix it in next version ?

Hi, I have the same problem, after generating a crud module I got a blank page, any suggestion ? thanks

See this PR for a solution to this issue.
Since this issue is related to the MEANJS Yo Generator, if the above fix doesn't work open a new issue in that repo.

Page doesn't load after i choose from menu. there is error found like view can't be loaded and error 404.i use mean 4.0. anyone have met with this problem?

@rifrayugo Can you provide more details on your issue? Code references, console errors, etc.

I create new module use yo meanjs:crud-modue. But i got blank page and i change menuConfig.$inject = ['menuService']; with
menuConfig.$inject = ['Menus'];
And page already appears with menus, when i click the menu page doesn't load form. And when i check on console i found this error

+1 @mleanos

1 @mleanos

@rifrayugo It looks as either the configuration is referencing a non-existent view. Does list-patients.client.view.html exist at that location inside your new module? Perhaps the generator created the file by a different name?


Use updated zxcvbn python library.

I've worked to create an updated zxcvbn python library based on the newest JS codebase and to also support python3. My port is now listed as the suggested python port on the main zxcvbn repository readme. Since Django will soon not support python2 you may want to consider changing your dependency to my library. Let me know if I can help in any way.
https://github.com/dwolfhub/zxcvbn-python

Oh this is great! I will take a look to see what is needed to integrate your library into this app :) Thanks for you work :+1:

I think I'll use the new feature in Django 1.9 (https://docs.djangoproject.com/en/1.10/topics/auth/passwords/#module-django.contrib.auth.password_validation) to add a ZXCVBN password validator.
The PasswordField for forms will validate password client-side with zxcvbn's javascript (need to update it). The developer will be able to extend the password validation server-side with other user inputs with a call from the form clean method: validate_password(password, User(field1=value1, ...)). The fields given to user should correspond to the validator's fields specified in settings.
By default, the server-side validation will check the password without any other user inputs (can't pass/predict them).

Sounds good to me.

@Pawamoy
custom validator, using python-zxcvbn could look like this:
from django.core.exceptions import ValidationError
from django.utils.translation import ugettext as _
from zxcvbn import zxcvbn

class ZxcvbnValidator(object):
    def __init__(self, min_score=2):
        self.min_score = min_score

    def validate(self, password, user=None):
        results = zxcvbn(password)
        if results.get('score', 0) < self.min_score:
            feedback = ', '.join(results.get('feedback', {}).get('suggestions', []))
            raise ValidationError(
                _(feedback),
                code='password_too_weak',
                params={},
            )

    def get_help_text(self):
        return _(
            "Your password must be stronger."
        )

and then in the settings.py something like:
AUTH_PASSWORD_VALIDATORS = [
    {
        'NAME': 'django-zxcvbn-password.ZxcvbnValidator'
    },
]

I have generally used 3 as a minimum.
0 # too guessable: risky password. (guesses < 10^3)
1 # very guessable: protection from throttled online attacks. (guesses < 10^6)
2 # somewhat guessable: protection from unthrottled online attacks. (guesses < 10^8)
3 # safely unguessable: moderate protection from offline slow-hash scenario. (guesses < 10^10)
4 # very unguessable: strong protection from offline slow-hash scenario. (guesses >= 10^10)

when you put it that way, 3 does sound like a better default

Okay I've pushed some commits to implement this. Django 1.8 is not supported anymore. Let me know if something is wrong so I can fix it before releasing on PyPI.


Revisit styling on /forum

On larger screens, the alternating rows are too starkly different. Consider removing the transparency because the gray background is too dark.

Agreed, thanks!


AutoPublishAlias is not triggered for environment variable changes

Description:
Changing or adding/removing environment variables for a function does not cause a new version to be published when using AutoPublishAlias.
Steps to reproduce the issue:

Deploy a SAM template with an AWS::Serverless::Function resource, with AutoPublishAlias set, and including an environment variable:

HelloWorldFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: hello_world/
      Handler: app.lambda_handler
      Runtime: python3.8
      AutoPublishAlias: live
      Environment:
        Variables:
          TestKey: TestVal1

Change TestVal1 to TestVal2.
Run sam deploy .

Observed result:
The lambda function is updated with the new environment variable, but no new version is published, and the defined alias still points to the last published version.
Expected result:
A new function version is published, and the defined alias is updated to point to it.

If the lambda function is invoked, does it have the old or new value for the environment variable?

It looks like we can add the Environment dictionary to the hash that gets computed to determine if a new version needs to be published.
Section of code to update: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessapi

When invoking via api gateway, the "old" version gets invoked.
@szilveszter Did you paste the right url? Was expecting a link to a section of code but your link goes to documentation.

@cakepietoast  @keetonian This is similar to the #1267 where environment variables stored in Secrets Manager that are changed don't trigger a new version of the lambda.

Closing this as it was resolved with #1310.

@cakepietoast this still doesn't work if the environment variable change was due to an updated value of a referenced parameter