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