Mmmmm I’ll try a fresh install on a different device to verify next week. I really can’t think of a reason why I would have enabled this. If this is the case another case of PEBCAC… I still think that it should be visible in the updater that you are installing a beta version.
There is a way to see where it is pulling from either /etc/fwupd/remotes.d/ and check the files to see which repo it is configured to use, or in Software check and see which one is enabled in the repositories list. Otherwise it is a feature request for the GUI. The fwupd package which is what is actually doing the work offer the fwupdmgr cli utility and that is the recommended method for interacting with it. Gnome-firmware is nice but not very informative and the integration in the Software application is simple, and intentionally so. It is assumed that you don’t want notifications for literally every concievable event and that he end user knows what is and is not enabled.
I went from 3.04 to 3.17 and started seeing the issue with ACPI temperature sensor 1 spiking randomly, and the fan spiking with it for a fraction of a second. I installed this via LVFS, and the fan is definitely not doing that anymore, which is quite good for my sanity.
Thanks for that!
Yet again, even on 3.18, I encountered another 400 MHz throttling—this time lasting at least half an hour in my estimation.
None of the BIOS updates have improved the situation in any clearly perceptible way.
This issue has wasted so much of my time that I find it to be highly disrespectful; it is absurd that this is a problem that has found itself so widespread on expensive, high-end, production hardware. Surely, in any sane world, this issue would have been identified prior to shipping faulty hardware to a large number of customers. My trust was evidently misplaced, and now I will continue to suffer either the unbearable throttling incidents, or the noticeably degraded performance by disabling Turbo Boost. Either way, it feels like I have wasted money on something that I cannot even use near to its full potential. The laptop is only three years old and I’m itching to have it replaced! This is bananas!
That said, I do appreciate that the device is still getting firmware updates for now (even if they are not fixing any of the several critical issues with the laptop).
Thanks,
(with great sadness)
Sorry you are continuing to experience this issue. I do wonder though since so few people actually experience this in a consistent manner or even at all what environmental factors are being missed. I can only assume at this point that it is most likely a per unit variable or a user induced variable. Troubleshooting something like this without a control unit has to be a nightmare. Without being able to replicate the problem, it is almost impossible to even begin.