2nd March 2017, 8:04
Thank you both for your replies. My updates:
1. For now at least, i have kept the Nvidia GT610 gpu OUT of the Tower, ie, the only gpu available is still the integrated Intel.
2. Unlike all last night, this morning from a cold boot there was no *initial* black screen; the monitor immediately received the HDMI signal from Tower right from my press of the Tower power button, so i saw the BIOS SSD/HDD unlock prompt & could enter my password without typing blind [like yesterday arvo & night]; i could then successfully enter BIOS*; I could see the Maui grub menu; & it did show me the 1st splash-screen.
3. That might sound basic, but perversely it's a slight improvement; for several hours last night there was no HDMI signal to the monitor.
4. Consistent with the ongoing fault, after the 1st splash-screen there was only the black screen with flashing cursor, again today.
5. I toggled to TTY, then installed the xserver-xorg-video-intel package as recommended, then rebooted. Sadly it made no improvement; still a black screen after the 1st splash-screen. Is there some way i can verify that this package really was fully/properly installed, & is fully-operational?
6. * In BIOS i returned to the "Peripherals" tab to double-check my recent settings change, & i confirmed they are still in place, ie:
(a) Initial Display Output = IGFX [which i assume is the integrated Intel gpu]
(b) Intel Processor Graphics = Enabled
[c) Intel Processor Graphics Memory Allocation = 512 MB
7. Rebooted into another post-splashscreen black screen, then toggled into TTY, opened /var/log/Xorg.0.log again, read thru it. Sadly it has continued trying & failing to load Nvidia & Nouveau modules [WHY?], & also Intel modules [WHY did the Intel package i've just installed not fix this?]. UPDATE: Oh! I've just realised; this file is IDENTICAL to yesterday's one, it has not updated with today's boot [even its date- & time-stamp are identical]. Is that normal? Surely this log file should be kept up to date? Though it is identical, i have attached it here for you to check & agree for yourselves.
Xorg.0.log_20170302.zip (Size: 2.54 KB / Downloads: 705)
8. I checked again in the /usr/share/X11/xorg.conf.d folder. Same as last night, there is only a single file here; 10-quirks.conf . I read it in nano, & it is irrelevant to this problem.
9. I checked again in the /etc/X11 folder. Same as last night, there is NO xorg.conf file here.
10. i ran inxi -Fxz again, & it CONTINUES to show for driver, "FAILED: nouveau". Grrrr.
11. AJ said:
I previously said nothing about this so i don't know why you decided that. In fact, though i did not report it here yesterday, one of the things i had tried was to boot with Live USB, but yesterday it did not work, in that there was constantly no HDMI signal, hence screen stayed black. HOWEVER today, it boots perfectly happily from Live USB, & gives me a normal-looking Maui desktop. From here i can access my Tower's root partition.
12. AJ said:
Given i now can boot from Live USB, then yes i suppose i could do this, BUT... i have no idea at all what to do for the fix... can you pls tell me what steps to perform?
Thanks.
1. For now at least, i have kept the Nvidia GT610 gpu OUT of the Tower, ie, the only gpu available is still the integrated Intel.
2. Unlike all last night, this morning from a cold boot there was no *initial* black screen; the monitor immediately received the HDMI signal from Tower right from my press of the Tower power button, so i saw the BIOS SSD/HDD unlock prompt & could enter my password without typing blind [like yesterday arvo & night]; i could then successfully enter BIOS*; I could see the Maui grub menu; & it did show me the 1st splash-screen.
3. That might sound basic, but perversely it's a slight improvement; for several hours last night there was no HDMI signal to the monitor.
4. Consistent with the ongoing fault, after the 1st splash-screen there was only the black screen with flashing cursor, again today.
5. I toggled to TTY, then installed the xserver-xorg-video-intel package as recommended, then rebooted. Sadly it made no improvement; still a black screen after the 1st splash-screen. Is there some way i can verify that this package really was fully/properly installed, & is fully-operational?
6. * In BIOS i returned to the "Peripherals" tab to double-check my recent settings change, & i confirmed they are still in place, ie:
(a) Initial Display Output = IGFX [which i assume is the integrated Intel gpu]
(b) Intel Processor Graphics = Enabled
[c) Intel Processor Graphics Memory Allocation = 512 MB
7. Rebooted into another post-splashscreen black screen, then toggled into TTY, opened /var/log/Xorg.0.log again, read thru it. Sadly it has continued trying & failing to load Nvidia & Nouveau modules [WHY?], & also Intel modules [WHY did the Intel package i've just installed not fix this?]. UPDATE: Oh! I've just realised; this file is IDENTICAL to yesterday's one, it has not updated with today's boot [even its date- & time-stamp are identical]. Is that normal? Surely this log file should be kept up to date? Though it is identical, i have attached it here for you to check & agree for yourselves.
Xorg.0.log_20170302.zip (Size: 2.54 KB / Downloads: 705)
8. I checked again in the /usr/share/X11/xorg.conf.d folder. Same as last night, there is only a single file here; 10-quirks.conf . I read it in nano, & it is irrelevant to this problem.
9. I checked again in the /etc/X11 folder. Same as last night, there is NO xorg.conf file here.
10. i ran inxi -Fxz again, & it CONTINUES to show for driver, "FAILED: nouveau". Grrrr.
11. AJ said:
Quote:So you can boot this machine via the USB live media an get a display (GUI)
I previously said nothing about this so i don't know why you decided that. In fact, though i did not report it here yesterday, one of the things i had tried was to boot with Live USB, but yesterday it did not work, in that there was constantly no HDMI signal, hence screen stayed black. HOWEVER today, it boots perfectly happily from Live USB, & gives me a normal-looking Maui desktop. From here i can access my Tower's root partition.
12. AJ said:
Quote:You may need to fix this from the Live media using a chroot.
Given i now can boot from Live USB, then yes i suppose i could do this, BUT... i have no idea at all what to do for the fix... can you pls tell me what steps to perform?
Thanks.