* How to use linux-firmware to install single firmware package? #kirkstone
@ 2022-11-03 23:07 Livius
2022-11-04 9:13 ` [OE-core] " Quentin Schulz
0 siblings, 1 reply; 9+ messages in thread
From: Livius @ 2022-11-03 23:07 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
Hi,
I would like to install linux-firmware-ath10k and linux-firmware-imx-sdma-imx7d firmware package to my image recipe in kirkstone release but when i append them to IMAGE_INSTALL somewhy each pack from linux-firmware recipe installs itself. It is extramly large in size about 500 MB, it is totaly not accaptable for me, it is too large.
I am using the following syntax to install them:
IMAGE_INSTALL:append = " linux-firmware-imx-sdma-imx7d linux-firmware-ath10k"
If i remove them, there are no any linux-firmware in my deployed image, it means somehow they trigger to install the full linux-firmware pack, how can i use it to install only some single linux-firmware?
[-- Attachment #2: Type: text/html, Size: 755 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] How to use linux-firmware to install single firmware package? #kirkstone
2022-11-03 23:07 How to use linux-firmware to install single firmware package? #kirkstone Livius
@ 2022-11-04 9:13 ` Quentin Schulz
2022-11-04 12:42 ` Livius
0 siblings, 1 reply; 9+ messages in thread
From: Quentin Schulz @ 2022-11-04 9:13 UTC (permalink / raw)
To: Livius, openembedded-core
Hi Livius,
On 11/4/22 00:07, Livius wrote:
> Hi,
>
> I would like to install linux-firmware-ath10k and linux-firmware-imx-sdma-imx7d firmware package to my image recipe in kirkstone release but when i append them to IMAGE_INSTALL somewhy each pack from linux-firmware recipe installs itself. It is extramly large in size about 500 MB, it is totaly not accaptable for me, it is too large.
>
> I am using the following syntax to install them:
>
> IMAGE_INSTALL:append = " linux-firmware-imx-sdma-imx7d linux-firmware-ath10k"
>
This seems correct to me.
> If i remove them, there are no any linux-firmware in my deployed image, it means somehow they trigger to install the full linux-firmware pack, how can i use it to install only some single linux-firmware?
>
There might be an issue somewhere, we need to debug this. Can you
reproduce this with only poky?
Which version of oe-core/yocto are you using?
Can you run bitbake -g <your-image>? Check that only your
linux-firmwasre packages are installed in the image. You can also check
that the linux-firmware packages don't contain more files than they
should (either look into the .rpm/.deb/.ipk packages in tmp/deploy or in
WORKDIR/packages/ of linux-firmware). Also look at the .dot files with
your favorite text editor and check what does linux-firmware-ath10k
bring in as a dependency, maybe there's a bad dependency somewhere that
brings some other packages in.
Cheers,
Quentin
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 9:13 ` [OE-core] " Quentin Schulz
@ 2022-11-04 12:42 ` Livius
2022-11-04 14:07 ` [OE-core] " Quentin Schulz
0 siblings, 1 reply; 9+ messages in thread
From: Livius @ 2022-11-04 12:42 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
In my tmp/deploy/rpm/noarch folder i can see many-many other firmware .rpm files like linux-firmware-bcm43xx, linux-firmware-nvidia-tegra and so on, these were not planed to be installed. It seems to me, the full linux-firmware package was deployed somehow. I think i am using poky now, this is my path for linux-firmware: PROJECT/sources/poky/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
So, my poky come from git.yoctoproject.org ( https://git.yoctoproject.org/poky/log/?h=kirkstone ) , i use latest kirkstone commit ( https://git.yoctoproject.org/poky/commit/?h=kirkstone&id=2e79b199114b25d81bfaa029ccfb17676946d20d ).
In pn-buildlist and task-depends.dot i can see only linux-firmware, i have no any listed single package like should be linux-firmware-imx-sdma-imx7d.
[-- Attachment #2: Type: text/html, Size: 904 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 12:42 ` Livius
@ 2022-11-04 14:07 ` Quentin Schulz
2022-11-04 14:59 ` Vincent Davis Jr
2022-11-04 17:08 ` Livius
0 siblings, 2 replies; 9+ messages in thread
From: Quentin Schulz @ 2022-11-04 14:07 UTC (permalink / raw)
To: Livius, openembedded-core
Hi Livius,
On 11/4/22 13:42, Livius wrote:
> In my tmp/deploy/rpm/noarch folder i can see many-many other firmware .rpm files like linux-firmware-bcm43xx, linux-firmware-nvidia-tegra and so on, these were not planed to be installed. It seems to me, the full linux-firmware package was deployed somehow.
Yes, that's normal. When a recipe is built, all its packages are created
and put into that directory. It's not because the package is created
that it's installed in the final rootfs.
> I think i am using poky now, this is my path for linux-firmware:
PROJECT/sources/poky/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
>
> So, my poky come from git.yoctoproject.org ( https://urldefense.com/v3/__https://git.yoctoproject.org/poky/log/?h=kirkstone__;!!OOPJP91ZZw!iE35Nh5nRc3nFT6cCWMcIbXJsRTSva3-k0ELYN7qrnPobvaTVmufMXyu6PTsr_2phXtEqT4WAHAyDmU3tfm0A0o7KOuVycOZZMX2Wg$ ) , i use latest kirkstone commit ( https://urldefense.com/v3/__https://git.yoctoproject.org/poky/commit/?h=kirkstone&id=2e79b199114b25d81bfaa029ccfb17676946d20d__;!!OOPJP91ZZw!iE35Nh5nRc3nFT6cCWMcIbXJsRTSva3-k0ELYN7qrnPobvaTVmufMXyu6PTsr_2phXtEqT4WAHAyDmU3tfm0A0o7KOuVycMxLdUTqg$ ).
>
And there's no bbappend for linux-firmware anywhere?
Run:
bitbake-layers show-appends linux-firmware
> In pn-buildlist and task-depends.dot i can see only linux-firmware, i have no any listed single package like should be linux-firmware-imx-sdma-imx7d.
>
Mmm indeed, less helpful than I had imagined. I think you can figure out
which packages are installed by adding INHERIT += "buildhistory". It
should create an installed-packages.txt file after a build.
Cheers,
Quentin
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 14:07 ` [OE-core] " Quentin Schulz
@ 2022-11-04 14:59 ` Vincent Davis Jr
2022-11-04 16:18 ` [OE-core] " Alexander Kanavin
2022-11-04 17:08 ` Livius
1 sibling, 1 reply; 9+ messages in thread
From: Vincent Davis Jr @ 2022-11-04 14:59 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
I can confirm I'm seeing something similar with MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "linux-firmware-amdgpu"
I use with OE-core kirkstone HEAD + custom distro config. Was wondering of the best way to debug why issue occurs.
Is there anything else besides bitbake -g <your-image> and INHERIT += "buildhistory" that I can try?
How would one best check what happens during rootfs creation?
[-- Attachment #2: Type: text/html, Size: 419 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 14:59 ` Vincent Davis Jr
@ 2022-11-04 16:18 ` Alexander Kanavin
0 siblings, 0 replies; 9+ messages in thread
From: Alexander Kanavin @ 2022-11-04 16:18 UTC (permalink / raw)
To: Vincent Davis Jr; +Cc: openembedded-core
On Fri, 4 Nov 2022 at 15:59, Vincent Davis Jr <vince@underview.tech> wrote:
> I can confirm I'm seeing something similar with MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "linux-firmware-amdgpu"
>
> I use with OE-core kirkstone HEAD + custom distro config. Was wondering of the best way to debug why issue occurs.
>
> Is there anything else besides bitbake -g <your-image> and INHERIT += "buildhistory" that I can try?
> How would one best check what happens during rootfs creation?
There is a log for it like for any other task - look in
WORKDIR/temp/log.do_rootfs for it. You'll see exact commands issued to
the package manager for one thing. That may help pinpoint where
unwanted packages are being requested and installed.
Alex
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 14:07 ` [OE-core] " Quentin Schulz
2022-11-04 14:59 ` Vincent Davis Jr
@ 2022-11-04 17:08 ` Livius
2022-11-04 18:44 ` Livius
1 sibling, 1 reply; 9+ messages in thread
From: Livius @ 2022-11-04 17:08 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
I have a linux-firmware_%.bbappend ( https://github.com/Freescale/meta-freescale-3rdparty/blob/kirkstone/recipes-kernel/linux-firmware/linux-firmware_%25.bbappend ) from meta-freescale-3rdparty layer. I think, it is too simple, it can not cause the problem. In my local.conf I set up to generate buildhistory (i used the following commands), soon my next image build is ready an i can share the results.
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "0"
[-- Attachment #2: Type: text/html, Size: 552 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 17:08 ` Livius
@ 2022-11-04 18:44 ` Livius
2022-11-07 13:03 ` [OE-core] " Quentin Schulz
0 siblings, 1 reply; 9+ messages in thread
From: Livius @ 2022-11-04 18:44 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
What should i check in buildhistory? In my buildhistory folder linux-firmware folder contains all packages as a subfolders, like was in my tmp/deploy/rpm/noarch. Following content is in my linux-firmware/linux-firmware-imx-sdma-imx7d/latest text file.
PE = 1
PV = 20220913
PR = r0
RPROVIDES =
RDEPENDS = linux-firmware-imx-sdma-license
RRECOMMENDS =
PKGSIZE = 2862
FILES = /lib/firmware/imx/sdma/sdma-imx7d.bin
FILELIST = /lib/firmware/imx/sdma/sdma-imx7d.bin
[-- Attachment #2: Type: text/html, Size: 618 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] How to use linux-firmware to install single firmware package? #kirkstone
2022-11-04 18:44 ` Livius
@ 2022-11-07 13:03 ` Quentin Schulz
0 siblings, 0 replies; 9+ messages in thread
From: Quentin Schulz @ 2022-11-07 13:03 UTC (permalink / raw)
To: Livius, openembedded-core
Hi,
On 11/4/22 19:44, Livius wrote:
> What should i check in buildhistory? In my buildhistory folder linux-firmware folder contains all packages as a subfolders, like was in my tmp/deploy/rpm/noarch. Following content is in my linux-firmware/linux-firmware-imx-sdma-imx7d/latest text file.
>
> PE = 1
> PV = 20220913
> PR = r0
> RPROVIDES =
> RDEPENDS = linux-firmware-imx-sdma-license
> RRECOMMENDS =
> PKGSIZE = 2862
> FILES = /lib/firmware/imx/sdma/sdma-imx7d.bin
> FILELIST = /lib/firmware/imx/sdma/sdma-imx7d.bin
>
The installed-packages.txt would probably list all linux-firmware
packages I assume?
Could you also check the
linux-firmware/linux-firmware-imx-sdma-license/latest text file and tell
us what it contains? Because the content of
linux-firmware/linux-firmware-imx-sdma-imx7d/latest seems to be fine.
Cheers,
Quentin
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-11-07 13:03 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-03 23:07 How to use linux-firmware to install single firmware package? #kirkstone Livius
2022-11-04 9:13 ` [OE-core] " Quentin Schulz
2022-11-04 12:42 ` Livius
2022-11-04 14:07 ` [OE-core] " Quentin Schulz
2022-11-04 14:59 ` Vincent Davis Jr
2022-11-04 16:18 ` [OE-core] " Alexander Kanavin
2022-11-04 17:08 ` Livius
2022-11-04 18:44 ` Livius
2022-11-07 13:03 ` [OE-core] " Quentin Schulz
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.