AMDGPU and SATA support for lx2160a_build images? / Kernel/Mesa support timeline in 5+ years of using the LX2K as a Desktop

Hi all,

TLDR: I can’t use the SolidRun HoneyComb LX2K as a desktop system with newer kernels due to patches that became incompatible Below are some questions:

  1. Do the lx2160a_build images support video-out via DisplayPort over an AMDGPU (RX 580)
    => Would it be trivial to add it? (Could I do it myself if I have little programming knowledge?)
  2. Does it also support booting off of SATA drives?
    => If yes, how can I boot off of one?

Kernel/Mesa support timeline:

in 2021 the driver for the ethernet NIC (I think fsl_dpaa2) landed into Linux 5.14
With 5.16 and later (I believe), the kernel changed so that booting a non-vendor kernel didn’t work

  • Jon built me a UEFI image with with an ecam part, which made booting work again (Thank you a lot, Jon!)

  • The mesa patch that fixes graphical glitches on Xorg and Xwayland applications with AMDGPU cards, stopped working (applying) ever since Mesa 22.3.7. (Using wayland mostly fixes the glitches)

  • [Linux 6.3 was the last vendor kernel made by SolidRun]( GitHub - SolidRun/linux-stable at linux-6.3.y-cex7 · GitHub ), so I gathered the necessary patches and applied them to my kernels.

  • With Kernel 6.18, eMMC-support stopped, around 7.0.0 many patches stopped applying (which I noticed I didn’t need)

  • and now the `818da6795040209e55b360ec9e28d1539a7da61f-fsl-mc-bus.patch` is incompatible with 7.2.0, which causes the fsl_dpaa2 ethernet NIC to not work anymore due to an error shown in the dmesg.

  • I booted some normal distribution kernels with the lx2160a_build image and noticed that all things worked, probably due to device-tree.

    • if lx2160a_build doesn’t support AMDGPU and/or SATA that’ll be fine. I’m sure the LX2K will do great as a server (which of course is what it was intended for in the first place (high-speed networking as well))
  • trying to upstream the following patches:
    13b8f32de441c499418269b07c7d199bfeea036e-memcpy.patch
    2a827b2d3f18c13ffe7e824af4e92c17f28a1ce5-dpio-driver.patch
    4030ddfd0e381814b52f00a07b98239c2f58c754-entry-common.patch
    5716686ddc4527c24b30d595903525eda593ece1-pcie-layerscape-ecam.patch
    780aebfdd1f506e7883429edf7a42c512377e4ce-entry.patch
    818da6795040209e55b360ec9e28d1539a7da61f-fsl-mc-bus.patch
    87fe1d4b69e9f36b6aa72f357a39047d109d2103-dprc-driver.patch
    8ba90cd0971052a3752c0f5fe60161a37aa5193d-acpi_apd.patch
    df6e0b3f2be312d3a3d1e5a0957119996db96e21-iommu.patch

    • might be worth a try, but I think that there is a reason, why at least necessary patches didn’t make it into upstream or maybe have not been bothered with upstreaming.
1 Like