Jump to content

slinde

Members
  • Posts

    59
  • Joined

  • Last visited

Everything posted by slinde

  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?
  16. 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.
  17. 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
  18. 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.
  19. All the instructions you need are on this page: http://docs.armbian.com/User-Guide_Getting-Started/
  20. 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.
  21. 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.
  22. 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.
  23. 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.
  24. 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?
  25. 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:
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines