Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Göteborg, Sweden

Recent Profile Visitors

2077 profile views
  1. 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.
  2. 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
  3. slinde

    h3 nat

    Did you enable ip forwarding in the kernel?
  4. 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.
  5. Put your command in the file /etc/rc.local. Put it on a new line just above the "exit 0" line.
  6. If you have that problem you should check your routes and DNS settings.
  7. 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.
  8. 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?
  9. 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.
  10. What is the serial number of your Beelink X2? (Can be seen on sticker underneath.)
  11. 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.
  12. 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.
  13. Maybe there is some difference in the hardware between A2H3CKHH***** and A2H3CKIG***** that Armbian is not aware of yet?
  14. 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?
  15. 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?
  • Create New...