Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch meson edge to 6.13 kernel #7747

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kernelzru
Copy link
Contributor

Switch meson edge to 6.13 kernel
Hdmi patches from xdarklight github repo

@github-actions github-actions bot added size/large PR with 250 lines or more Needs review Seeking for review Hardware Hardware related like kernel, U-Boot, ... Patches Patches related to kernel, U-Boot, ... labels Jan 25, 2025
@igorpecovnik
Copy link
Member

Can you also try to switch CURRENT to 6.12.y, which is going to be LTS?

@SteeManMI
Copy link
Contributor

iMHO, it would be best to first switch edge to 6.12 so that 6.12 gets some testing on it. Then move legacy to 6.6, current to 6.12 and edge to 6.13.
I don't think it is wise to move current to a version that wasn't first tested as an edge build first.

@igorpecovnik
Copy link
Member

iMHO, it would be best to first switch edge to 6.12 so that 6.12 gets some testing on it. Then move legacy to 6.6, current to 6.12 and edge to 6.13

Yes, better.

@igorpecovnik igorpecovnik mentioned this pull request Feb 5, 2025
5 tasks
@igorpecovnik igorpecovnik added 02 Milestone: First quarter release 05 Milestone: Second quarter release labels Feb 5, 2025
@domin144
Copy link
Collaborator

domin144 commented Feb 10, 2025

Hello @kernelzru . I tried your version on MXQ clone, which also uses s805 soc.

To get any HDMI output, I had to apply the same I apply for 6.12 kernel (https://github.com/armbian/build/blob/main/patch/kernel/archive/meson-6.12/0067-meson8b-mxq-add-HDMI-support.patch)

I am getting Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read error, when trying to switch the resolution from 1920x1200 to 1920x1080.
When time will allow, I will look through the patches, but letting you know in case the error message rings any bells.
hdmi_6.13_fail.txt

@kernelzru
Copy link
Contributor Author

Hello @kernelzru . I tried your version on MXQ clone, which also uses s805 soc.

To get any HDMI output, I had to apply the same I apply for 6.12 kernel (https://github.com/armbian/build/blob/main/patch/kernel/archive/meson-6.12/0067-meson8b-mxq-add-HDMI-support.patch)

I am getting Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read error, when trying to switch the resolution from 1920x1200 to 1920x1080. When time will allow, I will look through the patches, but letting you know in case the error message rings any bells. hdmi_6.13_fail.txt

Hello. I've taken patches from xdarklight repository. There is also dts for MXQ device. Can you try with it? Not shure, that it will help, but may be:)

https://github.com/xdarklight/linux/blob/meson-mx-integration-6.13-20250112/arch/arm/boot/dts/amlogic/meson8b-mxq.dts

@domin144
Copy link
Collaborator

domin144 commented Mar 2, 2025

The dts file you pointed me to, has exactly the same fixes as those already in armbian patches (except minor reordering), so it won't help.

I did some experiments. I can confirm that the issue is introduced with one of the xdarklight's patches. I looked through the patches to find something, that would resemble any of the functions in the crash callstack. I found two suspicious callbacks added and commented them out. Patches rebased on kernel v6.13.5, some patches copied over from 6.12 (not sure if still needed, but preferred to keep them for now) and the workaround are available on this branch: https://github.com/domin144/armbian-build/tree/meson_6.12_on_xdarklight_6.13_clean_up

With this workaround added, I no longer observed the crash. I did some tests and it worked really nicely. Even HDMI audio was working. Not yet sure, what got broken (the callbacks were there for some reason).

While this is definitely a workaround, not a solution, there is so much good staff in the xdarklight's patches, that I think it's worth giving it a try.

@xdarklight : no sure what would be the correct way to file an issue against the patches. Maybe you would like to take a look at the kernel crash above?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
02 Milestone: First quarter release 05 Milestone: Second quarter release Hardware Hardware related like kernel, U-Boot, ... Needs review Seeking for review Patches Patches related to kernel, U-Boot, ... size/large PR with 250 lines or more
Development

Successfully merging this pull request may close these issues.

4 participants