Software Archive
Read-only legacy content
17061 Discussions

Edison Wifi connection very slow

Jagadeesh_D_
Beginner
915 Views

1. Edison, flashed with "edison-image-ww05-15" image.  uname -r gives 3.10.17-poky-edison+

2. iwconfig wlan0 power off to disable power management.  The systemctl start wifi-power-management-off does not work.

3. The connection over wired USB connection is just fine.  Both SSH and the serial connection is just fine. The ping latency is just fine < 10 ms.

4. Wifi is configured, wpa_supplicant is enabled to enable wifi automatically after every reboot.

5. Then disconnected the USB, reboot, trying to connect to Edison using Wifi

I am seeing the following problems,

a. The pings are very slow (@1.5seconds), missing few pings also.

b. The wlan0 power management is on (after reboot the setting is disabled).

c. The SSH connection establishment is too slow.

b. Every time the first character on the terminal is missing.

Please help to resolve these issues.

0 Kudos
5 Replies
samontab
Valued Contributor II
915 Views

Try setting up the device with:

configure_edison --setup

It should let you set the device name, password and wifi. Do this through the USB connection.

Also, make sure that you upgrade to the latest version with this:

configure_edison --upgrade

Check that you have the latest version with this:

configure_edison --version

And check the latest available version with this:

configure_edison --latest-version

 

0 Kudos
Jagadeesh_D_
Beginner
915 Views

Hi Samontab,

Appreciate the response.

The Wifi was configured using "configure_edison".

Also, in my system, the configure_edison --setup command does not work, see the response below.  Also, --version and --latest-version options also does not work in my system.  The version info is retrieve using uname -r and is posted in previous post.

root@myedison:~# configure_edison --upgrade

Incorrect input. Redirecting to --help

  Interactive configuration options:
    (none)                  Goes through changing the device name, password, and wifi options.
    --name or -n            Changes the device name
    --password or -p        Changes the device password
    --wifi or -w            Changes the wifi options

  Non-interactive configuration options
    --changePassword        Changes the device password to the following argument
    --changeName            Changes the device name to the following argument

  Other options
    --help or -h        Displays these help options
    --server            Starts the server (testing only)

- Thanks,

0 Kudos
Matthias_H_Intel
Employee
915 Views

could you pls repost on https://communities.intel.com/community/makers forum?

0 Kudos
Jagadeesh_D_
Beginner
915 Views

Thank you for all the guidance provided.

I was making a mistake when upgrading the flash to the latest image of Edison.

I was copying the correct files into the "Edison" drive, but was issuing the command "reboot" instead of "reboot ota".

Once I gave the correct command the system rebooted, the issues mentioned in this thread have gone away except disablement of wlan0 power management during reboot. 

I did copy the file as suggested in the Edison wifi user guide "create a file with the name wifi-power-management-off.service and save it in the /lib/systemd/system folder" with the script as suggested.  I will debug this further.

- Thanks,

 

 

0 Kudos
Stewart_C_Intel
Employee
915 Views

All of the symptoms you are seeing are indicative of a failed firmware upgrade, ie you are still running the original firmware.

The telltale piece is the missing --setup flag in the configure_edison command. An easier way to detect a successful reflash is to rename your board, before attempting.  The sign of a successful reflash is that your board name will be reset back to "Edison".

My recommendation is to run the board off a separate power supply, and to use both USB cables to setup the firmware reflash, and then remove the USB  cable that exports the Edison share drive, ie keep the serial port.  The issue with a failed reflash are many, but on-access virus scan, USB power negotiation and other things can affect this.

 

0 Kudos
Reply