walterw

Hi digifuzzy, Good call - I think you are most certainly right, I checked and I do not have x11-drivers/xf86-input-synaptics installed, nor the use flags with synaptics (which probably pulls that in). I'm building now and will report back :). Thanks, Walter

Hi all, I am having difficulty getting the touchpad working on my laptop - if I boot up to Ubuntu, it works fine. I played around with removing modules to semi isolate which modules I need and have deduced that I need at least: i2c_hid hid_multitouch When I remove those on Ubuntu, the touchpad stops working. However, merely having those built and available on my funtoo installation is insufficient. I also tried copying the xorg.conf.d/*.conf files for anything resembling input devices and that also did not work (after restarting X11). I will play around more with other kernel modules. I am trying to dig through lspci to see if I'm missing something but it isn't entirely clear to me, perhaps this might be what I need support: Communication Controller: Intel Corporation Point-LP CSME HECI #1 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) Thanks, Walter

Great - good catch.

Hi, I am starting with a base release 1.3 64-bit image and getting this message throughout my build process: Unavailable repository 'gentoo' referenced by masters entry in '/var/git/met a-repo/kits/rust-kit/metadata/layout.conf' It appears whenever I am calling equery l <package-atom>, I am getting this error. Any ideas what might be causing this? Thanks, Walter

Hi all, I built a java-based application that can build Gentoo / Funtoo / Ubuntu (and other Debian-based) systems from within any Linux distribution that has Java installed. The source code is here: https://github.com/walterjwhite/linux-builder And, I have a corresponding "system" to build an image: https://github.com/walterjwhite/funtoo-linux Caveats: 1. I will be updating the code on github as all of the dependencies for the linux-builder project are about a year old. There is no documentation, this needs to be written for anyone to use. 2. My own systems are much more complicated than the sample system there. This is meant to showcase what you CAN do. Furthermore, there is also no documentation as to what patches are available, this needs written. a. a "system" contains patches b. a "patch" contains all the changes necessary for that single patch unit. This could be copying files, creating a user, group, adding a service to a runlevel, installing packages, etc. Patches that are inter-related are linked through "dependencies". This ensures the base patch is installed first so if those files or libraries, etc. are needed, they will be installed prior to installing this patch. It is meant to be as generic as possible so if you want to prepare a configuration for Gentoo and want to translate that to Ubuntu, you can with ease (provided you know the package names and configuration directory). c. a "phase" can be setup, build, update, finalize and provides hooks at various stages of the build process. Say for instance, you need to download a file before you attempt to unpack and install it, you would create a download item in the setup phase. I've been using this system for about 3 years now and my goals are / were to: 1. make it easier to get started with Gentoo / Funtoo 2. allow users to switch across distributions whilst having the same applications, configuration, etc. partially supported, each distribution tends to put files in different places and has different package names thus requiring the packages listed in add-packages to be updated as well as the configuration files to be in the right place 3. share this utility with other linux users (Gentoo, Funtoo, etc.) and see what others' interests were and how this might help them to accomplish those goals 4. allow users to backup their systems easily and restore them to a pristine state 5. provide a means to capture all the patches applied to a system provided in an earlier release, and not currently implemented (relied on python and latex to generate PDF files describing the system) Thanks for your feedback, Walter

Hi cardinal, My distfiles are downloaded to /var/cache/portage/distfiles as best as I can tell and it is installing genkernel-next-68. I overwrote my logs, so I don't have the original message, but here is my /etc/make.conf (it is automatically generated, so I apologize for all the lines, they're organized by patches): http_proxy="http://localhost:8118" CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=x86-64 -O2 -pipe" CXXFLAGS="-march=x86-64 -O2 -pipe" CPU_FLAGS_X86="mmx mmxext sse sse2" MAKEOPTS="-j5" USE="" VIDEO_CARDS="" SANE_BACKENDS="" LINGUAS="" # kernel USE="${USE} symlink -fortran -openmp acpi" # funtoo-network USE="${USE} -networkmanager" # compression USE="${USE} zlib minizip" # lvm USE="${USE} lvm device-mapper" # permissions USE="${USE} pam caps filecaps" # cups USE="${USE} cups" # ext4 USE="${USE} ext4" # luks USE="${USE} cryptsetup" # zsh USE="${USE} zsh-completion" # english LINGUAS="${LINGUAS} en" # compression USE="${USE} lz4" I could remove the symlink and uninstall the kernel and try to reproduce it? Also, for genkernel, I do have a custom init + scripts, so that could be a potential concern, but I also grepped there and do not see anything that'd point to /usr/share/genkernel/src. The error message was for genkernel-next only and it was after building the kernel and modules. I think it was during the initramfs phase. EDIT: I am building a different system that uses ZFS and as such requires an earlier kernel, interestingly enough, that kernel built just fine along with the initramfs (no error messages about files not being in /usr/share/genkernel/src, and that directory does not exist). The one that built is: 4.14.80 and the one that wasn't was 4.19.1. Now, before I upgraded to 1.3-release, the last time I built the other system, it was actually using the 4.20 kernel, so the portage trees must have been different. Furthermore, the last time I built this system, it was actually using the 4.14.90 kernel. I'll have to investigate in more detail, maybe that will shed some light onto what is really going on.

I am trying to build / install funtoo from a stage 3 tarball using the latest 1.3-release and hitting a snag with kernel compilation. All other packages (from what I can tell) are being properly fetched to /var/cache/portage/distfiles and installed. During the kernel compilation (specifically, when generating the initramfs), I'm getting an error: Could not find source tarball /usr/share/genkernel/src/open-iscsi-2.0-872.tar.gz. Please refetch. This is occurring for any files that are required for the init such as busybox and open-iscsi (which oddly enough should not be in my init), I manually copied a file there to see that it'd resolve it and it did just resolve that single one, but I don't want to do it piece meal. Now, the files are in distfiles (/var/cache/portage/distfiles) and I am thinking I can symlink /usr/share/genkernel/src/ to distfiles, but is that required or is there something else broken that is causing this? I did check the install guide and don't see anything alluding to that. I also grepped /etc for any such configuration also to no avail. EDIT: symlinking /usr/share/genkernel/src to /var/cache/portage/distfiles worked and I was able to install gentoo sources. Thanks, Walter

Will funtoo be tracking upstream automatically or will there still be human intervention (even for current)? Also, along the same lines, I noticed that sometimes I have packages I cannot install because my kits don't have that package version available. Is there a utility that exists to perform that dependency check with the kit to ensure accuracy? I am on master so I would expect that to be manually revised / curated whereas 1.3 release would be automatic?

Thanks - I will wait then.

Thanks - I tried that many times. I also started over with a new stage3. My systems with zfs in them all have this problem, the systems without do not. I have no idea why yet.

Thanks - the bug report is closed, what are the next steps for this?

I am attempting to update my systems and for whatever reason, when running: emerge --newuse -uD world -vp mips-sources is complaining of eapi7-ver: EAPI=5 not supported. I don't have mips-sources installed and I'm on an x86/64 system. Calculating dependencies / * ERROR: sys-kernel/mips-sources-4.13.16::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.13.16.ebuild' * mips-sources-4.13.16.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' - * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.13.16::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.13.16::nokit'`. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.13.16/work/linux--20171007' | * ERROR: sys-kernel/mips-sources-4.9.75::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.9.75.ebuild' * mips-sources-4.9.75.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.9.75::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.9.75::nokit'`. - * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.9.75/work/linux--20161216' \ * ERROR: sys-kernel/mips-sources-4.4.110::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.4.110.ebuild' * mips-sources-4.4.110.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.4.110::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.4.110::nokit'`. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.4.110/work/linux--20160123' ... done! Total: 0 packages, Size of downloads: 0 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-python/urllib3:0 dev-python/urllib3-1.23:0/0::python-modules-kit, ebuild scheduled for merge conflicts with <dev-python/urllib3-1.23[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by dev-python/elasticsearch-py-6.3.0:0/0::python-modules-kit, installed Now, the interesting thing is, I only get this error when updating systems with ZFS, but those ebuilds don't appear to have changed recently. I'm running the default kits, but I also tried updating to 1.2 where possible, but that didn't seem to make any difference.

Hi cafaia, File received, I see it is compressed with gzip. I see that scandelay actually supports no args, it waits 3 seconds by default (when passed as an argument with no parameters) I didn't see anything that stood out, can you try editing /usr/share/genkernel/defaults/linuxrc and adding echo statements throughout to see where it might be occurring, followed by rebuilding the initramfs (and booting up with the modified init)? Then, we can narrow down exactly. Don't forget to backup your original ... Also, share the updated initramfs just so I can see it was updated as expected.

Hi cafaia, If you don't mind, can you post your initramfs? That is the only way I see to troubleshoot this. The other alternative is to look at the source files in /usr/share/genkernel to try and backtrack what is going on there. BTW, I checked my linuxrc (/usr/share/genkernel/defaults/linuxrc), and I don't see an ro option, is that a kernel command-line option? Just for giggles, can you remove that argument?

I masked gentoo-sources > 4.15.0 and rebuilt everything since apparently 4.17 is not ready yet and the newer ZFS ebuilds are not yet available.