101–110 of 131 posts
Earlier quoted context omitted.
At least it doesn't contain adware (yet?). I can choose to trust Samsung (I already did when I bought their SSD) and not trust Microsoft.
SSD firmware adding ads to the files you save would be peak ad industry.
Stupid question: is it not possible to use nvme-cli for Samsung SSD updates in Linux?
Is there any significant benefit of updating firmware? Intuitively it seems like the risk/reward is very skewed towards not doing it. I've never really updated the firmware on any component other than routers or motherboard/bios.
I generally don't update firmware ever unless there is a problem. One exception is bios. Then if I have the occassional mysterious freeze/reboot I'll try it. Also if there is something like known ram size or particular hardware fix. But I can count those on 1 hand over 20 years. Also I suppose there are cases when you bought stuff just as it came out, there can be useful firmware updates after the first several month…
Earlier quoted context omitted.
Hard drive, and SSD firmwares have had massive issues in the past, including ones causing major filesystem corruption and data loss. There was even once a bug which, after X hours of SMART recorded usage, would cause the SSD to lockup every hour thereafter: https://www.reddit.com/r/buildapc/comments/oh18a/attention_c... SSD firmware issues can be very serious.
SSD firmware issues? I think you mean SSD issues that are solved by new firmware?
But I meant "faulty firmwares due to bad firmware code, needing updates".
Earlier quoted context omitted.
> I have found that on my machines, they provide a means to disable the security check and allow the downgrade anyway. I was usually able to this, and my other HP machines propose to do a BIOS downgrade. But in this particular case I haven't managed to do a rollback, even with a "BIOS recovery", whatever that is.
That's unfortunate. Does your company buy a lot of these? Perhaps they can get in touch with your supplier to pass a complaint about the poor update so they might be able to pass it on to their devs and hopefully fix the issue?
Such a standard could define capabilities (firmware slots, online update, power cycle required, etc). The OS could handle it from that point.
Earlier quoted context omitted.
That reminds me of an internal hard disk I had several years ago. I think it was a Seagate, but it might have been Western Digital. This was a retail drive bought at BestBuy, and the box specifically said that it worked with Windows, MacOS, and Linux, although it noted that their fancy add-on software only worked under Windows. No problem for me, because I didn't need the fancy add-on software. A year later the drive…
I had same problem with failed Seagate HDD. They were asking me to use their Windows-only app to diagnose the problem. I tried to explain that I use it with a NAS and I cannot install Windows on it just to do such diagnostics test. No luck to convince the support and I had to hack some pieces of old hardware together just to run that tool. Funny enough the tool was able to tell only something like "the drive is broke…
There may be a difference here between the consumer drives and the enterprise drives, or maybe they changed the system to not require it in any case now.
Earlier quoted context omitted.
SSD firmware adding ads to the files you save would be peak ad industry.
I've got a better nightmare - processors injecting ads in realtime :D
This is some insanity that shouldn't be needed, when fwupd[0] exists. Samsung is to blame for this. [0]: https://fwupd.org/
does that firmware update come with any changelog? I have the same drive for my database dev work and I somehow feel uneasy to update it without really knowing what will change, will my specific workload improve or tank due to some other edge case they might have solved or broken? I mean, the drive works fine, will it work even better? for what workloads exactly? All I could find was someone mentioning it works bette…