Puppy Linux Discussion Forum

KLV-Airedale-beta22
Kennel Linux Void Airedale Beta 22 566 MiB download size ->
KLV-Airedale-beta22
SHA1-MD5.txt

This is KLV-Airedale-beta21 with a kernel version 6.0.1-KLV bumping the version to beta22

Kernel 6.0.1-KLV is built for KLV-Airedale and has no AUFS. It is configured for low-latency SMP PREEMPT DYNAMIC with Overlayfs and NTFS support built in, as is virtualization support.

Only changes are a routine rolling system update and the addition of a xfce4 desktop tiling configuration. A tip from @wiak for configuring Tiling windows done with the Super (Windows) key and an up, down, left, right, home, pgup, pgdown or end key.

gxmessage in the default rootfs.

save2flash has been expanded to handle persistence on FAT32 and NTFS partitions.
The mksplash GUI utility to create splash notification banners.

has the latest FirstRib skeleton initrd v6.0-rc1 supplying the initrd.gz
and is currently equipped with the kernel 6.0.1-KLV (no AUFS support).
00modules-6.0.1-KLV.sfs has the file structure -> /usr/lib/modules

The latest initrd.gz brings vFat and NTFS formatted partition support to KLV, allowing persistence on NTFS/vFat systems as well as the usual /ext2/ext3/ext4 /swap support.

• Beta22 has wiak's FirstRib skeleton initrd v6.0-rc1 and w_init_6.0-rc1

• the kernel's 00Module SFS file structure has been modified by moving /lib/modules to /usr/lib/modules

• included htop

• created a symlink /root/spot with the target /home/spot

• Auto login cleaned up.

• includes also the logout logic provided by fredx181 gives true mulit-user support.

• replaced loop.cfg to the most recent modifications.

• kernel 6.0.1-KLV (overlayfs built in and no AUFS) is used.

• added gtkhash

Plus the other important improvements contributed by the KLV team.

Added @fredx181's save2flash utility that can be used when KLV is started in RAM2 mode to perform session saves on demand for persistence.
This is similar to PUPMODE13 in Puppy Linux.

fredx181's swap partition enable script includes the latest revisions and also added are the packages

• mime-add-1.0_0.noarch.xbps

• edit-sfs-1.0_0.noarch.xbps

KLV-Airedale-beta21 is able to load squash SFS packages on the fly or during the boot sequence.
Squash files and ISO images can be opened from the file manager and the read the contents.

• can run with rootfs, 01fimware and 00module SFS files as uncompressed directories.

• Also able to load compressed and/or decompressed directories,
  once a 2 digit prefix is added to the file name.

• It is possible to mix using compressed squash files and uncompressed directories.

Also can be downloaded from https://rockedge.org/kernels in ISO->Kennel_Linux->Airedale

@wiak This new kernel 6.0.1-KLV has both new modules and firmware SFS files just successfully created with the kernel-kit from the testing branch of woof-CE and modified to run with the current skeleton initrd.gz

Issue seems to be that I need modules for kernel -> audio -> soc ->sof and KLV seems to have these missing

Can you test beta22 in the same way and check if the modules are now present?

rockedge wrote: ↑Mon Oct 17, 2022 3:21 am

@wiak This new kernel 6.0.1-KLV has both new modules and firmware SFS files just successfully created with the kernel-kit from the testing branch of woof-CE and modified to run with the current skeleton initrd.gz

Issue seems to be that I need modules for kernel -> audio -> soc ->sof and KLV seems to have these missing

Can you test beta22 in the same way and check if the modules are now present?

Just tried beta22, but no, sorry, still no modules at usr/lib/modules > 6.0.1-KLV > kernel > sound > soc > sof (check vdpup and you will see these modules are available there, which is why I think sound works with that on my laptop).

and that seems to be required for my laptop to use microphone input device. Audio output does work okay, but not using sof as far as I can see:

root# dmesg | grep snd
[ 12.030065] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 12.030084] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 12.155403] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 12.268940] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC236: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 12.268942] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 12.268944] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 12.268944] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 12.268945] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 12.268946] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19

Despite above mentioning Mic, it doesn't appear in pavucontrol and sound recording not working. Maybe sof-firmware not installed (and you have sof built into kernel rather than modules?). However, I can't install sof-firmware because currently getting following repo error (not sure if KLV bug or something wrong with upstream Void repos at the minute...):

root# xbps-install -Sy             
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
ERROR: [reposync] failed to fetch file `https://repo-default.voidlinux.org/current/x86_64-repodata': Connection refused
[*] Updating repository `https://mirror.clarkson.edu/voidlinux/current/nonfree/x86_64-repodata' ...

I actually know next to nothing about Intel sof so just reporting my mic input not working, but working when swapping over to use vupup kernel/firmware/modules instead

EDIT: Here is what dmesg shows me when I use vupup kernel/firmware/modules with KLV beta22 instead:

root# dmesg | grep snd
[ 11.172391] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 11.172415] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 11.775201] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -2
root#

Still getting the Void repo error at the moment though, but that nothing to do with the snd issue - maybe just upstream Void issue: something odd though since using browser I see https://mirror.clarkson.edu/voidlinux/current/nonfree/ without issue and x86_64-repodata file seems to be there...
EDIT2: Ah, https://repo-default.voidlinux.org/current/ isn't showing in browser. Maybe it is trying to find https://repo-fi.voidlinux.org which isn't loading either at the moment in my browser - so likely just an upstream Void repo glitch. I've seen similar happen before with Void repos...

@wiak I have successfully installed sof-firmware from the Void Linux repos

xbps-install -Sy sof-firmware

Also works using the OctoXBPS package manager GUI.

I think I can include this in beta21 and/or beta22 rootfs pretty easily.

I have no way of testing this out though for sure!

UPDATE: I have improved the beta22 rootfs and repackaged beta22 ISO to include the changes.

Also now can launch .sh scripts via left mouse click in Thunar windows.

KLV-Airedale-beta22 is available for download! Check the first post for the links.

Completed booting todays version's ISO file via QEMU & bare-metal vai SG2D without any issues getting to desktop nor any issues of it interacting with any of the system's hardware components. ALL tests were done using the default KLV Menu boot stanza; 'RAM0'.

@wiak I ask: When you boot QEMU with the following, are you getting sound on your host desktop from the VM? ... I am: And Youtube works well.
qemu-system-x86_64 -enable-kvm -m 2G -vga std -smp 2 -device AC97 -cdrom /root/Erasedis/KLV-Airedale-beta22.iso

rockedge wrote: ↑Mon Oct 17, 2022 12:35 pm

@wiak I have successfully installed sof-firmware from the Void Linux repos

Code: Select all

xbps-install -Sy sof-firmware

I don't think that is the problem rockedge.

I have managed to install sof-firmware before on KLV. But it doesn't include the modules in /usr/lib/modules/KLVxxx/kernel/sound/soc/sof

I'll try again later today with pristine newest beta22, but unless all of same is somehow built into the kernel then won't work on my computer. But doesn't matter to me since as I say vupup kernel/firmware/modules combination works fine once substituted in.

Clarity, I am not using QEMU.

Remember, sound output and everything else is working fine on my machine with supplied KLV kernel and so on; youtube works fine - it is sound recording, which needs that sof device detection that isn't working.

Pristine newest beta22 install. Notice sof-firmware already installed. But sound recording still not working sorry. I think special kernel configuration needed for sof DSP digital mics; I came across that the other day, but can't remember source. @dimkr maybe knows and could clarify

Maybe here helps? (also refer my next posts viewtopic.php?p=69722#p69722 and viewtopic.php?p=69724#p69724):

https://forums.gentoo.org/viewtopic-p-8 ... 08#8670384

https://forums.gentoo.org/viewtopic-p-8 ... ml#8688277

https://www.google.com/url?sa=t&source= ... q4qfswfXOh

https://github.com/torvalds/linux/blob/ ... of/Kconfig

Sof kernel config seems a bit of a nightmare, hence if dimkr kernel config works best to duplicate maybe.

Sound output and mic input also working on my Zorin lite full-install. Here is lspci -k relevant info:

00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20)
	Subsystem: Hewlett-Packard Company Device 87df
	Kernel driver in use: sof-audio-pci-intel-tgl
	Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

On Sunday I did a new manual frugal install of beta 21 with 5.16 kernel. It booted, but the touchpad on my Asus laptop didn't function. I used a USB wireless mouse. This morning I saw the beta 22 with 6.0.1 kernel was released. The results were the same. with a non functioning touchpad. Running lsmod shows no module loaded. I followed wiak's lead and swapped in the vanilla Upup kernel, all working well now.

root# lsmod | grep hid
root# dmesg | grep hid
[    0.496177] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR0, rdevid:160
[    0.496178] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR1, rdevid:160
[    0.496179] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR2, rdevid:160
[    0.496179] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR3, rdevid:160
[    0.532011] hid: raw HID events driver (C) Jiri Kosina
[    0.532068] usbcore: registered new interface driver usbhid
[    0.532068] usbhid: USB HID core driver
[    0.986002] hid-generic 0003:2389:00A6.0001: input,hidraw0: USB HID v2.00 Mouse [Usb Compliant device Usb Compliant device] on usb-0000:04:00.4-1/input0
[    1.047781] hid-generic 0003:2389:00A6.0002: input,hidraw1: USB HID v2.00 Keyboard [Usb Compliant device Usb Compliant device] on usb-0000:04:00.4-1/input1
[    1.051989] hid-generic 0003:2389:00A6.0003: hiddev96,hidraw2: USB HID v2.00 Device [Usb Compliant device Usb Compliant device] on usb-0000:04:00.4-1/input2
[   61.393353] hid-generic 0003:0128:6901.0004: input,hidraw0: USB HID v1.10 Keyboard [HID 0128:6901] on usb-0000:04:00.4-1/input0
[   61.456308] hid-generic 0003:0128:6901.0005: input,hidraw1: USB HID v1.10 Mouse [HID 0128:6901] on usb-0000:04:00.4-1/input1
root# 

Output when using Vanilla Upup 5.15.x kernel:

root# lsmod | grep hid
hid_multitouch         28672  0 
hid_generic            16384  0 
i2c_hid_acpi           16384  0 
mac_hid                16384  0 
i2c_hid                32768  1 i2c_hid_acpi
root# dmesg | grep hid
[    0.078839] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR0, rdevid:160
[    0.078840] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR1, rdevid:160
[    0.078841] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR2, rdevid:160
[    0.078841] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR3, rdevid:160
[    1.753597] hid: raw HID events driver (C) Jiri Kosina
[    1.753663] usbcore: registered new interface driver usbhid
[    1.753665] usbhid: USB HID core driver
[    6.798537] hid-generic 0003:0128:6901.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 0128:6901] on usb-0000:04:00.4-1/input0
[    6.858488] hid-generic 0003:0128:6901.0002: input,hidraw1: USB HID v1.10 Mouse [HID 0128:6901] on usb-0000:04:00.4-1/input1
[    6.859256] hid-generic 0018:04F3:3134.0003: input,hidraw2: I2C HID v1.00 Mouse [ASUE140A:00 04F3:3134] on i2c-ASUE140A:00
[    7.244986] hid-multitouch 0018:04F3:3134.0003: input,hidraw2: I2C HID v1.00 Mouse [ASUE140A:00 04F3:3134] on i2c-ASUE140A:00
root# 

TerryH wrote: ↑Tue Oct 18, 2022 1:08 am

On Sunday I did a new manual frugal install of beta 21 with 5.16 kernel. It booted, but the touchpad on my Asus laptop didn't function. I used a USB wireless mouse. This morning I saw the beta 22 with 6.0.1 kernel was released. The results were the same. with a non functioning touchpad. Running lsmod shows no module loaded. I followed wiak's lead and swapped in the vanilla Upup kernel, all working well now.

Try also these commands in case help track this one down (difference between KLV and Vupup kernel/modules etc):

libinput list-devices

dmesg | grep usb

Don't know how relevant (or if), but came across:

https://bugzilla.kernel.org/show_bug.cgi?id=214597

2. In the kernel config, enable CONFIG_X86_INTEL_LPSS and make sure to enable all TIGERLAKE and TGL (ones that are specifically for Tiger-Lake only) options including CONFIG_PINCTRL_TIGERLAKE.

3. In the kernel config, disable all RMI4 options, like CONFIG_RMI4_CORE. For SYNAPTICS options, only keep MOUSE_PS2_SYNAPTICS enabled. Enable CONFIG_I2C_DESIGNWARE_CORE and CONFIG_I2C_DESIGNWARE_PLATFORM

