slinde

May 7, 2017

Often the problem with executing scripts fron cron or att system startup is that the environment is more limited than when you are logged in at the prompt.

Try giving full paths to your commands. If you don't know the paths ypu can find out with the 'which' command.

If for example:

which rtl_fm

returns something like /some/path/rtl_fm

Then you put in your script /some/path/rtl_fm instead of just the short rtl_fm command. Do the same for direwolf command.

December 21, 2016

I experienced a problem with my Beelink X2 yesterday. I could repeat the problem on a fresh install.

If I install my Beelink X2 with the file "Armbian_5.20_Beelinkx2_Debian_jessie_3.4.112.7z" from the download area everything works fine. But if I then do an apt-get update/apt-get upgrade the system will not boot anymore.

Is this a known problem? Is there a fix?

I have the first version of Beelink X2 with serial number X2H3CKFH1****. The packages I installed in the update was:

Start-Date: 2016-12-21  00:42:08
Commandline: apt-get upgrade
Upgrade: tzdata:armhf (2016f-0+deb8u1, 2016j-0+deb8u1), armbian-firmware:armhf (
5.20, 5.22), linux-headers-sun8i:armhf (5.20, 5.23), hostapd:armhf (2.5~armbian5
.20+1, 2.5~armbian5.24.161202+1), linux-image-sun8i:armhf (5.20, 5.23), linux-je
ssie-root-beelinkx2:armhf (5.20, 5.23), sunxi-tools:armhf (1.3-1~armbian5.20+1,
1.4.1-1~armbian5.24.161202+1), linux-u-boot-beelinkx2-default:armhf (5.20, 5.23)
End-Date: 2016-12-21  00:45:48

December 12, 2016

Did you enable ip forwarding in the kernel?

December 4, 2016

I did but it does not work.

That file is:

#!/bin/sh -e

#

# rc.local

#

# This script is executed at the end of each multiuser runlevel.

# Make sure that the script will "exit 0" on success or any other

# value on error.

#

# In order to enable or disable this script just change the execution

# bits.

#

# By default this script does nothing.

/root/jivelite/bin/jivelite

exit 0

Maybe the PATH in environment is not sufficient at system start. When you are logged in as root check your environment wit the command:

env

Find the line that starts with "PATH="

Copy that line and paste it into the file /etc/rc.local above your "/root/jivelite/bin/jivelite" line.

Then add a line:

export PATH

between the "PATH=" line and the "/root/jivelite/bin/jivelite" line.

So the end of your rc.local should look similar to:

# By default this script does nothing.

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

export PATH

/root/jivelite/bin/jivelite

exit 0

But it is important that you replace the PATH example above with your real PATH from your system.

December 4, 2016

Put your command in the file /etc/rc.local.

Put it on a new line just above the "exit 0" line.

November 9, 2016

Has this happened to anyone yet? Have internet but then have no connection?

If you have that problem you should check your routes and DNS settings.

October 28, 2016

I have a Raspberry Pi model B with Raspbian running in a server hall with UPS-power. It has been up over two years now:

root@halo:~# uptime
 02:36:39 up 758 days, 16:40,  1 user,  load average: 0.21, 0.25, 0.57
root@halo:~#

I also have 2-3 Seagate Dockstars with Debian running for months and years as long as there is no power interruption.

I have not been using Armbian for more than a few months but my Beelink X2:s and Orange Pi PC:s with Armbian also runs for months without problems.

So I think there are lot of hardware you can choose from. As long as you choose a reliable brand of SD-card the hardware is in my experience seldom a problem. You have to be more careful with other things such as configuration and power supply.

October 22, 2016

I noticed on my Orange Pi PC that if I unplug an USB harddisk the system becomes erratic and stops responding.

I believe it's a power issue like on the first Raspberry Pi where you can't unplug or plug in USB items without causing a reboot.

Have you tried connecting the disks through a powered USB hub?

October 4, 2016

e) Eagerly wait for an install/boot process that does not rely on sdcards, perhaps using fel and usb cables. Or possibly Orange will release boards with small nand chips so that a small boot linux can be used which enables ftp/http installs.

Well, I am totally happy with installing from SD-cards. I have done several dozens of installations, starting out with Raspberry Pi and lately gone into Orange Pi PC/Beelink X2 with Armbian. I have rarely ever had any problems with SD-card installation.

To me it seems more awkward bringing out special cables instead of just flashing an SD-card and away you go. If your hardware is in order and you use quality SD-cards (Samsung) you will very seldom have any troubles with using SD-cards.

September 25, 2016

I have Beelink x2 and there no video on the screen (no signal) does

Armbian_5.20_Beelinkx2_Debian_jessie_3.4.112 will make my x2 work? where can i download it?

What is the serial number of your Beelink X2? (Can be seen on sticker underneath.)

September 24, 2016

You do not need to format the SD-card. Just write the image file to the SD-card with an appropriate software like Etcher or Win32diskimager in Windows or dd if you are using Linux.

When you write the image to the SD-card you over-write any formatting previously done.

September 18, 2016

Sorry for a noob question, when you say SSH or Ping how can I do that without a network connection

I assume you have a home network and a router?

When the Beelink X2 boots it tries to get an IP-address from your router. You can enter the routers menu and check which IP-address is assigned to the Beelink X2. Check for DHCP client list or similar in the router menu.

When you know the IP-address of the Beelink X2 you can try to reach it from another computer in your home network for example your desktop PC. Ping is a command that checks if there is network connectivity between two computers. Ssh is a way of remotely logging in to another computer. Armbian is by default configured so that you can connect to it via ssh.

September 18, 2016

Maybe there is some difference in the hardware between A2H3CKHH***** and A2H3CKIG***** that Armbian is not aware of yet?

September 18, 2016

Hi assuming the serial number is from the bottom of the plastic casing, I have two X2 box's

S/N X2H3CACG10156

S/N A2H3CKIG40374

Thanks

That seems to correspond to the same two versions I have. The X2H3**** is the older version using the brcmdhd wifi driver. The A2H3**** is a newer version using the 8189es wifi driver. Both of these should run perfectly with Armbian.

I always run my Beelink X2:s headless without display and keyboard, just using ssh to login to commandline so I don't really know if there is som kind of problem with the display output. I guess I have to test that some day.

When you say the second boot fails, have you tested to see if it responds to ping? Did you try to login via ssh? Do you have anything connected to the USB ports when it fails?

September 17, 2016

Hi - Have being trying a number of different images for the H3 CPU on the beelink X2, the Nanopi-m1 Ubuntu Mate image boots up and works although no WIFI etc- I have finally tried the Armbian beelink X2 image and although initially it loads up, it fails on second boot with no output with a purple/blue light on the box.

Wondering if anyone has a fix or if their is just to many variants of the X2 board for it to work every time.

Thanks for your time

I have two different HW versions of Beelink X2 and both work just fine with Armbian. Maybe you have another (newer) version? What is the first nine characters in your serial number?

September 14, 2016

Gearbest sell these at good prices on a regular basis. I have bought some at $6.99 as best.

So far I can tell they are genuine Samsung cards.

September 10, 2016

Had a bit of time today to do testing.

Downloaded a fresh copy of the Beelink X2 Jessie server image file Armbian_5.14_Beelinkx2_Debian_jessie_3.4.112.7z. Unpacked it and burnt to a micro-SD card. Put the card in my Beelink X2 and switched the power on. The only thing connected to the Beelink X2 is power and network cable.

Of course it booted just as expected and performed the dual boot it should do on first boot. So there is no fault in the ARMbian image file.

Here are my observations of the LED behaviour. By LAN led I mean the led on the switch port my Beelink X2 is connected to. I find observing the led on the switch to be the best way to know what is happening.

1st boot:

solid purple

solid blue

LAN led on

flashing blue/purple

LAN led off

flashing red/blue

2nd boot:

solid purple

solid blue

LAN led on

flashing blue

solid blue

ready to log in via ssh

September 8, 2016

Are you guys sure it doesn't boot the second time?

It could be the case it just doesn't show video output for some reason. I have done quite a few Armbian installations on Beelink X2 without any problems. But I do not use monitor or keyboard/mouse. I just ssh into my systems. And that has always worked.

When booting i find it most useful to watch the LED:s on the network port on my switch to which the Beelink X2 is connected. At first boot you should see the LED:s turn on as Armbian starts up the network. Then they will turn off as the Beelink X2 does reboot, after that they will turn on again when the second boot is finished.

After that you should be able to find the IP-address used in your routers DHCP client list and ssh into the system.

September 5, 2016

Is any docs to make bootable sd-card for OPi PC from another linux machine? My OPi PC doesn't boot from

http://mirror.igorpecovnik.com/Armbian_5.14_Orangepipc_Debian_jessie_3.4.112_desktop.7z

Changed a lot of cards and drives. Other images, like Lubuntu_jacer boots great.

All the instructions you need are on this page: http://docs.armbian.com/User-Guide_Getting-Started/

August 10, 2016

The most simple solution would be to start your script from the file /etc/rc.local.

Just add a line starting your script before the "exit 0" line last in the /etc/rc.local file.

In this way there is no need to login. The file /etc/rc.local is run automatically by the system at boot.

August 5, 2016

Formated 8 GB SD card with FAT32, copied Armbian_5.14_Orangepipcplus_Debian_jessie_3.4.112_desktop.raw onto it.

It is not enough to simply copy the file to the SD-card.

You need to write the image file to the SD-card using dd command in Linux or a tool like win32diskimager in Windows.

August 4, 2016

There are two different HW versions of the Beelink X2.

If your serial number starts with X2 you can follow these instructions: http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/page-3#entry12339

If your serial number starts with A2 you can follow these instructions: http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/page-4#entry12895

It might be useful to read through the entire Beelink X2 thread.

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.

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?

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

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by slinde

Important Information