manuti Posted July 21, 2016 Posted July 21, 2016 Finally I discover my Beelin X2 have a `8189es` so applying same firmware but change the bcmhd part by the 8189es all the tings go up. manuti@beelinkx2:~$ sudo modprobe 8189es firmware_path=/lib/firmware/ap6210/8189es.bin nvram_path=/lib/firmware/ap6210/nvram.txt manuti@beelinkx2:~$ lsmod Module Size Used by 8189es 1076034 0 mali_drm 2732 1 drm 178255 2 mali_drm mali 123208 0 ump 29379 3 mali sunxi_spdma 3703 1 sunxi_spdif 7037 1 sunxi_sndspdif 3885 0 sndspdif 2743 1 hid_logitech_dj 10040 0 manuti@beelinkx2:~$ sudo ifconfig wlan0 up manuti@beelinkx2:~$ sudo iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: xx:xx:xx:xx:xx:xx ESSID:"xxx" Thanks a lot to everybody. 1
jernej Posted July 21, 2016 Posted July 21, 2016 There is no need for arguments with 8189es driver. sudo modprobe 8189es Should be enough
Algi Zid Posted July 22, 2016 Posted July 22, 2016 Finally I discover my Beelin X2 have a `8189es` so applying same firmware but change the bcmhd part by the 8189es all the tings go up. manuti@beelinkx2:~$ sudo modprobe 8189es firmware_path=/lib/firmware/ap6210/8189es.bin nvram_path=/lib/firmware/ap6210/nvram.txt manuti@beelinkx2:~$ lsmod Module Size Used by 8189es 1076034 0 mali_drm 2732 1 drm 178255 2 mali_drm mali 123208 0 ump 29379 3 mali sunxi_spdma 3703 1 sunxi_spdif 7037 1 sunxi_sndspdif 3885 0 sndspdif 2743 1 hid_logitech_dj 10040 0 manuti@beelinkx2:~$ sudo ifconfig wlan0 up manuti@beelinkx2:~$ sudo iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: xx:xx:xx:xx:xx:xx ESSID:"xxx" Thanks a lot to everybody. Hello manuti How did you manage to run wifi?? i have the same problem, and for me that doesn't work i get wlan0: ERROR while getting interface flags: No such device
tkaiser Posted July 22, 2016 Posted July 22, 2016 Finally I discover my Beelin X2 have a `8189es` That means a new hardware revision is out since the older Beelink X2 are equipped with AP6181: http://linux-sunxi.org/images/1/19/X2_PCB_top.jpg(the device I have also has AP6181 but different DRAM modules compared to the wiki picture) Did you check which hardware revision you have? 1
manuti Posted July 22, 2016 Posted July 22, 2016 Hello manuti How did you manage to run wifi?? i have the same problem, and for me that doesn't work i get wlan0: ERROR while getting interface flags: No such device I download the firmware from the link from @slinde links in ths post: http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/page-3#entry11871 And I follow the instruction in this other post http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/page-3#entry12339 but changing all the references to bcmhd to 8189es. The Wi-Fi is up and running but I can't connect to my WPA2 !!! Only WEP!!! Any idea about this issue? Thanks.
slinde Posted July 22, 2016 Posted July 22, 2016 The Wi-Fi is up and running but I can't connect to my WPA2 !!! Only WEP!!! Any idea about this issue? I have no problems connecting to wpa2 using the following routine: First prepare a file with name wpa_supplicant.conf and the content like this (replace your own SSID and PSK): network={ ssid="XXXXXXX" psk="yyyyyyyy" scan_ssid=1 } Then issue the following commands: ifconfig wlan0 up wpa_supplicant -c wpa_supplicant.conf -i wlan0 & dhclient wlan0
manuti Posted July 22, 2016 Posted July 22, 2016 I have no problems connecting to wpa2 using the following routine: First prepare a file with name wpa_supplicant.conf and the content like this (replace your own SSID and PSK): network={ ssid="XXXXXXX" psk="yyyyyyyy" scan_ssid=1 } Then issue the following commands: ifconfig wlan0 up wpa_supplicant -c wpa_supplicant.conf -i wlan0 & dhclient wlan0 thanks slinde I give a try next week
manuti Posted July 22, 2016 Posted July 22, 2016 That means a new hardware revision is out since the older Beelink X2 are equipped with AP6181: http://linux-sunxi.org/images/1/19/X2_PCB_top.jpg(the device I have also has AP6181 but different DRAM modules compared to the wiki picture) Did you check which hardware revision you have? here you are the inside pictures of my Beelink X2 https://raspberryparatorpes.net/img_4155/ https://raspberryparatorpes.net/img_4156/ Thanks and I hope this can help.
Algi Zid Posted July 22, 2016 Posted July 22, 2016 That means a new hardware revision is out since the older Beelink X2 are equipped with AP6181: http://linux-sunxi.org/images/1/19/X2_PCB_top.jpg(the device I have also has AP6181 but different DRAM modules compared to the wiki picture) Did you check which hardware revision you have? Yeah, manuti and i, have different version of box (the newer one), to be exactly: x2_v3.1.1_20160224. I upload some photos of the box. The Wi-Fi chip is Realtek 8189ETV https://drive.google.com/open?id=0BwvVdWyZVml1NVRLaDcxckY2NDQ
slinde Posted July 22, 2016 Posted July 22, 2016 That means a new hardware revision is out since the older Beelink X2 are equipped with AP6181: http://linux-sunxi.org/images/1/19/X2_PCB_top.jpg(the device I have also has AP6181 but different DRAM modules compared to the wiki picture) Did you check which hardware revision you have? Indeed there are two different hardware versions. I have a total of three units of Beelink X2. The first two with serial numbers: X2H3CKFH1D054 and X2H3CKFH80684 have wifi chip that uses the brcmdhd driver. My newest third unit with serialnumber: A2H3CKHH71819 has wifi chip using the 8189es driver. There is no externally visible indication of HW version other than the serial number. I have not opened my units to have a look inside.
tkaiser Posted July 22, 2016 Posted July 22, 2016 "Wonderful", they simply exchanged the WiFi module between different PCB revisions. Do you both allow me to choose one of the images to upload it to linux-sunxi wiki? Maybe not only the WiFi module has been replaced but also pin mappings differ. Please read both through this commit log comment how to extract the original fex contents from eMMC (where an Android is living with correct settings for the new WiFi config I would suppose): https://github.com/linux-sunxi/sunxi-boards/commit/4a432501c910fddf759dd1171b15b0327b0d787a
tkaiser Posted July 22, 2016 Posted July 22, 2016 My newest third unit with serialnumber: A2H3CKHH71819 has wifi chip using the 8189es driver. And did it work by following the steps you posted above? I hope so since then we don't have to provide a newer fex variant (and different device tree settings later).
manuti Posted July 22, 2016 Posted July 22, 2016 "Wonderful", they simply exchanged the WiFi module between different PCB revisions. Do you both allow me to choose one of the images to upload it to linux-sunxi wiki? Maybe not only the WiFi module has been replaced but also pin mappings differ. Please read both through this commit log comment how to extract the original fex contents from eMMC (where an Android is living with correct settings for the new WiFi config I would suppose): https://github.com/linux-sunxi/sunxi-boards/commit/4a432501c910fddf759dd1171b15b0327b0d787a
manuti Posted July 22, 2016 Posted July 22, 2016 "Wonderful", they simply exchanged the WiFi module between different PCB revisions. Do you both allow me to choose one of the images toYes, you can take the pictures. I installed armbian in the eMMC so the Android has gone. Sorry.
slinde Posted July 22, 2016 Posted July 22, 2016 Regarding wifi on the newer version of Beelink X2 with the Realtek 8189ETV chip I manage to get it working (including wpa2) as follows: Upon boot the 8189es driver is loaded and can be seen with lsmod. For some reason there is no wifi interface wlan(x). For me it is sufficient to just do: rmmod 8189es modprobe 8189es Then I have the interface wlan3 and can configure it. See logfile for details: root@beelinkx2:~# lsmod Module Size Used by sunxi_spdma 3703 1 sunxi_spdif 7037 1 sunxi_sndspdif 3885 0 sndspdif 2743 1 8189es 1076034 0 root@beelinkx2:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 5e:a7:da:62:4d:67 brd ff:ff:ff:ff:ff:ff inet 192.168.1.137/24 brd 192.168.1.255 scope global eth0 inet6 2001:47:128:7ad:5ca7:daff:fe62:4d67/64 scope global dynamic valid_lft 86378sec preferred_lft 14378sec inet6 fe80::5ca7:daff:fe62:4d67/64 scope link valid_lft forever preferred_lft forever 3: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN group default link/ipip 0.0.0.0 brd 0.0.0.0 root@beelinkx2:~# rmmod 8189es root@beelinkx2:~# modprobe 8189es root@beelinkx2:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 5e:a7:da:62:4d:67 brd ff:ff:ff:ff:ff:ff inet 192.168.1.137/24 brd 192.168.1.255 scope global eth0 inet6 2001:47:128:7ad:5ca7:daff:fe62:4d67/64 scope global dynamic valid_lft 86386sec preferred_lft 14386sec inet6 fe80::5ca7:daff:fe62:4d67/64 scope link valid_lft forever preferred_lft forever 3: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN group default link/ipip 0.0.0.0 brd 0.0.0.0 20: wlan3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether cc:79:cf:54:cb:ac brd ff:ff:ff:ff:ff:ff root@beelinkx2:~# ifconfig wlan3 up root@beelinkx2:~# wpa_supplicant -c /opt/wpa_supplicant.conf -i wlan3 & [1] 1064 root@beelinkx2:~# Successfully initialized wpa_supplicant wlan3: Trying to associate with 14:cc:20:cb:a4:72 (SSID='XXXXX' freq=2437 MHz) wlan3: Associated with 14:cc:20:cb:a4:72 wlan3: WPA: Key negotiation completed with 14:cc:20:cb:a4:72 [PTK=CCMP GTK=CCMP] wlan3: CTRL-EVENT-CONNECTED - Connection to 14:cc:20:cb:a4:72 completed [id=0 id_str=] root@beelinkx2:~# dhclient wlan3 root@beelinkx2:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 5e:a7:da:62:4d:67 brd ff:ff:ff:ff:ff:ff inet 192.168.1.137/24 brd 192.168.1.255 scope global eth0 inet6 2001:47:128:7ad:5ca7:daff:fe62:4d67/64 scope global dynamic valid_lft 86380sec preferred_lft 14380sec inet6 fe80::5ca7:daff:fe62:4d67/64 scope link valid_lft forever preferred_lft forever 3: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN group default link/ipip 0.0.0.0 brd 0.0.0.0 20: wlan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether cc:79:cf:54:cb:ac brd ff:ff:ff:ff:ff:ff inet 192.168.1.138/24 brd 192.168.1.255 scope global wlan3 inet6 2001:47:128:7ad:ce79:cfff:fe54:cbac/64 scope global dynamic valid_lft 86380sec preferred_lft 14380sec inet6 fe80::ce79:cfff:fe54:cbac/64 scope link valid_lft forever preferred_lft forever
slinde Posted July 22, 2016 Posted July 22, 2016 Please read both through this commit log comment how to extract the original fex contents from eMMC (where an Android is living with correct settings for the new WiFi config I would suppose): https://github.com/linux-sunxi/sunxi-boards/commit/4a432501c910fddf759dd1171b15b0327b0d787a Is it safe to open up the case of Beelink X2 in order to attach a serial console? I have been avoiding opening mine up not to destroy the thermal pad between CPU and cooler. Will it come off?
tkaiser Posted July 22, 2016 Posted July 22, 2016 Is it safe to open up the case of Beelink X2 in order to attach a serial console? I have been avoiding opening mine up not to destroy the thermal pad between CPU and cooler. Will it come off? The thermal pad is not really adhesive, it will stick to either H3 or the large metal plate above, you can easily remove it. I ordered different thermal pads on Aliexpress today (to test some cooling variants with a few NanoPi that should soon arrive), then I'll open my Beelink again to use the rather thick thermal pad from there also for some comparisons regarding efficiency of heat dissipation. 1
Algi Zid Posted July 22, 2016 Posted July 22, 2016 Indeed there are two different hardware versions. I have a total of three units of Beelink X2. The first two with serial numbers: X2H3CKFH1D054 and X2H3CKFH80684 have wifi chip that uses the brcmdhd driver. My newest third unit with serialnumber: A2H3CKHH71819 has wifi chip using the 8189es driver. There is no externally visible indication of HW version other than the serial number. I have not opened my units to have a look inside. I confirm, A2 on the beginning inform of the 8189ETV chip inside, my serial number is A2H3CKHH7xxxx and also has 8189ETV
Algi Zid Posted July 22, 2016 Posted July 22, 2016 "Wonderful", they simply exchanged the WiFi module between different PCB revisions. Do you both allow me to choose one of the images to upload it to linux-sunxi wiki? Maybe not only the WiFi module has been replaced but also pin mappings differ. Please read both through this commit log comment how to extract the original fex contents from eMMC (where an Android is living with correct settings for the new WiFi config I would suppose): https://github.com/linux-sunxi/sunxi-boards/commit/4a432501c910fddf759dd1171b15b0327b0d787a yeah, take a pick one
timschuerewegen Posted July 23, 2016 Posted July 23, 2016 "Wonderful", they simply exchanged the WiFi module between different PCB revisions. Do you both allow me to choose one of the images to upload it to linux-sunxi wiki? Maybe not only the WiFi module has been replaced but also pin mappings differ. Please read both through this commit log comment how to extract the original fex contents from eMMC (where an Android is living with correct settings for the new WiFi config I would suppose): https://github.com/linux-sunxi/sunxi-boards/commit/4a432501c910fddf759dd1171b15b0327b0d787a I also have the newer revision (A2xxxxxxxx) and used a hex editor to extract the "config.fex" data from my eMMC backup. I hope this is what you wanted. beelink-x2-config.zip 2
Erik Posted July 24, 2016 Posted July 24, 2016 (edited) I have Lirc working on the Beelink X2.Also Suspend using systemd (using powerbutton and remote), also restore.Im working on making an accesspoint and wanted to change my ip to a static on (changed in interfaces).When i reboot i get the static ip-adres (192.168.1.150), but when the beelink wakes up, it uses a dhcp-lease (192.168.1.193).I did read some about problems with systemd on Arch Wiki, but not about this one. Start192.168.1.150Suspend/Resume192.168.1.193service networking restart --> changed on disk ??? systemctl daemon-reloadservice networking restart192.168.1.193service networking restart192.168.1.150 root@beelinkx2:~# cat /etc/network/interfaces# Wired adapter #1auto eth0iface eth0 inet static address 192.168.1.150 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.1 dns-search x.x # iface eth0 inet dhcp# hwaddress ether # if you want to set MAC manually# pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838## Wired adapter #2#auto eth1# iface eth1 inet dhcp# hwaddress ether # if you want to set MAC manually# pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838## Wireless adapter #1#auto wlan0# iface wlan0 inet dhcp# wpa-ssid SSID# wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx# to generate proper encrypted key: wpa_passphrase yourSSID yourpassword## Local loopbackauto lo iface lo inet loopbackroot@beelinkx2:~# syslog from service networking restart (first & second time) Jul 24 21:38:47 localhost systemd[1]: Stopping LSB: Raise network interfaces.... Jul 24 21:38:47 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:39:17 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:38:47 localhost dhclient: receive_packet failed on eth0: Network is down Jul 24 21:38:47 localhost networking[1633]: Deconfiguring network interfaces...done. Jul 24 21:38:47 localhost systemd[1]: Starting LSB: Raise network interfaces.... Jul 24 21:38:48 localhost kernel: [ 870.047072] gmac0: probed Jul 24 21:38:48 localhost kernel: [ 870.047543] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:38:48 localhost kernel: [ 870.068241] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:38:49 localhost systemd[1]: Reloading OpenBSD Secure Shell server. Jul 24 21:38:49 localhost systemd[1]: Reloaded OpenBSD Secure Shell server. Jul 24 21:38:49 localhost networking[1673]: Configuring network interfaces...done. Jul 24 21:38:49 localhost systemd[1]: Started LSB: Raise network interfaces.. Jul 24 21:38:49 localhost ntpd[629]: Listen normally on 8 eth0 192.168.1.150 UDP 123 Jul 24 21:38:49 localhost ntpd[629]: Deleting interface #7 eth0, 192.168.1.193#123, interface stats: received=48, sent=48, dropped=1, active_time=785 secs Jul 24 21:38:49 localhost ntpd[629]: 213.239.154.12 interface 192.168.1.193 -> (none) Jul 24 21:38:49 localhost ntpd[629]: 93.94.224.67 interface 192.168.1.193 -> (none) Jul 24 21:38:49 localhost ntpd[629]: 146.185.139.19 interface 192.168.1.193 -> (none) Jul 24 21:38:49 localhost ntpd[629]: 212.45.45.45 interface 192.168.1.193 -> (none) Jul 24 21:38:49 localhost ntpd[629]: Deleting interface #6 eth0, fe80::85a:eff:fee7:cd53#123, interface stats: received=0, sent=0, dropped=0, active_time=788 secs Jul 24 21:38:49 localhost ntpd[629]: peers refreshed Jul 24 21:38:51 localhost dhclient: Killed old client process Jul 24 21:38:52 localhost kernel: [ 874.040376] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:38:52 localhost kernel: [ 874.043435] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:38:52 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:38:52 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:38:52 localhost dhclient: All rights reserved. Jul 24 21:38:52 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:38:52 localhost dhclient: Jul 24 21:38:52 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:38:52 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:38:52 localhost dhclient: Sending on Socket/fallback Jul 24 21:38:53 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:38:53 localhost kernel: [ 874.922021] gmac0: probed Jul 24 21:38:53 localhost kernel: [ 874.922347] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:38:53 localhost kernel: [ 874.935452] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:38:53 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:38:53 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:38:53 localhost dhclient: All rights reserved. Jul 24 21:38:53 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:38:53 localhost dhclient: Jul 24 21:38:53 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:38:53 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:38:53 localhost dhclient: Sending on Socket/fallback Jul 24 21:38:53 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:38:53 localhost dhclient: send_packet: Network is unreachable Jul 24 21:38:53 localhost dhclient: send_packet: please consult README file regarding broadcast address. Jul 24 21:38:53 localhost dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface. Jul 24 21:38:54 localhost kernel: [ 875.596679] gmac0: probed Jul 24 21:38:54 localhost kernel: [ 875.597002] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:38:54 localhost kernel: [ 875.610173] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:38:55 localhost ntpd[629]: Deleting interface #8 eth0, 192.168.1.150#123, interface stats: received=4, sent=4, dropped=0, active_time=6 secs Jul 24 21:38:55 localhost ntpd[629]: 213.239.154.12 interface 192.168.1.150 -> (none) Jul 24 21:38:55 localhost ntpd[629]: 93.94.224.67 interface 192.168.1.150 -> (none) Jul 24 21:38:55 localhost ntpd[629]: 146.185.139.19 interface 192.168.1.150 -> (none) Jul 24 21:38:55 localhost ntpd[629]: 212.45.45.45 interface 192.168.1.150 -> (none) Jul 24 21:38:55 localhost ntpd[629]: peers refreshed Jul 24 21:38:58 localhost kernel: [ 879.590422] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:38:58 localhost kernel: [ 879.593452] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:38:59 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:38:59 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:38:59 localhost dhclient: All rights reserved. Jul 24 21:38:59 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:38:59 localhost dhclient: Jul 24 21:38:59 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:38:59 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:38:59 localhost dhclient: Sending on Socket/fallback Jul 24 21:38:59 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:38:59 localhost dhclient: send_packet: Network is unreachable Jul 24 21:38:59 localhost dhclient: send_packet: please consult README file regarding broadcast address. Jul 24 21:38:59 localhost dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface. Jul 24 21:39:00 localhost kernel: [ 881.656278] gmac0: probed Jul 24 21:39:00 localhost kernel: [ 881.656600] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:39:00 localhost kernel: [ 881.669804] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:39:00 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:39:00 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:39:00 localhost dhclient: All rights reserved. Jul 24 21:39:00 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:39:00 localhost dhclient: Jul 24 21:39:00 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:39:00 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:39:00 localhost dhclient: Sending on Socket/fallback Jul 24 21:39:00 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:39:00 localhost dhclient: send_packet: Network is unreachable Jul 24 21:39:00 localhost dhclient: send_packet: please consult README file regarding broadcast address. Jul 24 21:39:00 localhost dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface. Jul 24 21:39:00 localhost kernel: [ 882.215188] gmac0: probed Jul 24 21:39:00 localhost kernel: [ 882.215511] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:39:00 localhost kernel: [ 882.228676] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:39:02 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:39:02 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:39:02 localhost dhclient: All rights reserved. Jul 24 21:39:02 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:39:02 localhost dhclient: Jul 24 21:39:03 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:39:03 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:39:03 localhost dhclient: Sending on Socket/fallback Jul 24 21:39:03 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 Jul 24 21:39:04 localhost kernel: [ 886.210695] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:39:04 localhost kernel: [ 886.213723] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:39:07 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Jul 24 21:39:07 localhost ntpd[629]: Listen normally on 9 eth0 fe80::85a:eff:fee7:cd53 UDP 123 Jul 24 21:39:07 localhost ntpd[629]: peers refreshed Jul 24 21:39:09 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 24 21:39:09 localhost dhclient: DHCPOFFER from 192.168.1.1 Jul 24 21:39:09 localhost dhclient: DHCPACK from 192.168.1.1 Jul 24 21:39:09 localhost dhclient: bound to 192.168.1.193 -- renewal in 34135 seconds. Jul 24 21:39:10 localhost ntpd[629]: Listen normally on 10 eth0 192.168.1.193 UDP 123 Jul 24 21:39:10 localhost ntpd[629]: peers refreshed Jul 24 21:39:14 localhost kernel: [ 896.350096] eth0: no IPv6 routers present Jul 24 21:39:48 localhost systemd[1]: Starting Cleanup of Temporary Directories... Jul 24 21:39:48 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:40:18 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:39:48 localhost systemd[1]: Started Cleanup of Temporary Directories. Jul 24 21:40:58 localhost systemd[1]: Reloading. Jul 24 21:40:58 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:41:28 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:40:59 localhost systemd[1]: Started ACPI event daemon. Jul 24 21:40:59 localhost systemd[1]: Listening on ACPID Listen Socket. Jul 24 21:40:59 localhost systemd[1]: Mounted /. Jul 24 21:41:02 localhost systemd[1]: Stopping LSB: Raise network interfaces.... Jul 24 21:41:02 localhost dhclient: receive_packet failed on eth0: Network is down Jul 24 21:41:02 localhost networking[2006]: Deconfiguring network interfaces...done. Jul 24 21:41:03 localhost systemd[1]: Starting LSB: Raise network interfaces.... Jul 24 21:41:03 localhost kernel: [ 1005.415262] gmac0: probed Jul 24 21:41:03 localhost kernel: [ 1005.415732] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:41:03 localhost kernel: [ 1005.435620] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:41:04 localhost systemd[1]: Reloading OpenBSD Secure Shell server. Jul 24 21:41:04 localhost systemd[1]: Reloaded OpenBSD Secure Shell server. Jul 24 21:41:04 localhost networking[2046]: Configuring network interfaces...done. Jul 24 21:41:04 localhost systemd[1]: Started LSB: Raise network interfaces.. Jul 24 21:41:05 localhost ntpd[629]: Listen normally on 11 eth0 192.168.1.150 UDP 123 Jul 24 21:41:05 localhost ntpd[629]: Deleting interface #10 eth0, 192.168.1.193#123, interface stats: received=7, sent=7, dropped=0, active_time=115 secs Jul 24 21:41:05 localhost ntpd[629]: 213.239.154.12 interface 192.168.1.193 -> (none) Jul 24 21:41:05 localhost ntpd[629]: 93.94.224.67 interface 192.168.1.193 -> (none) Jul 24 21:41:05 localhost ntpd[629]: 146.185.139.19 interface 192.168.1.193 -> (none) Jul 24 21:41:05 localhost ntpd[629]: 212.45.45.45 interface 192.168.1.193 -> (none) Jul 24 21:41:05 localhost ntpd[629]: Deleting interface #9 eth0, fe80::85a:eff:fee7:cd53#123, interface stats: received=0, sent=0, dropped=0, active_time=118 secs Jul 24 21:41:05 localhost ntpd[629]: peers refreshed Jul 24 21:41:07 localhost dhclient: Killed old client process Jul 24 21:41:07 localhost kernel: [ 1009.410329] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:41:07 localhost kernel: [ 1009.411195] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:41:08 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:41:08 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:41:08 localhost dhclient: All rights reserved. Jul 24 21:41:08 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:41:08 localhost dhclient: Jul 24 21:41:08 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:08 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:08 localhost dhclient: Sending on Socket/fallback Jul 24 21:41:09 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:41:09 localhost kernel: [ 1010.745495] gmac0: probed Jul 24 21:41:09 localhost kernel: [ 1010.745819] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:41:09 localhost kernel: [ 1010.758891] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:41:09 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:41:09 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:41:09 localhost dhclient: All rights reserved. Jul 24 21:41:09 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:41:09 localhost dhclient: Jul 24 21:41:09 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:09 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:09 localhost dhclient: Sending on Socket/fallback Jul 24 21:41:09 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:41:09 localhost dhclient: send_packet: Network is unreachable Jul 24 21:41:09 localhost dhclient: send_packet: please consult README file regarding broadcast address. Jul 24 21:41:09 localhost dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface. Jul 24 21:41:09 localhost kernel: [ 1011.425388] gmac0: probed Jul 24 21:41:09 localhost kernel: [ 1011.425715] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:41:09 localhost kernel: [ 1011.438852] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:41:11 localhost ntpd[629]: Deleting interface #11 eth0, 192.168.1.150#123, interface stats: received=4, sent=4, dropped=0, active_time=6 secs Jul 24 21:41:11 localhost ntpd[629]: 213.239.154.12 interface 192.168.1.150 -> (none) Jul 24 21:41:11 localhost ntpd[629]: 93.94.224.67 interface 192.168.1.150 -> (none) Jul 24 21:41:11 localhost ntpd[629]: 146.185.139.19 interface 192.168.1.150 -> (none) Jul 24 21:41:11 localhost ntpd[629]: 212.45.45.45 interface 192.168.1.150 -> (none) Jul 24 21:41:11 localhost ntpd[629]: peers refreshed Jul 24 21:41:13 localhost kernel: [ 1015.420903] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:41:13 localhost kernel: [ 1015.423919] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:41:15 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:41:15 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:41:15 localhost dhclient: All rights reserved. Jul 24 21:41:15 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:41:15 localhost dhclient: Jul 24 21:41:15 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:15 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:15 localhost dhclient: Sending on Socket/fallback Jul 24 21:41:15 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:41:15 localhost dhclient: send_packet: Network is unreachable Jul 24 21:41:15 localhost dhclient: send_packet: please consult README file regarding broadcast address. Jul 24 21:41:15 localhost dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface. Jul 24 21:41:16 localhost kernel: [ 1017.655962] gmac0: probed Jul 24 21:41:16 localhost kernel: [ 1017.656284] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:41:16 localhost kernel: [ 1017.669483] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:41:16 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:41:16 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:41:16 localhost dhclient: All rights reserved. Jul 24 21:41:16 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:41:16 localhost dhclient: Jul 24 21:41:16 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:16 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:16 localhost dhclient: Sending on Socket/fallback Jul 24 21:41:16 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67 Jul 24 21:41:16 localhost dhclient: send_packet: Network is unreachable Jul 24 21:41:16 localhost dhclient: send_packet: please consult README file regarding broadcast address. Jul 24 21:41:16 localhost dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface. Jul 24 21:41:16 localhost kernel: [ 1018.245027] gmac0: probed Jul 24 21:41:16 localhost kernel: [ 1018.245350] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:41:16 localhost kernel: [ 1018.258578] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:41:18 localhost dhclient: Internet Systems Consortium DHCP Client 4.3.1 Jul 24 21:41:18 localhost dhclient: Copyright 2004-2014 Internet Systems Consortium. Jul 24 21:41:18 localhost dhclient: All rights reserved. Jul 24 21:41:18 localhost dhclient: For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url] Jul 24 21:41:18 localhost dhclient: Jul 24 21:41:18 localhost dhclient: Listening on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:18 localhost dhclient: Sending on LPF/eth0/0a:5a:0e:e7:cd:53 Jul 24 21:41:18 localhost dhclient: Sending on Socket/fallback Jul 24 21:41:18 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 Jul 24 21:41:20 localhost kernel: [ 1022.240379] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:41:20 localhost kernel: [ 1022.243487] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:41:23 localhost ntpd[629]: Listen normally on 12 eth0 fe80::85a:eff:fee7:cd53 UDP 123 Jul 24 21:41:23 localhost ntpd[629]: peers refreshed Jul 24 21:41:23 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 Jul 24 21:41:25 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 24 21:41:25 localhost dhclient: DHCPOFFER from 192.168.1.1 Jul 24 21:41:25 localhost dhclient: DHCPACK from 192.168.1.1 Jul 24 21:41:26 localhost dhclient: bound to 192.168.1.193 -- renewal in 35995 seconds. Jul 24 21:41:27 localhost ntpd[629]: Listen normally on 13 eth0 192.168.1.193 UDP 123 Jul 24 21:41:27 localhost ntpd[629]: peers refreshed Jul 24 21:41:31 localhost kernel: [ 1033.210109] eth0: no IPv6 routers present Jul 24 21:41:31 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:42:01 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:44:13 localhost systemd[1]: Stopping LSB: Raise network interfaces.... Jul 24 21:44:13 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:44:43 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:44:13 localhost dhclient: receive_packet failed on eth0: Network is down Jul 24 21:44:13 localhost networking[2379]: Deconfiguring network interfaces...done. Jul 24 21:44:13 localhost systemd[1]: Starting LSB: Raise network interfaces.... Jul 24 21:44:14 localhost kernel: [ 1196.098957] gmac0: probed Jul 24 21:44:14 localhost kernel: [ 1196.099278] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00) Jul 24 21:44:14 localhost kernel: [ 1196.112719] ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 24 21:44:14 localhost systemd[1]: Reloading OpenBSD Secure Shell server. Jul 24 21:44:14 localhost systemd[1]: Reloaded OpenBSD Secure Shell server. Jul 24 21:44:15 localhost networking[2419]: Configuring network interfaces...done. Jul 24 21:44:15 localhost systemd[1]: Started LSB: Raise network interfaces.. Jul 24 21:44:15 localhost ntpd[629]: Listen normally on 14 eth0 192.168.1.150 UDP 123 Jul 24 21:44:15 localhost ntpd[629]: Deleting interface #13 eth0, 192.168.1.193#123, interface stats: received=8, sent=8, dropped=0, active_time=168 secs Jul 24 21:44:15 localhost ntpd[629]: 213.239.154.12 interface 192.168.1.193 -> (none) Jul 24 21:44:15 localhost ntpd[629]: 93.94.224.67 interface 192.168.1.193 -> (none) Jul 24 21:44:15 localhost ntpd[629]: 146.185.139.19 interface 192.168.1.193 -> (none) Jul 24 21:44:15 localhost ntpd[629]: 212.45.45.45 interface 192.168.1.193 -> (none) Jul 24 21:44:15 localhost ntpd[629]: Deleting interface #12 eth0, fe80::85a:eff:fee7:cd53#123, interface stats: received=0, sent=0, dropped=0, active_time=172 secs Jul 24 21:44:15 localhost ntpd[629]: peers refreshed Jul 24 21:44:18 localhost kernel: [ 1200.091009] PHY: gmac0-0:00 - Link is Up - 100/Full Jul 24 21:44:18 localhost kernel: [ 1200.094182] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 24 21:44:21 localhost ntpd[629]: Listen normally on 15 eth0 fe80::85a:eff:fee7:cd53 UDP 123 Jul 24 21:44:21 localhost ntpd[629]: peers refreshed Jul 24 21:44:29 localhost kernel: [ 1210.640118] eth0: no IPv6 routers present Jul 24 21:45:59 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:46:29 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:45:59 localhost systemd[1]: Starting Session 3 of user root. Jul 24 21:45:59 localhost systemd[1]: Started Session 3 of user root. Jul 24 21:47:37 localhost systemd[1]: Time has been changed Jul 24 21:47:37 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Sun Jul 24 21:48:07 2016 [try [url=http://www.rsyslog.com/e/2007]http://www.rsyslog.com/e/2007[/url] ] Jul 24 21:47:37 localhost systemd[1021]: Time has been changed Jul 24 21:47:37 localhost systemd[898]: Time has been changed root@beelinkx2:/var/log# Any ideas? Edited July 28, 2016 by zador.blood.stained Added spoiler and code tags
Erik Posted July 25, 2016 Posted July 25, 2016 I did clear network manager in the GUI. The result is that i have now NO ip-adres after suspend-resume. If i do a service networking restart - then the network is restarted correctly. If i do a systemctl daemon-reload and then a service networking restart. Then there are some daemons disturbed - lirc will stop working correctly. So i think not all services are resumed correctly after a suspend restore.
Algi Zid Posted July 27, 2016 Posted July 27, 2016 I download the firmware from the link from @slinde links in ths post: http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/page-3#entry11871 And I follow the instruction in this other post http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/page-3#entry12339 but changing all the references to bcmhd to 8189es. The Wi-Fi is up and running but I can't connect to my WPA2 !!! Only WEP!!! Any idea about this issue? Thanks. On my 4G router, i can only choose unsecured or WPA1 or 2. WPA 1 or 2 doesn't work: always get Bad Password info... But when i choose Unsecured then works like a charm ;/ Soo same problem like yours, did you resolve problem?
manuti Posted July 27, 2016 Posted July 27, 2016 On my 4G router, i can only choose unsecured or WPA1 or 2. WPA 1 or 2 doesn't work: always get Bad Password info... But when i choose Unsecured then works like a charm ;/ Soo same problem like yours, did you resolve problem? Yes, same problem here. Not resolved. But for now I didn't tested the plain text config, wpa-suplicant, suggested by slunde. I don't have enough time test.
Algi Zid Posted July 28, 2016 Posted July 28, 2016 Yes, same problem here. Not resolved. But for now I didn't tested the plain text config, wpa-suplicant, suggested by slunde. I don't have enough time test. I'm tested, and nothing change. Still had info about bad password. So i'm burn staright to sdcard, img from orangepi site (Debian 8 Jessie) and it works from a start. i get cpufreq err only, but it works.
slinde Posted July 29, 2016 Posted July 29, 2016 I'm tested, and nothing change. Still had info about bad password. So i'm burn staright to sdcard, img from orangepi site (Debian 8 Jessie) and it works from a start. i get cpufreq err only, but it works. Do you have any exotic characters in your password that might be a problem? As I have said in previous postings I have no problems connecting to my wifi with wpa security. But my password consists only of lowercase a-z letters and a _ sign.
manuti Posted July 29, 2016 Posted July 29, 2016 Do you have any exotic characters in your password that might be a problem? As I have said in previous postings I have no problems connecting to my wifi with wpa security. But my password consists only of lowercase a-z letters and a _ sign. Nop, I don't use spanish (easy for me to include) characters like Ñ ñ is more or less plain than your password. Thanks @slinde I don't have time to test in nexts weeks, so don't worry about this. I found another thread http://forum.armbian.com/index.php/topic/1713-orange-pi-lite-wifi-cannot-connect-to-wpa/andmaybe it is related to the same problem with some installations.
Algi Zid Posted July 29, 2016 Posted July 29, 2016 Nop, I don't use spanish (easy for me to include) characters like Ñ ñ is more or less plain than your password. Thanks @slinde I don't have time to test in nexts weeks, so don't worry about this. I found another thread http://forum.armbian.com/index.php/topic/1713-orange-pi-lite-wifi-cannot-connect-to-wpa/andmaybe it is related to the same problem with some installations. manuti, i found a solution. After add firmware from slinde link and root@beelinkx2:~# rmmod 8189es root@beelinkx2:~# modprobe 8189es i go to Wicd Network Manager -> refresh network, and select my wifi. Next go to properties and paste my password for wifi, click ok and try Connect. Get as usual info about Bad password. Then a click Preferences (right upper corner=triangle) ->advanced ->wpa supplicant and select driver from wext to none. Then Connect to wifi and voila. Connection established and working. Next step is need to modify modules.conf sudo nano /etc/modules-load.d/modules.conf change "bcmdhd" to" #bcmdhd" and add a line 8189es save the file and reboot. After system bootup wait a 30s, and the connection to wifi automatically up and running.
mdel Posted August 3, 2016 Posted August 3, 2016 i'm a bit at a loss here, i can't get my beelink x2 to boot current armbian images, i feel i've missed something obvious. i've downloaded the 5.14 armbian images for jessie desktop and xenial server, flashed them with dd in linux, plugged the sdcard and then power. The led turns instantly blue ("on", stays red whithout sdcard) but nothing seems to happen, no video output, no eth link. In my memory i have not tempered with that beelink x2 much, probably only installed a different version of kodi in android, and haven't used it in a while. Android still boots fine and the sd card can be browsed in the file manager (plugged after android boot). I'm using a 32G Samsung Evo HC1, i'll try another one. thx
Algi Zid Posted August 3, 2016 Posted August 3, 2016 i'm a bit at a loss here, i can't get my beelink x2 to boot current armbian images, i feel i've missed something obvious. i've downloaded the 5.14 armbian images for jessie desktop and xenial server, flashed them with dd in linux, plugged the sdcard and then power. The led turns instantly blue ("on", stays red whithout sdcard) but nothing seems to happen, no video output, no eth link. In my memory i have not tempered with that beelink x2 much, probably only installed a different version of kodi in android, and haven't used it in a while. Android still boots fine and the sd card can be browsed in the file manager (plugged after android boot). I'm using a 32G Samsung Evo HC1, i'll try another one. thx Hello. Yeserday i'm install armbian from scratch. Everything is fine. So try rufus software for win or different sd-card (U1 is recommended but Class4 works to) or different pc. Cya
Recommended Posts