This is not a request for help, but rather information about a curious case in our variety of computer-program combinations.

I'm trying to install Slackware on a Lenovo s205 netbook.
I burn the slackware64-live-15.0.iso image with the
dd if=/home/uly_15.3/Downloads/Dist/slackware64-live-xfce-current.iso of=/dev/sdc bs=1M && sync
command in the openSuse 15.3 environment to a USB flash drive usb.
Not loaded on Lenovo s205, but loaded on another computer.

OK, I'm burning this image using YUMI-2.0.9.4.exe with the GRUB bootloader.
It loads, but does not find the disk image.

I'm trying to write the slackware64-15.0-install-dvd.iso image with the dd command under the same conditions.
The flash drive is connected as /dev/sdc, in the process two windows pop up, as expected, but then two more appear, but already as / dev/sdd and the computer freezes. The system monitor shows 0 CPU usage.

And the most interesting, under all the same conditions, the salixlive64-xfce-15.0.iso image is recorded by dd and launched without problems.

I can only add.
With YUMI-exFAT-1.0.0.9 I was able to start downloading slackware64-live-15.0.iso. It ended with "Kernel panic".
I'm just wondering why the Slackware clone boots without problems, but Slackware itself doesn't?

Just a side note: Slackware-current does not means the latest fanciest coolest <beep> yeah! Slackware, but it's the development tree of Slackware, which may or may not work at random times.

Using Slackware-current means that you signup as beta-tester of Slackware and you assume any damages may come, including but not only an alien invasion or your cat eating your dog at dinner. It's supposed to assume that you fix everything yourself, no questions asked, and eventually to report back, the useful suggestions being appreciated.

Seems like your coup of tea? Nope? Then I strongly recommend you to use the latest Slackware 15.0 and to avoid the word "-current" like a devil the churches.

1 members found this post helpful.

@LuckyCyborg
Thanks, it's not about "-current"

The very first thing is that in the Linux community, no one owes anything to anyone.
Therefore, I have no complaints.

Second. With today's variety of computer hardware, it is almost impossible to test all combinations. My problem with Lenovo s205 is apparently caused by the peculiarities of its BIOS.
By the way, I have seen cases when a distribution clone is installed with less problems before.

Regards.

1 members found this post helpful.

Did you try to mount the slackware install dvd iso in open suse, then copy its content to an empty exFat formated usb flash drive?

No, why?
As far as I understand, you need a bootloader, it will be written by the dd command or a third-party multi-boot program, ventoy, for example, or YUMI-exFAT.

The bootloader is in the EFI dir in install dvd (for efi bios)
Just try it, copy all dvd content into usb key (exfat formated which is default format if you didn't reformat it) then boot from usb key (using bios boot menu, F8 or other depending on bios)

@keefaz

Thank you, I'll try, but tomorrow.

Try cat instead.

Trying to open slackware64-15.0-install-dvd.iso and copy to flash drive.
Part of the files with the message "cannot copy ...".
When you try to boot, the flash drive is selected from the menu, tries to read something and goes to the boot menu from the hard drive.

And trying to cat as root, with user rights is the same.

Attached Thumbnails

   

I don't know what happened but this is not the slackware directories structure

for mounting dvd, try (as root):
then copy all from /mnt/dvd in your usb key

in terminal, this would be something like

Thank you.
Everything is copied except for symbolic links.
Terminal output "unable to create symbolic link... Operation not allowed."
Does not boot, goes to the hard disk menu.

Attached Thumbnails

 

When you reboot with the usb key connected, you do fn + F12 keys multiple times, then you goes to bios boot menu?
Do you see the usb key entry here?

Hmm. Maybe you have a dying USB stick (or a 2GB stick pretending to be 32GB). I don't get that error after a successful imaging run. As of today, salixlive64-xfce-15.0.iso is 1.4GB and slackware64-15.0-install-dvd.iso is 3.5GB. I'd try alternative USB sticks at this point.

Yes, to boot from a flash drive, I need to press Fn + F11, then a menu appears with disks and a flash drive, incl.

@SW64
The thing is that on another computer, the same flash drive with the slackware image recorded by the dd command loads without problems.
And on this netbook only salixlive.