blindpet

Members
  • Content Count

    49
  • Joined

  • Last visited

  1. Thank you, I see it in the userpatches folder and it worked now. I made the mistake of looking in the github instead of the documentation page
  2. I'm having trouble getting this working, I compile images just fine on Ubuntu 14.04. I renamed the customize-image.sh.template to customize-image.sh Then I added my custom commands RELEASE=$1 FAMILY=$2 BOARD=$3 BUILD_DESKTOP=$4 git clone https://github.com/blindpet/MediaServerInstaller /root/HTPCGuides Tried also without renaming the template file and still nothing. On earlier versions of the build script I did this in another way but it seems to be deprecated.
  3. So it is the hardware itself for the USB to SATA bridge that is garbage? No amount of driver tweaking will help? Just trying to clarify so I don't waste my time, I never got above 20 MB/s in my old Pi Plus tests. I will have a read on CNX, thanks for the link. I will include a disclaimer with future sysbench statistics.
  4. Gerd I'm not sure why you are against systemd. I was pissed about it in the beginning until I learned all init.d scripts work on Debian Jessie with systemd. Then my anger disappeared
  5. I am guilty of using sysbench for benchmarks of the Banana Pi, unfortunately users look for these in choosing a board (sadly I did not know about armbian at the time). My primary focus was however network throughput for samba, ntfs, exfat over SATA and USB. I am curious what kind of cli benchmarks are any good besides sysbench, I would think compiling a program from source would be a better measure. Looks like now that armbian is out for the Orange Pi Plus I can finally test SATA throughput properly unless you all think I should wait for a kernel or driver update? I would of course appreciate any feedback on these benchmarks I prepared (additional ones for exfat vs ntfs vs ext4 and unrar par2 processing at the bottom).
  6. @Igor, I agree just using a minimal debian running some installer is not that useful. I do a lot of testing for making guides and want to emulate the arm chips and use the right repo. Reasons for this are compilation testing and using mono or java apps that may behave differently on non-arm devices. It would also provide users a nice test environment they can easily restore to fresh when tinkering, saving more sd card flashes for added convenience. @zador, if you have any resources or how-tos for these that would be cool. I only recently started playing with docker. I'd like to do minimal nested virtualization if possible.
  7. I started looking at the DietPi VM in more depth and alas it does just seem to be minimal debian with the official repos. My original inquiry still stands then since I believe the armhf debian repo differs slightly from the non-arm one, it would be valuable for testing to build an armbian for qemu.
  8. I would love to see a guide on how to create a virtual machine for Armbian which would be great for testing in VMWare Workstation, Player or Virtualbox. It would be similar to the diet pi vm which autoboots into the qemu (I think) for the Raspberry Pi If someone has a rough guide on how to do it I can make something noob friendly. My guess is you need to install qemu, add some repositories and then get it to autoboot using rc.local or something like that. Any resources on how to get started would be much appreciated.
  9. I finally settled on Configserver Firewall, here is a pretty complete guide.
  10. Thank you tkaiser, glad to see you are still digging for this critical info about new arm boards. I had high hopes for the Guitar and its modular design. LeMaker sent me the Guitar test board for review and feedback. I listed many of my concerns which echo your own. None of them seem to have been implemented on updated revisions to the boards. I did my best to explain to them the common use cases for these boards which should be possible with any new boards they release, unless they are targeting a different market. More importantly any new LeMaker devices must be at least as capable as the Banana Pi since that was their own flagship device. My current concerns which need to be fixed before I can recommend this device to users: Cannot power a 2.5" hard drive with a 5V 2A adapter. Nobody wants to have to search for obscure power adapters just to be able to power the board and a hard drive USB 3 micro b makes no sense, I don't know anybody who flashes daily or would like to sacrifice throughput, why wouldn't flashing over USB 2 be sufficient? Gigabit ethernet - because USB 3 makes no sense to me without a fat enough pipe to push it through HDMI-CEC (less important) - supposed to be supported eventually
  11. Thank you Igor. So basically I just have to edit /boot/boot.cmd to point the /dev/sda1 and then recompile to boot.scr format, do I understand you correctly?
  12. I have several users following my move Linux to SATA on the Banana Pi guide using Armbian with Kernel 4.1 and they are saying that uEnv.txt on the boot partition isn't there. Is this a bug or is the procedure different for armbian? Can you shed any light on this?
  13. The version in the repo (even jessie) is a year old. Build miniDLNA from source in case you get any problems with the old version.
  14. Have you tried Loboris images? I have compiled a working Ubuntu 15.04 for the Orange Pi Plus here
  15. I am using your build script to create the 4.1 kernel but I get prompted for 400 things to answer, is there a way to accept all as modular or 'y' so I get the most hardware possible? I am trying to test if the USB TV Tuner will work with this kernel on the Lemaker Banana Pi.