I am getting an intermittent screen failure.
The relevant dmesg output is:
[ 8.392335] Goodix-TS 1-0014: Error reading 1 bytes from 0x8140: -5
[ 8.421991] Goodix-TS 1-0014: Error reading 1 bytes from 0x8140: -5
[ 8.449382] Goodix-TS 1-0014: I2C communication failure: -5
It appears to happen approximately 50% of the time.
I feel like this is an i2c address collision.
The raspberry pi usually boots and from an ssh console, I can see when it fails, that there is no i2c device but when it succeeds there is one at 0x5d.
There are other people with similar devices having this issue, I was wondering what the resolution was. I have the 7in LCD touch screen 800x480 and a Raspberry pi 4b.
I think I figured it out.
I went to the fkms version of the kms driver. Boots much faster and without error. Though touch quit working when using the overlays, so I started using the overlays from the DSI_800x480_gt911_har_touch, though there were no fkms drivers in overlays designed specifically for 7in.
Then I had to adjust the baud rate.
#dtoverlay=gt911-3b
#dtoverlay=gt911-4b
The only weird issue that remains, is the sway/wayland has a shut down prompt, that doesn't seem to get the events. It's on the edge of the screen, but the windows underneath get the messages, so the scanning is OK.
"The only weird issue that remains, is the sway/wayland has a shut down prompt, that doesn't seem to get the events. It's on the edge of the screen, but the windows underneath get the messages, so the scanning is OK."
This is likely a related to fkms being firmware driven and kms being kernel driven, and there being restrictions on layers. I can ignore this.
Also, it appears that kms is newer and may still be underdevelopment.
