• Posts

  • Joined

  • Last visited

Reputation Activity

  1. Like
    wildcat_paris reacted to zador.blood.stained in [sun8i][H3] missing kernel features: /sbin/tc - We have an error talking to the kernel   
    You tested Banana Pi with mainline kernel, not H3 device with legacy kernel. I added some options to sun8i-default kernel config file, but didn't test yet if this fully solves the issue.
  2. Like
    wildcat_paris reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
  3. Like
    wildcat_paris reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    As it turned out, the images of workers.  
    The download does not occur due to a failure in the procedure of the extension section. The procedure prescribed force /dev/mmcblk0. And when you start from SD card, this device indicates the internal memory (eMMC). Where you already have the partitions from Android. If you disable the extension root partition in the script, it works (without automatic extensions section).
  4. Like
    wildcat_paris reacted to tpc010 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   

    here is a short howto to boot Armbian on Mini M8S from SD Card.

    You have to change the u-boot environment to check the SD-Card and then start a autoscript script.

    To boot the Armbian image you have to change some files from Armbian, change all mmcblk0 to mmcblk1 in file /etc/fstab /etc/init.d/firstrun /etc/init.d/resize2fs

    You need the file boot-s905.txt and have to convert it to autoscript, the Mini M8S u-boot can't work with Armbians u-boot boot.ini.
    setenv cec "cecf" setenv mesontimer "0" setenv nographics "0" setenv condev "console=ttyS0,115200n8 console=tty0 consoleblank=0" setenv verbosity "255" setenv bootargs "root=/dev/mmcblk1p2 rootwait rootflags=data=writeback rw ${condev} no_console_suspend hdmimode=${hdmimode} m_bpp=${display_bpp} fsck.repair=yes loglevel=${verbosity} net.ifnames=0" setenv initrd_loadaddr "0x13000000" fatload mmc 0:1 ${initrd_loadaddr} uInitrd fatload mmc 0:1 ${loadaddr} zImage fatload mmc 0:1 ${dtb_mem_addr} dtb/meson8_Mini-M8S.dtb fdt addr ${dtb_mem_addr} if test "${mesontimer}" = "1"; then fdt rm /timer; fi if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi booti ${loadaddr} ${initrd_loadaddr} ${dtb_mem_addr} Convert it with u-boot tools to autoscript.
    mkimage -A arm -O linux -T script -C none -d boot-s905.txt s905_autoscript Copy it to SD-Card to the boot partition, and also copy the file "meson8_Mini-M8S.dtb" the Boot partition in folder "dtb".

    Now open the case and connect the UART connector.
    Read this Howto for more informations.
    setenv preboot "run factory_reset_poweroff_protect;run upgrade_check;run bootmode_check;run init_display;run storeargs;run upgrade_key;run user_start;run switch_bootmode;" setenv user_start "if mmcinfo; then run linux_start_mmc;fi;" setenv linux_start_mmc "if fatload mmc 0 ${loadaddr} s905_autoscript; then echo ===[LINUX START from mmc]===;autoscr ${loadaddr};fi;" saveenv After reboot the Mini M8S should boot from SD-Card.
    Please check the lines and be careful, an error can brake the possibility to interrupt the boot sequence.
    UPDATE 2016/09/08:
    after apt-get distupgrade, the uboot package was updated and this was rewriting the uboot data from emmc, but the Mini m8s is not working with the uboot from Hardkernels Ordroid uboot.
    I got this after boot:
    ***** Warning!! ************************************************** ***
    * This board have not been autorized or product keys are not valid. *
    * Please contact with Hardkernel or your distributor *
    ************************************************** *******************
    After shorten the emmc at boottime, I was able to recover the stockimage via OTG USB and amlogic's windows tool, thanks to balbes150, I found a info on freaktab.
    So after first armbian boot from SD, you have to remove the uboot package with "apt-get remove linux-u-boot-odroidc2".

  5. Like
    wildcat_paris reacted to RagnerBG in BPI new images   
    Hello. Browsing through my email i note something from long forgotten, useless http://forum.banana-pi.org. It's about some new images they "release" like:
    BPI-R1 new image:raspbian-jessie-bpi-m1-m1p-r1.img 2016-07-13

    BPI-R1 new image:ubuntu-mate-16.04-desktop-armhf-raspberry-pi-bpi-m1-m1p-r1-sd-emmc 2016-07-21
    BPI-R1 new image: Kanux-Beta-3.3.0-preview-bpi-m1-m1p-r1.img 2016-07-15
    There is a note - "kernel 3.4.112 (based on armbian's build)", so hem, congratulations i guess. Looks like you guys are official support for team bpi now .
  6. Like
    wildcat_paris reacted to Gravelrash in NanoPi M2 - Any interest?   
    best i can find is this - should keep me out of mischief on when the weather turns nasty
    i will load it up - stick a mahooooosive heatsink on it with a fan and use it as my apt-cacher-ng unit
  7. Like
    wildcat_paris reacted to Gravelrash in NanoPi M2 - Any interest?   
    donating to @lex
  8. Like
    wildcat_paris reacted to Gravelrash in NanoPi M2 - Any interest?   
    @wildcat_paris : 
    Thats probably why i was given it.... It can go and live on the shelf along with the Remix Mini.....
  9. Like
    wildcat_paris reacted to tkaiser in Orange PI PC operating temperature   
    You seem to confuse ambient temperature (H3 is specified to be operated in environments that are as hot as 70°C) with internal temperature (look for 125°C in the datasheet). I would suggest the following:
    Install RPi-Monitor (sudo armbianmonitor -r) Read through this issue to get some understanding of the relationships between temperature, throttling and performance Watch the graphs, maybe play a bit around with THS settings Eventually stay with Armbian's defaults (we wasted days already trying to develop best suited thermal settings possible -- no need to further waste time with this stuff unless you have special needs)
  10. Like
    wildcat_paris reacted to Igor in [SOLVED] Orange PI PC H3 Winner, compiled with igorpecovnik jessie desktop   
    (supported) TFT LCD screens should work fine, drivers are already built into kernel as modules (noted here http://www.armbian.com/orange-pi-pc-plus/#legacy ).Whatever you find on our download page should be safe to build, but keep in mind that you are using development version of our tools by default.
    BTW: we are writing docs to save our time and keep forum post quality without repeating things more than needed.
  11. Like
    wildcat_paris reacted to aliceander in armbian and sound   
    Did you read through the pinned thread [Tutorial] Orange Pi One - adding USB, analog audio out, TV out, mic and IR receiver  at the top of the forum?  I know it has some information on audio; hopefully it has something pertaining to your issue.
  12. Like
    wildcat_paris reacted to @lex in Stripe artifacts (or not) from a gc2035 sensor   
    Answer: http://forum.armbian.com/index.php/topic/1517-bird-watching-station-opi-one-and-aliexpress-csi-cam-with-armbian/#entry12699
  13. Like
    wildcat_paris got a reaction from Tido in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    When possible, please, send us bird images from your special device
    @TheTeam: Tido, Alex, Thomas, Mikhael
    you rock for the birds 
    note: I only take the credit for adding [bird watching station] in the title

    note: if someone wants to preorder the Pepsi Co Phablet
    we could port Armbian... no, I am kidding
  14. Like
    wildcat_paris reacted to aliceander in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    Using all brand new equipment (an Orange Pi One, gc2035 cam on expansion board, 5V3A power supply, and fresh jessie server image updated/upgraded to 5.16) I can verify that steps suggested by @lex work and I can get a nice image from my CSI video cam with fswebcam. 
    domo arigatou gozaimasu
  15. Like
    wildcat_paris reacted to aliceander in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    I would also like to thank everyone too.  I haven't been derided for asking silly questions (and, trust me, I KNOW some of them are dumb; but I'll only stay ignorant until I ask and learn).  Suggestions are quick and varied, and necessary changes are quickly implemented.  I consider this an ideal environment.
    I found this forum because I'm exploring different form factors.  So many choices!  My recent experience is with the orange pi one, but I'm really excited about the NanoPi Neo.  I found the discussion in another thread about that interesting so I ordered two, and when I get them I plan on following the suggestions to test armbian.
  16. Like
    wildcat_paris reacted to tkaiser in Marriage between A20 and H3, UPS mode, sunxi-pio utility   
    Let's start with a weird image first:

    In the plastic box is an Olimex A20-Lime2, a 2.5" HDD with 2TB and Olimex' largest battery with 6600mAh. Mounted on the top cover (box standing on the side) is a Banana Pi M2+ (to be replaced with NanoPi M1 or OPi One/PC in the future)
    Why Lime2? Since this board from our friends at Olimex is designed intelligently and provides DC-DC step-up converters on the board providing the ability to power also the connected SATA disk when running from battery (unlike most other A10/A20 boards that do only provide 5V on USB ports in battery mode but not to the disk!). And since A20 is perfectly supported by mainline kernel (I run 4.6.4 on it with btrfs on both SD card and connected SATA disk. Since the Lime2 is used as monitoring/rsyslog host btrfs compression is active and the 2TB HDD might store up to 20TB of raw log/monitoring data)
    Why BPi M2+? Since board was lying around and I have no other use for it (SinoVoip sent me a review sample a while ago). The idea to combine A20 with a H3 device was simply to add a camera capable and performant device that is ultra cheap (does not apply to BPi M2+ but to NanoPi M1 or OPi One for example). The H3 device will be used to off-load some stuff (eg. OpenVPN encryption), to capture images and do other hardware monitoring (eg. checking temperature in server racks using 1-Wire sensors)
    Both boards in this mode run up to 8 hours on battery (6h when the 2 TB disk is also always spinning -- but I use a large 64GB Samsung EVO in the Lime2 and wake up the HDD only from time to time to move data over from SD card). And in this special mode the Lime2 is acting as UPS for the H3 board too since BPi M2+ is powered through Micro USB from Lime2's left USB type A receptacle. The same USB connection is also used as a 'private' network utilizing Ethernet gadget driver on the H3 device.
    BPi M2+ is running our sun8i legacy kernel, g_ether module is active and configuration using a link local address as outlined in this thread. Therefore as soon as BPi M2+ boots and brings up his usb0 interface the board appears as Ethernet USB dongle on the Lime2 and can be used easily with the following settings as directly connected network device (providing ~120 Mbits/sec throughput over the USB cable):
    This USB connection can now be used as a directly wired network connection (BPI M2+ is and Lime2 and both can interact through this connection or use it as 'heartbeat' connection to monitor network outages). And using BPi M2+ or NanoPi M1 or NEO the very same USB connection can also be used to power the H3 device (not with Oranges there a hardware mod is needed).
    Now the fun part: In case the USB powered H3 device freezes or is shut down and has to be restarted... how to do so? Some/most A10/A20 boards provide the 5V on their USB ports not directly from DC-IN but through their AXP209 PMU. And if the board is designed that way, power can be switched on/off on request. This is where the sunxi-pio tool gets interesting since with this tool you can query and switch pin state.
    In the above example BPi M2+ is powered through Lime2's left USB port. VDD_USB of this port can be controlled through PH06 pin. So to cut power from Lime2 to BPi M2+ all I have to do is
    sunxi-pio -m PH06'<default><default<default><0>' And to provide power again, it's the opposite:
    sunxi-pio -m PH06'<default><default<default><1>' (at least on my Lime2 the left USB port is more reliable than the right port that can be controlled through PH03 pin). To be able to use the sunxi-pio tool you need a recent sunxi-tools version. As Armbian user you don't have to care since we ship always the most recent version.
    Not all A10/A20 boards support this and pin mappings differ between different boards. So where to look? In the fex files (don't trust them blindly, some vendors horribly suck providing documentation for their own hardware, compare the pin mappings in bananapiprolcd7.fex and bananapipro.fex for example).
    EDIT: Checked with both Banana Pi and Banana Pro: The USB voltage pin mappings in the fex files are plain BS and do not work (obviously 'copy&paste gone wrong' when they copied all of CubieTech's work in the beginning)
    I let a script check the fex files of all Allwinner boards we currently support. Two H3 devices show the ability to switch USB voltage (OPi 2 and Plus/Plus2 -- the pin here most probably controls power for the internal Terminus USB hub) but all the others are A10/A20 based:
    Edit: But at least on H3 Orange Pi boards it's possible to toggle power available on Micro USB port from userspace.
    So if you want to switch power on the USB ports of a Banana Pro you would not use PH03/PH06 but PH00/PH01 instead (and yes, sunxi-pio works with exactly these settings/syntax even when the board runs vanilla/mainline kernel). Since we're talking about A20 Bananas now: These devices do not provide power to a connected SATA disk when running on battery unlike Olimex' boards. So in case you want to ensure that a connected SATA disk keeps spinning when DC-IN is not available then you have to DIY a cable solution taking power from the 2 USB ports and feeding SATA power this way (the SATA power connector on Banana boards is directly wired to the Micro USB DC-IN jack so you can both provide DC-IN here more reliably and have to keep in mind that battery/AXP209 is not involved at all)
    BTW: sunxi-pio can be used for more than just switching power on USB ports. Simply call it without arguments to get the idea / help text. Anyone trying to decrease consumption of his Allwinner board might love this tool since you're able to switch off on-board consumers from user space.
  17. Like
    wildcat_paris reacted to aliceander in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    Your magic incantations work perfectly! 
    I added "gc2035 hres=0 mclk=34"  and "vfe_v4l2" to /etc/modules and rebooted, but that didn't seem to have the same effect as when they were added manually.  Perhaps /etc/modules doesn't like arguments?  If so, is there a way to make it stick?  Should /etc/modules accept arguments?
    Also, "-p YUV420P" seems critical for fswebcam.  I'll study up on that this weekend so I'll know more about that soon.
    On a minor note, I may have damaged my little camera by checking, undoing, redoing, rechecking, undoing, and redoing the cables countless times trying to be sure I didn't have things loose or in backwards.  My jpg image has a lot of bright green horizontal stripes across the bottom.  I have another new orange pi one, camera, and power supply, so I'll set that up from scratch to verify.  My power supply is 5V3A, so I don't think that should be a problem.  The main thing is that I can get images!!!!
  18. Like
    wildcat_paris reacted to aliceander in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    Your suggestions worked.  I added (well, uncommented) the following two lines in /etc/modules
    And created /etc/modprobe.d/gc2035.conf with the following
    options gc2035 hres=0 mclk=34
    The modules now load as I'd like across reboots.
  19. Like
    wildcat_paris reacted to zador.blood.stained in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    Yes, /etc/modules should support module parameters, but you can also put
    gc2035 in /etc/modules without any arguments and put
    options gc2035 hres=0 mclk=34 in /etc/modprobe.d/<some-file-name>.conf
  20. Like
    wildcat_paris reacted to tkaiser in [bird watching station] OPi One and Aliexpress CSI Cam with Armbian   
    I followed these procedures and can confirm that it works:
    tk@orangepipc:~$ fswebcam --Hflip 1 --rotate 180 -r 640x480 -p YUV420P - > cam640x480_1.jpg --- Opening /dev/video0... Trying source module v4l2... /dev/video0 opened. No input was specified, using the first. rc: 0 - get value: 1 rc: 0 - set value: 1 --- Capturing frame... Captured frame in 0.00 seconds. --- Processing captured image... Flipping image horizontally. Flipping image vertically. Writing JPEG image to '-'.
  21. Like
    wildcat_paris got a reaction from rodolfo in Differences between Armbian and classic Debian   
    le travail laborieux
  22. Like
    wildcat_paris reacted to zador.blood.stained in Armbian boot process unification   
    You don't have to have a rootfs entry in fstab - just pass "rw" and "rootflags" to kernel command line to mount it from kernel
    setenv bootargs "root=${uuid} rw rootflags=noatime,nodiratime ..." lime2-emmc is mainlined - separate DT file will be available in kernel 4.7
  23. Like
    wildcat_paris reacted to slinde in OrangePi PC $8.54 gearbest   
    I have bought from Gearbest 50+ times. I find them trustworthy and they deliver what they promise. If there is any trouble they have a customer service that works quite well for being a chinese webshop. Sometimes there are misunderstandings but they usually sort it out in the end.
    I will put in a order for an Orange Pi PC, today the price following your link is $8.57!
  24. Like
    wildcat_paris got a reaction from Pascal in [Lime/next/jessie/console] Armbian compilation stops   
    Bonjour Pascal,
    Don't worry because Igor, Zador.blood.stain, TK have already to deal with the French wildcat_paris.
    Have fun with Armbian = Amuse toi bien et pense à Virtualbox
  25. Like
    wildcat_paris reacted to chradev in Armbian boot process unification   
    Hi to All,
    I decided to start this new tread for searching of the best solution for unification of the boot process from any available media.
    Main target is Armbian next and development branches and mainline Kernel and U-Boot.
    Boot device can be eMMC, SD/MMC, USB Flash/HDD and SATA HDD/SSD probed in given order.
    In case of booting from eMMC, SD/MMC and USB Flash Read-Only Root FS can be used optionally.
    In case of booting from SD/MMC or USB Flash eMMC and / or SATA devices can be updated automatically.
    Some effort in this direction was done by me and described in Armbian Customization thread.
    The tests was done on Olimex' A20-Olimexino-Lime2-eMMC (HW rev. E) board with following additional staff:
    60GB SATA SSD with SATA-CABLE-SET MOD-WIFI-R5370 mounted on the rear panel - only antenna outside USB-ETHERNET-AX88772B - optional BATTERY-LIPO6600mAh ALUMINIUM-HEATSINK-20x20x6MM later changed with special high efficient cooling system A10-OLinuXino-LIME-BOX later changed to water and dust resistant solution based on Aluminum box FTDI FT4232H based USB Hi-Speed Serial/Hub Module AC/DC 5V/4A wall adapter Dual LED Red + Blue Display Digital Voltmeter Ammeter DC 3.5-28V 3A Additional User Push Button and 3 LEDs are connected via Lime2 GPIO-1 connector 1-Wire GPIO based Master and additional Device Boot control is implemented via Lime2 GPIO-1 connector Reset, Power On/Off buttons and Charge LED are wired to front panel doubles Console, DC-IN, USB and Ethernet connectors are wired to rear panel doubles The current status is:
    U-Boot is patched to:recognize eMMC; search a boot-able device on SATA, USB, SD/MMC, eMMC etc.; boot from the boot-able device with the highest priority; send to the kernel via the command line right root=PARTUUID=${uuid}; Kernel is patched to recognize eMMC; firstrun script is modified to resize right MMC device (mmcblk0 or mmcblk1); eMMC and SATA device experimental update scripts are implemented and tested; it is investigated the classical and overlayfs way to run Debian on RO Root FS; Described staff is working fine on latest Armbian (5.17), Kernel (4.6.3) and U-Boot (2016.05). Not solved issues are:
    to mount root accordingly without explicit setting in /etc/fstab; to resize root partition from firstrun script in case of USB and / or SATA devices; to prepare and use Read-Only Root FS on eMMC, SD/MMC and USB Flash optionally; to start eMMC and /or SATA device update procedure from firstrun script if boot from SD/MMC or USB Flash. The main use case will include following steps:
    If the system will be setup for the first time SD/MMC has to be used for been able to install U-Boot on empty eMMC; In case of next FW update USB Flash will be used to boot from by installed on eMMC U-Boot; Booting from SD/MMC will be forced by pushing of user button or renaming of /boot/boot.scr file on the devices with higher priority; Booting from USB Flash will be done always when present because of highest priority; firstrun script will be executed always if booting from image cloned device and the system will reboot if necessary; At the end of firstrun script eMMC and / or SATA device update scripts will be executed to update them from image or SD/MMC or USB Flash itself. The following staff was used to customize Armbian:
    Mainline U-Boot patch to enable eMMC:
    Mainline U-Boot patch to change boot order:
    Mainline U-Boot boot script:
    Mainline Kernel patch to enable eMMC:
    Change in do_expand_rootfs() function of firstrun script to recognize right MMC device to resize:
    # DEVICE="/dev/"$(lsblk -idn -o NAME | grep -w mmcblk0) DEVICE=$(mount|grep ' / '|cut -d' ' -f 1 | cut -dp -f1) Reboot script and service looking for user button push:
    Experimental script to update eMMC from image:
    Experimental script to update SATA SSD from image:
    Whole customization process with more details and test results can be found on Armbian Customization thread.
    Latest prototype insides and test results can be found in the attached files.
    Any ideas, comments and references are welcome.
    Best regards