[SOLVED] USB flashdrive made from Slackware15.iso will not boot
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
USB flashdrive made from Slackware15.iso will not boot
I'm trying to install Slackware15 on a new computer. I've downloaded the .iso and wrote it to a USB stick. The system will not boot from it.
Things I've done: used Rufus and BalenaEtcher to write the USB in DD and HybridISO mode. Neither are bootable.
I've wrote usbimg.sys to a different usb drive and that at least loads elilo but pressing enter only displays loading kernel huge.s.....done , loading intitrd img .....done and then it hangs there, forever.
I downloaded a ubuntu iso to a third usb flash drive and it boots just fine. What am I missing? How do I make the slackeware 15 usb stick bootable?
Note I don't have a working slackware system right now so I can't follow alienbob's instructions either.
Hello dalgrim and welcome to Slackware. I wonder is your PC new enough to support UEFI boot or Legacy MBR only? With that in mind are you using an F-Key to display boot order menu? ... and are you selecting UEFI USB if you have UEFI support or is this MBR-only?
IIRC Balenca, maybe Rufus too and certainly "isomaster" (both Windows and Linux versions) will check iso files and display if a boot sector is properly included.
Could happen that Slackware 15.0 to be already too old for the modern hardware of OP.
Additionally, the SlakLive has an unique support for booting under SecureBoot. Slackware itself hasn't.
Regarding OP's problem, I would note that I have 3 motherboards Asrock B75M-DASH which cannot boot in the CMS/legacy BIOS mode the Slackware, be it installation kit, liveSlak or my USB hard drives with full installs of Slackware.
The thing is that they behaves just like OP happens to see - the bootloader loading the kernel and initrd, then hangs.
BUT, they work well in the EFI boot mode. That's WHY I suggest to OP to ensure that he uses the EFI boot, not the CSM/legacy BIOS mode. This way there are better chances to boot.
Last edited by LuckyCyborg; 07-11-2022 at 06:24 PM.
It's hard to tell exactly what started to boot since the only mention is that usbimg.sys was written to a different USB drive. We can guess that initrd and kernel were there but we don't yet know. Also, only an MBR boot worked at all and we don't know if OP's PC supports UEFI or if his PC autoboots removable drives first, if OP used Booty Order Menu, or if Secure Boot, etc are enabled or not. It would be good to know such details.
@Dalgrim - AFAIK The boot sector of the USB is created along with the partition type and file system. The boot device I was referring to that can be checked by IsoMaster and possibly Balenca and Rufus, is that encoded on the iso.
First thing I would do is access Boot Order Menu to see if BOTH UEFI and MBR entries exist for the USB drive.
Are you using 64bit or 32bit iso? Secure boot, fast boot disabled in bios/firmware settings?
Good question!
Because the Slackware 32bit will NOT boot in the EFI mode, and IF happens the motherboard to have also CSM/legacy BIOS boot issues, the OP has no solutions to boot properly the Slackware installation kit.
Unless he borrows the Ubuntu bootloader and do some Boot-Fu, by booting Ubuntu stick and manually loading the kernel (with its parameters) and initrd from Slackware installation driver.
Last edited by LuckyCyborg; 07-11-2022 at 06:44 PM.
The slackware15 x64 iso flash drive does NOT boot. It isn't even a boot option. It does not boot when written with DD or with hybridISO (Rufus).
I manually wrote a different usb drive with usbimg.sys. That one boots, but hangs.
Secureboot is off, fast boot disabled, UEFI mode is on. Legacy off.
USB sicks I've tried 16GB USB3 PNY, 64GB usb3 PNY, 8GB Sansdisk. All same problem, the system does not even detect them as a boot device. The systems DOES detect a ubuntu iso burned to that same flash drive, or a windows10 ISO on a usb flash drive.
I've tried multiple usb ports no change.
I'll try the live Slack version and see if that changes anything.
You can find a set of new ISOs based on liveslak on my own servers: download.liveslak.org/latest/ in the Netherlands, or the US host us.liveslak.org/latest/ .
Note: all 64bit versions support Secure Boot.
Some people report that the ISO images won’t boot when copied (using ‘cp’ or ‘dd’ for instance) to a USB stick but they all boot properly if you use the ‘iso2usb.sh‘ script provided with liveslak to transfer the ISO content to a USB stick. Of course, this will give you nice persistent storage of all your modifications with optional data encryption, ideal for a secure on-the-road Slackware environment.
Well it was a roundabout thing but here is what I did:
1) redownloaded the .iso, just in case.
2) booted to slackware live
3) DD the iso to a usb flash drive
4) rebooted and this time it worked.
I'm not sure why but my guess is the ISO wasn't writing correctly from windows I think it was in MBR instead of GPT/UEFI, This would prevent UEFI from booting it but would allow the files to be seen once mounted. (in a nutshell: This is what was happening)
Thank you to everyone for all the help and suggestions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.