Nick

Members
  • Content Count

    140
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Nick reacted to martinayotte in Nano Pi AIR and I2C problem   
    Be aware that when "i2cdetect" scan the bus slowly, it is usually that you don't have any pullups on the bus ...
  2. Like
    Nick got a reaction from manuti in Does NanoPiNEO's GigE Mac Address randomly change from time to time, after rebooting?   
    I believe that the various PI boards do choose a random MAC address most / all of the time.
    If it helps you can specify a MAC address in the /etc/interfaces file 
     
    Something like this should do it:
     
    # Network interfaces allow-hotplug eth0 iface eth0 inet dhcp hwaddress ether 08:00:00:00:00:01  
  3. Like
    Nick got a reaction from jiapei100 in Does NanoPiNEO's GigE Mac Address randomly change from time to time, after rebooting?   
    I believe that the various PI boards do choose a random MAC address most / all of the time.
    If it helps you can specify a MAC address in the /etc/interfaces file 
     
    Something like this should do it:
     
    # Network interfaces allow-hotplug eth0 iface eth0 inet dhcp hwaddress ether 08:00:00:00:00:01  
  4. Like
    Nick got a reaction from wildcat_paris in Armbian wiki   
    Is it worth starting an Armbian wiki?
    It seems that for questions such as how do I write the raw file to an SD card, how do I disable LEDs on my whicheverPi, why doesn't my orange pi pc boot this work in progress image  and so forth could be answered there.
     
    Hopefully it would reduce the Forum traffic for such things, but also when they do pop up a simple one line response with the wiki link is all that's required.
     
    I realise that there is the Armbian documentation, which is great, but only really covers how to use Armbian to build images. Equally there is gold mine of information in the forum, but it's sometimes buried a few pages deep or only comes to the surface with a particular search string. It sometimes takes me a while to find my own posts and I at least know that they are there.
     
    If the wiki did go ahead then I see the forum as a discussion place, solving problems discussing new boards etc. with all of the noise that goes with it, with the wiki presenting a polished concise answer to most questions.
     
    A while ago (before I even knew about Armbian) I started a banana pi wiki here https://bananapi.widgethub.co.uk/ but it never went very far, partly because it didn't have the visitor traffic to warrant putting the work in.
    In the short term at least I would be happy to start writing some of the articles and getting the basic structure together, as long as it has the backing of everyone else.
     
    On the flip side, there is already a wiki at sunxi. Personally I find the linux-sunxi site a little hard to navigate, but equally there is alot of information there so simply coming up with a duplicate of that doesn't see like a good use of resources.
     
    Any thoughts?
  5. Like
    Nick reacted to tkaiser in [WiP / Orange Pi One] Support for the upcoming Orange Pi One?   
    BTW: @candratech, @martinayotte: I started a new thread asking for a way to build mainline kernel with Ethernet fixes without breaking everything again (as I did last times): Please join in: http://forum.armbian.com/index.php/topic/940-how-to-proceed-with-mainline-ethernet-on-sun8i/#entry7179
  6. Like
    Nick got a reaction from wildcat_paris in Raspberry Pi 3 heat issues   
    Hi tkaiser,
    I did read the GitHub link last night, it was very interesting. 
    I think one of the advantages that the Raspberry Pi brand has is that not only are the foundation pushing the hardware forward but that they also have a fairly decent grasp (at least when compared to the hundreds of piClone manufacturers) of the software and inner workings of the SoC. 
     
    That last point is one of the things that I love about the Armbian project / community, you guys really do know your stuff and push everything to be the best / highest quality that it can be. It's just a shame that Allwinner and often the board mfrs let you down repeatedly. 
     
    I've learnt so much in a very short space of time about boot processes, dtb files and alot more from just reading this forum and asking a few questions, that's before I even consider how helpful it is to have a stable OS to work with.
     
    I'm looking forward to learning even more and having alot of fun working with these boards which I don't think I would be having if I were trying to work with the stock images from the Mfrs!
  7. Like
    Nick reacted to Gravelrash in Armbian wiki   
    IMHO - wikis are a great thing to have, but can be very time consuming to setup with agreed formats, images, page layouts etc. then there is the pre-population of the wiki itself.
     
    I don't wish to appear down on the idea, in fact if there was one, i volunteer to assist, just trying to make people aware of the initial overhead associated with creating and maintaining a wiki
     
    WIKI - GOOD!
  8. Like
    Nick reacted to tkaiser in How can I compile a headless server kernel 4.1+ for the OrangePiOne ?   
    Jef Moine has made a driver (not tested by me, not included into kernel tree and maybe that will never happen with this driver): http://moinejf.free.fr/opi2/
  9. Like
    Nick reacted to tkaiser in Help booting Orange Pi PC   
    So you tried out nearly everything but Armbian and are asking now in an Armbian forum what to do next? Really?
     
    One of the many differences between Armbian and everything you already tried out is that our OS images use sane/safe DRAM and sane/safe CPU clockspeeds. In case you bought a lemon board that might make the difference.
  10. Like
    Nick reacted to tkaiser in Pi Clusters   
    Regarding stuff on a NAS: If it's a bit more intelligent NAS (I hope you use FreeNAS or something and not proprietary bullsh*t? ) then switching to SAN mode might speed up things like an Armbian build a lot.
     
    NAS = SMB/NFS for example
    SAN = iSCSI for example (the build host just uses the remote share/LUN as a block device with a local filesystem on top which makes a difference regarding use of FS caches/buffers that can speed up a few operations 100 times or even more)
     
    Switching from NAS to SAN not only increases random I/O (or let's better say frequent write/read operations on a large bunch of small files) a lot but also helps if the network connection is the bottleneck by using transparent filesystem compression. If you put an uncompressed desktop Armbian image on a NAS (~2GB) and you've a GbE connection only then sequential read/write transfer speed won't exceed ~100MB/s. If you do the same with an iSCSI LUN and btrfs with compression=zlib on top sequential transfer speeds will be 2.5 - 3 times faster.
     
    And in case both NAS and build host have 2 NICs you might be able to double the speed again by using I/O multipathing (not possible with NAS and link aggregration).
     
    So as usual: 'work smarter not harder' is the most important factor (but using a fast SSD will do even better )
  11. Like
    Nick reacted to zador.blood.stained in Pi Clusters   
    For kernel/u-boot compilation you could use distcc. Debootstrap/image creation process doesn't look cluster-friendly, so having more than one device won't help here.
     
    And keep in mind that 10 OPi PC should build kernel faster than one OPi PC if you set up things properly, but it probably won't be faster than more or less modern x86/x64 PC, especially with SSD and ccache.
     
    Also keep in mind that you probably want to leave 1 core unused to process network and storage I/O interrupts.
  12. Like
    Nick reacted to tkaiser in Pi Clusters   
    Anyway, as long as it supports iSCSI reliably a superiour way to combine a VM (hosted on Windows, Linux or OS X) with iSCSI storage is
    define a local datastore to be used for /boot and / assign the VM as much CPU cores as possible install Ubuntu Xenial there setup iSCSI from within the Ubuntu VM create a btrfs FS on the iSCSI LUN with compression=zlib move the Armbian build environment to this place This might speed things up a lot since in situations where I/O has been the bottleneck before now local filesystem semantics improve random I/O and sequential transfer speeds explode since CPU cores jump in by compressing the data on the fly. Since the different steps in an Armbian build are either CPU or I/O intensive you won't loose performance when CPU cycles are 'wasted' improving sequential transfers between SAN and VM.
  13. Like
    Nick got a reaction from Jens Bauer in Testdisk   
    Ok, I think I may have stumbled on the solution by accident last night, no surprises in that it looks like the cause was me being an idiot as usual... 
    I use ctrl-r and bash's history alot and it would appear that sometimes I've been trying to write the .raw file to /dev/sdb1 instead of /dev/sdb. As expected the Pi fails to boot, my Kubuntu desktop can't mount the fs etc. etc.
     
    The interesting thing is that testdisk appears to be able to fix this up! I need to confirm all of this with a few more tests but if that's the case then not only problem solved, but also how awesome is testdisk!!
  14. Like
    Nick got a reaction from Jens Bauer in Armbian customization   
    You might want to look here http://www.armbian.com/using-armbian-tools/ forvarious options, between lib.config and customize-image.sh you really shouldn't have to touch the Armbian code at all. I've been through the same process as you and learnt that almost everything can be customized.
     
    As you can see from the link, running
    compile.sh COMPRESS_OUTPUTIMAGE=no   will prevent Armbian from shrinking your image.
     
    As for disabling change of root password and first login, I do exactly the same with customize-image.sh
    #Remove annoying user creation at login rm -f /root/.not_logged_in_yet echo -e "password\npassword" | (passwd root) Note that the above will change the root password to "password"
  15. Like
    Nick reacted to help40 in new motd for ubuntu/debian   
    motd looks fantastic, but I wonder how I can get rid of it ? as I do not need it?
  16. Like
    Nick got a reaction from Code4Sale LLC in A case for "Sticky" Subjects   
    Hi Joe,
    How much are the mugs and do you have any idea of how much shipping to the UK would be?
     
    I love the blue handle, and would be more than happy to buy one as long as they aren't too expensive :-)
     
    Nick
  17. Like
    Nick reacted to martinayotte in Move to dev   
    For the patches, since most were already applied, I've applied manually the 0001-ethernet-add-sun8i-emac-driver.patch follow by 0005-ethernet-add-sun8i-emac-driver.patch, but both looks the same.
     
    For iperf, you will be deceived ... I didn't provide any options except -c/-s, tested on both directions, first thru the R8188eu Wifi  :
    root@orangepipc:~# iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ 4] local 10.111.111.73 port 5001 connected with 10.111.111.11 port 43820 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.3 sec 39.8 MBytes 32.5 Mbits/sec ^Croot@orangepipc:~# iperf -c 10.111.111.11 connect failed: Connection refused root@orangepipc:~# iperf -c 10.111.111.11 ------------------------------------------------------------ Client connecting to 10.111.111.11, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 10.111.111.73 port 56344 connected with 10.111.111.11 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 45.2 MBytes 37.8 Mbits/sec and then thru eth0 :
    root@orangepipc:~# iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ 4] local 10.111.111.80 port 5001 connected with 10.111.111.11 port 53540 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.4 sec 11.6 MBytes 9.41 Mbits/sec root@orangepipc:~# iperf -c 10.111.111.11 ------------------------------------------------------------ Client connecting to 10.111.111.11, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 10.111.111.73 port 56346 connected with 10.111.111.11 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 28.5 MBytes 23.7 Mbits/sec So, lets keep Champagne for another day, and open simple Sparkling wine instead ...
  18. Like
    Nick reacted to rodolfo in Orange Pi One - adding USB, analog audio out, TV out, mic and IR receiver   
    Instead of participating in a soldering contest I looked at the OrangePiOne board and found two fully functioning USB ports ( regular and microUSB dubbed OTG ) ready to be used. Two fast connections or one fast and several slower ones via external hub for testing are usually plenty. If you need more - the solution is called OrangePiPc.
     
    Please let us know who won the soldering competition and post some pictures of successfully added DIY USB host ports before hotgluing the mess to a repurposed old X86 PC with spare USB ports
  19. Like
    Nick reacted to tkaiser in Best budget device as torrent box?   
    I've never used transmission but if you're still talking about torrent stuff then please start to think about what's that all about: collecting small pieces of large files from others and then starting to insert these chunks into large files somewhere on disk. If this is not the definition of 'random I/O' I don't know what should it describe better.
     
    Since you're not interested in active benchmarking it's not possible to help you. But I hope you understand that your problems are neither related to the board you use nor the OS distro?
  20. Like
    Nick reacted to zador.blood.stained in Armbian customization   
    This will prevent packing raw image into zip archive. To prevent image shrinking, try setting
    EXTENDED_DEBOOTSTRAP=yes FIXED_IMAGE_SIZE=4000 image size is in megabytes; you can even create image that perfectly fits your SD card (you'll need to add
    touch /root/.no_rootfs_resize to customize-image.sh to prevent unneeded FS resize on first boot)
  21. Like
    Nick reacted to Schwemmlandebene in Setting onboard LEDs with rc.local or systemd   
    Hallo,   this Mini-Howto describes how to change the behavior of the onboard LEDs during booting. There are many ways to do that. Two ways are shown here, a SysV style using /etc/rc.local and a systemd style using a configuration file in /etc/tmpfiles.d/. The systemd file is earlier interpreted than rc.local.   It is tested on Banana Pi M1*/M2/R1 with Debian jessie next (5.0x, 4.4.x). * partly   Which LEDs could be accessed? root@bananapim2:~# ls -1 /sys/class/leds/ bpi-m2:blue:usr bpi-m2:green:usr bpi-m2:red:usr * The Banana Pi M1 lists the blue LED but it couldn't be set via /etc/tmpfiles.d/ or /etc/rc.local.
      Which behaviors are possible? root@bananapim2:~# cat /sys/class/leds/bpi-m2\:green\:usr/trigger none rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usb-gadget usb-host [mmc0] heartbeat cpu0 cpu1 cpu2 cpu3 default-on mmc1 rfkill0   Edit /etc/rc.local to set the behavior of the onboard LEDs root@bananapim2:~# cat /etc/rc.local #!/bin/sh -e echo "default-on" > /sys/class/leds/bpi-m2\:red\:usr/trigger echo "mmc0" > /sys/class/leds/bpi-m2\:green\:usr/trigger echo "heartbeat" > /sys/class/leds/bpi-m2\:blue\:usr/trigger exit 0 or  edit /etc/tmpfiles.d/leds.conf.
    root@bananapim2:~# cat /etc/tmpfiles.d/leds.conf w /sys/class/leds/bpi-m2:red:usr/trigger - - - - default-on w /sys/class/leds/bpi-m2:green:usr/trigger - - - - mmc0 w /sys/class/leds/bpi-m2:blue:usr/trigger - - - - heartbeat /etc/rc.local can be executed on the console, /etc/tmpfiles.d/leds.conf needs a reboot.
      A third way may be to create systemd rules. But it doesn't work for me. root@bananapim2:~# udevadm info -a -p /sys/class/leds/bpi-m2\:red\:usr [snip]   looking at device '/devices/platform/leds/leds/bpi-m2:red:usr':     KERNEL=="bpi-m2:red:usr"     SUBSYSTEM=="leds"     DRIVER==""     ATTR{brightness}=="255"     ATTR{max_brightness}=="255"     ATTR{trigger}=="none rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usb-gadget usb-host mmc0 heartbeat cpu0 cpu1 cpu2 cpu3 [default-on] mmc1 rfkill0 " [snip]   root@bananapim2:~#nano /etc/udev/rules.d/10-leds.rules   For setting the LEDs via dts files, have a look at this discussion: http://forum.armbian.com/index.php/topic/691-banana-pro-testers-wanted-sata-drive-not-working-on-some-boards/page-4#entry5641   Regards, Steve
  22. Like
    Nick reacted to tkaiser in Tethering on Orange pi pc   
    Please stop using Armbian or at least write wrong 'articles' here and there. If you're writing about 'network manager' then you're still using an old build based on Ubuntu trusty?
     
    The most recent image is based on Debian Jessie and enables all the stuff you tell others that would miss (GPU and video acceleration). You should also consider that the whole "Armbian for Orange Pi" approach is still work in progress and images for end users are considered test versions. We had to learn that we now have partially a whole new user base that seems to lack reading skills.
     
    If you click on any of the download links eg http://www.armbian.com/orange-pi-pc/  then there is a link to the relevant forum thread where you can get an idea what 'work in progress' might mean, there is also a link to a special FAQ we maintain for you Orange Pi users (with an extra verbose changelog!) and on the top a link to our normal user documentation 'Getting Started --> Basics'.
     
    But fortunately you already found the solution to all your problems: "android is  the only way". Have fun with it... or start to read and understand, use Armbian 5.05 (desktop version -- you get GUI acceleration currently only with this) or just wait until we release a version that is labeled as "stable for end users" (no release data available). Thank you a lot!
  23. Like
    Nick reacted to Tido in Need help on Pine A64, 64bit Quad Core 1.2GHz Single board computer   
    @KH Goh  I suggest you send a sample to tkaiser - so he can try, but I must warn you: He is brutally honest. So you better attach a heat sink to it before you send it   
     
    ROTFL, I just watch the movie on Kickass Krissy the marketing chick has most probably no clue what she is talking about on sec. 0:45 - but she is sweet,
    so who cares   
    I wonder if Kai Kreuzer (german) knows WTF he is talking about - this is nor Intel or AMD and of course his openHAB will never need to use 4k Video.
  24. Like
    Nick reacted to Igor in Need help on Pine A64, 64bit Quad Core 1.2GHz Single board computer   
    General public is easy to mislead to backup the project - general public aka kick-starter community is dumb as hell. It's all about marketing. SBC's are still hot stuff and hardware development become ridiculous cheap so it's a great way to make money.
     
    As I see you already made it to persuade investors. Why bother developers community, where you don't intent to invest more then few free boards here and there and use our channels for free marketing? BTW: You can run your marketing campaign on your own website or wherever but here you need to ask for permission. I hate ads.
     
    Even before your boards become stable (to be used by professionals which is stated in your first line of your marketing appeal) you will probably restart the whole thing with a "new and better" board and hope to catch as many backers as possible. All board manufacturers are using community's current and future contribution in their business models and everyone want's to become next RPi in numbers. This is the only way you don't need to pledge anyone. Until then, we control the game.
     
    Free sample? I have a bunch of boards and so do other people who develop and contribute. I don't even think to support your boards without paradigm change toward community. You collected the money for our work and you kept it. What the f*?
     
    You are an engineer. It's is not your fault nor responsibility to think about this in such way. Don't take it personally either.
  25. Like
    Nick reacted to d4xyjen in Orange Pi Plus2 and Ubuntu 15.10   
    Thanks, it works now with even my ethernet.
     
    I have a question if you login first time you will be forced to update the password / create user (You can cancel this by pressin CTRL+C)
     
    i do not need a secondary user. how can i disable this.
     
    where you put the script file for it.