From: "Grant Likely" <grant.likely@secretlab.ca>
To: schardt <g.schardt@fz-juelich.de>
Cc: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: Newbie and linux on virtex-II ppc
Date: Wed, 29 Aug 2007 08:44:52 -0600 [thread overview]
Message-ID: <fa686aa40708290744w261adfe8ya617a045e4860656@mail.gmail.com> (raw)
In-Reply-To: <46D5753C.70702@fz-juelich.de>
On 8/29/07, schardt <g.schardt@fz-juelich.de> wrote:
> me again :)
>
> i added a /dev/ttyUL0 (mknod ttyUL0 c 204 187) device and and a console
> link to it.
Yeah, you don't want a symlink, you want a console device node instead:
mknod /dev/tty 5 0
mknod /dev/console 5 1
> no warning anymore, but i think i'm listen on the "wrong" console ??? i
> see bootmessages
> and an errormessage from init ("init: can't open /dev/null: no such
> device or directory")
I would say you need to add a /dev/null device node, or fix it's
permissions. :-)
mknod /dev/null 1 3
>
> but the messages from init.d/rcS did not appear
>
> this is my inittab (from klingauf mkrootfs):
>
> ::sysinit:/etc/init.d/rcS
> ::askfirst:-/bin/sh
> ::ctrlaltdel:/sbin/reboot
> ::shutdown:/sbin/swapoff -a
> ::shutdown:/bin/umount -a -r
> ::restart:/sbin/init
> ::respawn:/sbin/getty 9600 tts/0
>
> Georg
>
> schardt wrote:
> > Step by step i becomes running :)
> >
> > kernel is booting, root-fs is mounting on systemace, busybox compiled
> > and rootfs installed (i used klingauf's mkrootfs)
> >
> > but now it says:
> > [ 2.964978] Freeing unused kernel memory: 92k init
> > [ 3.081332] Warning: unable to open an initial console.
> > [ 3.306406] request_module: runaway loop modprobe binfmt-4c46
> > [ 3.375612] request_module: runaway loop modprobe binfmt-4c46
> > [ 3.446800] request_module: runaway loop modprobe binfmt-4c46
> >
> > and i don't know what this is :(
> >
> > Can give me a hint, where to look ?
> >
> > thx
> > Georg
> >
> > Grant Likely wrote:
> >
> >> On 8/28/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> >>
> >>
> >>> On 8/28/07, schardt <g.schardt@fz-juelich.de> wrote:
> >>>
> >>>
> >>>> Okay, im really blind i think, so i started again :
> >>>>
> >>>> - 2.6.22 kernel from kernel.org
> >>>> - cp /arch/ppc/configs/ml300_defconfig .config
> >>>>
> >>>>
> >> BTW, "make ml300_defconfig" does this for you.
> >>
> >> g.
> >>
> >>
> >>
> >
> >
> >
> > -----------------------------------------------------------------------=
------------------
> > -----------------------------------------------------------------------=
------------------
> > Forschungszentrum J=FClich GmbH
> > 52425 J=FClich
> >
> > Sitz der Gesellschaft: J=FClich
> > Eingetragen im Handelsregister des Amtsgerichts D=FCren Nr. HR B 3498
> > Vorsitzende des Aufsichtsrats: MinDirig'in B=E4rbel Brumme-Bothe
> > Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (ste=
llv.
> > Vorsitzender)
> > -----------------------------------------------------------------------=
------------------
> > -----------------------------------------------------------------------=
------------------
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
> >
>
>
>
> -------------------------------------------------------------------------=
----------------
> -------------------------------------------------------------------------=
----------------
> Forschungszentrum J=FClich GmbH
> 52425 J=FClich
>
> Sitz der Gesellschaft: J=FClich
> Eingetragen im Handelsregister des Amtsgerichts D=FCren Nr. HR B 3498
> Vorsitzende des Aufsichtsrats: MinDirig'in B=E4rbel Brumme-Bothe
> Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stell=
v.
> Vorsitzender)
> -------------------------------------------------------------------------=
----------------
> -------------------------------------------------------------------------=
----------------
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-08-29 14:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 12:55 Newbie and linux on virtex-II ppc schardt
2007-08-27 13:09 ` Grant Likely
2007-08-27 14:17 ` schardt
2007-08-27 14:21 ` Grant Likely
2007-08-28 6:51 ` schardt
[not found] ` <46D2CFFB.6050602@fz-juelich.de>
[not found] ` <fa686aa40708270719s1fd230e9g188948ef02b3eda7@mail.gmail.com>
[not found] ` <46D41298.7060109@fz-juelich.de>
2007-08-28 13:06 ` Grant Likely
2007-08-28 13:24 ` schardt
2007-08-28 13:30 ` Grant Likely
2007-08-28 13:39 ` schardt
2007-08-28 13:55 ` Grant Likely
2007-08-28 14:12 ` schardt
2007-08-28 14:43 ` Grant Likely
2007-08-28 14:44 ` Grant Likely
2007-08-29 9:29 ` schardt
2007-08-29 13:31 ` schardt
2007-08-29 14:44 ` Grant Likely [this message]
[not found] ` <46DBA4F9.2010703@fz-juelich.de>
2007-09-03 13:41 ` Grant Likely
2007-08-27 13:54 ` Ming Liu
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=fa686aa40708290744w261adfe8ya617a045e4860656@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=g.schardt@fz-juelich.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).