Missing information about exact kernel patches for Stoneyridge devices.

Question

Missing information about exact kernel patches for Stoneyridge devices.

Opened this issue a year ago · 41 comments

Good evening,

I've got a problem with getting an exact information about what patches should be applied on the Linux kernel 6.1+ for Stoneyridge Chromebook devices.

The documentation of Known issues in the Stoneyridge devices section says:

Needs kernel compiled with AMDGPU=Y instead of =M and firmware built-in to get working audio

eMMC is only detected on a cold boot unless you have a patched kernel

although not linking any source to the patches for the Linux kernel as mentioned.

What patches should I use?

Additionally while reading dmesg for anything related to the problem of eMMC I've got:

[    0.000000] efi: EFI v2.7 by EDK II
[    0.000000] efi: SMBIOS=0xbf41a000 SMBIOS 3.0=0xbf418000 ACPI=0xbf533000 ACPI 2.0=0xbf533014 MEMATTR=0xbbf16c18 
[    0.000000] efi: Remove mem97: MMIO range=[0xffbc0000-0xffbfffff] (0MB) from e820 map

GamePlayer-8 commented a year ago

link?

GamePlayer-8 commented a year ago

yes

Answer 1 · 2023-10-16T17:16:26.000Z

I can add detailed info about stoney. The emmc issue is due to an update in the driver, which we have a patch for.

Answer 2 · 2023-10-16T17:32:27.000Z

Thank you. By the way, is there a gist / repo of the patch already? I'm configuring the PKGBUILD for the kernel right now.

Answer 3 · 2023-10-16T19:31:25.000Z

We have a repo but it's outdated. The person that is working on updating it will push the changes and make a pr sometime soon.

Answer 4 · 2023-10-16T19:58:27.000Z

https://github.com/chrultrabook/linux-build-scripts

Answer 5 · 2023-10-18T12:04:08.000Z

@WeirdTreeThing I've patched the kernel for my system (source code).

Although CONFIG_DRM_AMDGPU=y causes the kernel to freeze the screen, on the Stoneyridge device.
The rest of the system components (NetworkManager, sddm) is being loaded like nothing happened.

Answer 6 · 2023-10-18T12:15:05.000Z

diff of the original kernel configuration vs modified by the distro:

--- ../config	2023-10-18 08:09:34.572437859 +0000
+++ .config	2023-10-18 08:11:56.161685713 +0000
@@ -590,7 +590,7 @@
 CONFIG_ACPI_AC=y
 CONFIG_ACPI_BATTERY=y
 CONFIG_ACPI_BUTTON=y
-CONFIG_ACPI_VIDEO=m
+CONFIG_ACPI_VIDEO=y
 CONFIG_ACPI_FAN=y
 CONFIG_ACPI_TAD=m
 CONFIG_ACPI_DOCK=y
@@ -4673,7 +4673,7 @@
 
 CONFIG_I2C_HELPER_AUTO=y
 CONFIG_I2C_SMBUS=m
-CONFIG_I2C_ALGOBIT=m
+CONFIG_I2C_ALGOBIT=y
 CONFIG_I2C_ALGOPCA=m
 
 #
@@ -5840,7 +5840,7 @@
 CONFIG_RC_ATI_REMOTE=m
 CONFIG_RC_LOOPBACK=m
 CONFIG_RC_XBOX_DVD=m
-CONFIG_CEC_CORE=m
+CONFIG_CEC_CORE=y
 CONFIG_CEC_NOTIFIER=y
 CONFIG_CEC_PIN=y
 
@@ -6679,20 +6679,20 @@
 CONFIG_DRM_FBDEV_EMULATION=y
 CONFIG_DRM_FBDEV_OVERALLOC=100
 CONFIG_DRM_LOAD_EDID_FIRMWARE=y
-CONFIG_DRM_DISPLAY_HELPER=m
+CONFIG_DRM_DISPLAY_HELPER=y
 CONFIG_DRM_DISPLAY_DP_HELPER=y
 CONFIG_DRM_DISPLAY_HDCP_HELPER=y
 CONFIG_DRM_DISPLAY_HDMI_HELPER=y
 CONFIG_DRM_DP_AUX_CHARDEV=y
 CONFIG_DRM_DP_CEC=y
