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. Then select which of the listed boots you want. Then, request the log for that session: journalctl -b 2 If that is the one you need, then: journalctl -b 2 > somefilename.log and attach it to the bugzilla. Alternatively, you may have "/var/log/boot.msg" for the current boot and "/var/log/boot.omsg" for the previous boot. However, as the boot crashed, there will be nothing. You have instead to remove "quiet" and take a photo with your camera.

2. I do not want to install the operating system again as it will not help the situation at all most likely.

3. Sometimes I do get stack traces on the screen and am not booting with quiet boot option I believe.

4. I decided to take a photo of the "stack traces" and I have attached the image to this email.

Don't. Upload to susepaste.org, or upload to bugzilla. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)

On 5/5/21 1:15 AM, Felix Miata wrote:

-pj composed on 2021-05-04 15:07 (UTC-0500):

...

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. You can boot any live Linux media that has a kernel older than 5.12 to rescue mode from which you can chroot into your installed system.

Would you be able to give me a couple pointers on "chroot" as I am able to get to the tty1:rescue:-# Thanks

Once in, you can install kernel-default-5.11.16 from here: https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar... thus: "zypper in --oldpackage https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.10/standar..."

Once that's installed you can boot that kernel normally to attack the bug's requests and zypp.conf.

On 2021-05-05 10:29, Felix Miata wrote:

-pj composed on 2021-05-05 03:06 (UTC-0500):

...

Would you be able to give me a couple pointers on "chroot" as I am able to get to the tty1:rescue:-#

I'm going to bed. Try a web search

site:opensuse.org chroot

This is a starter for an opensuse-ling. https://en.opensuse.org/Portal:Support_database -- /bengan

Le 05/05/2021 à 12:53, Carlos E. R. a écrit :

mount the system to repair "somewhere":

mount /dev/sdXY /mnt

here /mnt, ok

Then do:

mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev

chroot /mnt

and then you can work on the broken system. You can run zypper or yast (in text mode, don't try graphics).

better cd /mnt then mount --bind /sys sys arow up, back key to remove sys twice, then proc proc same for dev chroot .. this way you donc't have to retype mount --bind of course, the result is the same jdd -- http://dodin.org

On 5/5/21 5:53 AM, Carlos E. R. wrote:

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

...

On 5/5/21 1:15 AM, Felix Miata wrote:

...

-pj composed on 2021-05-04 15:07 (UTC-0500):

...

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. You can boot any live Linux media that has a kernel older than 5.12 to rescue mode from which you can chroot into your installed system.

Would you be able to give me a couple pointers on "chroot" as I am able to get to the tty1:rescue:-#

From memory:

mount the system to repair "somewhere":

   mount /dev/sdXY /mnt

Then do:

   mount --bind /proc /mnt/proc    mount --bind /sys /mnt/sys    mount --bind /dev /mnt/dev

   chroot /mnt

and then you can work on the broken system. You can run zypper or yast (in text mode, don't try graphics).

It appears that kernel modules for wireless networking fail to load during the load process into "rescue mode" Wicked network manager does in fact appear though. That's great information above. Many thanks - getting to be sleeptime here. 1. This entire drive is an encrypted LUKS container with Btrfs filesystem. Proceed with mounting the same way after resting? (mind is a bit tired/foggy right now). 🐸 2. How can I get online in recovery mode since kernel modules are failing to load? (Wicked does succeed though). 3. How can I run zypper in text mode? How can I run yast in text mode? 4. Perhaps I could put together a how to manual at some point of how to do this on a 32 bit system: -> https://en.opensuse.org/Portal:Support_database <- Hopefully kernel 5.12 will have success with 32 bit though. AHA if it does succeed there will be nothing to write about it will just work. :-] -Best Regards

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

On 5/5/21 5:53 AM, Carlos E. R. wrote:

...

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

...

On 5/5/21 1:15 AM, Felix Miata wrote:

...

...

...

...

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. You can boot any live Linux media that has a kernel older than 5.12 to rescue mode from which you can chroot into your installed system.

Would you be able to give me a couple pointers on "chroot" as I am able to get to the tty1:rescue:-#

From memory:

mount the system to repair "somewhere":

   mount /dev/sdXY /mnt

Then do:

   mount --bind /proc /mnt/proc    mount --bind /sys /mnt/sys    mount --bind /dev /mnt/dev

   chroot /mnt

and then you can work on the broken system. You can run zypper or yast

...

(in text mode, don't try graphics).

It appears that kernel modules for wireless networking fail to load during the load process into "rescue mode" Wicked network manager does in fact appear though.

Well, that depends on what you are using as rescue system, some are more complete than others. I thought you would be simply using another kernel in the same system.

That's great information above. Many thanks - getting to be sleeptime here.

Ok, just writing so that you can read this later. That is the beauty of a mail list for support :-)

1. This entire drive is an encrypted LUKS container with Btrfs filesystem. Proceed with mounting the same way after resting? (mind is a bit tired/foggy right now). 🐸

Mounting that is a bit tricky. Best would be that the rescue system has some thing to automate the mounting. For example, my preferred rescue system is the "XFCE Leap 15.x rescue image", but it is 64 bit. You could try this one: http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-Rescue-CD-i6... on a CD or an USB stick. https://en.opensuse.org/Create_installation_USB_stick older instructions https://en.opensuse.org/SDB:Live_USB_stick There are also instructions for Windows or Macs. If that thing boots, just double click on the partition and it will ask for your password.

2. How can I get online in recovery mode since kernel modules are failing to load? (Wicked does succeed though).

Huh. Use another rescue system. Ugh.

3. How can I run zypper in text mode? How can I run yast in text mode?

zypper always runs in text mode. I mean, it CLI, you can use any graphical text terminal. For yast, just type "yast" in the terminal, not yast2. Or type "yast2 --ncurses". All that paragraph assumes you first do "su -" (don't forget the dash).

4. Perhaps I could put together a how to manual at some point of how to

do this on a 32 bit system: ->

Should be the same as for 64 bit, except that 32 bits is dying and people like me are forgetting its nuances :-)

https://en.opensuse.org/Portal:Support_database <- Hopefully kernel 5.12 will have success with 32 bit though. AHA if it does succeed there will

be nothing to write about it will just work. :-]

-Best Regards

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