Jump to content
funtoo forums

hellomynameisphil

Members
  • Content Count

    10
  • Joined

  • Last visited

1 Follower

About hellomynameisphil

  • Rank
    Member
  1. I switched to ntp from chrony and now my time is correct. Thanks!
  2. Figured it out. I generally have /boot on a separate partition. This partition seems to get unmounted automatically after booting is complete. So when I was compiling 4.0.1 and installing the linux kernel binary, it was to a directory called boot in my root file system which is inaccessible when the boot partition is mounted on /boot. I am typing this from 4.0.1. Thanks to all who made suggestions.
  3. Yes, chrony. How do I check if it writes to CMOS at halt?
  4. ~ % ls -l /etc/localtime lrwxrwxrwx 1 root root 37 May 3 11:36 /etc/localtime -> /usr/share/zoneinfo/America/Vancouver My computer clock currently says 11:51 AM. According to every other clock, it's more like 10:51. Daylight Savings started a few months ago already, so it's not that. I first noticed the issue this morning.
  5. Thanks, but that doesnt work either. As per man boot.conf, I should be able to specify which specific kernels I wants to use, all one line. Doing it your way, I only get: Funtoo Linux - vmlinuz-3.19.0 Funtoo Linux - vmlinuz-3.19.0.old Windows 7 which is the reason I specified particular kernels; I don't want those crufty *.olds to show up in my boot menu.
  6. I recently upgraded vanilla-sources to 4.0.1. I used eselect to select this kernel and went to /usr/src/linux (symlinked to linux-4.0.1) and built the kernel as per http://www.funtoo.org/Building_a_Kernel_from_Source (using the 'less advanced' instructions). This appears to have been successful. Here is /boot: phuntoo ~ # ls /boot/ config-3.19.0 config-4.0.1 config-4.0.1.old initramfs.cpio.gz System.map-3.19.0 System.map-4.0.1 System.map-4.0.1.old vmlinuz-3.19.0 vmlinuz-4.0.1 vmlinuz-4.0.1.old Here is my boot.conf: boot { generate grub # Below, you can specify the kernel image to boot by default, # or the default boot entry name default Funtoo Linux # default Windows 7 } display { gfxmode "1366x768" } "Funtoo Linux" { kernel vmlinuz-4.0.1 vmlinuz-3.19.0 initrd /initrams.cpio.gz params += resume=/dev/sda6 } "Windows 7" { type win7 params root=/dev/sda3 } Here is the output of boot-update: phuntoo ~ # boot-update boot-update 1.7.2 / Copyright 2009-2015 Funtoo Technologies [use option "-l" for license info, "-h" for help] * Generating config for grub... DEFAULT > Funtoo Linux - vmlinuz-3.19.0 Windows 7 * NOTE : Detected MBR boot. Configuring for Legacy MBR booting. * Completed successfully. Why is boot-update not seeing 4.0.1?
  7. This is still not working. Can anyone help?
  8. # USE="-introspection" emerge -1 libappindicator [snip] ="/bin/sh ../libtool" --include=GObject-2.0 --include=Gtk-3.0 --library=libappindicator3.la --cflags-begin -I/usr/include/libindicator3-0.4 -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I. -I../src --cflags-end app-indicator.c app-indicator.h libappindicator3.la --output AppIndicator3-0.1.gir Couldn't find include 'Gtk-3.0.gir' (search path: ['.', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0']) make[2]: *** [AppIndicator3-0.1.gir] Error 1 make[2]: Leaving directory `/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0' make: *** [all] Error 2 * ERROR: dev-libs/libappindicator-12.10.0 failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=dev-libs/libappindicator-12.10.0'`, * the complete build log and the output of `emerge -pqv '=dev-libs/libappindicator-12.10.0'`. * The complete build log is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0' * S: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0' >>> Failed to emerge dev-libs/libappindicator-12.10.0, Log file: >>> '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/build.log' * Messages for package dev-libs/libappindicator-12.10.0: * ERROR: dev-libs/libappindicator-12.10.0 failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=dev-libs/libappindicator-12.10.0'`, * the complete build log and the output of `emerge -pqv '=dev-libs/libappindicator-12.10.0'`. * The complete build log is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0' * S: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0'
  9. emerge info: http://www.pastebin.ca/2962403 emerge -pqv: [ebuild N ] dev-libs/libappindicator-12.10.0 USE="-introspection" build log: http://pastebin.ca/2962405 environment: http://pastebin.ca/2962407
  10. I've been having trouble with this for a few days. Previously it complained about a file not being found, but now I get this. >>> Emerging (2 of 2) kde-plasma/oxygen-fonts-5.2.0 !!! Fetched file: oxygen-fonts-5.2.0.tar.xz VERIFY FAILED! !!! Reason: Insufficient data for checksum verification !!! Got: !!! Expected: MD5 RMD160 SHA1 SHA256 SHA512 WHIRLPOOL * Fetch failed for 'kde-plasma/oxygen-fonts-5.2.0', Log file: * '/var/tmp/portage/kde-plasma/oxygen-fonts-5.2.0/temp/build.log' >>> Failed to emerge kde-plasma/oxygen-fonts-5.2.0, Log file: >>> '/var/tmp/portage/kde-plasma/oxygen-fonts-5.2.0/temp/build.log' * Messages for package kde-plasma/oxygen-fonts-5.2.0: * Fetch failed for 'kde-plasma/oxygen-fonts-5.2.0', Log file: * '/var/tmp/portage/kde-plasma/oxygen-fonts-5.2.0/temp/build.log'
×
×
  • Create New...