-CONFIG_DRM_TTM=m
-CONFIG_DRM_BUDDY=m
+CONFIG_DRM_TTM=y
+CONFIG_DRM_BUDDY=y
 CONFIG_DRM_VRAM_HELPER=m
-CONFIG_DRM_TTM_HELPER=m
+CONFIG_DRM_TTM_HELPER=y
 CONFIG_DRM_GEM_DMA_HELPER=m
 CONFIG_DRM_GEM_SHMEM_HELPER=y
-CONFIG_DRM_SUBALLOC_HELPER=m
-CONFIG_DRM_SCHED=m
+CONFIG_DRM_SUBALLOC_HELPER=y
+CONFIG_DRM_SCHED=y
 
 #
 # I2C encoder or helper chips
@@ -6710,7 +6710,7 @@
 
 CONFIG_DRM_RADEON=m
 CONFIG_DRM_RADEON_USERPTR=y
-CONFIG_DRM_AMDGPU=m
+CONFIG_DRM_AMDGPU=y
 CONFIG_DRM_AMDGPU_SI=y
 CONFIG_DRM_AMDGPU_CIK=y
 CONFIG_DRM_AMDGPU_USERPTR=y
@@ -8999,7 +8999,7 @@
 CONFIG_SURFACE_AGGREGATOR_BUS=y
 # CONFIG_SURFACE_AGGREGATOR_ERROR_INJECTION is not set
 CONFIG_X86_PLATFORM_DEVICES=y
-CONFIG_ACPI_WMI=m
+CONFIG_ACPI_WMI=y
 CONFIG_WMI_BMOF=m
 CONFIG_HUAWEI_WMI=m
 CONFIG_MXM_WMI=m

