wildcat_paris

@xwalter you can use the RPi SD card copier tool, it is a "community"-like tool https://www.raspberrypi.org/blog/another-update-raspbian/ if you know some git / github / compilation tools, you can try my temporary mini-fork https://github.com/golfromeo-fr/piclone or download the deb file (it may be faster) https://share.orange.fr/#QULfXfE0CX974e72652 note: I had to change a line of code because Raspbian assumes Debian Jessie and {me,others} using Trusty, "ported" tool doesn't have the same output.

[Pine64] A simple SanDisk 8GB Class 10 SDHC UHS-I Class 1 random random kB reclen write rewrite read reread read write 102400 4 2010 1993 8440 8422 8422 876 102400 16 7657 7513 16585 16622 16622 47 102400 512 11608 12550 23140 23142 23108 1567 102400 1024 12146 12519 23163 23164 23166 3001 102400 16384 12079 13288 23195 23197 23194 12536 details

@jobenvil yes that was a dead end in a previous message I mentioned https://github.com/umiddelb/armhf/wiki/How-To-compile-a-custom-Linux-kernel-for-your-ARM-device#odroid-xu4-mainline and Luisbg from Samsung Opensource Group twitted with another recipe to build from vanilla kernel 4.6 which I have built but I need to test on a spare image.

