- This topic has 53 replies, 7 voices, and was last updated Apr 2-10:38 am by anticapitalista.
-
Posts
-
AA BB
” Type connman-ui-gtk in a terminal …”
results in ” command not found” message…two awwows on task bar show “visible” “aoto hide” “clock ” etc but nothing related to any network
armando
provide the output of this commands on both systems, antix and MX, to see if there are any differences:
sudo inxi -Fxxxza
hwinfo --wlan
iw list(press “code” option, paste your results, then press “code” again, to enclose in backquotes your results.)
If your connection is just fine in MX, and in antix the connection drops in about 2-5 mins, I don’t know what can be the problem. Connection drops is most likely for low signal.
Try ceni, I find it very reliable, and you can see the log in realtime, plus I’ve never used connman.
I just can provide you with 4 realtime useful commands:
ip monitor sudo dmesg --follow -T wpa_cli iwevent
caprea
Your problems with base and connman might also be related to this
http://www.antixforum.com/forums/topic/antix-19-2-hannie-schaft-bug-fix-upgrade-isos-available/#post-34018Intel PRO/Wireless 2915ABG
There have been people on this forum who could use the 2915ABG without any problems with connman.
However, there were also people who could not get the card to work with connman.
In any case ceni always worked.Ceni is generally installed but not ready to use.
To use it instead of connman, you need to follow the steps below.
http://www.antixforum.com/forums/topic/failing-with-liveusb-persistence/#post-32414caprea
Also look here
http://forum.mxlinux.org/viewtopic.php?f=40&t=53512provide the output of this commands on both systems, antix and MX, to see if there are any differences:
sudo inxi -Fxxxza
hwinfo –wlan
iw listOn both systems iw list generates “command not found” error message
Huge output for sudo inxi -Fxxxza is in attached files file AX1.txt for AntiX and MX1.txt for MX (both AntiX and MX are dual boots on the SAME PC)
Likewise output for hwinfo –wlan is in Ax2.txt and MX2.txt
rokytnji
He might have ment
iwlist wlan0 eventmaybe.
iwlist –help will give the syntax to use when trouble shooting.
ust checked. He probably meant
iweventafter looking at his screen shots < which are too kewl for skewl > and checking in my terminal
That dmesg command is a New one for me also.
Sometimes I drive a crooked road to get my mind straight.
I don't suffer from insanity. I enjoy every minute of it.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsAttached is the iwevent output from AntiX (AX_iwevent.txt) and MX (MX_iwevent.txt)
anticapitalista
You should really be using antiX-19.2 and not antiX-19.1 (as shown by your uploaded txt file a couple of posts up)
You should also have said that you have upgraded the kernel.Anyhow- assuming you are not hiding anything else important from us,
Post the output of /etc/network/interfaces file.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
armando
duplicated
armando
…
On both systems iw list generates “command not found” error message
…iw is actualy a command (http://packages.debian.org/buster/iw)
when you get the message “command not found”, you just have to install it (sudo apt install iw)
“iw list List all wireless devices and their capabilities.”
but the output is not relevant right now. so dont worry about it——-
I’m not an expert but here is what I saw from your inxi and hwinfo output:inxi show that both antix and MX are using the same driver as expected: ipw2200
MX seems to detect a bluthooth device but antix dont.
MX seems to load an additional driver wl (http://wiki.debian.org/wl) that, probably belongs to the etherneth PCI card(?), Or maybe wl belongs to the bluethoot device but the brand don’t match. I’m not sure, you can install wl, or you can wait for someone else to say if the wl has anything to do with your problem.——
Attached is the iwevent output from AntiX (AX_iwevent.txt) and MX (MX_iwevent.txt)
for some reason your wireless interface is named eth1, not sure if this is an issue, it should be wlan0.
do as capitalista says and post the interfaces file and the output of iwconfig and ifconfig:sudo cat /etc/network/interfaces
iwconfig
ifconfigAlso your MX_iwevent.txt doesn’t show the moment when is associated when you are connected or disconnected, you have to wait the moment your network is connected to see which network uses or when your network got disconnected to see if there is any feedback, but use “sudo dmesg –follow -T” instead iwevent, I think dmesg provides more useful information, or the 4 commands at the same time.
Also you seems to have 5Gz and 2.4gz network available with the same name, if you know how you should enter the router (likely: http://192.168.0.1) and rename the 5gz network as “House stark_5gz” or something like that. Or disable 5ghz for debug purposes.
(my last post got hidden, to many edits I guess)
Attached is a file containing output of the three cmds requested above
You should really be using antiX-19.2 and not antiX-19.1 (as shown by your uploaded txt file a couple of posts up)
You should also have said that you have upgraded the kernel.Anyhow- assuming you are not hiding anything else important from us,
Post the output of /etc/network/interfaces file.
As i mentioned earlier in this thread, I installed 19.2 386 base in an effort to solve my wifi problem.
after installing 19.2 I did nothing to change anything in 19.2 ..
It is my understanding, per the 19.2 release notes, that 19.2 has an updated the kernel
I did nothing to alter the 19.2 386 base in any way, also 19.2 was installed
after wiping out the partition containing 19.1.it presently is just as I installed it from the iso file
anticapitalista
So are you using antiX-19.2 or 19.1 (base)?
There is a difference.It seems you used ceni to set up networking without doing what was suggested by caprea several posts ago.
http://www.antixforum.com/forums/topic/failing-with-liveusb-persistence/#post-32414
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
armando
try installing “broadcom-sta-dkms”
sudo apt install broadcom-sta-dkmsprobably has nothing to do, but your “hwinfo –wlan” in MX show the “wl” driver loaded for some reason.
Execute the command, restart. After restart check if the module is loaded with “lsmod | grep wl”. Connect and wait to see if that fix something.
If the drops continue or if broke your connection you can uninstall it with ‘sudo apt remove broadcom-sta-dkms’.So are you using antiX-19.2 or 19.1 (base)? There is a difference.
It seems you used ceni to set up networking without doing what was suggested by caprea several posts ago.
I believe I clarified three times that I’m currently running 19.2 -base -386.
I also made clear that connman is not part my installed 19.2-386-base.
And, when I try to run 19.2 ceni, it attempts to do to scan but sends back a error message indicating it failed.I also indicated that when I had 19.1 base installed (which contains connman)
that connman was able to connect, but not hold my wifi connection very longWhat about the various requested outputs that I submitted.. do they indicate what the problem might be ?
This may help..
here`s what happens when i run ceni > select “Hhardware interface” for “wireless” then select “Scan” (I’m not sure if I should select “Roam” instead )
driver does not support authen../assoc or connect commands nl80211 deinit ….
rfkill: WLAn soft locked…operation not possible due to RF-kill…Any ideas on how I can try armando`s suggestion without a wifi connect (19.2 live USB cant wifi connect) ?
- This reply was modified 6 years, 5 months ago by AA BB.
- This reply was modified 6 years, 5 months ago by AA BB.
armando
installing broadcom-sta-dkms requires to download about 2Mb
your iwconfig show that you are connected.
how do you connect in antix 19.2base?
- You must be logged in to reply to this topic.