Subj : Intel: Once mighty, now f
To   : Cougar428
From : Arelor
Date : Mon May 19 2025 14:04:27

  Re: Intel: Once mighty, now f
  By: Cougar428 to ARELOR on Mon May 19 2025 08:41 am

 >  I think the fix was to download the update and reboot the system. Of
 >  course I may be wrong about how it was done, but you update drivers for
 >  different hardware all the time. At every OS update.

First of all, we are not talking about a driver. We are talking about a bellow OS operation so it is a serious affair even if it seems clicky-clicky.

Second, you may upgrade your drivers all month log, but how many upgrades are designed to prevent your hardware from catching fire?

I check the changelogs of the stuff I run quite often and I must say updates aimed at preventing catastrophical failure exist in the realm of astronomically unfrequent events.

Seriously, if I was running production on a specific CPU model and it caught fire mid-operation, and the Intel representative told me that it is ok because it is not a hardware problem, that it only takes a UEFI update to fix, I would shove a whole rack full of servers up that guy's ass.




--
gopher://gopher.richardfalken.com/1/richardfalken

---
 þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

.