From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Rootfs etc/ help (target: arm64)
Date: Thu, 17 Sep 2015 19:22:24 +0100 [thread overview]
Message-ID: <55FB04E0.6030904@synopsys.com> (raw)
In-Reply-To: <CAMQcK5+_ffBd+6-ccaYjXJ_+TjjqcY4YeHfV5pMLRRpkCbnZeQ@mail.gmail.com>
It is working!
Thanks Ryan! I was missing the getty configuration!
Joao
On 9/17/2015 7:13 PM, Ryan Barnett wrote:
> Joao,
>
> On Thu, Sep 17, 2015 at 12:36 PM, Joao Pinto <Joao.Pinto@synopsys.com> wrote:
>>
>> HI,
>>
>> I am having a problem when generating a rootfs init process 100% from buildroot.
>> This is the log of the startup process (rootfs is on a USB pen drive):
>>
>>
>> Waiting for root device /dev/sda1...
>> scsi 0:0:0:0: Direct-Access Kingston DataTraveler G3 PMAP PQ: 0 ANSI: 0 CCS
>> atkbd serio1: keyboard reset failed on 1c070000.kmi
>> sd 0:0:0:0: [sda] 30695424 512-byte logical blocks: (15.7 GB/14.6 GiB)
>> sd 0:0:0:0: [sda] Write Protect is off
>> sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
>> sd 0:0:0:0: [sda] No Caching mode page found
>> sd 0:0:0:0: [sda] Assuming drive cache: write through
>> sda: sda1
>> sd 0:0:0:0: [sda] Attached SCSI removable disk
>> EXT3-fs (sda1): mounted filesystem with writeback data mode
>> VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
>> kjournald starting. Commit interval 5 seconds
>> devtmpfs: mounted
>> Freeing unused kernel memory: 464K (ffffffc000932000 - ffffffc0009a6000)
>> Freeing alternatives memory: 16K (ffffffc0009a6000 - ffffffc0009aa000)
>> INIT: version 2.88 booting
>> EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
>> EXT3-fs (sda1): using internal journal
>> Starting logging: OK
>> Starting irqbalance: OK
>> Initializing random number generator... random: dd urandom read with 60 bits of
>> entropy available
>> done.
>> Starting system message bus: done
>> Starting network...
>> INIT: Entering runlevel: 5
>> INIT: no more processes left in this runlevel
>> random: nonblocking pool is initialized
>>
>> The problem it remains stuck forever in "INIT: no more processes left in this
>> runlevel". I have a Linaro' rootfs example and it has rcX.d and all that stuff
>> but I want to make a functional rootfs 100% from buildroot.
>>
>> Can you give an hint?
>
> What is your console that you are getting this printout from?
>
> It appears that your getty session isn't launching on the correct tty
> device. Buildroot defaults to launching a getty session (your
> interactive console) on tty1. I assume this is a serial port?
>
> The value you will need to update is BR2_TARGET_GENERIC_GETTY_PORT to
> be the same as the console of your kernel boot arguments (sometimes
> ttyS0).
>
> Thanks,
> -Ryan
>
prev parent reply other threads:[~2015-09-17 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 17:36 [Buildroot] Rootfs etc/ help (target: arm64) Joao Pinto
2015-09-17 18:13 ` Ryan Barnett
2015-09-17 18:22 ` Joao Pinto [this message]
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=55FB04E0.6030904@synopsys.com \
--to=joao.pinto@synopsys.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 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.