Jump to content

kometchtech

Members
  • Posts

    48
  • Joined

  • Last visited

Everything posted by kometchtech

  1. Hello Igor, In past threads, it seems a bit argued about the zram module, but will not the zram module be enabled by default on other arm boards? I am using odroid-c2, but it is effective in hardkernel? It seems that it is becoming. If possible, if Armbian seems to have no problem, I want it to be valid. https://forum.odroid.com/viewtopic.php?f=136&t=20116 $ grep "ZRAM" /boot/config-3.14.79-odroidc2 CONFIG_ZRAM=y # CONFIG_ZRAM_LZ4_COMPRESS is not set # CONFIG_ZRAM_DEBUG is not set $ lsmod | grep zram $ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=odroidc2 BOARD_NAME="Odroid C2" VERSION=5.31 LINUXFAMILY=odroidc2 BRANCH=default ARCH=arm64 IMAGE_TYPE=stable Best regards.
  2. Hi, All ARM 64 get support plate. http://www.banana-pi.org/m64.html Spec: If it is like the 3.10 series kernel,?!?
  3. So do not arm64 in the following source is apparently not compile. Do you have a solution? https://github.com/friendlyarm/linux-3.4.y
  4. Thanks,@wildcat_paris Shown below, seems to not compile. # CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 make clean defconfig Makefile:568: /home/linux-3.4.y/arch/arm64/Makefile: No such file or directory make[1]: *** No rule to make target `/home/linux-3.4.y/arch/arm64/Makefile'. Stop. make: *** [clean] Error 2
  5. @wildcat_paris I do not know how to aarch64 because the official Git doesn't work like that. The Forum is not working actively. edit:https://github.com/friendlyarm/
  6. @wildcat_paris Thanks for the Info! Or better still you recompiled in aarch64... Only official, there is that way.
  7. FYI tkaiser uname -a Linux dns02.kometch.local 3.4.39-s5p6818 #2 SMP PREEMPT Fri May 20 15:51:46 HKT 2016 armv7l GNU/Linux cat /proc/version Linux version 3.4.39-s5p6818 (root@jensen) (gcc version 4.9.3 (ctng-1.21.0-229g-FA) ) #2 SMP PREEMPT Fri May 20 15:51:46 HKT 2016
  8. FYI. NanoPC-T3 result. time sysbench --test=cpu --cpu-max-prime=20000 --num-threads=8 run sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 8 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 57.1916s total number of events: 10000 total time taken by event execution: 457.3030 per-request statistics: min: 45.43ms avg: 45.73ms max: 166.89ms approx. 95 percentile: 45.73ms Threads fairness: events (avg/stddev): 1250.0000/1.00 execution time (avg/stddev): 57.1629/0.01 real 0m57.223s user 7m36.520s sys 0m0.068s
  9. Hi all. In response to aarch64 because the images have been distributed to the official NanoPC-T3 and NanoPC-M3 arm7l and Armbian you want to distribute. From the official not working so actively hard? http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T3 https://github.com/friendlyarm/ Thanks.
  10. NanoPC-T3 heatsink with photo uploads. Parameter to that I was reading about the temperature, it is not.
  11. I bought the same system configuration NanoPC-T3. Image has been distributed from the FriendlyARM and is distributed in the form of arm7l, in the form of aarch64 is like. And would convey expectations to the other side, but will support the Armbian!
  12. @tkaisar It was situation understanding. We decided to wait until the branch of the problem is resolved.
  13. Octacore "voluntary design (ARM64) you can buy cheaper, so personally hoping for Armbian.
  14. @tkaiser Bananapi M3 Armbian images are not public? I think the source.list contain Banana pi m2plus Armbian I debian-lite image has the Armbian based on published in banana pi Forum, but because poor conditions.
  15. The version of the past? So were working. Would do should wait until it is fixed.
  16. Verify kernel 4.6 with dev on test construction Armbian where the CPU is not recognized correctly. root@orangepipc:~# lscpu Architecture: armv7l Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0 Off-line CPU(s) list: 1-3 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 Model name: ARMv7 Processor rev 5 (v7l) [ 0.001455] CPU: Testing write buffer coherency: ok [ 0.001769] /cpus/cpu@0 missing clock-frequency property [ 0.001784] /cpus/cpu@1 missing clock-frequency property [ 0.001794] /cpus/cpu@2 missing clock-frequency property [ 0.001805] /cpus/cpu@3 missing clock-frequency property [ 0.001815] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.001867] Setting up static identity map for 0x40100000 - 0x40100058 [ 0.003909] Brought up 1 CPUs [ 0.003924] SMP: Total of 1 processors activated (48.00 BogoMIPS). [ 0.003931] CPU: All CPU(s) started in SVC mode. This is what Armbian modification which managed to do? Or it should be reported somewhere? My best regards.
  17. Hello, Igor Thank you for your reply. Do you plan to Kernel 4.6 is issued a will to work properly image Once you become the official version? nice to meet you.
  18. Hello, Did not start Orange Pi PC Armbian_5.10_Orangepih3_Debian_jessie_4.6.0-rc1 graceful on the Microsd and trying to start it. It is a serial TTL and HDMI are not so thin air conditions. from RC Nice in this recognition within the range of the bug? My best regards.
  19. thought associated with the following errors occur when you attempt to run the systemctl command, so all the previous threads. Failed to get D-Bus connection: Unknown error -1
  20. is init=/bin/systemd is not enabled, this is a known issue? http://forum.armbian.com/index.php/topic/342-dbus-error-when-using-systemctl/
  21. as igor's are saying, it seems I should do modify the setenv of /boot/boot.cmd. In the case of cubietruck setenv bootargs "init=/bin/systemd console=tty1 root=/dev/sda1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" to re-start it to regenerate the boot.scr mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
  22. Somehow I feel like solved. First put the init=/bin/systemd, good only to regenerate boot.scr? setenv bootargs "init=/bin/systemd console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" My best regards.
  23. sunxi# setenv bootargs "console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" sunxi# boot Still, it stops when Starting Kernel.
  24. Thanks for the advice. Commands taught in sunxi prompt then tried to boot but it stops when starting kernel. My best regards.
  25. I was not aware of the PGP sign. I'm sorry. Making the Systemd over there, there is no merit in using the jessie. Since the time being vanilla kernel does not start well with some reason out of the environment, and then to go in the legacy kernel. Best regards.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines