Installation problem

Forum Forums New users New Users and General Questions Installation problem

  • This topic has 9 replies, 4 voices, and was last updated Jan 31-7:06 pm by BillyBadBoy.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #98600
    Member
    BillyBadBoy

      Hi, I’m having problems installing AntiX. This is what I’ve done so far:

      [1] Copied the iso image to a usb stick using ‘USB Writer’

      [2] Booted to the usb stick with my Asus notebook:
      – the menu appeared
      – I set the keyboard to en/GB
      – I ran AntiX

      The desktop appeared OK, but then I realised that the touchpad and the wifi weren’t working.

      [3] At this point I temporarily gave up with AntiX and tried installing MX linux from another usb stick:
      – I booted to the usb stick
      – saw that the touchpad/wifi were working OK
      – went ahead and did a full install of MX (completely removing the windows o/s)

      [4] A couple of days later (after I had got hold of an ethernet/usb adapter), I thought I would try AntiX again.
      – I booted to the same AntiX usb stick that I’d used before
      – the menu appeared
      – I set the keyboard to en/GB
      – I tried to run AntiX

      But, unlike in [2] above, the desktop does NOT appear. Instead it leaves me at the command prompt, suggesting that I do a cli install.

      As a sanity check I tried using another AntiX usb stick – but the results are the same. It appears that installing MX linux has done something that prevents AntiX from booting properly.

      Any ideas about what I can do to fix this?

      • This topic was modified 3 months, 1 week ago by BillyBadBoy.
      #98607
      Member
      punranger
        Helpful
        Up
        0
        ::

        A partial suggestion to point 2:

        Try loading a different kernel when running the USB. This sometimes resolves wifi issues. Not sure about the touchpad, though.

        If you can get a system info output by running “inxi –full” from the usb and post it here, that might be helpful. You can do that from MX too.

        MX and antiX share some properties, so I’m guessing you’re right about point 4, but I’ll let the experienced guys respond to that…

        antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg

        #98608
        Forum Admin
        rokytnji
          Helpful
          Up
          0
          ::

          Looks like antiX is picking up that added wifi adapter and is dropping to cli install.

          What happens when you remove it? Then boot the antiX USB.

          Sometimes I drive a crooked road to get my mind straight.
          Not all who Wander are Lost.
          I'm not outa place. I'm from outer space.

          Linux Registered User # 475019
          How to Search for AntiX solutions to your problems

          #98609
          Forum Admin
          anticapitalista
            Helpful
            Up
            0
            ::

            Which version of antiX?
            Which version of MX?
            Which kernel did you boot into?

            Philosophers have interpreted the world in many ways; the point is to change it.

            antiX with runit - leaner and meaner.

            #98618
            Member
            BillyBadBoy
              Helpful
              Up
              0
              ::

              antiX-22-net_x64-net.iso
              MX-21.3_x64.iso
              kernel: whatever the default is

              I’ve just tried to install the base image and managed to get a little further.
              I was able to boot to the desktop and start the full installation, but it soon failed.
              I attach screenshot of the live logs – it complains about not being able to prepare the required partitions.

              #98620
              Member
              BillyBadBoy
                Helpful
                Up
                0
                ::

                Hi, it’s not an added wifi adapter – it’s built in to the laptop.

                #98621
                Member
                BillyBadBoy
                  Helpful
                  Up
                  0
                  ::

                  more info: here is the system info from the MX installation:

                  System:    Kernel: 5.10.0-21-amd64 [5.10.162-1] x86_64 bits: 64 compiler: gcc v: 10.2.1
                             parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64
                             root=UUID=<filter> ro quiet splash
                             Desktop: Xfce 4.18.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
                             dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower January 15  2023
                             base: Debian GNU/Linux 11 (bullseye)
                  Machine:   Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop E210MAB_E210MA v: 1.0
                             serial: <filter>
                             Mobo: ASUSTeK model: E210MAB v: 1.0 serial: <filter> UEFI: American Megatrends
                             v: E210MAB.304 date: 05/20/2022
                  Battery:   ID-1: BAT0 charge: 38.3 Wh (100.0%) condition: 38.3/38.0 Wh (100.6%) volts: 7.9
                             min: 7.9 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Discharging
                  CPU:       Info: Dual Core model: Intel Celeron N4020 bits: 64 type: MCP arch: Goldmont Plus
                             family: 6 model-id: 7A (122) stepping: 8 microcode: 1E cache: L2: 4 MiB
                             flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 4377
                             Speed: 898 MHz min/max: 800/2800 MHz Core speeds (MHz): 1: 898 2: 1022
                             Vulnerabilities: Type: itlb_multihit status: Not affected
                             Type: l1tf status: Not affected
                             Type: mds status: Not affected
                             Type: meltdown status: Not affected
                             Type: mmio_stale_data status: Not affected
                             Type: retbleed status: Not affected
                             Type: spec_store_bypass
                             mitigation: Speculative Store Bypass disabled via prctl and seccomp
                             Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
                             Type: spectre_v2
                             mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected
                             Type: srbds status: Not affected
                             Type: tsx_async_abort status: Not affected
                  Graphics:  Device-1: Intel GeminiLake [UHD Graphics 600] vendor: ASUSTeK driver: i915 v: kernel
                             bus-ID: 00:02.0 chip-ID: 8086:3185 class-ID: 0300
                             Device-2: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-5:2
                             chip-ID: 13d3:5a11 class-ID: 0e02
                             Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver:
                             loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1
                             Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
                             s-diag: 414mm (16.3")
                             Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 136 size: 256x144mm (10.1x5.7")
                             diag: 294mm (11.6")
                             OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 20.3.5
                             direct render: Yes
                  Audio:     Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: ASUSTeK
                             driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci bus-ID: 00:0e.0
                             chip-ID: 8086:3198 class-ID: 0403
                             Sound Server-1: ALSA v: k5.10.0-21-amd64 running: yes
                             Sound Server-2: PulseAudio v: 14.2 running: yes
                  Network:   Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave
                             driver: rtl8821ce v: v5.5.2.1_35598.20191029 modules: rtw88_8821ce,wl port: e000
                             bus-ID: 02:00.0 chip-ID: 10ec:c821 class-ID: 0280
                             IF: wlan0 state: up mac: <filter>
                             Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152 bus-ID: 1-3:4
                             chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
                             IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
                  Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-8:3
                             chip-ID: 13d3:3557 class-ID: e001 serial: <filter>
                             Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block:
                             hardware: no software: yes address: <filter>
                             Info: acl-mtu: 820:8 sco-mtu: 255:12 link-policy: rswitch hold sniff park
                             link-mode: slave accept
                  Drives:    Local Storage: total: 58.24 GiB used: 8.12 GiB (13.9%)
                             ID-1: /dev/mmcblk0 maj-min: 179:0 model: G1J38E size: 58.24 GiB block-size:
                             physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 0x8 scheme: GPT
                             SMART Message: Unknown smartctl error. Unable to generate data.
                  Partition: ID-1: / raw-size: 54.98 GiB size: 53.82 GiB (97.88%) used: 8.12 GiB (15.1%) fs: ext4
                             dev: /dev/mmcblk0p2 maj-min: 179:2
                             ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 282 KiB (0.1%) fs: vfat
                             dev: /dev/mmcblk0p1 maj-min: 179:1
                  Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
                             ID-1: swap-1 type: partition size: 3 GiB used: 0 KiB (0.0%) priority: -2
                             dev: /dev/mmcblk0p3 maj-min: 179:3
                  Sensors:   System Temperatures: cpu: 35.0 C mobo: N/A
                             Fan Speeds (RPM): cpu: 0
                  Repos:     Packages: note: see --pkg apt: 1980 lib: 990 flatpak: 0
                             No active apt repos in: /etc/apt/sources.list
                             Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
                             1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
                             Active apt repos in: /etc/apt/sources.list.d/debian.list
                             1: deb http://deb.debian.org/debian bullseye main contrib non-free
                             2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
                             Active apt repos in: /etc/apt/sources.list.d/mx.list
                             1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
                             Active apt repos in: /etc/apt/sources.list.d/vscode.list
                             1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
                  Info:      Processes: 183 Uptime: 7m wakeups: 85 Memory: 3.67 GiB used: 912.4 MiB (24.3%)
                             Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A
                             alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
                  Boot Mode: UEFI
                  • This reply was modified 3 months, 1 week ago by rokytnji. Reason: code tags
                  #98626
                  Forum Admin
                  rokytnji
                    Helpful
                    Up
                    1
                    ::

                    On something that new I would use the full iso since kernel 5.10 is included on that iso.

                    It is under advanced boot options on grub screen. Thanks for clearing up the wifi question.

                    All versions default to using our legacy 4.9.0-326 kernel. 5.10 kernels are available.

                    https://antixlinux.com/updated-antix-sid-iso-files-available/

                    Sometimes I drive a crooked road to get my mind straight.
                    Not all who Wander are Lost.
                    I'm not outa place. I'm from outer space.

                    Linux Registered User # 475019
                    How to Search for AntiX solutions to your problems

                    #98631
                    Member
                    BillyBadBoy
                      Helpful
                      Up
                      0
                      ::

                      My first attempt (with antiX-22-net_x64-net.iso) presumably used kernel 4.9 since it’s the default.
                      On my latest attempt (with antiX-22_x64-base.iso) I chose the ‘modern’ kernel.

                      But is the kernel version relevant? With the base image I able to bring up the desktop and begin the installation process, but it fails because it can’t “prepare the required partitions” (see the screenshot above). This sounds like something is fundamentally wrong.

                      #98639
                      Member
                      BillyBadBoy
                        Helpful
                        Up
                        1
                        ::

                        Update: I’ve now managed to install AntiX!!!

                        There were 2 issues:

                        [1] The first issue is down to my stupidity. I hadn’t noticed that the drop-down for selecting the destination drive was defaulting back to my usb stick!!! (Note that the MX installer does not do this – it defaults to my laptop’s hard disk).

                        [2] Even after correcting [1] the installation was failing because it could not format the partitions. I was using the default setting – with the slider to the right. The installation worked, however, if I move the slider to the left (and allocate a ‘home’ partition). (Note that with MX I was able to install with the slider completely to the right).

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