antiX NET expected behavior?

  • This topic has 2 replies, 2 voices, and was last updated Jun 23-5:21 pm by PDP-8.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #37935
    Member
    PDP-8

      Ok, so NET is not meant to be a production environment, but thought I’d check it out anyway..

      Burnt the 19.2 64 bit live on a bootable stick and noticed some things as compared to my working CORE and BASE 19.2 64 bit working installs / persistent sticks …

      1) Despite the absolutely gorgeous splash and simpler text-based boot options where I can choose my screen-font character length, and other options, when all is booted, it just drops to very teeny fonts on my 1980×1020 screen. Very much unlike my CORE and BASE setups. I just want to check that this is indeed the expected behavior to build on, or is it a simple grub edit kind of thing to get fonts back to liking for size? It’s looking like it, but wanted to check.

      2) On my 64 bit AMD box, that gorgeous splash has the menu system from what appears to be the 32-bit F1/F2/F3/F4….. options at the bottom, instead of answering a sequence of questions. Didn’t expect that – something may be up with my supposed 64 bit box looking like 32 bit at the first stage of boot!

      Unfortunately, on my AMD box only, it hangs at
      ..waiting for /dev to be fully populated…

      So I’ve got some homework to do since it doesn’t act like core and base do.

      Even so, NET is really nice. Not production for some, but I could probably live inside it! 🙂

      #37937
      Member
      Xecure
        Helpful
        Up
        0
        ::

        Ok, so NET is not meant to be a production environment

        If I am not mistake, net is the same as core but without firmware. Only meant for installs with a ethernet cable (no wifi support).

        1) Despite the absolutely gorgeous splash and simpler text-based boot options where I can choose my screen-font character length, and other options, when all is booted, it just drops to very teeny fonts on my 1980×1020 screen. Very much unlike my CORE and BASE setups. I just want to check that this is indeed the expected behavior to build on, or is it a simple grub edit kind of thing to get fonts back to liking for size? It’s looking like it, but wanted to check.

        If you want the text to be bigger, then select the correct option in the tty font size.

        2) On my 64 bit AMD box, that gorgeous splash has the menu system from what appears to be the 32-bit F1/F2/F3/F4….. options at the bottom, instead of answering a sequence of questions. Didn’t expect that – something may be up with my supposed 64 bit box looking like 32 bit at the first stage of boot!

        This has nothing to do with 32 and 64 bits, but with UEFI and LEGACY BIOS. As I mentioned in a very recent post, the boot screen in antiX is not unified. It is very nice in LEGACY BIOS mode, but it is a cascading menu of text options in UEFI systems. In the future, UEFI will be the only option, so a better boot screen should be creates, as it concerns antiX and MX Linux’s future.

        Unfortunately, on my AMD box only, it hangs at
        ..waiting for /dev to be fully populated…

        You may need to use the antiX version with 4.19 kernel, as some new hardware cannot boot with the default antiX edition with 4.9 kernel.

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

        #37972
        Member
        PDP-8
          Helpful
          Up
          0
          ::

          Xecure – thanks for the info, explains much.

          I run antiX on modern hardware, so the ones I like the most either come as UEFI-ONLY with no other choise, or I force them to be that way given the option. I actually prefer that to csm.

          Menu-issue solved! That explains it – one box tries to stay hybrid no matter what, so when I break the normal boot process to get a stick up, I have two options:

          boot:
          Sandisk Flash disk
          UEFI: Sandisk Flash disk

          And depending on which I choose, the antiX menus change accordingly. I gotta work on a way to force that box to be uefi only.

          Man, that’s gotta’ be a dev’s nightmare. 🙂

          Using Intel NUCS, and some other cheaper boxes to test with, so I’m always on the lookout for PEBCAK’s on my end.

          Thanks for the pointers – I’ll play with NET some more, although it is just a matter of interest for me, not a real problem. Of course did the usual with md5sum checking, and using the built-in tool to antiX to create the drive in the first place. Awesome work.

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