3 ms·

It's an AMD GPU. Maybe I'll try updating it to 35 just for the hell of it, even though I'm sure it won't have an effect...

• saltcured 5y ago
  As I recall, 34 is where there were some dracut bugs that caused booting to fail too. I don't think it even depended on AMD or not, but perhaps presence or absence of certain peripheral hardware. I had a working 34 system that suddenly wouldn't boot after a kernel update, while booting with an older kernel worked. But, this was because the older kernel was installed with an older dracut producing its initrd image. It took a while to sort out before it was finally stable again. During that broken period, a network install of 34 would produce the same result and there would not be an earlier boot entry to try instead. As I recall, one could rescue it with a rescue disk, downgrading dracut, and rebuilding the initrd. I've been using Fedora since around 2004 I think, and this was one of the rare few software-prevents-boot regressions I can remember (as opposed to me-breaks-config or hardware-fails). It was also an example where the default "quiet boot" obscured what was really going on, as a black screen hiding a bunch of boot activities getting stuck and timing out for many minutes.