Bug #761
Touchscreen not working
| Status: | Closed | Start date: | 14 Jun 2020 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: |  Hammel | % Done: | 100% | |
| Category: | 05 - Releases | |||
| Target version: | 1.1.0 - Upgrades | |||
| Severity: | 01 - Critical |
Description
rpi_ft5406 is not being loaded at boot time. But even if it is loaded, along with the backlight and evdev, the touchscreen is still not working.
Need to try the SD card with forced loading on different hardware to make sure this isn't a hardware problem.
Associated revisions
RM #761: Fall back to kernel 4.19.106 (and matching fw) because 4.19.122 broke touchscreens and 106 is the last known working version before PiBox release 1.1.0.
History
#1
Updated by Hammel about 1 month ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
The last known working combination of kernel/firmware is
- Kernel: git commit 216324a8655b7256961a378893f290d7fa1eecc4 (4.19.69)
- fw: git commit 67bfaeb8457737053d8bab414d3d21c7587043cf
- kernel: git commit 742cb761fa7f2a25e9fc57afd72deb0c47b0c864 (4.19.106) or ecb440abef61d198478b6e598b3510ff6680090a (branch head at time of pull)
- fw: git commit bf83b506b4a6f9e592e711d02871a278fad5bd1e
The former is running on a test touchscreen and everything works. The latter is in rpi4, so I can just try that build.
If either works (the newer the better) then I should revert to those and rebuild the kernel and rpi-firmware, sticking with those commit ids instead of using the head.
#2
Updated by Hammel about 1 month ago
- % Done changed from 10 to 20
Just tested the 4.19.106 kernel and touchscreen works. I'm going to copy that one to the broken release and see if that works. If not, then I'll copy the firmware too.
#3
Updated by Hammel about 1 month ago
- % Done changed from 20 to 70
Verified: 4.19.106 + fw works but 4.19.122 + fw does not.
The 1.1.0 release will use 4.19.106, as will future release until I can figure out what broke.
I've added the git ids to firmware and kernel builds. Need to push them and then rebuild: rpifw, kernel, buildroot, busybox. Since that's most of it I might as well just kick off a complete rebuild of everything to run overnight.
#4
Updated by Hammel about 1 month ago
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
Rebuilds completed for both rpi2 and rpi1 and retested as passed.
Changes committed and pushed.
Closing issue.