I'm new to Linux and am trying to dual-boot Void Linux with Windows 11 on my laptop. I disabled Fast Boot, Secure Boot, and BitLocker, shrank the Windows partition, and created a 512 MB EFI partition, a 100 GB ext4 root partition, and roughly 25 GB of swap space. The first installation completed, but I wasn't sure how to select services in the installer. Void booted afterward, but I couldn't get an internet connection, so I deleted the Linux partitions and started over.
During the next installation attempt, the display froze and the Caps Lock light began blinking, which I assume indicates a kernel panic. Windows has also occasionally crashed when the laptop sleeps or is unplugged, showing errors such as Hypervisor Error, KMODE Exception Not Handled, and references to ntoskrnl.exe. The laptop was plugged in during the Linux installation.
The system has a Ryzen 5 6600H, Radeon 660M integrated graphics, 32 GB of DDR5-4800 memory, and a Kingston NVMe SSD. I primarily use a phone hotspot for internet access and don't have an Ethernet port. What could be causing the freezes, and what hardware or firmware checks should I perform? Also, which services should be enabled at the end of the Void installer?
3 Answers
Void is perfectly usable, but it gives beginners more manual setup work than distributions with a more guided installer. For the first installation, it may be easier to test the exact live image in a virtual machine or try another current Linux live environment on the laptop. If several unrelated live systems freeze in the same way, focus on the laptop rather than reinstalling repeatedly.
The lack of internet after the first boot may simply have been because the network service or the appropriate Wi-Fi service was not enabled. A phone hotspot can work if the laptop supports it over Wi-Fi or USB, but Ethernet is not required. Once booted, verify that the wireless adapter is detected and that the networking service is running; you can enable or start services after installation instead of having to redo the partitioning.
A freeze with a blinking Caps Lock LED can be a kernel panic, but because Windows is also crashing, I would investigate the laptop's hardware and firmware before blaming the installer. Run a complete MemTest86 test, update the laptop's BIOS/UEFI if the manufacturer's release notes indicate newer firmware, and load BIOS defaults while troubleshooting. Also check for unusual power-management behavior, since sleep and unplugging problems can point to firmware or ACPI issues. Temporarily disabling aggressive CPU power-saving features may help identify whether a C-state problem is involved.
For the installer service screen, use the arrow keys to highlight a service, press Space to toggle it, and press Enter to confirm. A normal desktop installation generally needs networking, device management, and a display/login service; the exact names depend on the desktop and init setup. You can also enable services later, so don't treat that screen as irreversible.
Since both Windows and Linux have instability, this sounds more like a laptop-level problem than a Void partitioning mistake. Check the manufacturer's support page for the installed BIOS/EC versions and compare them with the latest versions for the exact model. Also return BIOS settings to defaults except for the settings genuinely required to boot the installer. Windows crash codes involving the hypervisor and kernel can come from faulty RAM, storage, firmware, drivers, or power management, even when one memory test passes.
Try a hardware-focused process: run additional memory tests, check the NVMe drive's health, install all available Windows firmware and chipset updates, and test whether crashes happen only during sleep, battery operation, or heavy load. If the live environment still panics, boot with minimal power-management options or try another distribution's current live image. That can help distinguish a Void-specific kernel issue from a broader hardware or firmware failure.
I ran MemTest86 for four passes with no errors. The BIOS is an AMI Aptio interface showing version 3.11 and EC firmware 5.09. I only changed virtualization, Secure Boot, Fast Boot, and boot order. Is updating the BIOS worthwhile, and should the memory test be repeated while unplugged?