[Buildroot] Linux kernel boot stops after NFS mount

[Buildroot] Linux kernel boot stops after NFS mount

[Divick Kishore]

Hi,
    I am trying to build a custom root filesystem using build root, but the
build process stops after nfs mount. It seems that init process is not
launched. Could anyone please suggest how can I debug this problem? I have
searched the list and tried googling it but couldn't find much help.

The toolchain used for building rootfs is CodeSourcery G++ Lite 2010.09-50
(arm-none-linux-gnueabi-gcc-4.5.1). My board is able to boot using the
filesystem provided with the board. The uboot is the one that was provided
by the h/w vendor and I have built the Linux kernel using the above
mentioned toolchain.

Version of buildroot used is buildroot-2010.11.

The boot log is shown below and the config file for build root is attached
with the mail.

=============================================================
Darrell's loader - Thanks to the u-boot project
Version 1.0. Build Feb 22 2010 15:45:18
64MB?
32MB?
Writing...
Reading...
RAM:32MB

1: Upload Darrell's loader to Dataflash
2: Upload u-boot to Dataflash
3: Upload Kernel to Dataflash
4: Start u-boot
5: Upload Filesystem image
6: Memory test
DataFlash:AT45DB321
Dataflash read successful: Starting U-boot


U-Boot 1.1.6 (Oct 22 2007 - 10:35:14)

DRAM:  32 MB
Atmel: Flash:  0 kB
DataFlash:AT45DB321
Nb pages:   8192
Page Size:    528
Size= 4325376 bytes
Logical address: 0xC0000000
Area 0: C0000000 to C000317F (RO) Darrell loader
Area 1: C0003180 to C001F73F (RO) U-boot
Area 2: C001F740 to C002183F      Environment
Area 3: C0021840 to C01ACFFF      Kernel
Area 4: C01AD000 to C041FFFF (RO) Filesystem
In:    serial
Out:   serial
Err:   serial
I am checking if it is connected
Hit any key to stop autoboot:  0
I am checking if it is connected
TFTP from server 192.168.1.4; our IP address is 192.168.1.7
Filename 'newat91.img'.
Load address: 0x20200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########
done
Bytes transferred = 1709973 (1a1795 hex)
## Booting image at 20200000 ...
   Image Name:   Linux Kernel Image
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    1709909 Bytes =  1.6 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Linux version 2.6.21.6 (divkis01 at divkis01-pc) (gcc version 4.5.1 (Sourcery
G++ Lite 2010.09-50) ) #13 Sat Jan 8 18:06:30 IST 2011
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0003177
Machine: emQbit's ECB_AT91 V1
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists.  Total pages: 8128
Kernel command line: mem=32M rootfstype=ext3 root=/dev/nfs
nfsroot=192.168.1.4:/nfs ip=dhcp console=ttyS0
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29140KB available (2968K code, 228K data, 104K init)
Security Framework v1.0.0 initialized
Capability LSM initialized
Failure registering Root Plug module with the kernel
Failure registering Root Plug  module with primary security module.
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
fuse init (API version 7.8)
JFS: nTxBlock = 227, nTxLock = 1821
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffc0000 (irq = 6) is a ATMEL_SERIAL
loop: loaded (max 8 devices)
at91_ether: phy_id1=0x0000ffff phy_id2=0x0000ffff
at91_ether: phy_id=0xffffffff
at91_ether: phy_id1=0x00000022 phy_id2=0x00001619
at91_ether: phy_id=0x00221619
eth0: Link now 100-FullDuplex
eth0: AT91 ethernet at 0xfefbc000 int=24 100-FullDuplex (00:00:00:00:00:5b)
eth0: Micrel KS8721 PHY
usbcore: registered new interface driver zd1201
st: Version 20070203, fixed bufsize 32768, s/g segs 256
SCSI Media Changer driver v0.25
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 23, io mem 0x00300000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
AT91 MMC: 4 wire bus mode not supported by this driver - using 1 wire
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <
jketreno@linux.intel.com>
eth0: Link now 100-FullDuplex
eth0: Link now 100-FullDuplex
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.8
IP-Config: Complete:
      device=eth0, addr=192.168.1.8, mask=255.255.255.0, gw=192.168.1.1,
     host=unknown00000000005b, domain=local.lan, nis-domain=(none),
     bootserver=192.168.1.1, rootserver=192.168.1.4, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.4
Looking up port of RPC 100005/1 on 192.168.1.4
VFS: Mounted root (nfs filesystem).
Freeing init memory: 104K

=============================================================

... No output is seen after this.


Thanks in advance,
DivKis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110108/e8ce14f8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config
Type: application/octet-stream
Size: 17984 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110108/e8ce14f8/attachment-0001.obj>

[Buildroot] Linux kernel boot stops after NFS mount

[Klaus Schwarzkopf]

Hi,

have you "Generic serial port config" enabled?

See FAQ:

http://buildroot.uclibc.org/downloads/buildroot.html#faq


Regards,

Klaus

Am 08.01.2011 14:02, schrieb Divick Kishore:
> Hi,
>      I am trying to build a custom root filesystem using build root, but
> the build process stops after nfs mount. It seems that init process is
> not launched. Could anyone please suggest how can I debug this problem?
> I have searched the list and tried googling it but couldn't find much help.
>
> The toolchain used for building rootfs is CodeSourcery G++
> Lite 2010.09-50 (arm-none-linux-gnueabi-gcc-4.5.1). My board is able to
> boot using the filesystem provided with the board. The uboot is the one
> that was provided by the h/w vendor and I have built the Linux kernel
> using the above mentioned toolchain.
>
> Version of buildroot used is buildroot-2010.11.
>
> The boot log is shown below and the config file for build root is
> attached with the mail.
>
> =============================================================
> Darrell's loader - Thanks to the u-boot project
> Version 1.0. Build Feb 22 2010 15:45:18
> 64MB?
> 32MB?
> Writing...
> Reading...
> RAM:32MB
>
> 1: Upload Darrell's loader to Dataflash
> 2: Upload u-boot to Dataflash
> 3: Upload Kernel to Dataflash
> 4: Start u-boot
> 5: Upload Filesystem image
> 6: Memory test
> DataFlash:AT45DB321
> Dataflash read successful: Starting U-boot
>
>
> U-Boot 1.1.6 (Oct 22 2007 - 10:35:14)
>
> DRAM:  32 MB
> Atmel: Flash:  0 kB
> DataFlash:AT45DB321
> Nb pages:   8192
> Page Size:    528
> Size= 4325376 bytes
> Logical address: 0xC0000000
> Area 0: C0000000 to C000317F (RO) Darrell loader
> Area 1: C0003180 to C001F73F (RO) U-boot
> Area 2: C001F740 to C002183F      Environment
> Area 3: C0021840 to C01ACFFF      Kernel
> Area 4: C01AD000 to C041FFFF (RO) Filesystem
> In:    serial
> Out:   serial
> Err:   serial
> I am checking if it is connected
> Hit any key to stop autoboot:  0
> I am checking if it is connected
> TFTP from server 192.168.1.4; our IP address is 192.168.1.7
> Filename 'newat91.img'.
> Load address: 0x20200000
> Loading: #################################################################
>           #################################################################
>           #################################################################
>           #################################################################
>           #################################################################
>           #########
> done
> Bytes transferred = 1709973 (1a1795 hex)
> ## Booting image at 20200000 ...
>     Image Name:   Linux Kernel Image
>     Image Type:   ARM Linux Kernel Image (gzip compressed)
>     Data Size:    1709909 Bytes =  1.6 MB
>     Load Address: 20008000
>     Entry Point:  20008000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
>
> Starting kernel ...
>
> Linux version 2.6.21.6 (divkis01 at divkis01-pc) (gcc version 4.5.1
> (Sourcery G++ Lite 2010.09-50) ) #13 Sat Jan 8 18:06:30 IST 2011
> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0003177
> Machine: emQbit's ECB_AT91 V1
> Memory policy: ECC disabled, Data cache writeback
> Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
> CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
> Built 1 zonelists.  Total pages: 8128
> Kernel command line: mem=32M rootfstype=ext3 root=/dev/nfs
> nfsroot=192.168.1.4:/nfs ip=dhcp console=ttyS0
> AT91: 96 gpio irqs in 3 banks
> PID hash table entries: 128 (order: 7, 512 bytes)
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 32MB = 32MB total
> Memory: 29140KB available (2968K code, 228K data, 104K init)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Failure registering Root Plug module with the kernel
> Failure registering Root Plug  module with primary security module.
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> Generic PHY: Registered new driver
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 1, 8192 bytes)
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> NetWinder Floating Point Emulator V0.97 (double precision)
> fuse init (API version 7.8)
> JFS: nTxBlock = 227, nTxLock = 1821
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
> atmel_usart.1: ttyS1 at MMIO 0xfffc0000 (irq = 6) is a ATMEL_SERIAL
> loop: loaded (max 8 devices)
> at91_ether: phy_id1=0x0000ffff phy_id2=0x0000ffff
> at91_ether: phy_id=0xffffffff
> at91_ether: phy_id1=0x00000022 phy_id2=0x00001619
> at91_ether: phy_id=0x00221619
> eth0: Link now 100-FullDuplex
> eth0: AT91 ethernet at 0xfefbc000 int=24 100-FullDuplex (00:00:00:00:00:5b)
> eth0: Micrel KS8721 PHY
> usbcore: registered new interface driver zd1201
> st: Version 20070203, fixed bufsize 32768, s/g segs 256
> SCSI Media Changer driver v0.25
> at91_ohci at91_ohci: AT91 OHCI
> at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
> at91_ohci at91_ohci: irq 23, io mem 0x00300000
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new interface driver usbserial
> drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
> usbcore: registered new interface driver usbserial_generic
> drivers/usb/serial/usb-serial.c: USB Serial Driver core
> mice: PS/2 mouse device common for all mice
> i2c /dev entries driver
> AT91 MMC: 4 wire bus mode not supported by this driver - using 1 wire
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> ieee80211: 802.11 data/management/control stack, git-1.1.13
> ieee80211: Copyright (C) 2004-2005 Intel Corporation
> <jketreno at linux.intel.com <mailto:jketreno@linux.intel.com>>
> eth0: Link now 100-FullDuplex
> eth0: Link now 100-FullDuplex
> Sending DHCP requests ., OK
> IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.8
> IP-Config: Complete:
>        device=eth0, addr=192.168.1.8, mask=255.255.255.0, gw=192.168.1.1,
>       host=unknown00000000005b, domain=local.lan, nis-domain=(none),
>       bootserver=192.168.1.1, rootserver=192.168.1.4, rootpath=
> Looking up port of RPC 100003/2 on 192.168.1.4
> Looking up port of RPC 100005/1 on 192.168.1.4
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 104K
>
> =============================================================
>
> ... No output is seen after this.
>
>
> Thanks in advance,
> DivKis
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


-- 
Sensortherm GmbH
Sitz:/Head quarter: Hauptstra?e 123, 65843 Sulzbach (Taunus)
Registergericht:/Registry office: Amtsgericht Frankfurt/M.
Eintragungs-Nr.:/Registry-No. HRB 52438
Gesch?ftsf?hrer:/General Manager: Werner Weldert

[Buildroot] Linux kernel boot stops after NFS mount

[Divick Kishore]

Hi Klaus,

>have you "Generic serial port config" enabled?

yeah I do have generic serial port config enabled. Any other suggestions please?

Regards,
DivKis

[Buildroot] Linux kernel boot stops after NFS mount

[Samuel Martin]

2011/1/8 Divick Kishore <divick.kishore@gmail.com>

> Hi Klaus,
>
> >have you "Generic serial port config" enabled?
>
> yeah I do have generic serial port config enabled. Any other suggestions
> please?
>
It might be that the console is disabled in /etc/inittab, just add the
following line (replace ttyS0 by your serial console if it is not ttyS0):
s0::respawn:/sbin/getty -L ttyS0 115200,38400,9600

Btw, take care of the console setting in the kernel command line and in the
inittab

Also, check in /etc/securetty that the console is enabled, to be able to
login through the console.

BR,
Sam


> Regards,
> DivKis
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110108/baca4fbe/attachment.html>

[Buildroot] Linux kernel boot stops after NFS mount

[Thomas Petazzoni]

On Sat, 8 Jan 2011 22:20:36 +0530
Divick Kishore <divick.kishore@gmail.com> wrote:

> yeah I do have generic serial port config enabled. Any other suggestions please?

Is your kernel compiled with CONFIG_AEABI ?

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

[Buildroot] Linux kernel boot stops after NFS mount

[Divick Kishore]

Hi Samuel,

> It might be that the console is disabled in /etc/inittab, just add the
> following line (replace ttyS0 by your serial console if it is not ttyS0):
> s0::respawn:/sbin/getty -L ttyS0 115200,38400,9600

Yeah I tried with this as well but still no output on console. My
serial console is ttyS0.

> Btw, take care of the console setting in the kernel command line and in the
> inittab

My kernel command line has the following bootargs (i.e. console is set
to be ttyS0).

bootargs=mem=32M rootfstype=ext3 root=/dev/nfs
nfsroot=192.168.1.4:/nfs ip=dhcp console=ttyS0


> Also, check in /etc/securetty that the console is enabled, to be able to
> login through the console.

I do see an entry ttyS0 in /etc/securetty apart from many other
entries like tty1, tty2 etc.

Regards,
DivKis

[Buildroot] Linux kernel boot stops after NFS mount

[Divick Kishore]

HI Thomas,


> Is your kernel compiled with CONFIG_AEABI ?

No the CONFIG_AEABI is not set in the config for my kernel.

Ahh..this is the catch. From what I am aware, I guess, both binaries
and kernel need to be built with either ABI or EABI. Since my
toolchain is arm-none-linux-gnueabi, which reflects the fact that all
binaries in my filesystem are built with EABI.

I tried building the kernel with CONFIG_AEABI enabled and now I do see
boot messages past the previous point(see boot log below). But it
looks like there are some problems with the default inittab settings.
Should I make a separate post to discuss these issues?

