Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

palica

Members
 View Profile  See their activity

  • Posts

    294

  • Joined

  • Last visited

  • Days Won

    11

 Content Type 

Posts posted by palica

  2. Changed cpu mother and ram can not boot or chroot now

    in General Help

    Posted

    seems to me that the two subarch are not compatible. so piledriver is not supported on ryzen. just guessing here. You will need to reinstall at least the @system part of the installation.

    I would backup /home and /etc and /var/lib/portage/world and use a stage3 that supports ryzen or just a plain generic_64bit and run a emerge @world after you copy the /etc /var/lib/portage/world back.

     

  3. [Solved] Why does debian kernel need 20G free disk space?

    in Installation Help

    Posted

    8 hours ago, bluephoenix said:

    For those OLD machine, 20G free disk space is not so easy.

    you can compile it on a newer machine and install binary package.

     

    8 hours ago, bluephoenix said:

    1. Why compiling debian kernel consumes too much resource while gentoo kernel does not?

    the kernel size and also the kernel compile/build dir size depends on the amount of modules/options selected. You can surely build a smaller kernel with only modules you know you'll use.

     

    8 hours ago, bluephoenix said:

    2. Could I choose to use Gentoo kernel without any problem coupled with Funtoo architecture? 

    Yes, you can!

  6. Xorg - Screen not found

    in Portage Help

    Posted

    Excerpt from manual www.funtoo.org/Install:
     
    Quote

     

    Important

    At this point it is wise to emerge latest sys-kernel/linux-firmware package, because various drivers rely on firmware blobs and instructions. Hardware like wi-fi cards, graphic cards, network cards, and others will not work properly or at all if firmware not present.

     

    it would be probably wise to make it a required step of the Install.

  8. Anonymous usage reports for funtoo kits usage

    in General Discussion

    Posted

    With the latest tree update there is a package for reporting usage of funtoo profiles, kits and other stuff. It is called -

    dev-perl/Funtoo-Report

    Please test it out and start reporting your machine to the elasticsearch backend. The kibana frontend can be found on this address http://elk.liguros.net/, I have made a simple Dashboard (http://elk.liguros.net/app/kibana#/dashboard/41e03450-0b28-11e8-a9dd-1718169924ab?_g=(refreshInterval%3A('%24%24hashKey'%3A'object%3A343'%2Cdisplay%3A'15 minutes'%2Cpause%3A!f%2Csection%3A2%2Cvalue%3A900000)%2Ctime%3A(from%3Anow-7d%2Cmode%3Aquick%2Cto%3Anow)). I and haxmeister would be happy to hear your thoughts and critique.

    The source code for the tool can be found here:

    https://github.com/haxmeister/funtoo-reporter.git

    Here a simple howto use this tool:

    e 

    emerge -av Funtoo-Report

Just launching the program will show you a help menu:

funtoo-report

Funtoo anonymous data reporting tool usage:

funtoo-report send              Send the report to funtoo's data collection
funtoo-report show-json         Show the output that will be sent, in JSON format
funtoo-report help              Show this help list

Output can be ommitted by modifying the /etc/report.conf file

help shows you the same output:

funtoo-report help

To see what data the report is generating use the show-json option:

funtoo-report show-json

You may get an error that no config file is found at /etc/report.conf and it will then try to create one with all available options turned on:

Could not open file the configuration file at /etc/report.conf
Attempting to create one...

A config file has been generated at /etc/report.conf
Please review this file for errors.

You can send your report to the elastic search database using the send option which will output nothing on the console if it is successful:

funtoo-report send

    It is ok to create a cron job for this to automatically submit new data to ES (Elasticsearch). It should handle the load :)

  12. Using layman on a funtoo container

    in Funtoo Hosting

    Posted

    you will have to delete /etc/portage/repos.conf symlink and create a normal directory and populate it as shown below ... 

    /etc/portage # ❯❯❯ ls -alF repos.conf
