On 05/05/2021 02.12, -pj wrote:

On 5/4/21 3:26 PM, Carlos E. R. wrote:

...

On 04/05/2021 22.07, -pj wrote:

...

I am wondering if it would be possible to maybe get a couple of pointers on what to do next as far as a bug report. I don't know if it is correct to ask more questions in Bugzilla at this point.

First off the bug report is here: -> https://bugzilla.opensuse.org/show_bug.cgi?id=1185542

My computer was able to boot fine with kernel 5.11.16-1-pae

I was asked to install kernel-default for testing purposes 5.12.1-1.g9bb8944-default which I did. kernel-default failed to boot.

So now 3 kernels are installed/listed in the bootmenu as follows.

1. 5.12.1-1.g9bb8944-default 2. 5.12.0-2-pae 3. 5.12.0-1-pae

kernel 5.11.16-1-pae <- Is now gone. Computer is unable to boot to splash screen with any of the 3 above listed kernels. It makes little/some sense since in /etc/zypp/zypp.conf - line 554 multiversion.kernel the kernel 5.11.16-1-pae must have been removed <- I do not understand though because when I installed KOTD the 5.11.16-1-pae was the running kernel.

Quoting the bug report now as per Comment #7 is as follows: "OK, thanks, then it's a generic problem of 32bit Intel kernel. Feel free to uninstall kernel-default again.

Now, we need more details about the crash. Any chance that you have the relevant kernel Oops or panic in the saved kernel logs? Or if not, try to boot without quiet boot option, and check whether you get the stack traces on screen, and take a picture. That's often helpful as a start.".

What does the kernel Oops or saved kernel logs mean? I have the openSUSE https://en.opensuse.org/openSUSE:Report_a_YaST_bug#How_can_I_setup_network_c...

1. Is this y2logs? What is the best way to retrieve these logs that are needed?

No. Those are the YaST logs.

You first run:

journalctl --list-boots

For this to work, the directory "/var/log/journal/" must exist. If it doesn't, create it, for the next time.

Great..I see here: -> https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref...

"section 11.1:". Which is the best way to perform this step (due to having kernels that are not allowing boot to Splash screen or desktop)? Will I need to create a Rescue-CD perhaps so that I can check for this "/var/log/journal" directory? I do see "C: Command Line  E: Edit Entry" at the bottom left corner of the "boot menu" screen.

It is far simpler than all that: you just boot the kernel that works, and ask journalctl to display the log of one, two, three boots before. The only condition is that "/var/log/journal" directory must exist before you start testing. If it doesn't, as you are already using the machine, just create the directory when the machine is running. After you create the directory you have to attempt to boot the kernel that fails so that it log things - if it gets far enough to write anything. (I see you had to take photos instead)

1. Is it best in my reply here to snip off the remainder (bottom portion) of this message before sending?

Yes :-) -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)