Hi
I recently upgraded from 12.3 to 13.1 via “zypper up”. All was fine until the “nVidia Graphics Drivers” repo provided a new driver version. Then on reboot the system fails to get into windows and drops back to black screen. (Terminal on F1 is available.)
I used the “failsafe” option and got back in, but wonder how to resolve the issue.
Thanks.
Fred
“zypper up”?
You should use “zypper dup” to upgrade to a newer openSUSE version.
All was fine until the “nVidia Graphics Drivers” repo provided a new driver version. Then on reboot the system fails to get into windows and drops back to black screen. (Terminal on F1 is available.)
I used the “failsafe” option and got back in, but wonder how to resolve the issue.
So you installed the nvidia driver from the repo, right?
Please post the output of:
zypper lr -d
rpm -qa | egrep "(nvidia|kernel)"
Maybe you have both G02 and G03 drivers installed and it only worked by luck before the update?
If that’s the case, please remove all nvidia packages completely, and install the correct one again afterwards.
Be sure that you verify the selected packages in YaST, because if you uninstall the packages they won’t get selected again automatically and you will miss a necessary one and/or get the wrong kernel module.
You need those packages:
G02: x11-video-nvidiaG02, nvidia-gfxG02-kmp-desktop (or nvidia-gfxG02-kmp-default if you’re using kernel-default), nvidia-computeG02
G03: x11-video-nvidiaG03, nvidia-gfxG03-kmp-desktop (or nvidia-gfxG03-kmp-default if you’re using kernel-default), nvidia-computeG03, nvidia-glG03 (especially this one won’t be installed automatically if you removed it first, but it is vital for 3d support)
And please also tell which graphics card you have.
Thanks! Yes, I meant zypper dup. And yes, it was the nvidia driver from the 13.1 repo.
1 | Google_Chrome | Google Chrome | No | Yes | 99 | rpm-md | http://dl.google.com/linux/rpm/stable/x86_64 | 2 | Mono_for_Windows | Mono for Windows | No | No | 99 | rpm-md | http://download.mono-project.com/download-stable/openSUSE_11.4 |
3 | nVidia Graphics Drivers | nVidia Graphics Drivers | Yes | Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/13.1/ |
4 | opensuse-guide.org-repo | libdvdcss repository | No | No | 99 | rpm-md | http://opensuse-guide.org/repo/12.2/ |
5 | packman.inode.at-suse | Packman Repository | No | No | 99 | rpm-md | http://packman.inode.at/suse/12.2/ |
6 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/non-oss/ |
7 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/oss/ |
8 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1/ |
9 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1-non-oss/
kernel-desktop-3.7.10-1.28.1.x86_64nvidia-glG03-331.67-26.1.x86_64
kernel-desktop-devel-3.11.10-7.1.x86_64
x11-video-nvidiaG03-331.67-26.1.x86_64
kernel-devel-3.7.10-1.28.1.noarch
nvidia-gfxG03-kmp-desktop-331.38_k3.7.10_1.1-23.1.x86_64
nvidia-gfxG03-kmp-desktop-331.67_k3.11.6_4-26.1.x86_64
nvidia-gfxG03-kmp-desktop-331.49_k3.11.6_4-29.1.x86_64
kernel-desktop-devel-3.7.10-1.28.1.x86_64
kernel-desktop-devel-3.7.10-1.24.1.x86_64
nvidia-computeG03-331.67-26.1.x86_64
nvidia-gfxG03-kmp-desktop-331.49_k3.7.10_1.1-29.1.x86_64
kernel-devel-3.11.10-7.1.noarch
kernel-devel-3.7.10-1.24.1.noarch
kernel-desktop-3.11.10-7.1.x86_64
kernel-desktop-3.7.10-1.24.1.x86_64
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)
Hang on! having said I got the new driver from the SUSE repo, looking at the post I just made, I didn’t did I? It was direct from nvidia. :embarrassed:
Presumably I should remove that repo and add the SUSE one?
No, that’s ok.
There is no (open)SUSE repo for the nvidia driver, the repo is provided by nvidia for openSUSE.
Your packages look ok as well.
Can you please do the following?
I think this contains the failed boot:
X.Org X Server 1.14.3.901 (1.14.4 RC 1)Release Date: 2013-10-26
38.896] X Protocol Version 11, Revision 0
38.896] Build Operating System: openSUSE SUSE LINUX
38.896] Current Operating System: Linux linux-txck 3.7.10-1.28-desktop #1 SMP PREEMPT Mon Feb 3 14:11:15 UTC 2014 (c9a2c6c) x86_64
38.896] Kernel command line: root=/dev/disk/by-id/ata-ST3500418AS_9VMVRK25-part6 resume=/dev/disk/by-id/ata-ST3500418AS_9VMVRK25-part5 splash=silent quiet video=1280x1024 vga=0x31a
38.896] Build Date: 17 April 2014 05:37:34AM
38.897]
38.897] Current version of pixman: 0.30.2
38.897] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
38.897] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
38.897] (==) Log file: "/var/log/Xorg.0.log", Time: Sun May 11 14:54:28 2014
38.897] (==) Using config directory: "/etc/X11/xorg.conf.d"
38.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
38.897] (==) No Layout section. Using the first Screen section.
38.897] (==) No screen section available. Using defaults.
38.897] (**) |-->Screen "Default Screen Section" (0)
38.897] (**) | |-->Monitor "<default monitor>"
38.898] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
38.898] (==) Automatically adding devices
38.898] (==) Automatically enabling devices
38.898] (==) Automatically adding GPU devices
38.964] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
38.964] Entry deleted from font path.
38.965] (==) 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/truetype/,
built-ins
38.965] (==) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules"
38.965] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
38.965] (II) Loader magic: 0x803c20
38.965] (II) Module ABI versions:
38.965] X.Org ANSI C Emulation: 0.4
38.965] X.Org Video Driver: 14.1
38.965] X.Org XInput driver : 19.1
38.965] X.Org Server Extension : 7.0
38.967] (--) PCI:*(0:1:0:0) 10de:0de1:1458:3506 rev 161, Mem @ 0xfb000000/16777216, 0xc8000000/134217728, 0xd6000000/33554432, I/O @ 0x0000af00/128, BIOS @ 0x????????/524288
38.967] Initializing built-in extension Generic Event Extension
38.967] Initializing built-in extension SHAPE
38.967] Initializing built-in extension MIT-SHM
38.967] Initializing built-in extension XInputExtension
38.967] Initializing built-in extension XTEST
38.967] Initializing built-in extension BIG-REQUESTS
38.967] Initializing built-in extension SYNC
38.967] Initializing built-in extension XKEYBOARD
38.967] Initializing built-in extension XC-MISC
38.967] Initializing built-in extension SECURITY
38.967] Initializing built-in extension XINERAMA
38.967] Initializing built-in extension XFIXES
38.967] Initializing built-in extension RENDER
38.967] Initializing built-in extension RANDR
38.967] Initializing built-in extension COMPOSITE
38.967] Initializing built-in extension DAMAGE
38.967] Initializing built-in extension MIT-SCREEN-SAVER
38.967] Initializing built-in extension DOUBLE-BUFFER
38.967] Initializing built-in extension RECORD
38.967] Initializing built-in extension DPMS
38.967] Initializing built-in extension X-Resource
38.967] Initializing built-in extension XVideo
38.967] Initializing built-in extension XVideo-MotionCompensation
38.967] Initializing built-in extension XFree86-VidModeExtension
38.967] Initializing built-in extension XFree86-DGA
38.967] Initializing built-in extension XFree86-DRI
38.967] Initializing built-in extension DRI2
38.967] (II) "glx" will be loaded by default.
38.967] (II) LoadModule: "dri2"
38.967] (II) Module "dri2" already built-in
38.967] (II) LoadModule: "glamoregl"
38.995] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
39.448] (EE) Failed to load /usr/lib64/xorg/modules/libglamoregl.so: /usr/lib64/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context
39.448] (II) UnloadModule: "glamoregl"
39.448] (II) Unloading glamoregl
39.448] (EE) Failed to load module "glamoregl" (loader failed, 7)
39.448] (II) LoadModule: "glx"
39.449] (II) Loading /usr/lib64/xorg/modules/updates/extensions/libglx.so
39.707] (II) Module glx: vendor="NVIDIA Corporation"
39.707] compiled for 4.0.2, module version = 1.0.0
39.707] Module class: X.Org Server Extension
39.707] (II) NVIDIA GLX Module 331.67 Fri Apr 4 11:43:47 PDT 2014
39.711] Loading extension GLX
39.711] (==) Matched nvidia as autoconfigured driver 0
39.711] (==) Matched nouveau as autoconfigured driver 1
39.711] (==) Matched nv as autoconfigured driver 2
39.711] (==) Matched modesetting as autoconfigured driver 3
39.711] (==) Matched fbdev as autoconfigured driver 4
39.711] (==) Matched vesa as autoconfigured driver 5
39.711] (==) Assigned the driver to the xf86ConfigLayout
39.711] (II) LoadModule: "nvidia"
39.711] (II) Loading /usr/lib64/xorg/modules/updates/drivers/nvidia_drv.so
39.712] (II) Module nvidia: vendor="NVIDIA Corporation"
39.712] compiled for 4.0.2, module version = 1.0.0
39.712] Module class: X.Org Video Driver
39.712] (II) LoadModule: "nouveau"
39.713] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
39.713] (II) Module nouveau: vendor="X.Org Foundation"
39.713] compiled for 1.14.3, module version = 1.0.9
39.713] Module class: X.Org Video Driver
39.713] ABI class: X.Org Video Driver, version 14.1
39.713] (II) LoadModule: "nv"
39.714] (II) Loading /usr/lib64/xorg/modules/drivers/nv_drv.so
39.714] (II) Module nv: vendor="X.Org Foundation"
39.714] compiled for 1.14.3, module version = 2.1.20
39.714] Module class: X.Org Video Driver
39.714] ABI class: X.Org Video Driver, version 14.1
39.714] (II) LoadModule: "modesetting"
39.715] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
39.715] (II) Module modesetting: vendor="X.Org Foundation"
39.715] compiled for 1.14.3.901, module version = 0.8.0
39.715] Module class: X.Org Video Driver
39.715] ABI class: X.Org Video Driver, version 14.1
39.715] (II) LoadModule: "fbdev"
39.715] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
39.715] (II) Module fbdev: vendor="X.Org Foundation"
39.715] compiled for 1.14.3, module version = 0.4.3
39.715] Module class: X.Org Video Driver
39.716] ABI class: X.Org Video Driver, version 14.1
39.716] (II) LoadModule: "vesa"
39.716] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
39.716] (II) Module vesa: vendor="X.Org Foundation"
39.716] compiled for 1.14.3, module version = 2.3.3
39.716] Module class: X.Org Video Driver
39.716] ABI class: X.Org Video Driver, version 14.1
39.716] (II) NVIDIA dlloader X Driver 331.67 Fri Apr 4 11:24:40 PDT 2014
39.716] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
39.716] (II) NOUVEAU driver
39.716] (II) NOUVEAU driver for NVIDIA chipset families :
39.716] RIVA TNT (NV04)
39.716] RIVA TNT2 (NV05)
39.716] GeForce 256 (NV10)
39.716] GeForce 2 (NV11, NV15)
39.716] GeForce 4MX (NV17, NV18)
39.716] GeForce 3 (NV20)
39.716] GeForce 4Ti (NV25, NV28)
39.717] GeForce FX (NV3x)
39.717] GeForce 6 (NV4x)
39.717] GeForce 7 (G7x)
39.717] GeForce 8 (G8x)
39.717] GeForce GTX 200 (NVA0)
39.717] GeForce GTX 400 (NVC0)
39.717] (II) NOUVEAU driver
39.717] (II) NOUVEAU driver for NVIDIA chipset families :
39.717] RIVA TNT (NV04)
39.717] RIVA TNT2 (NV05)
39.717] GeForce 256 (NV10)
39.717] GeForce 2 (NV11, NV15)
39.717] GeForce 4MX (NV17, NV18)
39.717] GeForce 3 (NV20)
39.717] GeForce 4Ti (NV25, NV28)
39.717] GeForce FX (NV3x)
39.717] GeForce 6 (NV4x)
39.717] GeForce 7 (G7x)
39.717] GeForce 8 (G8x)
39.717] GeForce GTX 200 (NVA0)
39.717] GeForce GTX 400 (NVC0)
39.717] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
39.717] (II) FBDEV: driver for framebuffer: fbdev
39.717] (II) VESA: driver for VESA chipsets: vesa
39.717] (++) using VT number 7
39.718] (II) Loading sub module "fb"
39.718] (II) LoadModule: "fb"
39.718] (II) Loading /usr/lib64/xorg/modules/libfb.so
39.719] (II) Module fb: vendor="X.Org Foundation"
39.719] compiled for 1.14.3.901, module version = 1.0.0
39.719] ABI class: X.Org ANSI C Emulation, version 0.4
39.719] (WW) Unresolved symbol: fbGetGCPrivateKey
39.719] (II) Loading sub module "wfb"
39.719] (II) LoadModule: "wfb"
39.719] (II) Loading /usr/lib64/xorg/modules/libwfb.so
39.720] (II) Module wfb: vendor="X.Org Foundation"
39.720] compiled for 1.14.3.901, module version = 1.0.0
39.720] ABI class: X.Org ANSI C Emulation, version 0.4
39.720] (II) Loading sub module "ramdac"
39.720] (II) LoadModule: "ramdac"
39.720] (II) Module "ramdac" already built-in
39.720] (WW) Falling back to old probe method for modesetting
39.720] (EE) open /dev/dri/card0: No such file or directory
39.720] (WW) Falling back to old probe method for fbdev
39.720] (II) Loading sub module "fbdevhw"
39.720] (II) LoadModule: "fbdevhw"
39.734] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
39.734] (II) Module fbdevhw: vendor="X.Org Foundation"
39.734] compiled for 1.14.3.901, module version = 0.0.2
39.734] ABI class: X.Org Video Driver, version 14.1
39.734] (WW) Falling back to old probe method for vesa
39.734] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
39.734] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
39.734] (==) NVIDIA(0): RGB weight 888
39.734] (==) NVIDIA(0): Default visual is TrueColor
39.734] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
39.734] (**) NVIDIA(0): Enabling 2D acceleration
39.749] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
39.749] (EE) NVIDIA(0): system's kernel log for additional error messages and
39.749] (EE) NVIDIA(0): consult the NVIDIA README for details.
39.749] (EE) NVIDIA(0): *** Aborting ***
39.749] (EE) NVIDIA(0): Failing initialization of X screen 0
39.749] (II) UnloadModule: "nvidia"
39.749] (II) UnloadSubModule: "wfb"
39.749] (II) UnloadSubModule: "fb"
39.749] (EE) Screen(s) found, but none have a usable configuration.
39.749] (EE)
Fatal server error:
39.749] (EE) no screens found(EE)
39.750] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
39.750] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
39.750] (EE)
39.781] (EE) Server terminated with error (1). Closing log file.
Yes, it does:
39.749] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
39.749] (EE) NVIDIA(0): system's kernel log for additional error messages and
39.749] (EE) NVIDIA(0): consult the NVIDIA README for details.
39.749] (EE) NVIDIA(0): *** Aborting ***
And I think it is caused by this:
38.896] Current Operating System: Linux linux-txck 3.7.10-1.28-desktop #1 SMP PREEMPT Mon Feb 3 14:11:15 UTC 2014 (c9a2c6c) x86_64
You’re still booting the kernel from 12.3 for some reason!
Could you please try to select the 3.11.10 kernel from 13.1 (hidden in “Advanced Options” if you use grub2) in the boot menu?
Normally grub2 should boot the kernel with the highest version (i.e. 3.11.10 in your case), when you select the standard “openSUSE” entry.
And with grub legacy the highest versioned kernel should be default as well.
Not sure why it boots the wrong kernel for you. Have you maybe set a different default entry in YaST->System->Boot Loader->Boot Loader Options?
If booting the 3.11.10 kernel works, I’d recommend you just uninstall the 3.7.10 kernel. (select the kernel-desktop package in YaST->Software Management, and click on “Versions” below the package list to remove specific package versions)
Maybe it worked before the driver update because you still had the kernel module from 12.3 installed I suppose, but it got removed by the update.
Yes, I hadn’t noticed that on boot but there seems to be no reference to 13.1 at all on the boot screen. It seems the upgrade didn’t change my grub options, which all refer to 12.3.
http://i100.photobucket.com/albums/m5/fred_jones2/Boot_zps7740b3ff.jpeg](http://s100.photobucket.com/user/fred_jones2/media/Boot_zps7740b3ff.jpeg.html)
Hm, maybe you edit /boot/grub/menu.list manually, so it doesn’t get changed automatically any more? (you still have the kernel 3.7.10-1.24 in there, which you haven’t even installed)
Change the entries manually, or try to create a new configuration (click on “Other”->“Propose a new configuration” or whatever it’s called).
Do you have a separate /boot partition?
Maybe it wasn’t mounted/there was a problem with it when you did the upgrade, so the new kernel is not there actually?
Better look into /boot which kernels you really have:
ls -l /boot
Well, “ls -l /boot” says:
total 139124
-rw------- 1 root root 512 Mar 24 2011 backup_mbr
lrwxrwxrwx 1 root root 1 May 5 11:49 boot -> .
-rw-r--r-- 1 root root 1484 Oct 18 2013 boot.readme
-rw-r--r-- 1 root root 140316 Feb 3 22:11 config-3.11.10-7-desktop
-rw-r--r-- 1 root root 136097 Dec 5 08:40 config-3.7.10-1.24-desktop
-rw-r--r-- 1 root root 136097 Feb 3 21:49 config-3.7.10-1.28-desktop
-rw-r--r-- 1 root root 0 May 5 11:54 do_purge_kernels
drwxr-xr-x 2 root root 4096 May 5 11:49 grub
drwxr-xr-x 7 root root 4096 May 5 11:58 grub2
lrwxrwxrwx 1 root root 5 Jan 27 19:04 grub2-efi.rpmsave -> grub2
lrwxrwxrwx 1 root root 24 May 9 13:08 initrd -> initrd-3.11.10-7-desktop
-rw------- 1 root root 32641023 May 9 13:08 initrd-3.11.10-7-desktop
-rw------- 1 root root 32627008 May 9 13:08 initrd-3.7.10-1.24-desktop
-rw------- 1 root root 32627568 May 9 13:09 initrd-3.7.10-1.28-desktop
-rw-r--r-- 1 root root 620544 May 5 12:02 message
-rw-r--r-- 1 root root 746538 Feb 3 23:25 symtypes-3.11.10-7-desktop.gz
-rw-r--r-- 1 root root 691683 Dec 5 10:09 symtypes-3.7.10-1.24-desktop.gz
-rw-r--r-- 1 root root 691701 Feb 3 23:28 symtypes-3.7.10-1.28-desktop.gz
-rw-r--r-- 1 root root 262119 Feb 3 23:20 symvers-3.11.10-7-desktop.gz
-rw-r--r-- 1 root root 241475 Dec 5 09:59 symvers-3.7.10-1.24-desktop.gz
-rw-r--r-- 1 root root 241500 Feb 3 23:21 symvers-3.7.10-1.28-desktop.gz
-rw-r--r-- 1 root root 516 Feb 3 23:19 sysctl.conf-3.11.10-7-desktop
-rw-r--r-- 1 root root 516 Dec 5 09:59 sysctl.conf-3.7.10-1.24-desktop
-rw-r--r-- 1 root root 516 Feb 3 23:21 sysctl.conf-3.7.10-1.28-desktop
-rw-r--r-- 1 root root 2681728 Feb 3 23:08 System.map-3.11.10-7-desktop
-rw-r--r-- 1 root root 2531960 Dec 5 09:44 System.map-3.7.10-1.24-desktop
-rw-r--r-- 1 root root 2532218 Feb 3 23:04 System.map-3.7.10-1.28-desktop
-rw-r--r-- 1 root root 6039636 Feb 3 23:19 vmlinux-3.11.10-7-desktop.gz
-rw-r--r-- 1 root root 5815992 Dec 5 09:58 vmlinux-3.7.10-1.24-desktop.gz
-rw-r--r-- 1 root root 5815569 Feb 3 23:20 vmlinux-3.7.10-1.28-desktop.gz
lrwxrwxrwx 1 root root 25 May 5 11:54 vmlinuz -> vmlinuz-3.11.10-7-desktop
-rw-r--r-- 1 root root 5179304 Feb 4 00:52 vmlinuz-3.11.10-7-desktop
-rw-r--r-- 1 root root 5000568 Dec 5 11:22 vmlinuz-3.7.10-1.24-desktop
-rw-r--r-- 1 root root 5000376 Feb 4 01:05 vmlinuz-3.7.10-1.28-desktop
fred@linux-txck:~>
Ok, so the kernels are indeed all there.
Btw, normally only two kernels should be kept installed, so maybe check this as well:
systemctl status purge-kernels
But it could be related to the fact that you are actually booting 3.7.10-1.28, not the latest one.
So please correct your boot menu, or just switch to GRUB2 (also with YaST->Boot Loader), this should just work and leave your old menu.lst in place.
OK. I got:
fred@linux-txck:~> systemctl status purge-kernels
purge-kernels.service - Purge old kernels
Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled)
Active: inactive (dead)
fred@linux-txck:~>
You may by now have gathered I’m not very fluent in all this! 
Presumably then I should just change the first boot entry to point to the 3.11.10-7 kernel. I’d rather not change the bootloader just now until this is sorted.
Well I did that and all seems to be well. Many thanks for your time!
I noticed the following when looking at YAST bootloader options:
http://i100.photobucket.com/albums/m5/fred_jones2/Boot2_zps926e3c76.jpeg](http://s100.photobucket.com/user/fred_jones2/media/Boot2_zps926e3c76.jpeg.html)
It seems I have a non-standard boot partition set, and perhaps this is why it didn’t get updated by the installer.
Ok, you should enable that service, either in YaST->System->Services Manager, or with:
sudo systemctl enable purge-kernels
It will then check on boot whether there are unneeded kernels installed and remove them.
Normally the latest two will be kept, so you can jump back to the previous (working) onw when you have a problem with a kernel update.
Great to hear!
I noticed the following when looking at YAST bootloader options:
http://i100.photobucket.com/albums/m5/fred_jones2/Boot2_zps926e3c76.jpeg](http://s100.photobucket.com/user/fred_jones2/media/Boot2_zps926e3c76.jpeg.html)
It seems I have a non-standard boot partition set, and perhaps this is why it didn’t get updated by the installer.
No.
That only specifies where the boot loader code gets installed. It has absolutely nothing to do with where the kernels and the grub menu are located (this is always /boot).
But you should make sure that that partition mentioned there actually exists. You could have problems when the boot loader is re-installed on certain updates otherwise.
Or just check “Boot from Master Boot Record” or “Boot from Root Partition”, those should work in any case.
(“Boot from Master Boot Record” is not really recommended if you have a multi-boot system though, as you apparently have because of the two Windows entries)
I cannot really tell you why your menu didn’t get updated.
Maybe there’s a flaw in the upgrade procedure, i.e. a bug in the grub package?
Nowadays grub2 is the default, so something like this could easily slip through I suppose…
Or maybe you had an invalid LOADER_TYPE setting in /etc/sysconfig/bootloader. But I guess YaST wouldn’t say “Boot Loader: GRUB” then as well.
Well no matter really, all seems OK now.
Though on reflection the wrong kernel may also have been the reason my wifi printer was no longer found after the update, I had to re-specify its IP address.
I doubt that booting the wrong kernel can cause this…
Where did you have to re-specify the IP address? In the cups configuration?
Or did your network not work in openSUSE?
No, the networking was fine and CUPS seemed happy enough - print jobs were “sent” as usual, and I was told the jobs were complete, but the printer never stirred. So I used “hp-setup” and that went through a “device discovery” process which didn’t find anything until I directed it specifically to the printer’s IP address. Then all was fine. But I fear we’re drifting off topic! 