Today I tried to install Tumbleweed on an old computer wich run Windows 10 on a Samssung internal SSD drive and did not work.
After starting the Grub Menu, I selected the install option and nothing happpened. Always went back to the menu. Any idea of what is the problem? The BIOS detects the drive properly
Most likely cause: image was written to USB in a wrong wat, f.e. to a partition instead of the raw device.
Please let know how you created the USB. Also be aware that TW uses grub-bls which does not support dual booting, but that is for later.
I actually burnt a DVD the old fashioned way
“old computer” so maybe legacy/BIOS boot? Then no grub-bls, maybe?
That doesn’t say much. My educated guess is that you burnt the ISO as a file to the DVD instead of burning the ISO image to disk.
Yes, correct
How old is “old”? And is the drive an SATA or a NVME one?
I burnt the image direct to DVD
the disk is SATA not NVME
I burnt the ISO image to a new DVD disk with Brasero, not as a file. And it starts, is when I chose Install in the menu that don’t work
Did you verify the checksum? Could be some download error. I installed tumbleweed a month ago on an old HP pc with 4 GB ram with legacy only. Desktop was probably made in 2005 and was able to install.
OK, so the Samsung disk has nothing to do with the problem (writing this from a 10 yrs old laptop with a SATA Samsung SSD, running Tumbleweed).
Is the PC Legacy BIOS only (made before 2011 or so?) or UEFI capable (possibly with CSM compatibility mode for Legacy booting)? If the latter, is Win10 installed using Legacy or UEFI?
Mount the DVD, open a filemanager and show the content of the DVD
It’s really an old BIOS, and windows 10 was installed using Legacy. The BIOS is from 2010… SATA mode is in AHCI mode.
Yes I did.
So a pure BIOS/Legacy system and the installer after boot should look like this:
(Please note the F1-F8 menu buttons at the bottom)
Choose “Install”, then at the “Loading basic drivers” screen press the “Esc” button to show what is going on and report back the last line shown if it stalls or any errors shown…
I just tested the 20260106 NET installer on a VM mimicking your setup and everything good with the current .iso installer…
2 Likes
Bruno, correct me if I’m wrong:
I mounted 2 isos, and looked at the content
knurpht@Lenovo-P16:~/Install/ISO> LANG=C sudo mount Leap-16.0-offline-installer-x86_64.install.iso /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
knurpht@Lenovo-P16:~/Install/ISO> ls -l /mnt
totaal 10
dr-xr-xr-x 4 root root 2048 29 sep 15:39 boot
dr-xr-xr-x 3 root root 2048 29 sep 15:39 EFI
dr-xr-xr-x 8 root root 4096 29 sep 15:51 install
dr-xr-xr-x 2 root root 2048 29 sep 15:44 LiveOS
knurpht@Lenovo-P16:~/Install/ISO> sudo umount /mnt
knurpht@Lenovo-P16:~/Install/ISO> LANG=C sudo mount openSUSE-Tumbleweed-KDE-Live-x86_64-Current.iso /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
knurpht@Lenovo-P16:~/Install/ISO> ls -l /mnt
totaal 6
drwxr-xr-x 1 root root 2048 31 okt 17:56 boot
drwxr-xr-x 1 root root 2048 31 okt 17:56 EFI
drwxr-xr-x 1 root root 2048 31 okt 18:05 LiveOS
knurpht@Lenovo-P16:~/Install/ISO>
Now further investigations with the Leap 16.0 image
knurpht@Lenovo-P16:~/Install/ISO> LANG=C sudo mount Leap-16.0-offline-installer-x86_64.install.iso /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
knurpht@Lenovo-P16:~/Install/ISO> ls -l /mnt
totaal 10
dr-xr-xr-x 4 root root 2048 29 sep 15:39 boot
dr-xr-xr-x 3 root root 2048 29 sep 15:39 EFI
dr-xr-xr-x 8 root root 4096 29 sep 15:51 install
dr-xr-xr-x 2 root root 2048 29 sep 15:44 LiveOS
knurpht@Lenovo-P16:~/Install/ISO> ls -l /mnt/install/
totaal 19548
-r--r--r-- 2 root root 5467747 29 sep 15:51 ARCHIVES.gz
dr-xr-xr-x 2 root root 2048 27 feb 2024 boot
-r--r--r-- 2 root root 13451041 29 sep 15:50 ChangeLog
-r--r--r-- 2 root root 347 29 sep 15:51 CHECKSUMS
-r--r--r-- 2 root root 827 29 sep 15:51 CHECKSUMS.asc
dr-xr-xr-x 2 root root 2048 29 sep 15:49 docu
-r--r--r-- 2 root root 1680 27 feb 2024 gpg-pubkey-09d9ea69-68595a8c.asc
-r--r--r-- 2 root root 1705 27 feb 2024 gpg-pubkey-25db7ae0-645bae34.asc
-r--r--r-- 2 root root 1968 27 feb 2024 gpg-pubkey-287a0027-682477e3.asc
-r--r--r-- 2 root root 1687 27 feb 2024 gpg-pubkey-29b700a4-62b07e22.asc
-r--r--r-- 2 root root 969 27 feb 2024 gpg-pubkey-39db7c82-66c5d91a.asc
-r--r--r-- 2 root root 1665 27 feb 2024 gpg-pubkey-3fa1d6ce-67c856ee.asc
-r--r--r-- 2 root root 18092 27 feb 2024 GPLv2.txt
-r--r--r-- 2 root root 35147 27 feb 2024 GPLv3.txt
-r--r--r-- 2 root root 37126 29 sep 15:51 INDEX.gz
-r--r--r-- 2 root root 66776 29 sep 15:51 ls-lR.gz
dr-xr-xr-x 2 root root 2048 29 sep 15:51 media.1
dr-xr-xr-x 2 root root 210944 29 sep 15:49 noarch
-r--r--r-- 2 root root 1265 27 feb 2024 README
dr-xr-xr-x 2 root root 6144 29 sep 15:51 repodata
-r--r--r-- 2 root root 99678 27 feb 2024 SUSEgo.ico
-r--r--r-- 2 root root 10247 27 feb 2024 SUSEgo.png
-r--r--r-- 2 root root 11612 27 feb 2024 SUSEgo.svg
dr-xr-xr-x 2 root root 579584 29 sep 15:49 x86_64
knurpht@Lenovo-P16:~/Install/ISO>
Doesn’t this show that the ISO’s content was burned to the DVD, instead of writing the image to disk
Not sure what to look for?
The OP is using a Tumbleweed offline install iso, you are showing a Leap 16 iso (which AFAIK uses Agama and might be somewhat different) and a Live KDE (which acts like the NET installer but has additional packages…).
Anyway the contents are the same whether you burn the image or copy files, the difference is in the first few bytes in the ISO-9660 image that might or might not be copied to the DVD boot space but are not shown by ls -l or any file manager listing the contents anyway.
I would say that if the DVD boots the ISO-9660 bootloader should be there (but I’m not an expert at byte level, sorry).
Now downloading https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso
Will repeat the experiment with that. Might be the YaST based installer is different.