• Content Count

  • Joined

  • Last visited

About jshc1

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. https://forum.armbian.com/topic/9277-proccpuinfo-show-only-litlle-cores-on-odroid-hc1-hints-appreciated
  2. HC2 doesn't have AES-NI so I don't know what HA you mean. First, just start using. What transfers do you currently have?
  3. Thank you for showing this. So I installed chromium from sid 72.0.3626.109-1 and it works. But the amount of dependence probably will give me a lot of trouble and probably it will not be worth sacrificing. Now only I will have to go and look what has stopped working through these dependencies ....
  4. jshc1@ODROID-HC1:~$ chromium Received signal 11 SEGV_MAPERR 000000000000 #0 0x0000022d9030 <unknown> #1 0x000002267920 <unknown> #2 0x0000022d937e <unknown> #3 0x0000022d95ac <unknown> #4 0x0000b2cf5fe0 <unknown> #5 0x000000b0214c <unknown> #6 0x0000025be95c <unknown> #7 0x000002a8f91e <unknown> #8 0x0000036afee0 <unknown> #9 0x0000036b0512 <unknown> #10 0x0000036b059c <unknown> #11 0x0000036b05d2 <unknown> #12 0x000002139a56 <unknown> #13 0x000002139a92 <unknown> #14 0x000001fba092 <unknown> #15 0x000001fc5c2e <unknown> #16 0x000001fc6130 <unknown> #17 0x000001098de8 <unknown> #18 0x000001356e64 <unknown> #19 0x00000109a7f6 <unknown> #20 0x00000109b422 <unknown> #21 0x00000108f790 <unknown> #22 0x000001f914bc <unknown> #23 0x000001f91626 <unknown> #24 0x000001f918a8 <unknown> #25 0x000001f9880e <unknown> #26 0x000001f90228 <unknown> #27 0x00000097e510 ChromeMain #28 0x0000b2ce74aa __libc_start_main [end of stack trace] Calling _exit(1). Core file will not be generated. ATTENTION: default value of option force_s3tc_enable overridden by environment. jshc1@ODROID-HC1:~$ [28554:28554:0221/212433.772966:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process. jshc1@ODROID-HC1:~$ firefox ExceptionHandler::GenerateDump cloned child 28758 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  5. The last chromium update has broken chromium, can anyone confirm? 71.0.3639.110-1 It works without a problem 72.0.3626.96-1 It does not start Firefox is still broken from what I see on the armv7 ... now chromium gets hiccups. 4.14.94 / 5.73
  6. 4.19 for xu4 at the moment is a mess. Stay at 4.14 if you are able. I currently have 4.14.87 https://forum.armbian.com/topic/9319-problem-with-underclocking-odroid-hc1hc2xu4-with-kernel41914armbian570/
  7. It's good that the problem is solved. If you have any stubborn program, you can always let it run on specific cores. I'm doing it with Kodi 17.1. This mofo is so greedy on the cores that eats all 8 in 90% regardless of whatever. It just so happens that I use kodi as a poor audio player and I only need to give it three litlle cores to perform its task. it does not occupy big cores, which at the same time allows them to sit on 600Mhz and in theory less heat and electricity.
  8. I'm not sure where the problem is. Your Exynos5422 is detected almost as it should. Only 1800/1300 is bad but it's the fault of 4.19. Are you sure that htop simply does not give you the same cores twice? In my case, htop 2.1.1 on both 4.14 and 4.19 gave the correct reading(2000/1500 - 1800/1300). Make sure that you have the cores properly set in htop. And if you stay on 4.19 remember that you lose 200Mhz on the core.
  9. Ok. I did it right away. ;) I hope that the kernel will be polished in the near future. ;)
  10. Try using 4.14.69. Personally, I have not noticed any problems with HC1 and 4.14.69 lately. However, on 4.19.14 I have problems with clocking ... I am not sure how the situation is up to 4.19.5. But according to Igor 4.19.y is not polished for XU4 (HC1 / 2). And Igor recommends returning to 4.14.y. Personally, I am currently using 4.14.69 for HC1 without problems, so maybe you can try and let us know how the situation looks like. Exynos5422 should be clocked up to 2000Mhz for big and 1500Mhz for LITTLE. 1800/1300 is a reduced bar on 4.19.y
  11. Hey Can anyone confirm the problem with under-clocking in Odroid HC1/HC2/XU4 with Kernel 4.19.14 / Armbian 5.70? I could always reach 2000/1500Mhz without a problem. Currently, after the last Armbian update from 5.60 to 5.70, I noticed a strange behavior that Odroid does not want to reach full clocks. With cpufrequtils min 600 max 2000 and "performance" and clocks do not want to go higher than 1800/1300Mhz temperature cpu 45.0 ° C. No changes just last updates nothing more was touched. After returning to 5.60 and 4.14.69 the CPU runs normally at 2000/1500 .... I also have the impression that HDD sometimes behaves strangely at 5.70 / 4.19.14 According to the @tkaiser suggestion.... -- John Stiles