mauricev

I'm building a machine fresh and I am at the point of running emerge for the first time and I'm seeing this error !!! Unable to parse profile: '/etc/portage/make.profile' !!! ParseError: Parent 'llvm-kit:funtoo/kits/python-kit/3.4-prime' not found: '/etc/portage/make.profile/parent' emerge info reveals Portage 2.3.8 (python 2.7.13-final-0, funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-5.4.0, glibc-2.23-r4, 4.4.28-std490-amd64 x86_64) ================================================================= System uname: Linux-4.4.28-std490-amd64-x86_64-Intel-R-_Xeon-R-_CPU_E5-1650_v2_@_3.50GHz-with-gentoo-2.2.1 KiB Mem: 3080320 total, 448420 free KiB Swap: 0 total, 0 free sh bash 4.4_p12-r1 ld GNU ld (Gentoo 2.28 p1.2) 2.28 app-shells/bash: 4.4_p12-r1::core-kit dev-lang/perl: 5.24.0-r2::gentoo dev-lang/python: 2.7.13::gentoo, 3.4.6::gentoo sys-apps/baselayout: 2.2.1::gentoo sys-apps/openrc: 0.23.2-r1::core-kit sys-apps/sandbox: 2.10-r4::core-kit sys-devel/autoconf: 2.69-r2::gentoo sys-devel/automake: 1.15-r2::gentoo sys-devel/binutils: 2.28-r4::core-kit sys-devel/gcc: 5.4.0::core-kit sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r4::core-kit sys-devel/make: 4.1-r1::gentoo sys-kernel/linux-headers: 4.9::gentoo (virtual/os-headers) sys-libs/glibc: 2.23-r4::gentoo Repositories: nokit location: /var/git/meta-repo/kits/nokit masters: core-kit priority: -500 core-hw-kit location: /var/git/meta-repo/kits/core-hw-kit masters: core-kit priority: 1 core-kit location: /var/git/meta-repo/kits/core-kit masters: core-kit priority: 1 aliases: gentoo desktop-kit location: /var/git/meta-repo/kits/desktop-kit masters: core-kit priority: 1 dev-kit location: /var/git/meta-repo/kits/dev-kit masters: core-kit priority: 1 editors-kit location: /var/git/meta-repo/kits/editors-kit masters: core-kit priority: 1 games-kit location: /var/git/meta-repo/kits/games-kit masters: core-kit priority: 1 haskell-kit location: /var/git/meta-repo/kits/haskell-kit masters: core-kit priority: 1 java-kit location: /var/git/meta-repo/kits/java-kit masters: core-kit priority: 1 kde-kit location: /var/git/meta-repo/kits/kde-kit masters: core-kit priority: 1 lang-kit location: /var/git/meta-repo/kits/lang-kit masters: core-kit priority: 1 lisp-scheme-kit location: /var/git/meta-repo/kits/lisp-scheme-kit masters: core-kit priority: 1 media-kit location: /var/git/meta-repo/kits/media-kit masters: core-kit priority: 1 ml-lang-kit location: /var/git/meta-repo/kits/ml-lang-kit masters: core-kit priority: 1 net-kit location: /var/git/meta-repo/kits/net-kit masters: core-kit priority: 1 perl-kit location: /var/git/meta-repo/kits/perl-kit masters: core-kit priority: 1 php-kit location: /var/git/meta-repo/kits/php-kit masters: core-kit priority: 1 python-kit location: /var/git/meta-repo/kits/python-kit masters: core-kit priority: 1 ruby-kit location: /var/git/meta-repo/kits/ruby-kit masters: core-kit priority: 1 security-kit location: /var/git/meta-repo/kits/security-kit masters: core-kit priority: 1 text-kit location: /var/git/meta-repo/kits/text-kit masters: core-kit priority: 1 xfce-kit location: /var/git/meta-repo/kits/xfce-kit masters: core-kit priority: 1 xorg-kit location: /var/git/meta-repo/kits/xorg-kit masters: core-kit priority: 1 gnome-kit location: /var/git/meta-repo/kits/gnome-kit masters: core-kit priority: 10 science-kit location: /var/git/meta-repo/kits/science-kit masters: core-kit priority: 10 ACCEPT_LICENSE="* -@EULA" CFLAGS="" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d" CXXFLAGS="" DISTDIR="/var/cache/portage/distfiles" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="" GENTOO_MIRRORS="http://distfiles.gentoo.org" LDFLAGS="" PKGDIR="/var/cache/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_TMPDIR="/var/tmp" USE="" Unset: ACCEPT_KEYWORDS, CBUILD, CHOST, CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, MAKEOPTS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS

I configured funtoo for kde-plasma-5. It has both use flags qt4 and qt5. When emerging with newuse , pinentry complains of the following: !!! The ebuild selected to satisfy "app-crypt/pinentry" has unmet requirements. - app-crypt/pinentry-1.0.0::core-kit USE="ncurses qt4 qt5 -caps -emacs -gnome-keyring -gtk -static" The following REQUIRED_USE flag constraints are unsatisfied: at-most-one-of ( qt4 qt5 ) The above constraints are a subset of the following complete expression: any-of ( ncurses gtk qt4 qt5 ) gtk? ( !static ) qt4? ( !static ) qt5? ( !static ) static? ( ncurses ) at-most-one-of ( qt4 qt5 ) New info: it seems that qt4 wasn't provided by the mix-in, but apparently I had to add it manually otherwise a bunch of things related to KDE wouldn't emerge. qt5 is apparently builtin to the mixin and without it, poppler won't emerge.

Wow, all those messages to come here. Thanks for everyone's efforts. Does grub require anything to be read from /dev/sda1 when it's installed? If it does and that stuff isn't present because /dev/sda1 is not mounted, then it should report an error. All this time, I was getting warnings about LVM, but there was never any error reported.

This is now in bugs, https://bugs.funtoo.org/browse/FL-4767

Yes, it boots the machine! So whatever makes grub work automatically gets blocked somehow by not having /dev/sda1 mounted at install time.

No, it's not blank. I just changed the name of the kernel to "kernel", so I wouldn't have to worry about mistyping it manually in the grub command line.

It does? grub.conf was indeed a typo.

With /dev/sda1 mounted or not, I get the same output from boot-update Copyright 2009-2017 Funtoo Technologies [use option "-l" for license info, "-h" for help] * Generating config for grub... DEFAULT > Funtoo Linux genkernel - kernel * NOTE: Detected MBR boot. Configuring for Legacy MBR booting. * WARN: Intel system detected - please emerge sys-firmware/intel-microcode and sys-apps/iucode-tool and run boot-update again; boot-update will then patch your system with the latest Intel CPU and chipset microcode patches at boot-time, protecting you against important vulnerabilities and errata. * Completed successfully with warnings. When /dev/sda1 is not mounted, boot-update enters this in the system log Feb 04 00:32:16 [kernel] [ 231.913202] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem Feb 04 00:32:16 [kernel] [ 231.928341] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) Grub is at 2.02_beta3-r2. boot-update is 1.8.2. At the failed grub prompt, configfile grub/grub.conf results in no output. It just gives me another blank prompt. It's not that it can't find the kernel; it can't find grub.conf

It does find the kernel if I enter the info manually at the grub prompt. But what does that tell us? If it's not finding it automatically, it's effectively the same as not finding it unless you consider it normal for users to have to manually enter the kernel information at every startup. Running boot-update with /dev/sda1 not mounted has no effect on grub failing. It still fails.

I confirmed the original issue is a bug. When "intel" is supplied to VIDEO_CARDS for X11, it inappropriately installs an unnecessary file, 20-intel.conf in xorg.conf.d. The presence of this file overrides the normal device detection in X11 and forces it to think the video card is intel. If there is not an actual Intel video card, X11 will throw up its hands and fail.

ls -alF /boot shows nothing when /dev/sda1 is not mounted. grub.cfg and the kernels reside on /dev/sda1, not in the empty /boot directory. When /dev/sda1 is not mounted and grub is installed, it spews bogus errors about lvm but no other errors. However, the machine loses the ability to boot because it now can’t find the kernel. bcowan seems to be claiming this behavior is impossible. But you’re claiming that it’s normal? That /dev/sda1 must be mounted when grub is installed or am I misunderstanding? Please disregard my mention of any custom script. I'm talking exclusively about installing grub.

I just tested it again and when /boot is not mounted, grub installation throws a fit and makes the computer non-bootable.

I have made some progress. consolekit in /etc/init.d has to be started. It's no longer crashing.

I tried to setup a Funtoo installation with cinnamon. I changed to the desktop flavor and added it as a mixin. It didn't complain, but emerge didn't find anything more to emerge. So I manually emerged cinnamon. When I started X, I got a basic X and not cinnamon. So I changed .xinitrc to the following exec ck-launch-session dbus-launch cinnamon-session When I ran startx again, it started to run and then promptly crashed. The logged output is Feb 02 12:33:52 [ck-launch-session] error connecting to ConsoleKit Feb 02 12:33:52 [cinnamon-session] WARNING: t+0.00378s: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory_ Feb 02 12:33:53 [kernel] [ 32.643783] csd-xrandr[24011]: segfault at 0 ip 00007fc98568a9d9 sp 00007fff44441e50 error 4 in libupower-glib.so.3.0.1[7fc985678000+26000] Feb 02 12:33:53 [kernel] [ 32.645367] csd-power[24010]: segfault at 0 ip 00007f812bfcd9d9 sp 00007ffdce11c8d0 error 4 in libupower-glib.so.3.0.1[7f812bfbb000+26000] Feb 02 12:33:53 [cinnamon-session] WARNING: t+0.47240s: Application 'cinnamon-settings-daemon-xrandr.desktop' killed by signal 11_ Feb 02 12:33:53 [cinnamon-session] WARNING: t+0.95457s: Application 'cinnamon-settings-daemon-power.desktop' killed by signal 11_ Feb 02 12:33:54 [kernel] [ 33.875096] csd-xrandr[24115]: segfault at 0 ip 00007fece8eb69d9 sp 00007ffcb40b5a50 error 4 in libupower-glib.so.3.0.1[7fece8ea4000+26000] Feb 02 12:33:54 [cinnamon-session] WARNING: t+1.70045s: Application 'cinnamon-settings-daemon-xrandr.desktop' killed by signal 11_ Feb 02 12:33:54 [kernel] [ 33.891378] csd-power[24116]: segfault at 0 ip 00007f154f4b59d9 sp 00007ffcb77fc6e0 error 4 in libupower-glib.so.3.0.1[7f154f4a3000+26000] Feb 02 12:33:54 [cinnamon-session] WARNING: t+1.71240s: Application 'cinnamon-settings-daemon-power.desktop' killed by signal 11_ Feb 02 12:34:00 [cinnamon-session] WARNING: t+7.43181s: Detected that screensaver has left the bus_

I don't know where that fstab came from, but somehow that fixed the other fstab and now it started mounting /boot. Very weird indeed.