Re: powerpc/sparc problems

[rubisher]

Bean wrote:
> On Sat, Oct 24, 2009 at 4:34 AM, rubisher <address@hidden> wrote:
[snip]
> > As it seems that you have some experience with powerpc, may be can you
> > advise me with some your tips (how did you build your image, a sample of one
> > your menuentry?): I also tried to follow recipe of
> > <http://grub.enbug.org/TestingOnPowerPC> i.e.
> > # cd /usr/lib/grub/powerpc-ieee1275 (where *.mod stand)
> > # /usr/bin/grub-mkelfimage -n --directory=/usr/lib/grub/powerpc-ieee1275
> > --output=/boot/grub/grubof.modules *.mod
> > (-n for pseries) but this image sadely make panicing ofs:
> > DEFAULT CATCH!, exception-handler=fff00300
> > at   %SRR0: 0000000000c3c25c   %SRR1: 800000000000b002
> > Call History
> > ------------
> > @  - c3c1f0
> > close-package  - c58060
> > (poplocals)  - c3a758
> > (init-program)  - c7e298
> > boot  - c7ec7c
> > evaluate  - c4a638
> > invalid pointer - d83655
> > invalid pointer - f
> > invalid pointer - f
> > catch  - c38fe8
> > bt-task-boot-on-this  - d140d8
> > (poplocals)  - c3a758
> > catch  - c38fe8
> > execute-device-method  - c58bcc
> > (poplocals)  - c3a758
> > (select-boot-seq)  - c59ba4
> >
> > Client's Fix Pt Regs:
> > Client's Fix Pt Regs:
> >  00 00100000000001f4 ffffffffffffffff 00000000deadbeef fffffffffffffffc
> >  04 0000000000000000 0000000000000000 0000000000000000 0000000000000001
> >  08 0000000000001000 0000030002001000 0000000000000003 0000000000007000
> >  0c 0000000022800000 0000000000c17100 0000000000c18000 000000000009c4b0
> >  10 0000000000db8c20 0000000000db8939 0000000000c57d80 0000000000c58060
> >  14 0000000000000000 ffffffffffffffff 0000000000000000 0000000000000000
> >  18 0000000000c13000 0000000000c38000 0000000000c14d40 0000000000c16ec0
> >  1c 0000000000c20000 0000000000c3fdf0 0000000000c11ea0 0000000000c10fa8
> > Special Regs:
> >    %IV: 00000300     %CR: 84800000    %XER: 20000008  %DSISR: 08000000
> >  %SRR0: 0000000000c3c25c   %SRR1: 800000000000b002
> >    %LR: 0000000000c3c1f0    %CTR: 0000000000000000
> >   %DAR: ffffffffffffffff
> > Virtual PID = 0
> >  ofdbg
> >
> > At this point I am worry that the change of optimization compile option (-Os
> > -> -O0) break something or am I facing to some issue related to my ofs or
> > something else in config file (e.g. I just figure out that I didn't change
> > my grub.cfg with the usage of lasetest describe image grubof.modules: I
> > didn't remove the 'insmod ext2', thought?)
>
> Hi,
>
> Don't include all modules, the boot image seems to be broken when it
> exceed certain size. The following list should be enough:
>
> minicmd fat part_msdos normal sh ls linux
>
> in the grub shell, use ls command to list detected devices.
Thanks;

at least i didn't encountered anymore ofs panic but in grub rescue sheel 'ls' 
just return an empty line;
I can just grab 'lsmod' info:
sh:grub> lsmod
Name    Ref Count       Dependencies
linux   1               boot,elf
elf     2               gzio
gzio    3
ls      1               normal,extcmd
extcmd  2
sh      1               normal
normal  4               boot
boot    6
part_msdos      1
fat     1
minicmd 1

but if I try to add another module (e.g. scsi or what else) it always respond:
"error: invalid arch independent ELF magic"