- This topic has 709 replies, 38 voices, and was last updated Jan 30-4:02 pm by Brian Masinick.
-
Posts
-
Brian Masinick
https://www.antixforum.com/forums/topic/what-are-you-here-with-today/page/379/#post-192998
getting Beta 2 running on other systems.--
Brian Masinick
Alternate "Search B":
This search pageBrian Masinick
I finally made it here with a system capable of running the 5.10 kernel, and I even took the chance to try dinit FIRST with it, and it’s a success. This is my Lenovo Thinkpad X201, one of two systems I have that can run a V5 kernel; the other is my Dell Inspiron 5558, which I am positive is able to run this same image.
Good day of testing; I got to multiple hardware systems and I also built two ISO snapshots, one for 23.2 updates and the other for Beta 2; both of those worked too.
ps ax | head -2;sudo ps_mem.py ;inxi -zv4 PID TTY STAT TIME COMMAND 1 ? S 0:00 /sbin/init Private + Shared = RAM used Program 152.0 KiB + 51.5 KiB = 203.5 KiB seatd 296.0 KiB + 114.5 KiB = 410.5 KiB dbus-launch 300.0 KiB + 214.5 KiB = 514.5 KiB startup 360.0 KiB + 243.5 KiB = 603.5 KiB udevil 356.0 KiB + 381.5 KiB = 737.5 KiB icewm-session 676.0 KiB + 359.5 KiB = 1.0 MiB devmon 752.0 KiB + 366.5 KiB = 1.1 MiB init 868.0 KiB + 375.5 KiB = 1.2 MiB desktop-session 908.0 KiB + 568.0 KiB = 1.4 MiB agetty (6) 1.0 MiB + 637.5 KiB = 1.6 MiB dbus-daemon (3) 928.0 KiB + 762.5 KiB = 1.7 MiB at-spi-bus-launcher 972.0 KiB + 730.5 KiB = 1.7 MiB at-spi2-registryd 1.5 MiB + 753.5 KiB = 2.3 MiB pipewire-pulse 2.4 MiB + 408.5 KiB = 2.8 MiB bash 2.1 MiB + 810.5 KiB = 2.9 MiB conky 952.0 KiB + 2.1 MiB = 3.0 MiB sudo (2) 3.5 MiB + 39.5 KiB = 3.6 MiB udevd 3.8 MiB + 405.5 KiB = 4.2 MiB connmand 1.4 MiB + 3.0 MiB = 4.4 MiB dhcpcd (5) 3.2 MiB + 1.3 MiB = 4.6 MiB pipewire 4.4 MiB + 1.5 MiB = 5.9 MiB slimski 5.7 MiB + 1.7 MiB = 7.3 MiB wpa_supplicant 5.8 MiB + 2.6 MiB = 8.3 MiB icewm 5.2 MiB + 4.1 MiB = 9.3 MiB volumeicon 10.0 MiB + 1.8 MiB = 11.9 MiB wireplumber 9.0 MiB + 3.8 MiB = 12.8 MiB zzzfm 10.0 MiB + 4.7 MiB = 14.7 MiB roxterm 87.1 MiB + 1.3 MiB = 88.4 MiB Xorg --------------------------------- 198.4 MiB ================================= System: Kernel: 5.10.240-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 14.3.0 Desktop: IceWM v: 3.9.0 Distro: antiX-25-b2_x64-full Stephen Kapos 17 December 2025 base: Debian GNU/Linux 13 (trixie) Machine: Type: Laptop System: LENOVO product: 3249CTO v: ThinkPad X201 serial: <superuser required> Mobo: LENOVO model: 3249CTO serial: <superuser required> BIOS: LENOVO v: 6QET66WW (1.36 ) date: 05/31/2011 Battery: ID-1: BAT0 charge: 78.6 Wh (99.2%) condition: 79.2/84.2 Wh (94%) volts: 12.05 min: 10.8 model: Panasonic 42T4696 status: not charging CPU: Info: dual core model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere rev: 5 cache: L1: 128 KiB L2: 512 KiB L3: 4 MiB Speed (MHz): avg: 2019 min/max: 1199/2667 boost: enabled cores: 1: 2019 2: 2019 3: 2019 4: 2019 bogomips: 21279 Flags-basic: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel arch: Gen-5.75 bus-ID: 00:02.0 Device-2: Lenovo Integrated Webcam driver: uvcvideo type: USB bus-ID: 1-1.6:4 Display: server: X.Org v: 21.1.16 driver: X: loaded: intel dri: swrast gpu: i915 resolution: 1280x800~60Hz API: OpenGL v: 4.5 compat-v: 2.1 vendor: mesa v: 25.0.7-2 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 19.1.7 128 bits) Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr Network: Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e v: kernel port: 1820 bus-ID: 00:19.0 IF: eth0 state: down mac: <filter> Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel bus-ID: 02:00.0 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 176.54 GiB used: 2.17 GiB (1.2%) ID-1: /dev/sda vendor: Toshiba model: THNS128GG4BAAA-NonFDE size: 119.24 GiB ID-2: /dev/sdb vendor: SanDisk model: USB 3.2Gen1 size: 57.3 GiB type: USB Partition: Message: No partition data found. Info: Memory: total: 8 GiB available: 7.56 GiB used: 523.9 MiB (6.8%) Processes: 157 Uptime: 2m Init: Dinit Packages: 1989 Compilers: gcc: 14.2.0 Shell: Bash v: 5.2.37 inxi: 3.3.39--
Brian Masinick
Alternate "Search B":
This search pageandfree
If turnstile is purged, runit-service-rc-local-user will be automatically
installedupgraded.
But, if runit-service-rc-local-user is purged again, turnstile won’t be automatically installed again.
Edit: Sorry for my carelessness, again.- This reply was modified 8 months, 3 weeks ago by andfree.
- This reply was modified 8 months, 3 weeks ago by andfree.
antiX utilities for processing PDF files (posted by ChPol)
ProwlerGr
Maybe append “depends-on = dbus” at the end of the service file & let us know if this works for you.
Unfortunately it did not do the trick…
Can you also try:
depends-on = seatd waits-for = dbusI can’t replicate the problem (on my VM), lightdm always starts successfully for me.
Attachments:
olsztyn
Can you also try:
depends-on = seatd
waits-for = dbusThis did not fix it either.
Something I brought up before:
As I am facing black screen with blinking cursor, when I switch to VT1, log in as demo then execute ‘sudo lightdm’, this sudo gets to the default lightdm greeter screen, as expected. With no ‘sudo’, as a user, it does not.
On the greeter screen I can log in as demo and as expected I get the desktop. So is this not something meaningful, perhaps pointing to some dinit authorizations?Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Wallon
Bonjour,
Technical Analysis: Why autoscale-antix breaks Multi-Monitor NVIDIA setups
Context
Users with multi-monitor setups and proprietary NVIDIA drivers often find their “Primary Display” and layout settings reset at every login on antiX-25 (Beta 2). This report identifies the conflict within /usr/local/bin/autoscale-antix and provides a definitive fix.
System Environment (Tested)
OS: antiX-25-b2_x64-full (Stephen Kapos, Dec 2025)
Kernel: 6.6.101-antix.1-amd64-smp
GPU: NVIDIA GeForce GTX 960 (Driver: 550.163.01)
Setup: Dual Monitor (DP-0 Primary / HDMI-0 Secondary)
Init: SysVinitTechnical Breakdown of the Conflict
The investigation reveals that autoscale-antix contains two logic blocks that interfere with manual Xorg/NVIDIA configurations:1. The Execution Trigger (Lines 16-22)
elif [ -x "$HOME/.screenlayout/default.sh" ] ; then echo "Loading .screenlayout/default.sh configuration..." $HOME/.screenlayout/default.sh exit 0Analysis: This block forces the execution of default.sh if it exists. In NVIDIA setups, this script (generated by ARandR) runs after the driver has initialized the screens via Metamodes. This “second layer” of xrandr commands often lacks the –primary flag or uses incorrect offsets, breaking the layout defined in /etc/X11/xorg.conf.d/.
2. The Automatic Recreation (Line 138)
else if [ ! -f "$HOME/.screenlayout/default.sh" ]; then echo "" > "$HOME/.screenlayout/default.sh" && chmod +x "$HOME/.screenlayout/default.sh" fi fiAnalysis: Even if a user deletes default.sh to let the NVIDIA driver take control, this line automatically recreates an empty executable file. On the next reboot, the script triggers the block at Line 16 again, creating a loop of configuration resets.
The Solution (Multi-Monitor NVIDIA Users)
To resolve this without modifying system files, you must trigger the “already-run” check at the beginning of the script.
Instructions:
Open your startup file: geany ~/.desktop-session/startup
Add the following lines before the desktop execution:# Disable antiX autoscale to prevent multi-monitor layout conflicts # This ensures NVIDIA Xorg settings (Primary screen, Metamodes) are preserved export AFTER_SCALE_INFO="/dev/shm/ignore_autoscale"Conclusion
By exporting this variable, autoscale-antix exits immediately. This allows the NVIDIA driver to manage multiple displays natively, ensuring that the Primary monitor, refresh rates, and positions remain exactly as defined in your NVIDIA-optimized Xorg configuration.For your information, here are the details of my /etc/X11/xorg.conf.d/20-nvidia.conf file for multi-monitors;
# nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 550.163.01 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 Option "Xinerama" "0" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "Unknown" ModelName "AOC 2590G5" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "NVIDIA GeForce GTX 960" # On garde Coolbits car c'est une option de niveau pilote Option "Coolbits" "1" # On garde TripleBuffer car il est encore utile pour la fluidité Option "TripleBuffer" "true" # SUPPRIMÉS car génèrent les (WW) dans votre log : # Option "GPUPowerMizerMode" "1" -> À régler via nvidia-settings au démarrage # Option "AllowFlipping" "true" -> Inutile avec ForceCompositionPipeline # Option "NoLogo" "true" -> Obsolète (désactivé par défaut) EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DP-0" # Vos metamodes sont parfaits pour éviter le "tearing" (déchirure d'image) Option "metamodes" "DP-0: 1920x1080_60 +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, HDMI-0: 1920x1080_60 +1920+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSectionBest,
Wallon
- This reply was modified 8 months, 3 weeks ago by Wallon.
Wallon
Hello dev team,
While testing antiX 25 Full 64-bit Beta 2 (SysVinit), I noticed that /tmp is still mounted on the disk (root partition) by default.
Since antiX 25 is based on Debian 13 Trixie, and Debian has now moved to tmpfs for /tmp by default, wouldn’t it be a good idea to offer this option in the installer or enable it automatically if enough RAM is detected (> 4GB)?
Many antiX users are no longer on 10+ year old machines. On modern hardware, using tmpfs reduces SSD/USB key wear and improves overall system performance.
What are your thoughts on this for the final release?Best,
WallonBrian Masinick
Hello dev team,
While testing antiX 25 Full 64-bit Beta 2 (SysVinit), I noticed that /tmp is still mounted on the disk (root partition) by default.
Since antiX 25 is based on Debian 13 Trixie, and Debian has now moved to tmpfs for /tmp by default, wouldn’t it be a good idea to offer this option in the installer or enable it automatically if enough RAM is detected (> 4GB)?
Many antiX users are no longer on 10+ year old machines. On modern hardware, using tmpfs reduces SSD/USB key wear and improves overall system performance.
What are your thoughts on this for the final release?Best,
WallonFor users with 8, 12, 16 or MORE GB your solution makes very good sense.
Would it be possible to have a multi branch check at configuration time – if more than 4 GB detected, configure tmpfs, else configure /tmp as usual?--
Brian Masinick
Alternate "Search B":
This search pagej_luz
Haven’t had time to look into the issue with NVIDIA driver and certain inits not booting once I installed it. Tonight I made a copy of my 25b2-dinit master install, booted dinit, updated, installed nvidia. Rebooted into tty, where it blinks 3 times then stabilizes, looked at the log in ~/.local/share/xorg. Rebooted. Booted sysvinit, booted into login manager/desktop. Looked for new log in ~/.local/share/xorg, only had that log from the dinit previous boot, found new log in /var/log. Compared the 2. It seems pretty obvious that sysvinit is loading NVIDIA driver and dinit doesn’t mention that driver at all.
My next step is to find out if this issue is something I can change easily with a config file or starting a service, or something that will be addressed once release version gets out. I am not very technical and also I sometimes miss important forum threads, so I’m supposing I was supposed to start some service on some of the inits but I’m not sure what. I’d hate to do a bunch of work figuring this out if it’s something slated to happen magically on release.
wouldn’t it be a good idea to offer this option in the installer or enable it automatically if enough RAM is detected (> 4GB)?
An option would be the best solution,. Maybe with an explanatory snippet along the lines of:
On modern hardware, using tmpfs reduces SSD/USB key wear and improves overall system performance.
with caveat about having enough RAM.
grindstone
zathura install (32 bit sysV)
ln: failed to create symbolic link ‘/usr/share/runit/sv.now/rc.local/supervise’: Not a directory
anticapitalista
zathura install (32 bit sysV)
ln: failed to create symbolic link ‘/usr/share/runit/sv.now/rc.local/supervise’: Not a directory
Already reported severaltimes.
Here’s the fix.Rename the file /usr/share/runit/sv.now/rc.local to rc.local1
Create a directory in /usr/share/runit/sv.now/rc.local
Copy the rc.local1 file into that directory and rename it back to rc.localPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Both packages at-spi2-common & at-spi2-core appear to be upgradable, but:
– if I try to upgrade at-spi2-core, unsatisfied dependencies will stop me.
– if I try to upgrade at-spi2-common, at-spi2-core will be automatically removed.$ sudo apt install at-spi2-core Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: at-spi2-core : Depends: libatspi2.0-0t64 (= 2.58.2-1~bpo13+1) but 2.56.2-1.0nosystemd1 is to be installed Depends: libsystemd0 but it is not installable Error: Unable to correct problems, you have held broken packages. Error: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. libsystemd0:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2 but none of the choices are installable: - libsystemd0:amd64=257.9-1~deb13u1 is not selected for install - libsystemd0:amd64=257.8-1~deb13u2 is not selected for install 2. libsystemd0:amd64 is selected for install because: 1. at-spi2-core:amd64=2.58.2-1~bpo13+1 is selected as an upgrade 2. at-spi2-core:amd64=2.58.2-1~bpo13+1 Depends libsystemd0$ sudo apt install at-spi2-common Upgrading: at-spi2-common gir1.2-atk-1.0 libatk-bridge2.0-0t64 libatk1.0-0t64 libatspi2.0-0t64 REMOVING: at-spi2-coreantiX utilities for processing PDF files (posted by ChPol)
anticapitalista
@andfree – don’t upgrade to the backports version
Are you using synaptic to check for updates?
- This reply was modified 8 months, 3 weeks ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Apology and thank you.
- You must be logged in to reply to this topic.