From kernel panic to segmentation fault

Hi

What a journey, no dragons to slay on the way, but still there were dangers.

After receiving two personal messages in another forum, which upset me (yeah I’m a delicate flower) I removed the distro on this old HP, and will want to ditto on my main Lenovo Laptop.

So I added some entries, and ISO files to an external drive with existing Ventoy on.

After a dozen or more failed installs, I made a single USB with 15.6 NET install iso, and managed to get a kernel panic, so that was actually real progress.
Nevertheless it still has upwards of a HUNDRED failed package installs, the first and most common among all the attempts was CA-Certificates, closely followed by python3.

Choosing the alternate recovery mode and Ctrl D a desktop booted. Massive help was needed with the Wi-Fi internal mechanism, and suited and booted I decided to do a clean install to remove the problem kernel panic.

I opted to add 15.4 main and net to the Vento

It is not advised to use Ventoy for installation of openSUSE. Ventoy is known for altering the installation parameters and media, resulting in a broken or not even bootable system. The forum is full of reports of broken systems because of Ventoy.
Latest report: Installation failure , only boots into rescue mode

Recommendation not to use Ventoy:
https://en.opensuse.org/Create_installation_USB_stick#Ventoy

1 Like

My impression is that you are making it too difficult for yourself. Just stick with one supported (thus not Leap 15.4) installation ISO, copied in a supported way (thus not Ventoy) on an USB “sticky” and install from it.

Then observe (make notes!) what you do during the installation and when stuck or having problems start a topic here with precise information on what you do, what you expect to get and what happened instead.

Hi

Just to clarify, a single stand-alone USB with the net install version of 15.6 FAILED repeatedly, just like the Ventoy one.

In over 25 years of installing Linux Distro’s (started with Caldera and then SuSE 6.0) this has been the most repeatedly failed attempts ever.

If a NET install fails because of failed package installs, the most logic conclusion would be that your internet connection or the mirror is bad. So the best approach would be to download the full installation ISO (even if it takes long bc of the bad internet connection). But you will be able to verify the installation media via its checksum. This is the most important step which should never be skipped. With the verified full installation media you will have the chance to install the distribution.

Well, this is OpenChat, thus we just chat a bit to and fro.

But I nevertheless ask:

Any threads in the technical Install/Boot/Login section of these forums where people were apparently not able to help you repeatedly?

Hi

What I did was revert to a DVD and internet searches of old topics within the forums on an alternate laptop.

I have never understood HOW2 verify a download, and since I used more than 1 download type I hoped all was well.

Thanks for that tip.

I now have some insight on checksums …

I downloaded files from the openSuSE site.

openSUSE-Tumbleweed-DVD-x86_64-Snapshot20241018-Media.iso.sha256
openSUSE-Tumbleweed-DVD-x86_64-Snapshot20241018-Media.iso

Already having gtkhash installed (sudo zypper install gtkhash hopefully), I could then proceed to verify said ISO files as original, genuine and untampered, like this …

Open gtkhash and navigate to your downloaded ISO and select it.
Then navigate and examine/view the contents of
openSUSE-Tumbleweed-DVD-x86_64-Snapshot20241018-Media.iso.sha256

AS it is a TXT you should see something like this at the LH side …
0bf5e672b161d075ec9ec5d38d226c1a26299216df83779d126bd8fca6723e70

Copy and paste the string into gtkhash ‘Check’ entry box, so that the File and Check lines are filled in with matching file references, Press the HASH option, and within 10 seconds I got 2 green lights.

NB: There is a W10 way, but it is long and winding in comparison.

You can teach an old dog new tricks, so thanks for the prompt.

@clive open a terminal sha256sum -c openSUSE...iso.sha256 :wink:

Hi

Well malcolmlewis I aint as green as I am cabbage looking…

W10 / 11 is where a lot of people will be starting out so …

Windows 10 PowerShell and LibreOffice Calc & Writer to make a HASH of IT.

PS C:>get-filehash and enter the path to the ISO file.

PS C:> get-filehash

cmdlet Get-FileHash at command pipeline position 1
Supply values for the following parameters:
Path[0]: U:\Downloads\openSUSE-Leap-15.6-DVD-x86_64-Build710.3-Media.iso
Path[1]:

Algorithm Hash Path


SHA256 A74D4072E639C75CA127DF3D869C1E57BCC44A093A969550F348A3EAD561FE4F U:\Downloads\openSUSE-Leap-15.6-DVD-x86_64-Build710.3-Media.iso

PS C:> “A74D4072E639C75CA127DF3D869C1E57BCC44A093A969550F348A3EAD561FE4F”.ToLower()
a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f You can use LibreOffice Writer to Convert to lower case of course.

Open the openSUSE-Leap-15.6-DVD-x86_64-Media.iso.sha256 in Writer, copy & paste the checksum into cell A1 of Calc,
then the powershell version into cellA2. =IF(A1=A2,“YES”,“NO”)

a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f
a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f
YES

You may actually see (probably) that it matches without the formula being applied.

Linux Command Line and LibreOffice Calc & Writer to make a HASH of IT.

$ sha256sum and enter the path to the ISO file.

$ sha256sum /mnt/UTILarea/DOWNLOADS/openSUSE-Leap-15.6-DVD-x86_64-Build710.3-Media.iso
a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f /mnt/UTIL….LOADS/openSUSE-Leap-15.6-DVD-x86_64-Build710.3-Media.iso

a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f openSUSE-Leap-15.6-DVD-x86_64-Media.iso

Open the openSUSE-Leap-15.6-DVD-x86_64-Media.iso.sha256 in Writer, copy & paste the checksum into cell A1 of Calc,
then the linux command line version into cellA2. =IF(A1=A2,“YES”,“NO”)

a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f
a74d4072e639c75ca127df3d869c1e57bcc44a093a969550f348a3ead561fe4f
YES

You may actually see (probably) that it matches without the formula being applied.

So I did learn, thanks.
And I missed of the -c switch from the sha256sum, so now I gotta go and learn some more.