| From: Russell via talk <talk@gtalug.org> | On December 9, 2017 9:02:03 AM EST, "Stewart C. Russell via talk" <talk@gtalug.org> wrote: | > http://www.masswerk.at/misc/card-punch-typography/ | | Very interesting link. Also nice to know how little endian transport | "return zero" errors we're being handled back in the day. Return zero? | Most recently, after trying several kernel taints What does that mean? As far as I understand, the kernel reports itself tainted if it observes any of a number of distateful things. Like loading proprietary kernel modules. The idea is that kernel maintainers will ignore problem reports from folks running such modules. | on my Intel gpu, which | is having font rendering issues, I dumped my DSDT table and found | namespace/pstate conflicts in returning zero as serialized data. I'm not sure what "returning zero as serialized data" means in this context. There are lots of buggy ACPI tables. If you are lucky, you can ignore them. You can disassemble ACPI tables and recompile them and get a surprising number of compiler warnings. I vaguely remember hearing the firmware developers generally use a Microsoft ACPI compiler but we Linux users use an Intel compiler, and it flags more errors (or at least different errors) than the Microsoft one. One of the common errors is ACPI routines falling off the end rather than returning a value. Does ACPI have anything to say about GPUs? | Seven | errors and a couple of hundred warnings. I tried Rawhide for better gpu | drivers but no joy there. Perhaps you need this kernel boot parameter: i915.alpha_support=1 Your kernel probably needs to be 4.13 or newer. See <https://www.phoronix.com/scan.php?page=article&item=coffee-uhd-graphics&num=1> (I speak with no experience.)