Hi all,
Very excited today for 15.2.
I wonder now, do the Nvidia Proprietary drivers work on Wayland or do you need to switch back from the Wayland DisplayManager?
No, AFAIK Wayland is still not compatible with Nvidia proprietary drivers: do you really have special needs for both of them? AFAIK KDE is still not fully compatible with Wayland either, at least in the version featured by Leap 15.2.
Maybe specialists have a better insight.
Do you know how to disable Wayland?
I can’t find it in the Sysconfig Editor.
I do need the Nvidia proprietary drivers for Vulcan / gaming.
On a default Gnome install using gdm as display manager where Wayland is enabled by default there is one line to uncomment in:
bruno@LT_B:~> cat /etc/gdm/custom.conf
# GDM configuration storage
#
# Note: settings from /etc/sysconfig/displaymanager have a higher priority
#
[daemon]
InitialSetupEnable=False
# Uncoment the line below to force the login screen to use Xorg
#WaylandEnable=false
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
bruno@LT_B:~>
On KDE I think it is disabled by default, but I might be mistaken.
I found the option WaylandEnable=false in the file /etc/gdm/custom.conf but then the NVidia drivers still won’t work. I was a day off, I thought 15.2 was released today. Yesterday it said 1 Day and now it says 21 hours. Which still is a day.
I’ll wait 
edit: Didn’t refresh the page to see your answer.
I use Gnome indeed.
Since you already have 15.2 installed, doing a “zypper dup” now is likely to bring in the “released” packages, unless there is an emergency update still in the pipe. What you do not find yet are the install media.
If proprietary drivers still don’t work, you should describe your HW and exactly what you do and what you see, so that somebody can help.
If you have an “Optimus” laptop (Intel+Nvidia) it is not unusual to have problems; I remember having to replace gdm with lightdm some time ago to have suse-prime working, but I haven’t checked recently and not on 15.2 yet.
Turning off Wayland in de /etc/gdm file results in a black login window. I see the mouse, but that’s it.
And the new NVidia driver, as the beta you can download from the NVidia site, won’t install at all on 15.2.
Missing dependencies.
This statement is imprecise… 
More correct would be that the nvidia driver is incompatible to other drivers, and therefore needs special support in the Wayland compositor.
Weston (the reference implementation of a Wayland compositor) does support nvidia since a long time, in the form of patches made available by NVidia themselves.
I don’t know about GNOME.
AFAIK KDE is still not fully compatible with Wayland either, at least in the version featured by Leap 15.2.
Actually, the version of KDE Plasma/Kwin (Wayland) included in Leap 15.2 does have explicit support for nvidia. (contributed by an NVidia employee IIANM).
I can’t say how well it works though. (Wayland in general is still having some rough edges, personally I’d still rather consider it experimental)
So I either go to KDE or Weston? Or turn off Wayland and wait for NVidia drivers that do install? Is that correct?
Not really.
Normally, you’d select a desktop session you want to start on the login screen, and that either uses X11 or Wayland.
(unless you want to setup things manually completely, but I can’t help you with that)
If you do want to use Wayland, you’d first need to use a display manager (i.e. login screen) that actually supports starting Wayland sessions.
gdm does (it actually runs the greeter on Wayland by default, but that can be disabled in its config, as mentioned in previous posts), sddm does (in this case the greeter actually runs on X11 only), lightdm maybe too but I don’t know.
Then you’d need to choose a Wayland session on the login screen:
GNOME uses Wayland by default (but there should be a “GNOME on X11” entry too AFAIK)
KDE Plasma 5 actually comes with 3 entries, the normal one uses X11, while there’s also “Wayland” and “Full Wayland”. The latter two only appear if the package plasma5-session-wayland is installed, “Full Wayland” differs from “Wayland” in that it forces GTK/GNOME and Qt/KDE applications to run natively on Wayland while they run under X11 via XWayland with “Wayland” (to avoid bugs in the Wayland implementations of those toolkits).
There maybe others that support/use Wayland, but I have no idea which (I think Enlightenment does, but I’m not sure).
Both GNOME and KDE/Plasma come with their own compositor, I think if you’d want to use Weston, you’d also have to set things up manually (unless there’s a desktop environment that uses Weston as compositor, or maybe Weston itself comes with a session file to show up on the login screen).
Oh, and the NVidia drivers do install (or not) regardless of whether you use X11 or Wayland…
If the driver installation is borked, it will be broken in X11 too.
(and Wayland should of course work with the opensource drivers too, maybe better or worse depending on the hardware and/or the compositor)
And the new NVidia driver, as the beta you can download from the NVidia site, won’t install at all on 15.2.
Missing dependencies.
What missing dependencies?
You need to have a C devel environment and the kernel devel packages installed.
But why don’t you rather use the available packages from the repo?
That should automatically pull in everything that’s necessary, and might also contain patches to make it work with the latest kernels.
https://en.opensuse.org/SDB:NVIDIA_drivers
Ah well, quoting from https://en.wikipedia.org/wiki/Wayland_(display_server_protocol):
Desktop environments
Desktop environments in process of being ported from X to Wayland include GNOME,[95]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-GNOME_wl-95) KDE Plasma 5[96]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-KDE_wl-96) and Enlightenment.[97]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-enlightenment_wl-97)
In November 2015, Enlightenment e20 was announced with full Wayland support.[98]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-e20_wl-98)[48]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-Larabel_2015_e20-48)[99]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-FOSDEM2016_wl-99)
GNOME 3.20 was the first version to have a full Wayland session.[100]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-GNOME_release_plan-100) GNOME 3.22 included much improved Wayland support across GTK, Mutter, and GNOME Shell.[101]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-101) GNOME 3.24 shipped support for the proprietary NVidia drivers under Wayland.[102]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-102)
Wayland support for KDE Plasma was delayed until the release of Plasma 5,[103]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-vizzzion-103) though previously KWin 4.11 got an experimental Wayland support.[104]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-Larabel_2013_kwin-104) The version 5.4 of Plasma was the first with a Wayland session.[105]](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#cite_note-Graesslin_2015-105)
As Leap 15.2 ships with GNOME 3.34, it should indeed work with the proprietary nvidia driver as well (if installed properly).
And for KDE Plasma/kwin’s nvidia support, see e.g.:
https://www.phoronix.com/scan.php?page=news_item&px=EGLStreams-Merged-KWin-5.16
It’s available since version 5.16, Leap 15.2 ships with 5.18.
I forgot to mention (but it is written in that article), to activate NVidia support in kwin, you’d need to set this environment variable:
KWIN_DRM_USE_EGL_STREAMS=1
The easiest way to do it is probably to add this line to /etc/environment, or add a file /etc/profile.d/kwin.sh (the actual name doesn’t matter) with that line.
I first installed the drivers from the repo, they do install but in Gnome Wayland doesn’t work ofc. So I get a terminal instead of GUI. When I disable Wayland in the /etc/gdm/custom.conf I just get a black login screen with a mouse pointer and that’s it. I have a GTX1080 and I was doing everything on 15.1 with it. Including top gaming titles.
As Leap 15.2 ships with GNOME 3.34, it should indeed work with the proprietary nvidia driver as well (if installed properly).
You are the first to say NVidia should work with Wayland. At least, so far I read it doesn’t work. I did install the NVidia drivers through their repo on 15.2, just one day too soon. Perhaps now there is an update. I’ll post the error when I try again.
I guess you should make sure that the nvidia driver works at all (with X11) before you go on about Wayland.
The Xorg log should have a clue.
IIRC, it will be in ~/.local/share/xorg/Xorg.log when using gdm.
You could also switch to a different display manager/login screen for now, until the nvidia driver is installed and working (gdm and sddm use OpenGL which can be broken if the nvidia driver is not installed correctly).
I’d suggest xdm as a start, that should be installed by default, and is so simple that there are high chances that it will work even if there are driver problems. Makes investigating easier…
In particular, it could be a permission problem. GDM runs the X server as unprivilileged user, while others (including xdm) run it as root.
The user might have not enough permissions to access the hardware, which can happen especially with the nvidia driver (because it cannot use the standard methods to gain access due to its proprietary nature).
To switch, run:
sudo update-alternatives --config default-displaymanager
I have a GTX1080 and I was doing everything on 15.1 with it. Including top gaming titles.
And what login screen/desktop environment did you use then?
I provided links…
I did install the NVidia drivers through their repo on 15.2, just one day too soon. Perhaps now there is an update.
I don’t see why the repo’s driver wouldn’t work just because you installed it “one day too soon”…
Did you get an error when trying to install it, or did it succeed and just not work?
Could be that there was indeed an update necessary because of a problem, no idea, I don’t use nvidia (and I haven’t even upgraded to 15.2 yet anyway).
I’ll post the error when I try again.
That would be a good idea.
Although, I’m not sure where exactly the log for gdm will be…
Maybe /var/lib/gdm/.local/share/xorg/Xorg.log ?
You could also switch to a different display manager/login screen for now, until the nvidia driver is installed and working (gdm and sddm use OpenGL which can be broken if the nvidia driver is not installed correctly).
In that case, the log will be located in /var/log/Xorg.0.log.
Alternatively, you could also login to text mode as root, and run “startx”.
That would print the log to the (text mode) console.
FYI, I found a blog post (from a KDE/Plasma developer) about how to get Plasma/Wayland running with the proprietary nvidia driver:
http://blog.davidedmundson.co.uk/blog/running-kwin-wayland-on-nvidia/
It mentions that modesetting support in the nvidia driver needs to be enabled.
This can be done e.g. by adding “nvidia-drm.modeset=1” to the kernel parameters (or creating a file in /etc/modeprobe.d/ with the content “options nvidia-drm modeset=1”).
I don’t know if that also applies to GNOME on Wayland, though it’s probably worth a try in case it doesn’t work out of the box.
Btw, as a side-effect this will also make plymouth’s boot splash work in graphics mode when the nvidia driver is installed…
Ok doing this step by step now. I installed the NVidia G05 driver (which is for the GTX1080). As I understand it, Wayland should still load but perhaps without NVidia? I installed from the repo with no errors. I reboot the machine, and now don’t see the Leap load screen. When I press ESC I see in the top left ^ and a blinking cursor. After a while I see a flash of text all over the screen and the machine now does nothing.
Now I do curl+alt+F1 and I get my login prompt.
I now type update-alternative default-displaymanager and I now see more options than when I type this in Wayland from a terminal. 0 to 5 where 0 is gdm auto mode. 1 is a console, don’t want that. I choose 2 which is also gdm (just to try) and reboot the machine. Same thing happens. Now I turn of Wayland from the /etc/gdm/custom.conf file and now when I reboot I just get a prompt.
I again type update-alternative default-displaymanager and I choose 3, lightdm and I reboot. The same thing happens.
I type journalctl -b and I see in between all the other lines:
systemd-udev: modprobe: ERROR: could not insert ‘nvidia’: Operation not permitted.
startproc: exit status of parent of /user/sbin/lightdm: 1
displaymanager: Starting service lightdm.failed
Failed to start X Display Manager.
Starting Terminate Plymouth Boot Screen...
Again I do update-alternative default-displaymanager and now I choose option 4, xdm and I reboot.
Now I get the login prompt again and the last line of the boot process says: OK Started X Display Manager
Yes, I’m on a console log in.
When I type starts I get:
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
journalctl -b now gives none of the errors as in the previous try.
The /var/log/Xorg.o.log shows:
[FONT=Menlo-Regular] 91.010] (II) LoadModule: "glx"[/FONT]
[FONT=Menlo-Regular] 91.010] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so[/FONT]
[FONT=Menlo-Regular] 91.010] (II) Module glx: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.010] compiled for 1.20.3, module version = 1.0.0[/FONT]
[FONT=Menlo-Regular] 91.010] ABI class: X.Org Server Extension, version 10.0[/FONT]
[FONT=Menlo-Regular] 91.010] (II) Scanning /etc/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers[/FONT]
[FONT=Menlo-Regular] 91.010] (II) Scanning /etc/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched intel as autoconfigured driver 0[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched nvidia as autoconfigured driver 1[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched nouveau as autoconfigured driver 2[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched nv as autoconfigured driver 3[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched modesetting as autoconfigured driver 4[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched fbdev as autoconfigured driver 5[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Matched vesa as autoconfigured driver 6[/FONT]
[FONT=Menlo-Regular] 91.010] (==) Assigned the driver to the xf86ConfigLayout[/FONT]
[FONT=Menlo-Regular] 91.010] (II) LoadModule: "intel"[/FONT]
[FONT=Menlo-Regular] 91.010] (WW) Warning, couldn't open module intel[/FONT]
[FONT=Menlo-Regular] 91.010] (EE) Failed to load module "intel" (module does not exist, 0)[/FONT]
[FONT=Menlo-Regular] 91.010] (II) LoadModule: "nvidia"[/FONT]
[FONT=Menlo-Regular] 91.010] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Module nvidia: vendor="NVIDIA Corporation"[/FONT]
[FONT=Menlo-Regular] 91.011] compiled for 1.6.99.901, module version = 1.0.0[/FONT]
[FONT=Menlo-Regular] 91.011] Module class: X.Org Video Driver[/FONT]
[FONT=Menlo-Regular] 91.011] (II) LoadModule: "nouveau"[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Module nouveau: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.011] compiled for 1.20.3, module version = 1.0.15[/FONT]
[FONT=Menlo-Regular] 91.011] Module class: X.Org Video Driver[/FONT]
[FONT=Menlo-Regular] 91.011] ABI class: X.Org Video Driver, version 24.0[/FONT]
[FONT=Menlo-Regular] 91.011] (II) LoadModule: "nv"[/FONT]
[FONT=Menlo-Regular] 91.011] (WW) Warning, couldn't open module nv[/FONT]
[FONT=Menlo-Regular] 91.011] (EE) Failed to load module "nv" (module does not exist, 0)[/FONT]
[FONT=Menlo-Regular] 91.011] (II) LoadModule: "modesetting"[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Module modesetting: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.011] compiled for 1.20.3, module version = 1.20.3[/FONT]
[FONT=Menlo-Regular] 91.011] Module class: X.Org Video Driver[/FONT]
[FONT=Menlo-Regular] 91.011] ABI class: X.Org Video Driver, version 24.0[/FONT]
[FONT=Menlo-Regular] 91.011] (II) LoadModule: "fbdev"[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Module fbdev: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.011] compiled for 1.20.3, module version = 0.5.0[/FONT]
[FONT=Menlo-Regular] 91.011] Module class: X.Org Video Driver[/FONT]
[FONT=Menlo-Regular] 91.011] ABI class: X.Org Video Driver, version 24.0[/FONT]
[FONT=Menlo-Regular] 91.011] (II) LoadModule: "vesa"[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Module vesa: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.011] compiled for 1.20.3, module version = 2.4.0[/FONT]
[FONT=Menlo-Regular] 91.011] Module class: X.Org Video Driver[/FONT]
[FONT=Menlo-Regular] 91.011] ABI class: X.Org Video Driver, version 24.0[/FONT]
[FONT=Menlo-Regular] 91.011] (II) NVIDIA dlloader X Driver 440.100 Fri May 29 08:21:27 UTC 2020[/FONT]
[FONT=Menlo-Regular] 91.011] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs[/FONT]
[FONT=Menlo-Regular] 91.011] (II) NOUVEAU driver [/FONT]
[FONT=Menlo-Regular] 91.011] (II) NOUVEAU driver for NVIDIA chipset families :[/FONT]
[FONT=Menlo-Regular] 91.011] RIVA TNT (NV04)[/FONT]
[FONT=Menlo-Regular] 91.011] RIVA TNT2 (NV05)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 256 (NV10)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 2 (NV11, NV15)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 4MX (NV17, NV18)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 3 (NV20)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 4Ti (NV25, NV28)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce FX (NV3x)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 6 (NV4x)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 7 (G7x)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce 8 (G8x)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce GTX 200 (NVA0)[/FONT]
[FONT=Menlo-Regular] 91.011] GeForce GTX 400 (NVC0)[/FONT]
[FONT=Menlo-Regular] 91.011] (II) modesetting: Driver for Modesetting Kernel Drivers: kms[/FONT]
[FONT=Menlo-Regular] 91.011] (II) FBDEV: driver for framebuffer: fbdev[/FONT]
[FONT=Menlo-Regular] 91.011] (II) VESA: driver for VESA chipsets: vesa[/FONT]
[FONT=Menlo-Regular] 91.011] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)[/FONT]
[FONT=Menlo-Regular] 91.011] (II) Loading sub module "fb"[/FONT]
[FONT=Menlo-Regular] 91.011] (II) LoadModule: "fb"[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Loading /usr/lib64/xorg/modules/libfb.so[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Module fb: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.012] compiled for 1.20.3, module version = 1.0.0[/FONT]
[FONT=Menlo-Regular] 91.012] ABI class: X.Org ANSI C Emulation, version 0.4[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Loading sub module "wfb"[/FONT]
[FONT=Menlo-Regular] 91.012] (II) LoadModule: "wfb"[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Loading /usr/lib64/xorg/modules/libwfb.so[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Module wfb: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.012] compiled for 1.20.3, module version = 1.0.0[/FONT]
[FONT=Menlo-Regular] 91.012] ABI class: X.Org ANSI C Emulation, version 0.4[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Loading sub module "ramdac"[/FONT]
[FONT=Menlo-Regular] 91.012] (II) LoadModule: "ramdac"[/FONT]
[FONT=Menlo-Regular] 91.012] (II) Module "ramdac" already built-in[/FONT]
[FONT=Menlo-Regular] 91.022] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the[/FONT]
[FONT=Menlo-Regular] 91.022] (EE) NVIDIA: system's kernel log for additional error messages and[/FONT]
[FONT=Menlo-Regular] 91.022] (EE) NVIDIA: consult the NVIDIA README for details.[/FONT]
[FONT=Menlo-Regular] 91.144] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19[/FONT]
[FONT=Menlo-Regular] 91.144] (WW) Falling back to old probe method for modesetting[/FONT]
[FONT=Menlo-Regular] 91.145] (II) modeset(1): using default device[/FONT]
[FONT=Menlo-Regular] 91.145] (WW) Falling back to old probe method for fbdev[/FONT]
[FONT=Menlo-Regular] 91.145] (II) Loading sub module "fbdevhw"[/FONT]
[FONT=Menlo-Regular] 91.145] (II) LoadModule: "fbdevhw"[/FONT]
[FONT=Menlo-Regular] 91.145] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so[/FONT]
[FONT=Menlo-Regular] 91.145] (II) Module fbdevhw: vendor="X.Org Foundation"[/FONT]
[FONT=Menlo-Regular] 91.145] compiled for 1.20.3, module version = 0.0.2[/FONT]
[FONT=Menlo-Regular] 91.145] ABI class: X.Org Video Driver, version 24.0[/FONT]
[FONT=Menlo-Regular] 91.145] (II) FBDEV(2): using default device[/FONT]
[FONT=Menlo-Regular] 91.145] (II) modeset(G0): using drv /dev/dri/card0[/FONT]
[FONT=Menlo-Regular] 91.145] (EE) Screen 0 deleted because of no matching config section.[/FONT]
[FONT=Menlo-Regular] 91.145] (II) UnloadModule: "modesetting"[/FONT]
[FONT=Menlo-Regular] 91.145] (EE) [/FONT]
[FONT=Menlo-Regular]Fatal server error:[/FONT]
[FONT=Menlo-Regular] 91.145] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices[/FONT]
[FONT=Menlo-Regular] 91.146] (EE) [/FONT]
[FONT=Menlo-Regular] 91.146] (EE) [/FONT]
[FONT=Menlo-Regular]Please consult the The X.Org Foundation support [/FONT]
[FONT=Menlo-Regular] at http://wiki.x.org[/FONT]
[FONT=Menlo-Regular] for help. [/FONT]
[FONT=Menlo-Regular] 91.146] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.[/FONT]
[FONT=Menlo-Regular] 91.146] (EE) [/FONT]
[FONT=Menlo-Regular] 91.157] (EE) Server terminated with error (1). Closing log file.[/FONT]
Now I removed the NVidia driver and change the /etc/gdm/custom.conf to load Wayland and I get the boot splash screen for the first time and a GUI/Wayland.
The driver did place a config file in the modprobe dir to blacklist nouveau and this got removed when I removed the NVidia driver.
I’m guessing the modprobe boot error, where it failed to insert ‘nvidia’ is the big bad guy here?
I think I saw this in a file the NVidia driver places in the modprobe dir. The kernel parameter. When I install I again, I’ll check that.
That’s normal, the (graphical) load screen needs modesetting enabled as mentioned (and nvidia doesn’t have it enabled by default.
Nothing new though, you must have seen that with previous distribution versions too. (actually nvidia only supports that since not too long ago in the first place, a year, maybe two)
[FONT=Menlo-Regular] 91.022] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the[/FONT]
[FONT=Menlo-Regular] 91.022] (EE) NVIDIA: system’s kernel log for additional error messages and[/FONT]
[FONT=Menlo-Regular] 91.022] (EE) NVIDIA: consult the NVIDIA README for details.[/FONT]
The nvidia kernel module cannot be loaded, and so the nvidia driver fails.
But the question is why.
Maybe this would give a clue (run with the nvidia driver installed, after X failed to start):
dmesg|grep -i nvidia
Also check if the kernel module is actually installed for the current kernel:
find /lib/modules/ -iname nvidia*
It wasn’t when I last checked a few months ago, and that you didn’t see the boot splash indicates it isn’t.
But as I said, I don’t know if it’s needed for GNOME on Wayland.
Doesn’t matter much though as long as the driver doesn’t work anyway.