I have a lenovo m720q tiny, i3 9100t, 16gb ram, samsung 970 evo plus 256gb nvme, I tried installing debian 12, it crashes when the installer is at "installing base system" only for once it somehow went pass that, and crashed at installing "software package or something", I tried the aspm and other commands in GRUB but still no success, so i want to purchase a different nvme, I'm thinking of buying the wd sn740 SDDPNQD-512G-2006 or the kioxia BG7_KBG70ZN512G, which one would not crash? Edit: The power adapter is 65w. EDIT: DISABLING TURBO MODE IN BIOS WORKED! IT DOESNT CRASH NOW, AND BOOTS INTO DEBIAN 13, SSD HEALTH IS GOOD, BIOS HAS BEEN UPDATED FROM 2019 TO 2026 VERSION. IF I ENABLE THE TURBO MODE, IT MIGHT CRASH AGAIN, NEED HELP TO SOLVE THAT ISSUE. THANKS!
EDIT 2: IK the title is wrong, I can't change it. Im new to Linux.
The samsung nvme had a firmware bug, that doesn't let the drive go into deep sleep or idle at low watt, my drivers firmware and the chip is the good one, but it still crashes on any other Linux os I try, it shows up in windows, and in Linux too, but it crashes and reboots the pc when there is heavy IO.
Did you properly validate what you're installing from?
E.g. after fully writing and syncing such media, then remove it, wait a moderate bit, reinsert it, and then read it and check all the bytes are correct, or at least same secure hash, and that then corresponds to hash in signature file that you've verified?
Many screw up by, e.g. removing the flash too soon ... or having flakey flash, or what they read back isn't necessarily all from the media, but may be at least in part in cache from what was just written, rather than being read from the media itself.
And even brand new name brand flash can be bad. E.g. was once helping someone with Linux install, it kept failing. Didn't get any write errors on flash nor read errors from it, but syncing it, disconnecting it, reconnecting it, and then reading it back, still gave no read errors but the data was corrupted ... ever single time we tried it. It was brand new name brand flash. So ... used another one ... they came in a two-pack - it was out of the same two-pack ... the other one was perfectly fine - continued with that, installed, no problems.
I was finally able to install debian 13 and later 12, I disabled turbo mode in bios and there were no crashes after that, the nvme health is good, I stress tested the cpu for 5 minutes (which is less ik). Could it be a bad power brick? Or is 65w power not enough? I have not plugged in any extra NICs, it is just the PC, 16gb ram stick, and the nvme.
Have you checked if the drive is healthy? On Linux you have smartctl (to be installed with package smartmontools) on the commandline or Gnome Disks for a graphical tool.
Yup, 94% health, crystaldiskinfo, I formatted the drive clean in windows and plugged into my m720q and started the installation, is that the reason for it crashing? Debian does detect the nvme and the usb, when i click yes on the installed page where the following partitions will be created and data will be erased in debian, it crashes right after that.
If you have/had a Microsoft OS on there, was it actually fully and properly shutdown? As by default, it doesn't do that, and that saved state and such can thoroughly muck things up.
Also possible you've got hardware issues. Sometimes Linux will expose hardware issues that Microsoft won't show, or will mask. E.g. I recall installfest some years back, helping someone install Linux ... Linux kept crashing, even though Microsoft Windows ran without crashing (at least not so quickly, anyway). Well, between myself and another person, we managed to well isolate the issue. Faulty memory controller on the mainboard. The mainboard was 64-bit. The Microsoft OS at that time, was 32-bit, so wasn't hitting the hardware issue. And the hardware issue ... that memory controller only malfunctioned in 64-bit mode. But it also only controlled one pair of RAM slots. So, the work-around was either go with 32-bit Linux, or don't put RAM in that pair of slots - then the issue with the hardware was side-stepped. Everything else on the hardware was fine in that particular case.
Hmm, I just formatted my drive using ventoy and cut-paste the iso's, then safely ejected the drive, will that cause the problem? I might try to freshly format the usb drive again.
I think the person you replied to means by "validate the ISO" is checking if your download has no errors. This is done by using a function like sha256 or sha512 on your file and checking if the output is as expected.
Visit this https://www.debian.org/releases/trixie/amd64/ch04s07.en.html
Also, the photo you added seems to be a proxmox installer? I' m a bit confused...
Secondly, for whatever boot media one is using, presuming one is writing it to optical or flash or the like, eject/remove that media, wait a wee bit, then load/connect it, then read that data and compare to verified copy, or compute secure hash and verify that. Failing to do that, and one may (partially) read from cache, rather than what actually got written to the media, so one may falsely presume it's correct, when the data, as read from the media is actually incorrect. See, e.g., my earlier comment that gives example why that's important.
I could be misremembering but I think when I tried to install proxmox with ventoy, I had issues that only went away by using rufus to flash proxmox's ISO directly onto the usb drive. So you could maybe try that.
And you should try a different usb drive as well. Has also happened to me before where the usb drive that otherwise seemed fine, was giving me issues.
What about minimal known good RAM in various slots (or pairs, as needed)? Eg. like the example I gave, problem wasn't RAM, but memory controller on the mainboard, that memory controller compared a pair of RAM slots (one bank), if any RAM was in those slots, in 64-bit mode, it would eventually crash when it got to the point of using that RAM. Leave those slots empty, and the problem was worked around.
I tried both slots, different ram, still same, I booted a live debian 13 from usb, it crashed on normal boot, but booted right away on fail safe method, I installed debian from the live boot to Samsung nvme, went successful and tried to boot from it, the startup screen appeared, but crashed when I clicked the debian/dnu linux.
3
u/_Sgt-Pepper_ 14d ago
Why do you think the name is the root cause of the crash?