Created attachment 536658 [details] 4.17.1-journalctl Included is the journalctl log, and the relevant .config files for the kernel as well as the lspci -k list, in case there is a config error i missed. the original base for the kernel config was a ubuntu one in case that may be relevant or useful (logic being, my hardware works on ubuntu, so one compiled based on that should be solid). the system hangs at boot up merely displaying the loading kernel message and doing nothing else. the kernel version it uses is sys-kernel/gentoo-sources-4.16.0. on versions 4.16.9, 4.16.11, 4.16.12 and 4.17.1 what appears to be the same general error occurs. obviously as the kernel version is not any-more actively supported it is concerning that no supported newer versions work. obviously that is not a full list of available updated versions, and if you would have me try another i will happily do so. of note may be the fact i haven't looked outside the official gentoo sources.
Created attachment 536660 [details] 4.16.0-config
Created attachment 536662 [details] 4.17.1-config
Created attachment 536664 [details] 4.16.0-lspci note that in newer kernels i disabled the sp5100_tco module as i get the impression i do not need or want it. the errors were still there with or without
Can you compile the 4.17 kernel with DEBUG_INFO=y and then recreate the error? Note, typically we don't support errors with proprietary external modules built in. If this goes upstream, you'll be asked to just recreate and make sure your nvidia module is not loaded.
Created attachment 537350 [details] 4.17.0-config
Created attachment 537352 [details] 4.17.0-journalctl possibly of note could be 'systemd-gpt-auto-generator[319]: Failed to determine block device of root file system: No such file or directory'
(In reply to seirra blake from comment #6) > Created attachment 537352 [details] > 4.17.0-journalctl > > possibly of note could be 'systemd-gpt-auto-generator[319]: Failed to > determine block device of root file system: No such file or directory' No Oops in this one? I don't see the error here.
Created attachment 537886 [details] 4.17.0-journalctl-r1 apologies you are correct, i must have been sleepier at the time than i realised when i checked the log, i must have rebooted it too soon. regardless, this log exhibits the errors. i gave it a good 10/20 minutes and no boot, no ability to change tty, (although i didn't expect it to) ctrl+c does nothing.
Error is confirmed exhibited in 4.17.15-r1, appears to be fixed in 4.18.3
(seirra blake in comment #9) > Error is confirmed exhibited in 4.17.15-r1, appears to be fixed in 4.18.3
