Yes I understand, we need though a way to determine if the proprietary
modules tainting the kernel are responsible (for an upstream report
thee is need for the kernel not to be tainted, otherwise there is
unlikely it is going to be looked at).
Totally fair - thanks for explaining. Would a boot from a liveUSB suffice? I did have similar issues off a liveUSB when installing - but it was relatively random, and less frequent.
I tried to SSH In on a hang, but unfortunately, SSH was unresponsive.
Assuming you can access the machine remotely as well, when the system
seems to hang, can you still login remotely to the machine? Is just
the graphical stack not coming up? If you can login, can you provide
the full boot log and check if things matches to the bug #1089513?
Right now I don't use a graphical login like sddm/gdm/etc -- been starting from scratch, so my system boots directly into a terminal. But yes, I also have the 1089513 issue, i.e. Nvidia doesn't work with 6.12.x (but that's a separate issue! 😆)
Secondly, we have in meanwhile 6.12.10 in unstable, can you upgrade to
this kernel. Is the problem still reproducible with 6.12.10?
Is the system booting with quiet in the kernel command line? If Yes,
can you drop it so you get more verbose boot log, where does it stops?
Ooh I can try this!
Recently I've noticed it will boot into 6.12.9 -- it doesn't seem to fail as often (I have been trying it after every apt full-upgrade I run).
I've been keeping everything very up to date, in hopes of a fix ☺️🤞🏻 so, maybe something else got updated recenty?
I'll keep you updated as I dig in further!
Mark