Seems to me that kernel config is getting increasingly complicated - best for creating huge kernels I would think would be to first consult official upstream Debian kernel configs for the likes of the above configurations before adding extra for detecting drive media. I haven't built kernels myself for years though. Still think following might be best pointer to solution I've come across thus far: https://forums.gentoo.org/viewtopic-p-8 ... 218715ad9a

I'm particularly suspecting CONFIG_X86_INTEL_LPSS (and anything related to TIGERLAKE and TGL)

https://www.kernelconfig.io/config_x86_intel_lpss
https://cateee.net/lkddb/web-lkddb/X86_INTEL_LPSS.html
https://cateee.net/lkddb/
https://cateee.net/lkddb/web-lkddb/

wiak wrote: ↑Tue Oct 18, 2022 2:33 am

TerryH wrote: ↑Tue Oct 18, 2022 1:08 am

On Sunday I did a new manual frugal install of beta 21 with 5.16 kernel. It booted, but the touchpad on my Asus laptop didn't function. I used a USB wireless mouse. This morning I saw the beta 22 with 6.0.1 kernel was released. The results were the same. with a non functioning touchpad. Running lsmod shows no module loaded. I followed wiak's lead and swapped in the vanilla Upup kernel, all working well now.

Try also these commands in case help track this one down (difference between KLV and Vupup kernel/modules etc):

Code: Select all

libinput list-devices

dmesg | grep usb

Thanks for the reply, I checked libinput, to check that tapping was disabled. So far using the vupup kernel is without issue. Everything is working well, keyboard(including sound and screen brightness Fn keys), touchpad, wifi, sound including microphone, all good.

I've installed Audacious and currently installing Cups, which after issuing command cupsd to start printer daemon appears to so far be working. I haven't connected to my printer yet, stopped to type this.

So far excellent results. So thanks @rockedge, your continued development work is producing an excellent distribution.

Regarding sof sound (Sound Open Firmware):

https://thesofproject.github.io/latest/ ... ction.html

SOF is available on Intel PCI devices starting with Gemini Lake, and has since been the only solution provided by Intel for the following platforms: Comet Lake, Ice Lake, and Tiger Lake.
...
User space and filesystem requirements¶

Selecting the SOF driver is not enough. Audio is properly configured only if the following elements are present on the file system.

Don't know if following helps or is relevant (I'd check dimkr config first since works...):

https://thesofproject.github.io/latest/ ... ratch.html

Step 6. Build Linux kernel¶

Sound Open Firmware uses the Linux kernel dev branch, and it must work with other dev branch firmware and topology. This short section shows how to build Debian kernel packages tested on Ubuntu in a small number of commands.

I have no idea, and even less idea about kconfig:
https://thesofproject.github.io/latest/ ... on-kconfig
https://github.com/thesofproject/kconfi ... README.md/

I note:

The Legacy HD-Audio driver and SOF driver can coexist in one Linux distribution. The snd-intel-dspcfg kernel driver implements logic to select the correct driver based on ACPI table contents and platform capabilities detected at runtime. For example, if no specific configuration is defined in ACPI tables and digital microphones are directly attached to the PCH (Intel Platform Control Hub), an audio DSP is required and thus the SOF driver is chosen automatically.

My system seems to use digital microphones, so I guessing sof audio DSP required, and vupup kernel/modules/firmware appears to provide that support.

Not sure again, but following kernel config info looks hopeful: https://github.com/thesofproject/kconfi ... -defconfig

https://www.spinics.net/lists/alsa-devel/msg126829.html

Distribution kernels are a good reference when building on your own, and
we in SOF also maintain example kconfig settings for typical systems.
Here's the bit for systems with DSP and HDA codecs:
https://github.com/thesofproject/kconfi ... -defconfig

More info at:
https://github.com/thesofproject/kconfig/

wiak wrote: ↑Mon Oct 17, 2022 11:53 pm

@dimkr maybe knows and could clarify

Look at https://github.com/puppylinux-woof-CE/w ... get_sof.sh, it's a very short script that creates a trimmed set of firmware
and topology files, given a directory containing kernel modules.

dimkr wrote: ↑Tue Oct 18, 2022 8:30 am

wiak wrote: ↑Mon Oct 17, 2022 11:53 pm

