All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Boyanov" <kkboyanov@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Building custom 2.6 kernel
Date: Mon, 1 May 2006 11:54:21 +0200	[thread overview]
Message-ID: <929bf310605010254j5b9afccdw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]

Hi there,

These days I'm trying to compile and get working a 2.6 kernel for the
Motorola MVME6100 VME single board computer. For the purpose I'm using an
ELinOS IDE by the SysGo company (don't ask me why, it's the boss' decision).
Since ELinOS lacks support I post here with the hope of getting some help.
Thus far I have succeeded in only compiling a bare kernel but not getting it
up. There is a running RedHat distro on the board but I want to get a
customized cernel for it, because RedHat does not support certain stuff
(like VME drivers for example).
So, the kernel I compiled seems to be quite messy, as you can see from the
dmesg at startup:

The existing kernel >>
http://www-zeuthen.desy.de/~boyanov/dmesg_normal.txt<http://www-zeuthen.desy.de/%7Eboyanov/dmesg_normal.txt>
The new one          >>
http://www-zeuthen.desy.de/~boyanov/dmesg_failed.txt<http://www-zeuthen.desy.de/%7Eboyanov/dmesg_failed.txt>

As you can see in the links above the kernel panics because of insufficient
"init" part of the command line passed to it. Another issue is the SCSI
hard-disk initialization and RAM disk creation. I forgot to mention, because
this is only a test kernel I just want basic functionality included, as I
tried to do so in the kernel configuration.
But nevertheless i failed to do so.
I'm actually only asking for some advice and tips (especially where to find
information on the web, if there is any) on the problems occuring, or if
someone has encountered such problems in the past and is willing to share
his/her experience.
I'm quite newbie to this stuff, and as such I'm really confused about what's
going on...
So any help and advice is appreciated.

Best regards,
Konstantin

[-- Attachment #2: Type: text/html, Size: 2034 bytes --]

                 reply	other threads:[~2006-05-01  9:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=929bf310605010254j5b9afccdw@mail.gmail.com \
    --to=kkboyanov@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.