Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Past hour
  2. Funtoo on a laptop best practices

    Thank you both. I will bare this in mind my install.
  3. Today
  4. I have a funtoo server that does all the package builds, and my other servers and desktops specify 'getbinpkg' in order to use the packages created by the primary server. This mostly works, but I often get messages like "The following binary packages have been ignored due to changed dependencies". Here is an example. On my laptop, when emerging @world, I get the following message and nothing gets emerged (all other packages have been brought up to date): !!! The following binary packages have been ignored due to changed dependencies: dev-lang/vala-0.28.1::gentoo NOTE: The --binpkg-changed-deps=n option will prevent emerge from ignoring these binary packages if possible. Using --binpkg-changed-deps=y will silence this warning. Neither of the suggested --bin-pkg-changed-deps options change the message in any way. Even stranger, this version of vala is not installed on the laptop (nor on the primary server). # ego query versions vala dev-lang/vala| slot| repo --------------+-----+--------------------- 0.26.2| 0.26| gnome-kit/3.20-prime --------------+-----+--------------------- 0.28.1| 0.28| gnome-kit/3.20-prime --------------+-----+--------------------- * 0.30.1| 0.30| gnome-kit/3.20-prime --------------+-----+--------------------- 0.32.1| 0.32| gnome-kit/3.20-prime In other cases, I get this message when I do have the specified version installed. For instance, on my desktop when emerging @world, I get the following message and nothing gets emerged. !!! The following binary packages have been ignored due to changed dependencies: media-sound/guayadeque-0.4.5_p20170110::gentoo dev-util/itstool-2.0.2::gentoo But these package versions are installed on both the desktop and the server: # ego query versions guayadeque media-sound/guayadeque| slot| repo -----------------------+-----+-------------------- * 0.4.5_p20170110| 0| media-kit/1.1-prime # ego query versions itstool dev-util/itstool| slot| repo -----------------+-----+------------------- * 2.0.2| 0| core-kit/1.0-prime In yet another case, I get this message and emerge wants to do an ebuild even though the binpkg is available. For instance, on desktop #2 when emerging @world: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS ] sys-kernel/debian-sources-4.14.12 [4.14.2] USE="binary" !!! The following binary packages have been ignored due to changed dependencies: sys-kernel/debian-sources-4.14.12::core-kit NOTE: The --binpkg-changed-deps=n option will prevent emerge from ignoring these binary packages if possible. Using --binpkg-changed-deps=y will silence this warning. However, I can run 'emerge -av debian-sources' on that same system and it will install the binary package: These are the packages that would be merged, in order: Calculating dependencies... done! [binary NS ] sys-kernel/debian-sources-4.14.12:4.14.12::core-kit [4.14.2:4.14.2::core-kit] USE="binary" 190,850 KiB Total: 1 package (1 in new slot, 1 binary), Size of downloads: 190,850 KiB Would you like to merge these packages? [Yes/No] All of these machines have the same USE options (make.conf, package.use, epro). I'm constantly fighting this battle to get the machines to use all the binaries built by the server. Can anybody shed some light on this? Am I doing something wrong? Is it a bug?
  5. X suddenly not working

    paste following output from both working and then non-working box: ls -dl /var/db/pkg/*/*/*
  6. Funtoo on a laptop best practices

    That part could probably be done best by a small script: - suspend hibernation event - emerge what you want or need - resume hibernation event Not sure if this would work though, as I don't use hibernation on my laptop.
  7. X suddenly not working

    This is odd, but for the previously working other machine going back in time, I had to really go back before I could find a snapshot where X would work. Here are the differences: Working epro show has mix-in set to xfce whereas failing one has nothing for the mix-in. Working epro doesn't have an X-kit whereas the failing one has xorg-kit = 1.19-prime. Make.conf seems to be the same, indicating VIDEO_CARDS="intel vmware" (this machine runs under VMWare.) Failing x log Xorg log [ 15128.083] X.Org X Server 1.19.3 Release Date: 2017-03-15 [ 15128.083] X Protocol Version 11, Revision 0 [ 15128.083] Build Operating System: Linux 4.8.15-1 i686 Gentoo [ 15128.084] Current Operating System: Linux vm 4.8.15-1 #2 SMP Thu May 11 11:08:16 Local time zone must be set--see zic i686 [ 15128.084] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86-4.8.15-1 root=/dev/sda3 rootfstype=ext4 [ 15128.084] Build Date: 19 January 2018 04:08:31AM [ 15128.084] [ 15128.084] Current version of pixman: 0.34.0 [ 15128.084] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 15128.084] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 15128.085] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 19 16:39:03 2018 [ 15128.085] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 15128.085] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 15128.086] (==) No Layout section. Using the first Screen section. [ 15128.086] (==) No screen section available. Using defaults. [ 15128.086] (**) |-->Screen "Default Screen Section" (0) [ 15128.086] (**) | |-->Monitor "<default monitor>" [ 15128.086] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 15128.086] (**) | |-->Device "Intel Graphics" [ 15128.086] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 15128.086] (==) Automatically adding devices [ 15128.086] (==) Automatically enabling devices [ 15128.086] (==) Automatically adding GPU devices [ 15128.086] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 15128.086] (WW) The directory "/usr/share/fonts/TTF/" does not exist. [ 15128.086] Entry deleted from font path. [ 15128.086] (WW) The directory "/usr/share/fonts/OTF/" does not exist. [ 15128.086] Entry deleted from font path. [ 15128.086] (WW) The directory "/usr/share/fonts/Type1/" does not exist. [ 15128.086] Entry deleted from font path. [ 15128.086] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/". [ 15128.086] Entry deleted from font path. [ 15128.086] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/"). [ 15128.086] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/". [ 15128.086] Entry deleted from font path. [ 15128.086] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/"). [ 15128.086] (==) FontPath set to: /usr/share/fonts/misc/ [ 15128.086] (==) ModulePath set to "/usr/lib/xorg/modules" [ 15128.086] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 15128.086] (II) Loader magic: 0x8291640 [ 15128.086] (II) Module ABI versions: [ 15128.086] X.Org ANSI C Emulation: 0.4 [ 15128.086] X.Org Video Driver: 23.0 [ 15128.086] X.Org XInput driver : 24.1 [ 15128.086] X.Org Server Extension : 10.0 [ 15128.086] (II) xfree86: Adding drm device (/dev/dri/card0) [ 15128.112] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0x????????/131072 [ 15128.112] (II) LoadModule: "glx" [ 15128.112] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 15128.115] (II) Module glx: vendor="X.Org Foundation" [ 15128.115] compiled for 1.19.3, module version = 1.0.0 [ 15128.115] ABI class: X.Org Server Extension, version 10.0 [ 15128.115] (II) LoadModule: "intel" [ 15128.115] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 15128.115] (II) Module intel: vendor="X.Org Foundation" [ 15128.115] compiled for 1.19.3, module version = 2.99.917 [ 15128.115] Module class: X.Org Video Driver [ 15128.115] ABI class: X.Org Video Driver, version 23.0 [ 15128.115] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 15128.115] (II) intel: Driver for Intel(R) HD Graphics [ 15128.115] (II) intel: Driver for Intel(R) Iris(TM) Graphics [ 15128.115] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics [ 15128.115] (--) using VT number 7 [ 15128.118] (EE) No devices detected. [ 15128.118] (EE) Fatal server error: [ 15128.118] (EE) no screens found(EE) [ 15128.118] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 15128.118] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 15128.118] (EE) [ 15128.120] (EE) Server terminated with error (1). Closing log file. Working x log [ 20.392] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 20.392] X Protocol Version 11, Revision 0 [ 20.392] Build Operating System: Linux 3.19.3-1~exp1 i686 Gentoo [ 20.392] Current Operating System: Linux vm 4.8.15-1 #2 SMP Thu May 11 11:08:16 Local time zone must be set--see zic i686 [ 20.392] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86-4.8.15-1 root=/dev/sda3 rootfstype=ext4 [ 20.392] Build Date: 11 May 2017 05:42:50AM [ 20.392] [ 20.393] Current version of pixman: 0.34.0 [ 20.393] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 20.393] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 20.394] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 20 02:03:24 2018 [ 20.404] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 20.404] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 20.406] (==) No Layout section. Using the first Screen section. [ 20.407] (==) No screen section available. Using defaults. [ 20.407] (**) |-->Screen "Default Screen Section" (0) [ 20.407] (**) | |-->Monitor "<default monitor>" [ 20.407] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 20.407] (==) Automatically adding devices [ 20.407] (==) Automatically enabling devices [ 20.407] (==) Automatically adding GPU devices [ 20.407] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 20.415] (WW) The directory "/usr/share/fonts/TTF/" does not exist. [ 20.415] Entry deleted from font path. [ 20.415] (WW) The directory "/usr/share/fonts/OTF/" does not exist. [ 20.415] Entry deleted from font path. [ 20.415] (WW) The directory "/usr/share/fonts/Type1/" does not exist. [ 20.415] Entry deleted from font path. [ 20.415] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/". [ 20.415] Entry deleted from font path. [ 20.415] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/"). [ 20.416] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/". [ 20.416] Entry deleted from font path. [ 20.416] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/"). [ 20.416] (==) FontPath set to: /usr/share/fonts/misc/ [ 20.416] (==) ModulePath set to "/usr/lib/xorg/modules" [ 20.416] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 20.416] (II) Loader magic: 0x82904e0 [ 20.416] (II) Module ABI versions: [ 20.416] X.Org ANSI C Emulation: 0.4 [ 20.416] X.Org Video Driver: 20.0 [ 20.416] X.Org XInput driver : 22.1 [ 20.416] X.Org Server Extension : 9.0 [ 20.417] (II) xfree86: Adding drm device (/dev/dri/card0) [ 20.442] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0 x????????/131072 [ 20.442] (II) LoadModule: "glx" [ 20.461] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 20.500] (II) Module glx: vendor="X.Org Foundation" [ 20.500] compiled for 1.18.4, module version = 1.0.0 [ 20.500] ABI class: X.Org Server Extension, version 9.0 [ 20.500] (==) AIGLX enabled [ 20.500] (==) Matched vmware as autoconfigured driver 0 [ 20.500] (==) Matched vmware as autoconfigured driver 1 [ 20.500] (==) Matched modesetting as autoconfigured driver 2 [ 20.500] (==) Matched fbdev as autoconfigured driver 3 [ 20.500] (==) Matched vesa as autoconfigured driver 4 [ 20.500] (==) Assigned the driver to the xf86ConfigLayout [ 20.500] (II) LoadModule: "vmware" [ 20.500] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so [ 20.729] (II) Module vmware: vendor="X.Org Foundation" [ 20.729] compiled for 1.18.4, module version = 13.1.0 [ 20.729] Module class: X.Org Video Driver [ 20.729] ABI class: X.Org Video Driver, version 20.0 [ 20.729] (II) LoadModule: "modesetting" [ 20.729] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 20.730] (II) Module modesetting: vendor="X.Org Foundation" [ 20.730] compiled for 1.18.4, module version = 1.18.4 [ 20.730] Module class: X.Org Video Driver [ 20.730] ABI class: X.Org Video Driver, version 20.0 [ 20.730] (II) LoadModule: "fbdev" [ 20.731] (WW) Warning, couldn't open module fbdev [ 20.731] (II) UnloadModule: "fbdev" [ 20.731] (II) Unloading fbdev [ 20.731] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 20.731] (II) LoadModule: "vesa" [ 20.731] (WW) Warning, couldn't open module vesa [ 20.731] (II) UnloadModule: "vesa" [ 20.731] (II) Unloading vesa [ 20.731] (EE) Failed to load module "vesa" (module does not exist, 0) [ 20.731] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710 [ 20.731] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 20.731] (--) using VT number 7 [ 20.734] (WW) Falling back to old probe method for modesetting [ 20.735] (II) vmware(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 20.735] (--) vmware(0): DRM driver version is 2.10.0 [ 20.735] (==) vmware(0): Depth 24, (--) framebuffer bpp 32 [ 20.735] (==) vmware(0): RGB weight 888 [ 20.735] (==) vmware(0): Default visual is TrueColor [ 20.735] (--) vmware(0): Min width 1, Max Width 4096. [ 20.735] (--) vmware(0): Min height 1, Max Height 4096. [ 20.736] (II) vmware(0): Output Virtual1 has no monitor section [ 20.736] (II) vmware(0): Output Virtual2 has no monitor section [ 20.736] (II) vmware(0): Output Virtual3 has no monitor section [ 20.736] (II) vmware(0): Output Virtual4 has no monitor section [ 20.736] (II) vmware(0): Output Virtual5 has no monitor section [ 20.736] (II) vmware(0): Output Virtual6 has no monitor section [ 20.736] (II) vmware(0): Output Virtual7 has no monitor section [ 20.737] (II) vmware(0): Output Virtual8 has no monitor section [ 20.737] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
  8. X suddenly not working

    to understand problem, it's required to get the following: 1. the state of working box 2. the state of non-working box To me it looks that update of some ebuilds, such virtualbox or virtualbox-related ebuilds happened in case 2. Also, it could be kernel update.
  9. Local overlay woes

    Got it. I guess I was expecting some command to do this. It seems strange as I've been using gentoo/funtoo for so long, but I must have never downloaded an ebuild that needed a patch before. Thanks.
  10. OS freezes suddenly

    # free -m total used free shared buff/cache available Mem: 3834 1925 892 89 1016 1593 Swap: 2047 0 2047 The problem repeats when I draw in Gimp or use openshot
  11. About eselect python

    yes, this is known bug. i reported it to usptream https://bugs.gentoo.org/635678
  12. X suddenly not working

    I had a system with X running fine, rebuilt world and now it's no longer working. So I added X to another system, which didn't have it, and on it, too, X won't launch. Both systems are running in VirtualBox. make.conf GRUB_PLATFORMS="pc" VIDEO_CARDS="intel vmware virtualbox" ego.conf # This is the ego.conf file [kits] # You can set your default kits here. Unset kits will use the Funtoo default prime/master # branch by default. # python-kit = 3.6-prime xorg-kit = 1.19-prime epro show === Enabled Profiles: === arch: x86-64bit build: current subarch: generic_64 flavor: desktop mix-ins: (not set) Here is X.org log matlab log # more Xorg.0.log [ 26654.527] X.Org X Server 1.19.3 Release Date: 2017-03-15 [ 26654.530] X Protocol Version 11, Revision 0 [ 26654.531] Build Operating System: Linux 4.8.15-1 x86_64 Gentoo [ 26654.532] Current Operating System: Linux matlab 4.8.15-1 #1 SMP Tue Dec 27 11:23:57 -00 2016 x86_64 [ 26654.533] Kernel command line: BOOT_IMAGE=/kernel-debian-sources-x86_64-4.8.15-1 dolvm rootfstype=ext4 resume=swap:/dev/mapper/funtoo-swap quiet real_root=/d ev/funtoo/root rootfstype=ext4 [ 26654.535] Build Date: 10 January 2018 10:56:50PM [ 26654.536] [ 26654.537] Current version of pixman: 0.34.0 [ 26654.540] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 26654.540] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 26654.548] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 11 02:47:49 2018 [ 26654.549] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 26654.550] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 26654.550] (==) No Layout section. Using the first Screen section. [ 26654.550] (==) No screen section available. Using defaults. [ 26654.550] (**) |-->Screen "Default Screen Section" (0) [ 26654.550] (**) | |-->Monitor "<default monitor>" [ 26654.550] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 26654.550] (**) | |-->Device "Intel Graphics" [ 26654.550] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 26654.550] (==) Automatically adding devices [ 26654.550] (==) Automatically enabling devices [ 26654.550] (==) Automatically adding GPU devices [ 26654.550] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 26654.550] (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ [ 26654.550] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 26654.550] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 26654.550] (II) Loader magic: 0x808c80 [ 26654.550] (II) Module ABI versions: [ 26654.550] X.Org ANSI C Emulation: 0.4 [ 26654.550] X.Org Video Driver: 23.0 [ 26654.550] X.Org XInput driver : 24.1 [ 26654.550] X.Org Server Extension : 10.0 [ 26654.556] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216, BIOS @ 0x????????/131072 [ 26654.556] (II) LoadModule: "glx" [ 26654.556] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 26654.557] (II) Module glx: vendor="X.Org Foundation" [ 26654.558] compiled for 1.19.3, module version = 1.0.0 [ 26654.558] ABI class: X.Org Server Extension, version 10.0 [ 26654.558] (II) LoadModule: "intel" [ 26654.558] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 26654.558] (II) Module intel: vendor="X.Org Foundation" [ 26654.558] compiled for 1.19.3, module version = 2.99.917 [ 26654.558] Module class: X.Org Video Driver [ 26654.558] ABI class: X.Org Video Driver, version 23.0 [ 26654.558] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 26654.558] (II) intel: Driver for Intel(R) HD Graphics [ 26654.558] (II) intel: Driver for Intel(R) Iris(TM) Graphics [ 26654.558] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics [ 26654.558] (--) using VT number 7 [ 26654.579] (EE) No devices detected. [ 26654.579] (EE) Fatal server error: [ 26654.579] (EE) no screens found(EE) [ 26654.579] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 26654.579] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 26654.579] (EE) [ 26654.596] (EE) Server terminated with error (1). Closing log file.
  13. About eselect python

    I tried to use the "python-kit = 3.6-prime" that compiled me the last version of python 3.6. Since it's not for my time, i'm returned to the "default" kit and I've removed python 3.6.X. But if I use eselect I still get the presence of python 3.6 also if i removed it and returned to precedent kit version. > sandro@ci74771ht ~ $ eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 [3] python3.5 [4] python3.6 Is this a little bug ? There is the possibility to remove python3_6 from the list ? Thanx for any suggestion.
  14. Funtoo on a laptop best practices

    I can share my experience with using funtoo on a laptop. I use gnome (3.20) and I am not using hibernation as I went the way of no swap partition on ssd. (8GB RAM) I can suspend to ram without problems, the lid events just-work (opening the lid with suspended laptop resumes). Gnome shows these settings under Power management: Not using systemd. Follow the Install guide. After that epro flavor desktop epro mix-ins gnome (optional epro mix-ins no-systemd) :) emerge -av gnome (or gnome-light) I don't know how to solve the "emerge / close-lid /wait for emerge to complete / hibernate" part of your question.
  15. Yesterday
  16. Funtoo on a laptop best practices

    Hi Palica, I have researched power management in Linux laptops for most the answer seems to be systemd with all its wonderful features. I have tried masking OpenRC and predicating everything off systemd but that has left me knots too. In Funtoo, I don’t see systemd being an option. There is sys-power/upower etc. which offer some features. https://wiki.gentoo.org/wiki/Suspend_and_hibernate I have read this page: https://www.funtoo.org/Power_Management What I’m looking for is an insight into lid closed events and as the above link describes low battery events. Laptops aren’t new and when I first scrapped these sources together and made a mess of it, I thought someone else might be able to share lessons learn or point to a useful blog post. As for WiFi, reading on this topic has suggested that it’s not to be taken lightly either. As that may be the case preparation is key. So, I’m not asking about systemd despite how many times I mention systemd. I imagine there are ways of solving this in Funtoo. Though another has already suggested Ubuntu to me (that uses systemd to this effect [other binary distros are available offering the same effect]). Thus as yet my research hasn’t yelded anything really laptop like in Funtoo. I haven’t tried with Gentoo, there my expectations wouldn’t be so very different. So to make this a clear question. From the point of inflating the tar in the installation process. How do you build a Funtoo laptop which functions with power management like any other modern laptop? Maybe I’m asking the wrong question. What am I missing? How should I be thinking about this problem? Thanks.
  17. Funtoo on a laptop best practices

    For what? Power management, installation on laptop, using hibernation, configuring WiFi ...? Sorry Stephen you will have to rephrase your question a bit.
  18. Funtoo on a laptop best practices

    I have a laptop workstation which I want to put Funtoo on. I am back at the planning stage (after not getting very far without planning). The SSD is partitioned as I want to enable hibernation. However, power management (and WiFi network discovery, although I haven’t got that far yet) appear to be the big issues. One thing I’d like if possible and circumstances allow, would be to kick off emerge, then close lid and after emerge finishes regular closed lid power management takes over :) as that would be nice. Please advise me on best practices? I am even willing to try systemd (please don’t get hung up on the mention of systemd, it’s just a tool that does a... many jobs). Btw, I have deliberately left out my mistakes to avoid confusion. — Stephen.
  19. TTY (console) colour changed after OpenRC start

    Hi! Its very difficult to follow the entire thread. To understand the patterns of a problem a following information could help: 1. using same kernel but different OpenRC versions will reproduce the bug. 2. using same OpenRC version but different kernel will reproduce the bug
  20. TTY (console) colour changed after OpenRC start

    ...and now were going off topic. This problem is not getting resolved but devolving into something else. ....thread abandoned.
  21. TTY (console) colour changed after OpenRC start

    Ok, I'll have a try (although I do all that stuff manually). The instrucions of @palica are good. You just need to have two kernels installed. A working one and another one you make the changes to. The missing part is the new entry in grub.cfg, which you add before the reboot (maybe genkernel already does that). Here is an example of my grub.cfg (don't mind the gentoo part, as I use gentoo-sources): menuentry "Funtoo Linux test" { insmod part_gpt insmod ext2 set root=(hostdisk//dev/sda,gpt5) search --no-floppy --fs-uuid --set c6e932b1-0a2d-4fc7-b1a6-19539207fce6 linux /boot/vmlinuz-4.14.14-gentoo root=/dev/sda5 raid=noautodetect } menuentry "Funtoo Linux - working" { insmod part_gpt insmod ext2 set root=(hostdisk//dev/sda,gpt5) search --no-floppy --fs-uuid --set c6e932b1-0a2d-4fc7-b1a6-19539207fce6 linux /boot/vmlinuz-4.14.13-gentoo root=/dev/sda5 raid=noautodetect } Basically you just duplicate the menu entry of your working kernel and change the kernel version to the one you want to test. With this you can boot the "test kernel" and if this does not work you reboot into the "working kernel". This way you always have a working kernel at hand if any new kernel does not work on your system. Hope that clarifies my suggestion. Feel free to ask again, if it is still not clear enough.
  22. TTY (console) colour changed after OpenRC start

    Please correlate this statement to the instructions I was given from palica above. Then detail how you would peel back the non-working kernel, please.
  23. TTY (console) colour changed after OpenRC start

    When trying out new kernels it is always a good idea to leave the current and working kernel on the system as well, in case the new kernel does not work. For that I have two entries in the grub config. One for the new and one for the old. If the new one does not work I can simply reboot and boot the old kernel. No need for a rescue cd then.
  24. TTY (console) colour changed after OpenRC start

    @palica - I'm trying not to confuse the descriptions here. The desktop box(w/ Artix) is a separate machine. I included it's config as I thought it would be helpful comparison because it is not exhibiting the behaviour as the Funtoo box. I built the genkernel on Funtoo via SSH. Quite certain I followed the instructions you gave me accurately. It just didn't work. Cleaning up afterwards was messy - not up on all the details of kernel handling. Ended up un-merging and re-merging debian-sources. Made me appreciate what the folks at SystemRescueCD have done even more. I'm not sure what you're asking me to do next.
  25. CPU Soft Lockups of custom kernel and ZFS?

    Will have to find the time to upgrade my system. For the time being, I don't use Firefox. Neither the `updatedb` command. Both of which freeze the system.
  26. Local overlay woes

    actually the easiest way is to switch to media-kit/1.2-prime there is darktable there in 2.4.0 version. ego config set kits media-kit 1.2-prime ego sync emerge -av darktable
  27. Outdated packages + Hardened profile (N00B)

    well, yes. but it has lots of rough edges, so be prepared. (gnome-3.26 kit is not ready for normal use). this is on my laptop ego kit list /var/git/meta-repo (updated 2 minutes ago): kit is active? branch stability core-kit 1.0-prime prime 1.1-prime deprecated active 1.2-prime alpha core-hw-kit active master prime security-kit 1.0-prime prime 1.1-prime deprecated active 1.2-prime alpha xorg-kit 1.17-prime prime active 1.19-prime prime gnome-kit active 3.20-prime prime 3.26-prime dev kde-kit active 5.10-prime prime media-kit 1.0-prime deprecated 1.1-prime prime active 1.2-prime dev perl-kit 5.24-prime prime active 5.26-prime dev python-kit 3.4-prime prime active 3.6-prime prime 3.6.3-prime deprecated php-kit active master prime java-kit 1.1-prime prime active 1.2-prime dev ruby-kit 1.1-prime prime active 1.2-prime dev haskell-kit 1.1-prime prime active 1.2-prime dev ml-lang-kit 1.1-prime prime active 1.2-prime dev lisp-scheme-kit 1.1-prime prime active 1.2-prime dev lang-kit 1.1-prime prime active 1.2-prime dev dev-kit 1.1-prime prime active 1.2-prime dev xfce-kit active 4.12-prime prime desktop-kit 1.1-prime prime active 1.2-prime dev editors-kit active master prime net-kit active master prime text-kit active master prime science-kit active master prime games-kit active master prime nokit active master prime
  28. Outdated packages + Hardened profile (N00B)

    Last one for now, for maximum bleeding edge I should use the dev kits, right?
  1. Load more activity
×