Screen refresh delay with kernel errors

[bchenlee609]

Hello,

I used your new patch, so hopefully have done the APPEND modification properly.

Output of dmesg | grep command listed below:

Code:

    [0.000000] Kernel command line: initrd=/initramfs-linux.img console=tty1 console=ttyS2,1500000 root=LABEL=ROOT_MNJRO rw rootwait video=eDP-1:1920x1080@60 video=HDMI-A-1:1920x1080@60 bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash analogix_dp.enable_psr=0

Any advice would be appreciated. If not, seems like this change will roll out on a wider scale eventually too, can wait until then. Was just trying to use this as a learning experience too

Thanks!
-B

Your kernel command line is correct, so the issue must be that you either didn't apply the patch correctly or didn't install/boot the new kernel correctly. I personally just used the kernel's own build system to build and install the kernel, so I'm not super familiar with Manjaro's makepkg method. According to mtnygard's post it seems the patch needs to be applied after `makepkg -o` and before `makepkg -e`, then you use `pacman -U` to install the newly built kernel.

If possible, could you try modifying the kernel's LOCALVERSION string to contain something unique? You should be able to edit the .config file after the `makepkg -o` step with a text editor to do this. This will allow you to see if the you're successfully booting the patched kernel by running `uname -r` and seeing if the new LOCALVERSION appears.

Thanks for your last reply! Life gets in the way tinkering with this laptop unfortunately.
May I ask for some clarification? Which .config file am i editing after the 'makepkg -o' step?
And once in there, how do I modify the LOCALVERSION string?

Sorry if these are silly questions, this is all new for me.

I wish there were a way to check at this point whether or not I applied your patch correctly (without modifying the kernel localversion string)
I'm assuming this is not possible?

Thanks again!

-B

[shawnanastasio]

Thanks for your last reply! Life gets in the way tinkering with this laptop unfortunately.
May I ask for some clarification? Which .config file am i editing after the 'makepkg -o' step?
And once in there, how do I modify the LOCALVERSION string?

Sorry if these are silly questions, this is all new for me.

I wish there were a way to check at this point whether or not I applied your patch correctly (without modifying the kernel localversion string)
I'm assuming this is not possible?

Thanks again!

-B

Like I mentioned earlier, I'm unfortunately not too familiar with manjaro's packaging system so I'm not sure exactly where their kernel package would store the config. `find . -name ".config"` should be able to find it though.

That said, the patch has landed in manjaro ARM's linux-aarch64 repo, so you should be able to just update (and keep your APPEND) to use it: https://gitlab.manjaro.org/manjaro-arm/p...2f97945e6a.

[bchenlee609]

Thanks for your last reply! Life gets in the way tinkering with this laptop unfortunately.
May I ask for some clarification? Which .config file am i editing after the 'makepkg -o' step?
And once in there, how do I modify the LOCALVERSION string?

Sorry if these are silly questions, this is all new for me.

I wish there were a way to check at this point whether or not I applied your patch correctly (without modifying the kernel localversion string)
I'm assuming this is not possible?

Thanks again!

-B

Like I mentioned earlier, I'm unfortunately not too familiar with manjaro's packaging system so I'm not sure exactly where their kernel package would store the config. `find . -name ".config"` should be able to find it though.

That said, the patch has landed in manjaro ARM's linux-aarch64 repo, so you should be able to just update (and keep your APPEND) to use it: https://gitlab.manjaro.org/manjaro-arm/p...2f97945e6a.

Thank you!
it worked, and it's glorious =)
Many thanks, again.

UPDATE: battery life has definitely taken a hit, but still very good. the overall increased usability is amazing though. made a huge difference.

[Lyrixcaz]

Folks anybody knows of this has this been added unto the mainline kernel in manjaro arm?

[shawnanastasio]

Folks anybody knows of this has this been added unto the mainline kernel in manjaro arm?

Which kernel package are you referring to? As I mentioned previously it's in manjaro's linux-aarch64 and linux-pinebookpro repositories.

[Lyrixcaz]

I'm on Manjaro arm with the latest kernel at the moment " 5.8.1-1-MANJARO-ARM " i have the package linux-aarch64 installed and when i dmesg i see the messages of:
[  526.782279] rockchip-dp ff970000.edp: Failed to apply PSR -110
[  526.782318] [drm:analogix_dp_bridge_atomic_enable [analogix_dp]] *ERROR* Failed to disable psr -110

[shawnanastasio]

I'm on Manjaro arm with the latest kernel at the moment " 5.8.1-1-MANJARO-ARM " i have the package linux-aarch64 installed and when i dmesg i see the messages of:
[  526.782279] rockchip-dp ff970000.edp: Failed to apply PSR -110
[  526.782318] [drm:analogix_dp_bridge_atomic_enable [analogix_dp]] *ERROR* Failed to disable psr -110

If you're running linux-aarch64 then you simply need to add `analogix_dp.enable_psr=0` to your kernel arguments as described earlier in the thread.

[Lyrixcaz]

Folks anybody knows of this has this been added unto the mainline kernel in manjaro arm?

Which kernel package are you referring to? As I mentioned previously it's in manjaro's linux-aarch64 and linux-pinebookpro repositories.

Thanks for letting me know, i did that and the touchpad seems to be more responsive? like so far so good. Has anyone been with this option on for a prolonged period of time? what are the negative effects of it?

[GhostDragon]

Thanks for your work. I just received my Pinebook Pro today and it was sluggish and choppy, this fixed it.

[bchenlee609]

Folks anybody knows of this has this been added unto the mainline kernel in manjaro arm?

Which kernel package are you referring to? As I mentioned previously it's in manjaro's linux-aarch64 and linux-pinebookpro repositories.

Thanks for letting me know, i did that and the touchpad seems to be more responsive? like so far so good. Has anyone been with this option on for a prolonged period of time? what are the negative effects of it?

I've noticed a small hit on battery life. Nothing formally tested just anecdotal. For me the trade off in usability is worth it.