Suggest using "cpus=1" for initial NVRAM boot-args to give coherent and complete logging output.

Hello, thank you so much for the "Installation Guide", it is amazing!

I have a suggestion for the guide that I think would help people. I went through the guide for Coffee Lake and ran into a kernel panic that was difficult to diagnose because the logging output was incomplete. The boot process stopped at "pci (build ..." and didn't finish the line. This led me to believe that I was "Stuck on RTC..., PCI Configuration Begins, Previous Shutdown..., HPET, HID: Legacy..." After many days of trying to figure out what was wrong I eventually set "cpus=1" as a boot arg, because in my experience, multiple threads cause problems with output. Once I did that, I got the full output with the callstack and kernel panic. It was actually "Invalid frame pointer" that was the problem and I was able to finally resolve my booting issue because my motherboard (Gigabyte Z370 AORUS Gaming 7 with the latest firmware) doesn't have MATs.