-
Search Results
-
In reply to: Does antiX run on newer AMD type computers.
ex_Koo
Will so far after installing the Asus modules https://github.com/electrified/asus-wmi-sensors this system is fully operational.
Linux antix21a 5.8.16-antix.1-amd64-smp #1 SMP PREEMPT Tue Oct 20 01:48:36 EEST 2020 x86_64 GNU/Linux$ lspci -nnk | grep -i -EA3 "3d|display|vga" 01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01) Subsystem: ASMedia Technology Inc. 400 Series Chipset USB 3.1 XHCI Controller [1b21:1142] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci -- 08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) Subsystem: Sapphire Technology Limited Radeon RX 5600 XT [1da2:e411] Kernel driver in use: amdgpu Kernel modules: amdgpukoo@antix21a:~ $ ls /sys/class/hwmon/; cat /sys/class/hwmon/*/name hwmon0 hwmon1 hwmon2 hwmon3 k10temp asus amdgpu asuswmisensors ---------------------------------------- koo@antix21a:~ $ for m in /sys/class/hwmon/* ; do echo -n "$m = " ; cat $m/name ; done /sys/class/hwmon/hwmon0 = k10temp /sys/class/hwmon/hwmon1 = asus /sys/class/hwmon/hwmon2 = amdgpu /sys/class/hwmon/hwmon3 = asuswmisensors$ sensors amdgpu-pci-0800 Adapter: PCI adapter vddgfx: 775.00 mV fan1: 0 RPM (min = 0 RPM, max = 3200 RPM) edge: +44.0°C (crit = +118.0°C, hyst = -273.1°C) (emerg = +99.0°C) junction: +44.0°C (crit = +99.0°C, hyst = -273.1°C) (emerg = +99.0°C) mem: +44.0°C (crit = +99.0°C, hyst = -273.1°C) (emerg = +99.0°C) power1: 8.00 W (cap = 135.00 W) k10temp-pci-00c3 Adapter: PCI adapter Vcore: 1.43 V Vsoc: 1.05 V Tctl: +41.6°C Tdie: +41.6°C Tccd1: +41.5°C Icore: 13.00 A Isoc: 3.50 A asuswmisensors-isa-0000 Adapter: ISA adapter CPU Core Voltage: 174.00 mV VPP MEM Voltage: 2.50 V +12V Voltage: 10.19 V +5V Voltage: 5.01 V 3VSB Voltage: 3.33 V VBAT Voltage: 3.23 V AVCC3 Voltage: 3.33 V SB 1.05V Voltage: 1.07 V CPU Core Voltage: 199.00 mV CPU SOC Voltage: 1.05 V CPU Fan: 753 RPM Chassis Fan 1: 967 RPM AIO Pump: 2051 RPM CPU OPT: 0 RPM CPU Temperature: +41.0°C CPU Socket Temperature: +37.0°C Motherboard Temperature: +39.0°C Chipset Temperature: +53.0°C Tsensor 1 Temperature: +216.0°C CPU VRM Temperature: +39.0°C CPU VRM Output Current: 0.00 ASystem: Host: antix21a Kernel: 5.8.16-antix.1-amd64-smp x86_64 bits: 64 compiler: N/A parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.16-antix.1-amd64-smp root=UUID=82593f8f-dfc1-43bd-8402-ff0a99626493 ro quiet Desktop: i3 4.19 info: i3bar dm: SLiM 1.3.6 Distro: antiX-bullseye-a1_x64-full Grup Yorum 3 January 2021 base: Debian GNU/Linux bullseye/sid Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx serial: <filter> UEFI: American Megatrends v: 4204 date: 01/28/2021 Memory: RAM: total: 15.62 GiB used: 809.8 MiB (5.1%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 L2 cache: 3072 KiB bogomips: 86398 Speed: 2200 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2200 2: 2199 3: 2205 4: 2193 5: 2199 6: 2198 7: 2199 8: 2200 9: 2199 10: 2200 11: 2199 12: 2200 Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sev sha_ni skinit smap smca sme smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip v_vmsave_vmload vgif vmcb_clean vme vmmcall wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown 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: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Sapphire Limited driver: amdgpu v: kernel bus ID: 08:00.0 chip ID: 1002:731f Display: x11 server: X.Org 1.20.10 driver: amdgpu unloaded: fbdev compositor: compton v: 1 resolution: 2560x1440~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 5.8.16-antix.1-amd64-smp LLVM 11.0.1) v: 4.6 Mesa 20.3.4 direct render: Yes Audio: Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 1002:ab38 Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0a:00.4 chip ID: 1022:1487 Device-3: TEAC US-2x2 type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-1:2 chip ID: 0644:8045 Sound Server: ALSA v: k5.8.16-antix.1-amd64-smp Network: Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k port: d000 bus ID: 03:00.0 chip ID: 8086:1539 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: ASUSTeK driver: rtw_8822be v: N/A port: c000 bus ID: 04:00.0 chip ID: 10ec:b822 IF: wlan0 state: down mac: <filter> WAN IP: <filter> Drives: Local Storage: total: 465.76 GiB used: 8.67 GiB (1.9%) ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT Message: No Optical or Floppy data was found. RAID: Message: No RAID data was found. Partition: ID-1: / raw size: 24.61 GiB size: 24.09 GiB (97.92%) used: 5.88 GiB (24.4%) fs: ext4 dev: /dev/sda6 label: rootantiX19 uuid: 82593f8f-dfc1-43bd-8402-ff0a99626493 ID-2: /boot/efi raw size: 100.0 MiB size: 96.0 MiB (96.00%) used: 31.0 MiB (32.3%) fs: vfat dev: /dev/sda2 label: N/A uuid: E463-F5AD ID-3: /home raw size: 96.01 GiB size: 94.00 GiB (97.91%) used: 2.76 GiB (2.9%) fs: ext4 dev: /dev/sda7 label: homeantiX uuid: 131a68bf-e32b-4404-8bf6-2bdaae384678 ID-4: swap-1 size: 16.17 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) cache pressure: 50 (default 100) dev: /dev/sda10 label: N/A uuid: da707172-2f9e-4092-8c00-ae2100abc6d8 Unmounted: ID-1: /dev/sda1 size: 300.0 MiB fs: ntfs label: Recovery uuid: EA26632C2662F949 ID-2: /dev/sda3 size: 128.0 MiB fs: <root required> label: N/A uuid: N/A ID-3: /dev/sda4 size: 132.27 GiB fs: ntfs label: N/A uuid: 306C18586C181AE4 ID-4: /dev/sda5 size: 517.0 MiB fs: ntfs label: N/A uuid: 84664A41664A3468 ID-5: /dev/sda8 size: 59.32 GiB fs: ext4 label: rootMX19 uuid: daa56471-769f-464c-9397-f3e47110ad52 ID-6: /dev/sda9 size: 136.37 GiB fs: ext4 label: homeMX uuid: bf25c21e-978e-483a-8fff-098d7f2d8234 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Device-1: 1-1:2 info: TEAC US-2x2 type: Audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 5 rev: 2.0 speed: 480 Mb/s chip ID: 0644:8045 Device-2: 1-6:3 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 0b05:1872 serial: <filter> Device-3: 1-8:4 info: ASUSTek Bluetooth Radio type: Bluetooth driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s chip ID: 0b05:185c serial: <filter> Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Device-4: 3-1:2 info: Razer USA DeathAdder Chroma type: Mouse,HID,Keyboard driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s chip ID: 1532:0043 Device-5: 3-2:3 info: Logitech Pro Gaming Keyboard type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s chip ID: 046d:c339 serial: <filter> Device-6: 3-3:4 info: Brother Industries HL-L2350DW series type: Printer driver: usblp interfaces: 2 rev: 2.0 speed: 480 Mb/s chip ID: 04f9:009e serial: <filter> Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 46.1 C mobo: 40.0 C gpu: amdgpu temp: 44 C Fan Speeds (RPM): cpu: 707 case-1: 1016 gpu: amdgpu fan: 0 Voltages: 12v: 10.14 5v: N/A 3.3v: N/A vbat: 3.25 Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb https: //mirrors.evowise.com/mxlinux-packages/antix// testing main nosystemd nonfree Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http: //deb.debian.org/debian/ bullseye main contrib non-free No active apt repos in: /etc/apt/sources.list.d/various.list Processes: CPU top: 5 1: cpu: 7.3% command: firefox-esr pid: 4483 mem: 358.9 MiB (2.2%) 2: cpu: 2.7% command: xorg pid: 2099 mem: 121.6 MiB (0.7%) 3: cpu: 0.7% command: firefox-esr pid: 4623 mem: 204.2 MiB (1.2%) 4: cpu: 0.4% command: gtkdialog pid: 7664 mem: 26.9 MiB (0.1%) 5: cpu: 0.2% command: conky pid: 2447 mem: 15.7 MiB (0.0%) Memory top: 5 1: mem: 358.9 MiB (2.2%) command: firefox-esr pid: 4483 cpu: 7.3% 2: mem: 204.2 MiB (1.2%) command: firefox-esr pid: 4623 cpu: 0.7% 3: mem: 121.6 MiB (0.7%) command: xorg pid: 2099 cpu: 2.7% 4: mem: 90.4 MiB (0.5%) command: firefox-esr pid: 7196 cpu: 0.0% 5: mem: 34.7 MiB (0.2%) command: i3 pid: 2388 cpu: 0.0% Info: Processes: 278 Uptime: 21m Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.0.36- This reply was modified 2 years, 3 months ago by ex_Koo.
In reply to: New Antix user running on Mac Mini 2008
Xecure
Welcome, Crashed Disk, to this small community for such a great distro.
The three things I now need to do are:
Be able to backup files to Nas drive
Install my HP Deskjet all in one printer to be able to print
Attempt to save live system to USB1. “Be able to backup files to Nas drive”. You could try Conectshares application (http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/connectshares.html). You can search the forum for some examples and troubleshooting.
2. “Install my HP Deskjet all in one printer to be able to print”. There are a few threads in the forum about HP drivers. Make sure you are running antiX 19 full or, if running base, to install all needed cups packages and printer config programs.
3. “Attempt to save live system to USB”. Many articles related to this, here, in the FAQ, in the antixlinux.com site and in the wiki.
If you don’t mind deleting all the USB content to use it as live USB, boot antiX with “toram” parameter, wait for it to boot completely, use the Live USB maker tool (Control Centre > Disks > “Live USB Maker (gui)”) to clone the live system to a USB. Then, on the next reboot, in the bootscreen select any of the persistence options available (for example. persist_root) so that all your changes are stored in the live USB at the end of each session (or whenever you run the program to save persistent changes).
Also, any change you do on the live session will be kept when you finally decie to install it on your system.antiX has lots of tools and options for running live, save live changes, remaster all changes to one file, convert a running live (or even an installed system) to a ISO file which you can later use to reinstall the system or run live on other machines, etc., etc.
Too much to write in one post.
Welcome and enjoy the ride!
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
Texto traduzido:
Como o antiX tenta dar suporte a computadores antigos, ele vem por padrão com uma versão do kernel Linux anterior ao Debian e outras distros Linux. Isso leva a alguns problemas ao inicializar máquinas mais novas com a edição padrão do antiX.Para resolver esse problema, a equipe de desenvolvimento também lançou uma edição do antiX com uma versão mais recente do kernel (4.19). Você pode baixá-lo aqui:
http://sft.if.usp.br/mx-linux/ANTIX/Final/antiX-19/4.19_kernel/Se a máquina for muito, muito nova (como CPUs Intel de 10ª geração), eles precisam de uma versão de kernel ainda mais recente. Eu construí um ISO antiX não oficial com o kernel 5.8 mais recente fornecido pela equipe de desenvolvimento do antiX aqui, mas não o use a menos que você não consiga inicializar a versão 4.19.
——————————————————-
Original text:
As antiX tries to give support to old computers, it comes by default by a Linux kernel version older than Debian and other Linux Distros. This leads to some trouble booting newer machines with the default antiX edition.To solve this problem, the dev team also released a antiX edition with a newer kernel version (4.19). You can download it here:
https://sourceforge.net/projects/antix-linux/files/Final/antiX-19/4.19_kernel/If the machine is very very new (like Intel 10th generation CPUs), they need an even newer kernel version. I built a non-official antiX ISO with the newer 5.8 kernel provided by the antiX dev team here, but don’t use it unless you cannot get the 4.19 version to boot.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.In reply to: [Solved]: ISO Snapshot of a live system?
redrooster
Hello all,
yes upgrading the iso-snapshot-antix and iso-template-antix packages as described in the link above given by anticapitalista solves the problem. My mistake and a good reminder to read the release notes before using a new system. Anyway staying true to the antiX philosophy i never intended to install antiX on any of my machines but use it as a live usb system.
Out of curiosity using the usb live maker made a running system out of the snapshot with the blank exclusions file and it worked fine. Boots and runs successfully.
Again thanks to all for your help and forgive me for wasting your valuable time.
In reply to: [Solved]: ISO Snapshot of a live system?
Anonymous
In order to fix it i had to upgrade the iso-template-antix package with the commands in terminal and actually create an empty file named iso-snapshot-exclude.list in the above mentioned directory.
Ouch!
Given a blank “excludes” list, I’m half surprised that the operation was able to complete.
The exclusions are necessary. Without ’em, I would not trust the resulting product to boot/run successfully. IMO, you should discard that iso you created while a blank exclusions file was present.Failing all else, you can retrieve the expected default content of the excludes file here:
https://gitlab.com/antiX-Linux/iso-snapshot-antix/-/raw/master/iso-snapshot-exclude.listIn reply to: [Solved]: ISO Snapshot of a live system?
Xecure
Can I do an ISO Snapshot of a remastered antiX live system without having to install it?
It will give you the option of including your user information, so the image will be almost identical to the running system (except removing some specific machine configurations, so you can boot the ISO form any/all other computer).
It is even able to snapshot a Live system with any modifications (even if they are not saved in persistence).antiX Live system enthusiast.
General Live Boot Parameters for antiX.In reply to: [Solved]: ISO Snapshot of a live system?
ModdIt
Hi redrooster, Below should work, I do not know a practical tool with gui.
To make an ISO from your stick and create a file named “bootableusb.iso” Example in your current working directory.
$ sudo dd if=/dev/sdc of=bootableusb.iso
Replace c in device path with your own drive letterAfter your iso is created you will also have to do
$ sudo chown $USER:$USER bootableusb.iso
as the iso image will be owned by root due sudo usage.In reply to: Backup ISO creation
snapshot is NOT a backup app
.
.
.
.in order to restore, you are typically required to…
but
if you have a snapshot iso at hand, you can
(if necessary, attach the removable device on which the iso file resides, and)
click, or double-click the iso file in spaceFM.
A mountpoint is automatically created, iso is mounted, and in your spaceFM tab you’re now browsing the toplevel directory within the iso. You can freely select and copy (or drag) any files you wish to “restore” onto the running system.a similar trick:
during a dynamic root persistence session
(and/or from an installed system, peeking an antiX liveboot device)
we can retrieve — from rootfs (and/or or linuxfs) file — copies of recently deleted files.man dfh man show-isomount man clean-isomount man isomount man isoumount man sqmount man squmount /usr/local/bin/clean-isomount /usr/local/bin/dfh /usr/local/bin/dfh-watch /usr/local/bin/isoumount /usr/local/bin/show-isomount /usr/local/bin/sqmount /usr/local/bin/squmount /usr/local/bin/usbmount /usr/local/bin/usbumountedited to clarify:
useful for selective recovery of known deleted files
(not for a bulk restore of the entire running system)In reply to: Backup ISO creation
persistenceofvision
Thank you to all for your responses. I was able to successfully create the bootable ISO snapshot. The only issue was after creating it i decided to create or attempt to create a dual boot laptop with Windows 10 and antiX. I installed Windows 10 but made sure to leave some room for antiX. After wiping the hard drive and installing windows, I then booted the snapshot off my usb flash drive and using the cli-installer attempted to install the snapshot and also partition the space i left when i installed windows 10.
i have no experience doing a dual boot creation or even trying to restore the snapshot so it was a tremendous disaster, just as i expected it would. the laptop ended up just booting into windows not giving me a choice of operating systems. When i install antiX I let the auto installer create the necessary partitions because when i try to do it manually I create the primary and the swap but seem to forget to do something right. I do make the primary bootable. I also try to create a separate partition for home too.
I decided to forget the dual boot and just go with antiX but you never know when you need a windows pc or laptop so i kind of wish i knew what i was doing and that it had worked. I don’t even know what mistake i made so it wasn’t even a learning experience. I’m just going to steer clear of creating dual boots.
i reinstalled antiX alone and now i’m trying to figure out how to restore the snapshot which did save kodi. i didn’t open it yet to see if my settings are all saved but the program is there. if you happen to know how to restore a snapshot I’m all ears! thank you!
- This reply was modified 2 years, 3 months ago by persistenceofvision.
- This reply was modified 2 years, 3 months ago by persistenceofvision.
Domarius
All the guides I can find seem to be written in a way that getting antiX installed is elementary, so I’m not sure what’s wrong.
I downloaded http://mirror.datamossa.io/mxlinux-iso/ANTIX/Final/antiX-19/antiX-19.3_x64-full.iso , I understand this to be the full version, 64bit. Wrote it to USB with Etcher.
It booted fine, I chose the default option, then chose the first option for video device. Pressed Enter to continue.
Then it got stuck on the loading screen for ages where it says “ALT+F1 for load details” and “ALT+F10 to return here”. When I pressed ALT+F1 it was asking for a login.
I rebooted and got the same result, so looking at the instructions on screen, I logged in as root, and then ran the command line install. I got passed the questions OK but when it started to write it spammed a “input/output error, Retrying” message over and over.
If this isn’t sufficient info, let me know, I’ll run it again and take photos of the screen at key points.
In reply to: Backup ISO creation
olsztyn
Yes. It will make a bootable ISO of your current installed system. It will give you the option of including your user information, so the image will be almost identical to the running system (except removing some specific machine configurations, so you can boot the ISO form any/all other computer).
It is even able to snapshot a Live system with any modificationsTo add to this excellent overview:
ISO-Snapshot is brilliant in it’s function and unique in Linux world. To my knowledge it is specific to antiX (and to some degree to MX) and not available to any other Linux distro. Nothing else comes close to it in functionality and it is puzzling that other distros can get by without it. Apparently users of other distros are not serious enough about their distros to appreciate such capability of precise backup image of their system.
Their ultimate objective (late in the game as it is) should be a project to retrofit ISO-Snapshot into their distros to add such important function. However nothing like this is being done that I heard of.
This fact alone gives antiX (perhaps to some degree MX too) a significant advantage not yet widely appreciated.
Just my two cents in addition to Xecure’s overview…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersIn reply to: Backup ISO creation
Xecure
I was wondering if the ISO snapshot includes all apps installed at the time of the backup?
Yes. It will make a bootable ISO of your current installed system. It will give you the option of including your user information, so the image will be almost identical to the running system (except removing some specific machine configurations, so you can boot the ISO form any/all other computer).
It is even able to snapshot a Live system with any modifications (even if they are not saved in persistence).The best procedure for you is to try it and see the result. Create a snapshot (with xz compression, so it results in a smaller ISO file) and then run it on a V or create a Live-USB with the snapshot ISO. Test it out and verify it yourself.
Don’t trust me, trust the results.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.In reply to: antiX-bullseye-a1-x64-bullseye-full available
Memory on boot desktop only about 200/250 more memory than 19.2.1
Are you comparing the default antiX system?
This is a table comparing memory use after boot to desktop, in Live ISO on Virtual Box.
https://docs.google.com/spreadsheets/d/1fd7XHQxH0y-R0jEV9s7Ou_qQeRUHUwZjh0F9fOf2o_g/edit?usp=sharingROX+Icewm (ISO) conky htop ps_mem.py Total running services: antix 19.2 FULL x64 (1050p) 171 174 208 24 antix 19.3 FULL x64 148 144 152,9 24 antix bullseye alpha FULL x64 140 136 155,3 22 Live on VBox with boot code quiet splasht disable=lxFBarely anything has changed from 19.3 FULL to 21alpha. Remember, you need to compare with the FULL release, and not with the BASE release (which has less number of programs and even less amount of services running at boot).
If you are comparing systems after installing your own packages, then you need to see what is going on with your installed programs (or compare the running services), as antiX has nothing to do with it.[/quote]
Thanks for the info I can only compare with the programs install sorry, as they are the same as I use all the time with 19.2.1 with maybe a few different versions. The only service program installed would be mpd the rest should not be running at all on bootup. Or their may be memory leak? As for full and base 19.2.1 is base if this is the differences in memory usage from full to base can’t for antiX21 base then.
I’m not going to reinstall I have put to much work into this and really like 21a.
You have all done an awesome job with 21a. And I’m sure not complaining.. Plus I have 16gb of memory whats a couple of hundred meg anyway. Its all good.In reply to: antiX-bullseye-a1-x64-bullseye-full available
Xecure
Install papirus-antix and remove papirus-mini-antix.
I’ll make some changes to papirus-mini-antix so the correct icon size is used.Thanks, anticapitalista. This is just a cosmetic problem and doesn’t really need your attention. This is not an important issue but I thank you for your attention to detail.
Memory on boot desktop only about 200/250 more memory than 19.2.1
Are you comparing the default antiX system?
This is a table comparing memory use after boot to desktop, in Live ISO on Virtual Box.
https://docs.google.com/spreadsheets/d/1fd7XHQxH0y-R0jEV9s7Ou_qQeRUHUwZjh0F9fOf2o_g/edit?usp=sharingROX+Icewm (ISO) conky htop ps_mem.py Total running services: antix 19.2 FULL x64 (1050p) 171 174 208 24 antix 19.3 FULL x64 148 144 152,9 24 antix bullseye alpha FULL x64 140 136 155,3 22 Live on VBox with boot code quiet splasht disable=lxFBarely anything has changed from 19.3 FULL to 21alpha. Remember, you need to compare with the FULL release, and not with the BASE release (which has less number of programs and even less amount of services running at boot).
If you are comparing systems after installing your own packages, then you need to see what is going on with your installed programs (or compare the running services), as antiX has nothing to do with it.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.In reply to: Internationalisation of antiX community scripts
I mentioned in another post recently:
skidoo is confused by the fact that
screenshot from the antiX21alpha boot menu shows 62 LANG entries (+1 for Default)
vs
this list shows only 61 total https://gitlab.com/antiX-Linux/antiX-Gfxboot/-/blob/master/Input/common/isolinux/languagesHere, I’m also wondering:
When maintaining antiX translations, do you (all, collectively) just drop//discard//ignore fr_FR
???
fr_FR
fr_BE
fr_CA
fr_CH
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
