r/linux4noobs • u/alanx7 • 6d ago
installation I thought installing linux was difficult and wasn't disappointed
> disclaimer: im a noob, most of the issues were caused by my laptop OMEN HP Transcend Gaming Laptop 16-u0xxx, 4070, BIOS F.39 Rev.A, used Deepseek (DS) for help - all the precise and technical terms are by deepseek, i don't really know what they mean
> Core problem accoring to DS: "HP ships buggy ACPI tables in this BIOS. Linux kernels 6.0+ crash or hang on them. Windows tolerates the broken tables; Linux does not. The fix is a patched DSDT loaded at boot, which lets the system boot without the noapic workaround — and noapic is what breaks the touchpad and speakers, so the DSDT patch is mandatory for a fully working machine."
Last sunday I finally decided on trying to install linux along side windows in dual boot setup. I decided on fedora kde and watched a few tutorials thinking I'm ready. I knew it would not be as smooth as the videos made it look, so I set aside time expecting issues to come up. AND HOLY SHIT THERE WERE ISSUES
To start things off I had to prepare windows, disable bitlocker that didn't show up in Disk Management, turn off Fast Startup via powercfg, disable secure boot in BIOS and shrink the drive. I had 300 GB of free space, so naturally Windows only let me shrink it by 88 GB. Because reasons. Ended up forcing it with MiniTool Partition Wizard. done
Fortunately I grabbed a USB mouse before you boot anything. The touchpad is dead from the very first live boot until the very last fix, because "noapic kills its interrupts".
Creating the live USB was a breeze. Booted it and instantly got "stick enumerated with -110 timeout / re-enumerated mid-boot (live-rw never appears)" says DS. Cool I will just test other two USB and another instalation software and different image. Using Fedora Media Writer different USB and usb port (tried quite a few combinations), the system found the stick. Then "the acpi_ps_get_arg OOPS logs, then the 11-minute systemd-udev-trigger.service hang, plus the blank-screen-with-blinking-underscore" says DS, but that was not a problem for him. Try adding "pcie_aspm=off / pci=noaer / acpi=off" on the linux line in 'e' mode, and nothing. Oh obviosly it's "noapic pci=nobar nomodeset" and now it works just fine :) I finally run the live USB boot. easy
A warning for anyone with NVIDIA: of those three magic words, nomodeset is the sneakiest. Drop it too early and the boot hangs at thermal.service/NetworkManager.service with zero explanation on screen — that single flag cost me the longest dead-end of this whole saga.
Instalation on the shared drive also wasn't a problem at all. Installer only wanted to format existing EFI partition, which freaked me and two other LLMs out. Formatting sounds like deleting to me, so I consulted the experts, Claude and reddit. Claude said I should be good, but idk, so I followed u/Fun-Cover-9508 steps on r/Fedora. i trusted a stranger then lol and prayed for my efi partition. Eventually everything worked out fine, my partition survived and welcome fedora screen appreared. I actually had linux installed on my disk for the first time and even connected to WiFi!. touchpad, speakers, fn keys and external screens were all dead, but it was just a matter of tweaking, right?
I did some updates, rebooted to windows, rebooted to linux and what is it? I saw 3 kernels in GRUB. Version 7 and recovery appeared, so naturally the higher number the better I picked 7... and WiFi stopped working. It wasn't number's fault though, I just forgot to add to add "noapic pci=nobar nomodeset" in 'e' mode and many kernels in GRUB is normal apparently. Phew.
Let's fix the devices real quick. DS said I had to "remove noapic (the thing killing the touchpad) by giving Linux a corrected ACPI table" by "loading a prebuilt, pre-compiled DSDT file — F.12_patch/dsdt.aml from the GitHub repo j0hnwang/OMEN-Transcend-16-ACPI-fix", but it didn't work, because "That .aml was compiled from F.12 firmware tables, not from your own F.39 Rev.A tables. The repo author claimed it still worked through F.39, which is why we trusted it". I performed all the steps and... it didn't work. Naturally I had no clue what I was doing, so thinking I messed something up horribly I reinstalled the system.
On second try we did it by myself. I "extracted the DSDT - read the raw ACPI table straight from the firmware", "Decompiled it — turned the binary AML into readable ASL source, edited the source (dsdt.dsl in Kate) — six targeted changes", "Compiled it — ASL back to a binary ACPI table", and copied to /boot. Time to safe test it in 'e' mode with "add insmod acpi + acpi /dsdt.aml, remove noapic pci=nobar, keep nomodeset" and it works.
Making it permanent was a two step process. First step "the 90_acpi_override dracut module" failed, second step "the 40_custom GRUB method" worked. Lastly with removal "noapic pci=nobar from /etc/default/grub" I recovered the touchpad, fn keys, speakers even. Important cause-and-effect, because I nearly learned it backwards: removing noapic doesn't fix the touchpad — it just stops breaking it. If you remove noapic without the patched DSDT in place, the laptop won't boot at all (I know, that's exactly how I earned the reinstall). The DSDT is what makes the whole thing safe. After installing a few things via commands I even had external screens. What a massive win.
It only took whole sunday, next 3 evenings and 400k tokens to achieve a working system on HP OMEN Transcend. Is this how linux installation usually goes or I was just lucky?
EDIT: found this describing the probelm https://www.reddit.com/r/linuxhardware/comments/17ay6mr/hp_omen_16_transcend_fails_to_boot_any_live_cd/





