- This topic has 30 replies, 11 voices, and was last updated Jan 1-3:24 pm by kbJFJF4fSzoJZw.
-
Posts
-
anticapitalista
Remove my membership now I wasted time I do not have to wasted heaps of typing for nothing..
I will do later today as requested.
Later : Done. Posts should show as ex_Koo
- This reply was modified 1 year, 5 months ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
PPC
Partly off-topic:
Well, I’ve seen Koo here in the forum for quite some time. I also had my share of problems with operating systems:
-In Windows (98, maybe 95) my brother got a new dedicated graphics card- it installed fine in Windows, ran great, but, after rebooting, it refused to run… It was a driver’s problem, and he had to swap the card for another one…
-In several distros I had to reinstall, simply because I messed something up so bad that I did not know how to solve it and it was faster than posting a question on a forum…
-In MX Linux- it refused to work with the Nvidia driver, at reboot, I was always stuck in the terminal (no X)- I redid the same steps, over and over, with tiny variations. sometimes repeating steps- until, out of the blue, the Nvidia driver began working!- that’s still the MX install I have on my secondary partition (MX 17)
-More to the point: In antiX- while trying out my ft10 transformation pack in all 3 floating window managers, I noticed something very strange- my CPU as always maxing out at 100%, and RAM usage kept increasing some 4-5mb for very 5-10 seconds- the computer was so slow it was almost unasable- I rebooted- no change- I tried to change to another window manager- no luck- Conky kept flashing “antix” and then “antiX min-fluxbox)- What the…?
I was beginning to think that was to right time to upgrade to antiX 21… until… I went to user management, removed auto-login, rebooted. ant the log-in window, I pressed F1 and chose IceWM- and it logged in to IceWM as usual- no 100% CPU usage, no increasing use of RAM! I logged off, selected Fluxbox, logged back on- 100% CPU usage, RAM usage always increasing- at that point lx task-manager informed me that the script to change desktop was running in a loop, starting a new instance every x seconds…
Log off and back on to IceWM. Purged fluxbox, reinstalled fluxbox, logged back on again- and I got the normal fluxbox desktop I’m running right now.What happened to Koo’s antiX install? I have no idea.
Like I have no idea why Windows refused to work with that graphics card, long ago, and why Mx 17 refused to work with nvidea, and why so many strange stuff happened in my computers over the years- sometimes, once in several millions, a power surge can make the wrong byte to be recorded – messing up your computer in an impossible to foresee way.
Maybe something similar happened to Koo, maybe not. It’s impossible to know- but antiX works for many people, all over the world, in every kind of computers (ranging from stuff that is over 20 years old to stuff that’s 20 hours old)- but, like Forest Gump used to say “S**t happens”. when that happens, usually the forum is here to help us ordinary folks, but when all fails- reinstall or, if that fails to succeed, downgrade! That’s why I’m not using antiX 21 as my daily driver- I’m waiting for every small wrinkle to be ironed over…P.
stevesr0
Update: I solved my problem.
After much thrashing around about the “conflict” between xserver-xorg-core and the modesetting function incorporated in it (xserver-xorg-video-modesetting), I went through all the related xserver packages and found one xserver-xorg-legacy which was the same version as the xserver-xorg-core in the upgrade, but which was not included in the packages to be upgraded.
It is said to be needed for systems with old drivers – since my Fujitsu is vintage around 2006, I thought this might be helpful.
After installing, my graphic desktop is back to normal.
(Hopefully, it will last <g>.)
Perhaps other folks might have the same need to install it if they upgrade/update xserver packages.
Hope that is helpful.
(Still don’t understand why/how there could be a conflict between xserver-xorg-core and the xserver-xorg-video-modesetting that is part of it.)
stevesr0
ModdIt
What happened to Koo’s antiX install? I have no idea, I had freezing or loss of input on 3 machines.
The crazy disk activity also on all three. Problems in part related to ICEWM setup but majority of the
issue runit related.Knowing koo, he was trying to post results of his testing and probably working fixes.
He has made many very useful contributions, to me a sad loss..I am now posting from a sysv setup, been running for hours, disk quiet, no rythmic intermittent network activity.
No freezes up to now. I made fresh runit setups, all had same problems. Core 2 duo, dual core Pentium, I5 made no
difference.Tired of testing now.
anticapitalista
I added this to the release announcement.
Note 1: antiX devs advise users to download and use the sysVinit versions
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Robin
antiX devs advise users to download and use the sysVinit versions
I’d propose there should be added an explanation, what is meant by the wording »sysVinit versions« since there are no versions marked this way present at the servers (See screenshot attached). There are only versions without any mark, and versions marked as »runit« within the »runit« folder. By now I have not researched what makes the difference between them, but I presume you refer to the non marked versions as »sysVinit« ?
Attachments:
Windows is like a submarine. Open a window and serious problems will start.
@anticapitalista – I think Robin is right – that info is highly specific, most people won’t know what it means- perhaps “antiX devs advise users to download and use non Runit versions“
olsztyn
most people won’t know what it means- perhaps “antiX devs advise users to download and use non Runit versions
Not my call but I am surprised at sudden advice to stick with sysvinit in the first place. I have a feeling troubles Koo (and possibly Moddit) had could have been unique, as not widely reported, and perhaps not having anything to do with Runit per se but rather perhaps with something in the install or certain update.
I have been running Runit 21 on a variety of machines, old and much newer, and never encountered any such issues.
Fact, I am running not-installed. Just Live, Frugal and internal SATA Live. Both USB sticks and SATA disks (both spinning and SSD). Not a single occurrence of such issue. I think I remember Koo mentioned it was running fine until some update installed recently. This means something but not pointing to Runit architecture IMO, since recent updates did not change runit system architecture.
My long IT experience taught me that if an issue pops up after some update then back out that update to return to previously working fine system, not swap to a different system…
Just my opinion…- This reply was modified 1 year, 5 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersFreezing occurred on three systems, I am not completely sure that is directly runit related
as on beta with same software setup but earlier versions I never had that happen.The present constant disk activity is definitely runit related.
Right now I do not have the time and energy to follow all the tracks and info I found,
in any case pointless to post further unless I have a solution to offer.I agree with anticapitalista that the runit version is better reserved for experts until
issues are solved.anticapitalista
Message reads –
Note 1: antiX devs advise users to download and use the sysVinit versions ie any iso files NOT in the runit folder.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
kbJFJF4fSzoJZw
If I have a working keyboard in the BIOS and a working keyboard (and mouse) in the live CD system, but no [working] keyboard and mouse in the installed system (installed using this live CD), could it be for the reason stated in this thread? I’m a complete zero on Linux, sorry.
caprea
Hello kbjfjf4fszojzw,which iso did you download and install ?
If possible could you post your hardware from the live cd, it’s the output from terminal of
inxi -zv6
This would also show which iso is downloaded.@kbjfjf4fszojzw – sometimes, on a old desktop, when I restart my computer, it refuses to work with my keyboard (I can’t even use it to make a selection from GRUB)- when that happens, I shut it down using the power button and then turn it back on- then the computer detects my keyboard (this is on antix 19.x, 64bits, on a old single core). I guess some power management problem blocks the usb ports… May be the same problem in your computer…
P.
Everything works now. I only changed two things: plugged in a floppy disk drive (I don’t think this made any difference, I still get some kind of fd0 error when I turn on the computer) and reinstalled antiX in Safe Video mode instead of Failsafe mode (Normal mode hung up during boot at “start init” stage).
I installed antiX-21_x64-full.
inxi -zv6: https://pastebin.com/ZEcshNwd
Thanks for the replies and sorry for the inconvenience. I should have tried to reinstall earlier.- This reply was modified 1 year, 4 months ago by kbJFJF4fSzoJZw. Reason: Sorry, I thought the spoiler code was working here
caprea
Might during installation there was made/or not an entry for the floppy disk in /etc/fstab
and now it’s looking during boot for this device
Is it still plugged in ?
You could post the /etc/fstab content.
- You must be logged in to reply to this topic.
