borsti67

Members
  • Content Count

    41
  • Joined

  • Last visited


Reputation Activity

  1. Like
    borsti67 reacted to AnonymousPi in Thank you heaps for making Armbian!   
    Hi,
     
    Just joined to say thanks to all to those that are involved in the development of Armbian. I recently bought an Orange Pi PC after reading the internet full of people bitching about non-booting devices, HDMI issues, overheating and general crapness.
     
    Decided to buy a Orange Pi PC nonetheless, found an old crap micro SD card, burnt Armbian (the internet has made it clear to not bother with the crap on the official Orange Pi website!) onto it and the thing booted without any issues! Typing this message from it as we speak in Iceweasel!
     
    The thing only cost me 9 quid, so decided to donate what I would have wasted in cash on a Raspberry Pi 3 (which is anything but the 25 dollar SBC it seems to be advertised) as a donation to Igor and co.
     
    I just run the Orange Pi PC out of the plastic static bag it came in LOL!
     
    Once again, great work.
  2. Like
    borsti67 got a reaction from wildcat_paris in Repository management   
    Did you miss some lines in the scripts by chance? (latest lib, lime2, 3.4.112, jessie, with extras and desktop)
    [ o.k. ] Applying common tweaks install: cannot stat '/[...]/lib/config/hostapd/hostapd.conf': No such file or directory install: cannot stat '/[...]/lib/config/hostapd/hostapd.realtek.conf': No such file or directory
  3. Like
    borsti67 reacted to Igor in Repository management   
    Yes, I did.  Corrected. 
     
    Thanks.
  4. Like
    borsti67 reacted to zador.blood.stained in Error in compile.sh?   
    Yes. Building (especially u-boot and kernel packages) should still work in Trusty without issues, but some features (container environment detection and building desktop acceleration and some other packages) will work only in Xenial.
  5. Like
    borsti67 got a reaction from wildcat_paris in [can wait][generic] patch in /scripts/something/ for compile.sh to solve some issues   
    /me = dumb.
     
    I've had that already in another project, so it was/is just c'n'p for the variable definitions (which should be set in compile.sh IMHO), the rest is search-and-replace.
     
    Compilation finished in the meantime: Inclusion of the conf worked as expected, and also the after-build hook!
  6. Like
    borsti67 got a reaction from wildcat_paris in [can wait][generic] patch in /scripts/something/ for compile.sh to solve some issues   
    Currently I'm working only with one board, so for me it's not an issue. The idea is in case the Armbian script gets broken for a specific board only (I've had this some time ago for a BBB) you would be able to set LIB_TAG to the latest working one in the config-<thisboard>.conf file.
    At the moment for me the actual master works fine, so no need here - I justed wanted to bring it to your attention in case you didn't consider this yet.
    I just have changed my lib.conf to define the hook and now it's compiling.
     
    Regarding my 2nd remark, there LIB_TAG was just an example, you also cannot pass BOARD and such as parameters, therefore my question. But the question is somewhat obsolete now as all of these can be set in the dedicated conf...
     
    Anyway thanks for the really fast reply (and action!)
     
    Do you dislike the idea of having the color definitions as variables instead of escape sequences at all or should I provide this once more later? But then over all scripts which use colored output...?
  7. Like
    borsti67 got a reaction from wildcat_paris in [can wait][generic] patch in /scripts/something/ for compile.sh to solve some issues   
    Thanks for the hook, I think this will do very good!
     
    But regarding the parameters and the inclusion script I have still some questions:
    you placed the script AFTER Armbian self-update. This means one will not be able to provide a LIB_TAG by the additional script. maybe I'm not experienced enough in bash scripting, but to my knowledge parameters don't have priority over code. This means if compile.sh contains LIB_TAG="" this won't work:
    LIB_TAG="v1.0" ./compile.sh ...or do I miss something? That's the main reason why I proposed the slightly more complex syntax in the patch.
  8. Like
    borsti67 got a reaction from wildcat_paris in [can wait][generic] patch in /scripts/something/ for compile.sh to solve some issues   
    forgot patch
    compile_sh.patch.txt
  9. Like
    borsti67 got a reaction from wildcat_paris in [can wait][generic] patch in /scripts/something/ for compile.sh to solve some issues   
    Hm, the forum doesn't support nested quotes?
     
    may be it's a little harder to read, but as the user doesn't have to change anything here I would not consider this a problem. The name of the variable and its standard value are visible and well documented in the comments, so if the user wants to have them changed he would do it in the separate conf (in standard syntax)... Oops, I have overlooked this one. This is better indeed, but it will work only as long as we don't expect more than 1 parameter, correct? good point, I never tried. $SUDO_USER was the only reference to the "real" logged-in user I was able to find. Do you know any better method? As long as it's unsafe this way, I'll put it in [[ -z ]]...
  10. Like
    borsti67 got a reaction from wildcat_paris in [can wait][generic] patch in /scripts/something/ for compile.sh to solve some issues   
    I have done some changes to compile.sh:
    Variables are now defined ONLY if not passed otherwise, so they can be set elsewhere without the need to make changes in this file (not necessary, just for readability of code) I have added the escape-sequences for the ANSI-coloring as variables, so they can be used anywhere later. This is just in case someone prefers other colors for output and doesn't want to change each line individually. At the moment it only works within compile.sh as I didn't touch other scripts yet, but I can easily do if I should! in case a file named "armbian_user.conf" is found in the same folder, it will be sourced just before Armbian self-update takes place. Within this file (which is absolutely not necessary to have) the user can set overrides to variables, call other scripts and so on. at the end of the script, all files in $SRC will be owned by the current user (instead of root) Please review the attached patch and apply if ok!
    (in case something is missing/wrong also please tell so I can modify and create another patch)
     
    [PS: I needed to change the extension to .txt to upload, .patch is not allowed...?]
      compile_sh.patch.txt
  11. Like
    borsti67 reacted to Melanrz in Armbian in raspberry pi geek magazine   
    I noticed in last raspberry pi geek (DE) in board comparison use Armbian as prefer os for cubieboard
     
    https://www.oboom.com/82BRP4U9/eere416.pdf
  12. Like
    borsti67 reacted to Nireus in Banana Pi Newer Mali drivers support   
    Hello!
     
    Is there any hope to acquire a r3p2 or a newer Mali driver support in an armbian kernel for Banana Pi?
  13. Like
    borsti67 got a reaction from LarsN in [minor][quick fix] "git pull" of "lib" before going sudo   
    I have added this:
    chown -R $SUDO_USER:$SUDO_USER $SRC at the end of compile.sh because I don't need ANY files owned by root...
  14. Like
    borsti67 got a reaction from wildcat_paris in [minor][quick fix] "git pull" of "lib" before going sudo   
    I have added this:
    chown -R $SUDO_USER:$SUDO_USER $SRC at the end of compile.sh because I don't need ANY files owned by root...
  15. Like
    borsti67 got a reaction from wildcat_paris in Issue with installation of firmware   
    My project is also a git "around" Armbian. - I found it a little uncomfortable to store this kind of data there as I would either copy it into my git repo or need some .gitignore(s). I fiddled with it but it was no fun as I'm experimenting a lot and so it got messed up quite often. I wanted to keep it clean so I prefer to only put somewhat "static" scripts and .deb files there.
  16. Like
    borsti67 got a reaction from Igor in Issue with installation of firmware   
    Your commit works, thanks a lot!
  17. Like
    borsti67 reacted to zador.blood.stained in Issue with installation of firmware   
    Desktop code wasn't updated to latest changes yet. Hope this fixes it for now.
     
     
    I agree that everything should go into the logs, but IMO stderr output of package installation should go both to log and console, so you can find regressions with
    PROGRESS_DISPLAY=none BUILD_ALL=yes without looking through dozens of compressed log files
  18. Like
    borsti67 got a reaction from wildcat_paris in [PATCH] Small bug in Logging   
    Hi,
     
    I noticed that "install.log" was missing the beginning of the process, it starts at building the .deb for u-boot.
    There is one ">" missing in common.sh:
    diff --git a/common.sh b/common.sh index 503a3ab..920ba38 100644 --- a/common.sh +++ b/common.sh @@ -90,7 +90,7 @@ compile_uboot (){ cd $DEST/debs display_alert "Target directory" "$DEST/debs/" "info" display_alert "Building deb" "$uboot_name.deb" "info" - dpkg -b $uboot_name > $DEST/debug/install.log 2>&1 + dpkg -b $uboot_name >> $DEST/debug/install.log 2>&1 rm -rf $uboot_name FILESIZE=$(wc -c $DEST/debs/$uboot_name.deb | cut -f 1 -d ' ')
  19. Like
    borsti67 reacted to Edgar Mondragon in Armbian on Wikipedia   
    Hi, I created an Armbian article on Wikipedia. It's just a basic entry. Please help improving it.

    https://en.wikipedia.org/wiki/Armbian

    Thanks!