Thanks pchristy, you saved my day on a brand new laptop !!!
didn't make a bootable drive so I used
and followed the remaining of your tutorial.

1 members found this post helpful.

Glad to be of help! And thanks for the tip about using dd instead of usbimg2disk.sh. It might help others out!

--
Pete

Hello,

is this problem supposed to be fixed?

I cannot boot my new Acer Aspire 3 A315-56 (BIOS version 1.19, SSD storage) with a
USB pendrive holding the "usbboot.img" in "slackware64-current" from October 10,
2021. The MS Windows installation worked fine.

This is what I did, after searching the Net:

1. at boot time, press F2 to enter the BIOS setup;

2. in BIOS's "Security" tab: set the Supervisor Password;

3. in BIOS's "Boot" tab: the only boot mode available is UEFI, but I disabled the
Secure Boot;

4. in BIOS's "Main" tab: press Ctrl+S to enable the supervisor features; change the
SATA mode from "Optane without RAID" to "AHCI";

5. in BIOS's "Exit" tab: select "Exit Saving Changes".

Now I try to boot from the USB pendrive:

1. at boot time press F12 to enter the boot menu;

2. select the "USB HDD" as boot device;

3. I see the first textual screen from Slackware's loader "Welcome to Slackware64
version 15.0 (Linux kernel 5.14.11)!"

4. I just press Enter to boot with the "huge.s" image;

5. loading starts; it loads "huge.s" until "done"; it loads "initrd.img" until
"done";

6. and it just stops doing nothing.

Sometimes I can reboot with Ctrl+Alt+Canc; other times I have to cut energy by
inserting a needle in the small reset hole under the laptop.

The same happens with "usbboot.img" in Slackware64 14.2. I can boot the laptop from
a USB pendrive holding one of the latest LinuxMint images
"linuxmint-20.2-xfce-64bit.iso".

If I leave SATA mode to "Optane without RAID": LinuxMint cannot see the internal SDD;
by setting it to "AHCI": LinuxMint can see the internal SDD with devices:

/dev/nvme0n1p1 EFI system partition

/dev/nvme0n1p2 Microsoft reserved partition

/dev/nvme0n1p3 Basic data partition (with the Windows installation in it)

/dev/nvme0n1p4 Basic data partition (with the Recovery system in it)

With SATA mode set to "AHCI", the preinstalled Windows does not boot anymore; I can
boot it again by switching SATA mode back to "Optane without RAID", boot, let it
"repair" the system and restart.

So I tried an equivalent of pchristy's method to create a bootable instllation USB
pendrive: it worked, I can boot the installation procedure (not finished yet, I will
in the upcoming days).

Glad it worked for you!

As far as I am aware, neither PV (Slackware creator / maintainer) nor Alien_Bob (creator of the script to make installation pendrives) have followed up on this. It only appears to affect a small number of machines. Whilst I am not absolutely certain of the cause, I *do* know that using grub to boot the install media (as described above) works.

Anyway, glad you got it sorted!

--
Pete

I only read the first four comments between pchristy and Alien Bob on the first page of this thread, so I don't know the rest of the conversation. I came to say that I've had the same problems, or similar anyway, as pchristy when trying to use the liveslak at times. I've posted about this in the past, but didn't have the technical knowledge to try to diagnose as pchristy did or to see Alien Bob's explanation as the background of issue. Hopefully though, there is some update to the installer or boot process so that it will be easier to use those media for testing, troubleshooting, or installation. Thanks, pchristy, for the thread.

Thanks, Thanks, Thanks pchristy !

I am just now exploring my new Sager NP9672M-G1 which is a rebranded Clevo CLEVO X170KM-G

Lots of shiney-new Hardware here but the Insyder BIOS Application seems dumbed-down to the point of being primitive ( ??? where are all the knobs and buttons for all those new goodies ??? )

Anyhow, Alien Bob's Slackware Live Edition Booted fine yesterday after I was able to find a Bootable 32GB Thumb Drive.

Everything seems to work ( Rare for me on new Hardware ) and Plasma is beautiful.

Bookmarked your post.

I am going to try the 'old way' of installing Slackware Current but if I have grub issues, I know where to look.

-- kjh

Good day.

Created install thumb drive for 15.0RC2 using supplied usbimg2disk.sh.
On system with MSI MS-7B51 mainboard (MSI MPG Z390 Gaming Plus), system hung after loading kernel and initrd.
Per your post, deleted contents of EFI folder and copied over from slackware64-current/EFI folder and edited grub config as shown.
On next boot from install media, was greeted by grub prompt. Was able to start boot by issuing commands

linux (hd0,msdos1)/efi/boot/huge.s
initrd (hd0,msdos1)/efi/boot/initrd.img
boot

Not sure why it didn't pick up the thumb drive partition automatically, but install worked properly afterwards.

Thanks much.

Hi - just want to chime in here. This issue is affecting new Intel Jasper Lake machines also.

I suspect most, if not all, integrated Intel graphics systems 10th generation and onward are going to be affected by this issue.

Just wanted to note that the machine does not lockup, just that graphics output doesn't happen after ELILO loads initrd.gz.
I have managed to do installations remotely using network via ssh through dropbear on the install media.

Andrew.

2 members found this post helpful.

Thanks for your input, Andrew. Whatever the issue is, it looks as if it is becoming more commonplace, as I feared. I still haven't seen any response from our beloved leader, and hesitate to keep prompting him about this.

Perhaps it needs a few others to file bug reports to prompt a proper investigation? In the meantime, switching to grub seems to be a viable work-around.

--
Pete

1 members found this post helpful.

Just to note - after the installation, when I booted, then I still had no graphics output in the standard vga framebuffer. It wasn't until the switch to the intel framebuffer around 6 seconds into boot that the display output returned. Thankfully that required no special setup or kernel parameters and worked as normal after that.

Andrew.

1 members found this post helpful.

Did you switch your installation to grub? Once I'd managed to get mine installed, initially it did exactly what you have described. I didn't get the frame buffer (penguins) back until I installed grub. Using grub on the install media just enables you to boot the install media. It doesn't automatically install grub on the final installation.

Grub appears to correctly use the efi buffer. From what I can make out, elilo (& syslinux?) tries to use a non-existent vga buffer!

--
Pete

1 members found this post helpful.

No, I used the original ELILO based install but "blind". I just started dhcp and dropbear to allow remote installation and did it from another machine on the network.

Once installed, also using ELILO. It's quite possible that the framebuffer switch issue comes from ELILO, but I haven't looked into it further.

Andrew.

OK, if you want the "penguins" (frame-buffer) back, just install grub instead of elilo.

Yes, I had to take a deep breath before I did it the first time, but its actually quite painless! A side benefit is that if you configure /etc/default/grub to your liking, not only do future kernel upgrades become very simple, but for dual boot systems, you can make it reboot to the last booted system by default. This makes upgrading systems that need multiple reboots to upgrade a doddle!

--
Pete

Thanks - I'm familiar with GRUB, but really don't want to go down that path now.

Might look into it in future though. Good to know that it works.

It sounds like Slackware may have to migrate to GRUB at some point if there are growing pains of ELILO (which is abandoned afaik) when it comes to newer graphics devices.

Andrew.

Thank you for this workaround which made me able to install Slackware 15.0 on my laptop.