Re: [yocto] user and password problem

Am Mo, 26. Jun 2023, um 14:32, schrieb Natanan Tirasukvongsa: > I got a problem. I use raspberry pi 4 with yocto kirkstone version. > I cannot login right now. What are username and password? > Thank you for helping me. > These are my other files. You might want to look into the IMAGE_FEATURE deb

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Am So, 25. Jun 2023, um 11:58, schrieb Electronic Consult: > I used the attached kas file to generate an image. I didn't try with Wayland > as it wasn't required, I was incorporating meta-qt6 which requires EGLFS for > the RPi4 (http://doc.qt.io/qt-6/configure-linux-device.html). That's my final

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Sun, Jun 25 2023 at 12:01:29 AM +0200, Manuel Wagesreither > wrote: >> The HDMI port is unused on my raspi. I'm using the official Raspberry Pi 7" >> Touchscreen connected via DSI. > > Have you also added ? > > dtoverlay=vc4-kms-dsi-7inch > dtoverlay=rpi

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

it information. Things I would try first are using a different > HDMI cable or switching the hdmi port. > > On Sat, Jun 24 2023 at 06:02:52 PM +0200, Manuel Wagesreither > wrote: >> Am Sa, 24. Jun 2023, um 17:25, schrieb Khem Raj: >>> On Sat, Jun 24, 2023 at 7:47 AM Manu

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Am Sa, 24. Jun 2023, um 17:25, schrieb Khem Raj: > On Sat, Jun 24, 2023 at 7:47 AM Manuel Wagesreither > wrote: >> Am Sa, 24. Jun 2023, um 00:04, schrieb Khem Raj: >> > On Fri, Jun 23, 2023 at 2:39 PM Manuel Wagesreither >> > wrote: >> >> >>

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Am Sa, 24. Jun 2023, um 00:04, schrieb Khem Raj: > On Fri, Jun 23, 2023 at 2:39 PM Manuel Wagesreither > wrote: >> >> Hi users of meta-raspberrypi, >> >> I'd like to ask around if for you people vc4-kms-v3d (opposed to >> vc4-fkms-v3d) *really* i

[yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Hi users of meta-raspberrypi, I'd like to ask around if for you people vc4-kms-v3d (opposed to vc4-fkms-v3d) *really* is the working way to get vc4 support on a Raspberry Pi 4 Model B. Both on master and kirkstone, vc4-kms-v3d is the default. It's defined in /conf/machine/raspberrypi4-64.conf:

[yocto] Asking for advice on how to establish license compliance

Hi all, I'd like to ensure license compliance for an embedded product I'm working on. Disclaimer: I've read https://docs.yoctoproject.org/dev/dev-manual/licenses.html and know about yoctos abilites to provide the license text and/or the source code. Still I feel I'm missing the key info of fin

Re: [yocto] core-image-minimal-xfce: Xorg screen remains black

I realized `core-image-minimal-xfce.bb` adds `packagegroup-core-x11` to IMAGE_INSTALL. Yet, * It doesn't add `x11` to IMAGE_FEATURES which would do the same but perhaps a bit more. * It doesn't add `x11-base` to IMAGE_FEATURES, which would add `packagegroup-core-x11-base` to IMAGE_INSTALL and p

[yocto] core-image-minimal-xfce: Xorg screen remains black

Hi all, I'd like to build core-image-minimal-xfce for qemux86-64. I'm on Dunfell. At first, Xorg didn't start properly but I could fix that by adding package xkeyboard-config manually to the image. Now Xorg seems to start (displays a mouse cursor), but the screen is otherwise black. At some poi

[yocto] Psplash and transparency in images

Hello all, I need to find something out regarding Psplash. I'm currently unable to try things out so I've got to ask around here. Does Psplash support any kind of transparency, either alpha channel in the PNG or setting one key color as the transparent one? I couldn't find any info at all rega

[yocto] LICENSE_CREATE_PACKAGE not working properly

Hi all, I'm on Dunfell [1] and just can't get LICENSE_CREATE_PACKAGE [2] to work right. I'd like to use it to get 'os-release-lic' onto my image. I don't want to install the license packages of *all* the packages onto my image, hence I'm setting NO_RECOMMENDATIONS [3] as well. [1] https://git

[yocto] Cannot build go-runtime on dunfell based image

Hi all, Currently I cannot recreate my dunfell based image because bitbake fails building go-runtime. I think this commit did build successfully in the past, though. If I recall correctly, the problems only started when I cleaned go-runtimes sstate cache: `bitbake -c cleansstate go-runtime`.

Re: [yocto] Multiconfig dependency

Hi Oleh, Am Do, 17. Mär 2022, um 21:29, schrieb Oleh Kravchenko: > do_install[mcdepends] = "mc:initramfs::core-image-minimal:do_image_complete" I have zero practical experience with multiconfig, but isn't this missing one argument? See here: https://github.com/JPEWdev/meta-multiconfig-demos/b

[yocto] Booting my raspberry pi image hangs at some point. Where exactly?

Hi all, I can netboot my Raspberry Pi 4 still fine, but when I flash the image onto a usb drive using wic, booting fails. I just stops to boot at one point. I'd be glad if someone could tell me where it's hanging so I could try to start tracking it down at the right place. All metalayers are on

Re: [yocto] qemu: Enable guest access to the internet

Hi Richard, Am Sa, 19. Mär 2022, um 13:00, schrieb Richard Purdie: > SLIRP only allows specific ports and will not work for general internet > connectivity. It can be done without root but the downside is it isn't as > powerful. TAP would allow the guest internet access but needs to be setup in >

Re: [yocto] qemu: Enable guest access to the internet

Hi Matthias, Am Sa, 19. Mär 2022, um 08:43, schrieb Matthias Klein: > Then everything worked through the tap device. Please note I'd like to use SLIRP instead of TAP as TAP needs root on the host. But I guess I could just try it for once, just to see if it works... Regards, Manuel -=-=-=-=-=-=

[yocto] qemu: Enable guest access to the internet

Hi all, I would like to configure my host to allow the yocto-built qemu guest access the internet. I'm running qemu with kvm virtualization and slirp, and according to [1] it should just work. I'd like to find out why it doesn't. [1] https://www.linux-kvm.org/page/Networking#User_Networking He

Re: [yocto] How to manage disk space while working with Yocto?

Am Mi, 16. Mär 2022, um 08:54, schrieb Sourabh Hegde: > I have tried deleting `$TMPDIR (build/tmp)`, `$SSTATE_DIR > (build/sstate-cache)`, `$DL_DIR (build/downloads)`. But these things didn't > help me. These directories are crucial for a yocto build and they will get recreated if not existing.

[yocto] Still affected by recent pkgconfig-native issue

Hi all, my dunfell build for a NVIDIA Jetson TX2 (support from meta-tegra) is failing in the way described here: https://lists.yoctoproject.org/g/yocto/topic/86571641#55134. As per a comment of Richard Purdie, it should already be fixed. I seem still affected, though. I digged into it and

Re: [yocto] Yocto suddenly creating directories with 700 instead 755.

Am Fr, 12. Nov 2021, um 11:35, schrieb Richard Purdie: > On Thu, 2021-11-11 at 18:28 -0500, Stephen John Smoogen wrote: >> On Thu, 11 Nov 2021 at 11:10, Manuel Wagesreither wrote: >> > >> > Hello all, >> > >> > sorry, wall of text incoming. >>

[yocto] Yocto suddenly creating directories with 700 instead 755.

Hello all, sorry, wall of text incoming. tl;dr: If recipes install directories with `install -d path/to/dir`, how is the default mode determined? What can cause it suddenly (that is, without updating metalayers or similar) to change from 755 to 700? full version: our CI is throwing "Transact

Re: [yocto] User configuration & host contamination

Hi Jeffrey, Am Do, 4. Nov 2021, um 11:00, schrieb Jeffrey Simons: > Hi all, > > I'm having some difficulty with setting up users and the respective > application user assignments. I have a generic recipe which inherits > useradd and sets a user, this > works great for my purpose without one exce

Re: [yocto] How to enable graphics acceleration on qemux86-64?

Hi all, hi Alexander, I solved my problems. Things work fine now. Below I'm summing things up as documentation for myself and also others in case this pops up in someones search query. Am So, 17. Okt 2021, um 13:32, schrieb Alexander Kanavin: > On Sat, 16 Oct 2021 at 14:08, Manuel Wage

Re: [yocto] How to enable graphics acceleration on qemux86-64?

Am Mi, 13. Okt 2021, um 22:56, schrieb Alexander Kanavin: > If you switch to master, it's best if you make a new build directory and dont > reuse the one you have. > > Alex > > On Wed, 13 Oct 2021 at 22:09, Manuel Wagesreither wrote: >> __ >> `export DI

Re: [yocto] How to enable graphics acceleration on qemux86-64?

`export DISPLAY=:0` did the trick. The following shows when still on poky dunfell: * I can now boot `runqmu kvm slirp sdl core-image-weston`. But gui is still slow. I cannot even type `systemctl poweroff` in weston-terminal, it inevitably becomes `wweesssttooo[...]`. * `runqemu kvm slirp sdl gl

Re: [yocto] How to enable graphics acceleration on qemux86-64?

Hi Alex, Am Fr, 8. Okt 2021, um 11:00, schrieb Alexander Kanavin: > Something in your custom setup disables opengl in qemu-system-native. > > Can you try core-image-weston with plain poky only? > > This is the test we use to ensure it does work, it lists all the settings > that have to be in p

[yocto] How to enable graphics acceleration on qemux86-64?

Hello all, How can I enable graphics acceleration on qemux86-64? My image is using wayland with weston and the GUI is not exactly fast. * When I do `runqemu slirp kvm gtk`, it throws the following error: `runqemu - ERROR - Failed to run qemu: qemu-system-x86_64: Display 'gtk' is not available.`

Re: [yocto] [OE-core] Incorrect systemd timer

Am Di, 28. Sep 2021, um 03:43, schrieb JH: >> perhaps use >> OnCalendar=*-*-* *:*:00 > > No, the same result, completely bewildered why the timer does not work > in Yocto Linux Is the timer unit shadowed by some other timer? Mind that units can live in * `/lib/systemd/system/`, * `/etc/systemd/sy

Re: [yocto] Gtk+3 applications are missing icons.

trying to open. > > Alex > > On Sun, 26 Sept 2021 at 00:58, Manuel Wagesreither wrote: >> Hello all, >> >> I built an image based on core-image and added the package gtk+3-demos. I'm >> using wayland with weston compositor. Unfortunately icons seem to

Re: [yocto] Gtk+3 applications are missing icons.

Am So, 26. Sep 2021, um 00:58, schrieb Manuel Wagesreither: > I built an image based on core-image and added the package gtk+3-demos. > I'm using wayland with weston compositor. Unfortunately icons seem to > be missing. Can anyone give me a hint on what went wrong? I'm on &g

[yocto] Gtk+3 applications are missing icons.

Hello all, I built an image based on core-image and added the package gtk+3-demos. I'm using wayland with weston compositor. Unfortunately icons seem to be missing. Can anyone give me a hint on what went wrong? I'm on Dunfell. Here's a screenshot: https://imgur.com/syLzQ1l Thanks a lot! Manuel

Re: [yocto] Wayland and X11 on Yocto

Hi all, hi Khem, Am Do, 19. Aug 2021, um 00:22, schrieb Khem Raj: > On Wed, Aug 18, 2021 at 3:06 PM Manuel Wagesreither > wrote: > > > > Hello all, > > > > I'm building an image to run on various SBCs and would like to equip it > > with a graphical

Re: [yocto] Wayland and X11 on Yocto

Am Do, 19. Aug 2021, um 00:22, schrieb Khem Raj: > On Wed, Aug 18, 2021 at 3:06 PM Manuel Wagesreither > wrote: > > > > Hello all, > > > > I'm building an image to run on various SBCs and would like to equip it > > with a graphical interface. > > &

[yocto] Wayland and X11 on Yocto

Hello all, I'm building an image to run on various SBCs and would like to equip it with a graphical interface. There are quite a few things very unclear to me. Can someone help me with that? * Why is X11 enabled by setting an IMAGE_FEATURE (namely x11, x11-base or x11-sato), while Wayland is

Re: [yocto] [meta-raspberrypi] Would like to run xterm on Raspberry Pi 4 but Xorg fails with "module fbdev not found"

Hello all, Am So, 15. Aug 2021, um 22:36, schrieb Manuel Wagesreither: > I'm building my project for qemux86-64 and Raspberry Pi 4. Currently, > when booted, it displays a textual root shell. I can work with it in > both qemu and Raspi and all is good. Now I want to chan

[yocto] ZFS/ZoL on Yocto

Hello all, I would like to know if anyone has experiences with equipping Yocto created images with ZFS support. If I'm not mistaken, the main problems of using ZFS in linux are of legal nature. ZFS can not go into the linux kernel source tree, as it conflicts with the GPL. Hence, the linux ver

[yocto] [meta-raspberrypi] Would like to run xterm on Raspberry Pi 4 but Xorg fails with "module fbdev not found"

Hello all, I'm building my project for qemux86-64 and Raspberry Pi 4. Currently, when booted, it displays a textual root shell. I can work with it in both qemu and Raspi and all is good. Now I want to change my image to display a graphical terminal when booted. On qemu, this already works. In

Re: [yocto] Cannot build yocto anymore after updating all layers to current dunfell branch tips

Am So, 15. Aug 2021, um 03:39, schrieb Khem Raj: > On 8/14/21 5:29 AM, Manuel Wagesreither wrote: > > Am Fr, 13. Aug 2021, um 23:59, schrieb Steve Sakoman: > >> On Fri, Aug 13, 2021 at 11:29 AM Manuel Wagesreither > >> wrote: > >>> > >>> Hello

Re: [yocto] Cannot build yocto anymore after updating all layers to current dunfell branch tips

Am Sa, 14. Aug 2021, um 12:14, schrieb Robert Berger: > On 14/08/2021 00:28, Manuel Wagesreither wrote: > > Hello all, > > > > I updated the layers of my project to the current dunfell branch tips. See > > here: > > https://gitlab.com/manue

Re: [yocto] Cannot build yocto anymore after updating all layers to current dunfell branch tips

Am Fr, 13. Aug 2021, um 23:59, schrieb Steve Sakoman: > On Fri, Aug 13, 2021 at 11:29 AM Manuel Wagesreither > wrote: > > > > Hello all, > > > > I updated the layers of my project to the current dunfell branch tips. See > > here: > > https://gitlab.

[yocto] Cannot build yocto anymore after updating all layers to current dunfell branch tips

Hello all, I updated the layers of my project to the current dunfell branch tips. See here: https://gitlab.com/manuel_wagesreither/bora-proj/-/commit/de631634d7556987d2551d0cedca8f67530bc78d Since then, the build is failing with the following message: ``` ERROR: ParseError at /home/manuel/bora

Re: [yocto] Where to define username/password when fetching sstate via http with basic authentication?

Hi Quentin, obviously I didn't read that page carefully enough. Sorry for the noise and thanks for the hint. Cheers, Manuel Am Fr, 28. Mai 2021, um 11:35, schrieb Quentin Schulz: > Hi Manuel, > > On Fri, May 28, 2021 at 11:26:26AM +0200, Manuel Wagesreither wrote: > > He

[yocto] Where to define username/password when fetching sstate via http with basic authentication?

Hello all, to speed up builds, we would like to make the CI generated sstate-cache available via internet. Due to IP concerns, we don't want to make it publically available but for authenticated hosts only. [1] indicates it is possible to serve the sstate-cache over http with basic authenticat

Re: [yocto] [meta-raspberrypi] Booting a Raspberry Pi 4 using PXE

Hello Anton, Am Mi, 5. Mai 2021, um 15:34, schrieb Anton Antonov: > I don't know what exactly you mean by "whenever the Raspi is booting over the > network". > When a machine boots from network (i,e. using DHCP/BOOTP) then usually DHCP > server points to, for example, a TFTP server where the ke

Re: [yocto] [meta-raspberrypi] Booting a Raspberry Pi 4 using PXE

k you, Regards, Manuel Am So, 2. Mai 2021, um 13:59, schrieb Manuel Wagesreither: > Hello all! > > Since a certain eeprom version, the Raspberry Pi 4 can directly boot from > network. Has anyone experience on this? > > I already managed to to have the Raspi to load the kernel and

[yocto] [meta-raspberrypi] Booting a Raspberry Pi 4 using PXE

Hello all! Since a certain eeprom version, the Raspberry Pi 4 can directly boot from network. Has anyone experience on this? I already managed to to have the Raspi to load the kernel and all the device tree stuff over network. I then exported `build/tmp/work/raspberrypi4_64-poky-linux/bora-ima

Re: [yocto] what to include in a "hardware bringup image"?

Hi, ethtool can be used to check the network cable connection status and the autonegotiated link speed. That way you can make sure the port was soldered on correctly. Regards, Manuel Am Do, 15. Apr 2021, um 10:24, schrieb Robert P. J. Day: > > for a current project (and subsequent projects