Jump to content

rufik

Members
  • Posts

    106
  • Joined

  • Last visited

Everything posted by rufik

  1. Mainline dev image as here: https://forum.armbian.com/index.php/topic/3574-orangepi-2-wifi-driver-issue-in-mainline-dev-410/ When I try to run armbianmonitor: rufik@opi2:~$ sudo armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU/usr/bin/armbianmonitor: line 271: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: No such file or directory 12:57:09: MHz 0.02 1% 0% 0% 0% 0% 0% 38.5°C^C So it looks like cpufreq not working. Dmesg says: rufik@opi2:~$ dmesg -T | grep -i cpu [Wed Feb 15 21:40:37 2017] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d [Wed Feb 15 21:40:37 2017] CPU: div instructions available: patching division code [Wed Feb 15 21:40:37 2017] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [Wed Feb 15 21:40:37 2017] percpu: Embedded 14 pages/cpu @ef6a8000 s26316 r8192 d22836 u57344 [Wed Feb 15 21:40:37 2017] pcpu-alloc: s26316 r8192 d22836 u57344 alloc=14*4096 [Wed Feb 15 21:40:37 2017] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [Wed Feb 15 21:40:37 2017] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [Wed Feb 15 21:40:37 2017] CPU: Testing write buffer coherency: ok [Wed Feb 15 21:40:37 2017] CPU0: update cpu_capacity 1024 [Wed Feb 15 21:40:37 2017] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [Wed Feb 15 21:40:37 2017] smp: Bringing up secondary CPUs ... [Wed Feb 15 21:40:37 2017] CPU1: update cpu_capacity 1024 [Wed Feb 15 21:40:37 2017] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [Wed Feb 15 21:40:37 2017] CPU2: update cpu_capacity 1024 [Wed Feb 15 21:40:37 2017] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [Wed Feb 15 21:40:37 2017] CPU3: update cpu_capacity 1024 [Wed Feb 15 21:40:37 2017] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [Wed Feb 15 21:40:37 2017] smp: Brought up 1 node, 4 CPUs [Wed Feb 15 21:40:37 2017] CPU: All CPU(s) started in HYP mode. [Wed Feb 15 21:40:37 2017] CPU: Virtualization extensions available. [Wed Feb 15 21:40:37 2017] cpuidle: using governor ladder [Wed Feb 15 21:40:37 2017] cpuidle: using governor menu [Wed Feb 15 21:40:40 2017] ledtrig-cpu: registered to indicate activity on CPUs [Wed Feb 15 21:40:44 2017] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19 [Wed Feb 15 21:40:44 2017] cpu cpu0: dev_pm_opp_get_opp_count: OPP table not found (-19) [Wed Feb 15 21:40:44 2017] cpu cpu1: cpufreq_init: failed to get clk: -2 [Wed Feb 15 21:40:44 2017] cpu cpu2: cpufreq_init: failed to get clk: -2 [Wed Feb 15 21:40:44 2017] cpu cpu3: cpufreq_init: failed to get clk: -2 Where can I start digging for this issue? Anyone can point me, please?
  2. @ArmbianCollab administrator - could you add new task with Orange PI 2 and assign it for me, please? Subtasks could be somehow standard: ethernet, wifi, shutdown, cpufreq/dvfs, etc. I'd like to make some fixes for OPI 2 (headless) in my spare time...
  3. I've build an dev image for my OrangePi 2 (kernel 4.10) to try mainline kernel and got into troubles with onboard wifi. It works fine in legacy with 8189es module, but there is no 8189es module in mainline image. So I tried 8189fs but it's not working. After doing some search I've managed to build 8189es module myself using https://github.com/jwrdegoede/rtl8189ES_linux.gitrepository. Quick manual: git clone https://github.com/jwrdegoede/rtl8189ES_linux.git cd rtl8189ES_linux/ make ARCH=arm KSRC=/usr/src/linux-headers-$(uname -r) CROSS_COMPILE= sudo mkdir /lib/modules/4.10.0-sun8i/kernel/drivers/net/wireless/realtek/rtl8189es/ sudo cp 8189es.ko /lib/modules/4.10.0-sun8i/kernel/drivers/net/wireless/realtek/rtl8189es/ sudo depmod -a sudo modprobe 8189es I'd suspect that this issue applies to all boards with RTL8189ETV sdio wifi (OPI 2, OPI+2, NanoPI A64, etc). And the question is - why this driver is missing in default armbian repo?
  4. Yes, it does. I have one running fine with wifi right now :-)
  5. Could you put full-resolution samples please? Day and night shots would be welcome
  6. Yes, I know, use case first. What I mean "in general" is dealing with archives (apt-get, zip, tar, etc), usb printer/scanner, Munin graphing, dlna audio, some crontab scripts, rsync, maybe some video encoding from time to time. Nothing really heavy, but CPU and DRAM speed matters mostly. If I can do these task with H5 about 30% faster, I'll go for it :-)
  7. Is the A7 core performance (H3) in pair with A53 (H5) when using Armbian/Ubuntu? Because if A53 can perform about 30% faster in general, then there is sense to have H5 support...
  8. Mine's been shipped out
  9. Yep, I've just bought one, I couldn't resist also :-)
  10. I have Opi 2 with wifi built-in. I can provide dmesg and other stuff if it will help in anyway...
  11. Any news about scheduling 5.11 build for H3?
  12. OPI 2 does not boot also with Jessie Server 5.10 Vanilla. My primary usage is headless server, so I'd like to test vanilla builds
  13. After few days of low activity, rx dropped packages rises to ca 12%.
  14. I've installed and it works fine so far. About 2% rx dropped on 2GB download, so not that bad. We'll see yet...
  15. Will it be included into 5.10 release? Because I'm really interested in, current version (v4.3.0.4_11916.20140724_COB) is a crap, I'm getting a lot of RX Packets dropped on OPI 2.
  16. I was also suprised with this eth and wlan dependency on my OPI 2. I started with eth0 auto, then configured wlan0, rebooted without LAN cable and it worked. Wlan is working this way, even with eth0 configured to auto. But after I plugged in and out cable, I lost wifi until rebooted. I was surprised because I had never such issue on my Alix with Ubuntu 12.04. It looks like Ubuntu is automatically preferring (and setting up) eth over wlan until cable is pulled off. It would be nice to have same behavior on Armbian. Maybe it could be done using some events listener and scripts?
  17. 1 year old Sandisk 32GB SD Card (model SE32G, so it's Extreme Plus AFAIK) used in DSLR camera. Test on OPI 2 + Armbian 5.05, 2nd and 3rd pass: random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 3168 3093 8178 8355 7134 2833 102400 16 6661 7139 15621 15832 15794 7021 102400 512 17313 18136 21632 21643 21655 20083 102400 1024 20643 20714 22152 22176 22160 20491 102400 16384 21284 21342 22944 22944 22942 21334 random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 3169 3158 8242 8322 7017 2842 102400 16 6664 7133 15748 16077 16029 7055 102400 512 15479 20580 21659 21652 21658 20145 102400 1024 20600 20669 22155 22163 22163 20521 102400 16384 21165 21300 22933 22934 22931 21267 Card info: mmc0:aaaa info: cid: 035344534533324780242e28a200e27b csd: 400e00325b590000edc87f800a4040c3 scr: 0235800300000000 date: 02/2014 name: SE32G type: SD preferred_erase_size: 4194304 fwrev: 0x0 hwrev: 0x8 oemid: 0x5344 manfid: 0x000003 serial: 0x242e28a2 uevent: DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=SE32G MODALIAS=mmc:block erase_size: 512
  18. You're writing about SD card speed but what about reliability? Is eMMC more reliable than SD card (ex. Samsung EVO)?
  19. Thanks for tips. I'll try with power bank as poor's man ups solution But this solution has disadvantages: - cannot get information about battery's running out (for safe shutdown) - possibly cannot be used in unattended installation, because you don't know how power bank cells react while always plugged in (charging) And it's to be checked how OPI will react for running out power bank and if it will boot after power comes back...I'll try it.
  20. I wonder if any OPI version follows RPi HAT Specification? UPS PIco or similar could be used then...
  21. One more brand new Samsung EVO 16GB (MB-MP16DA/EU) result on OPI 2 + Armbian 5.05 random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 2388 2172 6462 6658 6543 1195 102400 16 5634 6580 14451 14747 14232 3749 102400 512 11254 10524 21463 21467 21317 8986 102400 1024 11650 11604 22049 22044 21947 9091 102400 16384 11874 11383 22860 22877 22848 10566 random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 2236 2346 6664 6483 6547 1220 102400 16 5664 6571 14427 14712 14413 3677 102400 512 11227 10935 21470 21463 21318 9073 102400 1024 11596 11621 22055 22068 21961 8974 102400 16384 11893 11916 22886 22885 22830 10923 Card info: mmc0:59b4 info: cid: 1b534d303030303010f06d55a000f887 csd: 400e00325b590000775d7f800a4000a3 scr: 0235800300000000 date: 08/2015 name: 00000 type: SD preferred_erase_size: 4194304 fwrev: 0x0 hwrev: 0x1 oemid: 0x534d manfid: 0x00001b serial: 0xf06d55a0 uevent: DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=00000 MODALIAS=mmc:block erase_size: 512
  22. So C2 arm64 is not an option right now. I'd stick with OPI/H3 but I miss UPS solution for this board...
  23. So this is not arch64 time yet :-) Did you see any ups solution for OPI?
  24. I'm quite happy with old HP T5720 thin client (AMD Geode 1500 NX afair) but it's "adventure time" :-) Arm sbc looks promising and I'd like to jump into it. My home server is idling most of the time, there is munin with some temperature monitoring from remote sensors, Apache, cloud printer via USB, sane php scanner solution, squeezebox service, some cron jobs and it's my own development platform. So nothing heavy, mostly idling. I'd not be happy to replace it with less per-core-horsepower (it's like driving naturally aspirated engine after used to biturbo) , so I'm thinking about C2...but good software support is more important than hardware and this is my priority.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines