Re: [yocto] linux-raspberrypi_4.19.bb unknown commit
Le 11.05.19 à 21:46, Paul Barker a écrit : > On Sat, 11 May 2019, at 20:44, Jean-Christian de Rivaz wrote: >> Hi, >> >> I try to use the Linux 4.19 for the RaspberryPi from the >> meta-raspberrypi recipe linux-raspberrypi_4.19.bb but the commit >> ab8652c03fa081b27de7e28a74c2536cb2aa3e5b from his SRCREV don't exists >> into the repository github.com/raspberrypi/linux branch rpi-4.19.y . I >> searched that commit on a few others branches but failed to find it. >> Have anyone tested that recipe ? > The upstream rpi-4.19.y branch is still unstable and they enjoy rebasing > commits. The breaks the commit references used in our recipes. > > For now I recommend sticking to the 4.14.y kernels for Raspberry Pi. > Too bad, I need Linux >= 4.19 to enable cgroup2 memory.oom_group to properly kill and restart xserver-nodm with chromium in kiosk mode displaying videos all the days long. There a bug somewhere in chromium/ffmpeg/gpu that eat all the available memory, and I don't have time and money to dig in that complexity and patch acceptance marathon. Jean-Christian de Rivaz innodelec sàrl -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] linux-raspberrypi_4.19.bb unknown commit
Hi, I try to use the Linux 4.19 for the RaspberryPi from the meta-raspberrypi recipe linux-raspberrypi_4.19.bb but the commit ab8652c03fa081b27de7e28a74c2536cb2aa3e5b from his SRCREV don't exists into the repository github.com/raspberrypi/linux branch rpi-4.19.y . I searched that commit on a few others branches but failed to find it. Have anyone tested that recipe ? Best Regards. Jean-Christian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Proper way to set locale and keymap
Hi all, After some experiments on Poky thud I have found this method to set my fr_CH.utf8 local and fr_CH-latin keymap in my distribution with systemd and without busybox: Add this two lines to the local configuration or distribution configuration file: GLIBC_GENERATE_LOCALES = "fr_CH.UTF-8" IMAGE_LINGUAS = "fr-ch" After boot add this file to set local in the shell environment variable: cat < /etc/profile.d/locale.sh if [ -r /etc/locale.conf ]; then export \$(cat /etc/locale.conf) fi EOF Finally set the locale and keymap either with the localctl command: localectl set-locale fr_CH.utf8 localectl set-keymap fr_CH-latin1 Or by directly creating this two files: echo "LANG=fr_CH.utf8" > /etc/locale.conf echo "KEYMAP=fr_CH-latin1" > /etc/vconsole.conf The result is workable but a lot of [Alt Gr] + key characters are missing. Please comment on this method and if a recipe already exist to do that. Best regards. Jean-Christian de Rivaz -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing busybox
Le 28.02.19 à 06:19, Adrian Bunk a écrit : > On Wed, Feb 27, 2019 at 11:59:42PM +, Burton, Ross wrote: >> ... >> Also swap vim for something in core obviously. > It is not obvious how to do that. > > What other vi implementation is in core? > Is there even any good non-busybox non-GUI editor in core? > Replacing busybox vi with ed would be a bad fit for the > stated usecases. > > There has to be some vi implementation installed, > and the "desktop command" implementation is vim. I have see numbers of users trying nano before falling back to vim or vi. The nano editor is standard on Debian and Ubuntu making a lot of users expecting it more intuitive interface. Jean-Christian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing busybox
Le 28.02.19 à 00:59, Burton, Ross a écrit : > On Wed, 27 Feb 2019 at 23:55, Tom Rini wrote: >> My current incomplete list is: >> bind-utils \ >> bridge-utils \ >> coreutils \ >> dnsmasq \ >> e2fsprogs \ >> e2fsprogs-resize2fs \ >> e2fsprogs-tune2fs \ >> findutils \ >> gawk \ >> grep \ >> inetutils-ping \ >> inetutils-ping6 \ >> inetutils-traceroute \ >> iproute2 \ >> less \ >> net-tools \ >> parted \ >> pciutils \ >> procps \ >> sed \ >> util-linux \ >> vim \ >> which \ >> >> And it's also incomplete as there's more stuff under inetutils I don't >> need (but others may), and I set aside patch/diff/ed and some other >> stuff I don't need. And since some of that stuff comes from >> meta-openembedded, it's indeed really not clear how/where a packagegroup >> would reside as we need things out of meta-networking. > That's a good start. For a oe-core packagegroup I'd suggest dropping > dnsmasq bridgeutils bindutils to keep it lean. Does that remove > everything from meta-networking? Also swap vim for something in core > obviously. > > Ross > > Ross My image recipe look actually like below and require several meta-openembedded/meta-*. This is not a clean example. The packagegroup-core-full-cmdline already provides a chunk of commands but more are required to look like a modern distribution. LICENSE = "MIT" inherit core-image distro_features_check MACHINE_FEATURES += "acpi" MACHINE_FEATURES += "apm" MACHINE_FEATURES += "keyboard" MACHINE_FEATURES += "pcbios" MACHINE_FEATURES += "pci" MACHINE_FEATURES += "rtc" MACHINE_FEATURES += "screen" MACHINE_FEATURES += "serial" MACHINE_FEATURES += "wifi" REQUIRED_DISTRO_FEATURES = "x11" DISTRO_FEATURES += "keyboard" DISTRO_FEATURES += "ldconfig" IMAGE_FEATURES += "splash" IMAGE_FEATURES += "x11-base" IMAGE_FEATURES += "package-management" IMAGE_FEATURES += "ssh-server-openssh" IMAGE_FEATURES += "tools-debug" IMAGE_INSTALL += "python-modules python-misc" IMAGE_INSTALL += "packagegroup-core-full-cmdline" IMAGE_INSTALL += "e2fsprogs-mke2fs" IMAGE_INSTALL += "parted" IMAGE_INSTALL += "iproute2-ss" IMAGE_INSTALL += "iproute2-tc" IMAGE_INSTALL += "iproute2-lnstat" IMAGE_INSTALL += "iproute2-ifstat" IMAGE_INSTALL += "iproute2-genl" IMAGE_INSTALL += "iproute2-rtacct" IMAGE_INSTALL += "iproute2-nstat" IMAGE_INSTALL += "iproute2-ss" IMAGE_INSTALL += "iproute2-tipc" IMAGE_INSTALL += "kmod" IMAGE_INSTALL += "wget" IMAGE_INSTALL += "iputils-ping" IMAGE_INSTALL += "less" IMAGE_INSTALL += "vim" IMAGE_INSTALL += "nano" IMAGE_INSTALL += "glibc-utils" IMAGE_INSTALL += "glibc-gconv-cp1252" IMAGE_INSTALL += "glibc-charmap-cp1252" IMAGE_INSTALL += "ldd" IMAGE_INSTALL += "sysstat" IMAGE_INSTALL += "gettext" IMAGE_INSTALL += "curl" IMAGE_INSTALL += "socat" IMAGE_INSTALL += "htop" IMAGE_INSTALL += "autossh" IMAGE_INSTALL += "cronie" IMAGE_INSTALL += "networkmanager" IMAGE_INSTALL += "ethtool" IMAGE_INSTALL += "ntp" IMAGE_INSTALL += "openssh-sshd" IMAGE_INSTALL += "rsync" IMAGE_INSTALL += "git" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing busybox
Le 27.02.19 à 22:40, Adrian Bunk a écrit : > On Wed, Feb 27, 2019 at 03:09:02PM -0500, Tom Rini wrote: >> On Wed, Feb 27, 2019 at 09:06:38PM +0100, Jean-Christian de Rivaz wrote: >> ... >>> So as expected systemd is there and busybox is not. But there is a lot of >>> useful commands missing on the resulting QEMU image: >>> >>> root@qemux86:~# ps >>> ~sh: ps: command not found >>> root@qemux86:~# w >>> ~sh: w: command not found >>> root@qemux86:~# find >>> ~sh: find: command not found >>> root@qemux86:~# grep >>> ~sh: grep: command not found >>> root@qemux86:~# ip addr >>> ~sh: ip: command not found >>> >>> I expected that all the limited busybox commands would be replaced by >>> the full >>> featured commands. How to fix that ? >> Correct, you're missing a lot of stuff. Somewhere on my (and other >> folks too) TODO list is a packagegroup that includes procps and psmisc >> and grep and tar and various network packages and less and more and... > "all the limited busybox commands would be replaced" would be a huge > list from dc through gawk, minicom and wget to vim. > > And would vim-tiny qualify as "the full featured command" of busybox vi, > or should this include vim with full features? > > The nice thing about busybox is that it is so small, > in many cases one full featured command alone > is bigger than busybox. > > It is not obvious to me what usecases people have in mind for > getting rid of busybox, and whether everyone is aware that > something like "all busybox commands replaced" is *very* > expensive regarding filesystem size. The project I work for need nodejs and chromium (and a >100MB database on some nodes), so space is not an issue. I need to deliver an useful distribution with usual commands, tools and a working console + keyboard for my locale. If Poky is only maintained to be tested with sysvinit + busybox and US locale, then I wonder if it's the appropriate choice for that project. There nothing wrong in providing a sysvinit + busybox based small distribution, this is simply not the best fit for that project. Jean-Christian > >> Tom > cu > Adrian > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing busybox
Thank you very much Tom for help. Here is my complete method: git clone git://git.yoctoproject.org/poky -b thud cd poky cat << EOF > meta-poky/conf/distro/poky-ng.conf require conf/distro/poky.conf DISTRO = "poky-ng" # Switch to systemd DISTRO_FEATURES += "systemd" VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "" VIRTUAL-RUNTIME_syslog = "" VIRTUAL-RUNTIME_login_manager = "shadow-base" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" # Replace busybox PREFERRED_PROVIDER_virtual/base-utils = "coreutils" VIRTUAL-RUNTIME_base-utils = "coreutils" VIRTUAL-RUNTIME_base-utils-hwclock = "util-linux-hwclock" VIRTUAL-RUNTIME_base-utils-syslog = "" EOF source oe-init-build-env sed -i 's/^DISTRO.*/DISTRO = "poky-ng"/' conf/local.conf bitbake core-image-minimal runqemu core-image-minimal kvm So as expected systemd is there and busybox is not. But there is a lot of useful commands missing on the resulting QEMU image: root@qemux86:~# ps ~sh: ps: command not found root@qemux86:~# w ~sh: w: command not found root@qemux86:~# find ~sh: find: command not found root@qemux86:~# grep ~sh: grep: command not found root@qemux86:~# ip addr ~sh: ip: command not found I expected that all the limited busybox commands would be replaced by the full featured commands. How to fix that ? Best Regards. Jean-Christian de Rivaz Le 27.02.19 à 18:06, Tom Rini a écrit : > On Wed, Feb 27, 2019 at 01:16:56PM +0100, Jean-Christian de Rivaz wrote: > >> Hi all, >> >> After reading the thread "Removing busybox completely from the generated >> image" I tested to reproduce the method but this doesn't work as expected. >> >> git clone git://git.yoctoproject.org/poky -b thud >> cd poky >> echo 'require conf/distro/poky.conf' > meta-poky/conf/distro/poky-ng.conf >> echo 'DISTRO = "poky-ng"' >> meta-poky/conf/distro/poky-ng.conf >> echo 'VIRTUAL-RUNTIME_base-utils = ""' >> meta-poky/conf/distro/poky-ng.conf >> sed -i 's/^DISTRO.*/DISTRO = "poky-ng"/' conf/local.conf >> bitbake core-image-minimal >> runqemu core-image-minimal kvm >> >> After login as root there still a lot of links to busybox inside /sbin/ >> /bin/ /usr/sbin/ and /usr/bin/ . >> >> Can someone provides a working method ? > You're missing a few more things, yes. What I have is: > # Switch to systemd > DISTRO_FEATURES += "systemd" > VIRTUAL-RUNTIME_init_manager = "systemd" > VIRTUAL-RUNTIME_initscripts = "" > VIRTUAL-RUNTIME_syslog = "" > VIRTUAL-RUNTIME_login_manager = "shadow-base" > DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" > > # Replace busybox > PREFERRED_PROVIDER_virtual/base-utils = "coreutils" > VIRTUAL-RUNTIME_base-utils = "coreutils" > VIRTUAL-RUNTIME_base-utils-hwclock = "util-linux-hwclock" > VIRTUAL-RUNTIME_base-utils-syslog = "" > > If you aren't using systemd you'll need to move the login_manager > example over as well, otherwise busybox gets pulled for that. > > I'm using the above on thud, today. And that's not a 1:1 replacement as > my image pulls in a number of other packages for various things I > want/need. > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Removing busybox
Hi all, After reading the thread "Removing busybox completely from the generated image" I tested to reproduce the method but this doesn't work as expected. git clone git://git.yoctoproject.org/poky -b thud cd poky echo 'require conf/distro/poky.conf' > meta-poky/conf/distro/poky-ng.conf echo 'DISTRO = "poky-ng"' >> meta-poky/conf/distro/poky-ng.conf echo 'VIRTUAL-RUNTIME_base-utils = ""' >> meta-poky/conf/distro/poky-ng.conf sed -i 's/^DISTRO.*/DISTRO = "poky-ng"/' conf/local.conf bitbake core-image-minimal runqemu core-image-minimal kvm After login as root there still a lot of links to busybox inside /sbin/ /bin/ /usr/sbin/ and /usr/bin/ . Can someone provides a working method ? Best Regards, Jean-Christian de Rivaz -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QEMU Raspberry Pi 2 machine
Hi Alex, Yes, this is what I was forced to do anyway because I discovered in the meantime that my modified qemuarm.conf don't yield a working emulator. The idea was to make an automatic image validation of the client's applications before sending the image to the testing lab and real hardware. Thanks for the advise. Jean-Christian Le 18.02.19 à 19:50, Alexander Kanavin a écrit : > You can just use a qemux86-64 target, which is much faster because it > executes directly on the hardware. What's the need to emulate > specifically arm? > > Alex > > On Mon, 18 Feb 2019 at 19:34, Jean-Christian de Rivaz > wrote: >> Hi, >> >> The chromium-x11 browser can't be compiled for the qemuarm machine because >> it use the old ARM926 processor. I have modified the qemuarm.conf file >> inside poky/meta/conf/machine/ to add >> DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4" >> require conf/machine/include/tune-cortexa7.inc >> But I want to avoid patching files of the poky project. Is there a proper >> way to add a QEMU Raspberry Pi 2 target like qemuraspi2 for example ? It >> look like many recipe files contains specific part for qemuarm so I wonder >> if adding a new QEMU machine it a simple enough task. >> >> Best Regards, >> Jean-Christian de Rivaz >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] QEMU Raspberry Pi 2 machine
Hi, The chromium-x11 browser can't be compiled for the qemuarm machine because it use the old ARM926 processor. I have modified the qemuarm.conf file inside poky/meta/conf/machine/ to add DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4" require conf/machine/include/tune-cortexa7.inc But I want to avoid patching files of the poky project. Is there a proper way to add a QEMU Raspberry Pi 2 target like qemuraspi2 for example ? It look like many recipe files contains specific part for qemuarm so I wonder if adding a new QEMU machine it a simple enough task. Best Regards, Jean-Christian de Rivaz-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
