That wlan problem (yet again)

  • This topic has 29 replies, 6 voices, and was last updated Dec 8-5:25 pm by caprea.
Viewing 15 posts - 16 through 30 (of 30 total)
  • Author
    Posts
  • #46071
    Member
    roland
      Helpful
      Up
      0
      ::

      network-inxi missing from above response

      Attachments:
      #46076
      Member
      Xecure
        Helpful
        Up
        0
        ::

        Great news you got it to work. Now you have a beast of a machine and working much better. And you got to solve it all yourself, so I can only say, Well done!

        If you see any other strange thing pop up, let us know and we will try helping as best we can.

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

        #46174
        Member
        roland
          Helpful
          Up
          0
          ::

          Bad news this morning, I gave it a 100gb SD to HD copy to be getting on with, to simulate hard work, and immediately the wlan and freezing problems returned.

          Ceni reported ‘unable to write a 300b packet to wlan – no buffer space’ several times during the linkup phase to the selected network, it did get there after 3 or 4 such holdups. Again this is with the interim Usb wlan adapter which I will replace as soon as the Pci-e wireless lan adapter arrives. I have never liked Usb adapters for some reason. Should I abandon Ceni and try either Wicd or Connman?

          Anything I tried to do has been punctuated by mouse pointer freezes, every 15 or 20 seconds, and lasting 30 to 60 seconds but quite variable, and always clearing itself after waiting. Conky shows the background jobs and networking to be running apparently normally in the background, and the folder copies I set running eventually completed as expected.

          At times a left mouse button press is not immediately accepted and acted upon, a second press usually gets it going.

          Any suggestions most welcome and will be carefully considered, and thanks for all previous contributions.

          #46185
          Moderator
          Brian Masinick
            Helpful
            Up
            0
            ::

            Wow, it’s difficult to know for certain, but I have experienced ‘odd’ symptoms on a few old relics and they turned out to be hardware issues.

            Such things, when there is a major delay indicates that an intended path can’t be followed. That could be a software defect and it could be a system defect in software or hardware.

            In the past I look at software to make sure that it’s doing what I intended, but sometimes it’s not clear. If another piece of equipment can be substituted that can confirm or eliminate hardware as the cause of the problem.

            --
            Brian Masinick

            #46200
            Member
            ModdIt
              Helpful
              Up
              0
              ::

              Maybe you could check your network coneection with nicstat, if the connection gets dropped and
              reconnected repeatedly it does really weird things to the system.

              #46212
              Member
              roland
                Helpful
                Up
                0
                ::

                I have another PC side by side with this one running 17.4.1 and they can use the same screen keyboard mouse and Usb wlan adapter. This forms a good control check, this second PC is dead stable and never gives a moments bother, as one expects from such a tried and tested release, Any problems I can mirror on this PC with reasonable confidence.

                I am fairly sure the freezing and rogue behaviour is related to local networking. This morning I had a 2-hour session with it, offline of course, copying across data from other PCs, I did not experience a single freeze nor even short pause, it ran like a very fast Rolls Royce. Connecting to the wlan immediately introduced the troubles again.

                I think it reasonable to wait until the requested Pci-e network card arrives, as that’s what the control PC has, then I can make more direct comparisons.

                I shall be surprised if it turns out that Ceni is to blame, as I have been using it since 13.0 with every confidence, and have had my fingers burned by Wicd in the past, and have no experience with Connman. But I have the option of installing either Wicd or Connman. If the problem then goes away, it was Ceni to blame, if it’s still there, the problem lies elsewhere.

                All suggestions are most welcome, and thanks in advance. The pic shows the offending PC.

                Attachments:
                #46214
                Moderator
                Brian Masinick
                  Helpful
                  Up
                  0
                  ::

                  One suggestion, in order to determine whether either Ceni or Connman work is to use the antix-wifi-switch script to switch between the two network manager programs. On;y one of them can be active at any given time, and this program will ensure that the network manager selected will be activated and the other one deactivated.
                  You can use this whenever you choose to switch between them, especially if one or the other is experiencing difficulty.

                  This may at least confirm whether either of them is responsible for any issue and it will also ensure that only one of them is running.
                  Who knows, maybe this will actually help, maybe it won’t, but it will certainly allow you to test both and make sure that there are no other network manager images running.

                  I hope we get lucky with this; if not, perhaps some hardware diagnostics would be another thing to try out to eliminate possible causes. Best wishes!

                  --
                  Brian Masinick

                  #46235
                  Member
                  roland
                    Helpful
                    Up
                    0
                    ::

                    This morning the new PC is running perfectly, after the hiccup I mentioned earlier regarding Ceni buffer space, but it does succeed in connecting after a few attempts (see screenshot).

                    I connected a brand-new keyboard when it arrived yesterday, Spanish layout but English text, and having had trouble with rogue keyboards in the past I do not rule out the keyboard I was using as the culprit. The one I was using was a very poor quality 5 euro one. Curiously the mainboard does nor recognise a PS/2 keyboard despite the socket being present, forcing me to use a Usb device. I will treat it to a brand-new wired Usb mouse as soon as possible.

                    But it is behaving perfectly as I type this message, with no pauses or hangs of any kind.

                    It is not super fast as the cpus I fitted are only relatively slow ex-server items, but when time and funds permit and I am satisfied with the entire build I may upgrade these to something more racy.

                    Thanks to all for your very helpful suggestions, and thanks to antiX forum.

                    #46255
                    Member
                    Xecure
                      Helpful
                      Up
                      0
                      ::

                      If the USB adapter isn’t faulty, it may be that you have two firmwares competing for the device (the libre firmware and the proprietary firmware; this device is one of the few that has a libre firmware). You will have to check
                      sudo dmesg | grep -i "ath9k\|0cf3:9271"
                      next time you have wifi issues. We may find some conflict there.

                      It is most definitely not ceni. Or connman for that matter. Nobody has asked for debug info but I a would guess it is a problem related to communicating the device with the kernel. You have got it to connect many times (and the wifi switch was tested), but the problem seems to be how the machine manages the connection (which lead to believe that it could be related to the wifi manager program).
                      Also, wicd is NOT included in any antiX 19 iso. There is wpa_gui and wpa_cli, but that doesn’t do nothing if not configured properly.

                      Hopefully the problem doesn’t pop up again before your new wifi pci device arrives.

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

                      #46769
                      Member
                      roland
                        Helpful
                        Up
                        0
                        ::

                        roland@antix1:~/Desktop
                        $ sudo dmesg | grep -i “ath9k\|0cf3:9271”
                        [sudo] password for roland:
                        Sorry, try again.
                        [sudo] password for roland:
                        [ 13.280651] usb 3-1.4: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw requested
                        [ 13.281375] usbcore: registered new interface driver ath9k_htc
                        [ 13.601771] usb 3-1.4: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.dev.0.fw, size: 51008
                        [ 13.864495] ath9k_htc 3-1.4:1.0: ath9k_htc: HTC initialized with 33 credits
                        [ 14.483269] ath9k_htc 3-1.4:1.0: ath9k_htc: FW Version: 1.4
                        [ 14.483273] ath9k_htc 3-1.4:1.0: FW RMW support: On
                        roland@antix1:~/Desktop
                        $
                        I now have no significant wifi troubles on this PC and the install has become stable. There is just one small annoyance, Ceni does not automatically run after a cold boot, I have to run it manually typing in the network key and using the paste option each time, after choosing the network from the list presented. Should I shift networking to another runlevel, at present it is in ‘S’? Which runlevel is recommended? The messages Ceni returns about shortage of buffer space and failing to send 300b packets do not seem to affect its ability to connect.

                        I have now installed 19.3 on another PC which I use intending to gain experience with Connman, but after using the wifi switch as suggested Connman simply failed to do anything after I entered the network name and key. What does ‘tethering’ refer to? No apparent attempt was made by Connman to make a connection although I could see my wlan in the list. I quickly switched to Ceni, which on this PC starts and runs autonomously and makes the connection seamlessly.

                        Once again thanks in advance for all suggestions and contributions, they are all most welcome.

                        #46776
                        Moderator
                        caprea
                          Helpful
                          Up
                          0
                          ::

                          Does your /etc/network/interfaces
                          look the same on both PCs ?

                          #46777
                          Member
                          Xecure
                            Helpful
                            Up
                            0
                            ::

                            There is just one small annoyance, Ceni does not automatically run after a cold boot, I have to run it manually typing in the network key and using the paste option each time, after choosing the network from the list presented

                            Some other systems also have experienced this, but I am not technically knwoledgeable enough to find a fix. What they did is switch to connman.
                            My best suggestion for continuing with ceni and not break what is already working is to create a small script with the code

                            #!/bin/bash
                            
                            gksu service networking restart

                            place it in the desktop, and click it and run it just after booting. It will restart the networking service and have ceni auto-connect. this way you don’t need to type the password each time.

                            About your USB wifi:

                            [ 13.280651] usb 3-1.4: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw requested

                            I don’t have this firmware on my antiX 19 (updated) box. In mine, the firmware is named htc_9271-1.4.0.fw from “firmware-atheros” package. Did you install your driver manually? Anyway, I wouldn’t do any more experiments until the next time it fails you. If it works stably now, better not touch it.

                            Connman has worked for me reliably on 3 devices, and all the troubles I got to create I documented in the video I uploaded to youtube.
                            Most of the problems will solve themselves if you run the wifi switch again to connman (when connman is misbehaving, use the wifi switch to again activate connman).
                            I cannot hep here, except if you can give a step by step explanation (if on antiX 19 base or full, must be specified).
                            For now, if you are happy with ceni, continue using it. There are two options for a reason, so use the one you are more comfortable with.

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

                            #46834
                            Member
                            roland
                              Helpful
                              Up
                              0
                              ::

                              Both PCs have antix 19 full. The one which runs Ceni after boot automatically has 19.3 fully up to date with antix wifi switch pointing at Ceni after Connman failed to work at all. This is the etc/network/interfaces file belonging to it.

                              auto lo
                              iface lo inet loopback

                              allow-hotplug wlan0
                              iface wlan0 inet dhcp
                              wpa-psk XXXXXXXX
                              wpa-ssid MIWIFI_qG6k

                              The one which fails to run Ceni after boot automatically has 19.2 with kernel 4.19.152 fully up to date with antix wifi switch pointing at Ceni after Connman also failed to work at all. This is the etc/network/interfaces file belonging to it.

                              auto lo
                              iface lo inet loopback

                              iface wlan0 inet dhcp
                              wpa-psk XXXXXXXX
                              wpa-ssid MIWIFI_qG6k

                              allow-hotplug eth0
                              iface eth0 inet dhcp

                              allow-hotplug eth1
                              iface eth1 inet dhcp

                              Maybe I should try removing the eth0 and eth1 bits and reboot?

                              • This reply was modified 2 years, 5 months ago by caprea. Reason: Removed psk-keys
                              • This reply was modified 2 years, 5 months ago by roland.
                              #46835
                              Member
                              Xecure
                                Helpful
                                Up
                                0
                                ::

                                There is little you can do, except if you can find what makes networking service load before everything else is ready for it to work. That is what I think is the reason for the system not connecting to ceni automatically in one computer, while in the other doesn’t have that problem. My guess is that it is related to that, the order of services loading. Most computers don’t have a problem, but some do, and that is with the exact same software installed. I tried exploring the order of things loaded by SysVinit (this is not the first time the issue with ceni not auto-connecting at boot comes up in the forum), but my knowledge is too limited and I don’t know how to proceed.

                                For now, create the script, make it executable, and use it after booting up. Except if someone can help guide you (I don’t know enough, so I am as blind as you in this respect) and find out how to change service order and give correct instructions, you are stuck with the workaround I provided. Sorry I cannot give any better solution. The only other solution I could give to the other ones that came with this issue was creating the antix-wifi-swicth to help prepare everything for connman, as I didn’t know how to help otherwise.

                                Also, edit the post and remove all the wpa-psk lines, as you don’t want a neighbor seeing it on the forum and stealing your wifi (or even worse, spying on your browsing).

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

                                #46847
                                Moderator
                                caprea
                                  Helpful
                                  Up
                                  0
                                  ::

                                  Yes, you posted your keys.

                                  The PC which connects automatically has set in ceni

                                  allow-hotplug wlan0

                                  I can’t remember exactly where this setting is in ceni, but it is there and you can try what happens if you set it for the other PC , too.

                                Viewing 15 posts - 16 through 30 (of 30 total)
                                • You must be logged in to reply to this topic.