I recently had to install Ubuntu Desktop on a laptop that had a problematic NVidia chipset: The system would always freeze in a very short amount of time - most likely due to a combination of overheating and/or bad drivers. This article saved the day: https://itsfoss.com/fix-ubuntu-freezing/ I just changed the GRUB config for the initial start of installation and everything worked without a single glitch. Even post-install, I did not have to change the grub config Essentially, appending `nomodeset` to the line containing `linux` bypassed the default video check (even though it was listed during setup). Getting to the initial grub config with selecting the "lite" version of the USB partition.
Showing posts from May, 2021
- Other Apps
So while I was working on the last project to "Factory Out" Modules w/ Plaster, it dawned on me: why stop there? Having a standard script outline, that's a template in VS Code, over and over the same steps to make the current script unique -- editing in just the "right places" seems cumbersome when, down the road, you have to update/add functionality, remembering where everything is in this already giant script. All of this to say: Start with a scaffold 'main.ps1' script, that is never touched. Create a unique or 'functions.ps1' script file that is the meat of what needs to be done. The "old way" was to create the new script file and jumble it all together. What I've found is that this is no different (really) in using the "proper" Begin/Process structure - as far as support. In the 'main' file, it would handle the "big 3", standard checks and balances: Argument Testing Main Function Execution Output/Art