Re: Warning: unable to open an initial console

[Ayoub Zaki <ayoub.zaki@embexus.com>]

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

Hi Gerard,

indeed your Kernel it's quite outdated.

you can try to add a recipe like that in your image :

SUMMARY = "basic initramfs image init script"
LICENSE = "MIT"
LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
SRC_URI = "file://init-boot.sh"


S = "${WORKDIR}"

do_install() {
         install -d ${D}${base_sbindir}
         install -m 0755 ${WORKDIR}/init-boot.sh ${D}${base_sbindir}/init
}

do_install_append() {
         install -d ${D}/dev
         mknod -m 622 ${D}/dev/console c 5 1
         mknod -m 666 ${D}/dev/null c 1 3
}

inherit allarch

FILES_${PN} += "/dev /sbin/init "


Regards,

Ayoub



On 26.05.2017 16:27, Gerard van den Bosch wrote:
> Hello Ayoub,
>
> The kernel is quite old 2.6.20 and this variable is not available in 
> the config.
> On the internet I saw this is only introduced with kernel version 2.6.32.
>
> Cheers,
> Gerard
>
> On Fri, May 26, 2017 at 10:20 PM, Ayoub Zaki <ayoub.zaki@embexus.com 
> <mailto:ayoub.zaki@embexus.com>> wrote:
>
>     Hi Gerard,
>
>     did you try to set CONFIG_DEVTMPFS=y in your Kernel config ?
>
>     Cheers
>
>
>     On 26.05.2017 15:52, Gerard van den Bosch wrote:
>>     Hello Andrea,
>>
>>     I have tried to add the line to my machine config:
>>     IMAGE_DEVICE_TABLES = "files/device_table-minimal.txt"
>>
>>     But this didn't help, then I looked a bit further and also tried
>>     to set the following:
>>
>>     USE_DEVFS="0"
>>     VIRTUAL_RUNTIME_dev_manager = "mdev"
>>
>>     Unfortunately this doesn't seem to change anything.
>>
>>     Cheers,
>>     Gerard
>>
>>     On Fri, May 26, 2017 at 7:27 PM, Andrea Adami
>>     <andrea.adami@gmail.com <mailto:andrea.adami@gmail.com>> wrote:
>>
>>         On Fri, May 26, 2017 at 1:05 PM, Gerard van den Bosch
>>         <gvandenbosch@gmail.com <mailto:gvandenbosch@gmail.com>> wrote:
>>         > Hello,
>>         >
>>         > I have build my vendor custom kernel 2.6.20 with yocto daisy.
>>         > Daisy is used because seems to be last release supporting
>>         this old kernel.
>>         >
>>         > I tried building core-image-minimal and core-image-base.
>>         >
>>         > The kernel boots and the rootfs is mounted but then I get:
>>         >
>>         > "Warning: unable to open an initial console."
>>         >
>>         >
>>         > I found on the internet this is because "/dev/console"
>>         doesn't exists.
>>         > The dev folder in my generated rootfs is empty.
>>         >
>>         > On internet found can do the following commands:
>>         > "mknod -m 600 /dev/console c 5 1 "
>>         > "mknod -m 666 /dev/null c 1 3"
>>         >
>>         > But if this is the problem how do I add this to my recipe?
>>         > Or is there a proper way to populate this devices?
>>         >
>>         > Cheers,
>>         > Gerard
>>         >
>>         > --
>>         > _______________________________________________
>>         > yocto mailing list
>>         > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>         > https://lists.yoctoproject.org/listinfo/yocto
>>         <https://lists.yoctoproject.org/listinfo/yocto>
>>         >
>>
>>         Hello Gerard,
>>
>>         if your old kernel lacks devtmpfs you need a "device table".
>>         You need to set at least
>>         IMAGE_DEVICE_TABLES = "files/device_table-minimal.txt"
>>
>>         This is a default set in image.bbclass before and after
>>         daisy...dunno
>>         what's happened with this release.
>>
>>         Cheers
>>         Andrea
>>
>>
>>
>>
>
>     -- 
>
>     Ayoub Zaki
>
>     ayoub.zaki@embexus.com <mailto:ayoub.zaki@embexus.com>
>     Mobile:+49(0)176-62901545 <tel:+49%20176%2062901545>
>     https://embexus.com
>
>

-- 

Ayoub Zaki

ayoub.zaki@embexus.com
Mobile: +49(0)176-62901545
https://embexus.com


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