- This topic has 8 replies, 5 voices, and was last updated Dec 16-5:01 pm by Brian Masinick.
-
Posts
-
roland
Recently I installed 21 Grup Yorum on a build and was gratified to find Connman up and running ‘out of the box’. Since then however I have been plagued with mysterious and apparently random loss of connection to the lan even though Conky continues to show the 2 panels up and down transmissions, and characters appear to be moving up and down. I did run the Wifi switch script to confirm my use of Connman. Sadly I have now run the Wifi switch script to revert to Ceni, and which has apparently cured the problem.
ModdIt
Hi roland,
that might be due to the fact that connman pings in a never ending manner to MS servers, if they are unreacheable
even for a short period it goes nuts and initiates reconnections.
I am also on ceni, the usable as tracking pings no more, same goes for the connman related disk activity.Removing connman breaks printing with my Brother drivers so annoyingly, I have to leave it installed.
roland
Thanks Moddit, I have during several releases always given Connman a try, always with limited or no success, and always have selected Ceni as the dependable lan handler. I have also used Wicd in the past but comments in the forum regarding its high memory requirement caused me to prefer Ceni in the end, although I now have no memory limitations to speak of.
Ceni is simple to run and once set up and running, can be left to connect automatically. It just has one or two usability problems such as if a lan file already exists in wpa_supplicant there is no option but to start a root window to delete it then run Ceni again, also the available lans cannot be seen without starting the connection process.
Maybe my own requirements are too simplistic for general use as I only have the one lan to connect to, so Ceni suits me fine. But could not Ceni be cosmetically and functionally enhanced and then become the lan handler of choice for antiX? Quite honestly after several years of trying Connman I feel it is going nowhere.
roland
Even though I ran apt-update then apt-remove connman I am still getting a message relating to Connman and when I cancel this the Connman window still appears. Is there any way I can completely eliminate this? It’s not a big issue, just an annoyance, and it causes me to wonder if there is something else I should run or remove to completely eliminate Connman. I have decided to give Connman no further trials in view of the effectiveness of Ceni.
blur13
sudo apt-get purge might do the trick
Xecure
You have gone through this so many times. Remove the connman gui named CMST
sudo apt purge cmstQuite honestly after several years of trying Connman I feel it is going nowhere.
This may be bad luck or your specific configuration or needs.
I have been using connman since antiX 19, and had more trouble with ceni than with connman in the last few years. Moddit just doesn’t like all the extra network activity in connman, but that has nothing to do with your problem.If ceni works for you, that is great. Continue using it. If you don’t experience a large scan time when searching for Wireless Access points, and don’t need to add a hack for networking to restart on every session (because it automatically connects to your wireless network at boot time), then Ceni is for you.
Also, please remove the network checks from startup so that the program doesn’t bother you in the future.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Brian Masinick
I’m pretty sure I have cmst/Connman
installed on both of my antiX 21 instances, which I updated at midday here.Now I’m outside of a local elementary school to ‘wait in line’ to pick up my 5th grade nephew from school; my wife and I will also be watching him for his parents for a few hours this evening.
Meanwhile, back to antiX 21: both instances run very well, but I noticed that the runit instance, as I have it configured checks in with about 100 MB LESS memory consumed after login and process is idle.
I could be wrong, but I thought that both instances started with Base, but I do notice that more stuff seems to be enabled and started with the sysvinit instance; MAYBE I installed antiX 21 Full on that one; I’ll check next time. Either way, they’re both fairly frugal, but the runit instance is excellent, maybe around 120 MB mem used.
In the 2005-2008 era I could start up antiX with between 58-64 MB, with IceWM and Fluxbox at #1 and #2, respectively. Fluxbox had a couple more “features” while IceWM has always been effective and simple.
Our antiX today consumes just over twice the initial memory as the early versions did, but easily stands at or near the top in lean, effective use of resources today and definitely the easiest of the lean systems to get an effective system that is useful, lean and responsive.
--
Brian Masinickroland
Thanks, purging cmst has cured it. I’ ll be sticking with Ceni from now on, but I am uneasy that in some future release Ceni will maybe not be offered.
Brian Masinick
Thanks, purging cmst has cured it. I’ ll be sticking with Ceni from now on, but I am uneasy that in some future release Ceni will maybe not be offered.
If you are truly concerned about that, here’s my suggestion.
1. First find the location of the ceni / Ceni image. (It might be in /sbin).
2. Once you locate the image, note the exact file ownership and permissions.
3. Write all of this down, either on paper, on a file that you are able to preserve, or in another safe place.
4. Finally, copy the file into your own private directory and make back up copies.If you ever have to restore it, move it, or even replace it, whether it’s included in the system or not, you now have the information necessary to get it back and use it. As far as I know, there are no dependencies, but in case I’m wrong, check that out using apt, synaptic, or whatever you’re using to manage packages.
I probably have a copy somewhere myself.
--
Brian Masinick
- You must be logged in to reply to this topic.
