Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slackware-current doesn't boot as the bzImage path has changed #1563

Open
rilysh opened this issue Jan 20, 2025 · 0 comments
Open

slackware-current doesn't boot as the bzImage path has changed #1563

rilysh opened this issue Jan 20, 2025 · 0 comments
Labels

Comments

@rilysh
Copy link
Contributor

rilysh commented Jan 20, 2025

[]: 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/.

kernel ${slackware_mirror}/${dir}/kernels/huge.s/bzImage

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.
  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

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/
@rilysh rilysh added the bug label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant