More painful when it comes up during installation process.
IDK about when a true fix to code might happen but...
a NOPCC option would nice for initial installations where newer users are not yet building their own kernels.
Better yet to help true noobs and expedite things everyone wanting to do a quick and dirty install before recompiling...
couldn't options for MOBO architecture be set automatically based on a quick examination of BIOS date?
For instance the hardware for PCC simply did not exist before a certain date. So that code ideally should be automatically turned off if the BIOS date is not later than that. Not a complete or perfect solution of course. But I suspect the volume of problem reports would be dramatically reduced as many newer Linux inductees tend to either start with well used older hardware or brand new hardware.
More painful when it comes up during installation process.
IDK about when a true fix to code might happen but...
a NOPCC option would nice for initial installations where newer users are not yet building their own kernels.
Better yet to help true noobs and expedite things everyone wanting to do a quick and dirty install before recompiling...
couldn't options for MOBO architecture be set automatically based on a quick examination of BIOS date?
For instance the hardware for PCC simply did not exist before a certain date. So that code ideally should be automatically turned off if the BIOS date is not later than that. Not a complete or perfect solution of course. But I suspect the volume of problem reports would be dramatically reduced as many newer Linux inductees tend to either start with well used older hardware or brand new hardware.