@dimkr maybe knows and could clarify

Look at https://github.com/puppylinux-woof-CE/w ... get_sof.sh, it's a very short script that creates a trimmed set of firmware
and topology files, given a directory containing kernel modules.

I looked at the above script per your link to it. But I don't myself think it is likely to be the sof-firmware installable in KLV via Void Linux package manager that is causing any issue, but (as I've already detailed in many posts above) rather missing modules and possible kernel configs related to sof - I was more interested in any special sof configurations you used when building your kernel. Like I said, it is years since I built any kernels myself, but do note there are sof-related configs and also I have no idea how rockedge's build does not seem to contain any sof-related modules.

I could be wrong, but seems unlikely to me to be a firmware issue - rather a kernel config or modules related issue - so that script would not point to any answer unfortunately. Hope it does. I'll leave that between yourself and rockedge as kernel builders.

But, as I said, maybe something to do with (someone old link though): https://github.com/thesofproject/kconfi ... -defconfig

I know nothing about Puppy Linux kernel kit, but quick glance certainly suggested some kernel configs related to SOF, but I don't know if above discussed vupup kernel uses anything different in this regard; seems like KLV kernel build does though - since don't see the sof-related modules for KLV. The following woof-CE kernel kit extract appears to be for a 5.15.4-x86_64 kernel build whereas my vupup install uses 5.15.56 so may or may not be differently configured overall:

https://github.com/puppylinux-woof-CE/w ... 6_64#L6487

# CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH is not set
CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m
CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m
CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98357A_MACH=m
# CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98927_MACH is not set
# CONFIG_SND_SOC_INTEL_KBL_RT5660_MACH is not set
# CONFIG_SND_SOC_INTEL_GLK_DA7219_MAX98357A_MACH is not set
CONFIG_SND_SOC_INTEL_GLK_RT5682_MAX98357A_MACH=m
CONFIG_SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m
CONFIG_SND_SOC_INTEL_SOF_RT5682_MACH=m
# CONFIG_SND_SOC_INTEL_SOF_CS42L42_MACH is not set
# CONFIG_SND_SOC_INTEL_SOF_PCM512x_MACH is not set
# CONFIG_SND_SOC_INTEL_CML_LP_DA7219_MAX98357A_MACH is not set
# CONFIG_SND_SOC_INTEL_SOF_CML_RT1011_RT5682_MACH is not set
# CONFIG_SND_SOC_INTEL_SOF_DA7219_MAX98373_MACH is not set
# CONFIG_SND_SOC_INTEL_EHL_RT5660_MACH is not set
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
# CONFIG_SND_SOC_MTK_BTCVSD is not set
CONFIG_SND_SOC_SOF_TOPLEVEL=y
CONFIG_SND_SOC_SOF_PCI_DEV=m
CONFIG_SND_SOC_SOF_PCI=m
# CONFIG_SND_SOC_SOF_ACPI is not set
# CONFIG_SND_SOC_SOF_DEBUG_PROBES is not set
# CONFIG_SND_SOC_SOF_DEVELOPER_SUPPORT is not set
CONFIG_SND_SOC_SOF=m
CONFIG_SND_SOC_SOF_PROBE_WORK_QUEUE=y
CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL=y
CONFIG_SND_SOC_SOF_INTEL_HIFI_EP_IPC=m
CONFIG_SND_SOC_SOF_INTEL_ATOM_HIFI_EP=m
CONFIG_SND_SOC_SOF_INTEL_COMMON=m
CONFIG_SND_SOC_SOF_MERRIFIELD=m
CONFIG_SND_SOC_SOF_INTEL_APL=m
CONFIG_SND_SOC_SOF_APOLLOLAKE=m
CONFIG_SND_SOC_SOF_GEMINILAKE=m
CONFIG_SND_SOC_SOF_INTEL_CNL=m
CONFIG_SND_SOC_SOF_CANNONLAKE=m
CONFIG_SND_SOC_SOF_COFFEELAKE=m
CONFIG_SND_SOC_SOF_COMETLAKE=m
CONFIG_SND_SOC_SOF_INTEL_ICL=m
CONFIG_SND_SOC_SOF_ICELAKE=m
CONFIG_SND_SOC_SOF_JASPERLAKE=m
CONFIG_SND_SOC_SOF_INTEL_TGL=m
CONFIG_SND_SOC_SOF_TIGERLAKE=m
CONFIG_SND_SOC_SOF_ELKHARTLAKE=m
CONFIG_SND_SOC_SOF_ALDERLAKE=m
CONFIG_SND_SOC_SOF_HDA_COMMON=m
CONFIG_SND_SOC_SOF_HDA_LINK=y
CONFIG_SND_SOC_SOF_HDA_AUDIO_CODEC=y
CONFIG_SND_SOC_SOF_HDA_LINK_BASELINE=m
CONFIG_SND_SOC_SOF_HDA=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK_BASELINE=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE=m
CONFIG_SND_SOC_SOF_XTENSA=m

