Antix as a Linode VM. Any previous experience?

Forum Forums New users New Users and General Questions Antix as a Linode VM. Any previous experience?

  • This topic has 6 replies, 3 voices, and was last updated Aug 22-5:23 pm by frtorres.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #59294
    Member
    frtorres

      Hi all

      I have been trying to install Antix-19.3-x64-full *15 October 2020) in a Linode VM 8gb RAM and 160 GB on disk.

      I followed this howto>:

      install-a-custom-distribution-on-a-linode

      ISO file boots ok to grub2 menu but when trying to install I got:

      Fatal Error
      No usb,cd devices found
      p=power off
      r=reboot
      Select p or r  then press <enter>

      I tested other distros and the installer find disks to install and all continues ok.

      Any Antix community member with some previous experience installing Antix in a Linode VM?

      Maybe another ISO file with a different kernel could help?

      Thanks in advance for any hint to make some progress on this.

      Francisco

      #59300
      Member
      Xecure
        Helpful
        Up
        0
        ::

        I have no idea how Linode handles the ISOs. Maybe it requires a network PXE install method on the ISO.

        The error seems to be that it cannot find the boot devise. Try using the boot parameter
        from=all toram
        to see if that helps to initially boot it on the Linode server.

        antiX Live system enthusiast.
        General Live Boot Parameters for antiX.

        #59848
        Member
        frtorres
          Helpful
          Up
          0
          ::

          Thanks @Xecure.

          I Tested using your advised boot options,

          Results:

          booting the kernel keeps:

          
          waiting for /dev/ to be fully populated.
          

          See attachment.

          I was following this howto:

          Basically I used a VM 1Gb RAM configuration with a

          1- 2GB disk (where I copied Antix ISO File using [dd if= of] )
          2- 30GB for HD Installation.

          By means of Linode Web Interface, I booted Antix ISO File

          ISO used: antiX-19.3_x64-full.iso

          I tested this procedure successfully with other debian and slackware distros but I want Antix because this VM with 1Gb RAM and USD5 montly is suitable for Antix and my needs as a remote desktop.

          Any hint or advice? (maybe other Antix ISO?)

          Thanks again for your kind help.

          Francisco

          #59850
          Anonymous
            Helpful
            Up
            0
            ::

            Have you tried adding to your bootline
            nomodeset

            Have you queried linode community forum to check other cases similar to yours?
            https://www.linode.com/community/questions/search?query=udev

            adding one of the following to the bootline may coerece greater verbosity, details
            udev.log-priority=debug
            rd.udev.log-priority=debug

            #61193
            Member
            frtorres
              Helpful
              Up
              0
              ::

              Thanks @skidoo for your advice.

              I spent some time analyzing this issue.

              1. Both provided udev parameters seems to have some spelling error. I did not find them in this Antix boot parameters

              2. Tested load=all parameter as it seems was useful in similar situation, no success.

              3. It is a “weird” issue because using the same VM configuration (disk layout), I installed other linux distros and FreeBSD with no problems booting. From Linode forum they could not help me as this config works with other distros.

              4. At grub command prompt I found squashfs file at (hd0) and it is accessible.

              5. At boot time Finally I tested the breakpoint debugging boot parameter with these kernel boot parameters:

              load=all bp=3 verb=7

              Booted this latest iso (AntiX 19.4 64bit):

              The break point and a verbose level=7 showed the attached images. I understand hardware controllers are detected but no partition or disks are reported and detected in order to find:”squashfs” file with the compressed file system, so all ended up with the message:

              Fatal Error No block devices found

              6. Tested latest MX Linux ISO file (maybe another kernel?) but no changes and no success … it seems it has same base (grub, kernel, etc) for a xfce DE.

              I am at this point now, concluding by now, maybe this is a kernel issue / boot parameters. Is it possible to have another kernel to test?.

              I want to use Antix, because this VM at linode is US$5/month and has only 1Gb RAM +25Gb disk. I think Antix will fit well and will give me a remote desktop I can use while I travel.

              Thanks in advance for Antix community advice, comments or guidance in a proper direction.

              Thank you all

              Francisco.

              #61201
              Anonymous
                Helpful
                Up
                0
                ::

                Is it possible to have another kernel to test?

                .
                Yes —v

                https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/

                use the live-kernel-updater tool to change which kernel the live systems boots with. You need to first install the new kernel and do a remaster.

                .

                Tested latest MX Linux ISO file but no changes and no success

                FWIW, kernel(s) used in the MX ISO are different from those provided on the antiX -issued ISOs.

                As a separate matter, one detail common to both MX and antiX — and probably different from other distros you tried — is use of eudev in place of udev. Although their APIs should be essentially identical, the version of eudev in use by antiX//MX (also Devuan) may not be up-to-date with the version of udev used in the other distros you tried.

                Both provided udev parameters seems to have some spelling error. I did not find them in this Antix boot parameters

                Right, they are not exclusive-to-antiX boot parameters.

                udev.log-priority=
                is described in the udevd manpage

                UDEVD(8)                           udevd                                  UDEVD(8)
                
                NAME
                       udevd - Device event managing daemon
                
                SYNOPSIS
                       udevd
                
                       /sbin/udevd [--daemon] [--debug] [--children-max=] [--exec-delay=] [--event-timeout=]
                                   [--resolve-names=early|late|never] [--version] [--help]
                
                DESCRIPTION
                       udevd listens to kernel uevents. For every event, udevd executes matching instructions specified in udev rules.
                       See udev(7).
                
                       The behavior of the daemon can be configured using udev.conf(5), its command-line options, environment
                       variables, and on the kernel command-line, or changed dynamically with udevadm control.
                
                OPTIONS
                       -d, --daemon
                           Detach and run in the background.
                
                       -D, --debug
                           Print debug messages to standard error.
                
                       -c, --children-max=
                           Limit the number of events executed in parallel.
                
                       -e, --exec-delay=
                           Delay the execution of RUN instructions by the given number of seconds. This option might be useful when
                           debugging system crashes during coldplug caused by loading non-working kernel modules.
                
                       -t, --event-timeout=
                           Set the number of seconds to wait for events to finish. After this time the event will be terminated. The
                           default is 30 seconds.
                
                       -N, --resolve-names=
                           Specify when udevd should resolve names of users and groups. When set to early (the default), names will be
                           resolved when the rules are parsed. When set to late, names will be resolved for every event. When set to
                           never, names will never be resolved and all devices will be owned by root.
                
                       -h, --help
                
                KERNEL COMMAND LINE
                       Parameters starting with "rd." will be read when udevd is used in an initrd.
                
                       ____________________
                       ____________________
                       udev.log-priority=, rd.udev.log-priority=
                           Set the log level.
                
                       udev.children-max=, rd.udev.children-max=
                           Limit the number of events executed in parallel.
                
                       udev.exec-delay=, rd.udev.exec-delay=
                           Delay the execution of RUN instructions by the given number of seconds. This option might be useful when
                           debugging system crashes during coldplug caused by loading non-working kernel modules.
                
                       udev.event-timeout=, rd.udev.event-timeout=
                           Wait for events to finish up to the given number of seconds. This option might be useful if events are
                           terminated due to kernel drivers taking too long to initialize.
                
                       net.ifnames=
                           Network interfaces are renamed to give them predictable names when possible. It is enabled by default;
                           specifying 0 disables it.
                
                SEE ALSO
                       udev.conf(5), udev(7), udevadm(8)
                #65433
                Member
                frtorres
                  Helpful
                  Up
                  0
                  ::

                  Hi @Skidoo.

                  I just came to THANK YOU for your response. It was a matter of time and opportunity. I really think there is an space for Antix on those virtual machines around US$5 to have a remote desktop available.

                  I took note and with more time (now I am very busy in my current job), I will try this out.

                  Thanks again.

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