(I've modified only CONFIG_DRM_AMDGPU).

Answer 7 · 2023-10-18T19:31:48.000Z

You also need to build the AMDGPU firmware into the kernel.

Answer 8 · 2023-10-23T18:37:38.000Z

After a lot of troubleshooting, I have embeded the /lib/firmware/amdgpu/stoney* firmware into my kernel.

Although even if speakers / jack output is being recognized, there's no sound being played. A microphone is being shown, but there's a loud noise.

Camera isn't being recognized too. What might be the issue?

Answer 9 · 2023-10-23T18:39:28.000Z

Additional dmesg logs containing errors:

[   22.350783] acp3x-alc5682-max98357 AMDI5682:00: DMIC gpio failed err=-2
[   22.350826] acp3x-alc5682-max98357: probe of AMDI5682:00 failed with error -2
[  100.740655] Failed to stop ACP DMA channel : 13
[  101.761572] Failed to stop ACP DMA channel : 9
[  142.557143] Failed to stop ACP DMA channel : 13
[  143.578814] Failed to stop ACP DMA channel : 9
[  144.610460] Failed to stop ACP DMA channel : 10
[  144.610460] acp_audio_dma acp_audio_dma.0.auto: ASoC: error at soc_component_trigger on acp_audio_dma.0.auto: -110

Answer 10 · 2023-10-25T11:48:40.000Z

aplay error when trying to play sound to the soundcard provided by stoney* firmware:

aplay: pcm_write:2146: write error: Input/output error

Answer 11 · 2023-10-25T23:58:02.000Z

6.5 is known to have issues, I just kinda reverted a few things until it worked.

Answer 12 · 2023-10-26T04:56:16.000Z

Should I recompile under 6.1 kernel?

Answer 13 · 2023-10-26T11:05:31.000Z

Try that, afaik it should work until we figure out what broke 6.5.

Answer 14 · 2023-10-27T06:02:09.000Z

Your emmc.patch file works only under 6.4+ kernel versions. I'll try to compile under 6.4.16.

Answer 15 · 2023-10-27T12:55:50.000Z

Under 6.4.16 audio output works. Still Camera is unrecognized by the kernel and built-in microphone isn't working.

Answer 16 · 2023-10-27T13:54:59.000Z

The camera is just usb so it's likely to be a hardware issue.

Answer 17 · 2023-10-27T14:25:18.000Z

What to do about microphone?

dmesg reports:

[ 4754.381512] acp3x-alc5682-max98357 AMDI5682:00: DMIC gpio failed err=-2
[ 4754.382134] acp3x-alc5682-max98357: probe of AMDI5682:00 failed with error -2

Answer 18 · 2023-10-27T14:31:41.000Z

Problem with the webcam was reported before to the MrChromebox, but the issue got refused.

Answer 19 · 2023-10-27T15:09:02.000Z

That is not a real issue, that's a separate driver that loads automatically even though it isn't used on this platform.

Answer 20 · 2023-10-27T15:12:40.000Z

How to deal with it?

Answer 21 · 2023-10-27T15:36:03.000Z

Ignore it or blacklist the module.

Answer 22 · 2023-10-27T16:19:47.000Z

Which one should I blacklist exactly?

Answer 23 · 2023-10-27T16:44:42.000Z

I don't remember off the top of my head, look for acp3x in lsmod.

Answer 24 · 2023-10-30T04:01:25.000Z

MrChromebox 4.21.1 firmware has released today, which fixes emmc on warm reboots on the firmware side. The kernel patch is no longer needed.

Answer 25 · 2023-11-05T17:10:24.000Z

I don't remember off the top of my head, look for acp3x in lsmod.

lsmod doesn't show any type of acp3x module loaded. The nearest one might be snd_soc_acp_rt5682_mach what's being used for the audio ports / speakers.

Answer 26 · 2023-11-05T17:17:50.000Z

I just checked on my careena and yeah that's the one you need to blacklist.

Answer 27 · 2023-11-05T17:40:30.000Z

I've blacklisted and still no change in the Webcam detection.

modprobe loaded snd_soc_acp_da7219mx98357_mach - even after blacklisting this one too, there's no audio device detected.

Answer 28 · 2023-11-05T18:26:49.000Z

snd_soc_acp_da7219mx98357_mach is the one that's supposed to load. Blacklisting snd_soc_acp_rt5682_mach on my careena didn't break audio.

Answer 29 · 2023-11-05T19:25:00.000Z

Yeah, I meant, on both modules camera doesn't work

Answer 30 · 2023-11-05T19:42:41.000Z

Camera is not part of audio. Check for your camera in lsusb.

Answer 31 · 2023-11-14T17:12:14.000Z

lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:c542 Logitech, Inc. M185 compact wireless mouse
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hu

lspci:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] (rev eb)
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15b3
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge
00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Carrizo Platform Security Processor
00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Carrizo Audio Dummy Host Bridge
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 20)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 49)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 4b)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.7 SD Host controller: Advanced Micro Devices, Inc. [AMD] FCH SD Flash Controller (rev 01)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Stoney HT Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Stoney Address Maps
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Stoney DRAM Configuration
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Stoney Miscellaneous Configuration
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Stoney PM Configuration
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Stoney NB Performance Monitor
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
02:00.0 SD Host controller: O2 Micro, Inc. Device 8620 (rev 01)

Answer 32 · 2023-11-14T18:46:04.000Z

The usb device for your camera is missing. Either something in coreboot is broken or the physical cable is damaged. You can rule out coreboot by testing stock. I can say that on my careena, the camera cable was damaged and only worked at certain angles.

Answer 33 · 2023-11-14T19:46:29.000Z

Nothing bad happened to my camera when I was using ChromeOS so probably a firmware issue. Will try to compile the original kernel and see the difference.

Answer 34 · 2023-11-14T19:59:09.000Z

The kernel isn't gonna prevent usb devices from being detected. You will need to flash stock and verify the camera works there.

Answer 35 · 2023-12-04T19:43:00.000Z

Works on stock firmware, but only under ChromeOS.

Answer 36 · 2023-12-05T22:19:39.000Z

but only under ChromeOS

As in you tried to boot a mainline distro on stock firmware?

Answer 37 · 2023-12-06T12:28:20.000Z

I've never seen anything like this.

Answer 38 · 2023-12-06T16:59:01.000Z

snd_soc_acp_da7219mx98357_mach

This is the correct module for Stoney.

What to do about microphone?

dmesg reports:

[ 4754.381512] acp3x-alc5682-max98357 AMDI5682:00: DMIC gpio failed err=-2
[ 4754.382134] acp3x-alc5682-max98357: probe of AMDI5682:00 failed with error -2

ACP3x == Picasso (Ryzen 3000).

Answer 39 · 2024-01-04T19:55:11.000Z

ACP3x == Picasso (Ryzen 3000).

What should I do about it?