From: Dmytro Bablinyuk <dmytro.bablinyuk@tait•co.nz>
To: Sung <mikegas@tm•net.my>
Cc: Robin Gilks <robin.gilks@tait•co.nz>,
linuxppc mail list <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Problem with starting up 2.4.21 kernel
Date: Tue, 22 Jul 2003 09:58:40 +1200 [thread overview]
Message-ID: <3F1C6210.1080800@tait.co.nz> (raw)
In-Reply-To: <1058776120.17484.24.camel@localhost.localdomain>
>
>
>Hav you solve this problem?? Can I know what wrong with it because my
>kernel also acting up the same about the samething.
>
Yes, we resolved this problem.
First of all there was problem with ramdisk - it should have a header.
We used this makefile to generate proper ramdisk.
initrd.mk:
STAGING_DIR=.
TARGET_DIR=root
#############################################################
#
# make an initrd image - assumes all the tools are available
#
#############################################################
# this comes from the u-boot project!!
MKIMAGE=/usr/bin/mkimage
MNTPOINT:=$(STAGING_DIR)/mnt
$(MNTPOINT):
mkdir -p $(MNTPOINT)
#############################################################
#
# Build the ramfs root filesystem image
#
#############################################################
ramdisk.image.gz: $(TARGET_DIR) $(MNTPOINT)
dd if=/dev/zero of=ramdisk.img bs=1024 count=2048
/sbin/mkfs.ext2 -N 500 ramdisk.img -F
sudo mount -o loop ramdisk.img $(MNTPOINT)
cp -R $(TARGET_DIR)/* $(MNTPOINT)
sudo umount $(MNTPOINT)
cat ramdisk.img | gzip -9 -c > ramdisk.image.gz
rm -f ramdisk.img
initrd: ramdisk.image.gz
$(MKIMAGE) -n 'Simple Ramdisk Image' \
-A ppc -O linux -T ramdisk -C gzip \
-d ramdisk.image.gz initrd
rm -f ramdisk.image.gz
Call it "make -f initrd.mk initrd"
You should get a initrd file as output of this makefile - this what you
want. You just need to pick up a mkimage from u-boot project.
Also you should pass clocks in HZ. For this make sure that you have
undefined in u-boot clocks_in_*mhz* environment variable. Use printenv
in u-boot to make sure it is not present.
When you will get to the point when you start a busybox (if you use one)
then it could stuck if /dev has no all nodes required.
Hopefully this helps.
>After "Transferring control to Linux (at address 00000000)" nothing seems happen (see below).
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-21 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 4:51 Problem with starting up 2.4.21 kernel Dmytro Bablinyuk
2003-07-09 5:06 ` None Atall
2003-07-09 5:44 ` Dmytro Bablinyuk
2003-07-09 5:55 ` Dean Matsen
2003-07-09 7:14 ` None Atall
2003-07-21 8:28 ` Sung
2003-07-21 21:58 ` Dmytro Bablinyuk [this message]
2003-07-21 22:12 ` Robin Gilks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F1C6210.1080800@tait.co.nz \
--to=dmytro.bablinyuk@tait$(echo .)co.nz \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mikegas@tm$(echo .)net.my \
--cc=robin.gilks@tait$(echo .)co.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox