- This topic has 10 replies, 2 voices, and was last updated Nov 2-10:24 am by punranger.
-
Posts
-
punranger
I’m using Antix 19.2 on an old Macbook from 2009 which has a Broadcom card. I’m using Ceni to set up Wifi, which worked fine until recently. Now, when I reboot, all the Wifi settings are lost, and it doesn’t show in Conky. The only way I can fix the problem is by reconfiguring the card. Ceni tells me the card is already configured, but I’m not able to find out why the system doesn’t recognize the config. Any help appreciated.
- This topic was modified 2 years, 6 months ago by christophe.
antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg
Xecure
I have been waiting for you.
Next time you reboot, don’t reconfigure ceni and try executing this in terminal:
sudo service networking restart
and see if it connects automatically to your wifi after that.Some people have experienced it and opted to go to connman. I would like to figure out if there is a problem in the order of services that load during boot. Maybe using runit vs sysvinit has different results, but we still haven’t figured out why it only happens on some computers and not others.
If the connection problem is resolved by restarting the networing service, would you stay a bit with us and try to help us figure out the source of the problem?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.punranger
Hi Xecure, and big thanks for your reply. The solution did indeed work. For what it is worth, here is the output from my terminal below. If I can help others, I am more than happy to stick around. Just post instructions, and I will check in when I can.
By the way, I tried connman, but was not successful in getting it to work.
per@antix1:~ $ sudo service networking restart [sudo] password for per: [....] Running /etc/init.d/networking restart is deprecated because it may not r[warnble some interfaces ... (warning). [....] Reconfiguring network interfaces...ifdown: waiting for lock on /run/network/ifstate.wlan0 Killed old client process Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/00:24:36:b7:7a:71 Sending on LPF/wlan0/00:24:36:b7:7a:71 Sending on Socket/fallback DHCPRELEASE of 192.168.1.16 on wlan0 to 192.168.1.1 port 67 send_packet: Network is unreachable send_packet: please consult README file regarding broadcast address. dhclient.c:2878: Failed to send 300 byte long packet over fallback interface. [ ok 0 done.antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg
Xecure
Sorry for the delay.
I have been trying to find more information on how things are booting differently from before in antiX and I cannot find any good tests, as my knowledge is limited. I know connman and maybe some other networking related service was moved in order for a connectshare problem, but I still cannot find a reason why on some systems networking starts correctly and in others it doesn’t.
I would like to add a delay of 1 or 2 seconds to networking service before it starts, just to make sure that everything else, but I really cannot figure out how /etc/init.d/ for sysvinit works.
I can only propose workarounds. I would like one of the knowledgeable people on the init to give some advice.
Workarounds:
1: use auto instead of allow-hotplug in /etc/network/interfaces.
This workaround delays boot time alot, so it is not recommended.2. Add to /etc/rc.local
sudo dhcpcd wlan0
or whatever interface name you see that si assigned to your wifi (you can see it in /etc/network/interfaces) so that it see if dhcp can be assigned before loading wpa_supplicant.3. Add to sudoers the command /sbin/service networking restart so that it doesn’t ask for a password
and add the “sudo service networking restart” command to the startup file in ~/.desktop-session/startup4. Try connman again. I helped create antix-wifi-switch not only to help people to switch to ceni when connman is not working well, but also to solve most of the connman problems the first time it launches. Try one last time to launch connman from the antix-wifi-switch and see if this time it works on the first launch.
Could one of the devs knowleadgeable in sysvinit give us a hand here?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.punranger
Tried workaround suggestion #2:
2. Add to /etc/rc.local
sudo dhcpcd wlan0
or whatever interface name you see that si assigned to your wifi (you can see it in /etc/network/interfaces) so that it see if dhcp can be assigned before loading wpa_supplicant.No success. Couldn’t notice any difference whatsoever.
Will try #3 and #4 before trying #1 (minimized boot time is a major reason to use AntiX for me).
antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg
Xecure
Reverse the change for the second suggestion and start with launching connman from antix-wifi-switch next. After connecting with connman once, it should work better at boot, as (i think) it launches later in the boot process.
I though I could learn how boot is scheduled with sysvinit, but is way more difficult than I thought. For some reason, on some computers some services are a bit delayed and that is the possible reason networking launches too late or early.
I was hoping for one of the devs who understands sysvinit better could give us a hint.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.punranger
Thanks for your suggestions. Still struggling to work with the sudoers file, I’m a total noob in that respect. Got syntax errors and haven’t figured it out yet. Will report back. But this does not really resolve the problem does it? The simple workaround of restarting network services is usable enough for the time being, so big thanks for that.
I’ve also tried connman again, but when I try to launch it, nothing happens at all.
Would upgrading from 19.2 to 19.3 possibly resolve the issue?
antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg
Xecure
I’ve also tried connman again, but when I try to launch it, nothing happens at all.
Are you perhaps using antiX 19 base?
Did you get to see the video I did about how to configure connman (before wifi switch was created)
https://www.youtube.com/watch?v=b5Ryp4gM2Eg&feature=emb_titleOn antiX base, the connman app is different (as it is lighter and uses less RAM). You need to hold the left-click on the systemtray icon and release it on the Wireless Access Point you want to connect to. Ignore the “error resolving” parts as those no longer should come up after launching connman using the wifi-switch.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.punranger
Thank you! Yes, I’m using base. Using the advice in the video, I got connman working. It was not very intuitive, I must admit. Tried rebooting once to see if the wifi persisted. So far, so good.
I gotta say I’m very impressed by the kindness from complete strangers to a total antiX noob. I’ll do my best to pay the kindness forward.
antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg
Xecure
Great news! Most of the troubles people experience with connman is the initial connection. Once that is sorted, it works very well.
Hope you enjoy your antiX system! If anything else pops up, let us know and we will try to help as best as possible.
Regards.
PD: If you can still edit your first post, try adding [Solved] to the title so other may find this thread and possibly also a solution to their problem.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.punranger
Sorry, couldn’t edit post title. What’s the time limit for doing such edits?
antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg
- You must be logged in to reply to this topic.
