|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
I tried that first and it was horribly slow. That's why I try hardware acceleration now.
Do you _know_ it doesn't work? If yes, why?
I tried that first and it was horribly slow. That's why I try hardware acceleration now.
Do you _know_ it doesn't work? If yes, why?
|
By
Edgar Mobile
·
#56476
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
If you want an aarch guest on x86, then drop the gl option from
runqemu. This will fall back to software rendering.
Alex
If you want an aarch guest on x86, then drop the gl option from
runqemu. This will fall back to software rendering.
Alex
|
By
Alexander Kanavin
·
#56475
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
Sorry, but I need an Aarch64 guest.
Ok, using a newer qemu I now encounter the following problem:
root@qemuarm64:/usr/bin# XDG_RUNTIME_DIR=/run/user/0 ./eglinfo
EGL client extensions string:
Sorry, but I need an Aarch64 guest.
Ok, using a newer qemu I now encounter the following problem:
root@qemuarm64:/usr/bin# XDG_RUNTIME_DIR=/run/user/0 ./eglinfo
EGL client extensions string:
|
By
Edgar Mobile
·
#56474
·
|
|
[meta-openssl102-fips][dunfell][PATCH 2/2] openssh: Adapt the patch for CVE-2020-14145 fix on poky/dunfell
From: Harshal Gohel <harshaldhruvkumar.gohel@...>
openssh-8.2p1-fips.patch does not apply after CVE-2020-14145 patch
introduced in (poky:
From: Harshal Gohel <harshaldhruvkumar.gohel@...>
openssh-8.2p1-fips.patch does not apply after CVE-2020-14145 patch
introduced in (poky:
|
By
Harshal Gohel
·
#56473
·
|
|
[meta-openssl102-fips][dunfell][PATCH 1/2] conf: Make layer compatible with dunfell
From: Harshal Gohel <harshaldhruvkumar.gohel@...>
Create branch "dunfell" from 634d497355f4169237b97a57a2f32486b0972167
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1
From: Harshal Gohel <harshaldhruvkumar.gohel@...>
Create branch "dunfell" from 634d497355f4169237b97a57a2f32486b0972167
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1
|
By
Harshal Gohel
·
#56472
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
This configuration is not tested. If you want accelerated gl, build
for the qemux86-64 target.
Alex
This configuration is not tested. If you want accelerated gl, build
for the qemux86-64 target.
Alex
|
By
Alexander Kanavin
·
#56471
·
|
|
[meta-selinux][dunfell][PATCH] openssh: don't overwrite sshd_config unconditionally
From: Nisha Parrakat <Nisha.Parrakat@...>
The current implementation was overwriting the sshd_config and sshd
assuming PAM is needed by default
openssh should use the default sshd_config
From: Nisha Parrakat <Nisha.Parrakat@...>
The current implementation was overwriting the sshd_config and sshd
assuming PAM is needed by default
openssh should use the default sshd_config
|
By
Ranjitsinh Rathod
·
#56470
·
|
|
Re: [meta-selinux][PATCH] openssh: don't overwrite sshd_config unconditionally
Hi there,
I have sent the latest rebased patch here.
https://lists.yoctoproject.org/g/yocto/message/56468
Thanks,
Ranjitsinh Rathod
Hi there,
I have sent the latest rebased patch here.
https://lists.yoctoproject.org/g/yocto/message/56468
Thanks,
Ranjitsinh Rathod
|
By
Ranjitsinh Rathod
·
#56469
·
|
|
[meta-selinux][dunfell][PATCH] openssh: don't overwrite sshd_config unconditionally
From: Nisha Parrakat <Nisha.Parrakat@...>
The current implementation was overwriting the sshd_config and sshd
assuming PAM is needed by default
openssh should use the default sshd_config
From: Nisha Parrakat <Nisha.Parrakat@...>
The current implementation was overwriting the sshd_config and sshd
assuming PAM is needed by default
openssh should use the default sshd_config
|
By
Ranjitsinh Rathod
·
#56468
·
|
|
runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
Greetings,
I tried to run an Aarch64 Yocto with qemu on amd 64 Host. For that purpose, I built core-image-weston from Hardknott following the
Greetings,
I tried to run an Aarch64 Yocto with qemu on amd 64 Host. For that purpose, I built core-image-weston from Hardknott following the
|
By
Edgar Mobile
·
#56467
·
|
|
Re: How to manage disk space while working with Yocto?
Yes, I am building Yocto inside docker containers. But previously, I did not face this issue with docker container.
Yes, I am building Yocto inside docker containers. But previously, I did not face this issue with docker container.
|
By
Sourabh Hegde
·
#56466
·
|
|
Re: How to manage disk space while working with Yocto?
Are you running in a virtual machine of some kind? It's better to get a real linux computer. Otherwise you need to check how to allocate more disk space to the virtual machine from the host.
Alex
Are you running in a virtual machine of some kind? It's better to get a real linux computer. Otherwise you need to check how to allocate more disk space to the virtual machine from the host.
Alex
|
By
Alexander Kanavin
·
#56465
·
|
|
Re: How to manage disk space while working with Yocto?
Hi Alex,
Below is the output of "df":
Hi Alex,
Below is the output of "df":
|
By
Sourabh Hegde
·
#56464
·
|
|
Re: How to manage disk space while working with Yocto?
Can you show the output of 'df' please?
Alex
Can you show the output of 'df' please?
Alex
|
By
Alexander Kanavin
·
#56463
·
|
|
Re: How to manage disk space while working with Yocto?
Hello,
Thanks for the update.
Even after deleting build/tmp and build/sstate-cache and setting `INHERIT += "rm_work"` in the build/conf/local.conf.
But still I am facing same issue.
Is there any way
Hello,
Thanks for the update.
Even after deleting build/tmp and build/sstate-cache and setting `INHERIT += "rm_work"` in the build/conf/local.conf.
But still I am facing same issue.
Is there any way
|
By
Sourabh Hegde
·
#56462
·
|
|
Re: [meta-selinux][PATCH] openssh: don't overwrite sshd_config unconditionally
Hi there,
Is there anything pending here from our side?
Can someone let us know by when this patch can be merged?
Thanks,
Ranjitsinh Rathod
Hi there,
Is there anything pending here from our side?
Can someone let us know by when this patch can be merged?
Thanks,
Ranjitsinh Rathod
|
By
Ranjitsinh Rathod
·
#56461
·
|
|
Re: How to manage disk space while working with Yocto?
Only the last two. Deleting tmp/ does help as then any needed binary
items will be taken from sstate cache instead of being unpacked from
source and rebuilt.
Alex
Only the last two. Deleting tmp/ does help as then any needed binary
items will be taken from sstate cache instead of being unpacked from
source and rebuilt.
Alex
|
By
Alexander Kanavin
·
#56460
·
|
|
Re: [PATCH yocto-autobuilder-helper 1/4] scripts: run-docs-build: simplify patching logic
Hi Quentin,
Too late to give you a "Reviewed-by", but thanks for the corrections and
simplifications!
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel
Hi Quentin,
Too late to give you a "Reviewed-by", but thanks for the corrections and
simplifications!
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel
|
By
Michael Opdenacker
·
#56459
·
|
|
Re: How to manage disk space while working with Yocto?
Am Mi, 16. Mär 2022, um 08:54, schrieb Sourabh Hegde:
These directories are crucial for a yocto build and they will get recreated if not existing. Deleting them does nothing besides prolonging the
Am Mi, 16. Mär 2022, um 08:54, schrieb Sourabh Hegde:
These directories are crucial for a yocto build and they will get recreated if not existing. Deleting them does nothing besides prolonging the
|
By
Manuel Wagesreither
·
#56458
·
|
|
Re: How to manage disk space while working with Yocto?
Hi,
This is a common problem. I run to this almost weekly basis doing a lot yocto compiles
on my developer machine.
Solution for me is to manually check before compiling that I still have
100's
Hi,
This is a common problem. I run to this almost weekly basis doing a lot yocto compiles
on my developer machine.
Solution for me is to manually check before compiling that I still have
100's
|
By
Mikko Rapeli <mikko.rapeli@...>
·
#56457
·
|