[opensuse] Leap 15 fails to boot after kernel update today
All, Last line is Mounted filesystem with ordered data mode Opts: null and the boot hangs. Any ideas? Note, booting prior kernel works just fine, so it is something specific to new -19 kernel that came out in the past day or two. This is running in virtualbox. All prior kernel updates have been just fine. This one completed fine, but as soon as it got to the point of invoking wayland, it just locks. Using Yast to remove the latest kernel solves the problem. Booting with the -16 kernel works great. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/18 4:06 AM, David C. Rankin wrote:
Note, booting prior kernel works just fine, so it is something specific to new -19 kernel that came out in the past day or two. This is running in virtualbox.
That's your problem right there. There is an open bug report for problems with "virtualbox" and the new kernel. I'm not using "virtualbox" so I haven't been following closely. It has to do with virtualbox client extensions. The new kernel is fine with KVM clients. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/2018 09:06 AM, Neil Rickert wrote:
That's your problem right there.
There is an open bug report for problems with "virtualbox" and the new kernel.
I'm not using "virtualbox" so I haven't been following closely. It has to do with virtualbox client extensions. The new kernel is fine with KVM clients.
Thanks Neil, That's got to be openSuSE related then. I have both Leap and Arch in Virtualbox and Arch is on 4.18.12 without any problems, so I wasn't thinking kernel about a kernel vbox issue. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Oct 11, 2018 at 03:17:28PM -0500, David C. Rankin wrote:
On 10/11/2018 09:06 AM, Neil Rickert wrote:
That's your problem right there.
There is an open bug report for problems with "virtualbox" and the new kernel.
I'm not using "virtualbox" so I haven't been following closely. It has to do with virtualbox client extensions. The new kernel is fine with KVM clients.
Thanks Neil,
That's got to be openSuSE related then. I have both Leap and Arch in Virtualbox and Arch is on 4.18.12 without any problems, so I wasn't thinking kernel about a kernel vbox issue.
We have released a fixed kernel update for this problem. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/16/2018 04:00 AM, Marcus Meissner wrote:
We have released a fixed kernel update for this problem.
Ciao, Marcus
Thank you Marcus, I can confirm the fix. All is well. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I am still having boot issues. I did the update to the new kernel. The new kernel still freezes when attempting to start x. Prior to the update I only had one kernel image that would boot and now I have none. I would boot into run level 3 and attempt a fix but there is no longer an option line where I could enter init=init 3 at the grub menu. The only thing there is are C (command) and E (edit) options. If anyone could help me get to run level 3 using either of these options I would appreciate it. Really confused by this boot issue. I have two machines set up in a similar manner. Both have 2 500G SSD drives and 1 4T HDD drive. 1 SSD has Windows 10 and the other Leap15. The HDD is a shared drive between them. The computer I am on now has never had an issue. The other has this boot issue. There are two main differences between them. The no issue machine uses the old BIOS boot and the problem machine uses UEFI. The other difference is the problem machine uses an older LCD monitor. It's resolution is 1280x1024 @75Hz but has the smaller 4:3 screen instead of a newer 16:9 screen. They both use Nvidia cards with the proprietary Nvidia drivers. Had no problems until this boot issue started. Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/10/2018 12:19, Dave Smith wrote:
I am still having boot issues. I did the update to the new kernel. The new kernel still freezes when attempting to start x.
Have you tried disabling kernel modesetting (KMS)? Just add nomodeset ... to the kernel boot parameters. Press E on the GRUB boot menu to do this temporarily; if it works, you can edit it into the GRUB settings. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/10/2018 12.19, Dave Smith wrote:
I am still having boot issues. I did the update to the new kernel. The new kernel still freezes when attempting to start x. Prior to the update I only had one kernel image that would boot and now I have none. I would boot into run level 3 and attempt a fix but there is no longer an option line where I could enter init=init 3 at the grub menu. The only thing there is are C (command) and E (edit) options. If anyone could help me get to run level 3 using either of these options I would appreciate it.
Ok, yes, it is "E" you have to use. Then you have to search and find the actual kernel line, which starts with the word "linux". Something similar to this, wrapped: linux /vmlinuz-4.4.155-68-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap splash=verbose Go to the end of the line and write a number 3. Then boot pressing some letter I do not remember. The change is not permanent. Once booted, in YaST software module (it works in text mode too) you have to select to install the old kernel that worked. If you need help on this, I'll expand the instructions. Once installed, you have to add it to a list of non modified packages, do not touch (don't reboot yet). Edit file /etc/zypp/zypp.conf, and search for entry "multiversion.kernels". It will probably say: multiversion.kernels = latest,latest-1,running See the comments above the entry for help. You have to add one entry like: multiversion.kernels = latest,latest-1,running,2.6.32.12-0.7 but using the correct numbers for your case. (Possibly we can use the directory /etc/zypp/multiversion.d instead, somehow, but I do not know how, so do the above instead) Once you do this, you can reboot, and manually select in grub the old kernel. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 20/10/18 4:54 am, Carlos E. R. wrote:
On 19/10/2018 12.19, Dave Smith wrote:
I am still having boot issues. I did the update to the new kernel. The new kernel still freezes when attempting to start x. Prior to the update I only had one kernel image that would boot and now I have none. I would boot into run level 3 and attempt a fix but there is no longer an option line where I could enter init=init 3 at the grub menu. The only thing there is are C (command) and E (edit) options. If anyone could help me get to run level 3 using either of these options I would appreciate it.
Ok, yes, it is "E" you have to use. Then you have to search and find the actual kernel line, which starts with the word "linux". Something similar to this, wrapped:
linux /vmlinuz-4.4.155-68-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap splash=verbose
Go to the end of the line and write a number 3.
One very important qualification! There must be a space BEFORE the '3'. So, for example above, it should be "...splash=verbose 3".
Then boot pressing some letter I do not remember.
To boot press F10.
The change is not permanent.
Once booted, in YaST software module (it works in text mode too) you have to select to install the old kernel that worked. If you need help on this, I'll expand the instructions.
Once installed, you have to add it to a list of non modified packages, do not touch (don't reboot yet).
Edit file /etc/zypp/zypp.conf, and search for entry "multiversion.kernels". It will probably say:
multiversion.kernels = latest,latest-1,running
See the comments above the entry for help. You have to add one entry like:
multiversion.kernels = latest,latest-1,running,2.6.32.12-0.7
but using the correct numbers for your case.
(Possibly we can use the directory /etc/zypp/multiversion.d instead, somehow, but I do not know how, so do the above instead)
Once you do this, you can reboot, and manually select in grub the old kernel.
BC -- "One of the wettest we've ever seen from the standpoint of water". Donald Trump's observation on Hurricane Florence, 19 September 2018. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks everyone for the advise. I will try these suggestions this morning. Just curious why these kernels are not working on this particular machine. On Fri, Oct 19, 2018 at 9:46 PM Basil Chupin <blchupin@iinet.net.au> wrote:
On 20/10/18 4:54 am, Carlos E. R. wrote:
On 19/10/2018 12.19, Dave Smith wrote:
I am still having boot issues. I did the update to the new kernel. The new kernel still freezes when attempting to start x. Prior to the update I only had one kernel image that would boot and now I have none. I would boot into run level 3 and attempt a fix but there is no longer an option line where I could enter init=init 3 at the grub menu. The only thing there is are C (command) and E (edit) options. If anyone could help me get to run level 3 using either of these options I would appreciate it.
Ok, yes, it is "E" you have to use. Then you have to search and find the actual kernel line, which starts with the word "linux". Something similar to this, wrapped:
linux /vmlinuz-4.4.155-68-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap splash=verbose
Go to the end of the line and write a number 3.
One very important qualification! There must be a space BEFORE the '3'. So, for example above, it should be "...splash=verbose 3".
Then boot pressing some letter I do not remember.
To boot press F10.
The change is not permanent.
Once booted, in YaST software module (it works in text mode too) you have to select to install the old kernel that worked. If you need help on this, I'll expand the instructions.
Once installed, you have to add it to a list of non modified packages, do not touch (don't reboot yet).
Edit file /etc/zypp/zypp.conf, and search for entry "multiversion.kernels". It will probably say:
multiversion.kernels = latest,latest-1,running
See the comments above the entry for help. You have to add one entry like:
multiversion.kernels = latest,latest-1,running,2.6.32.12-0.7
but using the correct numbers for your case.
(Possibly we can use the directory /etc/zypp/multiversion.d instead, somehow, but I do not know how, so do the above instead)
Once you do this, you can reboot, and manually select in grub the old kernel.
BC
-- "One of the wettest we've ever seen from the standpoint of water".
Donald Trump's observation on Hurricane Florence, 19 September 2018.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
A final update. Used everyone's suggestions to boot into run level 3. Once there opened yast and did an online update. Noticed both yast and zypper were updated as well as numerous packages. Also noticed no Nvidia packages were updated. Ran yast online update a second time but no new packages were selected for update. After yast was done ran 'zypper up' and updated another 84 packages. Not sure why yast online update did not update these 84 packages. The Nvidia packages were updated this time. Rebooted and all is now back to a normal run level 5 boot. Thanks everyone for the help on this. Dave On Sat, Oct 20, 2018 at 6:18 AM Dave Smith <bushwacker551@gmail.com> wrote:
Thanks everyone for the advise. I will try these suggestions this morning. Just curious why these kernels are not working on this particular machine. On Fri, Oct 19, 2018 at 9:46 PM Basil Chupin <blchupin@iinet.net.au> wrote:
On 20/10/18 4:54 am, Carlos E. R. wrote:
On 19/10/2018 12.19, Dave Smith wrote:
I am still having boot issues. I did the update to the new kernel. The new kernel still freezes when attempting to start x. Prior to the update I only had one kernel image that would boot and now I have none. I would boot into run level 3 and attempt a fix but there is no longer an option line where I could enter init=init 3 at the grub menu. The only thing there is are C (command) and E (edit) options. If anyone could help me get to run level 3 using either of these options I would appreciate it.
Ok, yes, it is "E" you have to use. Then you have to search and find the actual kernel line, which starts with the word "linux". Something similar to this, wrapped:
linux /vmlinuz-4.4.155-68-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap splash=verbose
Go to the end of the line and write a number 3.
One very important qualification! There must be a space BEFORE the '3'. So, for example above, it should be "...splash=verbose 3".
Then boot pressing some letter I do not remember.
To boot press F10.
The change is not permanent.
Once booted, in YaST software module (it works in text mode too) you have to select to install the old kernel that worked. If you need help on this, I'll expand the instructions.
Once installed, you have to add it to a list of non modified packages, do not touch (don't reboot yet).
Edit file /etc/zypp/zypp.conf, and search for entry "multiversion.kernels". It will probably say:
multiversion.kernels = latest,latest-1,running
See the comments above the entry for help. You have to add one entry like:
multiversion.kernels = latest,latest-1,running,2.6.32.12-0.7
but using the correct numbers for your case.
(Possibly we can use the directory /etc/zypp/multiversion.d instead, somehow, but I do not know how, so do the above instead)
Once you do this, you can reboot, and manually select in grub the old kernel.
BC
-- "One of the wettest we've ever seen from the standpoint of water".
Donald Trump's observation on Hurricane Florence, 19 September 2018.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/10/2018 12.22, Dave Smith wrote:
A final update. Used everyone's suggestions to boot into run level 3. Once there opened yast and did an online update. Noticed both yast and zypper were updated as well as numerous packages. Also noticed no Nvidia packages were updated. Ran yast online update a second time but no new packages were selected for update. After yast was done ran 'zypper up' and updated another 84 packages. Not sure why yast online update did not update these 84 packages.
Because YaST does the equivalent to "zypper patch" not "zypper up".
The Nvidia packages were updated this time. Rebooted and all is now back to a normal run level 5 boot.
Thanks everyone for the help on this.
Welcome. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (7)
-
Basil Chupin -
Carlos E. R. -
Dave Smith -
David C. Rankin -
Liam Proven -
Marcus Meissner -
Neil Rickert