[GH-ISSUE #1563] slackware-current doesn't boot as the bzImage path has changed #2047

New issue

Open

opened 2026-03-01 18:38:09 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 18:38:09 +03:00

Owner

Originally created by @rilysh on GitHub (Jan 20, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1563

[]: This bug persists when memory is increased beyond 8GB.

Describe the bug

Slackware-current doesn't boot as the -current bzImage path is kernels/generic.s/. Stable bzImage path is kernels/huge.s/.
github.com/netbootxyz/netboot.xyz@d4a8baa67f/roles/netbootxyz/templates/menu/slackware.ipxe.j2 (L27)
I'm not exactly sure if huge.s means kernel-huge or just generic one. Current has removed support for huge-kernel as noted in the Changelog (http://www.slackware.com/changelog/current.php?cpu=x86_64).

a/kernel-huge-6.10.9-x86_64-1.txz: Removed.

To Reproduce
Steps to reproduce the behavior:

Download netboot 2.0.84.
Boot the ISO in QEMU (or any other virtualization software).
Select Slackware-current from Linux Network Installs

Expected behavior

-current should boot.

Screenshots

Additional context

Originally created by @rilysh on GitHub (Jan 20, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1563 []: This bug persists when memory is increased beyond 8GB.  **Describe the bug**  Slackware-current doesn't boot as the -current bzImage path is `kernels/generic.s/`. Stable bzImage path is `kernels/huge.s/`. https://github.com/netbootxyz/netboot.xyz/blob/d4a8baa67f3d782d4f4b92fe4ac419a02b9d133d/roles/netbootxyz/templates/menu/slackware.ipxe.j2#L27 I'm not exactly sure if `huge.s` means kernel-huge or just generic one. Current has removed support for huge-kernel as noted in the Changelog (http://www.slackware.com/changelog/current.php?cpu=x86_64). > a/kernel-huge-6.10.9-x86_64-1.txz: Removed. **To Reproduce** Steps to reproduce the behavior: 1. Download netboot [2.0.84](https://github.com/netbootxyz/netboot.xyz/releases/tag/2.0.84). 2. Boot the ISO in QEMU (or any other virtualization software). 3. Select Slackware-current from Linux Network Installs **Expected behavior**  -current should boot. **Screenshots**  ![Image](https://github.com/user-attachments/assets/e53fb07f-7498-480f-82d4-95da9f1aa8d4) **Additional context**  1. https://mirrors.kernel.org/slackware/slackware64-current/kernels/generic.s/ 2. https://mirrors.kernel.org/slackware/slackware64-15.0/kernels/huge.s/

kerem added the

bug

label

2026-03-01 18:38:09 +03:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#2047

No description provided.

Rows
Columns