Antix freeze

Tagged: ,

  • This topic has 6 replies, 4 voices, and was last updated Feb 20-8:46 pm by sbis.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #99300
    Member
    sbis

      Hi all,
      sometimes my pc freeze and nothing work.
      The pointer moves very slowly, the keyboard doesn’t work and the only way is reboot the pc.

      I don’t know how to replicate the problem so I want to know if there is a tool to read the logs when the pc freeze.
      I read in other web site there is a tool named “journalctl” but I don’t find it.
      What can I use?

      Thanks a lot

      #99319
      Member
      stevesr0
        Helpful
        Up
        0
        ::

        Hi sbis,

        It would help people to help you if you could describe in detail (a) what the computer is running when this happens, (b) details about the hardware (see inxi –help for details – oftentimes people ask for something like inxi -Fxxx) and (c) details of software that is installed. (Inxi -Fxxx includes the running kernel version.)

        I associate “journalctl” with systemd – I don’t think it is included on most antiX installs.

        stevesr0

        #99328
        Member
        sybok
          Helpful
          Up
          0
          ::

          Hi, expanding a bit on the recommendations by stevesr0:

          0) More info about your system, did you do any additional “suspicious” installs of packages such as changing desktop to other than already present in the default install etc.?

          1) Please describe the occurrences of this freezes in more detail. Is it typically associated with a specific program running? Do you run RAM/CPU heavy applications when this happens?

          2) You may wish explore/post (as attachments) the following logs:
          2.A) ‘~/.desktop-session/log’ or ‘~/.desktop-session/log.old’
          2.B) /var/log/ <– most of them are not to be read by user, i.e. you may need to access them with elevated privileges, few tips where to look are ‘dmesg’, ‘kern.log’, ‘Xorg.0.log’ (or their older versions); try to find errors.

          3) Freeze: I experienced freezes with AMD Ryzen, which was a known “issue” – using the most recent kernel available in antiX and changing BIOS settings (to more power hungry) helped.
          https://www.antixforum.com/forums/topic/random-freezes-with-ryzen/

          #99337
          Member
          marcelocripe
            Helpful
            Up
            0
            ::

            Hello sbis.

            Please read this topic How to get HELP with an antiX PROBLEM.

            #99352
            Member
            sbis
              Helpful
              Up
              0
              ::

              Hi friends,

              3) Freeze: I experienced freezes with AMD Ryzen, which was a known “issue” – using the most recent kernel available in antiX and changing BIOS settings (to more power hungry) helped.
              https://www.antixforum.com/forums/topic/random-freezes-with-ryzen/

              Thanks sybok, probably the problem is the CPU; a AMD Ryzen 5 5600G with Radeon Graphics as you can see in the attached files.
              I’ll read the link you posted for a solution.

              Bye

              Attachments:
              #99370
              Member
              sbis
                Helpful
                Up
                0
                ::

                Hi,
                I have upgrade the BIOS to the latest stable version.
                Let’s see what happen in the next days.
                I’ll write if the problem persist.
                Bye

                #100192
                Member
                sbis
                  Helpful
                  Up
                  0
                  ::

                  Hi all,
                  since the last bios update the problem there was no more.
                  I’ll see in the next few days but I’m confident.
                  Bye

                Viewing 7 posts - 1 through 7 (of 7 total)
                • You must be logged in to reply to this topic.