wiak wrote: ↑Tue Oct 18, 2022 11:10 am

kernel kit extract appears to be for a 5.15.4-x86_64 kernel build

woof-CE's 5.15.x kernel configurations are horrible, don't trust them. Battery life and performance are terrible, among other things. I don't use them in any of my builds, and all my proposals to align them with Ubuntu 22.04's kernels met objections from other Puppy developers, so I just gave up on that idea. The 5.10.x configurations are extremely close to the Debian 11 ones and work much better.

wiak wrote:

I could be wrong, but seems unlikely to me to be a firmware issue - rather a kernel config or modules related issue

It could be that both is required, kernel support for sof, but still the firmware may be required too.
The Debian kernel has it included, in the config CONFIG_SND_SOC_SOF=m and firmware is available https://packages.debian.org/bookworm/fi ... sof-signed

I have dove deep into the configuration needed for SOC support. Deep water for sure........but I am tracking it down and found the configurations in the kernel config that need to be done....my first attampt to compile the 6.0.2-KLV with all of the changes failed...but I am close......for now I am considering using one of dimkr's kernels.

@dimkr I agree with you on those proposed kernel configurations.

@fredx181 you are correct about the firmware. With SOC there are many pieces that need to be enabled and present. Both in the kernel configuration and the modules

wiak wrote:

# CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH is not set
CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m
CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m
CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98357A_MACH=m
# CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98927_MACH is not set
# CONFIG_SND_SOC_INTEL_KBL_RT5660_MACH is not set
# CONFIG_SND_SOC_INTEL_GLK_DA7219_MAX98357A_MACH is not set
CONFIG_SND_SOC_INTEL_GLK_RT5682_MAX98357A_MACH=m
CONFIG_SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m
CONFIG_SND_SOC_INTEL_SOF_RT5682_MACH=m
# CONFIG_SND_SOC_INTEL_SOF_CS42L42_MACH is not set
# CONFIG_SND_SOC_INTEL_SOF_PCM512x_MACH is not set
# CONFIG_SND_SOC_INTEL_CML_LP_DA7219_MAX98357A_MACH is not set
# CONFIG_SND_SOC_INTEL_SOF_CML_RT1011_RT5682_MACH is not set
# CONFIG_SND_SOC_INTEL_SOF_DA7219_MAX98373_MACH is not set
# CONFIG_SND_SOC_INTEL_EHL_RT5660_MACH is not set
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
# CONFIG_SND_SOC_MTK_BTCVSD is not set
CONFIG_SND_SOC_SOF_TOPLEVEL=y
CONFIG_SND_SOC_SOF_PCI_DEV=m
CONFIG_SND_SOC_SOF_PCI=m
# CONFIG_SND_SOC_SOF_ACPI is not set
# CONFIG_SND_SOC_SOF_DEBUG_PROBES is not set
# CONFIG_SND_SOC_SOF_DEVELOPER_SUPPORT is not set
CONFIG_SND_SOC_SOF=m
CONFIG_SND_SOC_SOF_PROBE_WORK_QUEUE=y
CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL=y
CONFIG_SND_SOC_SOF_INTEL_HIFI_EP_IPC=m
CONFIG_SND_SOC_SOF_INTEL_ATOM_HIFI_EP=m
CONFIG_SND_SOC_SOF_INTEL_COMMON=m
CONFIG_SND_SOC_SOF_MERRIFIELD=m
CONFIG_SND_SOC_SOF_INTEL_APL=m
CONFIG_SND_SOC_SOF_APOLLOLAKE=m
CONFIG_SND_SOC_SOF_GEMINILAKE=m
CONFIG_SND_SOC_SOF_INTEL_CNL=m
CONFIG_SND_SOC_SOF_CANNONLAKE=m
CONFIG_SND_SOC_SOF_COFFEELAKE=m
CONFIG_SND_SOC_SOF_COMETLAKE=m
CONFIG_SND_SOC_SOF_INTEL_ICL=m
CONFIG_SND_SOC_SOF_ICELAKE=m
CONFIG_SND_SOC_SOF_JASPERLAKE=m
CONFIG_SND_SOC_SOF_INTEL_TGL=m
CONFIG_SND_SOC_SOF_TIGERLAKE=m
CONFIG_SND_SOC_SOF_ELKHARTLAKE=m
CONFIG_SND_SOC_SOF_ALDERLAKE=m
CONFIG_SND_SOC_SOF_HDA_COMMON=m
CONFIG_SND_SOC_SOF_HDA_LINK=y
CONFIG_SND_SOC_SOF_HDA_AUDIO_CODEC=y
CONFIG_SND_SOC_SOF_HDA_LINK_BASELINE=m
CONFIG_SND_SOC_SOF_HDA=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK_BASELINE=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE=m
CONFIG_SND_SOC_SOF_XTENSA=m

