I have LL4.0 temporarily multi-booted with Windows 8, Manjaro, Linux Mint and Elementary OS. The laptop I have is setup[1] in my signature below, which is also listed on my forum profile on the left side of this forum window. The laptop has dual video cards installed (Intel & nVidia) and so has Optimus installed for LL.
LL4 has been working fine with the Intel card. However, when I switched to the nVidia card (the proprietary nVidia 390 driver is installed), and rebooted, LL just ended up frozen on a blank black screen, failing to boot fully, with a small static white 'cursor' visible in the top left corner of the screen. Is this the problem that English Bob (EB) mentioned in his video at the forum link https://www.freecinema2022.gq/forums/tutor...ard-users/ ?
I observed that the same thing happened with Linux Mint 19, when switching from Intel to the nVidia 390 driver. In contrast, I found that this didn't happen with Elementary OS (also Ubuntu-based like LL & LM) - the difference here is that the proprietary nVidia driver installed on Elementary is not 390 but the 384 version.
In the above video link, EB advised that the 390 driver should be replaced by the 396 driver, as the 390 one can "just brick up your system" - he emphasized it was a fault of the nVidia driver, not the operating system. My observations described above - with LL, LM and Elementary - seem to support EB's view. Have you experienced a similar issue with the nVidia 390 driver?
Assuming I can get out of this, using the terminal in the live environment (rather than having to reinstall LL), should I follow English Bob's advice by replacing the nVidia 390 driver for the 396 version? At first impression, this would appear to be a no-brainer. The only problem is that when I installed the 396 driver previously, according to EB's method, it appeared impossible to switch back to the Intel card, as the NVIDIA X Server Settings app wouldn't open, as I reported previously in post #3 of the above forum link.
Many thanks in advance for any advice on this one, which I'm sure must have affected at least some of you with the dual nVidia/Intel video card setup.
All ideas welcome and much appreciated, as always 8)
LL4 has been working fine with the Intel card. However, when I switched to the nVidia card (the proprietary nVidia 390 driver is installed), and rebooted, LL just ended up frozen on a blank black screen, failing to boot fully, with a small static white 'cursor' visible in the top left corner of the screen. Is this the problem that English Bob (EB) mentioned in his video at the forum link https://www.freecinema2022.gq/forums/tutor...ard-users/ ?
I observed that the same thing happened with Linux Mint 19, when switching from Intel to the nVidia 390 driver. In contrast, I found that this didn't happen with Elementary OS (also Ubuntu-based like LL & LM) - the difference here is that the proprietary nVidia driver installed on Elementary is not 390 but the 384 version.
In the above video link, EB advised that the 390 driver should be replaced by the 396 driver, as the 390 one can "just brick up your system" - he emphasized it was a fault of the nVidia driver, not the operating system. My observations described above - with LL, LM and Elementary - seem to support EB's view. Have you experienced a similar issue with the nVidia 390 driver?
Assuming I can get out of this, using the terminal in the live environment (rather than having to reinstall LL), should I follow English Bob's advice by replacing the nVidia 390 driver for the 396 version? At first impression, this would appear to be a no-brainer. The only problem is that when I installed the 396 driver previously, according to EB's method, it appeared impossible to switch back to the Intel card, as the NVIDIA X Server Settings app wouldn't open, as I reported previously in post #3 of the above forum link.
Many thanks in advance for any advice on this one, which I'm sure must have affected at least some of you with the dual nVidia/Intel video card setup.
All ideas welcome and much appreciated, as always 8)
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work