-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Booting with Z790 Asus Motherboard with 64G of memory not working #327
Comments
What's the error message? |
"error: out of memory...." is all I get.....
I then tried the Ventoy method mentioned in your Github post and I got the same result - even with the Ventoy ISO method. Grub2 does not work and the first listing doesn't work. With the Ventoy method I got a bit farther, I did see a menu show up, but none of the options (there were three) would work.
This is very similar to when I tried to upgrade from Linux Mint 20 to 22. Basically I couldn't, and had to boot from v22 and reinstall everything. But then it worked.
…________________________________
From: PartialVolume ***@***.***>
Sent: Tuesday, February 4, 2025 12:42 PM
To: PartialVolume/shredos.x86_64 ***@***.***>
Cc: meaganmargaret ***@***.***>; Author ***@***.***>
Subject: Re: [PartialVolume/shredos.x86_64] Booting with Z790 Asus Motherboard with 64G of memory not working (Issue #327)
What's the error message?
—
Reply to this email directly, view it on GitHub<#327 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AELIXDZZ2Y7F6OGF2E5V76T2OEQ5BAVCNFSM6AAAAABWPOUF66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGAZDQMZVGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Do you have XMP enabled? |
Yes
From: PartialVolume ***@***.***>
Date: Tuesday, February 4, 2025 at 1:24 PM
To: PartialVolume/shredos.x86_64 ***@***.***>
Cc: meaganmargaret ***@***.***>, Author ***@***.***>
Subject: Re: [PartialVolume/shredos.x86_64] Booting with Z790 Asus Motherboard with 64G of memory not working (Issue #327)
Do you have XMP enabled?
—
Reply to this email directly, view it on GitHub<#327 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AELIXD36K32DGS2GABME74D2OEV2RAVCNFSM6AAAAABWPOUF66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGEYDSMBXGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I would temporarily disable XMP and see if it then works. I could be overclocking the memory is making it intermittently unstable depending upon your RAM type. |
So, I turned off XMP and still got the same error.
From: PartialVolume ***@***.***>
Sent: Tuesday, February 4, 2025 1.31 PM
To: PartialVolume/shredos.x86_64 ***@***.***>
Cc: meaganmargaret ***@***.***>; Author ***@***.***>
Subject: Re: [PartialVolume/shredos.x86_64] Booting with Z790 Asus Motherboard with 64G of memory not working (Issue #327)
I would temporarily disable XMP and see if it then works. I could be overclocking the memory is making it intermittently unstable depending upon your RAM type.
—
Reply to this email directly, view it on GitHub<#327 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AELIXD4JWWP3NSDQ4PB4QLD2OEWPXAVCNFSM6AAAAABWPOUF66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGEYTQOJWGM>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Have you run memtest86 to check for bad memory? |
Sounds like grub is running out of memory due. |
Oh God….yes! This is a perfectly functioning PC which runs Linux Mint v22 (perfectly), Windows 11, and MacOS Monterey. All work just fine, with no issues with the existing memory and all have been for almost a year.
From: PartialVolume ***@***.***>
Date: Tuesday, February 4, 2025 at 3:13 PM
To: PartialVolume/shredos.x86_64 ***@***.***>
Cc: meaganmargaret ***@***.***>, Author ***@***.***>
Subject: Re: [PartialVolume/shredos.x86_64] Booting with Z790 Asus Motherboard with 64G of memory not working (Issue #327)
Have you run memtest86 to check for bad memory?
—
Reply to this email directly, view it on GitHub<#327 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AELIXD3VQM2NK6LZLG4XNQ32OFCRHAVCNFSM6AAAAABWPOUF66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGI3TEMBTGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I have a discrete GPU, but after looking at your post, this is way over the top. I’ll pass. I just wanted to see if it would work for me.
I think your kernel is too old, I have no problems with newer.
I hope you get this worked out, but for now, I’m out.
From: Firminator ***@***.***>
Date: Tuesday, February 4, 2025 at 3:14 PM
To: PartialVolume/shredos.x86_64 ***@***.***>
Cc: meaganmargaret ***@***.***>, Author ***@***.***>
Subject: Re: [PartialVolume/shredos.x86_64] Booting with Z790 Asus Motherboard with 64G of memory not working (Issue #327)
Sounds like grub is running out of memory due.
Adding GRUB_GFXMODE=800x600 is supposed to fix it (that would be needed to be added to the ShredOS grub commandline; see how @ https://github.com/PartialVolume/shredos.x86_64?tab=readme-ov-file#how-to-edit-the-shredos-efibootgrubcfg-and-bootgrubgrubcfg-files-when-using-ventoy-with-shredos-img-files )
Do you have discrete video or use the GPU in CPU?
—
Reply to this email directly, view it on GitHub<#327 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AELIXD6LWPSQMSOUTTO72DT2OFCTZAVCNFSM6AAAAABWPOUF66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGI3TEOBYG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
There may be insufficient memory because you have a large amount of memory being reserved in your bios settings for the video card. This may be reducing the amount of space in the first 4GB that's used to load ShredOS. ShredOS probably occupies more space than those other OS, due to its virtual RAM disc that contains the entire OS. So if there is a setting in the bios for adjusting the amount of memory allocated to graphics, then reducing it may fix the problem. I've not seen this on any of my test systems, even the gaming laptop (12th Gen I7-12700H) but maybe you have a high end GPU. |
Interesting, I've never known a CPU degrade over time. Apparently one of the symptoms can be out of memory errors. It apparently occurs under elevated voltage and temperature settings. This problem may be corrected by a Intel microcode upgrade or a replacement processor from Intel.
Anyway, as the op isn't interested in looking into this further, I'm closing this as 'out of memory' seems to crop up quite a lot on these motherboards for all operating systems. |
This makes quite a read https://www.pcgamer.com/hardware/processors/intel-cpu-crashes-what-you-need-to-knowmicrocode-to-blame-but-fix-incoming-this-month-alongside-two-year-extended-warranty/ There seems to be upteen different ways the processor is failing, under load and at idle due to incorrect voltage requests and certain motherboard manufacturers that don't stick to lower voltages 1.4v. Apparently not just gaming rigs but some servers are also seeing this problem. I think I'll be sticking to my 12th gen Intel for a few more years. If there's one thing I hate, it's flaky unreliable hardware. |
@meaganmargaret One last question, as I'm still curious about this problem, are you running one of these processors? and as gigabyte released the Intel 0x12b microcode update in their bios update, has that been done? The concerning thing with this CPU is that once you have experienced this instability in the past, the incorrect voltages being supplied to the chip have already degraded it, so the update is really for brand new chips, hence why Intel extended the warranty by 2 years. |
Can't boot as the system used can seem to read the memory in my Z790 motherboard. I had this issue with an older version of Linux Mint, but newer versions (v22) can read my memory just fine. Any workarounds for this? Some setting somewhere?
The text was updated successfully, but these errors were encountered: