View Issue Details

IDProjectCategoryView StatusLast Update
0009518Kali LinuxKali Package Bugpublic2026-02-25 16:16
Reportergdijim Assigned Toarnaudr  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0009518: Wrong Kernel in the installer package (Netboot)
Description

The newest update netboot package doesn't appear to be updated or working properly. This was working last week before the newest update. Previous instructions to replace the initrd.gz and linux files (and/or the entire netboot directory) fails.

I last used this to image machines Monday this week, but I believe the netboot files have been replaced since I last did the work, because my process fails.

Note: Additionally, even with the working files last week, there was a strange issue where the machine wouldn't finish loading properly on a SATA drive. However, it worked fine imaging NVME's. Now it errors saying Kernel mismatch.

I was running the previous month's spin of Kali, the one from December, but updating to January's latest spin has broken our process.

This is the exact error I get when the initrd.gz and linux files are not in line with the distro on the mirrors, which happened the last time the monthly update came out. Last month, I simply copied the linux and initrd.gz files from https://http.kali.org/kali/dists/kali-rolling/main/installer-amd64/current/images/netboot/debian-installer/amd64/ to the directory my PXE server points to boot from. This month, this same fix doesn't work, leading me to question whether or not the Netboot directory/boot files were included in the month's change.

The instructions I'm speaking of are our internal instructions to correct the boot files after the kernel updates.

Please let me know if I can provide more information.

Thanks!

Jim

Activities

gdijim

gdijim

2026-02-05 19:01

reporter   ~0021312

They fixed this with a new update to netboot files.

arnaudr

arnaudr

2026-02-25 16:16

manager   ~0021390

I'm closing, I suppose it was fixed then. I'm sorry I didn't find the time to look into it when you reported it.

Issue History

Date Modified Username Field Change
2026-01-22 15:25 gdijim New Issue
2026-02-05 19:01 gdijim Note Added: 0021312
2026-02-25 16:16 arnaudr Note Added: 0021390
2026-02-25 16:16 arnaudr Assigned To => arnaudr
2026-02-25 16:16 arnaudr Status new => closed
2026-02-25 16:16 arnaudr Resolution open => fixed