What`s a quick way to activate wifi using current ceni setup ?

[Moderator caprea]

Helpful

Up

0

::

The wifi-card of the OP is one of the intel calexico2 cards, which are almost always issued as eth1.
Intel PRO/Wireless 2915ABG[Calexico2]

AA BB, would you mind giving ceni one last chance with the following content in etc/network/interfaces
Edit as root

#------------------------------------------------------------------------------
# /etc/network/interfaces
#
# interfaces(5) file used by ifup(8) and ifdown(8)
# Used by ceni but not by connman
#------------------------------------------------------------------------------

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
	wpa-psk XXXXXXXXXX
	wpa-ssid House stark

[Member AA BB]

Helpful

Up

0

::

If the tools we provide are not working for you, try the ideas on the page:
https://linuxconfig.org/connect-to-wifi-from-the-linux-command-line

I followed the above link to the letter to set-up and verify
/etc/wpa_supplicant/wpa_supplicant.conf
was set up per the author`s recommendations

BUT could not understand how to do the last step “restart wpa_supplicant for the changes to take effect”
so I ran wpa_cli >scan then re-booted and tried to connect…but still no wifi

For some reason antix wifi tools still insists on creating a wifi interface called ‘eth1’ rather than ‘wlan0’
ceni correctly identifies the wifi card but cant make it operational

.

[Member Xecure]

Helpful

Up

0

::

AA BB wrote:

For some reason antix wifi tools still insists on creating a wifi interface called ‘eth1’ rather than ‘wlan0’

I have checked your other posts, and it isn’t just antiX. Your MX linux inxi post also displays your wifi as eth1. And caprea also said:

caprea wrote:

The wifi-card of the OP is one of the intel calexico2 cards, which are almost always issued as eth1.

So don’t worry too much about it being eth1 or wlan0

AA BB wrote:

I followed the above link to the letter to set-up and verify
/etc/wpa_supplicant/wpa_supplicant.conf
was set up per the author`s recommendations

BUT could not understand how to do the last step “restart wpa_supplicant for the changes to take effect”
so I ran wpa_cli >scan then re-booted and tried to connect…but still no wifi

I am not too knowledgeable about wpa_supplicant, but maybe you need to launch it on startup. Try editing ~/.desktop-session/startup and adding an extra line for wpa_supplicant

#launch wpa_supplicant on startup
wpa_supplicant -B -i interface -c /etc/wpa_supplicant/wpa_supplicant.conf &

This is just a suggestion. I have no idea if this will work or if it is needed.
Another option could be to launch a different script on startup, as described by one of the links referenced on previous posts (creating a wifi-start.sh file and adding a “launch” command on the startup file) may work.

• This reply was modified 3 years, 1 month ago by Xecure. Reason: typing too fast

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member AA BB]

Helpful

Up

0

::

AA BB, would you mind giving ceni one last chance with the following content in etc/network/interfaces
Edit as root

I verified /etc/network/interfaces was set-up as requested, rebooted ran ceni and when I tried to ‘scan’
ceni reported and error related tp ‘RF kill’
I couldn’t copy the terminal output sent by ceni, but a tried again and was able to get a ceni screen that
allowed me to ‘force’ ESSID House stark, then I re-scaned
This time I could capture ceni’s output (see attached file)

Attachments:

1. Apr8.txt

[Member AA BB]

Helpful

Up

0

::

I am not too knowledgeable about wpa_supplicant, but maybe you need to launch it on startup. Try editing ~/.desktop-session/startup and adding an extra line for wpa_supplicant

#launch wpa_supplicant on startup
wpa_supplicant -B -i interface -c /etc/wpa_supplicant/wpa_supplicant.conf &

I made this modification, re-booted and could definitely see an expected slowdown in the booting process due to network ‘Lisnening’ ..
but after antiX booted, I still had no conky display for either eth0 or eth1
So I ran ceni, did a scan, but the ceni scan found no BSSID s

This is really weird..it seems I’m moving backward in my efforts to connect :
Prior to this i always got ‘eth0’ up and ‘eth1’ down in the conky display

[Member Xecure]

Helpful

Up

0

::

Edit:
By the way, it should be:
wpa_supplicant -B -i eth1 -c /etc/wpa_supplicant/wpa_supplicant.conf &
and not “interface” in my last post. Sorry for the mistake

AA BB wrote:

I made this modification, re-booted and could definitely see an expected slowdown in the booting process due to network ‘Lisnening’ ..
but after antiX booted, I still had no conky display for either eth0 or eth1
So I ran ceni, did a scan, but the ceni scan found no BSSID s

Sorry for that. Delete those lines then and reboot.

My only experience with antiX 19 has been ceni, connman and gnome network manager. My best experience has been with ceni, but I have never experienced the problem you have (that it doesn’t autoconnet).
To get ceni back working you may need to kill all ceni and wpa_supplicant processes

sudo killall ceni
sudo killall wpa_supplicant

And then start ceni up again.

• This reply was modified 3 years, 1 month ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator BobC]

Helpful

Up

0

::

While testing for this, I’ve broke my test system that was working just fine connecting via connman, to being able to get an ip address via ceni, but not being able to transfer any data via wifi or hardwired. The same machine used to work just fine with ceni under antiX 17.x. I think that I caused the situation by mixing ceni and connman. I will have to reload it. It’s not a big deal, but just stating that was how I think I got into that position.

Question, did you ever have connman on the system in question?

[Member AA BB]

Helpful

Up

0

::

This may help…

when I run ceni > scan the error message is

rfkill : WLAN soft locked..could not set eth1 flags (UP): operation not possible due to RF-kill

..but this very same box has no trouble connecting when I dual boot MX 19.1 instead of antiX 386 base
so I’m wondering if it`s a good idea to copy over one or two MX 19 directories to overwrite some antiX directoy(s) ??

