Re: Call for testers: new yaboot package release - power5 installation
Thanks for the suggests, I'm going to change to sid.
As I dont like to give up, some further investigation made me clear
that mkofboot is a link to /ybin instead of simply ybin. After
rebooted in rescue mode, and running ybin manually, prep part. has
been set up properly and now the system boots from HD happily without
any issue. There was no need to change anything else. /etc/yaboot.conf
was created well.
Previous 1.3.13.a1 worked well.
And one experience to share regarding to OF. Sometimes the installer
cannot start due to ramdisk error "ran out of compressed data".
Example at http://us.generation-nt.com/ramdisk-ran-out-compressed-data-p550-help-170281631.html
I've searched almost the full Internet without success and at last,
one of my friend (an IBM hw expert) told me that frequent installation
can fill the NVRAM.
So, before PPC installation I had to free it with these commands in OF
(it performs a partiton reboot) :
Donno whether I should address it to the kernel team, but at least I
informed those who read this maillist :)
But, back to yaboot. Benjamin, can you please provide your git-url?
I'm going to create another ISO and I gladly package it.
On Tue, Oct 5, 2010 at 5:38 PM, Benjamin Cama <firstname.lastname@example.org> wrote:
> Le mardi 05 octobre 2010 à 15:12 +0200, Zsombor a écrit :
>> Oct 5 14:11:33 yaboot-installer: chroot: can't execute 'mkofboot': No
>> such file or directory
> This is a packaging mistake, already reported here, and fixed in my git
> repo. But the package is not up to date.
>> I included the official 2.6.32-5-powerpc64 kernel. Should I compile a
>> custom one?
> Not needed, it's just a stupid mistake of mine.
>> Retrying kernel-install on prep succeeded but the machine cannot boot
>> from harddisk:
>> Elapsed time since release of system processors: 116 mins 52 secs
>> DEFAULT CATCH!, exception-handler=fff00400
>> at %SRR0: 00000000c0000000 %SRR1: 0000000008003002
>> Open Firmware exception handler entered from non-OF code
>> Client's Fix Pt Regs:
>> 00 0000000000000000 00000000018fffe0 0000000000000000 0000000000000000
>> 04 0000000000000000 0000000000c39a48 0000000000000000 0000000000000000
>> 08 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> 0c 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> 10 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> 14 0000000000c00000 0000000000000008 0000000000000000 0000000000000000
>> 18 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> 1c 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> Special Regs:
>> %IV: 00000400 %CR: 00000000 %XER: 00000000 %DSISR: 00000000
>> %SRR0: 00000000c0000000 %SRR1: 0000000008003002
>> %LR: 0000000000000000 %CTR: 0000000000000000
>> %DAR: 0000000000000000
>> Virtual PID = 0
>> PFW: Unable to send error log!
>> 0 >
>> Do you have any advise? Maybe I missed something from the installer?
> Wow, no idea. I'm just merging patches and adding packaging, but I'm no
> expert in OF things. Did the previous yaboot (1.3.13a) work ?