Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

palica

Members
  • Posts

    294
  • Joined

  • Last visited

  • Days Won

    11

Posts posted by palica

  1. Funtoo tries to test stuff internally by the devs and not "leave" the testing to normal users that sometimes don't have a clue. So that is why funtoo is using gcc-5.4.0 to compile stages and also as default compiler. There are already stages that are getting build with gcc-6.3.0 and there soon will be a new toolchain upgrade/release for all. You are welcome to join the #funtoo-dev on freenode (IRC) if you have time and resources and would like to help test new stuff.

  2. @Sandro, I would like to redirect you here -

    The topic title should be edited from "VLC doesn't run very well" to something more concrete like: Random flashes or black frames in VLC while playing movies in fullscreen

    Try to add more information, that you think could be relevant to the problem. Like driver used, kernel version, is it only for certain videos or for all, fullscreen/windowed...

    Also try to update to media-kit:1.1-prime by issuing these commands

    Quote

    ego config set kits media-kit 1.1-prime

    ego sync

    emerge -av vlc

     

  3. I would start over from a fresh install. Just backup your data and wipe the partition.

    1. Your processor is Silvermont according to this https://en.wikipedia.org/wiki/List_of_Intel_Pentium_microprocessors#"Bay_Trail-M"_(22_nm)
      1. Grab this stage3 from build.funtoo.org - funtoo-current/x86-64bit/intel64-silvermont/2017-12-09/stage3-intel64-silvermont-funtoo-current-2017-12-09.tar.xz
        1. these are the settings already active in the stage3 so no need to set them by hand
          Quote

          CPU Information

          CHOST x86_64-pc-linux-gnu
          CFLAGS -march=silvermont -O2 -pipe
          CPU_FLAGS (see CPU_FLAGS for more info) aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3

           

        2. add only these settings to the make.conf:
          Quote
          LINGUAS="en ru"
          L10N="${LINGUAS}"
           
          VIDEO_CARDS="intel"
          INPUT_DEVICES="evdev keyboard mouse synaptics"


           

        3. run these commands:
           

          Quote

          epro flavor desktop

          epro mix-ins lxde


           

        4. update your system:
           

          Quote

          emerge -avuDN --with-bdeps=y --newrepo @world


           

        5. emerge lxde-meta:
           

          Quote

          emerge -av lxde-meta


           

        6. continue the installation according to:
          https://www.funtoo.org/Install#Configuring_your_system

        7. report back here how it went

     

  4. znavko, please follow the Install guide on www.funtoo.org - https://www.funtoo.org/Install

    if you cannot/or don't want to - paste every single file that you have in /etc/portage so

    /etc/portage/make.conf
    /etc/portage/package.*
    ...
    /var/lib/portage/world
    emerge --info

    But frankly, it will take so much time to resolve it, that a reinstall is probably a better and faster solution. Also don't use -O3 period.

    Quote from gentoo wiki:

    Quote

    -O3: the highest level of optimization possible. It enables optimizations that are expensive in terms of compile time and memory usage. Compiling with -O3 is not a guaranteed way to improve performance, and in fact, in many cases, can slow down a system due to larger binaries and increased memory usage. -O3 is also known to break several packages. Using -O3 is not recommended. However, it also enables -ftree-vectorize so that loops in the code get vectorized and will use AVX YMM registers.

    Once you get familiar with funtoo and portage you can then switch, but starting with funtoo and doing all sorts of crazy things that you don't understand is just a waste of time for everybody.

     

  5. We’d love to help you. To improve your chances of getting an answer, here are some tips:

    Search, and research

    ...and keep track of what you find. Even if you don't find a useful answer elsewhere on the site, including links to related questions that haven't helped can help others in understanding how your question is different from the rest.

    Write a title that summarizes the specific problem

    The title is the first thing potential answerers will see, and if your title isn't interesting, they won't read the rest. So make it count:

    • Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem? Include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site.

    • Spelling, grammar and punctuation are important! Remember, this is the first part of your question others will see - you want to make a good impression. If you're not comfortable writing in English, ask a friend to proof-read it for you.

    • If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem.

    Examples:

    • Bad: Is there command to do what it needs?
    • Good: How can I apply changes proposed by emerge?
    • Bad: Problem update system
    • Good: Why does the compile of dev-libs/boost-1.63.0 fail with x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)?

    Introduce the problem before you post any code

    In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible.

    Help others reproduce the problem

    Not all questions benefit from including code. Here are some guidelines:

    • Include just enough code to allow others to reproduce the problem.
    • For portage errors include all the relevant info and output.

    Include all relevant tags

    Try to include a tag for the language, library, and specific API your question relates to. If you start typing in the tags field, the system will suggest tags that match what you've typed - be sure and read the descriptions given for them to make sure they're relevant to the question you're asking! See also: What are tags, and how should I use them?

    Proof-read before posting!

    Now that you're ready to ask your question, take a deep breath and read through it from start to finish. Pretend you're seeing it for the first time: does it make sense? Try reproducing the problem yourself, in a fresh environment and make sure you can do so using only the information included in your question. Add any details you missed and read through it again. Now is a good time to make sure that your title still describes the problem!

    Post the question and respond to feedback

    After you post, leave the question open in your browser for a bit, and see if anyone comments. If you missed an obvious piece of information, be ready to respond by editing your question to include it. If someone posts an answer, be ready to try it out and provide feedback!

    Look for help asking for help

    In spite of all your efforts, you may find your questions poorly-received. Don't despair! Learning to ask a good question is a worthy pursuit, and not one you'll master overnight. Here are some additional resources that you may find useful:

  6.  

    3 hours ago, znavko said:

    I am seeing this problem again now just browsing the web.

    what problem are you seeing again?

    maybe there is something wrong with your hardware if it stops working, maybe there was something wrong with xfce and maybe there is something wrong with lxde. It is hard to tell if you don't provide any context.

    Do you have anything in the logs, anything in dmesg ...

    I would also suggest you try to run software compiled with "supported" CFLAGS as was already suggested. I don't see any problem with the last emerge lxde-meta lxde-common ... What do you mean:

    4 hours ago, znavko said:

    I typed `emerge lxde-meta lxde-common xorg-x11` and got this https://pastebin.com/R2GmsBZ8

    Why are you compiling your system with -O3? How are you recompiling it? There are just too many variables involved.

×
×
  • Create New...