MVME3100 and linux-2.6.10

MVME3100 and linux-2.6.10

[vittorio barulli]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3320 bytes --]

I have a PowerPc Motorola, I install on it a kernel image (2.6.10) that
use a ramdisk as root filesystem.
The original version issued with kernel 2.6.10 is working even if I
recompile it.

Now I want to modify the original ramdisk to insert some file that I
need. If I insert in the ramdisk some little file the kernel continue
to start, but if i insert a great file (4 Mb) the kernel don't boot.
the result on video is:

loaded at:     01864400 0253356C
relocated to:  00400000 010CF16C
board data at: 010CD124 010CD16C
relocated to:  00405238 00405280
zimage at:     00405A05 005BA5C2
initrd at:     005BB000 010CC420
avail ram:     010D0000 AACC8A8B

Linux/PPC load: console=ttyS0,9600 root=/dev/ram0 ramdisk_size=64000
ramdisk_blocksize=1024
Uncompressing Linux...done.
Now booting the kernel

At this point the system is stopped.
The next line describe what I do to modify the ramdisk and to compile
the kernel.

Mounting ramdisk:

gunzip /usr/src/linux-2.6.10.rm02/arch/ppc/boot/images/ramdisk.image.gz
losetup /dev/loop0
/usr/src/linux-2.6.10.rm02/arch/ppc/boot/images/ramdisk.image
mount  /dev/loop0 /opt/commcpu/CommEnvironment/ -o loop -t ext2

Unmounting ramdisk:
umount /opt/commcpu/CommEnvironment/
losetup -d /dev/loop0
fsck /usr/src/linux-2.6.10.rm02/arch/ppc/boot/images/ramdisk.image
gzip -9 /usr/src/linux-2.6.10.rm02/arch/ppc/boot/images/ramdisk.image

Compiling kernel:

cd /usr/src/linux-2.6.10.rm02/
export ARCH=ppc
export CROSS_COMPILE=ppc-
make zImage.initrd 




--------------------------------------------------------------------------------
INFORMATIVA SULLA PRIVACY
Le informazioni contenute nella presente comunicazione e i relativi allegati
possono essere riservate e sono, comunque, destinate esclusivamente alle persone
o alla Società sopraindicate.
La diffusione, distribuzione e/o copiatura del documento trasmesso da parte di 
qualsiasi soggetto diverso dal destinatario è proibita, sia ai sensi 
dell.art. 616 c.p. , che ai sensi del D.Lgs. n. 196/2003. 
Se avete ricevuto questo messaggio per errore, vi preghiamo di distruggerlo e di
informarci immediatamente per telefono allo 0735/59051 o inviando un messaggio 
all'indirizzo e-mail privacy@gemrad.com (all' attenzione ing. Giovanni Lazzeri).


The information in this e-mail (which includes any files transmitted with it) 
is confidential and may also be legally privileged. 
It is intended for the addressee only. Access to this e-mail by anyone else is 
unauthorised.It is not to be relied upon by any person other than the addressee, 
except with our prior written approval. If no such approval is given, we will 
not accept any liability (in negligence or otherwise) arising from any third 
party acting, or refraining from acting on such information. 
Unauthorised recipients are required to maintain confidentiality. 
If you have received this e-mail in error please notify us immediately 
(privacy@gemrad.com),destroy any copies and delete it from your computer system. 
Any use, dissemination, forwarding, printing or copying of this e-mail is 
prohibited. 
Copyright in this e-mail and any document created by us will be and remain 
vested in us and will not be transferred to you. 
We assert the right to be identified as the author of and to object to any 
misuses  of the contents of  this e-mail or such documents.

Re: MVME3100 and linux-2.6.10

[Thomas Feller]

vittorio barulli wrote:
> I have a PowerPc Motorola, I install on it a kernel image (2.6.10) that
> use a ramdisk as root filesystem.
> The original version issued with kernel 2.6.10 is working even if I
> recompile it.
>
> Now I want to modify the original ramdisk to insert some file that I
> need. If I insert in the ramdisk some little file the kernel continue
> to start, but if i insert a great file (4 Mb) the kernel don't boot.
> the result on video is:
>
> loaded at:     01864400 0253356C
> relocated to:  00400000 010CF16C
> board data at: 010CD124 010CD16C
> relocated to:  00405238 00405280
> zimage at:     00405A05 005BA5C2
> initrd at:     005BB000 010CC420
> avail ram:     010D0000 AACC8A8B
>   
The last line here looks wrong. It should be someting like 10000000 (256
MB) or 20000000 (512 MB). Not AACC8A8B which is ~ 2732,783 MB.
I've noticed that this only works right with gcc < 4.1. It seemed like
they did change some things in ld.
> Linux/PPC load: console=ttyS0,9600 root=/dev/ram0 ramdisk_size=64000
> ramdisk_blocksize=1024
> Uncompressing Linux...done.
> Now booting the kernel
>   
That is where my kernel stops to boot too!!!
Is there someone out there who can tell us, what we did wrong?

Regards,
    Thomas

Re: MVME3100 and linux-2.6.10

[Thomas Feller]

vittorio barulli wrote:
> I have a PowerPc Motorola, I install on it a kernel image (2.6.10) that
> use a ramdisk as root filesystem.
> The original version issued with kernel 2.6.10 is working even if I
> recompile it.
>
> Now I want to modify the original ramdisk to insert some file that I
> need. If I insert in the ramdisk some little file the kernel continue
> to start, but if i insert a great file (4 Mb) the kernel don't boot.
> the result on video is:
>
> loaded at:     01864400 0253356C
> relocated to:  00400000 010CF16C
> board data at: 010CD124 010CD16C
> relocated to:  00405238 00405280
> zimage at:     00405A05 005BA5C2
> initrd at:     005BB000 010CC420
> avail ram:     010D0000 AACC8A8B
>   
The last line here looks wrong. It should be someting like 10000000 (256
MB) or 20000000 (512 MB). Not AACC8A8B which is ~ 2732,783 MB.
I've noticed that this only works right with gcc < 4.1. It seemed like
they did change some things in ld.
> Linux/PPC load: console=ttyS0,9600 root=/dev/ram0 ramdisk_size=64000
> ramdisk_blocksize=1024
> Uncompressing Linux...done.
> Now booting the kernel
>   
That is where my kernel stops to boot too!!!
Is there someone out there who can tell us, what we did wrong?

Regards,
    Thomas

Re: MVME3100 and linux-2.6.10

[ST]

Hi
> That is where my kernel stops to boot too!!!
> Is there someone out there who can tell us, what we did wrong?
Magnus Hjorth told us that "Early serial boot msgs" lead to a kernel crash.
Probably switch these of and give it a try?
ST