These are just part of it. There are dependent parameters that must be enabled to enable some of these which are not clearly evident.

I am really close to a successful build of 6.0.2-KLV with full SOC support.

I blew up 2 Fossapup64's building stuff.......things just stopped working that worked steady up to an hour before so off to build a woof-CE Fossapup64 to attempt another build run of 6.0.2 with all the details covered. I am learning it as I go trial and error.

On my laptop, I attempted to set up the the included gufw firewall. It failed to run. The following is from the output when attempted to run from a terminal:

root# gufw
(gufw.py:1673): Gdk-CRITICAL **: 12:39:50.139:  gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
>
(gufw.py:1673): Gtk-CRITICAL **: 12:39:50.139: _gtk_css_lookup_resolve: assertion '(((__extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((provider)); GType __t = ((_gtk_style_provider_private_get_type ())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type == __t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r; }))))' failed
/usr/lib/python3.10/site-packages/gufw/gufw/view/gufw.py:77: Warning: g_object_set_data_full: assertion 'G_IS_OBJECT (object)' failed
  self.builder.add_from_file('/usr/share/gufw/ui/gufw.ui')

(gufw.py:1673): Gtk-ERROR **: 12:39:50.146: Can't create a GtkStyleContext without a display connection
/sbin/gufw-pkexec: line 2:  1673 Trace/breakpoint trap   python3 /usr/lib/python3.10/site-packages/gufw/gufw.py $1
root# 

Note: > I deleted 20 or so similar lines.

@TerryH Thanks good to know. I have replicated the problem immediately. The gufw firewall recently updated and something has gone amiss. Will look into it.

UPDATE: because gufw was updated the modified .desktop file was also replaced.

TO FIX:
open /usr/share/spplications/gufw.destop
change the line ->

Exec=gufw

to

Exec=gufw-pkexec

Also like this in a terminal: gufw-pkexec

I will look at an alternative way to start gufw that will allow updating without breaking something like the launcher.

fredx181 wrote: ↑Tue Oct 18, 2022 1:33 pm

wiak wrote:

I could be wrong, but seems unlikely to me to be a firmware issue - rather a kernel config or modules related issue

It could be that both is required, kernel support for sof, but still the firmware may be required too.
The Debian kernel has it included, in the config CONFIG_SND_SOC_SOF=m and firmware is available https://packages.debian.org/bookworm/fi ... sof-signed

Oh both the firmware and the modules and suitably configured kernel are also required. I am already using with vupup kernel and did need the sof-firmware.

I meant that Void Linux sof-firmware works fine when using Void Linux kernel and modules (with sof modules present), but that suitably configured kernel including sof modules was needed and that was what was wrong with current KLV kernel/modules/firmware situation. I already had my latest FirstRib Arch64 working with official Arch kernel/modules/firmware (including installing of sof-firmware) - I first discovered the KLV issue when swapping in KLV's kernel as an experiment in my FR Arch build and then swapped in vupup kernel and noticed the issue and its reason.