On Fri, 06 Aug 2021 17:10:05 +0000
dep <dep(a)drippingwithirony.com> wrote:
said Gianluca Interlandi:
| I did send a link that you could have used for further reading:
|
|
https://bugzilla.kernel.org/show_bug.cgi?id=201693
|
| I was just sharing my personal experience to be helpful, but there is no
| way I can tell you whether you would have had no problems if you had
| gone the Samsung route. You can always send back what you ordered and
| get a Samsung, but you are the one who will have to deal with it if
| there is an incompatibility. If you want to know the answer for sure you
| would have to contact Samsung and AMD. I don't think anyone on this list
| has ever tested all possible combinations to tell what works and what
| doesn't.
I have no issue with you or anyone on this list over this, and I read the
link top to bottom. All that it said was that the problem always ocurs
with Samsung drives and at least almost always occurs with AMD chipsets. I
have, and have no intention of replacing, an AMD chipset. It is not brand
new, so it is old by some conceivable use of the word. I am buying an SSD
drive. Given the facts as stated, the one sensible conclusion is not to
get a Samsung drive, so I didn't. It is, it seems to me, up to AMD and
Samsung to convince me otherwise, not to me to get in touch with them and
ask to be convinced. Particularly because the Samsungs are ~50 percent
more expensive than other choices among SSDs from brands that I perceive
to be reliable.
Having skimmed the bug (out of curiosity, since I have an AMD-based
system with a Samsung 850 EVO and have never experienced any problems
with that combination), it looks to me like the problem appears when you
combine a pre-Ryzen motherboard with a recent Samsung SSD (newer than
mine). If you have a Ryzen-based system, Samsung drives should be viable.
Older systems with AMD or Intel controllers should avoid the Samsung 860
and 870 drives.
E. Liddell