Antix 19 does not start

  • This topic has 6 replies, 5 voices, and was last updated Oct 20-10:19 pm by andfree.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #28244
    Member
    byjosemaria

      Antix 19 does not start.
      It may seem curious in a Virtual Box virtual machine, antix 19 starts very quickly and correctly. But on a real computer, Antix 19 does not start, it goes very slow and in the boot processor it is completely stopped in the window called ….. “start X”.
      The loading process up to that “Start X” window is slower than with Antix 17.4.1

      I have installed Antix 17.4.1, Mx Linux 18.3 on that same computer and they work perfectly. I created the live usb with rufus or MX Constructor Usb. I have tried the Isos: Full and Base.

      Regards

      #28247
      Forum Admin
      BitJam
        Helpful
        Up
        0
        ::

        completely stopped in the window called ….. “start X”.

        This sounds only like a problem with the graphics driver. You should be able to get to a console log-in from that screen with the key combo Alt-F2.

        Have you tried the “Safe Video” boot option? It should be in the bootloader menu. This should help you get X started but without accelerated graphics. We would also like to see the output of the “inxi -Fxx” command but it may be hard to get that info to us if X doesn’t start. One way would to switch to a virtual console with Alt-F2, log in, run the command, and then take a picture of the screen.

        You can also get that information from your antiX-17 or MX-18 install or live media because we want to know about your hardware.

        This situation is not extremely unusual. The “safe video” option should help you get to X. Once we know more about your hardware then we can suggest solutions.

        PS: we added that “Start X” window so it would be easier to distinguish between a video driver problem and the system not booting at all. The video driver problem should be easier to solve.

        Context is worth 80 IQ points -- Alan Kay

        #28251
        Member
        byjosemaria
          Helpful
          Up
          0
          ::

          Hi:
          The first video Antix 17.4.1 Ok
          https://photos.app.goo.gl/ne4Uq9cr8PFRrcQt7

          The second Antix 19 video, “normal boot”
          https://photos.app.goo.gl/kFSYZd8YfQLAM5eC9

          The third video Antix 19, “Safe video Mode”
          https://photos.app.goo.gl/R3iaD3LQ4KjTmbDw7

          Neither of the two ways to start Antix19 has finished well

          regards

          #28261
          Member
          ex_Koo
            Helpful
            Up
            0
            ::

            @byjosemaria

            Try failsafe mode..
            or
            try editing Boot Options line by adding nomodeset to end of the line make sure you add a space before you type nomodeset

            What type of video card do you have or is integrated cpu video ?

            #28281
            Member
            byjosemaria
              Helpful
              Up
              0
              ::

              Hi:

              Yes i have a external video card (Pci express) Hdmi: Nvidia Geforce GT170

              – Try failsafe mode….> not start

              – option “nomodoset” over:
              * normal boot -> does not work
              * “save video mode” -> does not work
              * “Failsafe Boot” -> If it works only with 1024×768 resolution
              Thanks

              @byjosemaria

              Try failsafe mode..
              or
              try editing Boot Options line by adding nomodeset to end of the line make sure you add a space before you type nomodeset

              What type of video card do you have or is integrated cpu video ?

              • This reply was modified 3 years, 6 months ago by byjosemaria.
              #28283
              Moderator
              christophe
                Helpful
                Up
                0
                ::

                I had the same situation (hanging at “start x” screen). It would hang there for several minutes; so long that I assumed it was frozen.

                Although it doesn’t seem like this would be the answer, this forum post fixed it for me:
                https://www.antixforum.com/forums/topic/upon-booting-dhcp-looks-for-eth0-network-which-slows-boot-time/

                In particular, using this recommendation from anticapitalista:

                Another option since you are running frugal (live) 
                is to add m to the disable cheat at the boot menu.
                
                eg disable=lxm
                • This reply was modified 3 years, 6 months ago by christophe.

                confirmed antiX frugaler, since 2019

                #28327
                Member
                andfree
                  Helpful
                  Up
                  0
                  ::

                  Hi. In my case, it’s not exactly that it never starts, but sometimes (not all times) the slim login screen takes too many time to appear.

                  $ inxi -Fxz
                  System:
                    Host: dragon Kernel: 4.9.193-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 
                    Desktop: IceWM 1.5.5+git20190610 
                    Distro: antiX-19_386-full Marielle Franco 16 October 2019 
                    base: Debian GNU/Linux 10 (buster) 
                  Machine:
                    Type: Laptop System: TOSHIBA product: Satellite 2450 v: PS245E-03TE0-GK 
                    serial: <filter> 
                    Mobo: TOSHIBA model: Portable PC v: Version A0 serial: <filter> BIOS: TOSHIBA 
                    v: Version 1.30 date: 03/20/2003 
                  CPU:
                    Topology: Single Core model: Intel Pentium 4 bits: 32 type: MCP 
                    arch: Netburst Northwood rev: 7 L2 cache: 512 KiB 
                    flags: pae sse sse2 bogomips: 5585 
                    Speed: 2793 MHz min/max: N/A Core speed (MHz): 1: 2793 
                  Graphics:
                    Device-1: NVIDIA NV17M [GeForce4 420 Go] vendor: Toshiba America Info Systems 
                    driver: nouveau v: kernel bus ID: 01:00.0 
                    Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa 
                    resolution: 1024x768~60Hz 
                    OpenGL: renderer: Mesa DRI nv17 x86/MMX/SSE2 v: 1.2 Mesa 18.3.6 direct render: Yes 
                  Audio:
                    Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: Toshiba America Info Systems 
                    driver: snd_intel8x0 v: kernel bus ID: 00:1f.5 
                    Sound Server: ALSA v: k4.9.193-antix.1-486-smp 
                  Network:
                    Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
                    vendor: Toshiba America Info Systems driver: 8139too v: 0.9.28 port: ce00 
                    bus ID: 02:09.0 
                    IF: eth0 state: down mac: <filter> 
                    IF-ID-1: wlan0 state: up mac: <filter> 
                  Drives:
                    Local Storage: total: 93.16 GiB used: 19.93 GiB (21.4%) 
                    ID-1: /dev/sda vendor: Toshiba model: MK1032GAX size: 93.16 GiB 
                  Partition:
                    ID-1: / size: 89.19 GiB used: 19.93 GiB (22.3%) fs: ext4 dev: /dev/sda1 
                    ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
                  Sensors:
                    System Temperatures: cpu: 65.0 C mobo: N/A 
                    Fan Speeds (RPM): N/A 
                  Info:
                    Processes: 134 Uptime: 14m Memory: 1001.0 MiB used: 294.1 MiB (29.4%) Init: SysVinit 
                    runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36
                  • This reply was modified 3 years, 6 months ago by andfree.
                Viewing 7 posts - 1 through 7 (of 7 total)
                • You must be logged in to reply to this topic.