Re: initrd fails load with "ERROR: claim of 0xfe49172 in range 0x1340000-0x10000000 failed"
On Sun, Mar 4, 2018 at 4:11 AM, Dennis Clarke <dc@oetec.com> wrote:
>
> Dear PPC types :
>
> So I carefully built kernel 4.15.6 and created the needed
> initrd.img-4.15.6 in /boot with update-initramfs and checked it
> carefully against the pre-existing initrd.img-4.13.0-1-powerpc64 for
> Debian buster/sid. Everything looks great and my objective was to
> poke around the RFI flush of L1-D cache issue. Which may exist. No
> one really knows ( yet ):
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa8a5e0062ac940f7659394f4817c948dc8c0667
>
> I had to take a picture of the screen but really it seems to say that my
> new initrd will not load into memory for some reason. Perhaps too darn
> big? This is an old yet well loved PowerMac G5 and I am wondering if
> there is an nvram or maybe an openfirmware command magic incantation to
> utter? I have 8G of memory and surely no reason to not load in a very
> large initrd image?
Maybe I am missing the whole point here. But why don't you built the
bindeb target ?
(not tested):
make ARCH=powerpc g5_defconfig
make ARCH=powerpc CROSS_COMPILE=powerpc64-linux-gnu- bindeb-pkg
When you dpkg -i the package, make sure the initrd / vmlinux links are
updated (I do ln -sf manually).
> What I see on the screen seems fairly clear :
>
> Welcome to yaboot version 1.3.17
> Enter "help" to get some basic usage information
> boot: Linux
> Please wait, loading kernel...
> Elf64 kernel loaded...
> Loading ramdisk...
> ERROR: claim of 0xfe49172 in range 0x1340000-0x10000000 failed
> Claim failed for initrd memory
> ramdisk load failed !
>
> Apple PowerMac11,2 5.2.7f1 BootROM built on 09/30/05 at 15:31:03
> Copyright 1994-2005 Apple Computer, Inc.
> All Rights Reserved.
>
> Welcome to Open Firmware, the system time and date is: 03/03/2018 23:31:47
>
>
> etc etc and the usual "0 >" prompt wherein I went looking for nvram
> data with printenv. I won't retype all that. I am hoping that the
> variable load-base may be of help here.
>
> Any thoughts?
>
>
> Dennis
>
> ps: yaboot conf is trivial :
>
>
>
> nix# cat /etc/yaboot.conf
> ## yaboot.conf generated by debian-installer
> ##
> ## run: "man yaboot.conf" for details. Do not make changes until you have!!
> ## see also: /usr/share/doc/yaboot/examples for example configurations.
> ##
> ## For a dual-boot menu, add one or more of:
> ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
>
> boot="/dev/disk/by-id/ata-Hitachi_HDS725050KLA360_KRVN23ZAHA5DBD-part2"
> device=/ht@0,f2000000/pci@9/k2-sata-root@c/@0/@0
> partition=3
> root="/dev/sda3"
> timeout=50
> install=/usr/lib/yaboot/yaboot
> magicboot=/usr/lib/yaboot/ofboot
> enablecdboot
>
> image=/boot/vmlinux
> label=Linux
> read-only
> initrd=/boot/initrd.img
>
> image=/boot/vmlinux.old
> label=old
> read-only
> initrd=/boot/initrd.img.old
> nix#
>
> However I did add in these :
>
> nix# diff /etc/yaboot.conf_20180303232549 /etc/yaboot.conf
> 20a21,22
>> append="verbose ipv6.disable=1"
>> pause-after
> nix#
>
Reply to: