PDA

View Full Version : [SOLVED] 18.04/18.10 clean install, GTX 970, can only see login screen with nomodeset?


Dáire Fagan
October 29th, 2018, 01:18 AM
From testing so far, I am only able to see the login screen if I remove quiet splash and input nomodeset to the grub options for booting Ubuntu. I have read that after doing this one should sudo apt-get remove --purge nvidia-*, which I have done, and I then installed the highest numbered version nvidia-driver-390. On reboot, unfortunately this made no difference.

From Gnome I next selected the additional drivers tab from Software & Updates, and tried 410 (open source), but the same issue occurred. For a sometimes gamer, which driver will give me the best experience on Ubuntu with my GTX 970, and do I need to make nomodeset permanent or is there something else I should do please?
Bashing-om
October 29th, 2018, 01:59 AM
dusf; Yukkie !



16.10 clean install,



is there something else I should do please?

->>


Ubuntu: Ubuntu 16.10 (Yakkety Yak) was the 25th release of Ubuntu. Support ended on July 20th, 2017.
See: https://ubottu.com/y/yakkety

The software repository for 16.10 no longer exists
So, bottom line is to install a current release - 18.04 is high on the recommendation list.



my bit to try and help
Dáire Fagan
October 29th, 2018, 10:36 AM
Thanks for the reply. Apologies, it was late here last night when I posted. I was stuck on 16.10 as I left it too long to upgrade, but I clean installed 18.10 yesterday evening, and that is the version I seem to have the graphics issue with, that I meant to post about initially, and that I am now asking for help with.

If it helps perhaps there are some logs or other files I could provide?
Bashing-om
October 29th, 2018, 05:57 PM
dusf; Ho Kay :) Let's work 18.10 :)

Please edit the thread title to so reflect this is an 18.10 install.

What returns for terminal commands:


echo $XDG_SESSION_TYPE
dpkg -l | grep -i nvidia
cat /proc/driver/nvidia/version

see what it is going to take to get the proprietary driver installed.



bring up the heat
Dáire Fagan
October 29th, 2018, 07:10 PM
Hi Basing-om, thanks for coming back to me :D Updated thread title with edit post >> go advanced when I first posted several hours ago, I on some forums it only changes the post title in thread, rather than the actual title as visible from the main forum?

Output:


dusf@contraption:~$ echo $XDG_SESSION_TYPEx11
dusf@contraption:~$ dpkg -l | grep -i nvidia
ii libnvidia-cfg1-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA binary OpenGL/GLX configuration library
ii libnvidia-common-390 390.87-0ubuntu1 all Shared files used by the NVIDIA libraries
ii libnvidia-common-410 410.73-0ubuntu0~gpu18.10.1 all Shared files used by the NVIDIA libraries
rc libnvidia-compute-390:amd64 390.87-0ubuntu1 amd64 NVIDIA libcompute package
rc libnvidia-compute-390:i386 390.87-0ubuntu1 i386 NVIDIA libcompute package
ii libnvidia-compute-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA libcompute package
ii libnvidia-compute-410:i386 410.73-0ubuntu0~gpu18.10.1 i386 NVIDIA libcompute package
ii libnvidia-decode-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA Video Decoding runtime libraries
ii libnvidia-decode-410:i386 410.73-0ubuntu0~gpu18.10.1 i386 NVIDIA Video Decoding runtime libraries
ii libnvidia-encode-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVENC Video Encoding runtime library
ii libnvidia-encode-410:i386 410.73-0ubuntu0~gpu18.10.1 i386 NVENC Video Encoding runtime library
ii libnvidia-fbc1-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-fbc1-410:i386 410.73-0ubuntu0~gpu18.10.1 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-gl-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-gl-410:i386 410.73-0ubuntu0~gpu18.10.1 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-ifr1-410:amd64 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA OpenGL-based Inband Frame Readback runtime library
ii libnvidia-ifr1-410:i386 410.73-0ubuntu0~gpu18.10.1 i386 NVIDIA OpenGL-based Inband Frame Readback runtime library
rc nvidia-compute-utils-390 390.87-0ubuntu1 amd64 NVIDIA compute utilities
ii nvidia-compute-utils-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA compute utilities
rc nvidia-dkms-390 390.87-0ubuntu1 amd64 NVIDIA DKMS package
ii nvidia-dkms-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA DKMS package
ii nvidia-driver-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA driver metapackage
rc nvidia-kernel-common-390 390.87-0ubuntu1 amd64 Shared files used with the kernel module
ii nvidia-kernel-common-410 410.73-0ubuntu0~gpu18.10.1 amd64 Shared files used with the kernel module
ii nvidia-kernel-source-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA kernel source package
ii nvidia-prime 0.8.10 all Tools to enable NVIDIA's Prime
ii nvidia-settings 410.73-0ubuntu0~gpu18.10.1 amd64 Tool for configuring the NVIDIA graphics driver
ii nvidia-utils-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA driver support binaries
ii xserver-xorg-video-nvidia-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA binary Xorg driver
dusf@contraption:~$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module 410.73 Sat Oct 20 22:12:33 CDT 2018
GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
Bashing-om
October 29th, 2018, 07:18 PM
dusf; Uh Huh ..

We have a driver conflict:


ii libnvidia-common-390 390.87-0ubuntu1 all Shared files used by the NVIDIA libraries
ii libnvidia-common-410


Per Nvidia the 4.10 driver is what you want to install. Where did you get the 4.10 driver ? As we prepare to purge and re-install the graphic's driver .



maybe Yes
Dáire Fagan
October 29th, 2018, 08:04 PM
Okay. I am with you, does this mean I should sudo apt-get remove one, and if so which one?

So because I was running 16.04/16.10, I was advised previously it would be too difficult to go through the different upgrades. It was never upgraded in the past because there was some error with my sources. So then this issue with graphics occurred after I clean installed Ubuntu 18.10 to / and root partitions, and after selecting Ubuntu from grub, I would see some text at the top, and then a black screen with graphics distortion. After reading some posts online, I was able to login to a TTY, and I tried following different advice, but none of it worked. I was then able to login properly, using nomodeset, and I tried the different graphics drivers visible in software and updates >> additional drivers.

What should I do now?
Bashing-om
October 29th, 2018, 08:16 PM
dusf; Hey ..



What should I do now?


1st is tell me the source of the 4.10 driver. And ... believe me you are over working this ...You are trying to hard .
There is this saying in linux: " If it is hard, you are doing something wrong". But ... there is that learning curve.

So what we look forward to is whatever it may take to clean up the bad driver install and that depends on where you got the driver(s) from. purge the drivers, update the system, and install the 4.10 driver from our trusted PPA.


all in the process
Dáire Fagan
October 29th, 2018, 08:53 PM
dusf; Hey ..



1st is tell me the source of the 4.10 driver. And ... believe me you are over working this ...You are trying to hard .
There is this saying in linux: " If it is hard, you are doing something wrong". But ... there is that learning curve.

So what we look forward to is whatever it may take to clean up the bad driver install and that depends on where you got the driver(s) from. purge the drivers, update the system, and install the 4.10 driver from our trusted PPA.

all in the process



Here is a cat of my .bash_history file, does this help?


sudo apt-get purge nvidia*sudo add-apt-repository ppa:graphics-drivers And update sudo apt-get update
sudo add-apt-repository ppa:graphics-drivers
sudo apt-get update
sudo apt-get install nvidia-410
sudo apt-get install nvidia-390
reboot
sudo apt-remove nvidia*
apt-get purge nvidia*
sudo apt-get purge nvidia*
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install nvidia-
sudo apt-get install nvidia-361
Bashing-om
October 29th, 2018, 09:42 PM
dusf; Yeah ...


That will work well to tell what you have done :)

OK .. moving right on along ...
run:


sudo apt remove --purge nvidia*
sudo apt update
sudo full-upgrade
sudo apt autoremove
sudo ubuntu-drivers autoinstall

where I am "assuming" there is *ONLY* the GTX970 card to deal with.

reboot to see the effect.



easy as falling out of bed wide awake
Dáire Fagan
October 29th, 2018, 09:50 PM
Just a quick one, do you mean sudo apt-get --purge nvidia*?

I ask as I know some of the guides I tried use the asterisk...
Bashing-om
October 29th, 2018, 10:23 PM
dusf;

Well .. apt is now the replacement for apt-get .. and nvidia with out the wildcard will get the job done.
https://www.reddit.com/r/linux/comments/26q2sm/apt_vs_aptget/
http://www.howtogeek.com/234583/simplify-command-line-package-management-with-apt-instead-of-apt-get/
https://mvogt.wordpress.com/2014/04/04/apt-1-0/


Edit: On my 3rd thought of the matter; on this case I do think that nvidia* is the better course - sorry for the miss direction;





my bit to try and help
Dáire Fagan
October 29th, 2018, 10:39 PM
dusf;

Well .. apt is now the replacement for apt-get .. and nvidia with out the wildcard will get the job done.
https://www.reddit.com/r/linux/comments/26q2sm/apt_vs_aptget/
http://www.howtogeek.com/234583/simplify-command-line-package-management-with-apt-instead-of-apt-get/
https://mvogt.wordpress.com/2014/04/04/apt-1-0/


Edit: On my 3rd thought of the matter; on this case I do think that nvidia* is the better course - sorry for the miss direction;



my bit to try and help




Okay, the first time I did that command just with nvidia and with nvidia*. Also added apt before full-upgrade. Unfortunately the same issue on rebooting, purple screen after selecting login.

After editing grub to include nomodeset again to login, I tried all of the commands again (although not as much seemed to happen, much less output), this time without the nvidia* (just nvidia instead), but unfortunately same purple screen trying to boot.

I am attaching a picture of the grub options in case that helps?

Output from second input of commands:


dusf@contraption:~$ sudo apt remove --purge nvidia[sudo] password for dusf:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'nvidia' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
dusf@contraption:~$ sudo apt update
Hit:1 http://ie.archive.ubuntu.com/ubuntu cosmic InRelease
Hit:2 http://ie.archive.ubuntu.com/ubuntu cosmic-updates InRelease
Hit:3 http://ie.archive.ubuntu.com/ubuntu cosmic-backports InRelease
Hit:4 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic InRelease
Ign:5 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable Release
Ign:7 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu cosmic InRelease
Err:8 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu cosmic Release
404 Not Found [IP: 91.189.95.83 80]
Hit:9 http://apt.insynchq.com/ubuntu cosmic InRelease
Get:10 http://security.ubuntu.com/ubuntu cosmic-security InRelease [79.6 kB]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/team-xbmc/ppa/ubuntu cosmic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
dusf@contraption:~$ sudo full-upgrade
sudo: full-upgrade: command not found
dusf@contraption:~$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
dusf@contraption:~$ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
dusf@contraption:~$ sudo ubuntu-drivers autoinstall
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Bashing-om
October 29th, 2018, 10:53 PM
dusf; Yukkie ..

Hummmm .. the last screenshot of grub indicates that grub is not finding its boot files. Do not know what to make of that - yet .

Still able to boot to the console interface ( ctl+alt+F2) ?


The http://ppa.launchpad.net/team-xbmc/ppa/ubuntu PPA has not seen any action in a long time:
http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/dists/
disable that PPA.

And that last " ubuntu-drivers autoinstall" not doing anything is perplexing .

what shows :


lsmod | grep nvidia
dpkg-query -l nvidia* | grep ii
cat /var/log/gpu-manager.log


see what we can finger out here .
Dáire Fagan
October 29th, 2018, 11:05 PM
Okay, so just rebooted again and cannot access console with ctl+alt+f2, although I was able to at some point, though I may have been trying different custom grub commands to try and boot at the time. Also, just in case unclear, I can boot fine with nomodeset, I am typing this now on the same computer with the issue.

I will come back to removing the PPA.

Yeah so there was much more output from ubuntu-drivers autoinstall - the first time I input it and rebooted, just not the second time.


dusf@contraption:~$ lsmod | grep nvidianvidia_uvm 815104 0
nvidia_drm 40960 8
nvidia_modeset 1040384 17 nvidia_drm
nvidia 16572416 809 nvidia_uvm,nvidia_modeset
drm_kms_helper 172032 2 nvidia_drm,i915
drm 458752 12 drm_kms_helper,nvidia_drm,i915
ipmi_msghandler 102400 2 ipmi_devintf,nvidia
dusf@contraption:~$ dpkg-query -l nvidia* | grep ii
ii nvidia-compute-utils-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA compute utilities
ii nvidia-dkms-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA DKMS package
ii nvidia-driver-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA driver metapackage
ii nvidia-kernel-common-410 410.73-0ubuntu0~gpu18.10.1 amd64 Shared files used with the kernel module
ii nvidia-kernel-source-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA kernel source package
ii nvidia-prime 0.8.10 all Tools to enable NVIDIA's Prime
ii nvidia-settings 410.73-0ubuntu0~gpu18.10.1 amd64 Tool for configuring the NVIDIA graphics driver
ii nvidia-utils-410 410.73-0ubuntu0~gpu18.10.1 amd64 NVIDIA driver support binaries
dusf@contraption:~$ cat /var/log/gpu-manager.log
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/4.18.0-10-generic/updates/dkms
Found nvidia module: nvidia-modeset.ko
Looking for amdgpu modules in /lib/modules/4.18.0-10-generic/updates/dkms
Is nvidia loaded? yes
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is nvidia kernel module available? yes
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:412
BusID "PCI:0@0:2:0"
Is boot vga? no
Error: can't access /sys/bus/pci/devices/0000:00:02.0/driver
The device is not bound to any driver.
Vendor/Device Id: 10de:13c2
BusID "PCI:1@0:0:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Does it require offloading? no
last cards number = 2
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
Has the system changed? No
Unsupported discrete card vendor: 8086
Nothing to do
Bashing-om
October 29th, 2018, 11:38 PM
dusf; Ouch !!

We do have a horse of a different color. Intel graphics are at play .. and it is the Intel driver at fault here !
This is not single GTX970 system.



Vendor/Device Id: 8086:412
BusID "PCI:0@0:2:0"
Is boot vga? no
Error: can't access /sys/bus/pci/devices/0000:00:02.0/driver
//
last cards number = 2
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2


So we back up and regroup. Change focus to Intel .
what shows:


dpkg -l xserver-xorg-core xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-dri:i386

Be aware I do not have Intel graphics and can not directly verify what is sane - we may be flying a bit by the seat of our pants.

as this is now a Optimus system we look at what the hardware is and for a config file.
what shows:


