Originally posted by lolren
View Post
Announcement
Collapse
No announcement yet.
It Turns Out Windows Unconditionally Reserves The First 1MB Of RAM, Linux Was Just Late To Do So
Collapse
X
-
- Likes 2
-
Originally posted by lamka02sk View PostAny motherboard manufacturers to avoid? If they can't fix their shit, they certainly don't deserve my money.
The problem you'll find if you ask that question enough is that everyone will report that every brand sucks so the best you can do is ask about what luck people are having with their current hardware.
About my only complaint is on a cold boot it can be a PITA to access the UEFI....my keyboard takes for fucking ever to initialize so I have to spam whatever I'm trying to do because, on cold boot, there's a split second where both the keyboard is initialized and the initial boot screen will take input. That's not my motherboard's fault but it's an annoyance none-the-less.
If you have an RGB keyboard that does bullshit when it initializes....well.....that might be an issue with any motherboard that initializes quickly and not just mine. I need a Goldilocks motherboard. Doesn't initialize too fast; doesn't initialize too slow; initializes just right. Or a better keyboard....
Comment
-
Originally posted by AnAccount View Post
The correct way would be for both Windows and Linux to refuse to boot if the BIOS corrupts the memory. That would lead to an actual fix of the root cause....
I would think it's much more preferable for the OS to take steps to ensure that the system boots so that an end user can find a fix to the problem.
How would you guys go about fixing a system where the BIOS corrupts the ram if both Windows and Linux refused to boot?
And of course Windows does it better, there's a reason why MS is worth billions of dollars and one of the world's most valuable companies and there are maybe 4 Linux based companies that actually make a profit.
- Likes 5
Comment
-
Originally posted by sophisticles View PostI would think it's much more preferable for the OS to take steps to ensure that the system boots so that an end user can find a fix to the problem.
- Likes 2
Comment
-
-
Originally posted by Termy View PostOf course it's too late now, but if both windows and linux would do it "the right way" and the system wouldn't boot, the hardware-vendor would be forced to write a proper firmware. That's the "fix" he mentioned...
Remember that the profit margins on PC sales are pretty slim, and the refresh cycles are fast paced. There's simply not time or budget to rework and fine tune the BIOS implementations. It's more important to get product out the door, than to have it be really polished and clean. Again, I don't like it, but I understand why they do it this way.
This is one reason I only use server / workstation grade hardware in my PC builds. Supermicro motherboards are my go-to. There's more budget in the enterprise hardware space to do things the right way, and less tolerance for buggy implementations. That's not to say they're flawless, but they are certainly better than the low-budget family peecee stuff.Last edited by torsionbar28; 09 June 2021, 11:34 AM.
- Likes 4
Comment
-
I read the original announcement wrong, it seems. I though this change was to *eliminate* the reservation of the first MB or DRAM on x86/x86_64 (clearly not an issue on other archs). And I though "Wow, that seems like a risky bet for a tiny amount of memory. I hope this doesn't cause tons of subtle bugs due to crappy BIOS/UEFI/firmware." Glad to see I misread it. Can't believe we've been doing it this way all this time. Once memory went over 1GB, this seems like an obvious low hanging fruit of stability.
Comment
Comment