- This topic has 15 replies, 3 voices, and was last updated Nov 20-1:21 pm by Xunzi_23.
-
Posts
-
Xunzi_23
Latest sid breakage, the machine is only one which will properly drive a pretty old Brother Printer.
Please see attached boot messages, I could only take a photo of the screen.Any help or advice on a possible fix welcome.
Would a mod pls remove the non rotated image, sry
- This topic was modified 10 months, 1 week ago by Xunzi_23.
Attachments:
ProwlerGr
Which runit boot module are you using?
It looks like /usr/bin/wtmpdb is missing
I don’t have this installed on antiX-25-beta1
With a live cd do a chroot rescue & either:
install the runit-service-boot-module
or
install the wtmpdb packageAre you OK with these instructions?
Hallo ProwlerGR, thank you for help.
I have installed wtmpdb,
do not know how to check on runit-service-boot module in the change root environment.apt says no install candidate.
Strangely now I get a dinit boot to console, no network no x. If I try to start X black screen no input possible.
- This reply was modified 10 months, 1 week ago by Xunzi_23.
apt says no install candidate.
Righto, I can see @anticapitalista hasn’t moved it into the main sid repo yet (still in dev)
Strangely now I get a dinit boot to console, no network no x. If I try to start X black screen no input possible.
Hmmm, to me it sounds like an issue with udev, but I”d imagine runit would also be affected if this is the case…
anticapitalista
Enable dev repo as well as the usual ones for antix.list(sources).
Chroot into the installed partition and install
runit-antix runit-init-antix runit-service-boot-module runit-service-seatd runit-service-slimski runit-service-connman
runit-service-dbus runit-service-dhcpcd runit-service-udevdThat should get you to a desktop
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
anticapitalista
For dinit, install
dinit dinit-init-antix dinit-service-boot-module-antix dinit-service-seatd dinit-service-dbus dinit-service-slimski
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Many thanks for the assistance anticapitalista,
Sorry, seems I have to ask for a working /etc/apt/sources.list.d/antix.list
for sid and with dev active. So I can install the recommended packages.
I am probably doing something daft, or the repos I have tried are having
some kind of issue.anticapitalista
antix.list
# Use with Debian Sid repositories. deb [signed-by=/etc/apt/keyrings/antix-archive-keyring.gpg] http://repo.antixlinux.com/sid sid main nonfree nosystemd devPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Sorry for slow reaction, other important work to do.
@anticapitalista, another thank you for the kind assistance
I now have a boot to desktop with runit. 🙂
Will do more testing this evening including dinit.
In the end I had to replace the entire antiX list entry in apt list.d, before that it always gave an error.
Getting to desktop required a number of upgrade reboot and dpkg configure cycles, first in chng root, then I
had to do same in the installed system while it was still only booting to a command line.last error I see now below, that is after disabling dev again, but shows same if I enable dev.
If there is a probable fix I can go for it, otherwise for now just live with it.sudo apt dist-upgrade
Paketaktualisierung (Upgrade) wird berechnet… Fehler!
Fehler: Unable to satisfy dependencies. Reached two conflicting decisions:
1. (root) is selected for install
2. (root) -> | sysvinit-utils:amd64 | sysvinit-utils:i386
but none of the choices are installable:
– sysvinit-utils:amd64 is not selected for install because:
1. sysvinit-utils-antix:amd64 is selected for install
2. sysvinit-utils-antix:amd64 is available in versions 3.05-6.0antix1, 3.01-1.0antix1
[selected sysvinit-utils-antix:amd64=3.05-6.0antix1 for install]
3. sysvinit-utils:amd64 Kollidiert mit lsb-base (< 11.3~)
For context, additional choices that could not be installed:
* In sysvinit-utils-antix:amd64 is available in versions 3.05-6.0antix1, 3.01-1.0antix1:
– sysvinit-utils-antix:amd64=3.01-1.0antix1 is not selected for install
– sysvinit-utils:i386 is not selected for install because:
1-2. sysvinit-utils-antix:amd64=3.05-6.0antix1 is selected for install as above
3. sysvinit-utils:i386 Kollidiert mit lsb-base (< 11.3~)
For context, additional choices that could not be installed:
* In sysvinit-utils-antix:amd64 is available in versions 3.05-6.0antix1, 3.01-1.0antix1:
– sysvinit-utils-antix:amd64=3.01-1.0antix1 is not selected for installanticapitalista
@Xunzi_23 – glad to see back into desktop.
I see that error message on one of my sid installed but not the other.
I have to do apt upgrade rather than apt dist-upgrade.
I’m not sure why this is happening as there are no conflicts even though apt says there are.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
@anticapitalista
Thanks for info on the error message, marked solved.One of the strongest points of antiX is, (not just) in such situations
the live tools, they did a great job yet again.anticapitalista
@Xunzi_23 – do you have any idea what caused the breakage?
If you upgraded using dev repos, you now have the latest runit implementation.
Basically the means you will need to install various runit services as they are now packaged separately (runit-service-*).Existing sid and testing users should be covered by the old way so no important service files get removed.
This should apply to runit and sysVinit users.In a week or so, I’m going to move all the init apps from sid and testing dev to sid and testing main/nosystemd.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Most likely candidate for boot fail is below, runit update, excerpt from update on 17.11.2025
after that time no full boot possible, until today that is:-)Vorbereitung zum Entpacken von …/07-runit-antix_2.2.0-3.0antix6_amd64.deb …
Entpacken von runit-antix (2.2.0-3.0antix6) ĂĽber (2.2.0-1.0antix1) …
[1mdpkg:[0m [1;33mWarnung:[0m Altes Verzeichnis »/lib/runit« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer
translated. old directory /lib runit can not be deleted, it is not emptyI f you want the full log no problem, I just think it is not neccesary.
from history log
Start-Date: 2025-11-17 08:02:07
Commandline: apt upgrade
Requested-By: user (1000)
Install: linux-image-6.17.8+deb14-amd64:amd64 (6.17.8-1, automatic)
Upgrade: claws-mail:amd64 (4.3.1-1, 4.3.1-1+b1), runit-antix:amd64 (2.2.0-1.0antix1, 2.2.0-3.0antix6), desktop-defaults-zzzfm-antix:amd64 (0.7.0, 0.7.1), apt:amd64 (3.1.12, 3.1.12.0nosystemd1), f3-qt:amd64 (2.1.0~antix23, 2.1.0+git20240415.5110939-2), claws-mail-pgpmime:amd64 (4.3.1-1, 4.3.1-1+b1), libapt-pkg7.0:amd64 (3.1.12, 3.1.12.0nosystemd1), claws-mail-smime-plugin:amd64 (4.3.1-1, 4.3.1-1+b1), slimski:amd64 (1.5.0-6.0antix8, 1.5.0-6.0antix11), palemoon:amd64 (33.9.0.1-1mx25, 33.9.1-1mx25), claws-mail-pdf-viewer:amd64 (4.3.1-1, 4.3.1-1+b1), desktop-defaults-rox-antix:amd64 (0.9.0, 0.9.1), linux-image-amd64:amd64 (6.17.7-2, 6.17.8-1), apt-transport-https:amd64 (3.1.12, 3.1.12.0nosystemd1), apt-utils:amd64 (3.1.12, 3.1.12.0nosystemd1), claws-mail-pgpinline:amd64 (4.3.1-1, 4.3.1-1+b1)
End-Date: 2025-11-17 08:02:29anticapitalista
Yeah, seems like it was the runit update.
In hindsight I probably shouldn’t have updated it to sid/main but sid/dev.Early test for when the floodgates open 🙂
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
- You must be logged in to reply to this topic.