New answers tagged

0

GDM 3.34.1 known issue currently as unstable, caused mine to freeze just before login screen. ctrl-alt-f2 logged in and typed startx then i was able to have my gui screen back. Made sure autologged in was checked in settings and I'm getting by. Can't log out or login but can use Ubuntu 19.10 for now! Good luck, keep us posted.


0

Solution for the gdm problem should fix it for you. Be patient. GDM 3.34.1 is super unstable as we speak. login/corruption/not seeing enviroments proper etc.. To name a few issues I've been just learning about


-1

How to: (KDE Linux 64-bit) On a clean or freshly installed and fully updated operating system. (Make sure the non-free repository is enabled). Reboot at least once after updating. Download a Nvidia driver run file that suits your video card from Nvidia.com. Make sure you copy the run file into your /home/your-username directory. Do not copy it into ...


0

None of the solutions listed here worked for me. I could however use ssh -X <user>@<host> to start an X session from a different machine. (Fill your actual user, host obviously.) Then do sudo nvidia-settings and select Intel instead of nvidia. Now I can get past the previous problem, but the resolution is miserably low, 960x540 at best. ...


0

Leave the USB key after the post install reboot. Tick the "CD/USB" source for packages and you will have the additional drivers for nvidia coming off the USB key. Don't forget to enable restricted drivers (proprietary).


-1

May be a dumb question but are you sure your display is enabled ? Settings -> display (I guess mine in french is "Affichage") What happens when you unplug your external monitor ?


0

I discovered that there's a way to manually unbind kernel modules for specific devices in the pci so I did this little script echo -n "0000:07:00.1" > /sys/bus/pci/drivers/snd_hda_intel/unbind echo -n "0000:07:00.1" > /sys/bus/pci/drivers/vfio-pci/bind echo -n "0000:07:00.2" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n "0000:07:00.2" > /sys/...


0

I had the same problems with Nvidia drivers. In my case I have been installed xanmod kernel without supported Nvidia drivers. During sudo apt install nvidia-340, sudo apt install -f, sudo ubuntu-drivers autoinstall commands execution, it throws: Setting up nvidia-340 (340.108-0ubuntu0.19.10.1) ... dpkg: error: version '-' has bad syntax: revision number is ...


1

Readers who want a quick answer please skip to the last paragraph of this answer. There's not much difference between Nvidia drivers in the upgrade direction. The later version of the Nvidia driver will usually have a little bit better performance, but you can use either version and either of the versions will work, however there can be a real difference ...


0

I have the identical setup referenced. I had this blurring problem and traced it to enabling FXAA in Nvidia settings. Originally I enabled this feature out of curiosity and noticed no difference. I then forgot about it. Yesterday I applied available updates and suddenly this blurring problem presented. After much futile struggle, I recalled fiddling with ...


0

I discovered that when installing the drivers, it asks for a password for secure boot. After rebooting Ubuntu, you need to enrol the MOK. If you don't do the enrolment, then Ubuntu will still boot but not with the Nvidia drivers. So it will use the default driver.


0

In my situation I had to install the i386 NVIDIA drivers. It worked thereafter. sudo apt install libnvidia-gl-440:i386 Have a great day!


1

sudo update-alternatives --all Change everything with clang selected back to gcc It works. Finally.


0

I had the same issue. tried what user535733 recommended, but received an error. I did not have nvidia-cuda-dev installed, so I could not remove it. However, nvidia-cuda-toolkit was a dependency, so I removed that. That seems to have cleared up my issue, but now I do not have nvidia-cuda-toolkit! So that's no good for me but seems to be what @itamar-...


0

Can you disable the 3D Accelaration in virtual box for this VM and then reboot the VM. I had the same issue after disabling 3D Acceleration it worked perfectly.


0

I just typed sudo ubuntu-drivers install and my machine booted, and I was able to use my graphics card as normal. (I have had trouble with nvidia drivers before so I feel pretty lucky that this worked.)


0

I had the same problem. At some point I recall that I also needed to do something like apt-get update apt-get upgrade Apart from that, deleting and reinstalling gdm3 was that it fixed it. Don't remember the particular order in which I did it. I think I found the answer in this same forum, but don't remember the particular post...


2

