technik007_cz

Members
  • Content count

    147
  • Joined

  • Last visited


Reputation Activity

  1. Like
    technik007_cz got a reaction from Naguissa in IoT with an OrangePi Zero: Node-Red + Mosquitto + ESP8266/NRF24l01   
    It would be nice to get working a second ESP8266 with a display connected to and redirect temperature and humidity data to this.
  2. Like
    technik007_cz reacted to zador.blood.stained in Armbian for OrangePi PC2, AllWinner H5   
    Not exactly "usable", but possible to use.
     
    First, write the u-boot (u-boot-sunxi-with-spl.bin located somewhere in /usr/lib/linux-u-boot-dev...) to the SPI flash, either with dd to /dev/mtd0block or with flashcp to /dev/mtd0. No offsets are needed for dd.
    Second, write a fresh image to the USB HDD (i.e. using Etcher). Old images (even after upgrades) or installed with nand-sata-install may not work and were not tested.
    Third, shut down the board, remove the SD card, power it on and hope that your HDD spins up fast enough. U-boot has a timeout for detecting USB devices that AFAIK can be changed only with recompilation and if HDD spins up long enough it won't be detected.
     
    If there are any issues, they will not be looked into without a log from the serial console.
  3. Like
    technik007_cz reacted to manuti in SD card from ancient times   
    See your 32 and go down to 16MB
     
  4. Like
    technik007_cz reacted to martinayotte in SD card from ancient times   
    That makes me remembering when I purchased my first digital camera : 1Mpix per picture, 32MB FullSD. cost me $1000 ...
     
  5. Like
    technik007_cz reacted to zador.blood.stained in no space in /armbian/output/cache/   
    Do you mean no space on the rootfs when you are installing additional packages in customize-image.sh?
    Build process uses tmpfs for the rootfs to improve performance on HDDs and reduce writes on SSDs, and tmpfs size is automatically set to 2/3 of total RAM size.
    You can disable it by adding FORCE_USE_RAMDISK=no to the build options.
  6. Like
    technik007_cz reacted to zador.blood.stained in no space in /armbian/output/cache/   
    Looks like I have to update my comments or update the code 
    This code determines whether tmpfs should be used or not based on amount of available RAM, and changing the code to
    [[ $use_tmpfs == yes ]] && mount -t tmpfs -o size=${phymem}M tmpfs $CACHEDIR/$SDCARD (replacing tmpfs_max_size with phymem) will set it to 2/3 of total RAM size
  7. Like
    technik007_cz reacted to zador.blood.stained in no space in /armbian/output/cache/   
    I watched it too when I set those values. Maximum space usage happens after the package nstallations but before running apt-get clean. I'll change 1500 to 2000 for the server images (doesn't hurt much, memory is allocated only when it's needed, so it will only disable tmpfs when you have < 3GB RAM).
  8. Like
    technik007_cz got a reaction from wildcat_paris in Claim a task, set DUE date and start doing it!   
    @tkaiser
    I want to claim last task you posted - armbian-test-reliability.
    I have 1pcs of Orange Pi One, 15pcs of Orange Pi PC and 2pcs of Orange Pi PC Plus.
    I have never tried to build my *.deb package but I like hw testing and scripting...
    Due date? 1..2 weeks? I must collect informations what can I get and what I am missing/do not know.
    I will let you know tomorrow.
  9. Like
    technik007_cz got a reaction from wildcat_paris in Raspberry Vs Orange Pi   
    @rsegoly,
    original power adapter I bought together with Orange Pi One has no issues. When I tried some cable to power it from usb it failed even I feed it with about 6V. Reason is probably thin cable and usb male <=> female conector resistance. So basically I can only confirm what @tkaiser said.
  10. Like
    technik007_cz reacted to tkaiser in Armbian SD card backup   
    While I still don't know what you're trying to achieve just a small remark: If you try to clone just a single partition with dd then the resulting clone can not start. You would've to use
    dd if=/dev/mmcblk0 of=/dev/sdb instead to get a clone (this has nothing to do with backup of course)
  11. Like
    technik007_cz got a reaction from wildcat_paris in Moving SWAP to SATA or external drive   
    Hi again,
    I found great article about swap folow link below. But I must mention something important. Swap file does not contain any valuable information. So it has not sense to move it. We just delete old, create new one and change path if it is a file somewhere on filesystem or UUID if it is partition in fstab.
    I do prefer to create swap partition on the end of sdcard or microsd because even value on label of card says it is 8GB every brand has different capacity. And this difference can be sometimes more than 100MB. So I decided to shrink root partition to 7.5GB and rest of capacity is swap partition. When I need to clone whole microsd I delete swap partition first, then I use simple dd command to clone it with bootloader and everything and for last I do create new swap partition.
     
    Somebody can say I can do same with simple script which can resize root and left swap like originally was inside root because we do not want to use swap at all on slow these cards and it is here for emergency.
     
    Answer is you have right. Swapfile on microsd card is for emergency cases only because it has low I/O bandwitch and I personally do prefer using swap partition if it is necessary on singleboard computers with sata port attached ssd's (even somebody can protest we do swaps on spindle drives because it do not lower it's lifetime).
     
    https://www.linux.com/news/all-about-linux-swap-space
  12. Like
    technik007_cz got a reaction from wildcat_paris in Moving SWAP to SATA or external drive   
    True. Between steps 4 and 5.
     
    Sent from my Redmi Note 2 using Tapatalk
  13. Like
    technik007_cz got a reaction from wildcat_paris in Moving SWAP to SATA or external drive   
    Hi mate,
    log in your system with terminal and do commands.
     
    1) you need to be sure swap is not used
    swapoff -a
     
    2) move swap to different location or create new one swap file or swap partition. Second is better, first simple to create.
    Here is example for 1G swap file:
    dd if=/dev/zero bs=1M count=1024 of=/var/swap.img
     
    3)change path and filename if necessary in fstab
     
    nano /etc/fstab
     
    4)run command "swapon -a" or reboot
     
    Sent from my Redmi Note 2 using Tapatalk
  14. Like
    technik007_cz got a reaction from rodolfo in Orange Pi PC: Wifi dongle showing 2 times   
    This is what worked for adapter below:
     
    lsusb
     
    ...
    Bus 003 Device 002: ID 0bda:0179 Realtek Semiconductor Corp.
    ...
     
    nano /etc/modules-load.d/modules.conf
     
    and I added line:
     
    8192cu
     
    Thank you @rodolfo !
  15. Like
    technik007_cz got a reaction from Godz in Orange Pi PC: Wifi dongle showing 2 times   
    Hi guys,
    I received 5pcs of Orange Pi PC recently. I prepared system for all of them based on 3.4.xxx kernel Jessie sever image. Every board with only wifi connection I cannot reach on network. I have started investigating problem and these Realtek dongles are showing up like 2 devices wlan0 wlan1. Wpa supplicant driver crashed during boot and there is some strange message in startup log about usb. I am at work now so I cannot post it but on development version I tested this morning is that wifi dongle working and successfully connected to network.
     
    Sent from my Redmi Note 2 using Tapatalk
  16. Like
    technik007_cz reacted to tkaiser in Read-only file system   
    I would better do a web search for 'overlayfs initramfs debian' and then ask if OverLayFS is available for H3 and if Armbian supports initramfs. That would be a sane approach to mount the rootfs on SD card read-only without breaking anything.
  17. Like
    technik007_cz got a reaction from tkaiser in SD card performance   
    Toshiba Memory Exceria M301 8GB MicroSDXC Class 10 48 Mbps
    http://sprunge.us/bSfN
    brand new card, result of 3rd test
    Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 637 629 7416 7420 6402 611 102400 16 6997 7375 10210 10654 10091 63 102400 512 16026 15845 22069 22070 21991 2022 102400 1024 16468 16261 22488 22488 22443 4027 102400 16384 16558 16217 22443 22442 22440 12880
  18. Like
    technik007_cz reacted to tkaiser in backup & restore   
    Cloning is not backup. Never.
     
    To create a clone from time to time that can be transferred to a new SD card on a Linux PC two steps are necessary: After connecting the card, you simply transfer the 1st MB to a file by doing:
    dd if=/dev/$card of=u-boot_spl_partition-table.img bs=1M count=1 You use the whole device here and not a partition since you want u-boot+spl. Then you mount the first partition to eg. /mnt/armbian/ and then create one huge compressed tar archive excluding uneeded stuff relying on this list (paths need to be relative therefore remove the leading slashes):
    cd /mnt/armbian/ && tar -czf clone.tar.xz --options=compression-level=9 --exclude-from=$exclude-list * Your PC is fast and SD cards are slow so this is the best variant to create an archive with minimal size in minimal time. If you want to use this stuff with a new SD card later simply write u-boot_spl_partition-table.img with dd to the new card, use parted or gparted to adjust/fix the partition table, mount the first partition and then do a
    cd /mnt/armbian/ && tar -xf clone.tar.xz But this is not backup but just a clone. Backups need versions to be able to recover from accidents. In case a x86 Linux box is involved a more reasonable approach would be to use a btrfs FS with maximum ZLIB compression on the PC and then either create snapshots on the SBC (when used with mainline kernel and using btrfs for the rootfs -- Armbian is capable to benefit from btrfs thanks to Zador!) and send them using btrfs send/receive or in case you have to use ext4 on the SBC use rsync to send the changes to the PC (and use btrfs snapshots there or rsync with hardlinks to store multiple copies of data without wasting space).
     
    For desaster recovery you still only need the 1MB file u-boot_spl_partition-table.img created sometimes before (or use the appropriate u-boot package from apt.armbian.com) and can then transfer the contents of your backup storage to a new SD card.
     
    In case you have a bunch of SBCs that need to be backed up then better use deduplication instead of compression on the Linux PC (also a btrfs feature worth a look)
  19. Like
    technik007_cz got a reaction from Igor in Division by zero in kernel.   
    Let me try...
     
    I extracted it from file linux-u-boot-bananapi_5.00_armhf.deb and used command below to write it to microsd.
     
    dd if=u-boot-sunxi-with-spl.bin of=/dev/sdx bs=1024 seek=8
     
    It was not necessary to touch anything else ... and u-boot sucessfully started kernel.
    It was u-boot problem and it is sorted out now.
     
    Thank you Igor
  20. Like
    technik007_cz got a reaction from HAZArD in LeMaker Banana-Pi-Pro not recognized & WiFi   
    Wifi is working now...
     
    I used following commands on my BananaPro board with legacy kernel and Ubuntu Trusty:
    ( Download link of used system image http://mirror.igorpecovnik.com/Armbian_4.5_Bananapi_Ubuntu_trusty_3.4.109_desktop.zip.
    Note: If this link should be different for BananaPi and for BananaPro it is not my fault :-) )
     
    # based on previous posts I decided return back old kernel version 3.4.109 for bananapi because wifi driver is not working on latest kernel supplied with system image
    apt-get purge linux-firmware-image-sun7i -y
    rm /etc/modules -Rv # apt-get cannot remove this folder during uninstall procedure # removed 20.1.
    rm /lib/firmware -Rv # apt-get cannot remove this folder during uninstall procedure # added 20.1.
    aptitude install linux-image-banana linux-headers-banana linux-firmware-image-banana linux-u-boot-bananapi -y
     
    rm -v /boot/script.bin
    ln -vs /boot/bin/bananapipro.bin /boot/script.bin
     
    echo ap6210 >> /etc/modules && cat /etc/modules
     
    # generate encrypted wifi password and copy output to clipboard
    wpa_passphrase yourSSID yourpassword
    # edit /etc/network/interfaces
    # remove "#" symbol like you can see in example below
    # replace "yourSSID" and "yourpassword" with your wifi SSID and ecrypted password
    nano /etc/network/interfaces
     
    EXAMPLE:
    # Wired adapter #1
    auto eth0
            iface eth0 inet dhcp
    #       hwaddress ether # if you want to set MAC manually
    #       pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838
    #
    # Wired adapter #2
    #auto eth1
    #       iface eth1 inet dhcp
    #       hwaddress ether # if you want to set MAC manually
    #       pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838
    #
    # Wireless adapter #1
    auto wlan0
            allow-hotplug wlan0
            wpa-ssid yourSSID
            wpa-psk yourpassword
    # to generate proper encrypted key: wpa_passphrase yourSSID yourpassword
    #
    # Local loopback
    auto lo
            iface lo inet loopback
     
    AND REBOOT and it should work like in my case ;-)
  21. Like
    technik007_cz got a reaction from Igor in B-Pi or Cubietruck + battery => poweroff means always reboot   
    I am running kernel 3.4.110-sun7i and this missed line (power_start = 1) has not been added yet. So If u connected battery to your Banana Pi clone or Cubietruck and your device instead shutdown only reboots again and again you need to add this line manually.
  22. Like
    technik007_cz reacted to wildcat_paris in linux-jessie-root-cubietruck_4.6_armhf.deb is trying to make backup link on vfat filesystem   
    "Help yourself and Armbian will help you. ARMen."
  23. Like
    technik007_cz got a reaction from Igor in mkimage: Can't open /boot/zImage: No such file or directory   
    I tested your new script on same setup like before but with Jessie running and kernel 3.4.XXX. I can only confirm it works now ! Thank you for your effort Igor !
  24. Like
    technik007_cz reacted to Igor in LANG et al env variables not properly set   
    Strangely, locales on Jessie are somehow corrupted. It could be my fault ... I am going to rebuild images soon, so I won't fix this one.
     
    Solution:
    locale-gen logout / login
  25. Like
    technik007_cz got a reaction from wildcat_paris in LANG et al env variables not properly set   
    Ok mate, but keep in mind the source of this problem can be in: corrupted system image, weak power adapter for your Lime2 board (there are lot of power adapters dropping voltage under load below "safe" values and only few good ones on the market), microSD or SD card has been removed after transferring system image too early (these card are slow and it still takes time to write all data even system say 100% written) or card reader is plugged in internal or external hub which is underpowered and causes data corruption during transfers.