Added by Daniel Kulesz about 7 years ago. Updated almost 7 years ago.
0%
Description
It was working in Coreboot 4.5 - please find the logs attached.
Files
| cbfs.txt (1020 Bytes) cbfs.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| config.short.txt (444 Bytes) config.short.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| coreboot_console.txt (36 Bytes) coreboot_console.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| config.txt (18.8 KB) config.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| coreboot_timestamps.txt (39 Bytes) coreboot_timestamps.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| payload_config.txt (1.59 KB) payload_config.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| kernel_log.txt (61.1 KB) kernel_log.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| revision.txt (173 Bytes) revision.txt | Daniel Kulesz, 04/14/2017 01:05 PM | ||
| rom_checksum.txt (53 Bytes) rom_checksum.txt | Daniel Kulesz, 04/14/2017 01:05 PM |
Enabling trackpoint is an RTC cmos option. Some things were moved in the layout of the nvram which can cause this. Using nvramtool you can enable it again.
This was announced on mailing list with some instructions: https://mail.coreboot.org/pipermail/coreboot/2017-January/082945.html
I must have overlooked this announcement. Enabling the trackpoint via nvramtool did the trick - many thanks!