Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Built a file system, have a working kernel - how to login ?
Date: Sat, 17 Nov 2012 11:11:32 +0100	[thread overview]
Message-ID: <20121117111132.17a91542@skate> (raw)
In-Reply-To: <CAF-Ht3yZfCDAMpPGJ7NFd_RQ0brOwxw3pSSoA3YFtzVf7kpf2g@mail.gmail.com>

Dear Juha Lumme,

On Sat, 17 Nov 2012 17:22:27 +0900, Juha Lumme wrote:

> I'm new to buildroot, and actually also to creating linux systems. I really
> need help understanding some basics of how a system bring up should happen..
> I have been working on a custom system of mine, running currently on a
> reference HW from Olimex.
> 
> I have built a working kernel, and now I created a file system with
> buildroot with all the settings default. Well, I did change the default
> console to ttyAMA0, as that is passed to the kernel by the loader.

Which /dev management method did you choose in the Buildroot
configuration?

> Now, the system boots up to the mounting filesystem, and then just hangs
> there:
> .....
> [    3.130000] VFS: Mounted root (ext3 filesystem) on device 179:2.
> [    3.140000] Freeing init memory: 144K
> Starting logging: OK
> Starting network...
> ip: RTNETLINK answers: Operation not permitted
> ip: SIOCSIFFLAGS: Permission denied
> 
> (The whole boot log is here: http://paste.ubuntu.com/1364407/ )
> 
> Can someone please educate me a bit what are the steps needed to get a
> login prompt, and to be able to access the system ? I don't really
> understand how the TTY links in /dev/ work, and how I need to tie them to
> the kernel configuration..
> 
> My understanding is that inittab is the file I should modify.. Contents of
> that is:

No, you shouldn't have to modify the inittab file.

> # Startup the system
> null::sysinit:/bin/mount -t proc proc /proc
> null::sysinit:/bin/mount -o remount,rw / # REMOUNT_ROOTFS_RW
> null::sysinit:/bin/mkdir -p /dev/pts
> null::sysinit:/bin/mkdir -p /dev/shm
> null::sysinit:/bin/mount -a
> null::sysinit:/bin/hostname -F /etc/hostname
> # now run any rc scripts
> ::sysinit:/etc/init.d/rcS
> 
> # Put a getty on the sttyAMA0::respawn:/sbin/getty -L ttyAMA0 115200 vt100
> # GENERIC_SERIAL

If your inittab really looks like this, then there is no way it can
work: the line starting getty is commented out.

So:

 *) Do not modify the inittab

 *) Tell us what hardware you're using exactly, becausing depending on
    the hardware, the ttyXYZn to use is different.

 *) Tell us which /dev management style you've chosen. If you chose
    devtmpfs or mdev or udev, then make sure your kernel has
    CONFIG_DEVTMPFS + CONFIG_DEVTMPFS_MOUNT (Buildroot ensures that your
    kernel is built with those options if Buildroot is responsible for
    building your kernel, but if you build your kernel outside of
    Buildroot, it's your job).

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-11-17 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17  8:22 [Buildroot] Built a file system, have a working kernel - how to login ? Juha Lumme
2012-11-17 10:11 ` Thomas Petazzoni [this message]
2012-11-17 11:07   ` Juha Lumme
2012-11-17 11:35     ` Thomas Petazzoni
2012-11-17 11:45       ` Juha Lumme
2012-11-17 12:07         ` Thomas Petazzoni
2012-11-17 13:17           ` Shawn Goff
2012-11-17 13:34             ` Juha Lumme
2012-11-18 20:11               ` Zoltan Gyarmati

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=20121117111132.17a91542@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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