==============================================================
...
...
IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.8
IP-Config: Complete:
      device=eth0, addr=192.168.1.8, mask=255.255.255.0, gw=192.168.1.1,
     host=unknown00000000005b, domain=local.lan, nis-domain=(none),
     bootserver=192.168.1.1, rootserver=192.168.1.4, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.4
Looking up port of RPC 100005/1 on 192.168.1.4
VFS: Mounted root (nfs filesystem).
Freeing init memory: 104K

INIT: version 2.86 booting
INIT: /etc/inittab[18]: duplicate ID field "null"
INIT: /etc/inittab[19]: duplicate ID field "null"
INIT: /etc/inittab[20]: duplicate ID field "null"
INIT: /etc/inittab[21]: duplicate ID field "null"
INIT: /etc/inittab[23]: missing id field
INIT: /etc/inittab[26]: id field too long (max 4 characters)
INIT: /etc/inittab[33]: duplicate ID field "null"
INIT: /etc/inittab[34]: duplicate ID field "null"
INIT: /etc/inittab[35]: duplicate ID field "null"
INIT: /etc/inittab[39]: missing id field
INIT: /etc/inittab[42]: shutdown: unknown action field
INIT: /etc/inittab[43]: shutdown: unknown action field
INIT: /etc/inittab[44]: shutdown: unknown action field
INIT: /etc/inittab[45]: shutdown: unknown action field

Enter runlevel:

Enter runlevel: 3
INIT: Entering runlevel: 3
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
tail: can't open '/var/log/messages': No such file or directory
tail: no files
INIT: Id "tty3" respawning too fast: disabled for 5 minutes
==============================================================


Thank you all for your help,
Regards,
DivKis

[Buildroot] Linux kernel boot stops after NFS mount

[Thomas Petazzoni]

Hello,

On Sun, 9 Jan 2011 03:29:41 +0530
Divick Kishore <divick.kishore@gmail.com> wrote:

> No the CONFIG_AEABI is not set in the config for my kernel.
> 
> Ahh..this is the catch. From what I am aware, I guess, both binaries
> and kernel need to be built with either ABI or EABI. Since my
> toolchain is arm-none-linux-gnueabi, which reflects the fact that all
> binaries in my filesystem are built with EABI.

Yep, your kernel needs to support EABI. Buildroot ensure that it is the
case when Buildroot is in charge of building the kernel, but when the
kernel is built separatly, there's nothing Buildroot can do, except
relying on the user knowledge.

> I tried building the kernel with CONFIG_AEABI enabled and now I do see
> boot messages past the previous point(see boot log below). But it
> looks like there are some problems with the default inittab settings.
> Should I make a separate post to discuss these issues?

You have enabled BR2_PACKAGE_SYSVINIT, so the init being used is the
traditional SysV init, and not Busybox init. And our default inittab
only works well with Busybox init (which is the standard setup for a
Buildroot system).

So, two solutions :

 1) Unless you have strong reasons not to use Busybox init, I would
    recommend using it by disabling BR2_PACKAGE_SYSVINIT. 

 2) If you really need to use SysV init, then you should use the Git
    version of Buildroot, or at least merge
    http://git.buildroot.net/buildroot/commit/?id=7e2bf63080cc0011c84ee46ee2aba161569154c5
    into your Buildroot version. This commit adds an inittab that works
    well with SysV init.

Regards,

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

[Buildroot] Linux kernel boot stops after NFS mount

[Divick Kishore]

Hi Thomas,

> Yep, your kernel needs to support EABI. Buildroot ensure that it is the
> case when Buildroot is in charge of building the kernel, but when the
> kernel is built separatly, there's nothing Buildroot can do, except
> relying on the user knowledge.

Yeah you are right. Since I was just using the same config for kernel
provided by my h/w vendor for an older kernel which had EABI disabled,
I just overlooked it.

> You have enabled BR2_PACKAGE_SYSVINIT, so the init being used is the
> traditional SysV init, and not Busybox init. And our default inittab
> only works well with Busybox init (which is the standard setup for a
> Buildroot system).

Hmmm. I removed this and now I don't get those error messages.

> So, two solutions :
>
> ?1) Unless you have strong reasons not to use Busybox init, I would
> ? ?recommend using it by disabling BR2_PACKAGE_SYSVINIT.
>
> ?2) If you really need to use SysV init, then you should use the Git
> ? ?version of Buildroot, or at least merge
> ? ?http://git.buildroot.net/buildroot/commit/?id=7e2bf63080cc0011c84ee46ee2aba161569154c5
> ? ?into your Buildroot version. This commit adds an inittab that works
> ? ?well with SysV init.

Busybox init is good enough for me. I unknowingly selected sysVinit.


Thank you all for you help,
Regards,
DivKis