You can install the correct proprietary Nvidia drivers by running the following commands: sudo apt update sudo ubuntu-drivers autoinstall Then, reboot.


0

You can try reading this answer: How do I install the Nvidia drivers? I had the same problem for weeks. Unfortunately, the only way to use Ubuntu for me was to change from the Nvidia driver to Intel. You can do it with: sudo prime-select intel


0

My /etc/modprobe.d/blacklist-nvidia-nouveau.conf: blacklist nouveau options nouveau modeset=0 blacklist nvidiafb Then, sudo update-initramfs -u Ctrl-Alt-F(1-5), systemctl disable|stop lightdm apt install xdm Reboot. Check nouveau not loaded: lsmod apt install nvidia-driver-435 systemctl enable xdm


0

I had a raft of these problem with nvidia-340 diverts in Ubuntu 19.10; it seems to be a known bug with Ubuntu. package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 (NOT FIXED) The workaround I did was #5, Yuri's improvement of Alexandre's ...


1

Looks like this is a bug with Ubuntu. package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 (NOT FIXED) The workaround I did was #5, Yuri's improvement of Alexandre's suggestion Try # for FILE in $(dpkg-divert --list | grep nvidia-340 | ...


0

Looks like this is a bug with Ubuntu. package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 (NOT FIXED) The workaround I did was #5, Yuri's improvement of Alexandre's suggestion Try # for FILE in $(dpkg-divert --list | grep nvidia-340 | ...


0

Well I found ubuntu drivers for my graphics card at https://www.amd.com/en/support and after installing them it made a big difference. Not 100% perfect, but 90% better. Hooray for those that make linux drivers.


1

I've had this issue on an Nvidia-equipped laptop. The problem and a workaround are nicely described here - https://dev.getsol.us/T6335 Basically, you can work around this by forcing NVidia Vulkan ICD with the environment variable set from one of the startup scripts: VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/10_nvidia.json Your path to the NV ICD may be ...


1

Well, this is pretty awkward! I remembered the Composition tab in System Settings > Display and Monitor > Compositor and changed the rendering backend from OpenGL 2.0 to OpenGL 3.1. Did a reboot, and everything works as intended with nVidia drivers! Screen 1 Screen 2 Pretty embarassing, but I hope this helps someone out there!


0

This is just an informed guess, but on battery power your GPU is probably throttled down automatically, but on AC power it may be overheating, and that may result in even more throttling. Alternately, being on AC the charging battery, and increased CPU clockrate are going to increase the internal heat generation, and the overall internal temperature inside ...


0

Welp i found the culprit, i somehow fycked up my first ubuntu install by not allowing a swapping space big enough , by doing so followed a random tuto to start with the "nomodeset" in recovery mode , thus making it kinda work but only in recovery , but deactivacting the graphic card options and making it impossible for sofwares to get a proper acces to it , ...


2

I would suggest to upgrade the driver. Run in a terminal sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update sudo apt install nvidia-driver-418 sudo apt upgrade Most likely this will fix the issue on the 5.3 kernel.


1

Depends on how the app was compiled and with what resources. The app in question was compiled/developed when CC2.0 was current and probably checks for that as minimum requirement. When the app checks current hardware and software drivers, the returned values are outside the minimum requirement because the app wasn't written for >2.0 as a possibility. ...


0

For the Nvidia GT2XXM video card, you need to install their 340.1080 driver, which can be downloaded from https://www.geforce.com/drivers


0

I scoured the web when I got my MSI GS65 Stealth with GeForce GTX 1660 Ti/PCIe/SSE2 and installed Ubuntu 18.04. I tried pretty much everything but nothing helped. What did it for me was installning Ubuntu 19.10. Everything worked right out of the box and seeing as Ubuntu 20.04 LTS is right around the corner, this feels like a viable solution.


0

I found a solution to my own problem, even though I wasn't able to track down the cause of the issue with the Intel integrated graphics, which appeared to have been cleared on its own. On my next boot (still without access to the desktop environment) I verified the contents of the gpu-manager.log file: mary@mary:~$ cat /var/log/gpu-manager.log log_file: /...


0

As @Ali Rasooli said it, the tool you want to use is the prime-select command. Unfortunately on 18.04 you have to reboot to put into effect the change. You can benchmark your GPU by installing glmark2 (sudo apt-get install glmark2) and see if after reboot it actually switched between your dedicated and integrated graphics. I did not find another reliable ...


0

I get that sometimes on my Ubuntu 18.04.3. Last time when I checked the system logs it seemed that it's all caused by a lack of free memory (I have 8GB RAM). I found a workaround so I don't have to restart my computer and it's simply restarting gnome with: Alt+F2 typing r and pressing Enter. And if that is not working you could try to open your terminal ...


1

You can find the release notes for all Nvidia drivers HERE Just enter your info in the drop down menus and search, it will return all Nvidia drivers still in service. If you select the driver version it will bring up a new page and give you 3 tabs. The first will tell you what has changed since the last release. The second tab will give you a list of ...


0

Converting Ubuntu into Legacy mode If Ubuntu is installed on a GPT disk (you can check it via the 'sudo parted -l' command), use Gparted to create a BIOS-Boot partition (1MB, unformatted filesystem, bios_grub flag) at the start of its disk. Start Boot-Repair, click on "Advanced options", go to the "GRUB location" tab. Untick the "Separate /boot/efi ...


1

Problem solved! Got the driver installed. So it turns out the dependency to the driver (nvidia-dkms-440) had a dependency (dkms) which had a dependency (dpkg-dev) which had a dependency (libdpkg-perl) which was in fact installed on my computer. The problem was that I had the latest version of that package (1.19.0.5ubuntu2.1) and for some reason that was ...


0

In Linux command line, type matlab -softwareopengl, it will start Matlab with normality. To make this default, inside Matlab command line, type opengl('save','software'). It works with Matlab R2019b on Ubuntu 18.04.


0

Shangchun's answer worked for my UX362F. To make the boot change permanent I edited /etc/grub/default GRUB_CMDLINE_LINUX_DEFAULT="dis_ucode_ldr" and then ran sudo update-grub I did not have to do the apt steps. Not sure if this means I'm missing something important or if this issue is only related to the boot process. Seems to work.


2

There is not a lot to do since the software we used to use for this (laptop mode, tlp) all got incorporated into the kernel. Ubuntu comes with software and drivers for nVidia and that is installed by default. At the top panel it will have the nVidia software where you can switch between Intel for power saving and nVidia for performance. Example where you ...


1

Kernel updated to 5.3 recently. But Ubuntu maintainers forgot to update the 390 Nvidia driver to build with that kernel. The solution is to install a driver from PPA. Run in a terminal: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update sudo apt upgrade and reboot. That solved exactly same issue for me.


0

This fixed it for me: sudo apt-get install libnvidia-gl-390:i386 Source


1

Well, by the end, Bumblebee did the trick. But, to make it work, after a lot of trials and errors, I did the following: 1. Purge EVERYTHING related to NVidia What I mean: sudo apt purge *nvidia* Note that I'm not doing nvidia* because it lefts behind stuff like libnvidia-whatever.so 2. Reboot After this, the notebook was not booting properly: it was ...


1

Tried everything. Only one thing helped: disable the ASPM. Add this to kernel boot arguments: pcie_aspm=off


0

In my case the solution would be to go to the previous kernel version and wait for the new kernel to get released.


0

Solved! I installed again ubuntu 19.04 in safe graphics mode. It seems that also Nvidia now works. But, I have another issue: after login Ubuntu is blocked. May be issue with graphic card driver..but I didn't check yet Should I do a new thread? Thanks


0

I have this issue and for me, it looks like it is an nvidia issue: https://devtalk.nvidia.com/default/topic/1060783/linux/random-xid-61-and-xorg-lock-up Check your syslog / kern.log for something like the following: [28736.200395] NVRM: GPU at PCI:0000:07:00: GPU-06a0a514-1651-491d-717c-2e1e24b93c99 [28736.200398] NVRM: GPU Board Serial Number: ...


0

I had similar problem, played with UEFI & Legacy boot mode, searched for hours but finally got it done by following ways: 1. goto Software & Updates 2. Additional Drivers 3. Changed the display driver from there. 4. restart


0

Since this module is currently in use by another module, you can't. If you don't need it anymore, you can remove the nvidia driver from your system. Another method would be to forcefully remove it with rmmod -f, but I would not recommend doing so.


Top 50 recent answers are included