total 108
drwxr-xr-x 1 root root 696 Feb  7 21:17 ./
drwxr-xr-x 1 root root 504 Jan 30 03:12 ../
-rw-r--r-- 1 root root  90 Feb 13 19:39 ego-core-hw-kit
-rw-r--r-- 1 root root 116 Feb 13 19:39 ego-core-kit
-rw-r--r-- 1 root root  90 Feb 13 19:39 ego-desktop-kit
-rw-r--r-- 1 root root  82 Feb 13 19:39 ego-dev-kit
-rw-r--r-- 1 root root  90 Feb 13 19:39 ego-editors-kit
-rw-r--r-- 1 root root  86 Feb 13 19:39 ego-games-kit
-rw-r--r-- 1 root root  86 Feb 13 19:39 ego-gnome-kit
-rw-r--r-- 1 root root  90 Feb 13 19:39 ego-haskell-kit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-java-kit
-rw-r--r-- 1 root root  82 Feb 13 19:39 ego-kde-kit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-lang-kit
-rw-r--r-- 1 root root  98 Feb 13 19:39 ego-lisp-scheme-kit
-rw-r--r-- 1 root root  86 Feb 13 19:39 ego-media-kit
-rw-r--r-- 1 root root  90 Feb 13 19:39 ego-ml-lang-kit
-rw-r--r-- 1 root root  82 Feb 13 19:39 ego-net-kit
-rw-r--r-- 1 root root  81 Feb 13 19:39 ego-nokit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-perl-kit
-rw-r--r-- 1 root root  82 Feb 13 19:39 ego-php-kit
-rw-r--r-- 1 root root  88 Feb 13 19:39 ego-python-kit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-ruby-kit
-rw-r--r-- 1 root root  90 Feb 13 19:39 ego-science-kit
-rw-r--r-- 1 root root  92 Feb 13 19:39 ego-security-kit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-text-kit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-xfce-kit
-rw-r--r-- 1 root root  84 Feb 13 19:39 ego-xorg-kit
-rw-r--r-- 1 root root 200 Feb  7 21:17 layman.conf

    copy or link the files from /var/git/meta-repo/repos.conf to /etc/portage/repos.conf as shown above

    here is a oneliner to link all files from meta-repo to portage 

    cd /var/git/meta-repo/repos.conf; for i in *;do ln -s $i /etc/portage/repos.conf/ego-$i;done

    create your overlay file such as layman.conf or local.conf or whatever and put your overlay settings there.

     

  15. ZFS Mountpoints

    in Server Help

    Posted

    Supported boot parameters

    • rollback=<on|yes|1> Do a rollback of specified snapshot.
    • zfs_debug=<on|yes|1> Debug the initrd script
    • zfs_force=<on|yes|1> Force importing the pool. Should not be necessary.
    • zfs=<off|no|0> Don't try to import ANY pool, mount ANY filesystem or even load the module.
    • rpool=<pool> Use this pool for root pool.
    • bootfs=<pool>/<dataset> Use this dataset for root filesystem.
    • root=<pool>/<dataset> Use this dataset for root filesystem.
    • root=ZFS=<pool>/<dataset> Use this dataset for root filesystem.
    • root=zfs:<pool>/<dataset> Use this dataset for root filesystem.
    • root=zfs:AUTO Try to detect both pool and rootfs

    In all these cases, <dataset> could also be <dataset>@<snapshot>.

    Booting from snapshot:

    Enter the snapshot for the root= parameter like in this example: 

    linux   /ROOT/funtoo-1@/boot/vmlinuz root=ZFS=rpool/ROOT/funtoo-1@some_snapshot ro boot=zfs $bootfs quiet

    This will clone the snapshot rpool/ROOT/funtoo-1@some_snapshot into the filesystem rpool/ROOT/funtoo-1_some_snapshot and use that as root filesystem. The original filesystem and snapshot is left alone in this case.

     

  21. Can you explain x86_64-pc-linux-gnu-gcc -v versus -V in my log files?

    in Installation Help

    Posted

    12 hours ago, dougbmorris said:

    I tried piecemeal with gcc, binutils, and glibc.  I ran 'emerge -avk1 gcc' and got good results until end of output:

    Locke ~ # emerge -avk1 gcc

    why don't you finish rebuilding the toolchain and start emerging @preserved-rebuild in the middle of the procedure?

    Please run: 

    # Fixing GCC
emerge -avk1 gcc
gcc-config -l
(output of compiler profiles use the reinstalled version in the next command)
gcc-config --force x86_64-pc-linux-gnu-5.4.0
. /etc/profile

# Fixing binutils
emerge -avk1 binutils
binutils-config -l
(output of binutils profiles again use the one reinstalled from binary)
binutils-config x86_64-pc-linux-gnu-2.29.1

# Fixing glibc
emerge -avk1 glibc

    now I would probably run 

    emerge -ave @system

    after this is complete (and you didn't upgrade gcc version - so gcc-5 was also before system failure your default compiler) you can now take care of anything else that needs fixing on your box. running emerge -avuDN --with-bdeps=y @world and then if needed emerge -av @preserved-rebuild

    If you also upgraded from a different major version of gcc, then you need to run (before @world and @preserved-rebuild) 

    revdep-rebuild --library 'libstdc++.so' -- --exclude gcc

    Let us know how it went.

×
×
  • Create New...