Upgrade to Leap 15.0 Starting Problem

I have just done an upgrade from Leap42.3 on my laptop and now the default boot stalls with the Leap logo (V with box n top!)
If I select advanced from boot menu and select a lower kernel number? all is OK.
At present my Kinfocentre tells me I am running kernel 4.4.138-59-default.
Is there something I can do to get the latest kernel to run?
Budge

How did you perform the upgrade? Leap 15.0 doesn’t use kernel 4.4.x, so that suggests an incomplete upgrade perhaps. Show us the output of the following…

zypper lr -d
ls -l /boot/vm*
cat /etc/os-release

Also, tell us about your graphics chipset

/usr/sbin/hwinfo --gfxcard

Hi Deano, thanks for the quick reply. I upgraded using the zypper dup method having updated all and removed all but four repos. I think the problem may be with my graphics setup. Here are the results of your prompts:-

alastair@linux-jqbk:~> zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.

# | Alias               | Name                              | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                               | Service
--+---------------------+-----------------------------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------+--------
1 | repo-non-oss        | openSUSE-Leap-15.0-Non-Oss        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/ |        
2 | repo-oss            | openSUSE-Leap-15.0-Oss            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/     |        
3 | repo-update         | openSUSE-Leap-15.0-Update         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/                |        
4 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/            |        
alastair@linux-jqbk:~> 

alastair@linux-jqbk:~> ls -l /boot/vm*
-rw-r--r-- 1 root root 7997083 May 23 20:54 /boot/vmlinux-4.12.14-lp150.12.4-default.gz
-rw-r--r-- 1 root root 7109007 Jun 18 18:17 /boot/vmlinux-4.4.138-59-default.gz
lrwxrwxrwx 1 root root      34 Jul 16 16:38 /boot/vmlinuz -> vmlinuz-4.12.14-lp150.12.4-default
-rw-r--r-- 1 root root 7033040 May 23 21:26 /boot/vmlinuz-4.12.14-lp150.12.4-default
-rw-r--r-- 1 root root 6192824 Jun 18 19:02 /boot/vmlinuz-4.4.138-59-default
alastair@linux-jqbk:~> 


alastair@linux-jqbk:~> cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.0"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
alastair@linux-jqbk:~> 


Couldn’t get the hwinfo for --gfxcard using cat. Looked at hwinfo file but no clear answer there. Is there another way of finding this.
I am booting using a fall back option in the advanced boot option which offers the older kernel.
The distribution suggests there is an issue and that I use nomodeset. Not sure where to add this instruction.
Hope this helps.

You don’t use ‘cat’ for this. Just execute the hwinfo command as given.

or use lspci eg

/sbin/lspci -nnk|grep '\03' -A3

*Filtered for graphics devices

I am booting using a fall back option in the advanced boot option which offers the older kernel.

Right, I see that now.

The distribution suggests there is an issue and that I use nomodeset. Not sure where to add this instruction.
Hope this helps.

You can do it ‘on the fly’ at the grub screen (which is not persistent)…
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.grub2.html#sec.grub2.menu_change
or via YaST > System > Boot Loader (which will take effect next boot and is persistent)…
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.grub2.html#sec.grub2.yast2.config

Hi Deano,
My mistake. Here is missing info.

alastair@linux-jqbk:~> /usr/sbin/hwinfo --gfxcard
08: PCI 02.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.378]
  Unique ID: _Znp.SaA15gG59q9
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel 3rd Gen Core processor Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0166 "3rd Gen Core processor Graphics Controller"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x21f5 
  Revision: 0x09
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xf1400000-0xf17fffff (rw,non-prefetchable)
  Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
  I/O Ports: 0x7000-0x703f (rw)
  IRQ: 28 (70916 events)
  Module Alias: "pci:v00008086d00000166sv000017AAsd000021F5bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

22: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: VCu0.mkXum+RVN4E
  Parent ID: vSkL.FoMJhW7D6t7
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GK107GLM [Quadro K1000M]"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0ffc "GK107GLM [Quadro K1000M]"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x21f5 
  Revision: 0xa1
  Driver: "nouveau"
  Driver Modules: "drm"
  Memory Range: 0xf0000000-0xf0ffffff (rw,non-prefetchable)
  Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable)
  Memory Range: 0xd0000000-0xd1ffffff (ro,non-prefetchable)
  I/O Ports: 0x6000-0x6fff (rw)
  Memory Range: 0xf1000000-0xf107ffff (ro,non-prefetchable,disabled)
  IRQ: 25 (97 events)
  Module Alias: "pci:v000010DEd00000FFCsv000017AAsd000021F5bc03sc00i00"
  Driver Info #0:
    Driver Status: nouveau is active
    Driver Activation Cmd: "modprobe nouveau"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #7 (PCI bridge)

Primary display adapter: #8
alastair@linux-jqbk:~> 

Will use grub menu method for now as I hope a fix is due.
Many thanks.

Okay, so you have hybrid graphics. Did you have have bumblebee installed previously?

Just in case this post is useful to you…
https://forums.opensuse.org/showthread.php/531327-Anyone-get-Nvidia-Optimus-working-in-Leap-15?p=2873785#post2873785
*The user claimed that installing bumblebee via the X11:Bumblebee repository was the way to go.

I had been on 42.3 and certainly was not aware of any bumblebee installation.
I see that the link refers to 32bit version so will check out the repo site.
Am I right in understanding there will be a fix shortly? Odd that what must be a common problem had not been addressed in beta releases and Tumbleweed.
Many thanks for your help. Will report back in due course.

Hi Deano,
For those that may follow with similar problem, the bumblebee solution in your link above worked.
I followed the commands faithfully and all is well but I confess I was well out of my comfort zone as I didn’t really know what I was doing.

I mentioned a possible fix being in the pipeline and wonder if now I have bumblebee installed the system will not update the kernel or if it does that it will not be used.
Well thats the laptop fixed. Now to another machine I just messed up!
Thanks again,
Budge

Just a few additional hints.

Are you using the discrete Nvidia card? If so, by which method (DRI_PRIME if you are not aware of any Bumblebee install?) Have you uninstalled any proprietary Nvidia drivers before the upgrade?
Is Mesa-dri-nouveau installed? Try uninstalling it if you don’t use discrete graphics.
Maybe “zypper dup” left behind one or more “orphaned” packages, i.e. packages that are no more in Leap 15 repositories? For instance drm-kmp-default? Try uninstalling that package, it is not needed with kernel 4.12.x.

EDIT: Sorry, I didn’t see your last post while I was typing. So PROBLEM SOLVED with bumblebee. If you left the X11 repo enabled, you should have no problems with updates, including those involving a new kernel.

Good to read of your success with this. :slight_smile: