[opensuse] I can't start graphics, NVidia problem (Leap 42.3)
Hi, after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start. Telcontar:~ # startx xauth: file /root/.serverauth.4034 does not exist Using MD5DIR="/var/adm/SuSEconfig/md5"... No changes for /etc/X11/xdm/Xservers No changes for /etc/X11/xdm/xdm-config X.Org X Server 1.18.3 Release Date: 2016-04-04 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts Build Date: 16 October 2017 07:19:15PM Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 4 23:20:36 2018 (==) Using config file: "/etc/X11/xorg.conf" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" log" for additional information.(EE) VGA Arbitration: Cannot restore default device.(EE) Server terminated with error (1). Closing log file.at "/var/log/Xorg.0.xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error Telcontar:~ # rcgpm start Telcontar:~ # /var/log/Xorg.0.log: [ 89.027] X.Org X Server 1.18.3 Release Date: 2016-04-04 [ 89.027] X Protocol Version 11, Revision 0 [ 89.027] Build Operating System: openSUSE SUSE LINUX [ 89.027] Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 [ 89.027] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts [ 89.027] Build Date: 16 October 2017 07:19:15PM [ 89.027] [ 89.027] Current version of pixman: 0.34.0 [ 89.027] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 89.027] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 89.027] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 4 23:20:36 2018 [ 89.027] (==) Using config file: "/etc/X11/xorg.conf" [ 89.028] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 89.028] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 89.031] (==) ServerLayout "Layout0" [ 89.031] (**) |-->Screen "Screen0" (0) [ 89.031] (**) | |-->Monitor "Monitor0" [ 89.031] (**) | |-->Device "Device0" [ 89.031] (**) |-->Input Device "Keyboard0" [ 89.031] (**) |-->Input Device "Mouse0" [ 89.031] (==) Automatically adding devices [ 89.031] (==) Automatically enabling devices [ 89.031] (==) Automatically adding GPU devices [ 89.031] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 89.039] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/cyrillic:unscaled, /usr/share/fonts/misc/sgi:unscaled, /usr/share/fonts/truetype/, built-ins [ 89.039] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 89.039] (**) Extension "XFree86-DGA" is disabled [ 89.039] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 89.039] (WW) Disabling Keyboard0 [ 89.039] (WW) Disabling Mouse0 [ 89.039] (II) Loader magic: 0x80fce0 [ 89.039] (II) Module ABI versions: [ 89.039] X.Org ANSI C Emulation: 0.4 [ 89.039] X.Org ANSI C Emulation: 0.4 [ 89.039] X.Org Video Driver: 20.0 [ 89.039] X.Org XInput driver : 22.1 [ 89.039] X.Org Server Extension : 9.0 [ 89.040] (++) using VT number 1 [ 89.040] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 89.041] (--) PCI:*(0:1:0:0) 10de:0640:1462:1573 rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x00009c00/128, BIOS @ 0x????????/524288 [ 89.041] (II) LoadModule: "glx" [ 89.046] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 89.207] (II) Module glx: vendor="NVIDIA Corporation" [ 89.207] compiled for 4.0.2, module version = 1.0.0 [ 89.207] Module class: X.Org Server Extension [ 89.207] (II) NVIDIA GLX Module 340.104 Thu Sep 14 16:40:42 PDT 2017 [ 89.209] (II) LoadModule: "nvidia" [ 89.209] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 89.221] (II) Module nvidia: vendor="NVIDIA Corporation" [ 89.221] compiled for 4.0.2, module version = 1.0.0 [ 89.221] Module class: X.Org Video Driver [ 89.224] (II) NVIDIA dlloader X Driver 340.104 Thu Sep 14 16:18:31 PDT 2017 [ 89.224] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 89.224] (II) Loading sub module "fb" [ 89.224] (II) LoadModule: "fb" [ 89.225] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 89.226] (II) Module fb: vendor="X.Org Foundation" [ 89.226] compiled for 1.18.3, module version = 1.0.0 [ 89.226] ABI class: X.Org ANSI C Emulation, version 0.4 [ 89.226] (WW) Unresolved symbol: fbGetGCPrivateKey [ 89.226] (II) Loading sub module "wfb" [ 89.226] (II) LoadModule: "wfb" [ 89.227] (II) Loading /usr/lib64/xorg/modules/libwfb.so [ 89.228] (II) Module wfb: vendor="X.Org Foundation" [ 89.228] compiled for 1.18.3, module version = 1.0.0 [ 89.228] ABI class: X.Org ANSI C Emulation, version 0.4 [ 89.228] (II) Loading sub module "ramdac" [ 89.228] (II) LoadModule: "ramdac" [ 89.228] (II) Module "ramdac" already built-in [ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for details. [ 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 89.236] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 89.236] (EE) Maybe that "fbGetGCPrivateKey"? Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice: Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-computeG03-340.104-11.1.x86_64 x11-video-nvidiaG03-340.104-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-glG03-340.104-11.1.x86_64 Telcontar:~ # rpm -qa | grep kernel kernel-source-4.4.104-18.44.1.noarch texlive-l3kernel-doc-2016.122.svn_6512svn41246-25.5.noarch kernel-source-4.4.104-39.1.noarch kernel-docs-4.4.104-39.1.noarch kernel-default-4.4.103-18.41.1.x86_64 kernel-default-4.4.104-39.1.x86_64 kernel-default-devel-4.4.104-39.1.x86_64 kernel-syms-4.4.104-39.1.x86_64 kernel-macros-4.4.104-39.1.noarch kernel-devel-4.4.104-18.44.1.noarch kernel-syms-4.4.104-18.44.1.x86_64 kernel-devel-4.4.104-39.1.noarch texlive-l3kernel-2016.122.svn_6512svn41246-25.5.noarch kernel-default-4.4.104-18.44.1.x86_64 kernel-default-devel-4.4.104-18.44.1.x86_64 kernel-firmware-20170530-14.1.noarch nfs-kernel-server-1.3.0-28.1.x86_64 Telcontar:~ # uname -a Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]:
Hi,
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
[ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for details. [ 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module try the NV...run package. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 00:15, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]:
Hi,
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
[ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for details. [ 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module
try the NV...run package.
I do not want to go that route, the rpm must work. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On 02/04/2018 05:44 PM, Carlos E. R. wrote: Carlos, those still look like 42.2 rpms. I'm still on 42.2 and have: $ uname -a Linux wizard 4.4.104-18.44-default #1 SMP Thu Jan 4 08:07:55 UTC 2018 (05a9de6) x86_64 x86_64 x86_64 GNU/Linux So your kernel devel, etc.. e.g. kernel-devel-4.4.104-18.44.1.noarch Looks a whole lot like 42.2. -- David C. Rankin, J.D.,P.E.
On 2018-02-05 03:17, David C. Rankin wrote:
On 02/04/2018 05:44 PM, Carlos E. R. wrote:
Carlos, those still look like 42.2 rpms. I'm still on 42.2 and have:
$ uname -a Linux wizard 4.4.104-18.44-default #1 SMP Thu Jan 4 08:07:55 UTC 2018 (05a9de6) x86_64 x86_64 x86_64 GNU/Linux
So your kernel devel, etc.. e.g.
kernel-devel-4.4.104-18.44.1.noarch
Looks a whole lot like 42.2.
I know, that looked suspicious and I verified. They are actually similar distro releases. I have at this time: cer@Telcontar:~> rpm -q kernel-default warning: waiting for shared lock on /var/lib/rpm/Packages kernel-default-4.4.103-18.41.1.x86_64 kernel-default-4.4.104-18.44.1.x86_64 kernel-default-4.4.104-39.1.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qi kernel-default | grep Distri warning: waiting for shared lock on /var/lib/rpm/Packages Distribution: openSUSE Leap 42.2 Distribution: openSUSE Leap 42.2 Distribution: openSUSE Leap 42.3 cer@Telcontar:~> The third one is active and it is for 42.3. The other two will be purged as soon as a new kernel comes the update channel, so no issue. I have the same mixture in the other two upgraded machines, no issue there. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 18:45]:
On 2018-02-05 00:15, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]:
Hi,
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
[ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for details. [ 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module
try the NV...run package.
I do not want to go that route, the rpm must work.
well, the rpm is not working, black screen. and you do have an option. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 03:17, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 18:45]:
On 2018-02-05 00:15, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]:
Hi,
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
[ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for details. [ 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module
try the NV...run package.
I do not want to go that route, the rpm must work.
well, the rpm is not working, black screen. and you do have an option.
No, I don't. The rpms have to work, they are intended to work, have worked for years, and must keep working. Something is wrong somewhere and has to be solved. Installing the .run package is surrendering in defeat. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2018-02-05 03:17, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 18:45]:
On 2018-02-05 00:15, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]:
Hi,
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
[ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel [ module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional [ error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for [ details. 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module
try the NV...run package.
I do not want to go that route, the rpm must work.
well, the rpm is not working, black screen. and you do have an option.
No, I don't. The rpms have to work, they are intended to work, have worked for years, and must keep working. Something is wrong somewhere and has to be solved. Installing the .run package is surrendering in defeat.
Carlos, that is not what was meant - the kernel modules still have to be built to match your kernel. This package for instance: nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64.rpm (I don't know which one you use). -- Per Jessen, Zürich (-0.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 08:08, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-05 03:17, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 18:45]:
On 2018-02-05 00:15, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]:
Hi,
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
[ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel [ module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional [ error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for [ details. 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module
try the NV...run package.
I do not want to go that route, the rpm must work.
well, the rpm is not working, black screen. and you do have an option.
No, I don't. The rpms have to work, they are intended to work, have worked for years, and must keep working. Something is wrong somewhere and has to be solved. Installing the .run package is surrendering in defeat.
Carlos, that is not what was meant - the kernel modules still have to be built to match your kernel.
But not by me. By the packager.
This package for instance: nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64.rpm
(I don't know which one you use).
nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 Same one. The correct one. Patrick wants me to uninstall the rpms and use the NVidia.run binary, and I refuse to do that unless there is absolutely no other way. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2018-02-05 08:08, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-05 03:17, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 18:45]:
On 2018-02-05 00:15, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-04-18 17:42]: > Hi, > > after upgrading my desktop machine (DVD offline method) from > 42.2 to 42.3, graphics mode will not start.
> [ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel > [ module. Please see the > [ 89.236] (EE) NVIDIA: system's kernel log for additional > [ error messages and > [ 89.236] (EE) NVIDIA: consult the NVIDIA README for > [ details. 89.236] (EE) No devices detected. > [ 89.236] (EE) > Fatal server error: > [ 89.236] (EE) no screens found(EE) > [ 89.236] (EE)
the nvidia rpm you are using is not building the kernel module
try the NV...run package.
I do not want to go that route, the rpm must work.
well, the rpm is not working, black screen. and you do have an option.
No, I don't. The rpms have to work, they are intended to work, have worked for years, and must keep working. Something is wrong somewhere and has to be solved. Installing the .run package is surrendering in defeat.
Carlos, that is not what was meant - the kernel modules still have to be built to match your kernel.
But not by me. By the packager.
No, the module build happens on your system when you install the package. The packager cannot know which kernel you're running. That's why that package requires gcc and the kernel headers.
nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
Same one. The correct one.
Patrick wants me to uninstall the rpms and use the NVidia.run binary, and I refuse to do that unless there is absolutely no other way.
Right, there should be no need for that. It certainly worked for me last week, except for my disabling the nvidia repo. Btw, nouveau works quite well now. Very few artifacts. -- Per Jessen, Zürich (1.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/02/2018 13:52, Carlos E. R. wrote:
Patrick wants me to uninstall the rpms and use the NVidia.run binary, and I refuse to do that unless there is absolutely no other way.
If you have ever installed the NVidia.run binary in the past it leaves things behind that can cause problems at a later stage. Uninstall the nvidia rpms and revert to nouveau drivers. Then search for anything with the name libnvidia* in your library directories. You can see the other libraries that the run package installs by running it as normal user with the -x option, extract only. Then try the nvidia rpms again. Hope this helps, Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-05 a las 17:56 +0200, Dave Plater escribió:
On 05/02/2018 13:52, Carlos E. R. wrote:
Patrick wants me to uninstall the rpms and use the NVidia.run binary, and I refuse to do that unless there is absolutely no other way.
If you have ever installed the NVidia.run binary in the past it leaves things behind that can cause problems at a later stage. Uninstall the nvidia rpms and revert to nouveau drivers. Then search for anything with the name libnvidia* in your library directories. You can see the other libraries that the run package installs by running it as normal user with the -x option, extract only. Then try the nvidia rpms again.
No, last time I installed the .run was years ago, I have been using the rpms since long.
Hope this helps,
Thanks, but you can see in another post that I got the issue solved, although the real cause is not known. (I reinstalled all of OSS) - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp4lKkACgkQja8UbcUWM1wsqwD+PYu6wd+4y4IweSoH8tZKmg/Y 3RAe9EDc18HC5VRfW1oA/jEnzfNWIHABooCPKkmTQ9aJu/Zg2Hcp5UemppzJ+5dl =NQ/i -----END PGP SIGNATURE-----
Carlos E. R. composed on 2018-02-04 23:39 (UTC+0100):
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts
That spaghetti looks like an invitation for an NVidia driver snafu: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts Why do you need duplication, console=tty0, or proprietary NVidia driver for a mere 1280x1024 tty display (vga=0x31a)? Have you tried using video= instead of vga=, or cleaning up the cmdline to include only a bare minimum? Note that AFAIK, splash=verbose == IOW, default is that for us non-plymouth users, boot console "splash" is verbose with or without splash=, unless =quiet. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 04:16, Felix Miata wrote:
Carlos E. R. composed on 2018-02-04 23:39 (UTC+0100):
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts
That spaghetti looks like an invitation for an NVidia driver snafu:
I corrected that already. It is a bug in YaST upgrade procedure that I have to report, but is not the issue. Now I have: [ 63.857] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap splash=verbose
BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts
Why do you need duplication, console=tty0, or proprietary NVidia driver for a mere 1280x1024 tty display (vga=0x31a)? Have you tried using video= instead of vga=, or cleaning up the cmdline to include only a bare minimum?
Note that AFAIK,
splash=verbose ==
IOW, default is that for us non-plymouth users, boot console "splash" is verbose with or without splash=, unless =quiet.
Blame YaST. The correct line is above, the same one as worked with 42.2 just two days ago since months. Well, except that I must change the uuid by label. Another yast bug. Did the same thing in all my upgrades to 42.3 :-( Still, none of that should affect the NVidia driver. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. composed on 2018-02-05 04:25 (UTC+0100):
Still, none of that should affect the NVidia driver.
Of course it *shouldn't*. Is anything stopping you from checking that maybe something there is? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-04 a las 22:52 -0500, Felix Miata escribió:
Carlos E. R. composed on 2018-02-05 04:25 (UTC+0100):
Still, none of that should affect the NVidia driver.
Of course it *shouldn't*. Is anything stopping you from checking that maybe something there is?
But I tell you, I already mended that line and posted the mended line, the same one I have been using with openSUSE 42.2 in that same partitition for a year. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp31jgACgkQja8UbcUWM1znqgD9E8+eO4+KNsb7eTwA7TrA2+zq G8YzDMFzVCzNuXbJyeQA/jku2RnKjR3BUBokgupaxWNRUS/YfVPpJFB5qbRMOmi0 =Li7P -----END PGP SIGNATURE-----
Carlos E. R. composed on 2018-02-05 04:57 (UTC+0100):
Still, none of that should affect the NVidia driver.
Of course it *shouldn't*. Is anything stopping you from checking that maybe something there is?
But I tell you, I already mended that line and posted the mended line...
Mended line yes, but not same thing as what I asked: "...cleaning up the cmdline to include only a bare minimum?" For testing, none of your cleaned up line should be required. Root= is in the initrd, which means any root= on cmdline if inconsistent with the initrd can serve only to override it. For testing purposes at least, everything you have there AFAIK is entirely optional. IOW, "bare minimum" = "". -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-04 a las 23:08 -0500, Felix Miata escribió:
Carlos E. R. composed on 2018-02-05 04:57 (UTC+0100):
Still, none of that should affect the NVidia driver.
Of course it *shouldn't*. Is anything stopping you from checking that maybe something there is?
But I tell you, I already mended that line and posted the mended line...
Mended line yes, but not same thing as what I asked:
"...cleaning up the cmdline to include only a bare minimum?" For testing, none of your cleaned up line should be required. Root= is in the initrd, which means any root= on cmdline if inconsistent with the initrd can serve only to override it. For testing purposes at least, everything you have there AFAIK is entirely optional. IOW, "bare minimum" = "".
The root= part is absolutely needed, I'm not going to remove it, and it is not inconsistent with the initrd. In fact, what I write there is copied to the initrd, not the other way round. The vga= is also needed, I experimented time ago and was needed. Video= does not work on this machine. Loglevel= and tty= also were needed. Maybe tty=1 instead of 0. But I'm not going to play with those. Doing so might make boot to not work, and reversing to the working status again takes work, booting a rescue systemd and all. Not going there. All that is not related to nvidia, I'm not going to play with things not related to nvidia now. In case it is not clear, I boot to text mode. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp32wAACgkQja8UbcUWM1ysSwD/f8hdBkcSZw/C/czEg3CWy170 voCyiOZdHIT6pXKH7WgBAIcurowyzpjAWvIYEOQcPhPiQRRPEJqMd078vfIXcg3d =a76s -----END PGP SIGNATURE-----
Carlos E. R. composed on 2018-02-05 05:18 (UTC+0100):
The root= part is absolutely needed,
Maybe the proprietary NVidia driver needs it, or Grub2 needs it, but 42.3's Grub Legacy and basesystem/systemd do not. I just booted host gx62b with (in effect, by editing the cmdline on the fly) this grub stanza: title openSUSE 42.3 defkernel root (hd0,17) kernel /boot/vmlinuz initrd /boot/initrd # cat /proc/cmdline # grep RETT /etc/os-release PRETTY_NAME="openSUSE Leap 42.3" #
I'm not going to remove it, and it is not inconsistent with the initrd. In fact, what I write there is copied to the initrd, not the other way round.
I made no conscious implication to do anything that changes menu.cfg. Instead use the e key in the Grub2 runtime menu and check whether I'm right or not.
The vga= is also needed, I experimented time ago and was needed. Video= does not work on this machine.
(Keyword: "was".) For what purpose exactly? Is it similarly necessary while troubleshooting?
Loglevel= and tty= also were needed. Maybe tty=1 instead of 0.
loglevel is used for some troubleshooting purposes, but not AFAIK for any default bootloader stanza. tty= I can't recall ever seeing used. That string is not found in: https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt ...
In case it is not clear, I boot to text mode.
I remember. Maybe that could be part of the problem. Startx works for me on 42.3, but I don't use proprietary drivers on any of my own machines. One of my TW updates just days ago wouldn't start X at all any more. I didn't have time at the time to troubleshoot, and now I don't remember which host. :-p -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 05:44, Felix Miata wrote:
Carlos E. R. composed on 2018-02-05 05:18 (UTC+0100):
The root= part is absolutely needed,
Maybe the proprietary NVidia driver needs it, or Grub2 needs it, but 42.3's Grub Legacy and basesystem/systemd do not. I just booted host gx62b with (in effect, by editing the cmdline on the fly) this grub stanza:
I'm not using grub legacy
title openSUSE 42.3 defkernel root (hd0,17) kernel /boot/vmlinuz initrd /boot/initrd
# cat /proc/cmdline
# grep RETT /etc/os-release PRETTY_NAME="openSUSE Leap 42.3" #
I'm not going to remove it, and it is not inconsistent with the initrd. In fact, what I write there is copied to the initrd, not the other way round.
I made no conscious implication to do anything that changes menu.cfg. Instead use the e key in the Grub2 runtime menu and check whether I'm right or not.
The vga= is also needed, I experimented time ago and was needed. Video= does not work on this machine.
(Keyword: "was".) For what purpose exactly? Is it similarly necessary while troubleshooting?
Loglevel= and tty= also were needed. Maybe tty=1 instead of 0.
loglevel is used for some troubleshooting purposes, but not AFAIK for any default bootloader stanza.
tty= I can't recall ever seeing used. That string is not found in: https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt ...
Ok, I'll try. [...] No difference. startx fails. [ 226.149] X.Org X Server 1.18.3 Release Date: 2016-04-04 [ 226.149] X Protocol Version 11, Revision 0 [ 226.149] Build Operating System: openSUSE SUSE LINUX [ 226.149] Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 [ 226.149] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap [ 226.149] Build Date: 16 October 2017 07:19:15PM [ 226.149] [ 226.149] Current version of pixman: 0.34.0 [ 226.149] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 226.149] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 226.149] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 5 13:27:00 2018 [ 226.150] (==) Using config file: "/etc/X11/xorg.conf" [ 226.150] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 226.150] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 226.153] (==) ServerLayout "Layout0" [ 226.153] (**) |-->Screen "Screen0" (0) [ 226.153] (**) | |-->Monitor "Monitor0" [ 226.153] (**) | |-->Device "Device0" [ 226.153] (**) |-->Input Device "Keyboard0" [ 226.153] (**) |-->Input Device "Mouse0" [ 226.153] (==) Automatically adding devices [ 226.153] (==) Automatically enabling devices [ 226.153] (==) Automatically adding GPU devices [ 226.153] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 226.163] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/cyrillic:unscaled, /usr/share/fonts/misc/sgi:unscaled, /usr/share/fonts/truetype/, built-ins [ 226.163] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 226.163] (**) Extension "XFree86-DGA" is disabled [ 226.163] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 226.163] (WW) Disabling Keyboard0 [ 226.163] (WW) Disabling Mouse0 [ 226.163] (II) Loader magic: 0x80fce0 [ 226.163] (II) Module ABI versions: [ 226.163] X.Org ANSI C Emulation: 0.4 [ 226.163] X.Org Video Driver: 20.0 [ 226.163] X.Org XInput driver : 22.1 [ 226.163] X.Org Server Extension : 9.0 [ 226.164] (++) using VT number 1 [ 226.164] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 226.166] (--) PCI:*(0:1:0:0) 10de:0640:1462:1573 rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x00009c00/128, BIOS @ 0x????????/524288 [ 226.166] (II) LoadModule: "glx" [ 226.171] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 226.332] (II) Module glx: vendor="NVIDIA Corporation" [ 226.332] compiled for 4.0.2, module version = 1.0.0 [ 226.332] Module class: X.Org Server Extension [ 226.332] (II) NVIDIA GLX Module 340.104 Thu Sep 14 16:40:42 PDT 2017 [ 226.334] (II) LoadModule: "nvidia" [ 226.334] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 226.348] (II) Module nvidia: vendor="NVIDIA Corporation" [ 226.348] compiled for 4.0.2, module version = 1.0.0 [ 226.348] Module class: X.Org Video Driver [ 226.350] (II) NVIDIA dlloader X Driver 340.104 Thu Sep 14 16:18:31 PDT 2017 [ 226.350] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 226.350] (II) Loading sub module "fb" [ 226.350] (II) LoadModule: "fb" [ 226.351] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 226.352] (II) Module fb: vendor="X.Org Foundation" [ 226.352] compiled for 1.18.3, module version = 1.0.0 [ 226.352] ABI class: X.Org ANSI C Emulation, version 0.4 [ 226.352] (WW) Unresolved symbol: fbGetGCPrivateKey [ 226.352] (II) Loading sub module "wfb" [ 226.352] (II) LoadModule: "wfb" [ 226.352] (II) Loading /usr/lib64/xorg/modules/libwfb.so [ 226.353] (II) Module wfb: vendor="X.Org Foundation" [ 226.353] compiled for 1.18.3, module version = 1.0.0 [ 226.353] ABI class: X.Org ANSI C Emulation, version 0.4 [ 226.354] (II) Loading sub module "ramdac" [ 226.354] (II) LoadModule: "ramdac" [ 226.354] (II) Module "ramdac" already built-in [ 226.361] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 226.361] (EE) NVIDIA: system's kernel log for additional error messages and [ 226.361] (EE) NVIDIA: consult the NVIDIA README for details. [ 226.361] (EE) No devices detected. [ 226.361] (EE) Fatal server error: [ 226.361] (EE) no screens found(EE) [ 226.361] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 226.361] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 226.362] (EE)
In case it is not clear, I boot to text mode.
I remember. Maybe that could be part of the problem. Startx works for me on 42.3, but I don't use proprietary drivers on any of my own machines. One of my TW updates just days ago wouldn't start X at all any more. I didn't have time at the time to troubleshoot, and now I don't remember which host. :-p
Well, that's the issue, I have used the nvidia driver for many years and I want to keep using it. There are some programs that need it. I have two other partitions with 42.3 and nouveau which work. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. composed on 2018-02-05 13:32 (UTC+0100):
Felix Miata wrote:
Carlos E. R. composed on 2018-02-05 05:18 (UTC+0100):
The root= part is absolutely needed,
Maybe the proprietary NVidia driver needs it, or Grub2 needs it, but 42.3's Grub Legacy and basesystem/systemd do not. I just booted host gx62b with (in effect, by editing the cmdline on the fly) this grub stanza:
I'm not using grub legacy
Irrelevant. Everything on cmdline is normally optional: http://fm.no-ip.com/SS/tty1-s423-1024.jpg
title openSUSE 42.3 defkernel root (hd0,17) kernel /boot/vmlinuz initrd /boot/initrd
# cat /proc/cmdline
# grep RETT /etc/os-release PRETTY_NAME="openSUSE Leap 42.3" # -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-06 01:10, Felix Miata wrote:
Carlos E. R. composed on 2018-02-05 13:32 (UTC+0100):
Felix Miata wrote:
Carlos E. R. composed on 2018-02-05 05:18 (UTC+0100):
The root= part is absolutely needed,
Maybe the proprietary NVidia driver needs it, or Grub2 needs it, but 42.3's Grub Legacy and basesystem/systemd do not. I just booted host gx62b with (in effect, by editing the cmdline on the fly) this grub stanza:
I'm not using grub legacy
Irrelevant. Everything on cmdline is normally optional: http://fm.no-ip.com/SS/tty1-s423-1024.jpg
I tried, and you are right. But I had to leave: linuxefi /boot/vmlinuz-4.14.15-1-default -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-02-06 23:02 (UTC+0100):
Felix Miata wrote:
...Everything on cmdline is normally optional: http://fm.no-ip.com/SS/tty1-s423-1024.jpg
I tried, and you are right. But I had to leave:
linuxefi /boot/vmlinuz-4.14.15-1-default
It appears the kernel cmdline begins after the name of the kernel image that the bootloader must load to get anything useful to happen (strings that show up in /proc/cmdline). :-) -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-04 a las 22:16 -0500, Felix Miata escribió:
Carlos E. R. composed on 2018-02-04 23:39 (UTC+0100):
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.104-39-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/ssd-swap showopts resume=/dev/disk/by-label/ssd-swap splash=verboseshowopts
That spaghetti looks like an invitation for an NVidia driver snafu:
Even funnier is this one in /boot/grub2/device.map, which caused YaST to complain bitterly during the upgrade: (hd1) /dev/sda (hd2) /dev/sdc (hd3) /dev/sdb (hd4) /dev/sdd (hd0) /dev/sde (hd2) /dev/sdb (hd3) /dev/sdc (hd4) /dev/sdd (hd0) /dev/sda (hd1) /dev/sde (hd5) /dev/sdf I have seen the same thing in other 42.3 upgrades. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp31EAACgkQja8UbcUWM1x5CwD/dvTOqd8yfphdl+sdUnk9/LRX XYBPk/RGzb/jtB10lOoA/3fJSaaLPMK7lH56+11uzc+6T3c7ULnfLAgNWwcBCaBZ =8gPB -----END PGP SIGNATURE-----
Carlos E. R. composed on 2018-02-05 04:49 (UTC+0100):
Even funnier is this one in /boot/grub2/device.map, which caused YaST to complain bitterly during the upgrade:
(hd1) /dev/sda (hd2) /dev/sdc (hd3) /dev/sdb (hd4) /dev/sdd (hd0) /dev/sde (hd2) /dev/sdb (hd3) /dev/sdc (hd4) /dev/sdd (hd0) /dev/sda (hd1) /dev/sde (hd5) /dev/sdf
I have seen the same thing in other 42.3 upgrades.
Maybe the bootloader configurators would do better with device.map converted to (hd0) /dev/disk/by-id/ syntax? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-04 a las 22:58 -0500, Felix Miata escribió:
Carlos E. R. composed on 2018-02-05 04:49 (UTC+0100):
Even funnier is this one in /boot/grub2/device.map, which caused YaST to complain bitterly during the upgrade:
(hd1) /dev/sda (hd2) /dev/sdc (hd3) /dev/sdb (hd4) /dev/sdd (hd0) /dev/sde (hd2) /dev/sdb (hd3) /dev/sdc (hd4) /dev/sdd (hd0) /dev/sda (hd1) /dev/sde (hd5) /dev/sdf
I have seen the same thing in other 42.3 upgrades.
Maybe the bootloader configurators would do better with device.map converted to (hd0) /dev/disk/by-id/ syntax?
The actual grub entries use uuids, so the above doesn't really act. Consider this code - not the actual one, but similar: menuentry 'oS 13.1, sdb9 (label a_boot_3)' --id cer-sdb9-001 { insmod part_gpt insmod ext2 set root='hd2,gpt6' if search --no-floppy --fs-uuid --set=root 810339a7-20f4-43b5-8aab-edb051247f81 ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi } The "set root=hd2" entry is superseded a bit later with an uuid; if the uuid the grub entry aborts, so the hd2 part is ignored. Why it has to be there, I do not know. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp32U0ACgkQja8UbcUWM1xiswD/RWnCeXiew+4lTRYc64UAJiDz RNoZYWHv3CyyxhbLPn4A/2sXZTw7v670VUyZiENXmVQjlUOeBf5H+h6/UzxALJAR =TiZC -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-04 a las 23:39 +0100, Carlos E. R. escribió:
after upgrading my desktop machine (DVD offline method) from 42.2 to 42.3, graphics mode will not start.
Telcontar:~ # startx
[ 89.226] (II) Module fb: vendor="X.Org Foundation" [ 89.226] compiled for 1.18.3, module version = 1.0.0 [ 89.226] ABI class: X.Org ANSI C Emulation, version 0.4 [ 89.226] (WW) Unresolved symbol: fbGetGCPrivateKey <========== ??
[ 89.228] compiled for 1.18.3, module version = 1.0.0 [ 89.228] ABI class: X.Org ANSI C Emulation, version 0.4 [ 89.228] (II) Loading sub module "ramdac" [ 89.228] (II) LoadModule: "ramdac" [ 89.228] (II) Module "ramdac" already built-in [ 89.236] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 89.236] (EE) NVIDIA: system's kernel log for additional error messages and [ 89.236] (EE) NVIDIA: consult the NVIDIA README for details. [ 89.236] (EE) No devices detected. [ 89.236] (EE) Fatal server error: [ 89.236] (EE) no screens found(EE) [ 89.236] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 89.236] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 89.236] (EE)
This repeated message in the log might be relevant: <3.6> 2018-02-05 05:25:13 Telcontar console-kit-daemon 4852 - - (process:5168): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed <3.6> 2018-02-05 05:25:23 Telcontar console-kit-daemon 4852 - - (process:5203): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed <3.6> 2018-02-05 05:25:35 Telcontar console-kit-daemon 4852 - - (process:5214): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed <3.6> 2018-02-05 05:25:36 Telcontar console-kit-daemon 4852 - - (process:5216): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed As they seem to appear when I try startx. Google finds hits related to firefox, but that's impossible, there is no X running in that computer now. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp33moACgkQja8UbcUWM1ylywEAoLRlT3bTpS+OSWNZ2+XBVtS5 8oQ14fMHg0veYhgnhVoA+QGgUdq5DGi9d0lwSE9n1NO1156Zeh3h6e9bSMGGfWvT =RV9g -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP
[snip]
Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice:
Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
That looks like the wrong kernel version - 4.4.76_1 ? -- Per Jessen, Zürich (-0.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Carlos E. R. wrote:
Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP
[snip]
Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice:
Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
That looks like the wrong kernel version - 4.4.76_1 ?
The rpms normally have modules for an older kernel version and are 'upgraded' via weak-update links, lux:~ # l /lib/modules/4.14.15-2-default/weak-updates/updates/ total 16 drwxr-xr-x 1 root root 104 Feb 2 21:36 ./ drwxr-xr-x 1 root root 14 Feb 2 21:36 ../ lrwxrwxrwx 1 root root 52 Feb 2 21:36 nvidia-drm.ko -> /lib/modules/4.14.11-1-default/updates/nvidia-drm.ko lrwxrwxrwx 1 root root 48 Feb 2 21:36 nvidia.ko -> /lib/modules/4.14.11-1-default/updates/nvidia.ko Carlos, check if those are there. What happens if you 'modprobe nvidia'? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin wrote:
Per Jessen wrote:
Carlos E. R. wrote:
Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP
[snip]
Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice:
Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
That looks like the wrong kernel version - 4.4.76_1 ?
The rpms normally have modules for an older kernel version and are 'upgraded' via weak-update links,
lux:~ # l /lib/modules/4.14.15-2-default/weak-updates/updates/ total 16 drwxr-xr-x 1 root root 104 Feb 2 21:36 ./ drwxr-xr-x 1 root root 14 Feb 2 21:36 ../ lrwxrwxrwx 1 root root 52 Feb 2 21:36 nvidia-drm.ko -> /lib/modules/4.14.11-1-default/updates/nvidia-drm.ko lrwxrwxrwx 1 root root 48 Feb 2 21:36 nvidia.ko -> /lib/modules/4.14.11-1-default/updates/nvidia.ko
Ah you're right - I even went through just that circus last week :-) -- Per Jessen, Zürich (1.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 12:52, Peter Suetterlin wrote:
Per Jessen wrote:
Carlos E. R. wrote:
Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP
[snip]
Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice:
Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
That looks like the wrong kernel version - 4.4.76_1 ?
zypper lr --details 24 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.3 Repo is correct and there is no newer rpm there, says YaST.
The rpms normally have modules for an older kernel version and are 'upgraded' via weak-update links,
lux:~ # l /lib/modules/4.14.15-2-default/weak-updates/updates/ total 16 drwxr-xr-x 1 root root 104 Feb 2 21:36 ./ drwxr-xr-x 1 root root 14 Feb 2 21:36 ../ lrwxrwxrwx 1 root root 52 Feb 2 21:36 nvidia-drm.ko -> /lib/modules/4.14.11-1-default/updates/nvidia-drm.ko lrwxrwxrwx 1 root root 48 Feb 2 21:36 nvidia.ko -> /lib/modules/4.14.11-1-default/updates/nvidia.ko
Carlos, check if those are there.
Telcontar:/lib/modules # uname -a Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux Telcontar:/lib/modules # Telcontar:/lib/modules # l 4.4.*/weak-updates/updates/ total 8 drwxr-xr-x 2 root root 4096 Feb 4 20:16 ./ drwxr-xr-x 3 root root 4096 Jan 11 01:27 ../ lrwxrwxrwx 1 root root 47 Feb 4 20:15 nvidia.ko -> /lib/modules/4.4.76-1-default/updates/nvidia.ko lrwxrwxrwx 1 root root 51 Feb 4 20:16 nvidia-uvm.ko -> /lib/modules/4.4.76-1-default/updates/nvidia-uvm.ko Telcontar:/lib/modules # Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ ls: cannot access '4.4.104-39-default/weak-updates/updates/': No such file or directory Telcontar:/lib/modules # Well, they are not there!
What happens if you 'modprobe nvidia'?
Telcontar:/lib/modules # modprobe nvidia modprobe: ERROR: could not find module by name='nvidia' modprobe: ERROR: could not insert 'nvidia': Function not implemented Telcontar:/lib/modules # I copy the tree from /lib/modules/4.4.104-18.44-default, and now I have: Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ total 8 drwxr-xr-x 2 root root 4096 Feb 4 20:16 ./ drwxr-xr-x 3 root root 4096 Jan 11 01:27 ../ lrwxrwxrwx 1 root root 47 Feb 5 13:03 nvidia.ko -> /lib/modules/4.4.76-1-default/updates/nvidia.ko lrwxrwxrwx 1 root root 51 Feb 5 13:03 nvidia-uvm.ko -> /lib/modules/4.4.76-1-default/updates/nvidia-uvm.ko Telcontar:/lib/modules # But still: Telcontar:~ # modprobe nvidia modprobe: ERROR: could not find module by name='nvidia' modprobe: ERROR: could not insert 'nvidia': Function not implemented Telcontar:~ # Telcontar:/lib/modules/4.4.104-18.44-default # insmod /lib/modules/4.4.76-1-default/updates/nvidia.ko insmod: ERROR: could not insert module /lib/modules/4.4.76-1-default/updates/nvidia.ko: Invalid module format Telcontar:/lib/modules/4.4.104-18.44-default # Telcontar:/lib/modules/4.4.104-18.44-default # rpm -qf /lib/modules/4.4.76-1-default/updates/nvidia.ko nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 Telcontar:/lib/modules/4.4.104-18.44-default # rpm -qfV /lib/modules/4.4.76-1-default/updates/nvidia.ko Telcontar:/lib/modules/4.4.104-18.44-default # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2018-02-05 12:52, Peter Suetterlin wrote:
Per Jessen wrote:
Carlos E. R. wrote:
Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP
[snip]
Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice:
Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
That looks like the wrong kernel version - 4.4.76_1 ?
zypper lr --details
24 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.3
Funny, in https://en.opensuse.org/SDB:NVIDIA_drivers it is a slightly different URL: http://http.download.nvidia.com/opensuse/leap/42.3 The contents seem to be identical.
What happens if you 'modprobe nvidia'?
Telcontar:/lib/modules # modprobe nvidia modprobe: ERROR: could not find module by name='nvidia' modprobe: ERROR: could not insert 'nvidia': Function not implemented
That should be read as "cannot find nvidia module that matches this kernel version".
Telcontar:/lib/modules #
I copy the tree from /lib/modules/4.4.104-18.44-default, and now I have:
According to your OP, you're running 4.4.104-39 -- Per Jessen, Zürich (1.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 13:25, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-05 12:52, Peter Suetterlin wrote:
Per Jessen wrote:
Carlos E. R. wrote:
Current Operating System: Linux Telcontar 4.4.104-39-default #1 SMP
[snip]
Apparently everything is updated. I'm using the nvidia rpms, and I have reinstalled them twice:
Telcontar:~ # rpm -qa | grep -i nvidia nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64 nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
That looks like the wrong kernel version - 4.4.76_1 ?
zypper lr --details
24 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.3
Funny, in https://en.opensuse.org/SDB:NVIDIA_drivers it is a slightly different URL:
http://http.download.nvidia.com/opensuse/leap/42.3
The contents seem to be identical.
I'll try changing that.
What happens if you 'modprobe nvidia'?
Telcontar:/lib/modules # modprobe nvidia modprobe: ERROR: could not find module by name='nvidia' modprobe: ERROR: could not insert 'nvidia': Function not implemented
That should be read as "cannot find nvidia module that matches this kernel version".
Right.
Telcontar:/lib/modules #
I copy the tree from /lib/modules/4.4.104-18.44-default, and now I have:
According to your OP, you're running 4.4.104-39
Yes. But the nvidia module is for 4.4.76_1-11.1.x86_64, and the symlinks point to it: Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ total 8 drwxr-xr-x 2 root root 4096 Feb 4 20:16 ./ drwxr-xr-x 3 root root 4096 Jan 11 01:27 ../ lrwxrwxrwx 1 root root 47 Feb 5 13:03 nvidia.ko -> /lib/modules/4.4.76-1-default/updates/nvidia.ko lrwxrwxrwx 1 root root 51 Feb 5 13:03 nvidia-uvm.ko -> /lib/modules/4.4.76-1-default/updates/nvidia-uvm.ko Telcontar:/lib/modules # Maybe the links were not in place because the last thing I did yesterday was reinstall the entire OSS repo with YaST (all in this list, update unconditionally). I did not reinstall the nvidia drivers after that. I'm reinstalling them now, again, after changing the repo to point to the URL you wrote. There are no symptoms in YaST that it compiles anything. I look at the /var/log/YaST2/y2log and what I see is: 2018-02-05 13:45:53 <1> Telcontar(5069) [Ruby] clients/sw_single.rb:794 Summary dialog needed 2018-02-05 13:45:53 <2> Telcontar(5069) [Ruby] yast/convert.rb:73 Conversion from integer to float lead to loose precision. 2018-02-05 13:45:53 <2> Telcontar(5069) [Ruby] yast/convert.rb:73 Conversion from integer to float lead to loose precision. 2018-02-05 13:45:53 <1> Telcontar(5069) [Ruby] modules/PackagesUI.rb:635 Installation summary: <p><h3>Installation Successfully Finished</h3></p><p><h3>Packages</h3><ul><li>Updated Packages: 5<BR>nvidia-computeG03, nvidia-gfxG03-kmp-default, nvidia-glG03, nvidia-uvm-gfxG03-kmp-default, x11-video-nvidiaG03</li></ul></p><p><h3>Statistics</h3><ul><li>Elapsed Time: 03:01</li><li>Total Installed Size: 343.78 MiB</li><li>Total Downloaded Size: 70.42 MiB</li></ul></p><p><h3>Details</h3><ul><li><a href="install_log">Installation log</a></li></ul></p> 2018-02-05 13:45:53 <1> Telcontar(5069) [Ruby] modules/PackagesUI.rb:664 Displaying installation report: {"installed"=>0, "updated"=>5, "removed"=>0, "installed_list"=>[], "updated_list"=>["nvidia-gfxG03-kmp-default", "nvidia-uvm-gfxG03-kmp-default", "nvidia-glG03", "nvidia-computeG03", "x11-video-nvidiaG03"], "removed_list"=>[], "downloaded_bytes"=>73836279, "installed_bytes"=>360477836, "time_seconds"=>181.09334326199996, "success"=>true, "remaining"=>[], "install_log"=>"Downloading nvidia-gfxG03-kmp-default (download size 3.56 MiB)\nDownloading nvidia-uvm-gfxG03-kmp-default (download size 3.57 MiB)\nDownloading nvidia-glG03 (download size 27.56 MiB)\nDownloading nvidia-computeG03 (download size 17.41 MiB)\nDownloading x11-video-nvidiaG03 (download size 18.31 MiB)\nInstalling nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64.rpm (installed size 28.03 MiB)\nInstalling nvidia-uvm-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64.rpm (installed size 14.65 MiB)\nInstalling nvidia-glG03-340.104-11.1.x86_64.rpm (installed size 173.38 MiB)\nInstalling nvidia-computeG03-340.104-11.1.x86_64.rpm (installed size 55.74 MiB)\nInstalling x11-video-nvidiaG03-340.104-11.1.x86_64.rpm (installed size 71.99 MiB)\n"} 2018-02-05 13:46:26 <1> Telcontar(5069) [Ruby] modules/PackagesUI.rb:706 input: install_log 2018-02-05 13:46:27 <1> Telcontar(5069) [ui] YPushButton.cc(setFunctionKey):202 Guessing button role YOKButton for YPushButton "OK" at 0x7fe9797675a0 from function key F10 2018-02-05 13:47:03 <1> Telcontar(5069) [Ruby] modules/PackagesUI.rb:706 input: `next 2018-02-05 13:47:03 <1> Telcontar(5069) [Ruby] modules/PackagesUI.rb:746 Installation Summary result: `next I try "startx". Success! So the trick was that: reinstall everything from OSS (because I did not know what was bad), then reinstall again nvidia drivers, in that order. And the culprit was that the upgrade did not upgrade everything and in order. I'll explain why the upgrade did wrong, I have to retrieve the photos from the camera when system is fully running. Basically, the upgrade stopped and finished off when there were still *hundreds* of rpms that were not installed. Lets hop the logs have not rotated -I fear they have :-/ Yes, they have. The upgrade was finished 2018-02-04 18:52:55+01:00, and the earliest yast log is dated 2018-02-04 22:22:36 :-// It is absurd, the yast log rotation is way too aggressive, it only saves 4 MB of compressed logs :-/ -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
* Carlos E. R. <robin.listas@telefonica.net> [02-05-18 08:12]: [...]
I try "startx". Success!
So the trick was that: reinstall everything from OSS (because I did not know what was bad), then reinstall again nvidia drivers, in that order.
And the culprit was that the upgrade did not upgrade everything and in order. I'll explain why the upgrade did wrong, I have to retrieve the photos from the camera when system is fully running.
Basically, the upgrade stopped and finished off when there were still *hundreds* of rpms that were not installed. Lets hop the logs have not rotated -I fear they have :-/
Yes, they have. The upgrade was finished 2018-02-04 18:52:55+01:00, and the earliest yast log is dated 2018-02-04 22:22:36
:-//
It is absurd, the yast log rotation is way too aggressive, it only saves 4 MB of compressed logs :-/
good that you have display now. incorrect rpm. I still install syslog and limit journalctl to 4 hours. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 14:17, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-05-18 08:12]: [...]
I try "startx". Success!
So the trick was that: reinstall everything from OSS (because I did not know what was bad), then reinstall again nvidia drivers, in that order.
And the culprit was that the upgrade did not upgrade everything and in order. I'll explain why the upgrade did wrong, I have to retrieve the photos from the camera when system is fully running.
Basically, the upgrade stopped and finished off when there were still *hundreds* of rpms that were not installed. Lets hop the logs have not rotated -I fear they have :-/
Yes, they have. The upgrade was finished 2018-02-04 18:52:55+01:00, and the earliest yast log is dated 2018-02-04 22:22:36
:-//
It is absurd, the yast log rotation is way too aggressive, it only saves 4 MB of compressed logs :-/
good that you have display now. incorrect rpm.
I still install syslog and limit journalctl to 4 hours.
So I do, but this is not syslog, but YaST own logs in /var/log/YaST2/ that are needed for finding out why this happened. Of course I have full backup of the previous system. I could restore that, and redo the upgrade, but that would be several days of work that I'm not inclined to do. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
There are no symptoms in YaST that it compiles anything. I look at the /var/log/YaST2/y2log and what I see is:
I don't know if the build log is written to any file, but here is part of what is being run when I installed it: http://files.jessen.ch/compiling-nvidia-module-during-install.txt Compiler warnings: http://files.jessen.ch/compiling-nvidia-module-during-install2.txt (that was from "zypper in nvidia-gfxG03-kmp-default"). -- Per Jessen, Zürich (2.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 14:45, Per Jessen wrote:
Carlos E. R. wrote:
There are no symptoms in YaST that it compiles anything. I look at the /var/log/YaST2/y2log and what I see is:
I don't know if the build log is written to any file, but here is part of what is being run when I installed it:
http://files.jessen.ch/compiling-nvidia-module-during-install.txt
Compiler warnings: http://files.jessen.ch/compiling-nvidia-module-during-install2.txt
(that was from "zypper in nvidia-gfxG03-kmp-default").
Ah, you used zypper, me YaST. YaST doesn't print that info, and surprisingly, doesn't log it either. Or it is in another file? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On Monday, February 5, 2018 8:10:35 AM EST Carlos E. R. wrote:
So the trick was that: reinstall everything from OSS (because I did not know what was bad), then reinstall again nvidia drivers, in that order.
And the culprit was that the upgrade did not upgrade everything and in order.
This is the experience I had 2 weeks ago. For an unknown reason the DVD upgrade got confused with the nvidia repository. Initially the module was not built, then it would not load. I thought about your previous thread about corrupted rpm's and how many files you had to fix. That is also essentially what happened here. I deinstalled the nvidia rpm's, did a lot of manual work and then a wholesale forced reinstallation of OSS/Update, then reinstalled from the nvidia repo and all has worked well since. In the future I will deinstall these drivers before upgrade, reboot to ensure nouveau and X are working properly, upgrade, and reinstall from the nvidia repo. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 22:18, Dennis Gallien wrote:
On Monday, February 5, 2018 8:10:35 AM EST Carlos E. R. wrote:
So the trick was that: reinstall everything from OSS (because I did not know what was bad), then reinstall again nvidia drivers, in that order.
And the culprit was that the upgrade did not upgrade everything and in order.
This is the experience I had 2 weeks ago. For an unknown reason the DVD upgrade got confused with the nvidia repository. Initially the module was not built, then it would not load. I thought about your previous thread about corrupted rpm's and how many files you had to fix. That is also essentially what happened here. I deinstalled the nvidia rpm's, did a lot of manual work and then a wholesale forced reinstallation of OSS/Update, then reinstalled from the nvidia repo and all has worked well since. In the future I will deinstall these drivers before upgrade, reboot to ensure nouveau and X are working properly, upgrade, and reinstall from the nvidia repo.
My installation stopped itself when 570 packages remained to be installed, no reason given, and the log has rotated out. <http://susepaste.org/31345231> The "show full log" click is empty. Clicking on the button (not shown) at the bottom right run the finishing scripts. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
zypper lr --details
24 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.3
Repo is correct and there is no newer rpm there, says YaST.
Looks fine indeed.
Telcontar:/lib/modules # uname -a Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux
Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ ls: cannot access '4.4.104-39-default/weak-updates/updates/': No such file or directory
Then it can't load the module indeed :o
I copy the tree from /lib/modules/4.4.104-18.44-default, and now I have:
Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ total 8 drwxr-xr-x 2 root root 4096 Feb 4 20:16 ./ drwxr-xr-x 3 root root 4096 Jan 11 01:27 ../ lrwxrwxrwx 1 root root 47 Feb 5 13:03 nvidia.ko -> /lib/modules/4.4.76-1-default/updates/nvidia.ko lrwxrwxrwx 1 root root 51 Feb 5 13:03 nvidia-uvm.ko -> /lib/modules/4.4.76-1-default/updates/nvidia-uvm.ko Telcontar:/lib/modules #
But still:
Telcontar:~ # modprobe nvidia
Missing the depmod.... Or 'insmod /path/to/nvidia.ko'
Telcontar:/lib/modules/4.4.104-18.44-default # insmod /lib/modules/4.4.76-1-default/updates/nvidia.ko insmod: ERROR: could not insert module /lib/modules/4.4.76-1-default/updates/nvidia.ko: Invalid module format
OK, that's the reason the weak-update links are not there: They are only created if the module loads without errors, which it obviously doesn't. So something's wrong there. Best bet would indeed be to recompile (just) the kernel module yourself against the running kernel... Does the nvidia repo have a bug report address?
Telcontar:/lib/modules/4.4.104-18.44-default #
Telcontar:/lib/modules/4.4.104-18.44-default # rpm -qf /lib/modules/4.4.76-1-default/updates/nvidia.ko nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
Just a stupid question: Does 'zypper se -s nvidia-gfxG03-kmp-default' report it as coming from the nvidia repo, or as System Package? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-05 14:23, Peter Suetterlin wrote:
Carlos E. R. wrote:
zypper lr --details
24 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.3
Repo is correct and there is no newer rpm there, says YaST.
Looks fine indeed.
Telcontar:/lib/modules # uname -a Linux Telcontar 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux
Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ ls: cannot access '4.4.104-39-default/weak-updates/updates/': No such file or directory
Then it can't load the module indeed :o
I copy the tree from /lib/modules/4.4.104-18.44-default, and now I have:
Telcontar:/lib/modules # l 4.4.104-39-default/weak-updates/updates/ total 8 drwxr-xr-x 2 root root 4096 Feb 4 20:16 ./ drwxr-xr-x 3 root root 4096 Jan 11 01:27 ../ lrwxrwxrwx 1 root root 47 Feb 5 13:03 nvidia.ko -> /lib/modules/4.4.76-1-default/updates/nvidia.ko lrwxrwxrwx 1 root root 51 Feb 5 13:03 nvidia-uvm.ko -> /lib/modules/4.4.76-1-default/updates/nvidia-uvm.ko Telcontar:/lib/modules #
But still:
Telcontar:~ # modprobe nvidia
Missing the depmod.... Or 'insmod /path/to/nvidia.ko'
I tried insmod, it failed:
Telcontar:/lib/modules/4.4.104-18.44-default # insmod /lib/modules/4.4.76-1-default/updates/nvidia.ko insmod: ERROR: could not insert module /lib/modules/4.4.76-1-default/updates/nvidia.ko: Invalid module format
OK, that's the reason the weak-update links are not there: They are only created if the module loads without errors, which it obviously doesn't. So something's wrong there. Best bet would indeed be to recompile (just) the kernel module yourself against the running kernel... Does the nvidia repo have a bug report address?
The reason is that yesterday night I reinstalled everything from the OSS repo: YaST, repo view, all in this list, update unconditionally. That solved the hidden problem; but later I should have reinstalled the nvidia rpms, and I forgot, it was 5 AM. The OSS dup deleted the links and nvidia needed modules, I guess.
Telcontar:/lib/modules/4.4.104-18.44-default #
Telcontar:/lib/modules/4.4.104-18.44-default # rpm -qf /lib/modules/4.4.76-1-default/updates/nvidia.ko nvidia-gfxG03-kmp-default-340.104_k4.4.76_1-11.1.x86_64
Just a stupid question: Does 'zypper se -s nvidia-gfxG03-kmp-default' report it as coming from the nvidia repo, or as System Package?
I can still check, I have a backup of that info, I think. Right after the upgrade, I had: Wed Aug 09 2017 Mon Jul 24 2017 nvidia-gfxG03-kmp-default 340.102_k4.4.27_2-18.1 x86_64 obs://build.suse.de/Proprietary:X11:D rivers (none) == Proprietary:X11:Drivers / openSUSE_Leap_42.2 (none) It is the output from this command: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER}\n" | sort | cut --fields="2-" | less -S Notice it was the one from 42.2 - the upgrade failed to update it :-/ Another YaST run removed it, because I find not the string "nvidia" in the corresponding saved query. I can't believe that, so maybe I did a mistake in the query (wrong point in time?) "zypper se -si" did include it: i+ | nvidia-computeG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-glG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-uvm-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers But I forget what the "i+" means :-? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
i+ | nvidia-computeG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-glG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-uvm-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers
But I forget what the "i+" means :-?
I think(!) the '+' means "automatically selected", i.e. by requires. -- Per Jessen, Zürich (2.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Carlos E. R. wrote:
i+ | nvidia-computeG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-glG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-uvm-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers
But I forget what the "i+" means :-?
I think(!) the '+' means "automatically selected", i.e. by requires.
No, contrary: i+ installed by user request -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin wrote:
Per Jessen wrote:
Carlos E. R. wrote:
i+ | nvidia-computeG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-glG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-uvm-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers
But I forget what the "i+" means :-?
I think(!) the '+' means "automatically selected", i.e. by requires.
No, contrary:
i+ installed by user request
Ah right. I was sort of going by the same '+' in 'a+' during an installation. I guess they're not the same kind of '+' :-) -- Per Jessen, Zürich (2.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Ah right. I was sort of going by the same '+' in 'a+' during an installation. I guess they're not the same kind of '+' :-)
Oh, you mean there are positive ones, and negative ones? Have to be careful then! :D and SCNR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-05 a las 15:20 +0100, Per Jessen escribió:
Peter Suetterlin wrote:
Per Jessen wrote:
Carlos E. R. wrote:
i+ | nvidia-computeG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-glG03 | package | 340.104-11.1 | x86_64 | nVidia Graphics Drivers i+ | nvidia-uvm-gfxG03-kmp-default | package | 340.104_k4.4.76_1-11.1 | x86_64 | nVidia Graphics Drivers
But I forget what the "i+" means :-?
I think(!) the '+' means "automatically selected", i.e. by requires.
No, contrary:
i+ installed by user request
Ah right. I was sort of going by the same '+' in 'a+' during an installation. I guess they're not the same kind of '+' :-)
I feared it might mean "not installed, update available". Manually installed makes a lot of sense. Why the rpm list didn't catch these, I do not know. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp4lSMACgkQja8UbcUWM1zkIgD/YSBzLxoLRkcAZ7U8g+/XLgWA s1yy77PyL5RBFtvIRMoA/27coHHqbu2CE0JDMnx6QhKmBkQoL+0EVABsqqBs4Y6+ =nfTE -----END PGP SIGNATURE-----
participants (8)
-
Carlos E. R. -
Dave Plater -
David C. Rankin -
Dennis Gallien -
Felix Miata -
Patrick Shanahan -
Per Jessen -
Peter Suetterlin