@minusdelta I am doing sftp from my virtual machine to my Lamobo-R1 board as I need all the *.deb mput *.deb mput trusty/*.deb I store my past builds on the root of the card gr@bpi:~$ ls /armbian_kernel/ dpsysquery.sh kern_4.3.3_5 kern_4.4.2_2 kern_4.5.2_1 kern_4.5.5_2 mod_noreboot.sh~ frandom-dkms_1.1-0centrych4_armhf.deb kern_4.4.1_2 kern_4.4.4_1 kern_4.5.3_1 kern_4.5.5_3 mod_noreboot.sh.keep kern_4.3.0_4 kern_4.4.2_1 kern_4.4.6_1 kern_4.5.5_1 mod_noreboot.sh dpsysquery.sh to find the related kernel packages for my board sudo dpkg-query -W "*lamobo*" "*sunxi*" the other script reinstall frandom-dkms before I reboot the board sudo dpkg -i frandom-dkms_1.1-0centrych4_armhf.deb in case I mess with a custom kernel, I have old good packages on the rootfs, so from another computer I can extract the files with "dpkg -x *.deb" and put a working kernel back on the card. note: in the current revision of the tool, I am (mis-)using $SUBREVISON variable to add a name to the deb packages => 5.12-golfromeo SUBREVISON="-golfromeo" gr@bpi:/armbian_kernel$ dpkg-query -W "*lamobo*" "*sunxi*" linux-dtb-next-sunxi 5.12-golfromeo linux-firmware-image-next-sunxi 5.12-golfromeo linux-headers-next-sunxi 5.12-golfromeo linux-image-next-sunxi 5.12-golfromeo linux-modules-4.5.5-sunxi linux-trusty-root-next-lamobo-r1 5.12-golfromeo linux-u-boot-lamobo-r1-next 5.12-golfromeo

@Spooky4672 no idea, but what do you get with zcat /proc/config.gz | grep NFS

Igor, Yes, I have noticed the XU4 little.BIG Exynos effect on the forum. one page loads fast, the second slower, the next faster, etc. depending on the core little or BIG I have my Odroid XU4 not in production mode... available for testing...

I get a kind reply from luisbg from Samsung OpenSource Group (after reading Tjoe newsfeed) https://twitter.com/luisbg/status/737239277319426048 no need to update the initramfs. The firmware knows where to look for the kernel to boot. My steps: http://pastie.org/10857895 Steps to run mainline Linux kernel in ODROID XU4 ------------------------------------------------ download latest stable from kernel.org (4.6 currently) untar; cd sudo apt-get install gcc-5-arm-linux-gnueabihf (cross-compiler, arm-linux-gnueabihf) export CROSS_COMPILE="ccache arm-linux-gnueabihf-" ARCH=arm sudo ln -s /usr/bin/arm-linux-gnueabihf-gcc-5 /usr/bin/arm-linux-gnueabihf-gcc make exynos_defconfig make prepare modules_prepare (to refresh include/generated/autoconf.h) make -j4 bzImage modules dtbs plug microSD card sudo mount /dev/sdb1 /mnt/boot; sudo mount /dev/sdb2 /mnt/rootfs make modules_install INSTALL_MOD_PATH=/mnt/rootfs/ sudo cp -rv arch/arm/boot/zImage /mnt/boot/zImage sudo cp arch/arm/boot/dts/exynos5422-odroidxu4.dtb /mnt/boot/exynos5422-odroidxu3.dtb

Unix/MacOS tools to write images to SD cards: the usual dd dc3dd & dcfldd are improved forks of dd dcfldd has also a nice "on the fly" hashing mechanism (so to avoid complex md5 or sha*) but it has many options so it is a bit complicated to use (see). I am often using dc3dd on Debian like systems because you can see realtime the % of the processing and you may leave dc3dd to manage buffering & doing the hashing on the fly: sudo apt-get install dc3dd sudo dc3dd if=Image.bin of=/dev/sdX sudo dc3dd verb=on hash=md5 if=Image.bin of=/dev/sdX hof=sdX_output.md5 Prior to dc3dd, I was using "pv" (but "pv" has some delayed display because it is linked to the piped "dd") pv -baret Image.bin | sudo dd of=/dev/sdX bs=10M also make sure all the buffers are written to the SD card sudo sync

I am not expert in the Orange Pi boards. Please, do you have UART trace (UART to USB cable) of the boot much like

@bogdanw please what is /dev/rdisk2s1? a Mac drive? https://hiseasnet.ucsd.edu/wiki/display/hsnops/how+to+format+a+USB+drive+to+be+readable+by+a+Cisco+router it looks you are writing the image to the 1st partition of the SD card? but it should be written on the whole SD card sudo dd if=Armbian_5.10_Cubieboard2_Ubuntu_trusty_3.4.112.raw of=/dev/rdisk2 ???

TK, Bazinga! well, TKKT is like TBBT

@xwalter Please can you give us more details? your are trying to compile a program "WiringOP" from source tar.gz ? or from source like git clone https://github.com/zhaolei/WiringOP.git -b h3 the help is here: https://github.com/zhaolei/WiringOP/blob/h3/README.md or is it https://www.npmjs.com/package/wiring-opwith npm command for nodejs, you need sudo apt-get install npm if you want to be root all the time sudo -s you don't need to put the source in /root your $HOME is just fine

Hello TK, yes I looked @M3, thought of Odroid-XU4, then looked back to M1 I stopped looking @M3 with your review of M1 is almost fine, comparing with Rpi2 The big deal is the power supply. I can do DIY to make a good power supply with a step-down mini-board. I am re-learning and testing electronic, even now power electronic like solar panels (or AC) regulator to fill a 12V lead battery, then trying DC/AC inverter (hoping to approach sine wave form), current regulator (I have ACS712 hall effect miniboards) So I am learning, making mistakes, learning, testing...

yes the SoC has some interesting DIY features yes ADC 12bits DAC 10bit etc. but are the kernels going to make the features work???? Hope dies last

Strange... let's see if "someone" has to comment about Lemaker

I don't see it in the "official" list of boards http://www.armbian.com/download/ http://www.armbian.com/banana-pi-pro/ Are you sure you have a 5V 2A power supply and good micro-usb cable to power the board? http://www.lemaker.org/product-bananapro-specification.html a USB tool like this one can be useful (you can find cheaper keys)

I have tried Win7 / Ubuntu firefox/chromium normal/private mode I don't see any issue with forum.armbian.com or www.armbian.com or redirection with armbian.com

RPI has microusb power too I have proper cables (tested). Armbian support... but ok... it is too late, I have ordered.

I have looked at the M3, honestly the CPU/GPU is far too powerful (& maybe overheating) with so limited interface. Better go with T3 version. looking quickly at the M3 SoC datasheet, Samsung has plagued the SoC with the same "Trusted Zone" (firmware) as Ordroid XU4. So, I have ordered a M1 1GB yesterday as a "spare" for the Raspi 2... Well Armbian have some support with the Allwinner H3 SoC => 16 USD + 10 USD

@technik007_cz @electric 1/ paranoid mode: shred the swap because it may leak sensitive information, then delete 2/ IMHO, why bothering to partition a SD card for a swap space? Considering SD card I/O is very slow, my guess just create a file on top of the ext4 root filesystem, then "mkswap" the file, then add it to /etc/fstab at the end of the list Of course, unless you are doing full hibernation (swap partition needed I guess), the extra CPU overhead of ext4 is small & less risky compared to partition manipulation.

Matteo, I had a quick look at http://www.armbian.com/cubox-i/ it is noted for vanilla : serial console only, so it may not work wit HDMI, only TTL UART. => legacy kernel is a better option. Vanilla is a work-in-progress. Vanilla kernel Bugs or limitations Serial console only Gigabit ethernet transfer rate is around 50% of its theoretical max rate (internal chip bus limitation)

Matteo, you can thank Igor as well I am using aptitude from time to time. I guess it is not your real issue. I don't know your board "cubox", so if it is working with a legacy kernel now, deal with it for some time, see what's up with Armbian. Armbian devs have many many boards to deal with. Armbian team does a great job. Maybe the vanilla kernel will come back properly for you. I know Igor & Zador.blood.stain or TKaiser are interested in SolidRun boards. my story: I have got an Odroid-XU4 (for 8 months) I got sick of Hardkernel images and so the board was getting dust. Recently Armbian released a working & security patched legacy image... I am happy. There are vanilla kernel recipes for XU4 but board makers don't help much, they rely on communities like the Armbian crew. Kind regards, Guillaume

Maybe mkswap is useful also NAME mkswap - set up a Linux swap area SYNOPSIS mkswap [options] device [size] DESCRIPTION mkswap sets up a Linux swap area on a device or in a file.

thanks for reintroducing SUBVERSION (it was LOCALVERSION once) so I can compile my kernel without getting the "apt upgrade" when version (package "5.11") collides (ok updated to 5.12) => so I don't need to modify the lib source linux-dtb-next-sunxi_5.12-golfromeo_armhf.deb linux-image-next-sunxi_5.12-golfromeo_armhf.deb linux-firmware-image-next-sunxi_5.12-golfromeo_armhf.deb linux-trusty-root-next-lamobo-r1_5.12-golfromeo_armhf.deb linux-headers-next-sunxi_5.12-golfromeo_armhf.deb linux-u-boot-next-lamobo-r1_5.12-golfromeo_armhf.deb yet after dpkg -i *.deb I have to sudo dpkg -i frandom-dkms_1.1-0centrych4_armhf.deb but ok then reboot!

Matteo, there is nothing like a foolish question when someone is serious I have never tried "aptitude safe-upgrade" I hope the way ther kernel package are made do not break this way