Hacker News new | past | comments | ask | show | jobs | submit
yeah,

DDR5 training is a huge (UX) issues wrt. boot times (mainly on desktop systems).

sure only "once" if your system is correctly setup, but I have seen too many cases of buggy motherboards not properly handling this

and the biggest issue is the transparency, i.e. you don't see that it does DDR5 "training"/"parameter self adaption". It looks like it's "just stuck" in early EFI.

I was unprepared for how long training would take on my Framework laptop kit with 64 GB of DDR5, and actually thought there was something wrong with it.

Nope, training just took minutes, with nothing but a black screen.

Similar with my new NUC which also used DDR5. I genuinely thought there was something wrong, powered it off and reseated RAM and such. Kept debugging it for about 30 minutes before I searched and found out it might be training. Left it alone and sure enough after about 15 minutes the display started showing stuff.
loading story #50469030
I wasn't aware of DD5 training being expected to take that long often. That would explain why the box that is my current home-lab taking so long to boot when I first put it together (and on one other occasion) but behaving normally every other time. Every day is a school day!
A bit of a problem is that unless you add a PowerVM style boot, it's going to be hard adding indicators in today's "absolutely no status LEDs" world