1

At the start of this year, running a kali live USB on a Lenovo (Lunar Lake) "Aura Edition" laptop was impossible due to incompatible hardware. Then, approx. 4 months ago, kali 2025.3 released and I was able to boot, meaning a patch for this lack of compatibility was developed. However, flashing a USB with an image downloaded today gives the same error that was being thrown at the start of the year. Have we gone back?

I checked and a USB with the flash from ~4mo ago STILL works, so the problem is not a change to the laptop bios, but the Kali Image.

The boot freezes, not displaying any error in particular. However, when adding nomodeset in the GRUB, the boot does work but with poor graphics (e.g. cant adjust screen scale).

8
  • this might be a number of things, but a high contender is that the kernel does or doesn't include a specific driver for a specific component of your laptop. Since Kali is kind of special in a lot of respects: do general-purpose Linux live images boot (Ubuntu 25.10, Fedora 42)? if so, that could be a start to help you narrow down what exactly changed (if you still care at that point) Commented Nov 23 at 13:05
  • All distros have some kind of problem while booting, Ubuntu specifically does not boot. What worries me is that Kali used to work perfectly and now it does not anymore. Commented Nov 23 at 13:22
  • thing is that can be a change in their bootloading process, some kali-specific modification of the kernel, the kernel modules included in kali's initrd… Kali explicitly states that overly reliable wide hardware support is among their non-goals, so somehting like Ubuntu not booting is way more sensible to follow down and diagnose. For example, current Ubuntu not booting makes a general lack of kernel support more likely vs distro-specific pecularities. Commented Nov 23 at 13:38
  • However, that means that you'll either need to be able to get a debug output out of your not-booting-machine (which is unlikely to happen on a laptop), or you need to start bisecting kernel releases on a stable distro (for which a rolling-release distro like Kali is really not an appropriate choice, because everything changes all the time – you cannot easily recreate a Kali image with modern everything but a kernel package from a year ago and hope everything will just work) until you can really pinpoint "worked on version x.y.z, but not on x.y.z+1", and then you can read kernel changelogs. Commented Nov 23 at 13:43
  • 1
    note furthermore that there's no guarantee that the things not working today are the same things not working 6 months ago. Not that simple. Commented Nov 23 at 14:03

0

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.