Hi, Istvan Toth wrote: > Most > times, about 100 times so far, the compiler ran at 40 minutes, but then it > does not compile the nvidia-current 183.216.01 or the 535.183.01 module. > Because of this, there will be no /boot/initrd.img file, the boot will not > start.
This would match a prematurely ended "make" run. Does it report any error messages ? > [...] amd 5700G cpu [...] > The other time interval is more than 4 hours, on December 5 and > December 26, but then nvidia turned on too, the initrd.img was downloaded, > and the kernel started without errors and works. 4 hours on a ~4 GHz 8 core CPU seems a bit long. Can it be that your system lacks the necessary RAM, swaps heavily, and then lets the Out-Of-Memory killer do its work ? (If enough RAM: It's several years ago that i compiled kernels 5.X on a 4 core Xeon. I remember that "make" option -j8 speeded up compilation a lot.) > Could you help me with some ideas? You could try to catch the complete output of both kinds of runs in order to let "diff" compare them. At least you will have some possibly significant message lines to post here or to google for. Your report lets me assume that you will immediately get the messages of a short, bad run: make deb-pkg ...options... 2>&1 | tee -i "$HOME"/make_deb_pkg_log_1 and then will have to re-try often to get a message log of a good long one: make deb-pkg ...options... 2>&1 | tee -i "$HOME"/make_deb_pkg_log_2 Option -j might be unhelpful for the logging purpose, by making the sequence of messages non-deterministic. Have a nice day :) Thomas
