linux-postmarketos-mediatek-mt8173: upgrade to 6.11.1

6.11.x initially had an issue where it would not show text on the TTY. A new patch to revert this commit has been added to resolve this issue, and it has been reported upstream.

added 1 commit

• 64b99a9b - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-19T12:09:19

added 1 commit

• 0ea760d5 - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-19T12:16:10

changed the description

By Adam Thiede on 2024-09-19T13:40:06

added 21 commits

• 0ea760d5...3f662815 - 20 commits from branch postmarketOS:master
• 7516f343 - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-19T23:22:20

changed the description

By Adam Thiede on 2024-09-20T18:08:27

added 1 commit

• f7acd115 - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-21T20:33:01

Temporarily disabling powervr config, to see if that helps or fixes things in any way.

By Adam Thiede on 2024-09-21T20:35:08

added 1 commit

• 97a6ea56 - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-21T22:37:32

added 1 commit

• 4b8de828 - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-22T00:24:54

Disabling powervr did not work. Now attempting to enable all the BOE panels to see if that helps. (It's not clear to me what changed in terms of this machine's hardware between 6.10 and 6.11 yet)

By Adam Thiede on 2024-09-22T00:32:09

So this would - if successful - replace !5601 (merged)?

By Robert Eckelmann on 2024-09-22T01:13:19

This will probably take a little bit to figure out. If the other one could be merged first (so there could be a longer testing period for people other than me) that would be great.

By Adam Thiede on 2024-09-22T09:52:51

added 1 commit

• 718b6bed - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-22T11:07:35

• enabling all the BOE panels did not work
• enabling CONFIG_DRM_SIMPLEDRM and CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION did not work

By Adam Thiede on 2024-09-22T15:33:19

added 1 commit

• 58a4e0c7 - linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches

Compare with previous version

By Adam Thiede on 2024-09-22T15:39:48

changed title from Draft: linux-postmarketos-mediatek-mt8173: upgrade to 6.11 and remove patches to Draft: (help wanted) linux-postmarketos-mediatek-mt8173: upgrade to 6.11

By Adam Thiede on 2024-09-22T18:55:58

added help wanted kernel-config labels

git bisect log:

git bisect start '--first-parent' 'v6.11' 'v6.10'
git bisect bad 10826505f52357c7c9e12358db97a3acbe82e958
git bisect bad c434e25b62f8efcfbb6bf1f7ce55960206c1137e
git bisect good e55037c879a087a57d775e848a58430ab3380fc1
git bisect good 01f851a0e87ed64db7081a472061650e96dfb798
git bisect bad 91bd008d4e2b4962ecb9a10e40c2fb666b0aeb92
git bisect good 5b9ac6c2a735f5b1721e0bc7331f8707190f9ef6
git bisect bad 49208b67585d18521225bf72bf842593cea711f8
git bisect good b1bc554e009e3aeed7e4cfd2e717c7a34a98c683
git bisect bad b3ce7a30847a54a7f96a35e609303d8afecd460b

The commit that introduced the problem is https://github.com/torvalds/linux/commit/b3ce7a30847a54a7f96a35e609303d8afecd460b, which is this tag: https://gitlab.freedesktop.org/drm/kernel/-/tags/drm-next-2024-07-18

Next is bisecting through that.

By Adam Thiede on 2024-09-25T13:27:58

Seems like it's probably this commit. Did some builds and this is yet another merge commit culprit. https://gitlab.freedesktop.org/drm/kernel/-/commit/6256274c0182b584e7011077d071f905f2385f64

Once again, going through the commits in this merge to see which one causes it. Once that does I'll build with the reverse-diff and see what happens.

By Adam Thiede on 2024-09-29T20:10:50

entirely possible that bc46eb5d5d7780782c70c7915f59ed25a908d550 is the commit that's the issue. Trying to build the 6.11 tag with that commit reverted, and I'll see if that works. (it did!)

By Adam Thiede on 2024-09-30T22:11:12