[Moderator Brian Masinick]

Helpful

Up

0

::

Based on the text output it sounds like more than one process is attempting to access the network lines at the same time.

Whether you use ceni, network manager, Connman, wicd, or a script that directly opens the network ports, there can only be one process at a time accessing the network ports.

Ceni can co-exist along with another network manager as long as they do not have the network ports open at the same time.

--
Brian Masinick

[Member AA BB]

Helpful

Up

0

::

To get ceni back working you may need to kill all ceni and wpa_supplicant processes

sudo killall ceni
sudo killall wpa_supplicant

And then start ceni up again.

Done as requested BUT when I run ceni > scan the same old error message as in last post ..I’ve included one extra line that I omitted from the previous post

Driver does not support authentication/ assoociation or connect commands…
rfkill : WLAN soft locked..could not set eth1 flags (UP): operation not possible due to RF-kill

Based on the text output it sounds like more than one process is attempting to access the network lines at the same time.

Whether you use ceni, network manager, Connman, wicd, or a script that directly opens the network ports, there can only be one process at a time accessing the network ports.

Ceni can co-exist along with another network manager as long as they do not have the network ports open at the same time

Do the two killall commands above, followed by a call to ceni, ensure only one process is accessing the network ports ??

[Moderator Brian Masinick]

Helpful

Up

0

::

In theory the kill commands remove the extra network manager processes.

If a network manager gets restarted for any reason, the presence of more than one will definitely cause problems.

A network manager with daemon processes is an indication that it has to be the only controller for networking.

--
Brian Masinick

[Moderator BobC]

Helpful

Up

0

::

I downloaded and installed 19.2 386 base, and tried ceni and had the same issues AA BB had.

I then tried again, but didn’t install, worked from the flashdrive, and instead of using ceni I figured out how to get connman running, configured and working.

Nothing but ceni and wpa_gui appear on the network tab of control centre. That might lead someone to click one of those and get trapped like AA BB. This time I didn’t try it.

Then I found Connman Setup on the Internet menu. At first I didn’t think it ran. What’s weird is that you can barely see the wifi control down at the bottom next to the volume because its black on almost black, so I started it twice by mistake. I right clicked it and wifi was turned off so I turned it on. But that didn’t fix it. But I found that if I left click that icon and hold it down the list comes up and you can mouse to the connection. Somehow I got it to let me enter the password and it connected.

I hope that helps. I’m no real wifi expert. If it would be not too hard for you, I would suggest cold booting it, and trying it from the flashdrive like I did, and see if it workes the other way and just consider reinstalling and doing it the other way if it works. Once I tried ceni, I had no luck with connman, even after a cold boot.

[Moderator BobC]

Helpful

Up

0

::

I rebooted back into the installed setup and right clicked, turned on wifi, went to my connection and got it to connect

[Moderator BobC]

Helpful

Up

0

::

If I change the theme to Clearview Blue Medium I can see the Wifi icon much better. I went back into the flashdrive system, and its hard to see, but it comes up immediately with connman running down next to the volume icon, so if you try to run ceni, both will be running, and it won’t work.

I did not find a way to get ceni working, not that it doesn’t exist, but I didn’t find it. That’s all for me for this one. I’m going to see if I can get my respin to run in 32 bit mode for the old PC’s here. You never lose till you give up trying…

• This reply was modified 3 years, 1 month ago by BobC.

[Member AA BB]

Helpful

Up

0

::

Thank you BobC I think you hit the nail on the head.

I spent the better part of this evening installing a fresh downloaded copy of 19.2 386 base on another box that has MX installed.

After the install, the only changes I made were those recommended by anticapitalista :
1 Remove connman and cmst
sudo apt-get remove –purge connman cmst connman-bluetooth-firmware-antix
For antiX-19.2-base, cmst is not installed, nor connman-bluetooth-firmware-antix
but you should remove connman-ui in step 1
2 Delete the resolv.conf sym link in /etc/
3 Create a new symlink in etc like this (in a terminal)
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
4 Then use ceni

ceni sent back error messages so I remove file /run/wpa_supplicant/eth1 manually, then re-booted
… waited a minute…then run ceni again.
BUT ceni gives me the same output my other box gave me.

When I was running my antiX version prior to 19.2, I was able to connect using connman, but it kept dropping the connection after 1-5 minutes
Using ceni under 19.2 doesn`t seem to improve things .

[Author]

Posts