09-26-2017, 06:25 PM
Respectfully as I am only moderately skilled in this area, I would reiterate that it is indeed hardware specific especially where the laptops are concerned, and even sometimes firmware specific, but I think it may also be praxis specific because it can involve systemd and work habits on certain machines, such as shutting down from hibernation or suspend, or hard resetting before an update, or after a failed update. It can involve all or several different hardware specifics which is why I posted the Arch page. I am certain the problem exhibits a variety and often even a combination of factors, including hardware specific issues, BIOS ACPI issues, kernel updates, and so forth. I expect this to turn out to be an user instance specific bug with no specific uniform solution. I do not see an across the board solution, other than tuning specific hardware, firmware, software, and praxis to solve the issue on a user by user basis. I have six different boxes on the #120 kernel after this afternoon and none of them exhibits an issue. I expect this to keep coming up in laptops for a while, but at this point I honestly don't think the kernel is flawed. I can only add one instance, and it is not negative. When I updated to #120 on my oldest Dell laptop the screen brightness control keys which had never worked previously worked perfectly afterwards. If there's a fluke on some hardware new keyboard recognition sources may be the cause.
TC
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.