[opensuse-arm] Mesa in JeOS initial initrd
Hi, I've found that we have Mesa package in initial initrd in our JeOSes. Do we really need it? I estimated it takes about 20MB of 130MB total size of uncompressed initrd. Typical ARM boards don't have lots of RAM like big x86 servers. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 21.09.14 14:32, Matwey V. Kornilov wrote:
Hi,
I've found that we have Mesa package in initial initrd in our JeOSes. Do we really need it? I estimated it takes about 20MB of 130MB total size of uncompressed initrd.
I don't see why it should be there, no. Can you find out why it ends up in the initrd? Kiwi should only put things there that are marked as "bootinclude". Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea... you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way: [ 544s] + /usr/bin/zypper --non-interactive --pkg-cache-dir /var/cache/kiwi/packages --reposd-dir /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545//var/cache/kiwi/zypper/repos --solv-cache-dir /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545//var/cache/kiwi/zypper/solv --cache-dir /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545//var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.3545 --no-gpg-checks --root /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545 install --auto-agree-with-licenses --no-recommends atftp bc bind-libs bind-utils bootsplash btrfsprogs busybox bzip2 cryptsetup curl dialog diffutils dmraid dosfstools dtb-omap3 e2fsprogs fbiterm file filesystem fribidi genisoimage gettext-runtime glibc glibc-locale hwinfo iproute2 iputils kernel-default kiwi-tools kmod-compat kpartx lvm2 make net-tools netcfg parted pciutils procps psmisc python-base squashfs sysconfig sysfsutils sysvinit-tools tar u-boot-omap3beagle udev util-linux which xfsprogs xz So the task here would be to figure out which of these packages implicitly pull in Mesa. No idea which way would be the easiest to do so though ;). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
fbiterm pulls whole the X server (libXfont.so.1) and I think Mesa is requirement by some of X packages. 2014-09-21 17:35 GMT+04:00 Alexander Graf <agraf@suse.de>:
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log
https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea...
you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way:
[ 544s] + /usr/bin/zypper --non-interactive --pkg-cache-dir /var/cache/kiwi/packages --reposd-dir /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545//var/cache/kiwi/zypper/repos --solv-cache-dir /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545//var/cache/kiwi/zypper/solv --cache-dir /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545//var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.3545 --no-gpg-checks --root /usr/src/packages/KIWI-oem/oem/boot-VMX.Ed86zm/kiwi-VMXboot-3545 install --auto-agree-with-licenses --no-recommends atftp bc bind-libs bind-utils bootsplash btrfsprogs busybox bzip2 cryptsetup curl dialog diffutils dmraid dosfstools dtb-omap3 e2fsprogs fbiterm file filesystem fribidi genisoimage gettext-runtime glibc glibc-locale hwinfo iproute2 iputils kernel-default kiwi-tools kmod-compat kpartx lvm2 make net-tools netcfg parted pciutils procps psmisc python-base squashfs sysconfig sysfsutils sysvinit-tools tar u-boot-omap3beagle udev util-linux which xfsprogs xz
So the task here would be to figure out which of these packages implicitly pull in Mesa. No idea which way would be the easiest to do so though ;).
Alex
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
21.09.2014 17:35, Alexander Graf пишет:
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log
https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea...
you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way:
I have no idea why: linux:~ # LANG=c zypper in bootsplash Loading repository data... Reading installed packages... 'bootsplash' not found in package names. Trying capabilities. Resolving package dependencies... The following 48 NEW packages are going to be installed: Mesa Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 fontconfig gnu-unifont-bitmap-fonts libLLVM libX11-xcb1 libXdamage1 libXext6 libXfixes3 libXft2 libXrender1 libXxf86vm1 libcairo2 libdrm2 libdrm_freedreno1 libdrm_nouveau2 libdrm_radeon1 libfreetype6 libgbm1 libgraphite2-3 libharfbuzz0 libpango-1_0-0 libpixman-1-0 libply-boot-client2 libply-splash-core2 libply-splash-graphics2 libply2 libpng16-16 libwayland-client0 libwayland-server0 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-render0 libxcb-shm0 libxcb-sync1 libxcb-xfixes0 libxshmfence1 pango-tools plymouth plymouth-branding-openSUSE plymouth-dracut plymouth-plugin-label plymouth-plugin-script plymouth-scripts 48 new packages to install. Overall download size: 14.2 MiB. Already cached: 0 B After the operation, additional 52.6 MiB will be used. Continue? [y/n/? shows all options] (y): n -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2014-09-21 17:35 GMT+04:00 Alexander Graf <agraf@suse.de>:
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log
https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea...
you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way:
I've found that plymouth (providing bootsplash) requires libdrm.so.2()(64bit) Do we really need plumouth for ARM JeOSes? -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 22.09.14 19:19, Matwey V. Kornilov wrote:
2014-09-21 17:35 GMT+04:00 Alexander Graf <agraf@suse.de>:
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log
https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea...
you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way:
I've found that plymouth (providing bootsplash) requires libdrm.so.2()(64bit) Do we really need plumouth for ARM JeOSes?
I'd say no, but I have no idea how everything else reacts when it's not around. Furthermore, why do we get all these dependencies pulled in while dracut can handle plymouth without X just fine? Something seems broken in the packaging hints of Requires vs Suggests. Alex (For people joining in on the discussion, the initial kiwi initrd is heavily bloated because it contains a good amount of the X stack, Mesa and much more fun nobody needs. Hence it takes very long to load and may even exceed RAM on some machines) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2014-09-22 21:24 GMT+04:00 Alexander Graf <agraf@suse.de>:
Furthermore, why do we get all these dependencies pulled in while dracut can handle plymouth without X just fine? Something seems broken in the packaging hints of Requires vs Suggests.
plymouth package supplies file /usr/lib/plymouth/renderers/drm.so # ldd renderers/drm.so libdrm.so.2 => not found libply-splash-core.so.2 => not found libply.so.2 => not found libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6f3c000) libc.so.6 => /lib/libc.so.6 (0xb6e03000) /lib/ld-linux-armhf.so.3 (0xb6f7a000) So, I think it is auto-dependence. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, Sep 22, 2014 at 07:24:11PM +0200, Alexander Graf wrote:
On 22.09.14 19:19, Matwey V. Kornilov wrote:
2014-09-21 17:35 GMT+04:00 Alexander Graf <agraf@suse.de>:
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log
https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea...
you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way:
I've found that plymouth (providing bootsplash) requires libdrm.so.2()(64bit) Do we really need plumouth for ARM JeOSes?
I'd say no, but I have no idea how everything else reacts when it's not around.
plymouth is supposed to make booting shiny and to replace the splashscreen previously located in our kernel. plymouth is known to break things badly. So, honestly it's always a good idea to get rid of it, if you don't need it.
Furthermore, why do we get all these dependencies pulled in while dracut can handle plymouth without X just fine? Something seems broken in the packaging hints of Requires vs Suggests.
Alex
(For people joining in on the discussion, the initial kiwi initrd is heavily bloated because it contains a good amount of the X stack, Mesa and much more fun nobody needs. Hence it takes very long to load and may even exceed RAM on some machines)
It's weird to see such deps only on arm and not on other machines. I don't think plymouth needs more than libdrm of the X stack. CU, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Stefan Dirsch <sndirsch@suse.de> writes:
It's weird to see such deps only on arm and not on other machines. I don't think plymouth needs more than libdrm of the X stack.
plymouth requires plymouth-plugin-label (via plymouth-branding), which requires cairo. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Could somebody please explain how to disable bootstrap for kiwi? Removing <bootstrap> doesn't work 2014-09-23 16:06 GMT+04:00 Andreas Schwab <schwab@suse.de>:
Stefan Dirsch <sndirsch@suse.de> writes:
It's weird to see such deps only on arm and not on other machines. I don't think plymouth needs more than libdrm of the X stack.
plymouth requires plymouth-plugin-label (via plymouth-branding), which requires cairo.
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Stephan, Could you please point out why there is a Requires: plymouth-plugin-label in Base:System/branding-openSUSE/branding-openSUSE.spec My dracut generated initrd does not contain label.so, and there seems to be no mentions of label in openSUSE/plymouth/theme/openSUSE.script
From plymouth docs I learned only that it is plugin for "text label for text output".
2014-09-23 16:06 GMT+04:00 Andreas Schwab <schwab@suse.de>:
Stefan Dirsch <sndirsch@suse.de> writes:
It's weird to see such deps only on arm and not on other machines. I don't think plymouth needs more than libdrm of the X stack.
plymouth requires plymouth-plugin-label (via plymouth-branding), which requires cairo.
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 11.10.2014 um 09:36 schrieb Matwey V. Kornilov:
Hi Stephan,
Could you please point out why there is a
Requires: plymouth-plugin-label
in Base:System/branding-openSUSE/branding-openSUSE.spec
My dracut generated initrd does not contain label.so, and there seems to be no mentions of label in openSUSE/plymouth/theme/openSUSE.script From plymouth docs I learned only that it is plugin for "text label for text output".
No, I can't. And I don't think I added it Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Raymond, We are discussing this sr: https://build.opensuse.org/package/rdiff/Base:System/branding-openSUSE?linkrev=base&rev=116 and purpose to require plymouth-plugin-label package here. plymouth-plugin-label requires full X11 stack with GL and Mesa, that leads to over-bloated kiwi-generated initrd. 2014-10-11 13:05 GMT+04:00 Stephan Kulow <coolo@suse.de>:
Am 11.10.2014 um 09:36 schrieb Matwey V. Kornilov:
Hi Stephan,
Could you please point out why there is a
Requires: plymouth-plugin-label
in Base:System/branding-openSUSE/branding-openSUSE.spec
My dracut generated initrd does not contain label.so, and there seems to be no mentions of label in openSUSE/plymouth/theme/openSUSE.script From plymouth docs I learned only that it is plugin for "text label for text output".
No, I can't. And I don't think I added it
Greetings, Stephan
-- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn.
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
2014-09-21 17:35 GMT+04:00 Alexander Graf <agraf@suse.de>:
On 21.09.14 15:30, Matwey V. Kornilov wrote:
2014-09-21 17:25 GMT+04:00 Alexander Graf <agraf@suse.de>:
Can you find out why it ends up in the initrd?
I am not sure, that I know optimal way to do it.
Me neither, but if you look at the build log
https://build.opensuse.org/build/openSUSE:Factory:ARM/images/armv7l/JeOS-bea...
you will be able to spot the zypper command that kiwi uses to install its initrd packages which ends up resolving Mesa along the way:
I've found that plymouth (providing bootsplash) requires libdrm.so.2()(64bit)
libdrm doesn't require Mesa. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Alexander Graf -
Andreas Schwab -
Matwey V. Kornilov -
Stefan Dirsch -
Stephan Kulow