-
Notifications
You must be signed in to change notification settings - Fork 5.2k
fuzzy black text on the red background in a 15.6 touchscreen on raspberry kernel 5.10,but kernel 4.19 works well #5085
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
Comments
It sounds like issue occurs with 2022-04-04-raspios-bullseye-arm64 (with 5.15 kernel), so focus on that. By default that image uses the kms driver ( With kms, when you see fuzzy text can you post output of |
torvalds/linux@f741b28 introduced in 5.2 dropped the framebuffer default from 32bpp to 16bpp assuming you're running vc4-kms-v3d or vc4-fkms-v3d. If your text renderer is using anti-aliasing to try and smooth the font out, then the loss of colour definition may cause that sort of issue. |
@6by9 |
16bpp will be blurrier than 32bpp if using anti-aliased fonts. |
got it now. let try to change and test |
You should be able to override it by adding |
my debug info for Linux raspberrypi 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux 2022-04-04-raspios-bullseye-arm64 ( I am going to try @6by9 solutions. I will post the result)
cat /sys/kernel/debug/dri/1/state |
I am going to try |
@6by9 video=HDMI-A-1:1920x1080M-32@60 console=serial0,115200 console=tty1 root=PARTUUID=f3d36243-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles config.txt : but the issue is same as before |
The state posted for kms looks to have:
So, a 1920x1080 hdmi resolution. 24bpp framebuffer. And no scaling. So that all looks as expected. |
@popcornmix sorry, what do you mean? how I can change the config? change to video=HDMI-A-1:1920x1080M-24@60 ? |
I didn't suggest anything. I just looked at the kms state, which didn't have either of the obvious causes for the fuzzy text (a scaled or low bpp framebuffer). |
Although fkms:
kms:
are picking different hdmi resolutions. Do both appear fuzzy or only one? |
@popcornmix |
I'd asked in your forum post for a link to this display as a search only revealed a TK1560-T - you never answered. What is the native resolution of this display? How are you generating your text? It vaguely looks like it's running in a web browser. Both vc4-kms-v3d and vc4-fkms-v3d will be rendering the display through V3D and OpenGL. 4.19 is likely to be working directly with the framebuffer with no acceleration. Does it look blurry on a different HDMI display? |
I'd asked in your forum post for a link to this display as a search only revealed a TK1560-T - you never answered.I did not received the email (the system shows will send a email to me if posted ), sorry I did not reply. What is the native resolution of this display? How are you generating your text? It vaguely looks like it's running in a web browser. Both vc4-kms-v3d and vc4-fkms-v3d will be rendering the display through V3D and OpenGL. 4.19 is likely to be working directly with the framebuffer with no acceleration. Does it look blurry on a different HDMI display? not. we use more that 5 kinds HDMI display. there is no this kind issue. |
@6by9
|
Well that appears to answer your own question - run at 1280x720 60Hz. |
you mean I run xrandr --output HDMI-1 --mode 1280x720 --refresh 60 in kernel 5.10 at hardware version 1.4 , it will be fix ? for our app,we always use 1280x720 for long time |
That's the suggestion. Try it. You can also use preferences/screen configuration from desktop menu for a gui way of setting this. |
@6by9 /etc/X11/xorg.conf.d/10-monitor.conf |
The other thing from your tvservice output is that it is sending full range RGB in DVI mode, when I suspect that 5.10+ will be using limited range HDMI mode (depends on the EDID). This all sounds like it is down to a dodgy EDID. |
Do you have overscan on? I believe that can change the scaling away from the native resolution. |
which kernel I run xrandr --verbose ? kernel 5.10? |
I think I do not have overscan on(I do not know where to switch it on). we only open chromium(no frame,no address bar) pages to as a menu as GUI to display infos |
There was no scaling (see #5085 (comment)) |
Yes, 5.10 or 5.15. |
@6by9 5.10.83-v8 #1 SMP PREEMPT Tue Dec 7 13:42:57 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux |
@6by9 |
do you know it has used in https://github.com/agherzan/meta-raspberrypi for yocto ? if have done, I will clone it to test it |
@6by9 |
@6by9 @kraj |
@6by9 uname -a -- xrandr --verbose |
Hi @6by9 I tried kernel 5.10 and I enlarge the webpage with fingers on the touchscreen. it's clear. |
Describe the bug
HI all,
our application need to show black text on the red background as error,
but fuzzy black text on the red background in a 15.6 touchscreen (Lilliput. The model is tk156a ) on raspberry kernel 5.10 ( ycoto meta-raspberrypi agherzan/meta-raspberrypi@e1014d4), the pi 4 hardware versions are 1.4 and 1.2
at same time, I tested updated raspbian image 2022-04-04-raspios-bullseye-arm64.img.xz(not yocto image) from here: https://www.raspberrypi.com/software/ (kernel 5.15) it has the same issue on both pi4 hardware 1.4 and 1.2
we have pi 4 hardware version 1.2 ,so I tested older yocto image (kernel 4.19 , meta-raspberrypi agherzan/meta-raspberrypi@b112816) ,it works well!( of course ,this image can not startup in hardware 1.4,so we can not use 1.2 boards for our application )
therefore, I think kernel 4.19 work well for the touchscreen ,but updated kernel (5.10,5.15) not work well. Maybe the issue is from HDMI drivers in higher kernel?
so do you know where are the HDMI driver files in kernel? how to modified thems (I mean where is the key code ?)
any help?
I change different resolutions ,but same error.
Steps to reproduce the behaviour
see the pictures here for more info
agherzan/meta-raspberrypi#1069
Device (s)
Raspberry Pi 4 Mod. B
System
Which kernel version:
kernel 5.10
&
kernel 5.15
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: