| View previous topic :: View next topic |
| Author |
Message |
Mallock
n00b
Joined: 19 Jan 2021
Posts: 2
|
 Posted: Wed Jan 20, 2021 8:17 am Post subject: Invalid Memory Access error on first Boot |
 |
|
Hi. I just got a late 2005 PowerMac G5 Dual 2.3 GHz (8GB RAM) and have been trying to install gentoo for the last couple of days. To make a long story short, everything was fine until I had to install the bootloader. I tried for two days to get Yaboot to work, eventually I abandoned that once I realized I could use GRUB instead. Grub installed successfully, but on first boot I got some interesting errors:
| Code: |
Detached machine type: 00000400
Error: You can't boot a kdump kernel from OF!
Invalid memory access at %SRR0: 00000000.02c8472c %SRR1: 10000000.00023838
|
At this point I got an OF prompt. Trying to boot again got me some more interesting errors:
| Code: |
0 > boot
Can't allocate space for $LORD buffer (load_base)
0 > boot hd:2,\\:tbxi
Can't allocate space for $LORD buffer (load_base)
|
I'm using a full, bloated/everything Linux kernel made from genkernel (that took hours to compile).
Here is some info about the install:
This is what ofpath reports is /dev/sda:
| Code: |
ht@0,f2000000/pci@9/k2-sata-root@c/k2-sata@1/disk@0:
|
This is potentially wrong, when in OF devalias reports that:
| Code: |
ht@0,f2000000/pci@9/k2-sata-root@c/k2-sata@0/disk@0:
|
is /dev/sda or hd:. It's the only hard disk connected to the computer. I have the original disk that came with the mac but I took it out because it was the first disk that the mac saw, so it was always hd:. The new disk uses the same SATA cable as the old disk, so it should be hd:.
fstab
| Code: |
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3
# filesystems. This just tells the kernel to use the ext4 driver.
#
# NOTE: You can use full paths to devices like /dev/sda3, but it is often
# more reliable to use filesystem labels or UUIDs. See your filesystem
# documentation for details on setting a label. To obtain the UUID, use
# the blkid(8) command.
#LABEL=boot /boot ext4 noauto,noatime 1 2
#UUID=58e72203-57d1-4497-81ad-97655bd56494 / ext4 noatime 0 1
#LABEL=swap none swap sw 0 0
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
UUID=ed24fb22-56c4-4503-86a4-3a924d5c1baa /boot ext2 defaults 0 0
UUID=59b781e1-cb6c-4559-a6fb-e7849de2657b / ext4 noatime 0 1
|
mac-fdisk output:
| Code: |
/dev/sda
# type name length base ( size ) system
/dev/sda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map
/dev/sda2 Apple_Bootstrap bootstrap 1600 @ 64 (800.0k) NewWorld bootblock
/dev/sda3 Apple_UNIX_SVR2 GBoot 33554432 @ 1664 ( 16.0G) Linux native
/dev/sda4 Apple_UNIX_SVR2 GRoot 943217072 @ 33556096 (449.8G) Linux native
Block size=512, Number of Blocks=976773168
DeviceType=0x0, DeviceId=0x0
|
The boot partition is so big because it was originally a swap partition that was converted into a boot partition when I found having a boot partition wasn't optional.
Also, when first booting to grub I get:
| Code: |
Welcome to GRUB!
No S-ATA port=1
No S-ATA port =1 Unknown command `configfile'.
|
After these error messages GRUB starts up as normal. |
|
| Back to top |
|
 |
Mallock
n00b
Joined: 19 Jan 2021
Posts: 2
|
| Posted: Fri Jan 22, 2021 8:15 pm Post subject: Fixed it |
|
|
| I fixed it. As stated above I used genkernel to build Linux; this time I just used `make g5_defconfig`, and that kernel worked. |
|
| Back to top |
|
|
kahuna
n00b
Joined: 21 Apr 2022
Posts: 10
Location: Alberta, Canada
|
| Posted: Thu Apr 21, 2022 4:25 am Post subject: |
|
|
Hi there,
First post here in years, actually.
Just wanted to say, thanks Mallock for posting your findings!
I had the exact same experience, trying to make it work with yaboot, it didn't... then try GRUB and see that ugly message "invalid memory access".
I'm recompiling the kernel as you suggested.
Thanks again! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on PPC
