/sbin/fbcondecor_ctl: no such file or directory

[bilbotux]

Hi, I'm trying to add fbcondecor to my computer, but I'm having some troubles:

first, when compiling splashutils I get the following message:

Code: Select all

 * The kernel tree against which dev-libs/klibc was built was not patched
 * with a compatible version of fbcondecor. Splashutils will be compiled
 * without fbcondecor support (i.e. verbose mode will not work).

The klibc installed on my computer is the latest (my computer is ~amd64 profile, kernel tuxonice-2.6.23):

Code: Select all

bilbotux portage # emerge -pv klibc

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] dev-libs/klibc-1.5.7-r2  USE="-debug (-n32)" 0 kB

Thus, when I boot my computer, I got following messages when starting the fbcondecor service:

Code: Select all

fbcondecor       | * Setting framebuffer console images ...
fbcondecor       |/etc/init.d/fbcondecor: line 43: /sbin/fbcondecor_ctl: No such file or directory
fbcondecor       |/etc/init.d/fbcondecor: line 43: /sbin/fbcondecor_ctl: No such file or directory
fbcondecor       |/etc/init.d/fbcondecor: line 15: /sbin/fbcondecor_ctl: No such file or directory
fbcondecor       | * Failed to set background image on tty2
fbcondecor       | * ERROR: fbcondecor failed to start

I've searched but found nothing about this in bugzilla or in the forums. Should I fill a bug report ?

Thanks,

[Sadako]

What kernel sources are you using exactly?

I believe the patches required are only a part of gentoo-sources.

[bilbotux]

What kernel sources are you using exactly?

I believe the patches required are only a part of gentoo-sources.

As said in my first post, I'm using the tuxonice-sources-2.6.23. I think that the tuxonice sources have the same patches as the gentoo-sources plus the tuxonice patch.
But the message I get during the emerge of splahsutils is complaining about the klibc sources, not the kernel sources.

[Sadako]

As said in my first post, I'm using the tuxonice-sources-2.6.23. I think that the tuxonice sources have the same patches as the gentoo-sources plus the tuxonice patch.
But the message I get during the emerge of splahsutils is complaining about the klibc sources, not the kernel sources.

The error output you posted gives you the answer to this; "The kernel tree against which dev-libs/klibc was built"
klibc is actually built against he sources in /usr/src/linux

[topic=611282]This[/topic] posty seems identical, check out the bug referenced.

[bilbotux]

As said in my first post, I'm using the tuxonice-sources-2.6.23. I think that the tuxonice sources have the same patches as the gentoo-sources plus the tuxonice patch.
But the message I get during the emerge of splahsutils is complaining about the klibc sources, not the kernel sources.

The error output you posted gives you the answer to this; "The kernel tree against which dev-libs/klibc was built"
klibc is actually built against he sources in /usr/src/linux

[topic=611282]This[/topic] posty seems identical, check out the bug referenced.

Well, I do not see the relation: my /usr/src/linux points to the sources that tuxonice-sources extracted when it was installed; which have all the patches of the gentoo-sources plus some additional ones.
I'm more thinking that the problem is located in the klibc sources, quite similar to this bug that was recently solved: http://bugs.gentoo.org/show_bug.cgi?id=198937.

[Habbit]

Seems that last iterations of the klibc ebuild no longer build against /usr/src/linux, but against its private kernel tree, concretely a vanilla-sources-2.6.23 kernel with _some_ of the patches from gentoo-sources.

[noursbleu]

Hi,

This is how it works now :

klibc ebuild create a work directory where kernel sources are unpacked and patched.
klibc isn't build against /usr/src/linux anymore but against /var/tmp/portage/dev-libs/klibc-1.5.7-r2/work/linux-2.6.23.
The problem comes from that : those sources anren't patched with fbcondecor patch.

I've done this way :

Code: Select all

1) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild unpack
2) download fbcondecor patch : http://dev.gentoo.org/~spock/projects/fbcondecor/archive/fbcondecor-0.9.4-2.6.23-rc7.patch to /home/your_home
3) cd /var/tmp/portage/dev-libs/klibc-1.5.7-r2/work/linux-2.6.23
4) patch -p1 < /home/your_home/fbcondecor-0.9.4-2.6.23-rc7.patch
5) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild merge
6) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild clean
7) emerge splashutils

Portage won't complain anymore about klibc

hope this will help

[bilbotux]

Hi,

This is how it works now :

klibc ebuild create a work directory where kernel sources are unpacked and patched.
klibc isn't build against /usr/src/linux anymore but against /var/tmp/portage/dev-libs/klibc-1.5.7-r2/work/linux-2.6.23.
The problem comes from that : those sources anren't patched with fbcondecor patch.

I've done this way :

Code: Select all

1) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild unpack
2) download fbcondecor patch : http://dev.gentoo.org/~spock/projects/fbcondecor/archive/fbcondecor-0.9.4-2.6.23-rc7.patch to /home/your_home
3) cd /var/tmp/portage/dev-libs/klibc-1.5.7-r2/work/linux-2.6.23
4) patch -p1 < /home/your_home/fbcondecor-0.9.4-2.6.23-rc7.patch
5) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild merge
6) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild clean
7) emerge splashutils

Portage won't complain anymore about klibc

hope this will help

Ok, I've just tested and this works, thanks man.
During the patch, twho chunks failed, but I manually resolve them, and it works.

A couple days ago, I submited a bug report about this (http://bugs.gentoo.org/show_bug.cgi?id=199582) and Spock said that he will ship the headers with splashutils in the next release.

[gimpel]

Thanks for that hint. Worked fine.

About the rejects.. seems latest klibc compiles against 2.6.24-rc, so get the fbcondecor patch from gentoo sources trunk:
http://dev.gentoo.org/~dsd/genpatches/t ... -rc7.patch

[andrewwalker27]

Just thought I'd mention you need fbcondecor flag set for splashutils, I spent ages working that one out! If you don't, fbcondecor_ctl won't get built.
Now for my question, I now get the message

athlon64 fred # splash_manager -c set -t livecd-2007.0 --tty=2
Failed to open the fbcon_decor control device.
Failed to open the fbcon_decor control device.

so what am I doing wrong? Idon't know much about patching, I did as you said but wasn't sure what you meant about the following
During the patch, twho chunks failed, but I manually resolve them, and it works.
Could this be my problem?

[bilbotux]

Yes, you need the fbcondecor flag

If you are not familiar to manual patching, maybe you should wait a couple days: yesterday, spock closed the bug report I filled with this comment:

Fixed in media-gfx/splashutils-1.5.3. Please note that as of 1.5.3, support
for the fbcondecor patch is controlled by the 'fbcondecor' USE flag.

So I guess that it will soon be in portage.

About the two chunks that failed, I don't exactly remember what was the problem in the sources, but I guess this won't compile if patch didn't succesfully applied. As for the problem you are having, I can't help a lot since I didn't experience one similar.

[gerardo]

I tried compiling klibc with the above method, with no succes:

Code: Select all

 * Messages for package dev-libs/klibc-1.5.7-r2:

 * Applying patch-2.6.24-rc2.bz2 ...
 * Applying klibc-1.4.11-interp-flags.patch ...
 * Applying klibc-1.5-sigaction.patch ...
 * Applying klibc-1.5-klibcasmarch.patch ...
 * 
 * ERROR: dev-libs/klibc-1.5.7-r2 failed.
 * Call stack:
 *               ebuild.sh, line   35:  Called src_compile
 *             environment, line 2176:  Called die
 * The specific snippet of code:
 *       emake EXTRA_KLIBCAFLAGS="-Wa,--noexecstack" EXTRA_KLIBCLDFLAGS="-z,noexecstack" HOSTCC="${HOSTCC}" CC="${CC}" INSTALLDIR="/usr/${libdir}/klibc" KLIBCARCH=${KLIBCARCH} KLIBCASMARCH=${KLIBCASMARCH} SHLIBDIR="/${libdir}" libdir="/usr/${libdir}" mandir="/usr/share/man" ${myargs} || diefunc "$FUNCNAME" "$LINENO" "$?" "Compile failed!";
 *  The die message:
 *   Compile failed!
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-libs/klibc-1.5.7-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/klibc-1.5.7-r2/temp/environment'.

These are the lines from build.log:

Code: Select all

scripts/kconfig/conf -s arch/x86/Kconfig.x86_64
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  CC      arch/x86/kernel/asm-offsets.s
  GEN     include/asm-x86/asm-offsets.h
  CALL    scripts/checksyscalls.sh
defconfig has changed, please remove or edit .config
make: *** [.config] Error 1

There is also a bug open for this.

[kasim]

It works with klibc-1.5.8 and gentoo-sources 2.6.24-r4. Thank you very much~!

Hi,

This is how it works now :

klibc ebuild create a work directory where kernel sources are unpacked and patched.
klibc isn't build against /usr/src/linux anymore but against /var/tmp/portage/dev-libs/klibc-1.5.7-r2/work/linux-2.6.23.
The problem comes from that : those sources anren't patched with fbcondecor patch.

I've done this way :

Code: Select all

1) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild unpack
2) download fbcondecor patch : http://dev.gentoo.org/~spock/projects/fbcondecor/archive/fbcondecor-0.9.4-2.6.23-rc7.patch to /home/your_home
3) cd /var/tmp/portage/dev-libs/klibc-1.5.7-r2/work/linux-2.6.23
4) patch -p1 < /home/your_home/fbcondecor-0.9.4-2.6.23-rc7.patch
5) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild merge
6) ebuild /usr/portage/dev-libs/klibc/klibc-1.5.7-r2.ebuild clean
7) emerge splashutils

Portage won't complain anymore about klibc

hope this will help