lspci -k|grep -iEA5 'vga|3d'
ls -al /usr/share/X11/xorg.conf.d/*.conf


With the hope here all we have to do is remove an old config file and generate a new one.


but only a maybe
23dornot23d
October 30th, 2018, 01:34 PM
This is a interesting read ............ might affect the problem .........

https://ubuntuforums.org/showthread.php?t=2404556

I run optimus - with bumblebee on one system - also the primus on another and it shows performance mode - yet does not use it ..........

https://47e044bd-a-62cb3a1a-s-sites.googlegroups.com/site/000menu/wayland/problems-ubuntu-build/Screenshot%20at%202018-10-30%2020-01-05.png?attachauth=ANoY7cryHX9kjY6_TsThtXfCr1cDX2hU eisgvs896UDHbd3yulF-L4gQApfTNHRFo_J3csec4QybGKVUumjHSMIchE05WLBu7MfTsG 43tUwUpvCJgJ2Kh0TAbia04hDNITczHkoKnjjq9QpBjCqAXreU PK5c0DItUazln2lMFU3s9Lg9FQmS28NPRc6VWYTRMeHCUy3cXK 55UufBkZrY_MRZmEjIP-zPehvRbhZP2EVbl70tSMKjcAocJ-1EfThxMmgfLZ2jbgt2C3qhxwg2yOlz-Snk5r-6GA%3D%3D&attredirects=0

So the above link about gdm and lightdm ......... might be the solution to some of the problems encountered - I have yet to try it out though.

I do have a few videos - where I have been trying things out on 18.10 ......

https://www.youtube.com/channel/UCzt6wlVmVjPeCjY9_gtmo0A?view_as=subscriber
(https://www.youtube.com/channel/UCzt6wlVmVjPeCjY9_gtmo0A?view_as=subscriber)
This video in particular shows glxspheres running - yet the card does not work as expected with blender ......... as when blender
picks up the card it gives the option to use it ............ ( or should do )

https://youtu.be/c2IVi70H05s

I am hoping that by switching to lightdm from gdm3 ........... that it might also solve my problem .............

I also hope it helps in solving the problem you have here too - if not it may help someone else .........

My nvidia graphics card is not the same as yours (primary is intel i915 - secondary graphics gt540) - but maybe the same reason its not working is due to something else - like it not been used because of something else is switching it off for some reason .

The command below shows a lot of the system information too - it may need installing though - its quite a good command for information
about the system http://manpages.ubuntu.com/manpages/trusty/man1/inxi.1.html

inxi -F


Update - have now swapped to lightdm ......... a lot more things are working now can even run the cairo-dock desktop - which would not run from gdm3 ........ the nvidia settings pulls up all the information and I can see now that there may be another problem - due to blacklisting my nvidia card for some reason ..... only where you un-blacklist it - is not shown. ( well just one more thing - to find out where ubuntu has blacklisted the nvidia card ........ ) should be obvious where its doing it - but its not.

or is it ...... ? /etc/modprobe.d/blacklist.conf

in my case it seems to be bumblebee that blacklists it in the /etc/modprobe.d/bumblebee.conf ........... but why it never lets it work is another question ?

Still working on this ...... as I now have 3 screen shots telling me it knows its there ..... question is - why does it not want to use it .........


Will give it one more go from the official nvidia site ........ https://www.geforce.com/drivers/results/137276

That failed ..... its put it into really low resolution graphics - will remove and go back to what I had before ..... which is the
one from ubuntu ..... strange really - as that does load in as shown below these screens would come up with a warning
message that you are not using the nvidia driver as it does in the low resolution one that I used from above that was manually
installed.

Not sure what to do next .......... but as in the past as time goes on ........ things often change .........

I will have to revert back to older versions for doing 3d ........ but that is no problem ........ hope someone else has
more success with the dual cards ....... best of luck .........

https://47e044bd-a-62cb3a1a-s-sites.googlegroups.com/site/000menu/wayland/problems-ubuntu-build/Screenshot%20at%202018-10-30%2020-02-24.png?attachauth=ANoY7cor3XQoB5XCr7EbWKDBTprtvtoQ XvNNEHmyScxfkg9xLbFwMDiOQLMzu9IXYmRhseSJrvVg4fG61P q_R-HXfbSCkzBUqxa-Zv4pxWN8T5YH9D0qzxQ5sGRB-XtFuIEQmL49WwCYoy9sj8SqyAQzwjEtr2Tt_-Y5ULKGf-h0O2ijeMCcnAtLhuPGXpbrDy85RNfBGM20QOTGQK4JJ_DBN4hi WfIN513cxJ5yKT189NIXSXJmdgq69t10_zzxbjIKNgRByCbVal cu96oWN19laQtI0LvKNg%3D%3D&attredirects=0
Dáire Fagan
October 31st, 2018, 02:29 PM
dusf; Ouch !!

We do have a horse of a different color. Intel graphics are at play .. and it is the Intel driver at fault here !
This is not single GTX970 system.

Firstly, sorry for late reply, I have a lot going on.

Secondly, 'a horse of a different colour' indeed! :lolflag:

So it is a single GTX970 in the sense that it is my only graphics card, apart from onboard graphics on the Intel i5 CPU:


disf@contraption:~$ lspci | grep VGA00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)





So we back up and regroup. Change focus to Intel .
what shows:


dpkg -l xserver-xorg-core xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-dri:i386

Be aware I do not have Intel graphics and can not directly verify what is sane - we may be flying a bit by the seat of our pants.

I can hear the Flight of the Valkyries as we fly!


dusf@contraption:~$ dpkg -l xserver-xorg-core xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-dri:i386Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================================================== ==============-=====================================-=====================================-================================================== ================================================== ==================================
ii libgl1-mesa-dri:amd64 18.2.2-0ubuntu1 amd64 free implementation of the OpenGL API -- DRI modules
ii libgl1-mesa-dri:i386 18.2.2-0ubuntu1 i386 free implementation of the OpenGL API -- DRI modules
un libgl1-mesa-glx <none> <none> (no description available)
ii xserver-xorg-core 2:1.20.1-3ubuntu2.1 amd64 Xorg X server - core server
ii xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 amd64 X.Org X server -- Intel i8xx, i9xx display driver
dpkg-query: no packages found matching libgl1-mesa-glx:i386


Just to be clear, and I think you get this already, but I do not want to use the Intel graphics, just the GTX970 - although it is of course nice to to have the Intel i5 graphics to fall back on as a redundancy.


as this is now a Optimus system we look at what the hardware is and for a config file.
what shows:


lspci -k|grep -iEA5 'vga|3d'
ls -al /usr/share/X11/xorg.conf.d/*.conf



dusf@contraption:~$ lspci -k|grep -iEA5 'vga|3d'00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
Kernel driver in use: snd_hda_intel
--
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970]
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 High Definition Audio Controller
dusf@contraption:~$ ls -al /usr/share/X11/xorg.conf.d/*.conf
-rw-r--r-- 1 root root 92 Sep 18 08:23 /usr/share/X11/xorg.conf.d/10-amdgpu.conf
-rw-r--r-- 1 root root 206 Oct 25 19:29 /usr/share/X11/xorg.conf.d/10-nvidia.conf
-rw-r--r-- 1 root root 1350 Oct 25 15:53 /usr/share/X11/xorg.conf.d/10-quirks.conf
-rw-r--r-- 1 root root 92 Sep 18 09:54 /usr/share/X11/xorg.conf.d/10-radeon.conf
-rw-r--r-- 1 root root 945 Oct 16 05:48 /usr/share/X11/xorg.conf.d/40-libinput.conf
-rw-r--r-- 1 root root 3025 Apr 3 2018 /usr/share/X11/xorg.conf.d/70-wacom.conf




With the hope here all we have to do is remove an old config file and generate a new one.
but only a maybe



Oh, and if relevant, I am dual booting with Windows 10, and have had different kinds of custom LVM LUKS dm-crypt separate partition installs in the past - just in case those installs from the past may mean GRUB config is affected some how. After the latest install I did not do anything with GRUB, I just rebooted, and my bootmenu looked exactly the same.

Lead on...

23dornot23d thanks for posting, although I think bashing-om will make a lot more sense of what you have said than I will :)

My GTX970 worked fine on my last install of 16.04/16.10 - not sure if I had to do anything special or not to make it work, though as I type this I think I did post here before about 'black screen on boot'.
Kubilay_Ovacikli
October 31st, 2018, 06:03 PM
Hi!

I've faced a similar problem after upgrading to 18.10 with a Vaio with Nvidia graphics card. The system refused to boot and remained at the stage of loading graphics driver. After removing the nvidia drivers the system seems to boot now, but struggling with graphics actually. The response time to modifications in folder windows is too slow now...


ii libnvidia-cfg1-390:amd64 390.87-0ubuntu1 amd64 NVIDIA binary OpenGL/GLX configuration libraryii libnvidia-common-390 390.87-0ubuntu1 all Shared files used by the NVIDIA libraries
ii libnvidia-compute-390:amd64 390.87-0ubuntu1 amd64 NVIDIA libcompute package
ii libnvidia-compute-390:i386 390.87-0ubuntu1 i386 NVIDIA libcompute package
ii libnvidia-decode-390:amd64 390.87-0ubuntu1 amd64 NVIDIA Video Decoding runtime libraries
ii libnvidia-decode-390:i386 390.87-0ubuntu1 i386 NVIDIA Video Decoding runtime libraries
ii libnvidia-encode-390:amd64 390.87-0ubuntu1 amd64 NVENC Video Encoding runtime library
ii libnvidia-encode-390:i386 390.87-0ubuntu1 i386 NVENC Video Encoding runtime library
ii libnvidia-fbc1-390:amd64 390.87-0ubuntu1 amd64 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-fbc1-390:i386 390.87-0ubuntu1 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-gl-390:amd64 390.87-0ubuntu1 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-gl-390:i386 390.87-0ubuntu1 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-ifr1-390:amd64 390.87-0ubuntu1 amd64 NVIDIA OpenGL-based Inband Frame Readback runtime library
ii libnvidia-ifr1-390:i386 390.87-0ubuntu1 i386 NVIDIA OpenGL-based Inband Frame Readback runtime library
ii libnvtt2:amd64 2.0.8-1+dfsg-8.1build1 amd64 NVIDIA Texture Tools
ii xserver-xorg-video-nvidia-390 390.87-0ubuntu1 amd64 NVIDIA binary Xorg driver



cat /proc/driver/nvidia/version
cat: /proc/driver/nvidia/version: No such file or directory
Bashing-om
October 31st, 2018, 09:32 PM
dusf; Hummmm ...

All we know presently is that Intel can not load a driver:


Error: can't access /sys/bus/pci/devices/0000:00:02.0/driver


So now the question is the signal flow:


MUX-less: Optimus chipsets - that is, dual GPUs where the outputs are NOT switched between the GPUs using a multiplexer.
the Intel GPU would need to be active since MUX-less works by the nvidia doing the work but the Intel writing the framebuffer to the outputs, rather than with MUX systems where each GPU writes to its own framebuffers, and the outputs are switched between the 2 GPUs.

So run:


/usr/bin/prime-supported

that generates /var/log/prime-supported.log.
Show is that file:


cat /var/log/prime-supported.log
sudo grep -i switcheroo /boot/config-*

And, lets have a look at the config file - I expect that it is sane as it is of recent generation (Oct 25 19:29 /usr/share/X11/xorg.conf.d/10-nvidia.conf):


cat /usr/share/X11/xorg.conf.d/10-nvidia.conf

but will not hurt to see what Xorg expects.

'Tis a puzzle


we try and put the pieces together
Dáire Fagan
November 1st, 2018, 01:31 AM
dusf; Hummmm ...

All we know presently is that Intel can not load a driver:


So now the question is the signal flow:

So run:


/usr/bin/prime-supported

that generates /var/log/prime-supported.log.
Show is that file:


cat /var/log/prime-supported.log
sudo grep -i switcheroo /boot/config-*

And, lets have a look at the config file - I expect that it is sane as it is of recent generation (Oct 25 19:29 /usr/share/X11/xorg.conf.d/10-nvidia.conf):


cat /usr/share/X11/xorg.conf.d/10-nvidia.conf

but will not hurt to see what Xorg expects.

'Tis a puzzle

we try and put the pieces together





dusf@contraption:~$ sudo /usr/bin/prime-supported
dusf@contraption:~$ cat /var/log/prime-supported.log
No offloading required. Abort
dusf@contraption:~$ sudo grep -i switcheroo /boot/config-*
CONFIG_VGA_SWITCHEROO=y
dusf@contraption:~$ cat /usr/share/X11/xorg.conf.d/10-nvidia.conf
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
EndSection


Do I need to change something for the log generation?
Bashing-om
November 1st, 2018, 01:58 AM
dusf; Yukkie on me -

I am at a total loss here - no real idea if how to move forward:

I expected the config file to be somewhat similar:


Section "ServerLayout" #
#should be as this
Identifier "layout" ##should be as this
Screen 0 "nvidia"
Inactive "intel"
EndSection


Section "Device"
Identifier "intel"
Driver "intel"
BusID "PCI:0@0:2:0"
Option "AccelMethod" "SNA"
EndSection


Section "Screen"
Identifier "intel"
Device "intel"
EndSection


Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:8@0:0:0"
Option "ConstrainCursor" "off"
EndSection


Section "Screen"
Identifier "nvidia"
Device "nvidia"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection

Where the Intel hardware is seen.

The log file does not give us any additional info from what we know - that no driver is available.

I am stuck .. will have to give it some thought as to how to insure that an Intel Graphic's driver is installed, and the config file is populated sanely, and if this system is mux-less.



A know it all I am not
23dornot23d
November 1st, 2018, 04:37 PM
I will add a little here - as I have followed this from the start and learned a lot from it .......

I sit in the background - due to not wanting to confuse this situation too much as it is slightly different to my own ........

But I will add this ...... when I do a new install I always keep a full backup of the clean system .......

*this is so If things go pear shaped I can go back and start from a relatively clean slate.

Any way - to the point ......... one has messed up config files somewhere ...... no idea why or how or where they are .........

So I started again from the clean install ...... then using new knowledge gained from this thread and others I have read -


I set about it again this time with success .........

so just to keep the thread going - it seems there are three types of situation with the MUX type cards ........

found out a lot from here https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28#some-success-report

https://camo.githubusercontent.com/a1cdea34451339f0537fe0e5226f2f52e4cf93fd/68747470733a2f2f692e696d6775722e636f6d2f4749377638 476b2e6a7067


Then also this about bumblebee ........... SO maybe one question needs asking is Bumblebee installed on your system and if so is it the cause of problems when
you try to use the discreet card ...... there seems to be a mention of some sort of loop situation where the computer gets confused with the two cards and then
goes into a loop leaving only a black screen after booting into the desired installation

https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-300953759

Any way was just a thought and seeing you will only be on later as you are in a different time zone to me - I thought I would leave the links to browse through at your
leisure ...... mainly aimed at Bashing-Om ....... but also might be interesting to dusf.

look in the /etc/bumblebee/

base@base-K53SV:~$ cd /etc/bumblebee
base@base-K53SV:/etc/bumblebee$ ls
bumblebee.conf xorg.conf.d xorg.conf.nouveau xorg.conf.nvidia


directory as this has some config files in it that you may or may not be aware of ..... that is of course if (bumblebee) is loaded and in place ........

My own system now seems to be finding it ..........

https://sites.google.com/site/000menu/_/rsrc/1541040585707/wayland/problems-ubuntu-build/Screenshot%20at%202018-11-01%2003-33-03.png?height=224&width=400

but there is still some work to do ........

https://sites.google.com/site/000menu/_/rsrc/1541040557960/wayland/problems-ubuntu-build/Screenshot%20at%202018-11-01%2003-36-03.png?height=224&width=400


base@base-K53SV:~$ optirun --version
optirun (Bumblebee) 3.2.1
Copyright (C) 2011 The Bumblebee Project
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Bashing-om
November 1st, 2018, 08:57 PM
@23dornot23d :)
Great find, wonderful that you shared !

Guys, here is my thought.
As this system performed seamlessly on former installs, we have a MUX-less system.
As we have no Intel driver loaded I make the proposal we purge Nvidia, remove the config file, re-install ALL the Intel driver pieces -> reboot and come back up with the default nouveau driver. See then where we stand .. and if all appears acceptable then install the Nvidia proprietary driver.



maybe a way forward
23dornot23d
November 1st, 2018, 09:50 PM
As we have no Intel driver loaded I make the proposal we purge Nvidia, remove the config file, re-install ALL the Intel driver pieces -> reboot and come back up with the default nouveau driver.


mmm ...... this may work ....... then possibly try this ( only do things that Bashing Om says to do - I will try to keep a low profile ) too many cooks so to say ..........

Preferences - Additional Drivers - worked for me ...... but I did start from an almost clean install that I had on a backup drive. ( keep going slow though with one thing at a time )

( got to say here - that the other version I was working on ran into problems with things left over from before - that would not remove ...... something to do with nvidiagl - cannot
remember exactly which files they were - but they were persistent and locked into the system somehow - even purge would not get rid of them )

See how it goes anyhow - you may be luckier than me ........... ;) I will go back now to doing some 3D ......
Dáire Fagan
November 2nd, 2018, 10:26 PM
23dornot23d, thank you for the input :)

FTR, bash: cd: /etc/bumblebee: No such file or directory.

Bashing-om, can you please list the exact commands you would like me to input?
Bashing-om
November 2nd, 2018, 11:58 PM
dusf; Sure !

I "think" we want to run:


sudo apt purge nvidia*
sudo rm /usr/share/X11/xorg.conf.d/10-nvidia.conf
sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-dri:i386
sudo dpkg-reconfigure xserver-xorg

Any errors, we want to see all in context.

Reboot and let's see what we have now to work with .


cat /var/log/gpu-manager.log




look'n for that way forward
Dáire Fagan
November 3rd, 2018, 10:18 PM
Thanks for that!

Input and output of commands before reboot:


dusf@contraption:~$ sudo apt purge nvidia*[sudo] password for dusf:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'nvidia-390-dev' for glob 'nvidia*'
Note, selecting 'nvidia-325-updates' for glob 'nvidia*'
Note, selecting 'nvidia-346-updates' for glob 'nvidia*'
Note, selecting 'nvidia-driver-binary' for glob 'nvidia*'
Note, selecting 'nvidia-331-dev' for glob 'nvidia*'
Note, selecting 'nvidia-304-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-384-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-346-updates' for glob 'nvidia*'
Note, selecting 'nvidia-compute-390' for glob 'nvidia*'
Note, selecting 'nvidia-340-updates-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-common' for glob 'nvidia*'
Note, selecting 'nvidia-331-updates-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-cg-toolkit' for glob 'nvidia*'
Note, selecting 'nvidia-driver-libs-i386:i386' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-common-390' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-common-396' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-common-410' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-340-updates' for glob 'nvidia*'
Note, selecting 'nvidia-384-updates' for glob 'nvidia*'
Note, selecting 'nvidia' for glob 'nvidia*'
Note, selecting 'nvidia-driver' for glob 'nvidia*'
Note, selecting 'nvidia-367-updates' for glob 'nvidia*'
Note, selecting 'nvidia-modprobe' for glob 'nvidia*'
Note, selecting 'nvidia-texture-tools' for glob 'nvidia*'
Note, selecting 'nvidia-utils' for glob 'nvidia*'
Note, selecting 'nvidia-387-updates' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-340xx-vdpau-driver' for glob 'nvidia*'
Note, selecting 'nvidia-349-updates' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-304-updates' for glob 'nvidia*'
Note, selecting 'nvidia-310-updates' for glob 'nvidia*'
Note, selecting 'nvidia-331-updates' for glob 'nvidia*'
Note, selecting 'nvidia-352-dev' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-304xx-vdpau-driver' for glob 'nvidia*'
Note, selecting 'nvidia-vdpau-driver' for glob 'nvidia*'
Note, selecting 'nvidia-346-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-331-updates' for glob 'nvidia*'
Note, selecting 'nvidia-utils-390' for glob 'nvidia*'
Note, selecting 'nvidia-utils-396' for glob 'nvidia*'
Note, selecting 'nvidia-smi' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-361-updates' for glob 'nvidia*'
Note, selecting 'nvidia-313-updates' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-340xx-kernel-dkms' for glob 'nvidia*'
Note, selecting 'nvidia-334-updates' for glob 'nvidia*'
Note, selecting 'nvidia-utils-410' for glob 'nvidia*'
Note, selecting 'nvidia-331-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-prime' for glob 'nvidia*'
Note, selecting 'nvidia-dkms-390' for glob 'nvidia*'
Note, selecting 'nvidia-dkms-396' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-dkms' for glob 'nvidia*'
Note, selecting 'nvidia-dkms-410' for glob 'nvidia*'
Note, selecting 'nvidia-current-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-dev' for glob 'nvidia*'
Note, selecting 'nvidia-387-dev' for glob 'nvidia*'
Note, selecting 'nvidia-nsight' for glob 'nvidia*'
Note, selecting 'nvidia-common' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-346-updates' for glob 'nvidia*'
Note, selecting 'nvidia-352-updates' for glob 'nvidia*'
Note, selecting 'nvidia-headless-no-dkms-390' for glob 'nvidia*'
Note, selecting 'nvidia-headless-no-dkms-396' for glob 'nvidia*'
Note, selecting 'nvidia-headless-no-dkms-410' for glob 'nvidia*'
Note, selecting 'nvidia-openjdk-8-jre' for glob 'nvidia*'
Note, selecting 'nvidia-current-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-352-updates' for glob 'nvidia*'
Note, selecting 'nvidia-compute-utils-390' for glob 'nvidia*'
Note, selecting 'nvidia-compute-utils-396' for glob 'nvidia*'
Note, selecting 'nvidia-compute-utils-410' for glob 'nvidia*'
Note, selecting 'nvidia-355-updates' for glob 'nvidia*'
Note, selecting 'nvidia-driver-libs-nonglvnd' for glob 'nvidia*'
Note, selecting 'nvidia-375-dev' for glob 'nvidia*'
Note, selecting 'nvidia-current' for glob 'nvidia*'
Note, selecting 'nvidia-profiler' for glob 'nvidia*'
Note, selecting 'nvidia-375-updates' for glob 'nvidia*'
Note, selecting 'nvidia-driver-390' for glob 'nvidia*'
Note, selecting 'nvidia-driver-396' for glob 'nvidia*'
Note, selecting 'nvidia-337-updates' for glob 'nvidia*'
Note, selecting 'nvidia-358-updates' for glob 'nvidia*'
Note, selecting 'nvidia-367-dev' for glob 'nvidia*'
Note, selecting 'nvidia-driver-410' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-toolkit' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-304xx-driver' for glob 'nvidia*'
Note, selecting 'nvidia-driver-libs' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-source' for glob 'nvidia*'
Note, selecting 'nvidia-378-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-319-updates' for glob 'nvidia*'
Note, selecting 'nvidia-304-dev' for glob 'nvidia*'
Note, selecting 'nvidia-331-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-visual-profiler' for glob 'nvidia*'
Note, selecting 'nvidia-persistenced' for glob 'nvidia*'
Note, selecting 'nvidia-361-dev' for glob 'nvidia*'
Note, selecting 'nvidia-settings-binary' for glob 'nvidia*'
Note, selecting 'nvidia-361-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-304' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-331' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-340' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-346' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-352' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-361' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-367' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-375' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-384' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-387' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-390' for glob 'nvidia*'
Note, selecting 'nvidia-352-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-331-updates' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-352-updates' for glob 'nvidia*'
Note, selecting 'nvidia-304-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-headless-390' for glob 'nvidia*'
Note, selecting 'nvidia-headless-396' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-340xx-driver' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-304-updates' for glob 'nvidia*'
Note, selecting 'nvidia-headless-410' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-dev' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-doc' for glob 'nvidia*'
Note, selecting 'nvidia-340-updates' for glob 'nvidia*'
Note, selecting 'nvidia-361-updates' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-dev' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-dev' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-304xx-kernel-dkms' for glob 'nvidia*'
Note, selecting 'nvidia-cg-dev' for glob 'nvidia*'
Note, selecting 'nvidia-cg-doc' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-340-updates' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-361-updates' for glob 'nvidia*'
Note, selecting 'nvidia-381-updates' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-304' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-331' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-340' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-346' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-352' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-361' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-367' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-375' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-gdb' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-304' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-384' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-387' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-310' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-313' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-390' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-319' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-325' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-331' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-334' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-337' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-340' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-343' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-346' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-349' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-352' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-355' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-358' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-361' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-364' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-367' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-375' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-378' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-381' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-384' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-387' for glob 'nvidia*'
Note, selecting 'nvidia-343-updates' for glob 'nvidia*'
Note, selecting 'nvidia-364-updates' for glob 'nvidia*'
Note, selecting 'nvidia-304' for glob 'nvidia*'
Note, selecting 'nvidia-310' for glob 'nvidia*'
Note, selecting 'nvidia-313' for glob 'nvidia*'
Note, selecting 'nvidia-319' for glob 'nvidia*'
Note, selecting 'nvidia-325' for glob 'nvidia*'
Note, selecting 'nvidia-331' for glob 'nvidia*'
Note, selecting 'nvidia-334' for glob 'nvidia*'
Note, selecting 'nvidia-337' for glob 'nvidia*'
Note, selecting 'nvidia-340' for glob 'nvidia*'
Note, selecting 'nvidia-343' for glob 'nvidia*'
Note, selecting 'nvidia-346' for glob 'nvidia*'
Note, selecting 'nvidia-349' for glob 'nvidia*'
Note, selecting 'nvidia-352' for glob 'nvidia*'
Note, selecting 'nvidia-355' for glob 'nvidia*'
Note, selecting 'nvidia-358' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-source-390' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-source-396' for glob 'nvidia*'
Note, selecting 'nvidia-361' for glob 'nvidia*'
Note, selecting 'nvidia-364' for glob 'nvidia*'
Note, selecting 'nvidia-367' for glob 'nvidia*'
Note, selecting 'nvidia-375' for glob 'nvidia*'
Note, selecting 'nvidia-378' for glob 'nvidia*'
Note, selecting 'nvidia-381' for glob 'nvidia*'
Note, selecting 'nvidia-384' for glob 'nvidia*'
Note, selecting 'nvidia-387' for glob 'nvidia*'
Note, selecting 'nvidia-dkms-kernel' for glob 'nvidia*'
Note, selecting 'nvidia-390' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-source-410' for glob 'nvidia*'
Note, selecting 'nvidia-346-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-settings' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd' for glob 'nvidia*'
Note, selecting 'nvidia-settings' instead of 'nvidia-settings-binary'
Package 'nvidia-libopencl1-dev' is not installed, so not removed
Package 'nvidia-libopencl1' is not installed, so not removed
Package 'nvidia-vdpau-driver' is not installed, so not removed
Package 'nvidia-legacy-340xx-vdpau-driver' is not installed, so not removed
Package 'nvidia-legacy-304xx-vdpau-driver' is not installed, so not removed
Package 'nvidia-driver' is not installed, so not removed
Package 'nvidia-legacy-340xx-driver' is not installed, so not removed
Package 'nvidia-legacy-304xx-driver' is not installed, so not removed
Package 'nvidia-kernel-dkms' is not installed, so not removed
Package 'nvidia-legacy-340xx-kernel-dkms' is not installed, so not removed
Package 'nvidia-legacy-304xx-kernel-dkms' is not installed, so not removed
Package 'nvidia' is not installed, so not removed
Package 'nvidia-current-updates' is not installed, so not removed
Package 'nvidia-experimental-304' is not installed, so not removed
Package 'nvidia-310' is not installed, so not removed
Package 'nvidia-310-updates' is not installed, so not removed
Package 'nvidia-experimental-310' is not installed, so not removed
Package 'nvidia-313' is not installed, so not removed
Package 'nvidia-313-updates' is not installed, so not removed
Package 'nvidia-experimental-313' is not installed, so not removed
Package 'nvidia-319' is not installed, so not removed
Package 'nvidia-319-updates' is not installed, so not removed
Package 'nvidia-experimental-319' is not installed, so not removed
Package 'nvidia-325' is not installed, so not removed
Package 'nvidia-325-updates' is not installed, so not removed
Package 'nvidia-experimental-325' is not installed, so not removed
Package 'nvidia-experimental-331' is not installed, so not removed
Package 'nvidia-334' is not installed, so not removed
Package 'nvidia-334-updates' is not installed, so not removed
Package 'nvidia-experimental-334' is not installed, so not removed
Package 'nvidia-337' is not installed, so not removed
Package 'nvidia-337-updates' is not installed, so not removed
Package 'nvidia-experimental-337' is not installed, so not removed
Package 'nvidia-experimental-340' is not installed, so not removed
Package 'nvidia-343' is not installed, so not removed
Package 'nvidia-343-updates' is not installed, so not removed
Package 'nvidia-experimental-343' is not installed, so not removed
Package 'nvidia-experimental-346' is not installed, so not removed
Package 'nvidia-349' is not installed, so not removed
Package 'nvidia-349-updates' is not installed, so not removed
Package 'nvidia-experimental-349' is not installed, so not removed
Package 'nvidia-experimental-352' is not installed, so not removed
Package 'nvidia-355' is not installed, so not removed
Package 'nvidia-355-updates' is not installed, so not removed
Package 'nvidia-experimental-355' is not installed, so not removed
Package 'nvidia-358' is not installed, so not removed
Package 'nvidia-358-updates' is not installed, so not removed
Package 'nvidia-experimental-358' is not installed, so not removed
Package 'nvidia-experimental-361' is not installed, so not removed
Package 'nvidia-364' is not installed, so not removed
Package 'nvidia-364-updates' is not installed, so not removed
Package 'nvidia-experimental-364' is not installed, so not removed
Package 'nvidia-367-updates' is not installed, so not removed
Package 'nvidia-experimental-367' is not installed, so not removed
Package 'nvidia-375-updates' is not installed, so not removed
Package 'nvidia-experimental-375' is not installed, so not removed
Package 'nvidia-378' is not installed, so not removed
Package 'nvidia-378-updates' is not installed, so not removed
Package 'nvidia-experimental-378' is not installed, so not removed
Package 'nvidia-381' is not installed, so not removed
Package 'nvidia-381-updates' is not installed, so not removed
Package 'nvidia-experimental-381' is not installed, so not removed
Package 'nvidia-384-updates' is not installed, so not removed
Package 'nvidia-experimental-384' is not installed, so not removed
Package 'nvidia-387-updates' is not installed, so not removed
Package 'nvidia-experimental-387' is not installed, so not removed
Note, selecting 'libnvtt-bin' instead of 'nvidia-texture-tools'
Package 'nvidia-driver-libs' is not installed, so not removed
Package 'nvidia-driver-libs-nonglvnd' is not installed, so not removed
Package 'nvidia-driver-libs-i386:i386' is not installed, so not removed
Package 'nvidia-compute-390' is not installed, so not removed
Package 'nvidia-331' is not installed, so not removed
Package 'nvidia-331-dev' is not installed, so not removed
Package 'nvidia-331-updates' is not installed, so not removed
Package 'nvidia-331-updates-dev' is not installed, so not removed
Package 'nvidia-331-updates-uvm' is not installed, so not removed
Package 'nvidia-331-uvm' is not installed, so not removed
Package 'nvidia-340' is not installed, so not removed
Package 'nvidia-340-dev' is not installed, so not removed
Package 'nvidia-340-updates' is not installed, so not removed
Package 'nvidia-340-updates-dev' is not installed, so not removed
Package 'nvidia-340-updates-uvm' is not installed, so not removed
Package 'nvidia-340-uvm' is not installed, so not removed
Package 'nvidia-346' is not installed, so not removed
Package 'nvidia-346-dev' is not installed, so not removed
Package 'nvidia-346-updates' is not installed, so not removed
Package 'nvidia-346-updates-dev' is not installed, so not removed
Package 'nvidia-352' is not installed, so not removed
Package 'nvidia-352-dev' is not installed, so not removed
Package 'nvidia-352-updates' is not installed, so not removed
Package 'nvidia-352-updates-dev' is not installed, so not removed
Package 'nvidia-361' is not installed, so not removed
Package 'nvidia-361-dev' is not installed, so not removed
Package 'nvidia-361-updates' is not installed, so not removed
Package 'nvidia-361-updates-dev' is not installed, so not removed
Package 'nvidia-367' is not installed, so not removed
Package 'nvidia-367-dev' is not installed, so not removed
Package 'nvidia-375' is not installed, so not removed
Package 'nvidia-375-dev' is not installed, so not removed
Package 'nvidia-384' is not installed, so not removed
Package 'nvidia-384-dev' is not installed, so not removed
Package 'nvidia-compute-utils-390' is not installed, so not removed
Package 'nvidia-dkms-390' is not installed, so not removed
Package 'nvidia-driver-390' is not installed, so not removed
Package 'nvidia-headless-390' is not installed, so not removed
Package 'nvidia-headless-no-dkms-390' is not installed, so not removed
Package 'nvidia-kernel-common-390' is not installed, so not removed
Package 'nvidia-kernel-source-390' is not installed, so not removed
Package 'nvidia-opencl-icd-340' is not installed, so not removed
Package 'nvidia-utils-390' is not installed, so not removed
Package 'nvidia-common' is not installed, so not removed
Package 'nvidia-cg-dev' is not installed, so not removed
Package 'nvidia-cg-doc' is not installed, so not removed
Package 'nvidia-cg-toolkit' is not installed, so not removed
Package 'nvidia-cuda-dev' is not installed, so not removed
Package 'nvidia-cuda-doc' is not installed, so not removed
Package 'nvidia-cuda-gdb' is not installed, so not removed
Package 'nvidia-cuda-toolkit' is not installed, so not removed
Package 'nvidia-libopencl1-331' is not installed, so not removed
Package 'nvidia-libopencl1-331-updates' is not installed, so not removed
Package 'nvidia-libopencl1-340' is not installed, so not removed
Package 'nvidia-libopencl1-340-updates' is not installed, so not removed
Package 'nvidia-libopencl1-346' is not installed, so not removed
Package 'nvidia-libopencl1-346-updates' is not installed, so not removed
Package 'nvidia-libopencl1-352' is not installed, so not removed
Package 'nvidia-libopencl1-352-updates' is not installed, so not removed
Package 'nvidia-libopencl1-361' is not installed, so not removed
Package 'nvidia-libopencl1-361-updates' is not installed, so not removed
Package 'nvidia-libopencl1-367' is not installed, so not removed
Package 'nvidia-libopencl1-375' is not installed, so not removed
Package 'nvidia-libopencl1-384' is not installed, so not removed
Package 'nvidia-modprobe' is not installed, so not removed
Package 'nvidia-nsight' is not installed, so not removed
Package 'nvidia-opencl-dev' is not installed, so not removed
Package 'nvidia-opencl-icd-331' is not installed, so not removed
Package 'nvidia-opencl-icd-331-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-340-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-346' is not installed, so not removed
Package 'nvidia-opencl-icd-346-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-352' is not installed, so not removed
Package 'nvidia-opencl-icd-352-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-361' is not installed, so not removed
Package 'nvidia-opencl-icd-361-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-367' is not installed, so not removed
Package 'nvidia-opencl-icd-375' is not installed, so not removed
Package 'nvidia-opencl-icd-384' is not installed, so not removed
Package 'nvidia-openjdk-8-jre' is not installed, so not removed
Package 'nvidia-profiler' is not installed, so not removed
Package 'nvidia-visual-profiler' is not installed, so not removed
Package 'nvidia-current' is not installed, so not removed
Package 'nvidia-current-dev' is not installed, so not removed
Package 'nvidia-304' is not installed, so not removed
Package 'nvidia-304-dev' is not installed, so not removed
Package 'nvidia-304-updates' is not installed, so not removed
Package 'nvidia-304-updates-dev' is not installed, so not removed
Package 'nvidia-libopencl1-304' is not installed, so not removed
Package 'nvidia-opencl-icd-304' is not installed, so not removed
Package 'nvidia-libopencl1-304-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-304-updates' is not installed, so not removed
Package 'nvidia-387-dev' is not installed, so not removed
Package 'nvidia-387' is not installed, so not removed
Package 'nvidia-libopencl1-387' is not installed, so not removed
Package 'nvidia-opencl-icd-387' is not installed, so not removed
Package 'nvidia-390-dev' is not installed, so not removed
Package 'nvidia-390' is not installed, so not removed
Package 'nvidia-libopencl1-390' is not installed, so not removed
Package 'nvidia-opencl-icd-390' is not installed, so not removed
Package 'nvidia-compute-utils-396' is not installed, so not removed
Package 'nvidia-dkms-396' is not installed, so not removed
Package 'nvidia-driver-396' is not installed, so not removed
Package 'nvidia-kernel-source-396' is not installed, so not removed
Package 'nvidia-utils-396' is not installed, so not removed
Package 'nvidia-kernel-common-396' is not installed, so not removed
Package 'nvidia-headless-396' is not installed, so not removed
Package 'nvidia-headless-no-dkms-396' is not installed, so not removed
Package 'nvidia-headless-410' is not installed, so not removed
Package 'nvidia-headless-no-dkms-410' is not installed, so not removed
The following packages were automatically installed and are no longer required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386
libllvm7:i386 libnvidia-cfg1-410 libnvidia-common-410 libnvidia-compute-410
libnvidia-compute-410:i386 libnvidia-decode-410 libnvidia-decode-410:i386
libnvidia-encode-410 libnvidia-encode-410:i386 libnvidia-fbc1-410
libnvidia-fbc1-410:i386 libnvidia-gl-410 libnvidia-gl-410:i386
libnvidia-ifr1-410 libnvidia-ifr1-410:i386 libpciaccess0:i386
libsensors4:i386 libstdc++6:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 pkg-config
screen-resolution-extra xserver-xorg-video-nvidia-410
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED
nvidia-compute-utils-410* nvidia-dkms-410* nvidia-driver-410*
nvidia-kernel-common-410* nvidia-kernel-source-410* nvidia-prime*
nvidia-settings* nvidia-utils-410*
0 to upgrade, 0 to newly install, 8 to remove and 12 not to upgrade.
After this operation, 34.4 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 150411 files and directories currently installed.)
Removing nvidia-driver-410 (410.73-0ubuntu0~gpu18.10.1) ...
Removing nvidia-compute-utils-410 (410.73-0ubuntu0~gpu18.10.1) ...
Removing nvidia-dkms-410 (410.73-0ubuntu0~gpu18.10.1) ...
Removing all DKMS Modules
Done.
INFO:Disable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
update-initramfs: deferring update (trigger activated)
Removing nvidia-kernel-common-410 (410.73-0ubuntu0~gpu18.10.1) ...
update-initramfs: deferring update (trigger activated)
Removing nvidia-kernel-source-410 (410.73-0ubuntu0~gpu18.10.1) ...
Removing nvidia-prime (0.8.10) ...
Removing nvidia-settings (410.73-0ubuntu0~gpu18.10.1) ...
Removing nvidia-utils-410 (410.73-0ubuntu0~gpu18.10.1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-3ubuntu2) ...
Processing triggers for initramfs-tools (0.131ubuntu15) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=812f602d-f650-47e4-883b-156f873d48a9)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.28-0ubuntu1) ...
Processing triggers for man-db (2.8.4-2) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu2) ...
(Reading database ... 149925 files and directories currently installed.)
Purging configuration files for nvidia-compute-utils-410 (410.73-0ubuntu0~gpu18.10.1) ...
Purging configuration files for nvidia-prime (0.8.10) ...
Purging configuration files for nvidia-dkms-410 (410.73-0ubuntu0~gpu18.10.1) ...
update-initramfs: deferring update (trigger activated)
Purging configuration files for nvidia-settings (410.73-0ubuntu0~gpu18.10.1) ...
Purging configuration files for nvidia-kernel-common-410 (410.73-0ubuntu0~gpu18.10.1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.131ubuntu15) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=812f602d-f650-47e4-883b-156f873d48a9)
I: Set the RESUME variable to override this.
dusf@contraption:~$ sudo rm /usr/share/X11/xorg.conf.d/10-nvidia.conf
dusf@contraption:~$ sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-dri:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
dkms libnvidia-cfg1-410 libnvidia-common-410 libnvidia-compute-410
libnvidia-compute-410:i386 libnvidia-decode-410 libnvidia-decode-410:i386
libnvidia-encode-410 libnvidia-encode-410:i386 libnvidia-fbc1-410
libnvidia-fbc1-410:i386 libnvidia-gl-410 libnvidia-gl-410:i386
libnvidia-ifr1-410 libnvidia-ifr1-410:i386 libxnvctrl0 pkg-config
screen-resolution-extra xserver-xorg-video-nvidia-410
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed
libgl1-mesa-glx libgl1-mesa-glx:i386
0 to upgrade, 2 to newly install, 4 reinstalled, 0 to remove and 12 not to upgrade.
Need to get 7,280 kB/15.6 MB of archives.
After this operation, 135 kB of additional disk space will be used.
Get:1 http://ie.archive.ubuntu.com/ubuntu cosmic/main amd64 libgl1-mesa-dri amd64 18.2.2-0ubuntu1 [6,553 kB]
Get:2 http://ie.archive.ubuntu.com/ubuntu cosmic/main amd64 libgl1-mesa-glx amd64 18.2.2-0ubuntu1 [3,776 B]
Get:3 http://ie.archive.ubuntu.com/ubuntu cosmic/main i386 libgl1-mesa-glx i386 18.2.2-0ubuntu1 [3,776 B]
Get:4 http://ie.archive.ubuntu.com/ubuntu cosmic/main amd64 xserver-xorg-video-intel amd64 2:2.99.917+git20171229-1ubuntu1 [720 kB]
Fetched 7,280 kB in 1s (5,442 kB/s)
(Reading database ... 149925 files and directories currently installed.)
Preparing to unpack .../0-xserver-xorg-core_2%3a1.20.1-3ubuntu2.1_amd64.deb ...
Unpacking xserver-xorg-core (2:1.20.1-3ubuntu2.1) over (2:1.20.1-3ubuntu2.1) ...
Preparing to unpack .../1-libgl1-mesa-dri_18.2.2-0ubuntu1_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (18.2.2-0ubuntu1) over (18.2.2-0ubuntu1) ...
Preparing to unpack .../2-libgl1-mesa-dri_18.2.2-0ubuntu1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (18.2.2-0ubuntu1) over (18.2.2-0ubuntu1) ...
Selecting previously unselected package libgl1-mesa-glx:amd64.
Preparing to unpack .../3-libgl1-mesa-glx_18.2.2-0ubuntu1_amd64.deb ...
Unpacking libgl1-mesa-glx:amd64 (18.2.2-0ubuntu1) ...
Selecting previously unselected package libgl1-mesa-glx:i386.
Preparing to unpack .../4-libgl1-mesa-glx_18.2.2-0ubuntu1_i386.deb ...
Unpacking libgl1-mesa-glx:i386 (18.2.2-0ubuntu1) ...
Preparing to unpack .../5-xserver-xorg-video-intel_2%3a2.99.917+git20171229-1ubuntu1_amd64.deb ...
Unpacking xserver-xorg-video-intel (2:2.99.917+git20171229-1ubuntu1) over (2:2.99.917+git20171229-1ubuntu1) ...
Setting up libgl1-mesa-dri:amd64 (18.2.2-0ubuntu1) ...
Setting up libgl1-mesa-dri:i386 (18.2.2-0ubuntu1) ...
Setting up xserver-xorg-core (2:1.20.1-3ubuntu2.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...
Setting up libgl1-mesa-glx:amd64 (18.2.2-0ubuntu1) ...
Setting up libgl1-mesa-glx:i386 (18.2.2-0ubuntu1) ...
Processing triggers for man-db (2.8.4-2) ...
Setting up xserver-xorg-video-intel (2:2.99.917+git20171229-1ubuntu1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...
dusf@contraption:~$ sudo dpkg-reconfigure xserver-xorg


On reboot, without modifying the grub options, this time it hangs on a purple screen with some distortion, instead of just a purple screen:

281523

I was unable to access a TTY from this screen, so I REISUBed. Next I modified grub as I have been, replacing quiet splash with nomodeset. This then displayed the normal purple screen I have been seeing, and then hung on a blinking cursor top left. I was then able to access a TTY, and I displayed the log file:

281524

I then sudo apt install nvidia-driver-390, just so I could nomodeset and login to my desktop again. Perhaps you want me to repeat all of the commands again, but try something else instead of reinstalling the driver?
Bashing-om
November 4th, 2018, 02:15 AM
dusf; Yuk . Just Yuk

Totally UN-expected result.

Let's see what :


0 to upgrade, 0 to newly install, 8 to remove and 12 not to upgrade.

those 12 are about.

what results:


sudo apt update
sudo apt full-upgrade

What is of present concern is the notice " Unsupported Discreet card vendor: 8086" .
After the full upgrade, we try and see the boot messages and or look at the boot log. A bit ago I too installed an Nvidia card that had no open source support at that time . Took me a bit to tumble to look at the boot messages -> The boot messages told me so :)

But again, as the system was functional under 16.04, I can not see this as unsupported hardware at this stage. But we got to get some hints from somewhere.



seek and ye shall find
Dáire Fagan
November 4th, 2018, 02:44 PM
dusf; Yuk . Just Yuk

Totally UN-expected result.

Let's see what :

those 12 are about.

what results:


sudo apt update
sudo apt full-upgrade

What is of present concern is the notice " Unsupported Discreet card vendor: 8086" .
After the full upgrade, we try and see the boot messages and or look at the boot log. A bit ago I too installed an Nvidia card that had no open source support at that time . Took me a bit to tumble to look at the boot messages -> The boot messages told me so :)

But again, as the system was functional under 16.04, I can not see this as unsupported hardware at this stage. But we got to get some hints from somewhere.

seek and ye shall find




I think sometimes when I do things with apt I get a popup notice that Ubuntu has experienced an internal error (may or may not be related), as I did on first entering apt update on reading your post. After closing the notification I wanted to try to reproduce this so I could screenshot any info, so I rebooted and tried the update again. It did not happen this time, but please bear in mind the output I am about to paste was after I had already input update and rebooted twice:


dusf@contraption:~$ sudo apt update[sudo] password for dusf:
Hit:1 http://ie.archive.ubuntu.com/ubuntu cosmic InRelease
Hit:2 http://ie.archive.ubuntu.com/ubuntu cosmic-updates InRelease
Hit:3 http://security.ubuntu.com/ubuntu cosmic-security InRelease
Hit:4 http://ie.archive.ubuntu.com/ubuntu cosmic-backports InRelease
Ign:5 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 http://ppa.launchpad.net/deluge-team/ppa/ubuntu cosmic InRelease
Hit:7 http://dl.google.com/linux/chrome/deb stable Release
Hit:8 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic InRelease
Ign:9 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu cosmic InRelease
Hit:10 http://apt.insynchq.com/ubuntu cosmic InRelease
Err:12 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu cosmic Release
404 Not Found [IP: 91.189.95.83 80]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/team-xbmc/ppa/ubuntu cosmic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
dusf@contraption:~$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
libnvidia-common-410
Use 'sudo apt autoremove' to remove it.
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

Should I autoremove?

What do you think about the below, should I do the purge, try reboot into recovery and try the rest of the solution shown? I want to run it by you first as you are mid-troubleshooting:

281536

https://askubuntu.com/questions/450046/black-screen-with-nvidia-drivers-on-ubuntu

There may also be something to the guide below, it mentions reinstalling the system while the graphics card is disconnected from the mobo, but perhaps we could try it by purging nvidia instead before powering off and disconnecting the graphics card from the mobo? Again, I'm not doing any of this yet as you are midtroubleshooting, I just want to flag it with you in case it helps.

https://askubuntu.com/questions/792012/nvidia-geforce-gtx970-problem-ubuntu-16-04

As before, if you let me know the commands to try, I will input them.

Tried the guides I linked, no change.

Not sure if this means anything, but if I select Ubuntu Advanced Options from Grub, then the recovery option, and then resume normal boot, it boots fine. Screen flickers for a second, just like when I edit the main Ubuntu entry in Grub to include nomodeset.
Bashing-om
November 4th, 2018, 11:43 PM
dusf; Yes -

For sure check in Bios as to what is set for the primary display unit.

as to : " http://ppa.launchpad.net/team-xbmc/ppa/ubuntu " - disable this PPA as it is not supported in cosmic ->
http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/dists/

Then when you re-boot let's have a look at what X thinks:


cat /var/log/Xorg.0.log


You already have our Graphic's PPA enabled - hence the 4.10 driver availability .

Also, I do not have the resolution to adequately see your provided image files.

I remain convinced this is a driver issue .. just do not have a ready answer .



we be look'n
Dáire Fagan
November 5th, 2018, 12:02 AM
dusf; Yes -

For sure check in Bios as to what is set for the primary display unit.

It was set to PCI-1, so I changed it to IGFX as I read about that somewhere, but this made no difference. Should I leave as is, or revert back to PCI-1?


as to : " http://ppa.launchpad.net/team-xbmc/ppa/ubuntu " - disable this PPA as it is not supported in cosmic ->
http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/dists/

Just disabled that and the boot-repair PPA for same reason.


Then when you re-boot let's have a look at what X thinks:


cat /var/log/Xorg.0.log


I am guessing you mean reboot after the autoremove, which I did earlier, several reboots ago, so just inputting the cat now:

https://paste.ubuntu.com/p/ZK4DQYTjJd/



Also, I do not have the resolution to adequately see your provided image files.

The screenshot is just of the website I later edited the post to link to.


I remain convinced this is a driver issue .. just do not have a ready answer .

we be look'n





Happy to try anything you think might have even the slightest chance of helping.
Bashing-om
November 5th, 2018, 12:46 AM
dusf; Hummm - again .

The only thing that stands out is that X has issues finding the drivers for the mouse and keyboard. Maybe because you are booting in the recovery console ? Though I see both Nvidia and Intel chip sets identified .. I see no hint of X picking up on an Intel driver !

Let's try a different tact - try to get away from that 'nomodeset' .
Reboot to the login screen, and here execute key combo ctl+alt+F2 to gain a console interface.

Log in here with username and password - no response when password is entered,. Now what does the log file relate ?
post a new :


cat /var/log/Xorg.0.log

and insure that the " https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa " PPA is still enabled as the 4.10 driver is installed.




still gotta be a cause
23dornot23d
November 5th, 2018, 12:55 AM
Sorry for butting in but I saw this in the log ....... I have read somewhere on dual graphics systems not to use /etc/X11/xorg.conf .......... its for single card systems .....
knew I had read it somewhere - took a while to find it ...... on a arch forum though .........
https://bbs.archlinux.org/viewtopic.php?id=230139

[ 8.896] (==) Using config file: "/etc/X11/xorg.conf"
[ 8.896] (==) Using system config directory "/usr/share/X11/xorg.conf.d"


sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf-old

reboot and tell us what happens ........ you can always move it back in again ......
because its a 2 card system I think I read somewhere you do not need the /etc/X11/xorg.conf ...... on my system I
move it to old and it boots ok into the correct graphics with it being a dual system.


================================================== =======
if it does not work .........

to put it back do ( but I have a feeling you will find it works ok without this ..........

sudo mv /etc/X11/xorg.conf-old /etc/X11/xorg.conf
Bashing-om
November 5th, 2018, 01:12 AM
23dornot23d -

Good thought .. will surely not hurt to check for /etc/X11/Xorg.conf, however
I did think that " /usr/share/X11/xorg.conf.d/*.conf " is now the default ??
But, on an upgrade, who knows what may have happened .



inquiring minds want to know
23dornot23d
November 5th, 2018, 01:17 AM
i have found if one is there it would use it ........... it used to override the others - whether it is still doing that is another question - but it does not hurt to try

Now is the time to do it .......... then move on if it does nothing .............

I have nothing in there for xorg.conf and mine is working now.

base@base-K53SV:/etc/X11$ ls
app-defaults openbox Xreset.d xsm
cursors rgb.txt Xresources XvMCConfig
default-display-manager xinit Xsession Xwrapper.config
default-display-manager.dpkg-tmp xkb Xsession.d
fonts Xreset Xsession.options


Hope it helps ......... I have had to remove it in the past ........ otherwise I got a black screen at boot up ........

You could also have a look at /etc/X11/xorg.conf to see whats been put in it ........... !!!

The other thing is - if it did make a difference moving it - it proves it was using it and that then is the first port of call
which then would make it interesting to see what is actually in it ...... the log says it was [ 8.896] (==) Using config file: "/etc/X11/xorg.conf"
Dáire Fagan
November 5th, 2018, 11:34 PM
dusf; Hummm - again .


The only thing that stands out is that X has issues finding the drivers for the mouse and keyboard. Maybe because you are booting in the recovery console ? Though I see both Nvidia and Intel chip sets identified .. I see no hint of X picking up on an Intel driver !


I think I was actually logged in the way I have been during most of troubleshooting, editing Ubuntu entry in grub, replacing quiet splash with nomodeset. Out of curiosity, can you explain why the Intel driver is so important when we are trying to utilise the GTX 970?



Let's try a different tact - try to get away from that 'nomodeset' .
Reboot to the login screen, and here execute key combo ctl+alt+F2 to gain a console interface.



Log in here with username and password - no response when password is entered,. Now what does the log file relate ?
post a new :


cat /var/log/Xorg.0.log

and insure that the " https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa " PPA is still enabled as the 4.10 driver is installed.

still gotta be a cause





Okay, so I can only see a login screen if I use nomodeset, or alternatively if I boot to recovery, and select resume normal boot - perhaps this auto inserts nomodeset? When I boot normally, and the system freezes on purple screen, I cannot access a TTY using ctrl-alt-f2, and in fact ctrl-print screen-R-E-I-S-U-B does not work. Alternatively, I can boot into recovery, load networking, and drop to a root shell? Of the three options I have mentioned to get to a TTY, should I use one of those and then follow your instructions?

By the way, should I leave my BIOS set to use IGFX for POST, or switch it back to PCI-1?




sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf-old



So I did this, and although my system still freezes on the purple screen on boot (I am guessing you did not expect this to fix everything), I can still login as normal using nomodeset. Please feel free to butt in any time you think you can help, in fact I encourage and appreciate it :D




because its a 2 card system


When I read you guys mention it is a 2 card system, I worry you guys are thinking I am using SLI or Crossfire. Just to be clear, I have a single GTX 970, and whatever graphics is on the i5-4690K. Is it not pretty standard these days on desktops to have a discrete graphics card and then onboard graphics on the CPU?



You could also have a look at /etc/X11/xorg.conf to see whats been put in it ........... !!!

The other thing is - if it did make a difference moving it - it proves it was using it and that then is the first port of call
which then would make it interesting to see what is actually in it ...... the log says it was [ 8.896] (==) Using config file: "/etc/X11/xorg.conf"


dusf@contraption:~$ cat /etc/X11/xorg.conf-old# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 410.73


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection


Section "Files"
EndSection


Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection


Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection


Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection


Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection


Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
23dornot23d
November 6th, 2018, 12:23 AM
Just to be sure of what graphics card it is ....

Please do the following 2 commands ...... I will only do a little before Bashing Om arrives - then he can take over ....... we are just getting a bit more information

sudo apt install inxi

inxi -F

Then if you would please post back the full results as you have done before ......... cheers .......... ;)
Dáire Fagan
November 6th, 2018, 12:31 AM
Just to be sure of what graphics card it is ....

Please do the following 2 commands ...... I will only do a little before Bashing Om arrives - then he can take over ....... we are just getting a bit more information

sudo apt install inxi

inxi -F

Then if you would please post back the results as you have done before ......... cheers .......... ;)


dusf@contraption:~$ inxi -FSystem:
Host: contraption Kernel: 4.18.0-10-generic x86_64 bits: 64
Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
Type: Desktop Mobo: Gigabyte model: Z97MX-Gaming 5 v: x.x
serial: <root required> UEFI: American Megatrends v: F4 date: 05/30/2014
CPU:
Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP
L2 cache: 6144 KiB
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 800
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel
Device-2: Intel 9 Series Family HD Audio driver: snd_hda_intel
Device-3: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
Device-4: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.18.0-10-generic
Network:
Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 74:d4:35:ee:f3:98
Device-2: Microsoft Xbox 360 Wireless Adapter type: USB driver: xpad
Drives:
Local Storage: total: 3.25 TiB used: 2.35 TiB (72.3%)
ID-1: /dev/sda vendor: Western Digital model: WD10JPVX-22JC3T0
size: 931.51 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3320620AS size: 298.09 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EARX-00PASB0
size: 1.82 TiB
ID-4: /dev/sdd vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
Partition:
ID-1: / size: 19.10 GiB used: 7.49 GiB (39.2%) fs: ext4 dev: /dev/sdd6
ID-2: /home size: 110.09 GiB used: 2.11 GiB (1.9%) fs: ext4 dev: /dev/sdd5
ID-3: swap-1 size: 30.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 41 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 298 Uptime: 37m Memory: 7.65 GiB used: 3.44 GiB (44.9%)
Shell: bash inxi: 3.0.24
23dornot23d
November 6th, 2018, 12:46 AM
one more command ........ just lets us know a little about what resolutions are available.

xrandr

and post back please ........ just a bit of recon till Bashing Om arrives.

Not sure why the intel is not available ... N/A



Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73
Dáire Fagan
November 6th, 2018, 01:01 AM
one more command ........ just lets us know a little about what resolutions are available.

xrandr

and post back please ........ just a bit of recon till Bashing Om arrives.

Not sure why the intel is not available ... N/A



Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73


dusf@contraption:~$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 144.00 120.00 99.95 84.98 23.97
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
23dornot23d
November 6th, 2018, 01:26 AM
Just read this again ...........

By the way, should I leave my BIOS set to use IGFX for POST, or switch it back to PCI-1?

Can you switch it back again ......switch it back to PCI-1

"Igfx" refers to the Intel Graphics Media Accelerator, an onboard graphics chip - seems odd its not using it N/A when you have it set in the BIOS

Then do

inxi -F

and post the results for the graphics again ......... will it switch the Intel back on ...........

( is there also a AUTO in the BIOS ? ) ........ seem to have read that on other posts ........

Feel free to come in on this Bashing Om ........ the only other thing I can think of adding for more data and what is being set from BIOS is
Nvidia-Settings .......... and if the Intel is working now ........ to install Bumblebee ....... what do you think .... as we still do not seem to
know quite why its stopping at the Purple screen ......

Although I have turned off the splash in /etc/default/grub on my own system to see exactly what is happening at boot up ....... by removing - quiet and splash
from the line in bold .......... if you are confident in editing the file ....... if not we can keep looking at the logs.

It just saves having to keep going to the logs - if you can see something is happening at boot up - < ESC > key should work but I noticed it does not always
Systemd can hang for numerous reasons and it seems as if its never going to boot - but if you can see it is waiting for something - that could be the
reason for the purple screen - but the escape key should let you see what is happening .......... or remove the splash as below .....




# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Bashing-om
November 6th, 2018, 02:17 AM
23dornot23d; dusf = :)

I am watching and the situation is unchanged in that there is no driver for the Intel chip set loaded/ The question is, why not ?

We have re-installed the driver to no effect and I presently do not know what to do.
The signal flow from the Nvidia chip set is through the Intel chips, thus the Intel GPU has to be active .

My knowledge of Intel is sorely lacking, and presently I just do not know how to load the Intel module.



still think'n
23dornot23d
November 6th, 2018, 02:48 AM
The BIOS settings are something I cannot see - so not sure what options are available .......... but the Intel card is showing N/a not accessible for some reason.

I have read that bumblebee and prime will use the two cards and allow performance mode - which is shown in - Nvidia Settings - once everything is set up - but is there something

else stopping us getting to the login screen ....... I know in the past I was having to do CTRL-C to break out of some of the things Systemd was doing before ........

Then I could login and startx

https://47e044bd-a-62cb3a1a-s-sites.googlegroups.com/site/000menu/wayland/problems-ubuntu-build/Screenshot%20at%202018-10-30%2020-01-05.png?attachauth=ANoY7cqOCXT71keT7octTKsDXZnBVCU5 W9API1IbQN1hccoRnCqffvoLsRKlwta8pqFcbuGIf5HdWdyNAn m7lGMMC0OLKqsSGJPy5krz5VvAZJg5d4Ph05mPXRth_Fr2J0qM FwaP-INW_nn5y1G_nWwfYC0pqhCNoNKca7JPGaZkwFtZLJ1OUl1YSB5 r2PNuuqlYKoRjl89AOeVV6IHJWiEcs3J59j0KtlgO0arsCeD33 JeNRZv7CwEpEkegnfKl9QVbEuVsUG0HS2o2q43iIej8BZqqAX8 Haw%3D%3D&attredirects=0


And

inxi -F

shows this on my own setup - which is similar in that it too is intel and nvidia (hybrid graphics)



Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915
v: kernel
Device-2: NVIDIA GF108M [GeForce GT 540M] driver: nvidia v: 390.87
Display: x11 server: X.Org 1.20.1 driver: modesetting,nvidia
unloaded: fbdev,nouveau,vesa resolution: 1366x768~60Hz
OpenGL: renderer: GeForce GT 540M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87


Not so far away from what dusf is getting - other than the intel is Not Available or Accessible ......... for comparison ......


Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73

https://certification.ubuntu.com/catalog/component/pci/8086%3A0416/


I know this is for another operating system - but reading about the BIOS in it is interesting ..... my own is the first of the bios types
but dusf has the second type - from what has been explained already ..... earlier on in the post.
https://antergos.com/wiki/hardware/bumblebee-for-nvidia-optimus/


Found a video showing the bios setup ...... is this the same as you have dusf ?
https://youtu.be/KDITvvtWAAY

If so can the intel be enabled ..... to see if it then picks up ok ........
Dáire Fagan
November 6th, 2018, 12:01 PM
Just read this again ...........

By the way, should I leave my BIOS set to use IGFX for POST, or switch it back to PCI-1?

Can you switch it back again ......switch it back to PCI-1

( is there also a AUTO in the BIOS ? ) ........ seem to have read that on other posts ........



IGFX now reselected (no auto option available, unless that is the XHCI option?), and I am also attaching some pictures of the BIOS in case there is anything else there that will help. I can see from my old posts, that making changes to the BIOS resolved boot issues in the past, I think CSM and secure/fast boot, but I did not change anything before my 18.10 clean install.

281561281562


and post the results for the graphics again ......... will it switch the Intel back on ...........
inxi -F

It appears to have turned it back on:


dusf@contraption:~$ inxi -FSystem:
Host: contraption Kernel: 4.18.0-10-generic x86_64 bits: 64
Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
Type: Desktop Mobo: Gigabyte model: Z97MX-Gaming 5 v: x.x
serial: <root required> UEFI: American Megatrends v: F4 date: 05/30/2014
CPU:
Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP
L2 cache: 6144 KiB
Speed: 927 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 876 2: 848
3: 855 4: 840
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel
Device-2: Intel 9 Series Family HD Audio driver: snd_hda_intel
Device-3: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
Device-4: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.18.0-10-generic
Network:
Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 74:d4:35:ee:f3:98
Device-2: Microsoft Xbox 360 Wireless Adapter type: USB driver: xpad
Drives:
Local Storage: total: 3.25 TiB used: 1.81 TiB (55.7%)
ID-1: /dev/sda vendor: Western Digital model: WD10JPVX-22JC3T0
size: 931.51 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3320620AS size: 298.09 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EARX-00PASB0
size: 1.82 TiB
ID-4: /dev/sdd vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
Partition:
ID-1: / size: 19.10 GiB used: 7.50 GiB (39.2%) fs: ext4 dev: /dev/sdd6
ID-2: /home size: 110.09 GiB used: 2.16 GiB (2.0%) fs: ext4 dev: /dev/sdd5
ID-3: swap-1 size: 30.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 284 Uptime: 7m Memory: 7.65 GiB used: 2.47 GiB (32.3%)
Shell: bash inxi: 3.0.24
dusf@contraption:~$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 144.00 120.00 99.95 84.98 23.97
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)





The BIOS settings are something I cannot see - so not sure what options are available .......... but the Intel card is showing N/a not accessible for some reason.

Will I take pictures of every page of the BIOS, and every popup menu? There may be something there obvious to you but not me...


I have read that bumblebee and prime will use the two cards and allow performance mode - which is shown in - Nvidia Settings - once everything is set up - but is there something

else stopping us getting to the login screen ....... I know in the past I was having to do CTRL-C to break out of some of the things Systemd was doing before ........

Then I could login and startx

I like the idea of making changes so that the logs will be on screen in real time during boot, so that we may see where the system is freezing. I am removing quiet splash and replacing it with nomodeset when I boot at the moment, should that not be displaying the logs, or do I need to do something else? I am going to try pressing escape a few times, starting from just after I press F10 to boot from the grub edit, and then on another separate reboot ctrl-c when it freezes.
https://47e044bd-a-62cb3a1a-s-sites.googlegroups.com/site/000menu/wayland/problems-ubuntu-build/Screenshot%20at%202018-10-30%2020-01-05.png?attachauth=ANoY7cqOCXT71keT7octTKsDXZnBVCU5 W9API1IbQN1hccoRnCqffvoLsRKlwta8pqFcbuGIf5HdWdyNAn m7lGMMC0OLKqsSGJPy5krz5VvAZJg5d4Ph05mPXRth_Fr2J0qM FwaP-INW_nn5y1G_nWwfYC0pqhCNoNKca7JPGaZkwFtZLJ1OUl1YSB5 r2PNuuqlYKoRjl89AOeVV6IHJWiEcs3J59j0KtlgO0arsCeD33 JeNRZv7CwEpEkegnfKl9QVbEuVsUG0HS2o2q43iIej8BZqqAX8 Haw%3D%3D&attredirects=0


Found a video showing the bios setup ...... is this the same as you have dusf ?
https://youtu.be/KDITvvtWAAY

That seems to be it, though I usually just press F2 and go straight to classic mode.


If so can the intel be enabled ..... to see if it then picks up ok ........

I think that is what I have done by selecting IGFX, as per the screenshots, unless you think there is another option somewhere?

Okay, so I tried booting a few times, removing quiet splash but NOT inserting no modeset. The first time pressing nothing, the second time pressing escape many times, the third time pressing ctrl-c. There was no change, the purple screen appears immediately when I press F10 after editing grub.

Bashing-om, you left some instructions for me to input to a TTY a few posts ago, but you also mentioned something like getting rid of nomodeset so I was confused as I am unsure if I can access a TTY without it, apart from perhaps recovery. Are those instructions still worth trying, and if so can you please clarify exactly how you want me to access the TTY? Please refer to reply to your post.
23dornot23d
November 6th, 2018, 12:52 PM
In this shot On the BIOS image you posted (IMG_20181106_102714244.jpg) what does it say next to intel processor graphics - its hidden behind the window for setting PCI .........
which I believe wants to be back to IGFX as the PCI 1 has made no difference
to the inxi - F results ..........



Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73


On the BIOS image you posted (IMG_20181106_102714244.jpg)


;) the Intel Processor Graphics - should be enabled ...... if its not - please enable it

Also with the IGFX set .....



We have to get rid of the N/A on the intel card as far as I can tell .......... then when that is done or when Bashing Om comes
back on and says its ok to do so .......... do the following .....




apt install bumblebee bumblebee-nvidia

apt install bbswitch-dkms

See what we get back from the inxi -F command after doing the above.

also do the command after doing the above ,,,,

optirun glxgears

see if it gives us any output back .............


----------------------------


Okay, so I tried booting a few times, removing quiet splash but NOT inserting no modeset. The first time pressing nothing, the second time pressing escape many times, the third time pressing ctrl-c. There was no change, the purple screen appears immediately when I press F10 after editing grub.


dont forget to update grub - for the changes to take effect too as it says at the top of the /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

Have just read the last post and if the purple screen is not being removed with the escape key - then it does not appear to be running a driver
mmm ........ will Bashing Om make anything of this ....... later on as I do not think he comes on till later.

Adding Bumblebee should not make the situation worse ........ and may give more options ......



This should not upset the flow of things .......... hopefully ( but if you have any concerns - wait and check with what Bashing Om would like to do next. )

As I know what its like if two people try to help - it can get confusing ..........
================================================== =======
This is a video of mine working with just nouveau and no nvidia loaded in https://youtu.be/iicx1Ocr7rE
intel Sandybridge driver.

.......... inxi - F for this setup is ...........


Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
Device-2: NVIDIA GF108M [GeForce GT 540M] driver: nouveau v: kernel
Display: server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.2
Dáire Fagan
November 6th, 2018, 07:17 PM
In this shot On the BIOS image you posted (IMG_20181106_102714244.jpg) what does it say next to intel processor graphics - its hidden behind the window for setting PCI .........
which I believe wants to be back to IGFX as the PCI 1 has made no difference

Please see the BIOS option in the screenshot below. Also, are you sure it should be on IGFX? It was on PCI-1 originally, when everything was working with 16.04, and before I clean installed 18.10, I only changed it to IGFX briefly to see if it would help while we have been troubleshooting here. Now set back to IGFX...

281568


I will complete the commands you linked starting with apt install bumblebee bumblebee-nvidia when one of you confirm I should.


dont forget to update grub - for the changes to take effect too as it says at the top of the /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

I have not been editing that file. When I say I have been replacing quiet splash with nomodeset, or just removing quiet splash and not replacing it with anything - I am doing this from the grub boot menu, pressing E when the Ubuntu entry is selected. Let me know if you want me to do anything with the actual grub file.
23dornot23d
November 6th, 2018, 08:09 PM
Ok can you just post the

inxi -F again ........ to see if Intel is available now ...........




I have not been editing that file. When I say I have been replacing quiet splash with nomodeset, or just removing quiet splash and not replacing it with anything - I am doing this from the grub boot menu, pressing E when the Ubuntu entry is selected. Let me know if you want me to do anything with the actual grub file.



No problem with altering the grub file just yet then - till you have proper graphics to work with ......



I will wait to see what Bashing Om wants to do - he may have thought of something else - and before
we go anywhere else and mess up his train of thought or do something he may not require ....... its better just to hang on a while.

His last remark was



We have re-installed the driver to no effect and I presently do not know what to do.
The signal flow from the Nvidia chip set is through the Intel chips, thus the Intel GPU has to be active .

My knowledge of Intel is sorely lacking, and presently I just do not know how to load the Intel module.

still think'n





We still need to see that the Intel card has become available - before we can move on too ......

as shown in the graphic which was posted earlier on - which shows the line of information on muxless going through
the intel integrated card ......

https://camo.githubusercontent.com/a1cdea34451339f0537fe0e5226f2f52e4cf93fd/68747470733a2f2f692e696d6775722e636f6d2f4749377638 476b2e6a7067

which is why we were changing the BIOS ......... as it seems the place to enable it ........


I would like to see the N/A replaced with available or something to indicate we can use it ....... one more question while
you are on - what monitor is it that you are using - its ok found it in the logs ..... https://www.acer.com/ac/en/EE/content/model/UM.HB0EE.009

[ 9.749] (--) NVIDIA(GPU-0): Acer XB270HU (DFP-2): connected

and what resolutions were you using when you had it working before ?



I just loaded up my own 18.04 version to get some information from that ...... and did a quick video
video showing the nvidia card being used - back in 18.04 ........ 32 bit though as opposed to the 18.10 - 64bit I use now.

https://youtu.be/ZIJ5Xj2yTXc

Ok can you just post the

inxi -F again ........ to see if Intel is available now ...........

Sorry for the double post - was editing the above post - and hit *post quick reply* instead of save - and could not delete this .....



Please see the BIOS option in the screenshot below. Also, are you sure it should be on IGFX? It was on PCI-1 originally, when everything was working with 16.04, and before I clean installed 18.10, I only changed it to IGFX briefly to see if it would help while we have been troubleshooting here. Now set back to IGFX...


To answer your question - I am not totally sure - I have read either work ........ but whichever gets the intel card to move away from
N/A in the inxi listing would suit us.

If you are confident it was the way you said and works ........
then use the way that worked previously its all we have so far is that it worked ok before in 16.04 ......... PCI-1 .......

Has the N/A changed to anything other yet ?

Another question ( do you still have the 16.04 version saved as a backup on a drive ...... ) i.e. can you get to see that it still works in
16.04 .......... because running inxi -F in that system may give us the information we need.
heynnema
November 6th, 2018, 10:39 PM
I haven't read every word on the last 6 pages of dialog... but this is probably your fix...

You may have a problem with an older computer, with an older GPU. Try this...

- boot to recovery mode
- choose root access

type:

sudo mount -o remount,rw / # to remount the disk r/w

sudo pico /etc/gdm3/custom.conf # edit this file

change:

#WaylandEnable=false

to:

WaylandEnable=false

Then reboot.
Dáire Fagan
November 6th, 2018, 10:42 PM
Ok can you just post the

inxi -F again ........ to see if Intel is available now ...........

See how it is showing as device 1, is that not good? Or are we looking for inxi -F to display something else? I am guessing the N/A you mentioned we do not want to see is on the line underneath where it says driver.


dusf@contraption:~$ inxi -FSystem:
Host: contraption Kernel: 4.18.0-10-generic x86_64 bits: 64
Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
Type: Desktop Mobo: Gigabyte model: Z97MX-Gaming 5 v: x.x
serial: <root required> UEFI: American Megatrends v: F4 date: 05/30/2014
CPU:
Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP
L2 cache: 6144 KiB
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 802 2: 807
3: 800 4: 1019
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel
Device-2: Intel 9 Series Family HD Audio driver: snd_hda_intel
Device-3: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
Device-4: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.18.0-10-generic
Network:
Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 74:d4:35:ee:f3:98
Device-2: Microsoft Xbox 360 Wireless Adapter type: USB driver: xpad
Drives:
Local Storage: total: 3.25 TiB used: 1.81 TiB (55.6%)
ID-1: /dev/sda vendor: Western Digital model: WD10JPVX-22JC3T0
size: 931.51 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3320620AS size: 298.09 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EARX-00PASB0
size: 1.82 TiB
ID-4: /dev/sdd vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
Partition:
ID-1: / size: 19.10 GiB used: 7.58 GiB (39.7%) fs: ext4 dev: /dev/sdd6
ID-2: /home size: 110.09 GiB used: 2.14 GiB (1.9%) fs: ext4 dev: /dev/sdd5
ID-3: swap-1 size: 30.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 47 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 280 Uptime: 2h 58m Memory: 7.65 GiB used: 3.10 GiB (40.4%)
Shell: bash inxi: 3.0.24
dusf@contraption:~$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 144.00 120.00 99.95 84.98 23.97
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)




[ 9.749] (--) NVIDIA(GPU-0): Acer XB270HU (DFP-2): connected

and what resolutions were you using when you had it working before ?

I believe I have always been using native, WQHD, so 2560 x 1440, over display port. Annoyingly this monitor does not also have a HDMI port.



I just loaded up my own 18.04 version to get some information from that ...... and did a quick video
video showing the nvidia card being used - back in 18.04 ........ 32 bit though as opposed to the 18.10 - 64bit I use now.

https://youtu.be/ZIJ5Xj2yTXc

After watching you use glxgears:


dusf@contraption:~$ sudo apt install bumblebee bumblebee-nvidia[sudo] password for daire:
Sorry, try again.
[sudo] password for daire:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
bbswitch-dkms primus primus-libs primus-libs:i386 primus-libs-ia32:i386
socat
Suggested packages:
nvidia-driver-libs-nonglvnd
The following NEW packages will be installed
bbswitch-dkms bumblebee bumblebee-nvidia primus primus-libs primus-libs:i386
primus-libs-ia32:i386 socat
0 to upgrade, 8 to newly install, 0 to remove and 0 not to upgrade.
Need to get 522 kB of archives.
After this operation, 1,871 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 bbswitch-dkms amd64 0.8-5
Could not connect to ie.archive.ubuntu.com:80 (193.1.193.69). - connect (111: Connection refused) Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:2 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 bumblebee amd64 3.2.1-17
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:3 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 bumblebee-nvidia amd64 3.2.1-17
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:4 http://ie.archive.ubuntu.com/ubuntu cosmic/main amd64 socat amd64 1.7.3.2-2ubuntu2
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:5 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 primus-libs amd64 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:6 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 primus amd64 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:7 http://ie.archive.ubuntu.com/ubuntu cosmic/universe i386 primus-libs i386 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:8 http://ie.archive.ubuntu.com/ubuntu cosmic/universe i386 primus-libs-ia32 i386 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/b/bbswitch/bbswitch-dkms_0.8-5_amd64.deb Could not connect to ie.archive.ubuntu.com:80 (193.1.193.69). - connect (111: Connection refused) Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/b/bumblebee/bumblebee_3.2.1-17_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/b/bumblebee/bumblebee-nvidia_3.2.1-17_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/main/s/socat/socat_1.7.3.2-2ubuntu2_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus-libs_0~20150328-6_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus_0~20150328-6_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus-libs_0~20150328-6_i386.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus-libs-ia32_0~20150328-6_i386.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Irish repos may be down...
23dornot23d
November 6th, 2018, 11:00 PM
Ok yes that looks like its not connecting to the network ....... but the file list looks about right ....... very similar to my own.

Yes also ...... its the driver that is not available ...... so maybe it will become available with the new settings when primus and bumblebee are installed etc .....



The following NEW packages will be installed
bbswitch-dkms bumblebee bumblebee-nvidia primus primus-libs primus-libs:i386
primus-libs-ia32:i386 socat


....... mine works and even when it works - it does not always report back to me that it has found the gt540

You maybe saw that in the video ......... yet the card is working - as there is no way on earth I can get the speeds shown on the
glxspheres and glxgears using nouveau ........ maybe I should do a quick video to show the difference in speed as a visual is often
better than just giving frames per second.

Ubuntu 16.04 using the Sandybridge driver ...... https://youtu.be/AY3TmlxR_R8
(https://youtu.be/AY3TmlxR_R8)compare to .......
Ubuntu 18.04 using the Nvidia gt540 card ....... https://youtu.be/ZIJ5Xj2yTXc



See how it is showing as device 1, is that not good? Or are we looking for inxi -F to display something else? I am guessing the N/A you mentioned we do not want to see is on the line underneath where it says driver.



When we get the driver to display - then we should be ok ......... the N/A is either saying its not available or not accessible ...... yep that on my readouts
always has a driver there.

Its built into the kernel ...... so maybe the bbswitch dkms is what triggers it as it builds into the kernel .....

https://www.kernel.org/doc/html/v4.15/gpu/drm-kms.html



Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915
v: kernel






https://ubuntuforums.org/images/avatars/UF_Logo_original_90.png (https://ubuntuforums.org/member.php?u=811693) heynnema (https://ubuntuforums.org/member.php?u=811693)
https://ubuntuforums.org/images/ubuntu-VB4/statusicon/user-offline.png First Cup of Ubuntu https://ubuntuforums.org/images/rank_11.png

I haven't read every word on the last 6 pages of dialog... but this is probably your fix...

You may have a problem with an older computer, with an older GPU. Try this...

- boot to recovery mode
- choose root access

type:

sudo mount -o remount,rw / # to remount the disk r/w

sudo pico /etc/gdm3/custom.conf # edit this file

change:

#WaylandEnable=false

to:

WaylandEnable=false

Then reboot.


Thanks for the information .......


I have just checked my own system out and I did not change this to get mine running - this is as it stands - but if the op wants to try to edit it without
a screen to work from that is the OPs choice ....... what I did do though was to install lightdm.

I suppose the way around it - which includes no editing - is to install lightdm

sudo apt install lightdm.

------------------------------------------------------------------------------

This config file below runs from the gdm3 dm as far as I know ........ so would it stop xorg running completely now when gdm3 is in use.


/etc/gdm3/custom.conf



# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
AutomaticLoginEnable=true
AutomaticLogin=base

# Uncoment the line below to force the login screen to use Xorg
#WaylandEnable=false

# Enabling automatic login

# Enabling timed login
# TimedLoginEnable = true
# TimedLogin = user1
# TimedLoginDelay = 10

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
#Enable=true


-----------------------------------------------------------------------------------

To make things more concise as it has quickly got complicated ...........

-----------------------------------------------------------------------------------
Maybe to clarify in clear steps how I got my own working ...... ( this is to put it as clearly as possible as to how I got my own working)

I first did the install of Ubuntu 18.10
I then added Mate as a desktop ( this is my own preference )
I then changed my own system from gdm3 to lightdm ( which gets around the problem of wayland and xorg )
I then installed bumblebee
-----------------------------------------------------------------------------------

Clarification of the Problem.

So far - we have just being trying to get the intel graphic drivers installed correctly on the OPs system with no real success.
The logs and information given so far only show that the Intel driver is Not Available or Accessible
( yet they worked before with his system in 16,04 )
Could it be another problem - I have looked for other things related to the BIOS ........ but the OP dusf says its not changed much other that he did try IGFX out.

But as said below ...... it could be just not using the xorg

Which I did post in #19 ...... the link shown in this other thread https://ubuntuforums.org/showthread.php?t=2404556

In which case - the easiest solution might be to do

sudo apt install lightdm

as it involves no editing of files from the terminal and just uses xorg


(https://ubuntuforums.org/member.php?u=811693)
Dáire Fagan
November 7th, 2018, 06:50 PM
So I thought I would try bumblebee again before anything else, but I still cannot connect:


dusf@contraption:~$ sudo apt install bumblebee bumblebee-nvidia[sudo] password for dusf:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
bbswitch-dkms primus primus-libs primus-libs:i386 primus-libs-ia32:i386
socat
Suggested packages:
nvidia-driver-libs-nonglvnd
The following NEW packages will be installed
bbswitch-dkms bumblebee bumblebee-nvidia primus primus-libs primus-libs:i386
primus-libs-ia32:i386 socat
0 to upgrade, 8 to newly install, 0 to remove and 0 not to upgrade.
Need to get 522 kB of archives.
After this operation, 1,871 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 bbswitch-dkms amd64 0.8-5
Could not connect to ie.archive.ubuntu.com:80 (193.1.193.69). - connect (111: Connection refused) Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:2 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 bumblebee amd64 3.2.1-17
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:3 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 bumblebee-nvidia amd64 3.2.1-17
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:4 http://ie.archive.ubuntu.com/ubuntu cosmic/main amd64 socat amd64 1.7.3.2-2ubuntu2
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:5 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 primus-libs amd64 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:6 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 primus amd64 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:7 http://ie.archive.ubuntu.com/ubuntu cosmic/universe i386 primus-libs i386 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:8 http://ie.archive.ubuntu.com/ubuntu cosmic/universe i386 primus-libs-ia32 i386 0~20150328-6
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/b/bbswitch/bbswitch-dkms_0.8-5_amd64.deb Could not connect to ie.archive.ubuntu.com:80 (193.1.193.69). - connect (111: Connection refused) Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/b/bumblebee/bumblebee_3.2.1-17_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/b/bumblebee/bumblebee-nvidia_3.2.1-17_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/main/s/socat/socat_1.7.3.2-2ubuntu2_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus-libs_0~20150328-6_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus_0~20150328-6_amd64.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus-libs_0~20150328-6_i386.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Failed to fetch http://ie.archive.ubuntu.com/ubuntu/pool/universe/p/primus/primus-libs-ia32_0~20150328-6_i386.deb Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
dusf@contraption:~$ sudo apt-get update
Err:1 http://ie.archive.ubuntu.com/ubuntu cosmic InRelease
Could not connect to ie.archive.ubuntu.com:80 (193.1.193.69). - connect (111: Connection refused) Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:2 http://ie.archive.ubuntu.com/ubuntu cosmic-updates InRelease
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:3 http://ie.archive.ubuntu.com/ubuntu cosmic-backports InRelease
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Get:4 http://security.ubuntu.com/ubuntu cosmic-security InRelease [83.2 kB]
Hit:5 http://ppa.launchpad.net/deluge-team/ppa/ubuntu cosmic InRelease
Ign:6 http://dl.google.com/linux/chrome/deb stable InRelease
Get:7 http://dl.google.com/linux/chrome/deb stable Release [943 B]
Hit:8 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic InRelease
Get:9 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Hit:10 http://apt.insynchq.com/ubuntu cosmic InRelease
Get:11 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages [33.4 kB]
Get:12 http://security.ubuntu.com/ubuntu cosmic-security/main i386 Packages [33.4 kB]
Get:13 http://security.ubuntu.com/ubuntu cosmic-security/main Translation-en [13.7 kB]
Get:14 http://security.ubuntu.com/ubuntu cosmic-security/universe i386 Packages [22.2 kB]
Get:15 http://security.ubuntu.com/ubuntu cosmic-security/universe amd64 Packages [22.2 kB]
Get:16 http://security.ubuntu.com/ubuntu cosmic-security/universe Translation-en [11.8 kB]
Reading package lists... Done
E: Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
dusf@contraption:~$ sudo apt-get update --fix-missing
Err:1 http://ie.archive.ubuntu.com/ubuntu cosmic InRelease
Could not connect to ie.archive.ubuntu.com:80 (193.1.193.69). - connect (111: Connection refused) Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:2 http://ie.archive.ubuntu.com/ubuntu cosmic-updates InRelease
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Err:3 http://ie.archive.ubuntu.com/ubuntu cosmic-backports InRelease
Cannot initiate the connection to ie.archive.ubuntu.com:80 (2001:770:18:aa40::c101:c145). - connect (101: Network is unreachable)
Hit:4 http://ppa.launchpad.net/deluge-team/ppa/ubuntu cosmic InRelease
Ign:5 http://dl.google.com/linux/chrome/deb stable InRelease
Get:6 http://dl.google.com/linux/chrome/deb stable Release [943 B]
Hit:7 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic InRelease
Get:8 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Hit:9 http://apt.insynchq.com/ubuntu cosmic InRelease
Hit:10 http://security.ubuntu.com/ubuntu cosmic-security InRelease
Reading package lists... Done
E: Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.


Perhaps there is something I need to change?


dusf@contraption:~$ cat /etc/apt/sources.list# deb cdrom:[Ubuntu 18.10 _Cosmic Cuttlefish_ - Release amd64 (20181017.3)]/ cosmic main restricted


# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic main restricted
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic main restricted


## Major bug fix updates produced after the final release of the
## distribution.
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic-updates main restricted
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic-updates main restricted


## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic universe
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic universe
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic-updates universe
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic-updates universe


## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic multiverse
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic multiverse
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic-updates multiverse
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic-updates multiverse


## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://ie.archive.ubuntu.com/ubuntu/ cosmic-backports main restricted universe multiverse
# deb-src http://ie.archive.ubuntu.com/ubuntu/ cosmic-backports main restricted universe multiverse


## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu cosmic partner
# deb-src http://archive.canonical.com/ubuntu cosmic partner


deb http://security.ubuntu.com/ubuntu cosmic-security main restricted
# deb-src http://security.ubuntu.com/ubuntu cosmic-security main restricted
deb http://security.ubuntu.com/ubuntu cosmic-security universe
# deb-src http://security.ubuntu.com/ubuntu cosmic-security universe
deb http://security.ubuntu.com/ubuntu cosmic-security multiverse
# deb-src http://security.ubuntu.com/ubuntu cosmic-security multiverse


# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.


I am not sure why this is happening, I read it could be a proxy but I do not use one, and I am typing this now on the same computer, which does have Internet access. Not sure if it could be related to my using Smart DNS IP addresses for my DNS servers on my DD-WRT configured router?

Changed to UK server and seems to have fixed that issue, trying the bumblebee instructions shortly.

Okay, so tried the following. Please let me know if you want me to undo / uninstall / redo anything:


dusf@contraption:~$ sudo apt install bumblebee bumblebee-nvidia[sudo] password for dusf:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
bbswitch-dkms primus primus-libs primus-libs:i386 primus-libs-ia32:i386
socat
Suggested packages:
nvidia-driver-libs-nonglvnd
The following NEW packages will be installed
bbswitch-dkms bumblebee bumblebee-nvidia primus primus-libs primus-libs:i386
primus-libs-ia32:i386 socat
0 to upgrade, 8 to newly install, 0 to remove and 3 not to upgrade.
Need to get 522 kB of archives.
After this operation, 1,871 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 bbswitch-dkms amd64 0.8-5 [11.6 kB]
Get:2 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 bumblebee amd64 3.2.1-17 [49.0 kB]
Get:3 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 bumblebee-nvidia amd64 3.2.1-17 [2,944 B]
Get:4 http://gb.archive.ubuntu.com/ubuntu cosmic/main amd64 socat amd64 1.7.3.2-2ubuntu2 [342 kB]
Get:5 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 primus-libs amd64 0~20150328-6 [51.4 kB]
Get:6 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 primus amd64 0~20150328-6 [9,856 B]
Get:7 http://gb.archive.ubuntu.com/ubuntu cosmic/universe i386 primus-libs i386 0~20150328-6 [52.8 kB]
Get:8 http://gb.archive.ubuntu.com/ubuntu cosmic/universe i386 primus-libs-ia32 i386 0~20150328-6 [2,272 B]
Fetched 522 kB in 0s (1,325 kB/s)
Selecting previously unselected package bbswitch-dkms.
(Reading database ... 150972 files and directories currently installed.)
Preparing to unpack .../0-bbswitch-dkms_0.8-5_amd64.deb ...
Unpacking bbswitch-dkms (0.8-5) ...
Selecting previously unselected package bumblebee.
Preparing to unpack .../1-bumblebee_3.2.1-17_amd64.deb ...
Unpacking bumblebee (3.2.1-17) ...
Selecting previously unselected package bumblebee-nvidia.
Preparing to unpack .../2-bumblebee-nvidia_3.2.1-17_amd64.deb ...
Unpacking bumblebee-nvidia (3.2.1-17) ...
Selecting previously unselected package socat.
Preparing to unpack .../3-socat_1.7.3.2-2ubuntu2_amd64.deb ...
Unpacking socat (1.7.3.2-2ubuntu2) ...
Selecting previously unselected package primus-libs:amd64.
Preparing to unpack .../4-primus-libs_0~20150328-6_amd64.deb ...
Unpacking primus-libs:amd64 (0~20150328-6) ...
Selecting previously unselected package primus.
Preparing to unpack .../5-primus_0~20150328-6_amd64.deb ...
Unpacking primus (0~20150328-6) ...
Selecting previously unselected package primus-libs:i386.
Preparing to unpack .../6-primus-libs_0~20150328-6_i386.deb ...
Unpacking primus-libs:i386 (0~20150328-6) ...
Selecting previously unselected package primus-libs-ia32:i386.
Preparing to unpack .../7-primus-libs-ia32_0~20150328-6_i386.deb ...
Unpacking primus-libs-ia32:i386 (0~20150328-6) ...
Setting up socat (1.7.3.2-2ubuntu2) ...
Setting up primus-libs:amd64 (0~20150328-6) ...
Setting up primus-libs:i386 (0~20150328-6) ...
Processing triggers for initramfs-tools (0.131ubuntu15) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=812f602d-f650-47e4-883b-156f873d48a9)
I: Set the RESUME variable to override this.
Processing triggers for systemd (239-7ubuntu10.1) ...
Processing triggers for man-db (2.8.4-2) ...
Setting up bbswitch-dkms (0.8-5) ...
Loading new bbswitch-0.8 DKMS files...
Building for 4.18.0-10-generic
Building initial module for 4.18.0-10-generic
Secure Boot not enabled on this system.
Done.


bbswitch:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.18.0-10-generic/updates/dkms/


depmod...


DKMS: install completed.
Setting up primus-libs-ia32:i386 (0~20150328-6) ...
Setting up bumblebee (3.2.1-17) ...
Adding members from group(s) 'adm sudo admin' to 'bumblebee':
dusf syslog
Adding user dusf to group bumblebee
Adding user syslog to group bumblebee
Selecting 01:00:0 as discrete nvidia card. If this is incorrect,
edit the BusID line in /etc/bumblebee/xorg.conf.nouveau .
Created symlink /etc/systemd/system/graphical.target.wants/bumblebeed.service → /lib/systemd/system/bumblebeed.service.
Setting up primus (0~20150328-6) ...
Setting up bumblebee-nvidia (3.2.1-17) ...
Selecting 01:00:0 as discrete nvidia card. If this is incorrect,
edit the BusID line in /etc/bumblebee/xorg.conf.nvidia
Processing triggers for initramfs-tools (0.131ubuntu15) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=812f602d-f650-47e4-883b-156f873d48a9)
I: Set the RESUME variable to override this.
Processing triggers for systemd (239-7ubuntu10.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...
dusf@contraption:~$ sudo apt install bbswitch-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
bbswitch-dkms is already the newest version (0.8-5).
bbswitch-dkms set to manually installed.
0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.


***REBOOT with nomodeset***


dusf@contraption:~$ inxi -F
System:
Host: contraption Kernel: 4.18.0-10-generic x86_64 bits: 64
Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
Type: Desktop Mobo: Gigabyte model: Z97MX-Gaming 5 v: x.x
serial: <root required> UEFI: American Megatrends v: F4 date: 05/30/2014
CPU:
Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP
L2 cache: 6144 KiB
Speed: 3700 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 3700 2: 3700
3: 3700 4: 3700
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: N/A
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel
Device-2: Intel 9 Series Family HD Audio driver: snd_hda_intel
Device-3: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
Device-4: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.18.0-10-generic
Network:
Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 74:d4:35:ee:f3:98
Device-2: Microsoft Xbox 360 Wireless Adapter type: USB driver: xpad
Drives:
Local Storage: total: 3.25 TiB used: 1.81 TiB (55.6%)
ID-1: /dev/sda vendor: Western Digital model: WD10JPVX-22JC3T0
size: 931.51 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3320620AS size: 298.09 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EARX-00PASB0
size: 1.82 TiB
ID-4: /dev/sdd vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
Partition:
ID-1: / size: 19.10 GiB used: 7.68 GiB (40.2%) fs: ext4 dev: /dev/sdd6
ID-2: /home size: 110.09 GiB used: 2.16 GiB (2.0%) fs: ext4 dev: /dev/sdd5
ID-3: swap-1 size: 30.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 44 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 294 Uptime: N/A Memory: 7.65 GiB used: 3.29 GiB (43.0%)
Shell: bash inxi: 3.0.24
dusf@contraption:~$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 144.00 120.00 99.95 84.98 23.97
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
dusf@contraption:~$ optirun glxgears
primus: fatal: failed to load any of the libraries: /usr/lib/nvidia-current/libGL.so.1:/usr/lib32/nvidia-current/libGL.so.1
/usr/lib/nvidia-current/libGL.so.1: cannot open shared object file: No such file or directory
/usr/lib32/nvidia-current/libGL.so.1: cannot open shared object file: No such file or directory






To answer your question - I am not totally sure - I have read either work ........ but whichever gets the intel card to move away from
N/A in the inxi listing would suit us.


If you are confident it was the way you said and works ........
then use the way that worked previously its all we have so far is that it worked ok before in 16.04 ......... PCI-1 .......


...


Another question ( do you still have the 16.04 version saved as a backup on a drive ...... ) i.e. can you get to see that it still works in
16.04 .......... because running inxi -F in that system may give us the information we need.


BIOS now switched back to PCI-1. Unfortunately I have no backup from 16.04.




sudo apt install lightdm


as it involves no editing of files from the terminal and just uses xorg




dusf@contraption:~$ sudo apt install lightdm
[sudo] password for dusf:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
accountsservice-ubuntu-schemas geoclue geoclue-ubuntu-geoip
gnome-screensaver indicator-applet indicator-application indicator-common
indicator-datetime indicator-keyboard indicator-messages indicator-power
indicator-session indicator-sound libaccounts-glib0 libfcitx-config4
libfcitx-gclient1 libfcitx-utils0 libgeoclue0 libido3-0.1-0
liblightdm-gobject-1-0 libnm-glib4 libnm-util2 libpanel-applet3
libunity-settings-daemon1 liburl-dispatcher1 ubuntu-touch-sounds
unity-greeter unity-settings-daemon
Suggested packages:
unity-greeter-session-broadcast fcitx url-dispatcher bindfs
lightdm-remote-session-freerdp lightdm-remote-session-uccsconfigure
remote-login-service
Recommended packages:
systemd-services
The following NEW packages will be installed
accountsservice-ubuntu-schemas geoclue geoclue-ubuntu-geoip
gnome-screensaver indicator-applet indicator-application indicator-common
indicator-datetime indicator-keyboard indicator-messages indicator-power
indicator-session indicator-sound libaccounts-glib0 libfcitx-config4
libfcitx-gclient1 libfcitx-utils0 libgeoclue0 libido3-0.1-0
liblightdm-gobject-1-0 libnm-glib4 libnm-util2 libpanel-applet3
libunity-settings-daemon1 liburl-dispatcher1 lightdm ubuntu-touch-sounds
unity-greeter unity-settings-daemon
0 to upgrade, 29 to newly install, 0 to remove and 3 not to upgrade.
Need to get 15.1 MB of archives.
After this operation, 24.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 lightdm amd64 1.28.0-0ubuntu1 [150 kB]
Get:2 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 accountsservice-ubuntu-schemas all 0.0.7+17.10.20170922-0ubuntu1 [5,086 B]
Get:3 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libgeoclue0 amd64 0.12.99-4ubuntu2 [27.2 kB]
Get:4 http://gb.archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 libnm-util2 amd64 1.12.4-1ubuntu1.1 [118 kB]
Get:5 http://gb.archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 libnm-glib4 amd64 1.12.4-1ubuntu1.1 [80.2 kB]
Get:6 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 geoclue amd64 0.12.99-4ubuntu2 [19.4 kB]
Get:7 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 geoclue-ubuntu-geoip amd64 1.0.2+18.04.20180223-0ubuntu1 [11.6 kB]
Get:8 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 gnome-screensaver amd64 3.6.1-8ubuntu3 [235 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu cosmic/main amd64 libido3-0.1-0 amd64 13.10.0+17.04.20161028-0ubuntu1 [48.4 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libpanel-applet3 amd64 1:3.30.0-1ubuntu2 [18.8 kB]
Get:11 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-applet amd64 12.10.2+17.10.20170425-0ubuntu2 [75.6 kB]
Get:12 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-common all 16.10.0+18.04.20180321.1-0ubuntu1 [3,068 B]
Get:13 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-application amd64 12.10.1+17.04.20161201-0ubuntu1 [24.1 kB]
Get:14 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libaccounts-glib0 amd64 1.23+17.04.20161104-0ubuntu1 [41.0 kB]
Get:15 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 liburl-dispatcher1 amd64 0.1+17.04.20170328-0ubuntu4 [5,940 B]
Get:16 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-datetime amd64 15.10+17.10.20170829.2-0ubuntu4 [275 kB]
Get:17 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libfcitx-utils0 amd64 1:4.2.9.6-4 [34.4 kB]
Get:18 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libfcitx-gclient1 amd64 1:4.2.9.6-4 [20.7 kB]
Get:19 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 liblightdm-gobject-1-0 amd64 1.28.0-0ubuntu1 [39.8 kB]
Get:20 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-keyboard amd64 0.0.0+18.04.20180216-0ubuntu1 [50.3 kB]
Get:21 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-messages amd64 13.10.1+18.10.20180918-0ubuntu1 [68.9 kB]
Get:22 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-power amd64 12.10.6+17.10.20170829.1-0ubuntu4 [121 kB]
Get:23 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-session amd64 17.3.20+17.10.20171006-0ubuntu1 [111 kB]
Get:24 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libfcitx-config4 amd64 1:4.2.9.6-4 [33.9 kB]
Get:25 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 libunity-settings-daemon1 amd64 15.04.1+18.04.20180413-0ubuntu2 [75.8 kB]
Get:26 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 ubuntu-touch-sounds all 15.08 [12.7 MB]
Get:27 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 unity-settings-daemon amd64 15.04.1+18.04.20180413-0ubuntu2 [450 kB]
Get:28 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 unity-greeter amd64 18.04.0+18.10.20180926-0ubuntu1 [153 kB]
Get:29 http://gb.archive.ubuntu.com/ubuntu cosmic/universe amd64 indicator-sound amd64 12.10.2+18.10.20180612-0ubuntu1 [97.0 kB]
Fetched 15.1 MB in 3s (5,221 kB/s)
Preconfiguring packages ...
Selecting previously unselected package lightdm.
(Reading database ... 151073 files and directories currently installed.)
Preparing to unpack .../00-lightdm_1.28.0-0ubuntu1_amd64.deb ...
Unpacking lightdm (1.28.0-0ubuntu1) ...
Selecting previously unselected package accountsservice-ubuntu-schemas.
Preparing to unpack .../01-accountsservice-ubuntu-schemas_0.0.7+17.10.20170922-0ubuntu1_all.deb ...
Unpacking accountsservice-ubuntu-schemas (0.0.7+17.10.20170922-0ubuntu1) ...
Selecting previously unselected package libgeoclue0:amd64.
Preparing to unpack .../02-libgeoclue0_0.12.99-4ubuntu2_amd64.deb ...
Unpacking libgeoclue0:amd64 (0.12.99-4ubuntu2) ...
Selecting previously unselected package libnm-util2:amd64.
Preparing to unpack .../03-libnm-util2_1.12.4-1ubuntu1.1_amd64.deb ...
Unpacking libnm-util2:amd64 (1.12.4-1ubuntu1.1) ...
Selecting previously unselected package libnm-glib4:amd64.
Preparing to unpack .../04-libnm-glib4_1.12.4-1ubuntu1.1_amd64.deb ...
Unpacking libnm-glib4:amd64 (1.12.4-1ubuntu1.1) ...
Selecting previously unselected package geoclue.
Preparing to unpack .../05-geoclue_0.12.99-4ubuntu2_amd64.deb ...
Unpacking geoclue (0.12.99-4ubuntu2) ...
Selecting previously unselected package geoclue-ubuntu-geoip.
Preparing to unpack .../06-geoclue-ubuntu-geoip_1.0.2+18.04.20180223-0ubuntu1_amd64.deb ...
Unpacking geoclue-ubuntu-geoip (1.0.2+18.04.20180223-0ubuntu1) ...
Selecting previously unselected package gnome-screensaver.
Preparing to unpack .../07-gnome-screensaver_3.6.1-8ubuntu3_amd64.deb ...
Unpacking gnome-screensaver (3.6.1-8ubuntu3) ...
Selecting previously unselected package libido3-0.1-0:amd64.
Preparing to unpack .../08-libido3-0.1-0_13.10.0+17.04.20161028-0ubuntu1_amd64.deb ...
Unpacking libido3-0.1-0:amd64 (13.10.0+17.04.20161028-0ubuntu1) ...
Selecting previously unselected package libpanel-applet3.
Preparing to unpack .../09-libpanel-applet3_1%3a3.30.0-1ubuntu2_amd64.deb ...
Unpacking libpanel-applet3 (1:3.30.0-1ubuntu2) ...
Selecting previously unselected package indicator-applet.
Preparing to unpack .../10-indicator-applet_12.10.2+17.10.20170425-0ubuntu2_amd64.deb ...
Unpacking indicator-applet (12.10.2+17.10.20170425-0ubuntu2) ...
Selecting previously unselected package indicator-common.
Preparing to unpack .../11-indicator-common_16.10.0+18.04.20180321.1-0ubuntu1_all.deb ...
Unpacking indicator-common (16.10.0+18.04.20180321.1-0ubuntu1) ...
Selecting previously unselected package indicator-application.
Preparing to unpack .../12-indicator-application_12.10.1+17.04.20161201-0ubuntu1_amd64.deb ...
Unpacking indicator-application (12.10.1+17.04.20161201-0ubuntu1) ...
Selecting previously unselected package libaccounts-glib0:amd64.
Preparing to unpack .../13-libaccounts-glib0_1.23+17.04.20161104-0ubuntu1_amd64.deb ...
Unpacking libaccounts-glib0:amd64 (1.23+17.04.20161104-0ubuntu1) ...
Selecting previously unselected package liburl-dispatcher1:amd64.
Preparing to unpack .../14-liburl-dispatcher1_0.1+17.04.20170328-0ubuntu4_amd64.deb ...
Unpacking liburl-dispatcher1:amd64 (0.1+17.04.20170328-0ubuntu4) ...
Selecting previously unselected package indicator-datetime.
Preparing to unpack .../15-indicator-datetime_15.10+17.10.20170829.2-0ubuntu4_amd64.deb ...
Unpacking indicator-datetime (15.10+17.10.20170829.2-0ubuntu4) ...
Selecting previously unselected package libfcitx-utils0:amd64.
Preparing to unpack .../16-libfcitx-utils0_1%3a4.2.9.6-4_amd64.deb ...
Unpacking libfcitx-utils0:amd64 (1:4.2.9.6-4) ...
Selecting previously unselected package libfcitx-gclient1:amd64.
Preparing to unpack .../17-libfcitx-gclient1_1%3a4.2.9.6-4_amd64.deb ...
Unpacking libfcitx-gclient1:amd64 (1:4.2.9.6-4) ...
Selecting previously unselected package liblightdm-gobject-1-0:amd64.
Preparing to unpack .../18-liblightdm-gobject-1-0_1.28.0-0ubuntu1_amd64.deb ...
Unpacking liblightdm-gobject-1-0:amd64 (1.28.0-0ubuntu1) ...
Selecting previously unselected package indicator-keyboard.
Preparing to unpack .../19-indicator-keyboard_0.0.0+18.04.20180216-0ubuntu1_amd64.deb ...
Unpacking indicator-keyboard (0.0.0+18.04.20180216-0ubuntu1) ...
Selecting previously unselected package indicator-messages.
Preparing to unpack .../20-indicator-messages_13.10.1+18.10.20180918-0ubuntu1_amd64.deb ...
Unpacking indicator-messages (13.10.1+18.10.20180918-0ubuntu1) ...
Selecting previously unselected package indicator-power.
Preparing to unpack .../21-indicator-power_12.10.6+17.10.20170829.1-0ubuntu4_amd64.deb ...
Unpacking indicator-power (12.10.6+17.10.20170829.1-0ubuntu4) ...
Selecting previously unselected package indicator-session.
Preparing to unpack .../22-indicator-session_17.3.20+17.10.20171006-0ubuntu1_amd64.deb ...
Unpacking indicator-session (17.3.20+17.10.20171006-0ubuntu1) ...
Selecting previously unselected package libfcitx-config4:amd64.
Preparing to unpack .../23-libfcitx-config4_1%3a4.2.9.6-4_amd64.deb ...
Unpacking libfcitx-config4:amd64 (1:4.2.9.6-4) ...
Selecting previously unselected package libunity-settings-daemon1:amd64.
Preparing to unpack .../24-libunity-settings-daemon1_15.04.1+18.04.20180413-0ubuntu2_amd64.deb ...
Unpacking libunity-settings-daemon1:amd64 (15.04.1+18.04.20180413-0ubuntu2) ...
Selecting previously unselected package ubuntu-touch-sounds.
Preparing to unpack .../25-ubuntu-touch-sounds_15.08_all.deb ...
Unpacking ubuntu-touch-sounds (15.08) ...
Selecting previously unselected package unity-settings-daemon.
Preparing to unpack .../26-unity-settings-daemon_15.04.1+18.04.20180413-0ubuntu2_amd64.deb ...
Unpacking unity-settings-daemon (15.04.1+18.04.20180413-0ubuntu2) ...
Selecting previously unselected package unity-greeter.
Preparing to unpack .../27-unity-greeter_18.04.0+18.10.20180926-0ubuntu1_amd64.deb ...
Unpacking unity-greeter (18.04.0+18.10.20180926-0ubuntu1) ...
Selecting previously unselected package indicator-sound.
Preparing to unpack .../28-indicator-sound_12.10.2+18.10.20180612-0ubuntu1_amd64.deb ...
Unpacking indicator-sound (12.10.2+18.10.20180612-0ubuntu1) ...
Setting up accountsservice-ubuntu-schemas (0.0.7+17.10.20170922-0ubuntu1) ...
Setting up libnm-util2:amd64 (1.12.4-1ubuntu1.1) ...
Setting up libgeoclue0:amd64 (0.12.99-4ubuntu2) ...
Setting up libnm-glib4:amd64 (1.12.4-1ubuntu1.1) ...
Setting up libaccounts-glib0:amd64 (1.23+17.04.20161104-0ubuntu1) ...
Setting up gnome-screensaver (3.6.1-8ubuntu3) ...
Processing triggers for libglib2.0-0:amd64 (2.58.1-2) ...
Setting up libfcitx-utils0:amd64 (1:4.2.9.6-4) ...
Setting up libunity-settings-daemon1:amd64 (15.04.1+18.04.20180413-0ubuntu2) ...
Setting up libfcitx-config4:amd64 (1:4.2.9.6-4) ...
Setting up ubuntu-touch-sounds (15.08) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...
Setting up indicator-common (16.10.0+18.04.20180321.1-0ubuntu1) ...
Processing triggers for systemd (239-7ubuntu10.1) ...
Setting up lightdm (1.28.0-0ubuntu1) ...
Adding group `lightdm' (GID 131) ...
Done.
Adding system user `lightdm' (UID 125) ...
Adding new user `lightdm' (UID 125) with group `lightdm' ...
Creating home directory `/var/lib/lightdm' ...
usermod: no changes
usermod: no changes
Adding group `nopasswdlogin' (GID 132) ...
Done.
Setting up liblightdm-gobject-1-0:amd64 (1.28.0-0ubuntu1) ...
Setting up libido3-0.1-0:amd64 (13.10.0+17.04.20161028-0ubuntu1) ...
Processing triggers for man-db (2.8.4-2) ...
Processing triggers for dbus (1.12.10-1ubuntu2) ...
Setting up liburl-dispatcher1:amd64 (0.1+17.04.20170328-0ubuntu4) ...
Setting up libpanel-applet3 (1:3.30.0-1ubuntu2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Setting up libfcitx-gclient1:amd64 (1:4.2.9.6-4) ...
Setting up unity-settings-daemon (15.04.1+18.04.20180413-0ubuntu2) ...
Setting up indicator-datetime (15.10+17.10.20170829.2-0ubuntu4) ...
Setting up geoclue (0.12.99-4ubuntu2) ...
Setting up indicator-application (12.10.1+17.04.20161201-0ubuntu1) ...
Setting up indicator-session (17.3.20+17.10.20171006-0ubuntu1) ...
Setting up indicator-applet (12.10.2+17.10.20170425-0ubuntu2) ...
Setting up indicator-keyboard (0.0.0+18.04.20180216-0ubuntu1) ...
Setting up indicator-messages (13.10.1+18.10.20180918-0ubuntu1) ...
Setting up indicator-power (12.10.6+17.10.20170829.1-0ubuntu4) ...
Setting up geoclue-ubuntu-geoip (1.0.2+18.04.20180223-0ubuntu1) ...
Setting up indicator-sound (12.10.2+18.10.20180612-0ubuntu1) ...
Setting up unity-greeter (18.04.0+18.10.20180926-0ubuntu1) ...
Processing triggers for systemd (239-7ubuntu10.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...


*** And on reboot, without setting nomodeset, I now have a different - but beautifully VISIBLE login screen, without setting nomode set *** :D:D:D:D:D

Thank you to all who contributed to this thread :)



dusf@contraption:~$ inxi -F
System:
Host: contraption Kernel: 4.18.0-10-generic x86_64 bits: 64
Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
Type: Desktop Mobo: Gigabyte model: Z97MX-Gaming 5 v: x.x
serial: <root required> UEFI: American Megatrends v: F4 date: 05/30/2014
CPU:
Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP
L2 cache: 6144 KiB
Speed: 2201 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2036 2: 1955
3: 1962 4: 2188
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: i915 v: kernel
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: modesetting,nvidia
unloaded: fbdev,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel
Device-2: Intel 9 Series Family HD Audio driver: snd_hda_intel
Device-3: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
Device-4: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.18.0-10-generic
Network:
Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 74:d4:35:ee:f3:98
Device-2: Microsoft Xbox 360 Wireless Adapter type: USB driver: xpad
Drives:
Local Storage: total: 3.25 TiB used: 1.81 TiB (55.6%)
ID-1: /dev/sda vendor: Western Digital model: WD10JPVX-22JC3T0
size: 931.51 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3320620AS size: 298.09 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EARX-00PASB0
size: 1.82 TiB
ID-4: /dev/sdd vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
Partition:
ID-1: / size: 19.10 GiB used: 7.71 GiB (40.4%) fs: ext4 dev: /dev/sdd6
ID-2: /home size: 110.09 GiB used: 2.18 GiB (2.0%) fs: ext4 dev: /dev/sdd5
ID-3: swap-1 size: 30.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 44 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 230 Uptime: 1m Memory: 7.65 GiB used: 1.20 GiB (15.7%)
Shell: bash inxi: 3.0.24
dusf@contraption:~$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 144.00 120.00 99.95 84.98 23.97
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
VGA-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
dusf@contraption:~$ optirun glxgears
[ 97.256042] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia" (module does not exist, 0)


[ 97.256104] [ERROR]Aborting because fallback start is disabled.



So I just have some questions:

1. Do I need to do anything to tidy up after all of the commands that were input, bumblebee etc, glxgears not working?

2. I am happy to edit files with nano or vi from the command line, would that be a cleaner fix?

3. Can you explain what the issue is, why it occurred, and if I need to remember to do anything on my next Ubuntu clean install to make sure it does not happen again?
23dornot23d
November 7th, 2018, 07:37 PM
Ok - you can forget this then ............

I was wondering why it could not find nvidia-current .............



So I just have some questions:

1. Do I need to do anything to tidy up after all of the commands that were input, bumblebee etc, glxgears not working?

2. I am happy to edit files with nano or vi from the command line, would that be a cleaner fix?

3. Can you explain what the issue is, why it occurred, and if I need to remember to do anything on my next Ubuntu clean install to make sure it does not happen again?



1 ....... Bumblebee should not be a problem

2 ....... If you wanted to use gdm3 as your desktop management system - then that would be the only reason to edit the config file to stop it using wayland.

3 ....... It was probably gdm3 using wayland that was the cause of the problem - not getting by the login screen

And this part loaded in KMS from the bumblebee install ...... which I believe gave us the intel part that was needed.............



Setting up bbswitch-dkms (0.8-5) ...
Loading new bbswitch-0.8 DKMS files...
Building for 4.18.0-10-generic
Building initial module for 4.18.0-10-generic
Secure Boot not enabled on this system.
Done.


bbswitch:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.18.0-10-generic/updates/dkms/


depmod...


DKMS: install completed.



and I am happy to see this at last



Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
driver: i915 v: kernel
Device-2: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 410.73
Display: x11 server: X.Org 1.20.1 driver: modesetting,nvidia
unloaded: fbdev,nouveau,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73


What could you do on a clean install if you had to do it again ........

In hindsight ........

1 ...... Load Bumblebee in if you know its a integrated hybrid optimus system

2 ....... Then load lightdm as it is using xorg ( as the wayland system is relatively new )


A couple of more questions back ..........

Can you run nvidia-settings now ............ what does it show .............

Do you need to get CUDA working now to do 3D .......... if not mark it as solved as someone else may find parts of it useful
Bashing-om
November 7th, 2018, 11:28 PM
23dornot23d; dusf; -

Yall done such good work in my absence :)

Cookies to 23dornot23d for think'n to install lightdm - see what results.



alls well that ends well
23dornot23d
November 8th, 2018, 12:11 AM
Cheers Bashin Om ......

It was that came up with the idea https://ubuntuforums.org/images/avatars/UF_Logo_original_90.png (https://ubuntuforums.org/member.php?u=811693) heynnema (https://ubuntuforums.org/member.php?u=811693)-

I had read early on someone in this link had done similar using lightdm
was on post #19 answer from mefisto888 (https://ubuntuforums.org/member.php?u=1921682)

This is a interesting read ............ might affect the problem ......... :popcorn:

https://ubuntuforums.org/showthread.php?t=2404556


(https://ubuntuforums.org/showthread.php?t=2404556)
Dáire Fagan
December 30th, 2018, 01:14 PM
I installed 18.04 twice recently, yesterday and the day before (OP title updated to reflect this), and experienced the same issue trying to access the greeter. The first time I replaced the boot option splash screen with nomodeset, logged in, and input:


sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
sudo apt install nvidia-415

sudo apt install lightdm

This worked, but was it the correct procedure for that method? I did first try installing lightdm from a recovery shell with networking enabled but it could not find it for some reason. The reason for installing again was due to another issue, unrelated to this thread.

On my latest install, I logged in with nomodeset, and then in Software & Updates >> Additional Drivers >> I installed and am now using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested). I though I would then try the method heynnema outlined:




- boot to recovery mode
- choose root access

type:

sudo mount -o remount,rw / # to remount the disk r/w

sudo pico /etc/gdm3/custom.conf # edit this file

change:

#WaylandEnable=false

to:

WaylandEnable=false

Then reboot.

But it resulted in the following screen when trying to boot:

282039

lightdm works fine, but out of interest I just want to see if I can get gdm3 working.

Also, for my own understanding, is the issue that my GTX 970 is too old to support Wayland, which I have read is 'a protocol for communication between display servers and their clients', so between X.Org and Ubuntu or Gnome perhaps?
Dáire Fagan
January 3rd, 2019, 11:05 AM
Tried several times to get gdm3 working, with the WaylandEnable=false flag set and it still resulted in the same black screen, black screen with pink lines across the top (which I guess was the greeter background in some form) when the greeter should appear.

Using lightdm I was able to login, although every third or so login instead of the greeter I would see a black screen, with a blinking underscore top left.

When I could login normally a window would appear telling me that System Program problem has been detected and prompted me to report the error, and after doing so, /var/crash/ would contain a newly generated _usr_lib_xorg_Xorg.0.crash file.

I have copied this file to my home directory, but I am still unable to open it with a text editor.

Searching for the file online I found a post where someone explained their issue was with lightdm, and they were advised to switch to gdm3.

I thought I would try gdm3 again, so I input the following:


sudo apt-get install gdm3
sudo dpkg-reconfigure gdm3

The later command gave an error, but on searching the advice was to reboot anyway, so I confirmed the WaylandEnable=false flag was still set, and on rebooting gdm3 just worked. FTR I am using nvidia-driver-415.

When I logged back in I input sudo dpkg-reconfigure gdm3 again and this time the command was no complaint. There have been many reboots over the last day and it seems to work great bar once, where I could see the system hung on:


Started NVIDIA Persistence Daemon

As this only occurred once I am marking this thread as resolved, and if I encounter the same system hang again I will open a new thread and investigate.
Macmee
January 21st, 2019, 06:38 PM
Tried several times to get gdm3 working, with the WaylandEnable=false flag set and it still resulted in the same black screen, black screen with pink lines across the top (which I guess was the greeter background in some form) when the greeter should appear.

Using lightdm I was able to login, although every third or so login instead of the greeter I would see a black screen, with a blinking underscore top left.

When I could login normally a window would appear telling me that System Program problem has been detected and prompted me to report the error, and after doing so, /var/crash/ would contain a newly generated _usr_lib_xorg_Xorg.0.crash file.

I have copied this file to my home directory, but I am still unable to open it with a text editor.

Searching for the file online I found a post where someone explained their issue was with lightdm, and they were advised to switch to gdm3.

I thought I would try gdm3 again, so I input the following:


sudo apt-get install gdm3
sudo dpkg-reconfigure gdm3

The later command gave an error, but on searching the advice was to reboot anyway, so I confirmed the WaylandEnable=false flag was still set, and on rebooting gdm3 just worked. FTR I am using nvidia-driver-415.

When I logged back in I input sudo dpkg-reconfigure gdm3 again and this time the command was no complaint. There have been many reboots over the last day and it seems to work great bar once, where I could see the system hung on:


Started NVIDIA Persistence Daemon

As this only occurred once I am marking this thread as resolved, and if I encounter the same system hang again I will open a new thread and investigate.

Hey there. I also have a 970. I had the exact same problem with you where I boot up to a black screen. Due to your thread I saw you got it working with lightdm so I installed that as well as nvidia-driver-390 and sure enough it worked and I'm back in business.

Are there any reasons to prefer a gdm3 solution over lightdm? Also I tried uncommenting WaylandEnable with gdm3 but got the black screen anyway. Was there something else you had to do as well?