[Debian-ppc64-devel] Re: Package: installation-reports

[John Engel]

hi Frank,

   I installed on a few different POWER5 systems last week and ran into the same problem you have reported.  After installation, I was able to chroot into the installed system and create a PREP partition using cfdisk.  I then dd'ed the yaboot binary to this partition and created my yaboot.conf.  I also had to modify the /etc/securetty and /etc/inittab on partitions that used an hvc and hvsi console.  I will get my installation reports submitted soon to help out.  

   ... John
  

On  0, Frank van Berkel <frank at linux-os.nl> wrote:
> 
> Hi Sven,
> 
> >Indeed, and i believe that is your problem :
> >
> >        { "CHRP IBM,7028-6C4", "chrp_rs6k" },
> >        { "CHRP IBM,7029-6E3", "chrp_rs6k" },
> >        { "CHRP IBM,7038-6M2", "chrp_rs6k" },
> >        { "CHRP IBM,7039-651", "chrp_rs6k" },
> >        { "CHRP IBM,7040-681", "chrp_rs6k" },
> >        { "CHRP IBM,7044-270", "chrp_rs6k" },
> >        { "CHRP IBM,7046-B50", "chrp_rs6k" },
> >        { "CHRP IBM,8842-21X", "chrp_rs6k" },
> >        { "CHRP IBM,9111-520", "chrp_rs6k" },
> >        { "CHRP IBM,9113-550", "chrp_rs6k" },
> >        { "CHRP IBM,9117-570", "chrp_rs6k" },
> >        { "CHRP IBM,9124-720", "chrp_rs6k" },
> >
> >I think this rule is ridiculous, and that all CHRP IBM can be marked as
> >chrp_rs6k, or maybe we should change this to chrp_ibm, or something.
> >
> >Mmm, will investigate and fic.
> 
> Is there any view on when it will be fixed?
> 
> Regards,
> 
> 
> Frank
> 
> _______________________________________________
> Debian-ppc64-devel mailing list
> Debian-ppc64-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/debian-ppc64-devel