quik-1.3.1and 2.2.16_pmac-stable ?

quik-1.3.1and 2.2.16_pmac-stable ?

[Claus Enneper]

hi,
I'm happy with a 2.2.15pre14, mol-patched on a PB3400, booting with
the help of quik-1.3.1-0a.ppc.rpm,

rsync'ed 2.2.16 two days ago, built it with the same config, but got
this error in OF:
DEFAULT CATCH!, Code=FFF00300 at   %SRR0: 0014B008  %SRR1: 00003070

any hints?

Thanks
Claus

--
Yours, ce

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: quik-1.3.1and 2.2.16_pmac-stable ?

[Claus Enneper]

PB3400

 >rsync'ed 2.2.16 two days ago, built it with the same config, but got
 >this error in OF:
 >DEFAULT CATCH!, Code=FFF00300 at   %SRR0: 0014B008  %SRR1: 00003070

hi,
in '/usr/src/linux-pmac-stable/arch/ppc/kernel/prom.c' line 431:
	/* Find the OF version */
	prom_op = call_prom(RELOC("finddevice"), 1, 1, RELOC("/openprom"));
	RELOC(prom_version) = 0;
	if (prom_op != (void*)-1) {
	    char model[64];
	    int sz;
	    sz = (int)call_prom(RELOC("getprop"), 4, 1, prom_op, RELOC("model"), model, 64);
	    if (sz > 0) {
		if ( strncmp(model,RELOC("IBM"),3) ) {
	    	    char *c;
		    for (c = model; *c; c++)
		        if (*c >= '0' && *c <= '9') {
			    RELOC(prom_version) = *c - '0';
			    break;
		        }
		} else
		    chrp = 1;
	    }
	}
	if (RELOC(prom_version) >= 3)
		prom_print(RELOC("OF Version 3 detected.\n"));

all (prom_version) have their RELOC, so that's not the point.
unfortunatly, I'm not able to make a diff to 2.2.15pre14 to see the difference.

Thanks for any other hint.
--
Yours, ce

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: quik-1.3.1and 2.2.16_pmac-stable ?

[Benjamin Herrenschmidt]

On Sat, Jun 17, 2000, Claus Enneper <cl.en@gmx.net> wrote:

>
>all (prom_version) have their RELOC, so that's not the point.
>unfortunatly, I'm not able to make a diff to 2.2.15pre14 to see the
>difference.


Ah, yes, it's a different issue. You should probably use a more recent
quik (2.0+) to work with recent kernels. Old quik doesn't like the new
kernel entry point (without the pseudo-xcoff hack).


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: quik-1.3.1and 2.2.16_pmac-stable ?

[Claus Enneper]

 >:
 >: Ah, yes, it's a different issue. You should probably use a more recent
 >: quik (2.0+) to work with recent kernels. Old quik doesn't like the new
 >: kernel entry point (without the pseudo-xcoff hack).

is there any binary available?
quik-2.0-0d.src.rpm from Yellow Dog Linux <bugs@terraplex.com> complains:

make[1]: Entering directory `/usr/src/redhat/BUILD/quik-2.0/util'
gcc -O2 -o elfextract elfextract.c
In file included from /usr/include/linux/elf.h:5,
                 from elfextract.c:7:
/usr/include/asm/elf.h:43: parse error before `elf_vrreg_t'
/usr/include/asm/elf.h:43: warning: data definition has no type or storage class/usr/include/asm/elf.h:44: parse error before `elf_vrregset_t'
/usr/include/asm/elf.h:44: warning: data definition has no type or storage classmake[1]: *** [elfextract] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/quik-2.0/util'
make: *** [all] Error 1
Bad exit status from /var/tmp/rpm-tmp.35142 (%build)

--
Yours, ce

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: quik-1.3.1and 2.2.16_pmac-stable ?

[Daniel Jacobowitz]

On Sat, Jun 17, 2000 at 02:20:46AM +0200, Claus Enneper wrote:
>
>  >:
>  >: Ah, yes, it's a different issue. You should probably use a more recent
>  >: quik (2.0+) to work with recent kernels. Old quik doesn't like the new
>  >: kernel entry point (without the pseudo-xcoff hack).
>
> is there any binary available?
> quik-2.0-0d.src.rpm from Yellow Dog Linux <bugs@terraplex.com> complains:
>
> make[1]: Entering directory `/usr/src/redhat/BUILD/quik-2.0/util'
> gcc -O2 -o elfextract elfextract.c
> In file included from /usr/include/linux/elf.h:5,
>                  from elfextract.c:7:
> /usr/include/asm/elf.h:43: parse error before `elf_vrreg_t'
> /usr/include/asm/elf.h:43: warning: data definition has no type or storage class/usr/include/asm/elf.h:44: parse error before `elf_vrregset_t'
> /usr/include/asm/elf.h:44: warning: data definition has no type or storage classmake[1]: *** [elfextract] Error 1
> make[1]: Leaving directory `/usr/src/redhat/BUILD/quik-2.0/util'
> make: *** [all] Error 1
> Bad exit status from /var/tmp/rpm-tmp.35142 (%build)

Grab the .orig.tar.gz and .diff.gz from a Debian mirror (under
dists/potato/main/source/base/*).

And can someone please fix that vrreg_t bug?  Vector128 is only defined
if __KERNEL__, so elf_vrreg_t should only be defined if __KERNEL__.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: quik-1.3.1and 2.2.16_pmac-stable ?

[Claus Enneper]

>
>
>Grab the .orig.tar.gz and .diff.gz from a Debian mirror (under
>dists/potato/main/source/base/*).

yes, did it, patched, and compiled fine.
but I did not check the source, so got errors like 'unable to open filesystem'.
is it possible that quik moved to chrp in an pmac_pb3400_incompatible manner?
anyway, for me user it's not usable ( I was happy with quik since 1998);
I will give bootx-1.2.2 a try .

--
Yours, ce

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/