blindpet
-
Posts
49 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by blindpet
-
-
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.
-
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.
-
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
-
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).
-
@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.
-
Why should this image emulate a Raspberry Pi? It's a minimal x64 Jessie install containing the whole bunch of scripts that make DietPi somewhat special.
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.
-
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.
-
I finally settled on Configserver Firewall, here is a pretty complete guide.
-
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
-
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?
-
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?
-
You can include minidlna, a media server software fully compliant with DLNA/UPnP-AV clients.
I use it to watch my downloaded films on my smart tv.
sudo apt-get install minidlna
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.
-
I know what you mean. I have an OrangePi Plus as well and tried to build the source, but couldn't get it going. I just needed the cifs kernel module (I don't know why this isn't included in all images by default), but was not able to build it. If anyone manages to compile the module for 3.4.39 (or can tell me how to build it manually), please let me know.
Thanks!
Have you tried Loboris images? I have compiled a working Ubuntu 15.04 for the Orange Pi Plus here
-
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.
-
You will probably find it easier to use ufw which sets iptables for you, looks simpler than shorewall
-
Thank you, will try this soon.
I expected that the Banana Pi build script passed the board variable somehow and I could manipulate that. I will use your all in one solution so I can just pick the board from the nice little menu
-
-
I will test at some point and get back to you, are you saying I don't need to specify orange pi anywhere in the build.sh and WiFi on the Orange Pi (non-mini non-plus of course) will still work?
-
Do I need to specify something in the initial build script so that the Orange Pi banner is shown?
My Banana Pi image is working but is showing the Banana Pi banner on boot, would like it to show Orange Pi
-
I have forked your repo to add a lot of media server stuff, I added syncthing too with the code below
install_syncthing () { #-------------------------------------------------------------------------------------------------------------------------------- # Install syncthing #-------------------------------------------------------------------------------------------------------------------------------- SYNCTHINGUSER=$(whiptail --inputbox "Enter the user to run Syncthing as (usually pi)" 8 78 $SYNCTHINGUSER --title "$SECTION" 3>&1 1>&2 2>&3) exitstatus=$?; if [ $exitstatus = 1 ]; then exit 1; fi if ! getent passwd $SYNCTHINGUSER > /dev/null; then echo "User $SYNCTHINGUSER doesn't exist, exiting, restart the installer" exit fi if !(cat /etc/apt/sources.list.d/syncthing-release.list | grep -q Syncthing > /dev/null);then cat >> /etc/apt/sources.list.d/syncthing-release.list <<EOF # Syncthing deb http://apt.syncthing.net/ syncthing release EOF wget -O - https://syncthing.net/release-key.txt | apt-key add - debconf-apt-progress -- apt-get update debconf-apt-progress -- apt-get install syncthing -y sudo -u $SYNCTHINGUSER timeout 120s syncthing #Make syncthing webui remotely accessible sed -i "/ <address>127.0.0.1:8384/c\ \<address>0.0.0.0:8384\<\/address\>" /home/$SYNCTHINGUSER/.config/syncthing/config.xml cd /etc/init.d/ wget https://raw.github.com/blindpet/MediaServerInstaller/usenet/scripts/syncthing sed -i "/DAEMON_USER=root/c\DAEMON_USER=$SYNCTHINGUSER" /etc/init.d/syncthing chmod +x /etc/init.d/syncthing cd /tmp update-rc.d syncthing defaults service syncthing start echo Syncthing is running on $showip:8384 fi }I also changed btsync so it uses a repo and makes it much easier
cd /tmp wget http://debian.yeasoft.net/add-btsync-repository.sh ( echo yes && \ echo yes ) \ | sh add-btsync-repository.sh apt-get update apt-get install btsync -y
I haven't ever made a pull request but will try sometime next month
-
You are typing patch instead of path. This works for me
[TV] #This is the name of the share it will show up as when you browse comment = TV Folder path = /mnt/usbstorage/TV create mask = 0755 directory mask = 0755 read only = no browseable = yes public = yes force user = pi #force user = root only guest = no
-
Some processes are not closed properly. I made some fixes for this but it doesn't help always.
In general the script needs some additional fine tuning.
OK, to be fair for a complicated script it has only ever failed me this once, you have done an excellent job. I am really enjoying the fork I made of your micro server too, great framework. Please respond about the DVB tuner if you are interested I would like to contribute to you getting one
-
Yes, this is also possible. I usually don't install much after base system so it's always around 1G ... don't know how much do you need for plexmediaserver ... Initial size of 1200 might not be enough, 1500-2000 should probably do.
And one more think. If the script breaks in the middle is better to reboot before running script again.
Rebooting helped! What is that about?
-
I added the image shrinking part not long ago and I also experience this problem.
It could help if you enlarge this parameter:
https://github.com/igorpecovnik/lib/blob/next/common.sh#L380
from 1.2 to 1.5
I need to take some more time here to fix properly.
Thanks Igor, I tried that but same error, this part concerns me
After this operation, 0 B of additional disk space will be used.
It's like the problem is the current size of the working image it is using, if I change the size from 1200 to 1500 in build.sh do you think that would help?
resize2fs 1.42.9 (4-Feb-2014) The containing partition (or device) is only 306944 (4k) blocks. You requested a new size of 406528 blocks. /home/htpcguides/BananaPI-Debian/lib/common.sh: line 385: *4096/1024: syntax error: operand expected (error token is "*4096/1024")
SOLVED [TEST / customize image feature] Customize_image.sh doesn't appear to work properly
in Armbian build framework
Posted
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