[yocto] Device is unable to BOOT or INSTALL with generated .hddimg
All, I have device which has following configuration: - Chipset architecture - `Intel NM10 express` - Processor - `Atom D2550 Dual Core` - Display - `DVI` - Volatile Memory - `2GB DDR3` - Storage - `16GB` **Objective**: Device should run yocto embededded OS successfully What I have done, - Downloaded three required yocto layers for warrior branch i.e. 1. poky 2. meta-openembedded 3. meta-intel - Modified `local.conf` with `MACHINE ??= "intel-core2-32"` - Ran `source poky/oe-init-build-env` - Generated `.hddimg` by bitbake `core-image-minimal` - Flashed `.hddimg` to thumb drive through `dd` command Attached thumb drive to device and I could see BOOT and INSTALL option, upon clicking any of them nothing happens(not even logs) i.e. Blank screen Troubleshooting I tried out are, 1. Tried to boot `lubuntu` and it was successful 2. Replaced kernel & initrd of `lubuntu` with yocto's one and booting was successful which indicates there is no issue with kernel or initrd in `.hddimg` generated by yocto 3. Tried some experiment with `syslinux` as well but didn't work out Regards, Raxesh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Device is unable to BOOT or INSTALL with generated .hddimg
All, I have device which has following configuration: - Chipset architecture - `Intel NM10 express` - Processor - `Atom D2550 Dual Core` - Display - `DVI` - Volatile Memory - `2GB DDR3` - Storage - `16GB` **Objective**: Device should run yocto embededded OS successfully What I have done, - Downloaded three required yocto layers for warrior branch i.e. 1. poky 2. meta-openembedded 3. meta-intel - Modified `local.conf` with `MACHINE ??= "intel-core2-32"` - Ran `source poky/oe-init-build-env` - Generated `.hddimg` by bitbake `core-image-minimal` - Flashed `.hddimg` to thumb drive through `dd` command Attached thumb drive to device and I could see BOOT and INSTALL option, upon clicking any of them nothing happens(not even logs) i.e. Blank screen Troubleshooting I tried out are, 1. Tried to boot `lubuntu` and it was successful 2. Replaced kernel & initrd of `lubuntu` with yocto's one and booting was successful which indicates there is no issue with kernel or initrd in `.hddimg` generated by yocto 3. Tried some experiment with `syslinux` as well but didn't work out Regards, Raxesh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] No SELinux security context (/etc/crontab)
Hi, I have enabled SELinux in my yocto project(warrior branch) but cron is not functioning because of some SELinux context isuue. I am using minimum SELinux policy. Here is the error from `/var/log/messages` Oct 9 04:50:01 panther2 cron.info crond[261]: ((null)) No SELinux security context (/etc/crontab) Oct 9 04:50:01 panther2 cron.info crond[261]: (root) FAILED (loading cron table) Here are some contexts for relevant files, root@panther2:~# ps -efZ | grep cron system_u:system_r:kernel_t:s0 root 464 1 0 04:54 ?00:00:00 /usr/sbin/crond -n root@panther2:~# ls -lZ /etc/crontab -rw---. 1 root root system_u:object_r:unconfined_t:s0 653 Oct 9 2019 /etc/crontab root@panther2:~# ls -lZ /usr/sbin/crond -rwxr-xr-x. 1 root root system_u:object_r:unlabeled_t:s0 68160 Oct 9 2019 /usr/sbin/crond Any help? Thanks !! Regards, Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-selinux warrior support
Hi, I am getting the below error when I am trying to integrate 'meta-selinux' into our yocto solution. This error also happens when I just build 'core-image-selinux' by including the required layers in warrior branch. Can anyone provide a fix for this.. local.conf contains the following lines: - DISTRO_FEATURES_append = " acl xattr pam selinux" PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mls" - ERROR: glib-2.0-native-1_2.58.3-r0 do_configure: meson failed ERROR: glib-2.0-native-1_2.58.3-r0 do_configure: Function failed: do_configure (log file is located at /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2.58.3-r0/temp/log.do_configure.34545) ERROR: Logfile of failure stored in: /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2.58.3-r0/temp/log.do_configure.34545 Log data follows: | DEBUG: Executing shell function do_configure | NOTE: Executing meson -Ddtrace=false -Dfam=false -Dsystemtap=false -Dselinux=false -Dlibmount=true -Dman=false -Dselinux=disabled -Dinternal_pcre=false -Dinstalled_tests=false... | The Meson build system | Version: 0.49.2 | Source dir: | /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2 | .58.3-r0/glib-2.58.3 Build dir: | /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2 | .58.3-r0/build | Build type: native build | | meson.build:1:0: ERROR: Value disabled is not boolean (true or false). | | A full log can be found at | /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2 | .58.3-r0/build/meson-logs/meson-log.txt | ERROR: meson failed Thanks, Raxesh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
