ArchPOWER/packages
1
0
Fork 0
Code Issues 8 Pull Requests 1 Actions Packages Projects Releases 18 Wiki Activity

Grub version 2.12 error: couldn't claim memory. #110

New Issue
Open
opened 2025-03-03 16:55:33 +00:00 by WiiNewU · 8 comments
WiiNewU commented 2025-03-03 16:55:33 +00:00 (Migrated from github.com)
Copy Link

Hello, I recently got an IBM Power 720 server, I am having major issues with any Linux distro that uses a recent version of grub (in this case the archpower-2025.02.01-powerpc64.iso). There is an issue where grub boot menu will pop up, but when you run any option such as Boot LiveCD (kernel: ppc64) or Boot LiveCD (kernel: ibmpower) you will get this error:

error: couldn't claim memory
error: you need to load the kernel first.

Press any key to continue...

Then it will go back to the menu selection screen.

This happens with other Linux distro's that has updated Grub to version 2.12 like Debian Ports. The debian-12.0.0-ppc64-NETINST-1.iso ran just fine but when the install ran updates at the end and updated GRUB to ver 2.12 it has the same issue.

This error also happens on bare metal and through PowerVM/VIOS (a AIX based hypervisor).

I also tried running to boot the CD through yaboot through the open firmware prompt but yaboot just passes back to grub defeating the workaround.

Any help would be great, Thank you

Hello, I recently got an IBM Power 720 server, I am having major issues with any Linux distro that uses a recent version of grub (in this case the archpower-2025.02.01-powerpc64.iso). There is an issue where grub boot menu will pop up, but when you run any option such as `Boot LiveCD (kernel: ppc64)` or `Boot LiveCD (kernel: ibmpower)` you will get this error: `error: couldn't claim memory` `error: you need to load the kernel first.` `Press any key to continue...` Then it will go back to the menu selection screen. This happens with other Linux distro's that has updated Grub to version 2.12 like Debian Ports. The debian-12.0.0-ppc64-NETINST-1.iso ran just fine but when the install ran updates at the end and updated GRUB to ver 2.12 it has the same issue. This error also happens on bare metal and through PowerVM/VIOS (a AIX based hypervisor). I also tried running to boot the CD through yaboot through the open firmware prompt but yaboot just passes back to grub defeating the workaround. Any help would be great, Thank you
kth5 commented 2025-03-03 19:23:08 +00:00 (Migrated from github.com)
Copy Link

This is an interesting box I have next to no experience with. However, the boot options you mention do not sounds like it loaded the ArchPOWER grub.cfg. There is no option LiveCD or a ibmpower kernel.

Are you sure it boots the CD/image and not some leftover OS?

As a side note, for the S822L we have no access to any entitlements. Then again, I installed it in PowerVM mode and Opal the same with blank disks and it was able to install the powerpc64 flavor from physical CD.

This is an interesting box I have next to no experience with. However, the boot options you mention do not sounds like it loaded the ArchPOWER grub.cfg. There is no option LiveCD or a ibmpower kernel. Are you sure it boots the CD/image and not some leftover OS? As a side note, for the S822L we have no access to any entitlements. Then again, I installed it in PowerVM mode and Opal the same with blank disks and it was able to install the powerpc64 flavor from physical CD.
WiiNewU commented 2025-03-03 19:31:49 +00:00 (Migrated from github.com)
Copy Link

It has no other OS installed, but there have been issues with IBM Power 7 and 8 servers recently regarding memory issues at boot. The grub issue also appears with the Gentoo iso. As well there are memory issues when booting Ubuntu 16.04 & 16.10 (the last Power BE versions of Ubuntu) and outside of Linux, with FreeBSD 14.1 BSD Source 1 BSD Source 2 BSD Source 3 . I did test the final version of openSUSE Tumbleweed for PPC64 BE but its widely known to be bad in general and does not work. I been trying to use Yaboot, but for some reason yaboot just passes on to grub when running the command boot cd:,\boot\yaboot in open firmware, as well boot cdrom:1,yaboot from the Gentoo wiki

When booting on bare-metal it gives some different menu options, but the two available give the same error as before.

