since you said trying nvidia-driver-390 I can suggest you try some solutions. The first one is trying to get the drivers from Software & Updates, under the "aditional drivers" tab.
In my case I already installed Ubuntu with the proprietary drivers, but you could try selecting the first option: proprietary, tested.
If it doesn't work you could ...
Monitor stays black on boot. No BIOS startup screen
Looks like this is a hardware problem, rather than a software problem. So i would try this:
turn off the computer
disconnect the power cable
disconnect the monitor cable
remove the graphics card
look for anything suspicious, maybe a burned component on the card
put the graphics card back in, make sure it'...
I ran into a similar issue, and after a reboot the issue went away.
One thing I would recommend is not to use the automatic login on Ubuntu 20.04 because that is what caused me to get into an infinite login loop since the machine thinks I am already logged in even though I am not.
I have upgraded the Kernel from 5.11 to 5.14 and the problems I was experiencing have disappeared. I have been testing the Kernel for nearly three weeks with no adverse effects.
What is the search engine? Answer: all of them. Technical advice done by numbers? Answer: i.e. step1, step2, step3, etc.
Disable fast start
boot into Windows
open the Power control panel
choose change what the power buttons do
choose change options that are unavailable
uncheck fast startup
close the Power control panel
Don't do this if you use hibernation
open an administrative command prompt window
type powercfg /h off
Check your C: drive
type chkdsk /f c:
approve to run ...
It's really time for a first answer. ;-) At the beginning it should be noted that this topic here is one of the most complex regarding the installation of K(U)buntu in native EFI mode.
The first big problem is that on these early Apple Intel computers the vBIOS is not really exposed in native EFI Mode. On these Apple models, the vBIOS is usually only ...
I have the same laptop and I experienced a similar problem after I upgraded the kernel. To solve it, I downgraded the kernel to 5.11.0-31-generic (if you don't have it, install it with apt install linux-headers-5.11.0-31-generic (I'm not sure if you need to install some other things as well, like linux-image-5.11.0-31-generic, or if it will happen ...
I know this topic is quite old. But unfortunately nobody has given here the "right" answer. ;-)
Long speak short, this is NOT a driver issue! The underlying problem is that the "vBIOS is not exposed in EFI mode". This can be seen indirectly at the error message [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
No regular ...
After posting my question I found this answer from AskUbuntu's suggested answers. This worked and restored both keyboard and GUI LCD backlight brightness control functionality.
This is the link to the answer: https://askubuntu.com/a/199652/1128472.
These are the steps I followed from the answer:
# first I created the following file using this script. A blank ...
In '/etc/X11/Xwrapper.config' add:
allowed_users = anybody
needs_root_rights = yes
and change permissions:
chmod 2644 /etc/X11/Xwrapper.config
I got this working in a multi GPU config with 470.63.01 drivers. I thought that the problem was with the coolbits but it actually was the Xwrapper.config (by the way, I set the coolbits in '/etc/X11/xorg.conf')...
Actually, nvidia driver support on especially Ubuntu is quite good. The Geforce 820M however is quite a strange GPU. There exists multiple devices under the name of 820M. One of them is using a GF117 chip which is based on the Fermi architecture. There however also seems to be a variant that is based on the Kepler architecture using a GK107 chip which is ...
The issue was hardware acceleration. There are lots of information already online regarding how to deactivate it system-wise. I fixed these issues (apart from Zoom which is still flickering) by following the answer from this post. Note that the other solutions mentioning creating a /etc/X11/xorg.conf.d/20-intel.conf and putting an AccelMethod to sna didn't ...
I installed nvidia-driver-390 for my geforce 920M by typing sudo apt install nvidia-driver-390 in the terminal and now I don't have any issue.
EDIT: Few softwares gave an error that nvidia-driver-390 was too old and I needed a newer version to make them work properly, so I started testing some other drivers for my GPU and found that nvidia-driver-418-server ...
According to the Nvidia website, you are using the wrong driver version for your particular card.
Run the following commands to ensure proper installation and configuration of the correct proprietary driver:
sudo apt update
sudo ubuntu-drivers autoinstall
First of all this doesn’t look like tearing to me. It’s a graphical issue but likely not tearing. That is why Wayland probably didn’t help.
It looks more like a gpu related issue. Recently 20.04 should have gotten an update to 20.04.3 which includes a newer Kernel and Mesa GPU drivers. If possible can you find an older Ubuntu ISO of 20.04.2.0 and try run ...
After searching on internet for solutions, I came to know that it is the problem of my radeon GPU driver. Apparently there is some issue of Vulkan support with this driver(Reference Article Here). My GPU is also supported by amdgpu driver. It was also present in my laptop, but my Linux distro selected radeon by default.
I followed this article and switched ...