Faced with this problem in Lenovo G780, NVIDIA 635M and nvidia-
driver-390 package
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
Kernel Version: 5.0.0-29-generic
Addition of "WaylandEnable=false" to
/usr/share/lightdm/lightdm.conf.d/90-nvidia.conf resolved the problem.
--
You recei
I have a NVIDIA Corporation GP107 [GeForce GTX 1050] card and ubuntu 19.04
installed. After installing the lastest Nvidia driver-430, the dektop GUI is
lost when you reboot (18.10 gave the same issue). I tried many proposed
solutions, including the one above. Nothing worked.
I finally found a so
I am running ubuntu 18.04 and using the low latency kernel rather than
the default kernel. Since the "upgrade" to nvidia 390 it looks like the
kernel module is actually missing from my filesystem. Running dmesg |
grep nvidia and modprobe | grep nvidia tells me the nvidia driver is not
loaded. Wh
Please note this bug is closed, so generally will be ignored by
developers.
If you have any ongoing problems please consider joining one of these
open bugs instead:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=nvidia
or log a new bug by running the command:
ubuntu-bug gdm3
Same issue with Nvidia Geforce GTX 1060 6 GB - wouldn't work with 390,
396, 410, or 415 drivers. Only Nouveau under Ubuntu 18.10 (upgraded from
beta and previously 18.04 as original install)
Resolved by switching to lightdm and booting into Cinnamon Desktop instead of
Gnome. Mate works as well.
Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install
and applying nvidia-390
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot gra
Guys ..
I have Nvidia 1050ti with nvidia-390 driver installed.
When i boot am on 900 resolution instead of a 1920x1080 normal
resolution.
Anyone got a solution for that ??
Thanks in advance.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
On KUbuntu 18.04 same problem with card GT630M and 390,396 nvidia drivers
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
# cat /etc/X11/default-display-manager
/usr/bin/sddm
--
You received this
The uncommenting #WaylandEnable=false worked a treat for me as with the
previous posters. This is the answer to this problem and needs pinning
to the thread!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.la
I had the same problem after upgrading to 18.10. Uncommenting
"WaylandEnable=false" worked.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphic
I didn’t need to remove GDM3, but installing LightDM (and switching to
it) fixed it for me. Well, I should say it was a workaround, anyway...
> On Oct 24, 2018, at 11:56 PM, ccdisle wrote:
>
> Uncommenting "WaylandEnable=false " worked.
>
> Removing gdm3 did not work, I just got redirected to a
You're welcome, Ccdisle.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Status
Uncommenting "WaylandEnable=false " worked.
Removing gdm3 did not work, I just got redirected to a tty3 login shell.
Thanks again
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
T
I just tested this. It worked for me as well. Thanks, Nebojša.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa pa
:) You're welcome.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Status in nv
OMG! Where u were all this time?! Thank you very much!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in
Please try, in the /etc/gdm3/custom.conf, uncomment WaylandEnable=false
and Nvidia driver will work with gdm3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fa
Solution found with NVidia support.
GDM3 causing Ubuntu 18.10 to "freeze" before login screen
After remove GDM3 and LightDM installation Ununtu booted as usually
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bug
I would say workaround not solution
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Rele
Found this opened report related to the nvidia driver
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1795808
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/17520
@tjaalton ... funny, >185 persons report they have same issue here
without any solution.. and then bug reports get closed without reference
to where to duplicate all reports ? ))
Do you have bug number where we can copy and paste this to ?
--
You received this bug notification because you are a
this bug is closed, if you are seeing issues with current versions
please file a new bug instead of posting here
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390
Texted to NVidia support about the issue. Got reply
Your case is being escalated to our Level 2 Tech Support group. The
Level 2 agents will review the case notes and may attempt to recreate
your issue or find a workaround solution if possible. As this process
may take some time we ask that you be
Same problem here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Status in nv
Yes this is exactly the problem I have. Every-time I install the Nvidia-
drivers the machine won't boot up it hangs and displays
"Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/ubuntu--vg--root"
I even tried installing earlier drivers -340 or 361 . The problem
persist
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-
driver-390)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical displa
New install ubuntu 18.10. Nvidia-390, nvidia-410 freezes before login.
Only purge drivers makes system back to boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-3
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-
driver-390)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical displa
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-
driver-390)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical displa
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-
driver-390)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical displ
After upgrading from 18.04 to 18.10 the gnome freezes after GDM login.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in
It remains weird that a complete ciritical-show-stopping bug receives no
attention from the true experts... What are we doing wrong to report it
here?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.
I am also having this issue, system fully updated, nvidia-driver-396,
GTX 1050Ti, kernel 4.15.0-33-generic. Also happens with nvidia-
driver-390. The fix for me was #123:
sudo service gdm stop ; sleep 5 ; sudo service gdm start
This is definitely not fixed.
--
You received this bug notification
I know it's kind of rude just to "+1" on an issue. But whoever is
responsible for these NVidia drivers deserved it. So, +1. Issue is not
fixed. Blank screen on upgrade from 16.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ub
I am affected by this bug, too. Using an nVidia GTX 660 with legacy
nvidia-340 (both mainline as well as graphics-driver ppa) my system is
working as before. Switching to 390 or even 396 leaves me at a blinking
cursor DM both on sddm and gdm3. The only DM I could use has been
lightdm but only after
So I was able to get everything working on 16.04 with nvidia-384. I
tried many a different things on 18.04 with nvidia-390 and nvidia-396
but no luck including using proposed Bionic Beaver but no luck. If I can
help report anything though I'd be glad to post it if you tell me what
you need from my
I think I have the same issue.
Difference is that everything worked as charm until I've updated some
non-nvidia packages. Since then I'm stuck to uning nouveau as none of the
workarounds worked.
HW:
ROG STRIX GL503VM-FY022
nVIDIA GeForce GTX 1060 6GB
What worked fine before update:
kernel 4.15.
Solution in #123 did not work for me, even with higher sleep time.
So I have to switch back to lightdm.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to
I am using Google Translate because English is not very good.
I am sorry if there is content difficult to understand.
```
$ uname -srvpio
Linux 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64
x86_64 GNU/Linux
$ nvidia-smi
Fri Jul 13 14:12:01 2018
+---
Ubuntu 18.04
Mate & XFCE
Running Nvidia 390 - NVIDIA Corporation GM107M [GeForce GTX 850M] (rev a2)
Same issue faced here. Initially everything was running well until I
tried installing the CUDA libraries for Machine Learning purposes. This
was the start of this disaster.
This Issue should be co
https://sourceforge.net/projects/toysbox/files/bionic-
nvidia/xubuntu-18.04-4.15.0-24-nvidia.iso/
sorry for typo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-39
you might be interested to try liveiso xubuntu-bionic nvidia-390.48
a live_iso bionic-xubuntu with nvidia-390.48 prime-switchabled to experiment :
it's working on Acer VN7 4GB ram
boot the live iso http://sourceforge.net/projects/toysbox/
xubuntu-18.04-4.15.0-24-nvidia390.48.iso
open a terminal
I started to experience this problem for the first time on July 2nd,
2018 after upgrading to kernel 4.15.0-24-generic. It only happens on
machines with a Nvidia card. It does not matter if ANY Nvidia drivers
are installed or not. I downgraded to kernel 4.15.0-20, 0-22 and 0-23
but it didn't fix the
This is not fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Status in nv
It's indeed a big mystery when one of the maybe most serious bugs in
18.04 is marked as fixed while it clearly is not
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
n
Also having a this problem. Why is this marked fixed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in
Hello,
The GUI (graphicc user interface)!dose not start If i have no internet
connection (offline )
An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04
Have the same probkeme
The internet must connect at start (Ethernet or WiFi)
Same problem whith the live dvd ?
Why this
I opened a new bug report since nobody seems to be able to change the status of
"Fix Released" which is clearly not the case. Please comment and subscribe to
this one
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773113
--
You received this bug notification because
The graphical display failed to boot on laptop. The same system Ubuntu
18.04 works on the desktop.
https://drive.google.com/file/d/19i41gRcpzIErlU82Ekk-
Hq5JUpUByHEw/view?usp=sharing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa i
I had working proprietary drivers for my GTX 1080 Ti and then I upgraded
from 17.10 to 18.04. Everything worked well, gdm login screen appears,
but AFTER entering username and password and hitting ENTER, I only get a
black screen.
For me #123 solved the problem, thanks for the detailed description
@aurelienpierre: are you sure your laptop uses the same device number as
the Dell XPS 15 this script was for (:01:00.0)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
I have the same problem of power drains even when prime-select is on
intel. I know for sure that the nvidia GPU is running because the
external HDMI port is working and shouldn't since it's wired to the GPU.
sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
sudo sh -c "e
So, if this bug is marked as "fixed released" and 500 comments further
it's clear it doesn't fix anything, should we open a new bug report?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/17
The only working solution for me for the Nvidia graphic card problem in
Ubuntu 18.04, was to follow the instructions from this page:
https://medium.com/@emtudo/ubuntu-18-04-travamento-com-placa-nvidia-
3720dfe7410a
and then start the system through recovery mode.
--
You received this bug notifi
@bernadette, it baffels me. Today my Xps 15, 9560 works flawlessly fast
and nimble. I also nailed the power drain and now have ~5W running on
battery, see https://github.com/stockmind/dell-xps-9560-ubuntu-
respin/issues/8
Makes me thinking... what BIOS version do you have ? I run 1.9.4
** Bug wat
Hello. My situation was very complicated, and none of the fixes I found
would work. I am running a Nvidia GTX970 with an Intel CPU and using a
dual monitor setup. Ubuntu 17.04 was working very well. Later upgrading
to Ubuntu 17.10, the Nvidia graphics became an issue because of Wayland,
but I follo
also, still investigating. every one of these fixes all lead to the
same outcome for me - cannot boot with nvidia proprietary drivers
installed, or else stuck in a boot-loop after entering password at gdm
screen.
--
You received this bug notification because you are a member of Desktop
Packages,
echo "1" > /sys/bus/pci/devices/\:01\:00.0/remove is required for me
to powerdown nvidia, but it results in powerdown freeze
Still investigating ... ((
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.laun
If you want it to stay create a file /etc/rc.local and make it
executable:
sudo chmod +x /etc/rc.local
In rc.local type:
#!/bin/sh -e
sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
sh -c "echo "1" > remove" (I didn't need this)
exit 0
--
You received this bug notificatio
It seems with the following two commands, I can get my power from ~15W
to ~8W on Dell XPS 15 9560:
# move from Nvidia to intel graphics (if not already done)
prime-select intel
# switch of power to Nvidia (repeat after each laptop start)
sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:
@Dedas: I cant see any difference; power consumption on Dell XPS 15 9560
stays the same...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphica
I upgraded from 17.10 to 18.04. It wouldn't log in, but through ssh I
purged the nvidia drivers, installed 396 through the PPA, rebooted, and
it came up and worked. It is a tower with GTX 1060.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
@Tom
"can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?"
Yes it should be safe. It it freezes just restart your machine, the
setting will be gone.
It turns off the nvidia gpu så no.
I am not sure whether it is ok to post here, but I have lately found
this github repo dedicated to making Ubuntu run on XPS 9560. It works
for Ubuntu 17.10 and 18.04 will be hopefully added as well. Many of us
have this laptop and the repo partly adresses the issues mentioned here
so I thought post
Got back screen yesterday but for my case it was a disk space issue.
Booted into recovery mode, freed up space in root partition and
rebooted. Everything seems work ok after that... Apparently nvidia does
need some free space to boot up (it wasn't an issue before i think. My
system partition is rea
@Dedas can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
ht
Thank you for your answer. I solved the problem with nvidia prime not
really disabling the nvidia card (still drawing power) when switching to
Intel with:
sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
Almost halved the power draw on my Dell XPS 15.
--
You received this b
Andreas, nvidia on my notebook is enabled and working properly. It is
not disabled.
Currently I only one option enabled for GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="splash"
I do not have /etc/X11/xorg.conf file.
If you backup file /etc/X11/xorg.conf, remove
Ivan Janes,
With those options NVidia card seems to be disabled properly but now the
systems hang whenever I plug in the laptop power charger. Also, I can
only use Wayland and not Xorg (freeze again). Maybe the last one is a
bad xorg.conf?
--
You received this bug notification because you are a
I have finally getting to work my ubuntu 18.04 with drivers installed
from additional drivers.
After update from ubuntu 17.10 to 18.04 nvidia-390 drivers were
installed, nvidia-340 package was metapackage for nvidia-390.
Today I was able to install nvidia-340.106 driver directly from
additional d
no #121 don't work for me
I can access my desktop because i have blacklisted nouveau and using my intel
gpu system which I assume is functioning via mesa drivers nomodeset also works
only issue is if i try to run nvidia
--
You received this bug notification because you are a member of Desktop
@tom-lorinthe
I have no issues with accessing Intel I just blacklisted nouveau for
that purpose. I wanted to use Nvidia but on evry install it seems to
crash the OS
will try and fix nvidia-prime after getting nvidia driver working
there is also dkms seems not to install in the kernel 4.15.21
an
@Joseph: did you try #121 ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Sta
hey
There i am using ubuntu bionic 18.04 kernel 04.15.21
cant login on gdm or lightdm freezes on entering password or access tty
on install nvidia-390 , nvidia 396 from ppa:graphics-drivers/ppa and
nvidia-driver-390 from bionic main repo
used to have black screen on boot suddenly rectified
nou
I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to
give up on Ubuntu and give that a try. Some word of reassurance from the
Ubuntu team here would be nice. Where they marked this as fixed, I'm not
hopeful of a fix--at least anytime soon. If anyone has found a true and
simple w
In my case it was... complicated.
Turns out that after upgrade to 18.04 wayland was on by default for me.
prime-select intel worked fine
prime-select nvidia gdm would not show
Changing wayland to xorg in gdm (with intel) would not work - login
screen just kept reapearing. Forcing xorg through /et
This all might be related to https://bugs.launchpad.net/ubuntu/+source
/nvidia-prime/+bug/1765363 I think...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fai
Is there any way possible to gain early access to the "FIX RELEASED"
files???
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
St
Back to where I started with a non-bootable machine, after modifying
xorg.conf listed in post #121. I will go aheada purge these nvidia
drivers again, and try #123 to see if that works. This is a crazy
mess!!
--
You received this bug notification because you are a member of Desktop
Packages, wh
I just tested the thing in #123 and I can only conclude: i am writing
this note in 18.04 with nvidia-396 drivers on a Lenovo Y720. So I can
only agree to what Thijs says. This sounds like a timing problem.
--
You received this bug notification because you are a member of Desktop
Packages, whi
Why this have "Fix released" status? I cannot login after "prime-select
intel", I see only a black screen
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails t
I tried #116 by @minterior, and I now have a working desktop, but it
feels substantially more sluggish than it was under 17.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title
I've just ran do-release-upgrade on a Lenovo P51, and the systems hangs
just after "Starting Session c1 of user gdm". I get a little further by
purging nvidia-* (I get the GDM greeter again) but after logging in
there, the screen freezes and a little later I'm kicked back to the
greeter.
--
You r
@Thijs Kaper: I have the exact same problem.
My alternative workaround:
Like you I authenticate, black screen after typing the password and hitting
enter. Then I go to tty2, authenticate in the terminal, and type 'startx' (and
4 times Ctrl+C). And finally KDE starts without problem on tty2. This
I'm using a Dell m4800, with "NVIDIA GK107GLM Quadro K1100M" (3840x2160
pixels). Symptom; gdm login screen shows normally, but after typing
password and hitting enter, I end up on black screen. This is after
upgrade from 17.10 to 18.04.
I found a silly workaround (after trying many many other sugg
@Tom - getting closer! I can now login...but icons are HUGE!!! Lol.
Need to fix resolution
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphic
@Bernadette: If I would have same situation again, I think I would:
1 - Ctrl-Alt-F3/2 at login prompt
2 - sudo apt purge nvidia*
3 - sudo apt install nvidia-390
4 - sudo prime-select intel
5 - sudo nvidia-xconfig
6 - sudo nano /etc/X11/xorg.conf
7 - .. and replace with contents of #117
8 - sudo n
tried #116 and also #108. Now all I get is a boot loop at the lighdm
login screen. Put in password and it brings me back to login screen.
This is so frustratingsmh
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
http
#117 worked for me, although "suspend" is still shaky; 50% of time I
need to force power off.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graph
#116 worked for me, thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Stat
For PRIME users: as a workaround you can make you X session work with
Intel driver with this minimal xorg.conf
Section "ServerLayout"
Identifier "layout"
Screen 0 "Screen0" 0 0
Option "Xinerama" "0"
EndSection
Section "Monitor"
Identifier "Monitor0"
Vendo
Same problem here with a Dell XPS 15 9560 after Kubuntu 17.10 -> 18.04 upgrade.
Finally solved after lots of retries and reboots. I have now:
Graphics Drivers PPA
(https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
- sudo add-apt-repository ppa:graphics-drivers/ppa
- sudo apt update
- su
Today I got all working, but although prime-select query showed me
"nvidia", nvidia drivers were not loaded and nvidia-settings did not
start. I regret that I decided to run "sudo prime-select intel". Login
worked but it broke suspend mode and my logout/shutdown times are
horrible: 1,5 minutes.
*
I have managed to work nvidia binary drivers version 340.102 with kernel
4.15 with patch https://pastebin.com/raw/fVJVvQy7 , which is mentioned
on https://devtalk.nvidia.com/default/topic/1026911/linux/4-15-rc1
-patches-for-384-98-and-340-104.
My nvidia m720 graphics is working again on Ubuntu 18.
There are two setups where the solution is with my setup (NVIDIA Corporation
GK107M [GeForce GT 750M], laptop with nvidia and intel):
- Use Wayland with nouveau drivers: performance OK.
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1"
(see @tim-tim-richardson++'s remark
Forgot to add:
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1"
(see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when
you install the binary drivers). Performance: very good.
--
You received this bug notification because you are a member of Des
I've upgraded from ubuntu 17.10 to 18.04 and I got the same issue.
When I boot on my laptop with a gtx 1070, I can see on my laptop screen
and my monitor connected through a USB-C adapter the startup console
starting all the modules. On the other hand I have the login screen
working well on my ext
I'm running Ubuntu 18 (although I had exactly the same issue on 16 too)
and instalation of Nvidia drivers works fine, until I choose to change
to Intel graphics card. Then, after rebooting I can't open the Nvidia
GUI anymore. This means I can't use my Hdmi port. Seems like I'll have
to get back to
no fix is released, please change the status. Things are definetly not
fine yet
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
This is not a new problem, and it affects every gdm3-based distro that I have
used. Long story short; if you want to use modeset=1 with nvidia to get rid of
tearing (which would be every linux Optimus user on the planet), gdm3 doesn't
work. No one seems to know why.
Change your display manager
1 - 100 of 161 matches
Mail list logo
