Shimon

Members
  • Content count

    49
  • Joined

  • Last visited

  1. Yup, that's the plan! Any plans on updating the vegas95 images? I'm also curious if the composite A/V output is supposed to work on Linux? I'd already asked about overclockability of that kernel but forgot the modified binary blob allowing one to achieve over 1.6 Ghz might be Odroid specific. Can you confirm it's even doable?
  2. I'm going to test the Linux network performance of two different S905 GigE boxes next month so we'll be able to compare results.
  3. S905x doesn't support 1000M period, look at the Amlogic schematics. That makes S905 superior in that single area but S905x compensates with the addition of crypto instructions.
  4. That probably means you're using the universal 3.14.29 kernel whereas the original dtb's are supposed to work with 3.14.79 Vega kernel for S905 devices. But yeah, definitely a bug as both types of images work fine on my S905 based boxes.
  5. @balbes150 What happened to `zram` support in the 3.14.79 kernel from VegaS95 20170125? It seems to be compiled in instead built as a module, and doing the following doesn't work for me: # echo 1 > /sys/block/zram0/reset // OK # echo 4096M > /sys/block/zram0/disksize // bash: echo: write error: Invalid argument Any ideas? Other images work fine via the zram kernel module. edit: Missed the kernel message: zram: Cannot initialise lz4 compressing backend and the only way to make it work is to change back to lzo first, etc. Definitely not right! # echo lzo > /sys/block/zram0/comp_algorithm
  6. OK, I've found the culprit. VESA modes do work fine, indeed. For some reason, adding additional commands to my rc.local after the /boot/vegas95_init.sh invocation, interfered with setting the resolution somehow.
  7. Are you sure it's supposed to work? I was using the Armbian_5.24_Vegas95_Ubuntu_xenial_3.14.79_20160125 image for this test and it ends up with no console, as described. Moreover, you didn't include the dtb file for Mini MX III which was present in the github repo last year. I had to use a local copy.
  8. @balbes Are the VESA modes from vegas95_init.sh meant to be used in s905_autoscript.cmd or is that some generic armbian stuff? I ended up with green screen and no visible console trying to set 1280x1024p60Hz
  9. Forgot to mention, iotop stopped working (IIRC): Could not run iotop as some of the requirements are not met: - Linux >= 2.6.20 with - I/O accounting support (CONFIG_TASKSTATS, CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING)
  10. That's 1536 actually, never mind what the evil blob says. http://forum.odroid.com/viewtopic.php?p=157441#p157441
  11. Interesting! Looks not too hot @50°c, so provided you were on performance governor, this could either mean the 4-core baseline was slightly worse on that box or the benchmark doesn't scale at these settings.
  12. Yeah, that's more or less it on a S905X. If you shut the X server down, like: sudo service lightdm stop you should be able to achieve peak performance.
  13. Look at my comment #133 - the command is meant to run inside the c-ray-1.1 directory after compilation. If you ran the benchmark at least once, the c-ray-mt binary should be found there.
  14. Could you try running the renderer for a few minutes? e.g: ./c-ray-mt -t 32 -s 1900x1400 -r 8 -i sphfract -o output.ppm It takes 254 seconds on my MiniMX III (S905) so unless S912 starts overheating it should complete the same task in about 152s.
  15. Thanks @balbes150! The results (7992 vs 4781) do indicate perfect scaling. In other words, as long as there's no thermal throttling, S912 really seems to offer 66% more computing power. Not bad for a $50 box