Jump to content

lanefu

Members
  • Posts

    1331
  • Joined

  • Last visited

Reputation Activity

  1. Like
    lanefu reacted to zador.blood.stained in Claim a task, set DUE date and start doing it!   
    I don't think we need to maintain documentation for several languages at once, so let's better have single language, but good coverage and quality.
     
    Some suggestions are noted in the first message of this topic. Also some GitHub issues need testing and checking documentation (i.e. #337), some require having a specific device to test (i.e. #286), some require creating and testing a small kernel patch (#222 and #323), and some are obsolete and will be closed after checking.
     
    Was discussed already, feel free to add your suggestions.
     
    For now I would stay at using Markdown as markup language, stay at maintaining user-level documentation in current state and maybe migrating build script documentation to GitHub wiki attached to main repository (https://github.com/igorpecovnik/lib/)
  2. Like
    lanefu got a reaction from tkaiser in Claim a task, set DUE date and start doing it!   
    I'm totally interested in participating.   Is the issues list on github the source of truth for open tasks or are there other places?
     
    PS it looks like the issues in github arent taking advantage of labels.  probably worth while
  3. Like
    lanefu reacted to Igor in Claim a task, set DUE date and start doing it!   
    [Ended]   Be active, creative, helpful and you can get a powerful board in return. First give away batch is starting 11.6.2016  
    It's not often that you can work on a software project that actually brings joy and helps people. Armbian is one of those project. It is a system that helps one build a kernel or boot images for several ARM development boards. 
     
    It's in common interest that we improve level of support and to relieve most active people. Our crew needs an upgrade:
    we need more coders, kernel hackers, UX designers to find and solve problems. If you are one of them, join our forum, join project at Github. we need properly built, packed and supported desktop with major functions: video acceleration/fbturbo, libump, mali, etc. we need to put together much better documentation. We need to fine tune MkDocs documentation tools For those who are willing to claim a task or help others to understand "how do I do this in Armbian" we prepared a dozen of boards as a small reward. It's a Xunlong Orange PI+ 2E, which design was improved based on requests from our community. It's H3 based quad core with 2G RAM, 16G eMMC, Gigabit LAN, WIFI and 3x USB.     There might be just enough boards for everyone who are willing to do some public service work. Claim your projects at this topic and each weekend we will discuss and select up to 15 people who will get the board, starting with 11.6., ... until we run out of boards. One will be notified by email and expect an answer within 48 hours, if not, board goes to somebody else.   Boards were donated and will be sent directly from Xunlong Co., Shenzhen, China.     1st batch is going to: Kriston, lanefu, vlad59, martinayotte, jeanrhum, Gravelrash, xcasex, naibmra, Xer0, madilabs, wha, @lex, WereCatf   naibmra - Bulgaria - kernel testing, try hooking to kernelci.org, docs - mid July wha - USA - 50unattended-upgrades, issue #337 - June Kriston - USA - documentation rework - July, August Xer0 - Germany - media build - July, August lanefu - USA - issue tracking improvements between forum and github - 22 June, July madilabs - Martinique - Packaging for desktop video acceleration - June xcasex - Sweden - desktop packaging - July, August jeanrhum - France - documentation and debian packaging - July martinayotte - Canada - maintain/fix DTS entries for some devices such I2C/SPI/W1 - ASAP vlad59 - France - Nanopi M1 testing and documentation Gravelrash - UK - Prepare HOWTO's & package "armbian-gc2035-fswebcam package" - June   2nd batch is going to: dimag0g, R2D2_C3PO, miked, 0x0, sysitos, jmcneill    dimag0g - France -  Packaging of OpenGL wrapper library - end of July R2D2_C3PO - Germany - Improved SD-Card partitioning - end of August miked - Canada - build system recension - end of August 0x0 - Russian Federation - Redesign site and documentation WIP + add some changes to graphics in distro. - end of July sysitos - Germany - replace/rework ramlog for systemd - end of August jmcneill - Canada - (Armbian is helping porting Freebsd)    Users were notified and were requested to provide: project name, due date and their shipping address
  4. Like
    lanefu reacted to tkaiser in Orange Pi Plus 2E now available   
    Just a small update on eMMC on Orange Pi Plus 2E (and also Orange Pi PC Plus since there it's the same). My goal was to get Armbian running from the eMMC. Igor had to provide a new mini release 5.14 yesterday since we forgot to add the necessary bits to u-boot the day before yesterday to be able to use both SD card and eMMC on Plus 2E and PC Plus.
     
    So I took this new image, burned it to a small and slow SD card lying around, inserted the card into the board and booted. The usual procedure with one automated reboot, then I logged in, transferred the image on my SD card just to overwrite the eMMC contents in one single step:
    sudo dd if=Armbian_5.14_Orangepiplus2e_Debian_jessie_3.4.112.raw of=/dev/mmcblk1 bs=10M Partition table before and after:
     
     
     
    Afterwards I ejected the SD card, rebooted and then Armbian started its usual 'firstrun' procedure now running from eMMC. There are more elegant ways to get Armbian on eMMC but I had to choose this way since I was in a hurry. As recommended I checked the eMMC for errors and performance using 'armbianmonitor -c':
     
     

     
    Interesting observation: the f3write tool seems to use a rather small block size to write the test data patterns to 'disk' (so the 9.21 MB/s should be taken with a grain of salt since the eMMC is much faster with larger block sizes -- see here for a comparison of OPi Plus 2E and BPi M2+: http://pastebin.com/L1S7b3m7 )
     
    Now the OPi Plus 2E is temporarely gone replacing a customer's 'server' (an aging Sun Fire 280 that died recently hosting an image archive for layout purposes. They allowed me to re-save all the images that were on a 8 disk RAID and with applied compression the TIFFs now fit on a 64 GB Samsung Pro SD card and are served by OPi Plus 2E which is also faster compared to the +1000W setup they used before).
  5. Like
    lanefu got a reaction from tkaiser in Orange Pi Plus 2E now available   
    sure ill take a look this evening. i was just using ttl serial.console last time. ill hook it up.to a monitor this time
     
    Sent from my SM-G920V using Tapatalk
  6. Like
    lanefu reacted to zador.blood.stained in [NanoPi M3] Cheap 8 core (35$)   
    More about NanoPi M3 - USB ports are behind USB hub...
     
    Very specific board with high enough price, "Applications" tab on their site tells enough use cases where this price is OK. Unless you need FPGA  or RISC co-processor and you know how to work with this stuff, you don't need this board.
     
    Using as headless server: NAS with 2 HDD drives for storing stuff (Samba, rsync, syncthing), headless music server (mpd controlled via IR remote or Android app).
     
    Waiting for Ethernet and USB support in mainline kernel, meanwhile it's useful for testing intermediate Armbian releases.
     
    Waiting for the bright future (at least mainline u-boot with SPL and basic support in mainline kernel).
     
    Turn lights on and off with IR remote using connected IR sensor and nRF24L01+ module
    Display stuff (weather forecast, date&time, new e-mail notifications and some other things) on HD44780-compatible LCD display.
  7. Like
    lanefu got a reaction from tkaiser in Orange Pi Plus 2E now available   
    Fired up and tested my Plus 2e
     
    I posted my DRAM test results.   Hopefully my comment makes sense.
     
    Other stuff
     
    I built latest Armbian 5.12 jessie for OPi PC from repo and booted without issue Once I symlinked my fex to /boot/bin/orangepiplus2e.bin, I was able to see the onboard eMMC, and the onboard ethernet. Ethernet was able link at gigabit.   I hit 700mbit on a quick iperf No luck with wifi with  using already included modules no luck with wifi following instructions described in this thread http://forum.armbian.com/index.php/topic/942-rebuild-rtl8189es-from-git-for-opi/page-2?hl=8189ftv#entry9574 There's a garbage Fat32 Filesystem with android stuff on the onboard flash (let me know if anybody really interested) I found this while poking around on the onboard flash
     
     

    root@orangepipc:/mnt/tmp# cat misc/wifi/wifi_hardware_info  realtek:rtl8189fs
  8. Like
    lanefu got a reaction from wildcat_paris in Orange Pi Plus 2E now available   
    my opi 2e arrived today.
     
    so i should
    * run and document dram test
    * see if the untested wifi driver works
    * make a dorky unboxing video
     
     
    ... anything else of value I can do in the name of armbian?
     
    Sent from my SM-G920V using Tapatalk
  9. Like
    lanefu got a reaction from manuti in OPI ONE wireless success   
    I had to blacklist the standard realtek module in order to get things to behave with the patched one that comes with the distro
    lane@orangepione-2:~$ cat /etc/modprobe.d/wifi-blacklist.conf  blacklist rtl8192cu Prior to blacklisting, it would just crash and reboot as soon as the wifi module loaded.  
     
    This was using one of the little rt8192 dongles from adafruit running an armbian image I built from the repo yesterday.
  10. Like
    lanefu reacted to tkaiser in Orange pi câmera gc2035 works fine with v4l2 applications   
    AFAIK @lex provided a more improved version here (already as patch that should apply flawlessly). Thread/discussion here: http://forum.armbian.com/index.php/topic/996-gc2035-driver-update-320x240640x480-20-fps/
  11. Like
    lanefu reacted to Psychopete in EmulationStation   
    Thanks for the hard work on Armbian. I finally got the EmulationStation GUI to run under OpenGL ES @ ~88fps on OrangePI PC.

    The trick was mostly building SDL2 from source and not installing it with apt-get per the instructions. Really want to avoid anything "mesa".

    IIRC, I configured SDL2 with a similar command before making:

    ./configure --host=arm-linux-gnueabihf --disable-video-opengl
    Then building EmulationStation from source using:

    cmake -DGLSystem=OpenGL\ ES .
    make
    make install

    FWIW I did symlink some shared objects into /usr/lib/ (like libMali.so)

    Next is sorting out libretro stuff.
     
  12. Like
    lanefu got a reaction from neomanic in [testing] running Armbian tools with Docker style VM   
    I fought the good fight over the weekend trying to get Armbian builder to build full images while running in a docker container.    I've had some success, and managed to build a armban 5.11 image for my Orange Pi One.. I'm running on it with wifi etc.
     
    I'm using a CentOS7 Docker 1.9.1 host and using Ubuntu 14.04 Trusty Docker Container for the Armbian builder container. (I just used the Dockerfile from the armbian git repo)
     
    Bottom line loopback management inside containers is a bad time.. especially when losetup implementations vary between host and container.   The partprobe step in the container doesn't seem to trigger appropriate feedback to udev to create partitiion devices on the /dev loop back devices.   I got around it by creating them ahead of time.
     
    Here's a few tricks to limp through.  I'll try to add more clarity later.
     
    1.  Don't. just go build a ubuntu 14.04 VM or use a turn key one on amazon and get your life back.
     
     
    From Docker Host
    #you need modules modprobe binfmt_misc modprobe loop #scrub loopbacks for good luck rm -rf /dev/loop[0-9]*     Launch armbian builder container with --privileged=true #sudo docker run --privileged=true --name=armbian -it armbianbuilder #or if you're re-using container #sudo docker start -i armbian From container   #start apt-cacher-ng service apt-cacher-ng start ​ #scrub loopbacks again in container for good luck rm -rf /dev/loop[0-9]* #create all your loop back devices mknod /dev/loop0 b 7 0 mknod /dev/loop0p1 b 259 0 mknod /dev/loop0p2 b 259 1 mknod /dev/loop0p3 b 259 2 mknod /dev/loop0p4 b 259 3 mknod /dev/loop1 b 7 1 mknod /dev/loop1p1 b 259 0 mknod /dev/loop1p2 b 259 1 mknod /dev/loop1p3 b 259 2 mknod /dev/loop1p4 b 259 3 mknod /dev/loop2 b 7 2 mknod /dev/loop2p1 b 259 0 mknod /dev/loop2p2 b 259 1 mknod /dev/loop2p3 b 259 2 mknod /dev/loop2p4 b 259 3 #build your dreams cd ~ ./compile.sh Every time you build an image you should destroy the loopbacks and recreate.  It's your best chances of getting the partitions in the loopback image to behave for mounting.
     
     
         
  13. Like
    lanefu got a reaction from tkaiser in Testers wanted: Improving THS settings   
    I have 2 Opi Ones if additional testing is needed. one with heatsink one without. i have a 2e coming also
     
    Sent from my SM-G920V using Tapatalk
  14. Like
    lanefu reacted to tkaiser in Orange Pi One - adding USB, analog audio out, TV out, mic and IR receiver   
    Wow! Guess who made the original picture: http://linux-sunxi.org/File:Orange_Pi_One_Top.jpg#filehistory
     
    Someone sent me two pictures from Orange Pi forums (which I've not visited since 5 months), I combined those two images in Photoshop so that the image alone should be significant enough to get the idea and forgot to mention "@GUTEK@ the greatest artist on planet" since I didn't even know that the great @GUTEK@ was responsible for creating this masterpiece of art (combining a screenshot from schematic with someone else's photo). I truly apologyze for my mistake. Will correct that immediately!
     
    OMFG! It was such a mistake starting to support Orange Pi H3 boards.
  15. Like
    lanefu reacted to rodolfo in OPI ONE wireless success   
    Relax - Wireless is solved for OPI ONE
     
    There seems to be a lot of confusion and missing information on how to access the dirt cheap OPI ONE wirelessly and the steps necessary to successfully use cheap Realtek USB dongles ( 8188cus, 8188eu ) with Armbian_5.10.
     
    This is a short summary of the needed materials and steps to turn your OPI ONE into a wireless client or wireless AP. There are NO custom kernels, custom modules or anything else needed, we are using stock Armbian_5.10 with stock kernel, stock modules and stock software to configure wireless access for select tested and working Realtek wifi dongles.
     
    Follow the steps without variation. Once you get wifi working you may adapt setup/configuration to your specific needs
     
    Prerequisites
     
    - OPI ONE with quality power supply 5V/2A
    - MicroSD ( 4G or higher ) with stock Armbian_5.10 installed per official instructions
    - Supported wifi USB dongle
    - LAN connection to host computer ( preferrably notebook running Linux ) for needed setup/configuration 
    - WLAN-router accessible from host computer to test wireless connections.
     
    General procedure to set up wireless on OPI ONE
     
    - Set up your OPI ONE with basic Armbian_5.10 and configure a static IP LAN-address
    - Access OPI ONE via ssh from your host computer
    - Plug in wireless dongle and load correct driver module
    - check capabilities of wifi dongle (iw list)
    - configure wpa_supplicant for client mode
    - configure hostapd for AP mode
     
    >>> all configurations will be minimal without added automagic complexities ( bridges, DHCP etc...)
     
    OPI ONE wireless client
     
    Module 8192cu works with Realtek 8188CUS dongles and provides a wireless interface wlan0 ready to be configured in managed mode with wpa_supplicant.
     
     
    nano /etc/modules-load.d/modules.conf
    =====================================

    #8189es
    8192cu
     
     
     
    nano /etc/network/interfaces (adapt to your network setup)
    ==========================================================

    auto lo
            iface lo inet loopback

    #----- lan interface ( standard maintenance connection via ssh ) 
            
    allow-hotplug eth0
       iface eth0 inet static
            address 192.168.3.164           
            netmask 255.255.255.0
            network 192.168.3.0
     
    #----- Realtek 8192cu wlan interface client ( access defined in /etc/wpa_supplicant/wpa_supplicant.conf )
                
    allow-hotplug wlan0
       iface wlan0 inet static
            address 192.168.2.164
            netmask 255.255.255.0
            network 192.168.2.0
            broadcast 192.168.2.255
            gateway 192.168.2.77
        dns-nameservers 192.168.1.1
        dns-nameservers 8.8.8.8

            wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
     
     
    nano /etc/wpa_supplicant/wpa_supplicant.conf
    ============================================

    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
    update_config=1

    network={
            ssid="<your_ssid>"
            psk="<your_password>"
            key_mgmt=WPA-PSK
            priority=99
    }
     
     
    After restarting OPI ONE it should be connected to your configured wireless router and accessible under the static IP.
    Wireless connection is working now and the rest is up to your hopefully wild imagination and creativity.
     
    Tested working dongles
     
    RTL8188CUS cheap no-name dongle from Aliexpress ( < $2 )
     
    Bus 002 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter

    RTL8188CUS Edimax EW-7811Un high quality dongle ( $10 )
     
    Bus 001 Device 008: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

    Wifi performance is not stellar, but definitely adequate. Under ideal conditions ( same room as router, little interference ) speeds of 80mbps ( measured with iperf ) can be expected. Crossing two walls at 20m distance from router the signal was still usable yielding 20mbps.
     
     
    OPI ONE access point + wireless client
     
    Surprise : You were asking for AP mode and  now you are getting AP deluxe with an extra client interface for free.
     
    Module 8188eu works with Realtek 8188EU dongle and provides TWO wireless interfaces : wlan0 is ready to be configured in AP mode with hostapd and wlan1 in managed mode with wpa_supplicant.
     
    When the dongle is plugged in and the driver correctly loaded, iw list will enumerate the drivers parameters for the two new interfaces. iwconfig will show wlan0 and wlan1.
     
     
     
    nano /etc/modules-load.d/modules.conf
    =====================================

    #8189es
    8188eu

    nano /etc/default/hostapd
    =========================

    DAEMON_CONF="/etc/hostapd.conf"


    nano /etc/network/interfaces
    ============================

    auto lo
            iface lo inet loopback

    #----- lan interface ( standard maintenance connection via ssh )
            
    allow-hotplug eth0
       iface eth0 inet static
            address 192.168.3.164
            netmask 255.255.255.0
            network 192.168.3.0

    #----- Realtek 8188eu wlan interface AP ( access defined in /etc/hostapd.conf )
                  
    allow-hotplug wlan0
       iface wlan0 inet static
            address 192.168.4.164
            netmask 255.255.255.0
            network 192.168.4.0

    #----- Realtek 8188eu wlan interface client ( access defined in /etc/wpa_supplicant/wpa_supplicant.conf )
                
    allow-hotplug wlan1
       iface wlan1 inet static
            address 192.168.2.164
            netmask 255.255.255.0
            network 192.168.2.0
            broadcast 192.168.2.255
            gateway 192.168.2.77
        dns-nameservers 192.168.1.1
        dns-nameservers 8.8.8.8

            wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


    nano /etc/hostapd.conf
    ======================

    ssid=<your-OPI-ONE-ssid>            
    interface=wlan0
    hw_mode=g
    channel=5
    driver=nl80211
    logger_syslog=0
    logger_syslog_level=0
    wmm_enabled=1
    ieee80211n=1
    wpa=3
    preamble=1
    #wpa_psk=66eb31d2b48d19ba216f2e50c6831ee11be98e2fa3a8075e30b866f4a5ccda27
    wpa_passphrase='12345678'
    wpa_key_mgmt=WPA-PSK
    wpa_pairwise=TKIP
    rsn_pairwise=CCMP
    auth_algs=1
    macaddr_acl=0
    noscan=1
    #ht_capab=[HT40-][sHORT-GI-40][sHORT-GI-40][DSSS_CCK-40]
    country_code=<your country code>
    #ieee80211d=1


    nano /etc/wpa_supplicant/wpa_supplicant.conf
    ============================================

    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
    update_config=1

    network={
            ssid="<your-router-ssid>"
            psk="<your-router-password>"
            key_mgmt=WPA-PSK
            priority=99
    }
     
     
    After restarting OPI ONE it should be connected to your configured wireless router and accessible under the static IP. On your notebook the newly created OPI ONE access point should be visible when scanning. Specify a static IP for the link and connect using the chosen password ( e.g. '12345678' ) . Feel like a hero, empty a sixpack and order more pizza....
    Wireless connection is working now and the rest is up to your hopefully wild imagination and creativity.
     
     
    Tested working dongle for AP mode :
     
    RTL8188EU cheap no-name dongle from Aliexpress (  $2.20  )
    Bus 001 Device 009: ID 0bda:0179 Realtek Semiconductor Corp. ( noname identified as 8188EU )

    Wifi performance with both interfaces active is surprisingly good. Under ideal conditions ( same room as router, little interference ) speeds of 60 (client) / 30 (AP) mbps can be expected. Crossing two walls at 20m distance from router signals were still usable yielding 20 (client) / 5 (AP) mbps.
     
     
    Troubleshooting
    Most of the problems encountered while setting up WIFI are caused by inadequate or overly complicated testing setups, procedures and rampant wild guesses. Keep it simple and solve one problem at a time. As a stable datum you should realize that the procedures outlined above DO WORK and have been adequately TESTED and RETESTED..
     
    Solution No. 1 :  Follow the steps outlined
    Solution No. 2 :  Find out where you did not follow the steps outlined
    Solution No. 3 :  Find out what you added to the steps outlined
    Solution No. 4 :  Reiterate
     
     
    Good luck with your wireless OPI ONE, enjoy and flood the forum with working solutions.
  16. Like
    lanefu reacted to tkaiser in For our get all the data fre..ks :)   
    You find most if not all used methodologies/tools listed here: http://de.slideshare.net/brendangregg/broken-linux-performance-tools-2016
     
    On a SBC I would always take care to use a minimalistic monitoring approach since when the monitoring task starts to influence the behaviour of the system (always running at highest clockspeeds for example when interactive performance governor is used) then this is simply 'Monitoring gone wrong'.
     
    Another huge difference when we're talking about more recent SBCs is the thermal/throttling and dvfs/cpufreq behaviour. Not taking that into account and looking at something more or less useless like 'load average' is just fooling yourself (without taking notice). So if you've fun watching at meaningless graphs this might be great. Otherwise better stay away from it unless it serves ok for specific use cases you're an expert in (networking stuff for example)
     
    Please just think a few seconds about a monitoring approach that does not monitor CPU clockspeeds and throttling strategies either. Is having an average CPU utilisation of 50% 'bad'? When the system is downclocking to 240 MHz at the same time to save energy and lower temperatures? Is it better when the system only shows 10% CPU utilisation since cpufreq settings let it run at 1200 MHz instead (and the SBC consumes twice as much energy due to dvfs settings)?
  17. Like
    lanefu got a reaction from tkaiser in Testers wanted: Improving THS settings   
    I'm running an Orange Pi One -- no heat sink, open sitting on my desk.    I built latest legacy armbian kernel via armbian build process.  Folllowed instructions for fex settings, etc.
     
    I've been running cpuburn for over an hour, and here's the bottom of my log.. I'll run overnight and post on a gist or something
     
    It's been holding steady with these numbers for at least 30 minutes
    23:43:33:  912MHz  4.01 100%   0%  99%   0%   0%   0%   78°C 23:43:38:  912MHz  4.01 100%   0%  99%   0%   0%   0%   78°C 23:43:43:  912MHz  4.01 100%   0%  99%   0%   0%   0%   78°C 23:43:48:  912MHz  4.01 100%   0%  99%   0%   0%   0%   77°C 23:43:53:  912MHz  4.01 100%   0%  99%   0%   0%   0%   77°C 23:43:59:  912MHz  4.01  99%   1%  98%   0%   0%   0%   78°C 23:44:04:  912MHz  4.01  99%   0%  99%   0%   0%   0%   78°C 23:44:09:  912MHz  4.01  99%   0%  99%   0%   0%   0%   77°C 23:44:14:  912MHz  4.01  99%   0%  99%   0%   0%   0%   77°C 23:44:19:  912MHz  4.00  99%   0%  99%   0%   0%   0%   78°C 23:44:24:  912MHz  4.00 100%   0%  99%   0%   0%   0%   78°C 23:44:29:  912MHz  4.00 100%   0%  99%   0%   0%   0%   78°C 23:44:34:  912MHz  4.00  99%   0%  99%   0%   0%   0%   78°C 23:44:40:  912MHz  4.00  99%   0%  99%   0%   0%   0%   78°C 23:44:45:  912MHz  4.00  99%   0%  99%   0%   0%   0%   78°C 23:44:50:  912MHz  4.08  99%   0%  99%   0%   0%   0%   78°C 23:44:55:  912MHz  4.07 100%   0%  99%   0%   0%   0%   78°C 23:45:00:  912MHz  4.06 100%   0%  99%   0%   0%   0%   77°C 23:45:05:  912MHz  4.06  99%   0%  98%   0%   0%   0%   78°C 23:45:10:  912MHz  4.05  99%   0%  98%   0%   0%   0%   78°C 23:45:15:  912MHz  4.05  99%   0%  98%   0%   0%   0%   78°C 23:45:21:  912MHz  4.05 100%   0%  99%   0%   0%   0%   78°C
     
     
    And Since I had already let it run overnight.. here's a graph of it holding steady just because
     

  18. Like
    lanefu got a reaction from David in A quick howto for Orange Pi GPIO with WiringPi Python   
    Hey I managed to get the WiringOP libraries to build with the Python WiringPi libraries on my OPI One.     I wrote up a quick gist and made a dinky fork to save some people some time:
     
    Orange PI WiringPi-Python Gist
     
    PS: Igor, TKaiser, and other contributors.   Armbian is a really great distro. I'm very grateful for all your hard work.
  19. Like
    lanefu got a reaction from Ikrk in A quick howto for Orange Pi GPIO with WiringPi Python   
    Hey I managed to get the WiringOP libraries to build with the Python WiringPi libraries on my OPI One.     I wrote up a quick gist and made a dinky fork to save some people some time:
     
    Orange PI WiringPi-Python Gist
     
    PS: Igor, TKaiser, and other contributors.   Armbian is a really great distro. I'm very grateful for all your hard work.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines