Thanks Quentin,
That was exactly it! In my grub.conf I had the root partition wrong.
Now it boots, and I'm on to my next mission: Add wireless tools to
support my wireless network card (D-Link DWL-520)
Michael
On Tue, 14 Jun 2005, Quentin Arce wrote:
--- [EMAIL PROTECTED] wrote:
Hi Yuri, Heath, Gentoo-embedded folks:
I've taken your suggestion, Heath, and built a 2.6
kernel (instead of
the 2.4 I made by accident), and I've followed
version 0.6 of your HOWTO
with Yuri's comments.
Grub loads, finds the kernel, and booting starts,
but it doesn't go all
the way:
warning: unable to open an initial console
kernel panic: no init found
I had this exact error for a while with a 2.6 kernel
and using syslinux to boot. It turned out I had the
wrong root device. The naming changed between my
image build system and the real system. I'm assuming
you are building an embedded system for some old
hardware and it's not really an embedded system.
my 1.5 cents
Q
(That's not an exact quote). I've checked that my
kernel's .config
includes consoles, and that /dev/console exists and
is linked to
character device 5,1.
I haven't done a whole lot of research into this yet
but wonder if
anything springs to your collective minds.
As usual, any comments appreciated and any
suggestions entertained.
Michael
On Mon, 6 Jun 2005, Yuri Vasilevski wrote:
Hi,
On Mon, 6 Jun 2005 10:03:26 -0500
Heath H Holcomb <[EMAIL PROTECTED]> wrote:
Version 0.06
Please add, delete, modify. Thanks!
Just some things that came to my mind with respect
to this
version.
This procedure produces a working embedded
rootfs, that boots form a hard
drive on a Geode based SBC (single board
computer); at least on my
development system.
I've update my website with this version also.
http://www.bulah.com/embeddedgentoo.html
#--------------------------------------------------------------------------------
# Embedded Gentoo How-To for x86
#
# A how-to guide to setup a Gentoo embedded
environment, you must be root.
# These commands are to be run on your
development system,
# any x86 Gentoo Linux computer will do. The
system should be fast,
# to speed development. The target can be any
x86 based SBC. I'm
# using a Geode based SBC. Latter I'll use a Via
based SBC.
#
# version 0.06
# 2005.6.6
#
# Heath Holcomb (heath at bulah.com)
# Ned Ludd (embedded Gentoo project lead,
original commands posted)
# Lloyd Sargent (contributor)
# Yuri Vasilevshi (contributor)
It's Vasilevski :-)
# Mike George (contributor)
# Kammi Cazze (contributor)
# Marius Schaefer (contributor)
#
# Definitions and Terms
# system_rootfs = your regular rootfs
# development_rootfs = what you use to build the
embedded_rootfs
# embedded_rootfs = rootfs you deploy to the
target system
# SBC = single board computer (here it's an x86
based)
#
# References
# http://www.gentoo.org/doc/en/handbook/index.xml
# http://www.epiawiki.org
# http://epia.kalf.org
# Gentoo embedded mailing list
([email protected])
#
#
# Overview of process (steps)
# 1 - Prepare the development_rootfs from your
system_rootfs
# 2 - Build the development_rootfs
# 3 - Build the embedded_rootfs
# 4 - Build and install non-system programs to
the embedded_rootfs
# 5 - Build and install a kernel to the
embedded_rootfs
# 6 - Deploy embedded_rootfs to target
#
#--------------------------------------------------------------------------------
#----- Step 1 - Prepare the development_rootfs
from your system_rootfs -------
# You must be root.
su -
# Create the development_rootfs.
# I use i586 because of target is a Geode
processor.
mkdir -p
/opt/i586-gentoo-uclibc-linux/usr/portage
# Download the latest stage 1 tarball.
wget \
http://gentoo.osuosl.org/experimental/x86/embedded/stages/stage1-x86-uclibc-2005.0.tar.bz2
# Untar the stage to the development_rootfs.
tar -xvjf stage1-x86-uclibc-2005.0.tar.bz2 -C
/opt/i586-gentoo-uclibc-linux/
it should be tar -xvjpf ...
where -p stands for --preserve-permissions
# Mount the proc and portage directories to your
development_rootfs.
# Makes your system_rootfs's proc and portage
directory available from inside
# of your development_rootfs (after chrooting).
mount --bind /proc
/opt/i586-gentoo-uclibc-linux/proc/
mount --bind /usr/portage
/opt/i586-gentoo-uclibc-linux/usr/portage
# Copy over DNS information to the
development_rootfs.
cp /etc/resolv.conf
/opt/i586-gentoo-uclibc-linux/etc/resolv.conf
# Chroot into the development_rootfs.
chroot /opt/i586-gentoo-uclibc-linux /bin/bash
--login
#----- Step 2 - Build the development_rootfs
---------------------------------
# Create new environment and load variables into
memory.
env-update
source /etc/profile
# Modify make.conf file to your liking/needs.
nano -w /etc/make.conf
# This is for my target, Geode x86 processor.
/*
USE="bitmap-fonts minimal truetype-fonts uclibc
mmx"
The uclibc USE flag was obsoleted, see:
http://www.mail-archive.com/[email protected]/msg00140.html
CHOST="i586-gentoo-linux-uclibc"
CFLAGS="-march=i586 -Os -pipe
-fomit-frame-pointer -mmmx"
CXXFLAGS="${CFLAGS}"
FEATURES="buildpkg"
VIDEO_CARDS="chips"
UCLIBC_CPU="586MMX"
*/
# Set profile to use 2.6 kernel.
# The current stage uses 2.4 by default, and for
most cases you are going
# to want a 2.6.x kernel.
rm /etc/make.profile
This are equivalent but I would use:
unlink /etc/make.profile
for clarity's sake.
ln -s /usr/portage/profiles/uclibc/x86
/etc/make.profile
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
[email protected] mailing list
--
[email protected] mailing list
