Cannot install any Linux

[Rocketing-warp9]

Probably how linux points to the memory integers is probably why it's unaffected on windows. (Linux might point to the bad sectors while windows does not)
Do you have another computer you can try the Memory out on?
At least then you can tell if it's the board itself or the memory.

Maybe a CMOS Reset?

 

[APTI]

Hi all, I'm trying to make the move from Windows 11 to Linux and getting nowhere. My setup:


CPU: AMD Ryzen 9 9950X3D
RAM: Corsair Vengeance 64GB DDR5 6000MT/s
GPU: NVIDIA GeForce RTX 5090
Motherboard: ASUS TUF GAMING B850-PLUS WIFI
OS: Windows 11 IoT Enterprise LTSC (Build 26100)
Storage: Samsung SSD 990 EVO Plus 4TB

I have tried CachyOs, Nobara, Ubuntu 26.04 LTS and Pop!_OS and all fail after printing a message about malformed bluetooth vendor event most the time, but occasionally progress further to a point where it shows me progress on jobs 1 through 6, before freezing. I believe the malformed event is a red herring from what I can find. Just once, Nobara gave me a message about a soft lock on CPU#4.

Things I have tried:

Secure boot, fast boot and CSM are disabled. Legacy USB support set to auto (also tried disabled)
Updated BIOS, loaded optimised defaults (and then set the above settings)
Disabled iommu
Disabled native ASPM
Disabled fTPM
Disabled onboard bluetooth
Changed PCIe speeds to Gen3/4
Tried booting with nomodeset (I do use nVidia specific ISO's though where available)
Tried maxcpus=1
Blacklisted NVMe drivers
Disabled NVMe autonomous power state changes
Different USB sticks
Ventoy, Rufus, balenaEtcher

And probably a bunch more stuff, I've been at this for about 3 days. The only things I haven't tried yet is plugging into a different USB slot, and unplugging my NVMe, purely because my computer is in a fairly inaccessible location so I'd rather not have to pull everything out and unplug everything. Any help would be greatly appreciated.

First and foremost, DO NOT UPDATE BIOS.... that is dangerous to do and should only be done if you have an issue. those bios updates from microsoft are ill advised and they don't get it. One wrong move and your motherboard is a paper weight.

Next, it was suggested to use the live usb to run the system and see if things work. This way you are not wiping things out all the time. One issue I have seen is on occasion a BIOS update from microsoft causes massive issues in linux. Not sure what they do sometimes but have seen this. Another reason to NOT UPDATE BIOS.

Reset your bios to defaults and use a live usb of Fedora 44 and see what you get without installing anything.

 

[Brian Alex]

Useless Newbie here who has no business even posting in a WebTV forum but you said "...my computer is in a fairly inaccessible location so I'd rather not have to pull everything out and unplug everything." If it was me, I'd bite the bullet and actually do this. I'd strip it down to just a wired mouse and KB and boot to compatibility mode if such is offered.

 

[Rocketing-warp9]

If it was me, I'd bite the bullet and actually do this. I'd strip it down to just a wired mouse and KB and boot to compatibility mode if such is offered.

Or- Try Puppy Linux, as it uses GRUB4Dos Rather than Regular GRUB (I Think) To at least see if it is just a GRUB issue OR A distro- related issue.

 

[f33dm3bits]

that is dangerous to do and should only be done if you have an issue. those bios updates from microsoft are ill advised and they don't get it. One wrong move and your motherboard is a paper weight.

I was talking about BIOS motherboard updates from the vendors website, not from Microsoft. Downloading the update from the vendors website, copying it to a usb drive and then using then flash utility in the bios for updating. Never had an issue and some motherboards even support a rollback functionality, I've done this so many times over the years. Maybe back in the day with BIOS motherboard this was a thing I can't remember but with all my UEFI motherboards never had an issue.

 

[piorunz]

First and foremost, DO NOT UPDATE BIOS.... that is dangerous to do and should only be done if you have an issue

Well, he does have an issue. That's why he opened this thread.
BIOS update is a valid suggestion for a case like this.

 

[CaffeineAddict]

BIOS update is a valid suggestion for a case like this.

Yes, but someone who needs to open a thread is not ready to update BIOS.

The worst thing that can happen is power outage.

I know for instance this will happen mostly before 15:00h because that's when electricity workers tend to suspend power for maintenance in our city.

 

[f33dm3bits]

Yes, but someone who needs to open a thread is not ready to update BIOS.

Just because someone is not familiar with Linux doesn't mean they don't know how to update a BIOS. I know Windows power users who can update a BIOS but if you ask them anything about Linux they won't know what to do.

 

[piorunz]

Yes, but someone who needs to open a thread is not ready to update BIOS.

OP is more than qualified. Have you read his first post?

Things I have tried:

Secure boot, fast boot and CSM are disabled. Legacy USB support set to auto (also tried disabled)
Updated BIOS, loaded optimised defaults (and then set the above settings)
Disabled iommu
Disabled native ASPM
Disabled fTPM

And his other post:

I have decades of commercial experience in highly technical roles working on and with Linux.

He is more than qualified to manipulate BIOS. He is not a newbie, stop treating him as such, but read opening post again. He needs expert advice, not rookie caution.

 

[CaffeineAddict]

He is more than qualified to manipulate BIOS. He is not a newbie, stop treating him as such, but read opening post again. He needs expert advice, not rookie caution.

You're right, my comment was general, not aimed against the OP.

 

[KGIII]

The worst thing that can happen is power outage.

These days, it will (usually) prompt you to retry the upgrade or revert to the previous version if the power goes out. They come with built-in recovery tools, some of which will even store your previous version in case you want to. You just wait for the power to be restored and boot with the USB thumbdrive you were using to flash the BIOS.

 

[CaffeineAddict]

These days, it will (usually) prompt you to retry the upgrade or revert to the previous version if the power goes out. They come with built-in recovery tools, some of which will even store your previous version in case you want to. You just wait for the power to be restored and boot with the USB thumbdrive you were using to flash the BIOS.

Never heard of this but it's very useful info to know about.

Pretty sure I'd pull out USB and throw my mobo straight into trash bin.

 

[KGIII]

Pretty sure I'd pull out USB and throw my mobo straight into trash bin.

For some period of time, there would have been a jumper on your motherboard. If you removed the jumper and cycled the power, it'd write the original BIOS (or maybe the previous BIOS) back into that memory space. For the life of me, I can't remember if that required popping out the CMOS battery or if that bit is just a broken bit of memory in my head. It hasn't been something that has concerned me in a lot of years.

 

[Brickwizard]

, I can't remember if that required popping out the CMOS battery

that was the old way, but on most modern computers all you need do from on, is press and old the power button down for 60 seconds , release, and re-start