Thanks for that info; wasn't aware of that. Will have to look into it.You do know that you can get Github to build any kernel for you using our normal workflows? It generally takes about 45mins, and is free. Push multiple branches and they'll all get built in parallel.only to the first part (Did pastebinit work before the update to 6.12).Is that a yes to both questions?
Reverting to 6.6.62 requires me to compile the custom kernel again -> roughly 2 hours on that DUT
Go into your Github Linux repo, select Settings, then Actions. My settings are
"Allow <user>, and select non-<user>, actions and reusable workflows"
"Require approval for first-time contributors"
"Read repository contents and packages permissions"
Any push should trigger the CI build if the branch name starts "rpi-".
I believe using "sudo LINUX_REPO=https://github.com/<user>/linux rpi-update <branch>" will install that CI build for you too. (You probably want to add SKIP_FIRMWARE=1 in there)
The one downside is that it is a clean build every time, so it'll always take ~45mins, even for a one line change.
Same happens on 6.6.63!
Started with the screen on HDMI1 (2540x1440) and the LVDS connected to the bridge on DSI-1 --> no issues; system runs fine.
Powered down, connected the portrait screen to HDMI-2 --> HDMI-1 get's powered down 1min (around) after power-up.
Pasetbin works on that kennel version --> https://paste.debian.net/hidden/3ec09023/
Code:
[ 77.541158] vc4-drm gpu: [drm] *ERROR* flip_done timed out[ 77.541158] vc4-drm gpu: [drm] *ERROR* hw_done timed out[ 77.541178] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit[ 77.541185] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit[ 77.541238] vc4-drm gpu: [drm] *ERROR* [CRTC:103:pixelvalve-2] flip_done timed outTyp. that screen is used with a Pi5 8GB with no issues at all (6.6.62).
Statistics: Posted by aBUGSworstnightmare — Thu Nov 28, 2024 2:35 pm