Search Results for 'boot from iso'

Forum Forums Search Search Results for 'boot from iso'

Viewing 15 results - 391 through 405 (of 1,574 total)
  • Author
    Search Results
  • Member
    TheBigBadBoy

      Big news !

      I fully installed (not an usb-live), antiX-21-FULL with kernel 5.10.57 on the same machine. This new installation works absolutely fine : taking about 6 seconds for the whole boot process, with defaults kernel params. (During the boot I saw “Waiting for /dev […]”, but it took only ~2 sec).

      So, first of all : I am really sorry to have bother you for a thing that, apparently, I broke myself. Once again, sorry.

      –> Then, the problem is not really the same (or the approach to solve it).
      What can I do to find what I broke in the antix taking 1 min 20 to boot ? Read differences of the ‘dmes’ output ?

      In the possibility to not be able to find the problem, how can I create an iso (containing all the customisation I have done : packages, appearance, theme, config files of navigator, …), and then reinstall that iso which will (I hope) boot in ~6 sec

      (As a side note, during the installation of antiX, I discovered that we can not install antiX-21 on some devices – for example a usb-stick 3.0 I have; while for another usb-stick 3.0 it worked directly like a charm. I’m sure the partitions were well set, since there were the same between the 2 usb. Also, I prefer installing antiX on an usb than an usb-live system, due to personal choice/taste.)

      #76526
      Member
      rcva

        Greetings all. Long time sysadmin dude here, but new to the antiX ecosystem. Learning and experimenting with Linux distros has been a passion of mine for years, especially USB based ones. Recently, I downloaded antiX for the first time. Got it installed easily and running as a Virtual Box vm on a 2015 MacBook.

        However, I’m having a problem using the USB Live feature. I can boot into the Live and it loads without error. I can get to the desktop manager. The problem is I have no touchpad or keyboard functionality whatsoever. If you’re seen this behavior I’d like to know how you resolved it. Thanks.

        What I’m running-
        -MacBook 2015, Core M, runs solid, no hw or os errors
        -High Sierra 10.13.6
        -antiX-21_x64-full.iso
        -Used balenaEtcher and flashed it to two different usb sticks. Same results with both, Live loads but no touchpad or keyboard functionality.

        What I’ve done so far-
        -Experimented with numerous MacOS bootup switches, hoping to change BIOS or UEFI touchpad and keyboard settings. Can’t find any that address my problem.
        -Tried a couple different kernel switches during the install, such as disable ACPI, and I’ve chosen different keyboards, etc.
        -Searched the forums
        -Searched the wikis

        What I’ll try next-
        A different iso.
        Continue searching the forums & wikis.
        Kernel options.
        Edit startup scripts.

        Member
        TheBigBadBoy

          I used AntiX-19 for 3 months, booting in 4~5 seconds.

          After a fresh installation of AntiX-21 (full version), using the “5.10.57-antix.1-amd64-smp” kernel, all my boots take quite long time : after the message “Waiting for /dev to be fully populated…”, my computer does not show anything else during 1 min 20 sec, and then finally boot.

          I tried to delete the boot parameter “quiet”. What can be found around the message :

          Using make-file style concurrent boot in runlevel S.
          Starting hot-plug events dispatcher: udevd
          [    4.295284] udevd[597]: starting version 3.2.11
          Synthesizing the initial hotplug events (subsystems)...done.
          Synthesizing the initial hotplug events (devices)...done.
          Waiting for /dev to be fully populated...
          [    4.325922] udevd[597]: starting eudev-3.2.11

          The only boot errors (from “dmesg”) are :

          [    4.438878] nvidiafb: unknown NV_ARCH
          [   69.920365] Bluetooth: hci0: HCI reset during shutdown failed
          [ 1098.426907] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

          Also, since this problem is propably due to some of my hardware :

          $ inxi -Fxz
          System:
            Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 
            Desktop: IceWM 2.9.5 Distro: antiX-21_x64-full Grup Yorum 31 October 2021 
            base: Debian GNU/Linux 11 (bullseye) 
          Machine:
            Type: Laptop System: MACHENIKE product: T58-V v: N/A serial: <filter> 
            Mobo: MACHENIKE model: NH55DP-HMx serial: <filter> UEFI: INSYDE 
            v: 1.07.04TQLM6 date: 01/14/2021 
          CPU:
            Info: 8-Core model: Intel Core i7-10870H bits: 64 type: MT MCP 
            arch: Comet Lake rev: 2 cache: L2: 16 MiB 
            flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
            bogomips: 70399 
            Speed: 4766 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 4766 2: 4741 
            3: 4757 4: 4758 5: 4781 6: 4789 7: 4841 8: 4789 9: 2907 10: 4719 11: 4701 
            12: 4667 13: 4805 14: 4763 15: 4778 16: 4707 
          Graphics:
            Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: CLEVO/KAPOK 
            driver: i915 v: kernel bus-ID: 00:02.0 
            Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] 
            vendor: CLEVO/KAPOK driver: N/A bus-ID: 01:00.0 
            Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:2 
            Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting 
            unloaded: fbdev,vesa resolution: 1920x1080~144Hz 
            OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 
            direct render: Yes 
          Audio:
            Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK 
            driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 
            Device-2: NVIDIA driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
            Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes 
          Network:
            Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel 
            port: 5000 bus-ID: 00:14.3 
            IF: wlan0 state: up mac: <filter> 
            Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
            vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 3000 bus-ID: 06:00.1 
            IF: eth0 state: down mac: <filter> 
          Bluetooth:
            Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 
            bus-ID: 1-14:3 
            Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: running 
            rfk-block: hardware: no software: yes address: <filter> 
          RAID:
            Hardware-1: Intel Device driver: ahci v: 3.0 bus-ID: 00:17.0 
          Drives:
            Local Storage: total: 1.94 TiB used: 157.61 GiB (8.0%) 
            ID-1: /dev/sda vendor: Western Digital model: WD20SPZX-22UA7T0 
            size: 1.82 TiB 
            ID-2: /dev/sdb type: USB vendor: JMicron Tech model: Generic 
            size: 119.24 GiB 
          Partition:
            ID-1: / size: 110.65 GiB used: 10.66 GiB (9.6%) fs: ext4 dev: /dev/sdb2 
            ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat dev: /dev/sdb1 
          Swap:
            ID-1: swap-1 type: partition size: 6 GiB used: 0 KiB (0.0%) dev: /dev/sdb3 
          Sensors:
            System Temperatures: cpu: 63.0 C mobo: N/A 
            Fan Speeds (RPM): N/A 
          Info:
            Processes: 289 Uptime: 9m Memory: 31.19 GiB used: 1.47 GiB (4.7%) 
            Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1566 
            Shell: Bash v: 5.1.4 inxi: 3.3.06

          Thank you for any time spent to try to help me, and don’t hesitate to ask me to do manipulation, or add information (then which ones ?).

          • This topic was modified 1 year, 3 months ago by TheBigBadBoy.
          • This topic was modified 1 year, 3 months ago by TheBigBadBoy.
          • This topic was modified 1 year, 3 months ago by christophe.
          #76442
          Member
          fladd

            Default theme medium size (literally right after booting the ISO):

            https://imgur.com/TuZRDlX

            • This reply was modified 1 year, 3 months ago by fladd.
            • This reply was modified 1 year, 3 months ago by fladd.
            #76262
            Forum Admin
            anticapitalista

              Seems like libelogind0 needs to be installed.

              qemu-system-x86_64 -enable-kvm -boot d -cdrom /home/anticap/Remaster/iso-files/antiX-19.5_x64-full.iso -m 1024
              qemu-system-x86_64: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory

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

              antiX with runit - leaner and meaner.

              #76259
              Anonymous

                The above assumes, of course, that the host is of adequate size to accommodate the virtual disk in /home.

                Example: Host(my operating system) = 50G
                virtual hard disk = 20G
                the create command is:
                qemu-img create -f qcow2 virtu.img 20G

                The data exchange after an installation I do between client and host e.g. in zzzFM:
                sftp://male@IP-of-the-host/
                The client needs openssh-client and the host additionally openssh-server.

                Maybe also interesting to do only the ISO test in Qemu:
                Example without (U)Efi:
                qemu-system-x86_64 -enable-kvm -k de -smp 2 -m 2048 -vga std -monitor stdio -snapshot -cdrom /media/Distris/antiX/antiX-21-runit_x64-base.iso -name runit -boot d

                Finally it is worth to have a look at QEMU in the package management of Debian.

                #76245
                Anonymous

                  I don’t have a computer with (U)efi hardware. Therefore, it was obvious to compensate for this shortcoming (which I do not regret in the least) with QEMU.

                  Installation command:
                  $ qemu-system-x86_64 -enable-kvm -m 4096 -bios /usr/share/OVMF/OVMF_CODE.fd -smp 2 -vga std -cdrom /media/Distris/antiX/antiX-21-runit_x64-base.iso -boot d -drive file=/home/male/virtu/platte.img,format=qcow2 -m 4G

                  Start command:

                  #!/bin/sh
                  qemu-system-x86_64      -enable-kvm \
                                          -bios /usr/share/ovmf/OVMF.fd \
                                          -m 4096 \
                                          -vga std \
                                          -hda /home/male/virtu/platte.img \
                                          -cpu host \
                                          -smp 2 \
                                          -soundhw all \
                                          -monitor stdio 
                  

                  And no, this does not take place on antiX as host. 😉 unstable-sid

                  #76219
                  Member
                  PPC

                    If this does work (as it seems it does), maybe this script could be addapted and added to Package Installer (along with a simple GUI for QEMU, there are some available).
                    A mini tutorial on how to use qemu (to launch .iso’s, to launch cd/dvd’s and install to a virtula disk) is available here: https://linux-tips.com/t/booting-from-an-iso-image-using-qemu/136

                    I got this error on the very last part of the script (on antiX 19.X 64bits, sysv):

                    [....] Starting DNS forwarder and DHCP server: dnsmasq
                    dnsmasq: failed to create listening socket for port 53: Address already in use
                     failed!
                    invoke-rc.d: initscript dnsmasq, action "start" failed.

                    P.

                    Edit:
                    I tried to test qemu by running antiX’s iso in VM. I only got this:

                    qemu-system-x86_64 -boot d -cdrom ~/antiX-21_386-full.iso -m 1024
                    VNC server running on ::1:5900

                    qemu-system-i386 -boot d -cdrom ~/antiX-21_386-full.iso -m 1024
                    Got me the same result.

                    qemu-system-x86_64    -boot d \
                                          -cdrom ~/antiX-21-b2-runit_x64-full.iso \
                                          -m 1024 \
                                          -curses

                    Shows, for a fraction of a second, a “seabios” text then switches to 800×600 empty screen and stops.

                    The terminal didn’t freeze, but nothing happened… Long ago I used to test iso’s with qemu this way… Am I missing something?

                    • This reply was modified 1 year, 3 months ago by PPC.
                    • This reply was modified 1 year, 3 months ago by PPC.
                    • This reply was modified 1 year, 3 months ago by PPC.
                    #76212
                    Anonymous

                      is it again just the USB stick in particular I’m using?

                      Naw, I’ve just led you down a bad path.
                      Back in 2014, the intended purpose xtra feature was to livepatch and test antiX liveboot ISOs during betatesting (inject select modified system files and immedietely test following reboot, rather than distribute a new ISO for each set of small incremental changes). As such, the mechanism apparently wasn’t intended to replace per-user files ( pathed under /home )

                      Have you tried tar-ing /home/demo stuff?

                      No, my experimentation involved only system files (pathed under /usr)
                      (a detail which I had forgotten when suggesting its use in 2019, and in this current, topic. Sigh, sorry.)

                      the init script overall has indeed undergone several changes, and including the copy_xtra() function

                      So (guessing) copy_xtra occurs too early in the init script ~~ later in the script, some other routine notices that /home/* exists and doesn’t attempt to (create and) repopulate it?

                      • This reply was modified 1 year, 2 months ago by Brian Masinick. Reason: From skidoo
                      #76187
                      Forum Admin
                      anticapitalista

                        anticapitalista asked: what if you install seatd and libseat1.

                        vlc and tor both working (did reboot) without any other changes.
                        This just tested on antiX21 Sysv init, should be same on the runit version.

                        Glad it is working. Thanks for the feedback.

                        Although I would like antiX to be not only systemd-free but also 100% elogind-free too (that is/will be how the iso files are/will be shipped), I do understand that it may not be possible/an option for all antiX users.

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

                        antiX with runit - leaner and meaner.

                        #75808
                        Member
                        PPC

                          On a personal note, I recently tried to make a comparison between antiX, with FT10 enabled, and one of the most used distros in the World, Ubuntu (in a virtual environment, nor bare metal). Here’s the honest result:
                          -Ubuntu used way over 1gig of RAM. antix run on little over 100mb of RAM. Ubuntu used a little big more CPU on idle
                          -Ubuntu’s search field, by default allows the user to search both apps and files. FT10’s menu search field only serchs applications. To search for files (by name or even a word inside a document) you have to click Seamonkey’s icon, on the toolbar.
                          -Ubuntu allows you to install packages in snap format (even forces that on you). antiX does not work with snaps, but you can install flatpaks (you do have to install the flatkpak package it self first, and add a repository) or appimages freely
                          -Ubuntu looks great and modern, with a nice work flow- FT10’s work flow, at least to me is great (if you are used to Windows or any major Linux distro, you have almost no learning curve for regular actions, like opening apps, switching betting apps, searching for apps, installing apps, using the web, e-mail, a calendar, etc. But Ubuntu deals much better with multi workspaces (antiX with FT10 works great too, you can switch workspaces with keybinding or using the scroll button on the desktop- I didn’t really implement workspaces on FT10 because probably most users comming from Windows get confused by that… I never really got used to using more than one workspace myself)
                          -On the applications: Ubuntu has a nice choice of default apps, includes LibreOffice, a Web browser, Thunderbird e-mail client, a nice file manager and nice and simple to use Calendar and to do list apps. antiX matchs those generic features: it come (the full version) with LibreOffice, firefox-esr and Seamonkey Internet Browsers, zzzfm as a fully feature, simple to use GUI (although antiX lacks, by default, a Trash can- you can add one to zzzfm manually, following an how-to available here in the forum), Seamonkey and Claws e-mail clients, Seamonkey calendar and todo list, and a simple calendar (completely unrelated with Seamonkey’s) that can displays daily events (but not set alarms or search for events- like you can in Ubuntu’s calendar – implementing the “search” feature is easy, and I even have a calendar script that does set alarms, I just did not include it in FT10 because Seamonkey’s calendar is way better).
                          – By default, Ubuntu comes with visual effects turned on- they look great but use system resources. Se my previous post on how to toggle on some very nice looking visual effects on antiX with FT10.
                          – Installing new applications – Ubuntu comes with a very nice looking Application Store, almost like most people are used to in mobile devices (and, more recently on Windows too). antiX comes with Package Installer – it’s basically a simple app store, that does not show any images (not even the app’s icons) but allows you to search for and install over 100 of the most used apps (it has a huge Browser section, allows you to install localization packs, the latest LibreOffice and Gimp versions, Java, Steam, etc). For all other applications you can install them with Synaptic – one of the best GUI package installed ever devised by any Sentient Being – it gets some getting used to- but it explains everything to you (what dependencies you will have to install, how big will the download be, how much disk space will the packages use). On both systems you can install any application you want without ever needing to use the terminal.
                          -antiX does not, by default check automatically for updates. You can click the “antix updater” icon on the toolbar to check for updates (you do not have to use the terminal). You can install, from the Package Installer, an application that checks automatically for updates (but you’ll have to make a small edit to a system file to be make it start automatically every time you boot)
                          – Ubuntu has some great looking Wallpapers- antiX as a few, but also very nice ones- you can download any image you want and easily set it as your wallpaper (that a possibility in any OS, ops, except for “free” Windows 10 and 11 users…). Changing wallpapers is more intuitive in Ubuntu (just click the wallpaper and choose the option to change it). In antiX you have to do it via the Control Center.

                          All that taken in consideration, antiX with FT10 (and Visual Effects activated) feels in now way inferior to what is (still) the de facto standard of desktop Linux distros, and using less than 10% of it’s system resource, making it able to run effortlessly even in ancient hardware …

                          P.

                          • This reply was modified 1 year, 3 months ago by PPC.
                          #75679
                          Anonymous

                            If you boot the live iso of of antiX and from a terminal run

                            sudo e2fsck -c /dev/sda1

                            it will check linux partitions for bad blocks. Change sda1 to which partition
                            name your drive has to check for example…. mmcblk0p3

                            If the drive is not mounted you can run this to check the entire drive for bad blocks.
                            Warning if a drive has a filesystem on it … add -n as well. On a blank drive you can add -w
                            for a more thorough but data destructive read-write test.
                            Change sda to your drives name ….. mmcblk0

                            sudo badblocks -v /dev/sda

                            #75635
                            Member
                            melodie

                              Known issue (by me) and a new build was sent to our repo admin/manager yesterday.
                              Should appear in the repos soon.

                              Hello, still using non backports repos, now iso-snapshot-antix does not show anymore in the packages to be updated (which is fine by me for now), however I still can’t reinstall live-usb-maker-gui-antix. Maybe tomorrow?

                              Anyway now we can use Ventoy to create bootable USB devices : https://ventoy.net : it works great!

                              #75581
                              Member
                              ctcx

                                Hello.

                                Though relatively still short time here, I have been using AntiX for a while already, and learning a lot -and still keep learning-. I’m grateful for all this.

                                However, I think I really need to complain about a particular issue: the username I use here seemed to be completely deleted with no warning, and being replaced by a user called “Anonymous”. I had to register again.

                                Some of my previous threads:
                                https://www.antixforum.com/forums/topic/cannot-mount-internal-ntfs-partitions-only-as-root/
                                https://www.antixforum.com/forums/topic/cannot-mount-internal-ntfs-partitions-only-as-root/
                                https://www.antixforum.com/forums/topic/usb-stick-takes-too-long-to-be-recognized/
                                https://www.antixforum.com/forums/topic/alsa-and-32bit-game/
                                https://www.antixforum.com/forums/topic/booting-antix-with-multiboot-usb/
                                https://www.antixforum.com/forums/topic/mounting-iso-files-on-antix/
                                https://www.antixforum.com/forums/topic/connman-status-ready-or-online/
                                https://www.antixforum.com/forums/topic/general-problem-with-less-commercial-popular-web-browsers/
                                https://www.antixforum.com/forums/topic/small-doubt-about-packages-in-antix-releases/

                                So, with all due respect, what the heck happened? Did I break some rule? Or something?

                                #75498
                                Member
                                roland

                                  I downloaded Mint 19.2 64/bit Iso, removed all partitions from the HD, the Iso will not boot but produces the diagnostics below.

                                  TPM error 378 occurred get TPM pcr allocation
                                  couldn’t get size 0xB0000000000000000e
                                  Modsign Couldn’t get UEFI dg list
                                  Busybox v1.27.2 ubuntu 1.27.2ubuntu3.2 built/in shell ash
                                  intramfs Unable to find a medium containing a live file system

                                  It offers a table of commands available but none looked useful to me.

                                  One of the reasons I abandoned Mint quite some years ago was difficulty I had booting and installing it, but antiX never fails.

                                  I have no Windows of any release or version available to try, unless I can scrounge one from my daughter’s university. I have my doubts that Windows can offer a way out of this impasse.

                                  There remains to try the suggestion to try to format root as ext3 and not ext4, which I shall try now.

                                  I do not know of any utility that can run a sanity check on a hard drive on a block by block basis. Is there one available to antiX? When such block I O errors occur there are usually explicit diagnostics which would confirm a faulty drive or clear it?

                                  • This reply was modified 1 year, 3 months ago by roland.
                                  • This reply was modified 1 year, 3 months ago by roland.
                                Viewing 15 results - 391 through 405 (of 1,574 total)