wifi issue on CuBox-i4Pro
Home › Forums › GeeXboX on ARM SoCs › wifi issue on CuBox-i4Pro
Tagged: /etc/network2, CuBox-i4Pro, wifi, wlan0, wlan1 /etc/network
This topic contains 5 replies, has 3 voices, and was last updated by
tomlohave 3 months, 3 weeks ago.
-
AuthorPosts
-
Hi,
I’m still unable to get the integrated wifi of the CuBox-i4Pro running. I even wrote the following “script” to try various combinations of /etc/network2-combinations:
# cat wlan0_downup.sh #!/bin/bash vi /etc/network2 ifconfig wlan0 down ifconfig wlan0 up sleep 2 ifconfigCurrently I’m connected via cable (/etc/network-configuration file). Working perfectly.
I’m running a straight forward standard user environment with dhcp. So this is the current /etc/network2 what I think is correct:# cat /etc/network2 ENABLE="true" NETWORK_BACKEND="connman" NETWORK="WLAN" IFACE="B8:5A:F7:82:AB:A6" ADDRESS="" GATEWAY="" DNS_SERVER="" SSID="myWifisSSID" HIDDEN="" SECURITY="PSK" PASSPHRASE="passwordInCleartext"Nothing worked till now. So what else did I try?
* NETWORK_BACKEND => udhcpc # no change
* IFACE => wlan0 # currently using the wifis mac
* ADDRESS/GATEWAY/DNS_SERVER => to a static value
* SSID => I have two different wifis running, both don’t work
* SECURITY => also tried WPA and RSN (‘iwlist wlan0 scan’ showing PSK should be fine)
* PASSPHRASE => I just wrote the cleartext passwort here, tried nothing else
* executing ‘iwlist wlan0 scan’ shows all the available networks, so the kernel module is perfectly loaded everything should workMy Questions:
* I diagnosed the wifi is not working because ifconfig showed no ip-address for wlan0 => this assumption is correct, is it?
* I assume ‘ifconfig wlan0 down; ifconfig wlan0 up;’ reloads the config, correct?
* I assume it should be possible to get LAN and WLAN interface running at the same time? (with configuretion files /etc/network and /etc/network2)
* Do I have to transform the password (hash it or sth)?
* Are there any further logs from which I could get more information?Anyone having some suggestions how to get further with my problem?
greeeetz
There are problems running bluetooth and WiFi at the same time. Try to disable bluetooth by executing:
# systemctl mask bluetoothand reboot. If you use WPA2 on your network, select “RSN” security.
Hi Rudi,
thx for the answer, but didn’t help either… Tried various combinations of IFACE/SECURITY.
But I checked dmesg and for me it doesn’t look like bluetooth is disabled:
ystemd-udevd[159]: starting version 210 systemd-journald[148]: Received request to flush runtime journal from PID 1 cfg80211: Calling CRDA to update world regulatory domain ERROR: v4l2 capture: slave not found! ERROR: v4l2 capture: slave not found! brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 25 2011 19:34:12 version 5.90.125.104 brcmfmac: brcmf_fil_cmd_data: Failed err=-23 brcmfmac: brcmf_fil_cmd_data: Failed err=-23 brcmfmac: brcmf_fil_cmd_data: Failed err=-23 brcmfmac: brcmf_fil_cmd_data: Failed err=-23 fec 2188000.ethernet eth0: Freescale FEC PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1) brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists brcmfmac: brcmf_add_if: ignore IF event brcmfmac: brcmf_fil_cmd_data: Failed err=-23 brcmfmac: brcmf_construct_reginfo: channel 1: f=2412 bw=0 sb=-593183156 brcmfmac: brcmf_construct_reginfo: channel 2: f=2417 bw=0 sb=-593183156 Bluetooth: Core ver 2.16 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized libphy: 2188000.ethernet:00 - Link is Up - 1000/Full nr_pdflush_threads exported in /proc is scheduled for removal sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to [email protected].But before the whole dmesg has been full of bluetooth error messages, so sth changed…
greetz
Due to the line I mentioned the bluetooth hardware will not be initialized any more. However, some of the higher level components are still started. The ‘Failed err=-23′ messages are pretty much normal due to the sub-optimal state of the kernel driver. I use to connect to a WPA2 network:
NETWORK="WLAN" IFACE="wlan0" SECURITY="RSN" SSID="mySSID" HIDDEN="" PASSPHRASE="myPassphrase"Note, that I have added this to “/etc/network”, not “/etc/network2″.
OK, so I assumed the /etc/network2 file to work because it has been there from distribution side. But maybe that’s the problem!
Then the Question should be:
Is it possible to define two network interfaces and how is this done?
The other problem is, that it’s not really testable, because if i loose network connectivity due to the fact described in http://www.geexbox.org/forum/topic/cubox-i-terminal-access-problem/ => No network, no chance to configure anything… Anyone having a solution for this?btw: I tried a second network device (a TPLINK Wifi Dongle). ‘iwlist wlan1 scan’ showing all the networks, but configuring this is also not possible. Tried various combinations.
greetz
if you use connman, wired if used in place of wireless even if you configure only wireless … (with cable plugged, of )
It ‘s maybe time to switch to networkmanager. -
AuthorPosts
You must be logged in to reply to this topic.