It has no other OS installed, but there have been issues with IBM Power 7 and 8 servers recently regarding memory issues at boot. The grub issue also appears with the Gentoo iso. As well there are memory issues when booting Ubuntu 16.04 & 16.10 (the last Power BE versions of Ubuntu) and outside of Linux, with FreeBSD 14.1 [BSD Source 1](https://forums.freebsd.org/threads/freebsd-14-fails-to-boot-on-ibm-s814-lpar.91981/) [BSD Source 2](https://forums.freebsd.org/threads/freebsd-on-an-ibm-virtual-i-o-server-vios.53914/) [BSD Source 3](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279137) . I did test the final version of openSUSE Tumbleweed for PPC64 BE but its widely known to be bad in general and does not work. I been trying to use Yaboot, but for some reason yaboot just passes on to grub when running the command boot ` cd:,\boot\yaboot` in open firmware, as well `boot cdrom:1,yaboot` from the Gentoo wiki When booting on bare-metal it gives some different menu options, but the two available give the same error as before.
kth5 commented 2025-03-03 20:13:37 +00:00 (Migrated from github.com)
Copy Link

The only options you should see are:

ArchPOWER Install (ppc64)
ArchPOWER Install (serial hvc0 as console) (ppc64)

If you see any other options, it is not loading the correct grub & grub.cfg. Your yaboot issue may stem from the same source really.

The only options you should see are: ``` ArchPOWER Install (ppc64) ArchPOWER Install (serial hvc0 as console) (ppc64) ``` If you see any other options, it is not loading the correct grub & grub.cfg. Your yaboot issue may stem from the same source really.
WiiNewU commented 2025-03-03 20:18:26 +00:00 (Migrated from github.com)
Copy Link

Those two only options did appear, but only when running on bare-metal, within PowerVM many more options appeared for some reason. It looks like another bug, likely with PowerVM rather then Arch. The same error: couldn't claim memory does appear when you select either ArchPOWER Install (ppc64) or ArchPOWER Install (serial hvc0 as console) (ppc64) though.

Those two only options did appear, but only when running on bare-metal, within PowerVM many more options appeared for some reason. It looks like another bug, likely with PowerVM rather then Arch. The same `error: couldn't claim memory` does appear when you select either `ArchPOWER Install (ppc64)` or `ArchPOWER Install (serial hvc0 as console) (ppc64)` though.
kth5 commented 2025-03-03 20:30:46 +00:00 (Migrated from github.com)
Copy Link

Is there any way to get serial on the box/LPAR with the iso mounted?

Is there any way to get serial on the box/LPAR with the iso mounted?
WiiNewU commented 2025-03-03 20:37:07 +00:00 (Migrated from github.com)
Copy Link

There is, I did burn to a CD to run on bare metal and access through the serial cable. Is possible to write the iso to a USB flash drive and boot from it as well. I just cant get pass grub. Same applies when virtualisation within PowerVM that I can mount the iso virtually and access the console, just not pass grub.

There is, I did burn to a CD to run on bare metal and access through the serial cable. Is possible to write the iso to a USB flash drive and boot from it as well. I just cant get pass grub. Same applies when virtualisation within PowerVM that I can mount the iso virtually and access the console, just not pass grub.
mrbubzie commented 2025-03-08 13:20:11 +00:00 (Migrated from github.com)
Copy Link

I’m also running into issues with GRUB on regular PowerPC (big-endian) at the last step of generating the configuration file. I’ve been using Arch for 10 years, and just for my own sanity, I tried the same process on another system with a new partition table and fresh partitions, but it still just sits at generating the configuration file. I’ve used your installs for the last two years so I’m not new at this. But there is something up with grub…ya boot runs fine!

Image

I’m also running into issues with GRUB on regular PowerPC (big-endian) at the last step of generating the configuration file. I’ve been using Arch for 10 years, and just for my own sanity, I tried the same process on another system with a new partition table and fresh partitions, but it still just sits at generating the configuration file. I’ve used your installs for the last two years so I’m not new at this. But there is something up with grub…ya boot runs fine! ![Image](https://github.com/user-attachments/assets/cdb6c61f-1a24-42d3-a54d-329da81d0f2c)
kth5 commented 2025-03-10 17:08:03 +00:00 (Migrated from github.com)
Copy Link

Regarding the 720 server, there's a patch in Debian's grub that disables VSX for Grub in reference to POWWER7 and POWER6. I'm going to apply these and upload a package soon.

Regarding the 720 server, there's a patch in Debian's grub that disables VSX for Grub in reference to POWWER7 and POWER6. I'm going to apply these and upload a package soon.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
question
Further information is requested
wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kth5
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ArchPOWER/packages#110
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?