On 10/05/2025 at 02:12, Cyril Brulebois wrote:
Possible hint for people trying to understand this bug: forgetting possible firmware fun for a second, could this be some kind of hardware fault, like some power surge, some bad cable, some bad storage, etc.?
That was my first thought. But the fact that it happens after the missing firmware detection may not be just a coincidence. Could it happen when modules are unloaded and reloaded ?
Of course, looking into the installer's dmesg (made persistent in /var/log/installer/syslog alongside the rest) is likely to be a good place to start instead of relying on a (very) (wild) hunch of mine…
Yes, we really need the installer syslog.
