@Loell_Framework Hi thank you for your support on this forum.
I see you are using different title prefix describing the ticket status such as
[RESPONDED]. This difference might be small for you. But if you don’t have a specific preference for that, could you align the title prefix with the existing ones?
I’m expecting a batch 5 DIY Ryzen machine in the next few weeks, so I figure it’s time to look for a SSD for it.
It’s going to be a Fedora-only system, so I’m currently leaning towards a Samsung, mainly because there exists an - albeit hacky - way of updating firmware from Linux:
Thinking of a
2TB 990 Pro model. Any ideas, counterpoint(s) to that, would be grateful to hear.
Hello, I’m having trouble where no firmware updates are available after updating to use the lvfs-testing repo.
I have a
full debug session and notes as a github gist, but essentially the problem is:
find System Firmware device id
fwupdtool get-devices | grep -v Loading | grep "System Firmware" -A2
│ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
│ │ Summary: UEFI ESRT device
try updating , no available firmware updates
Yep, this is good. One point is I prefer (although I did forget for a hot minute) to stick to [RESOLVED] vs [SOLVED], technically it should be [RESOLVED] per my wishes.
But again, I’ve goofed this in the past myself.
Rationale for why we do this is it makes tracking easier, is kinder on the eyes/consistent and of course, makes search queries consistent.
I find all caps to be harsh. SINCE IT’S GENERALLY SEEN AS YELLING if it’s within a post.