All Activity

This stream auto-updates     

  1. Past hour
  2. AES has some major weaknesses, keys are breakable through timing attacks due to it's design flaws http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.140.2835&rep=rep1&type=pdf The most secure cipher seems to be DJB's XChaCha20. XChaCha20 performs almost as well as AES, even though there is no hardware acceleration for it. Due to the performance being really good on Embedded devices, Google has selected XChaCha as the default algorithm for devices without AES acceleration. For interest's sake I ran a cryptsetup benchmark of the available ciphers on my orange Pi Zero and got these results enc dec (MiB/s) aes-xts 256b 24 21 twofish-xts 512b 19 19 aes-xts 512b 19 16 twofish-xts 256b 19 19 aes-cbc 128b 18 19 twofish-cbc 256b 17 19 twofish-cbc 128b 17 19 aes-cbc 256b 14 15 serpent-xts 512b 12 13 serpent-xts 256b 12 13 serpent-cbc 256b 11 13 serpent-cbc 128b 11 13 I was not able to test XChaCha20 / adiantum because my Orange Pi Zero is only running Kernel 4.19. XChaCha20 support will is available from Kernel 4.21 onwards https://www.spinics.net/lists/dm-crypt/msg07821.html On all the devices I've tested (even powerful x86_64 CPUs (that have AES-NI of course)) the performance of XChaCha20 was close enough that it can be used without impacting performance (for example even on my old Haswell I get >1400MB/s for enc and dec with XChaCha20) Yes AES is faster, but if it's not actually doing it's job properly, it's not apples vs apples comparison. Anyway, whether you think AES is good enough or not, XChaCha20 will continue to see increased adoption. I'd love to try it out on the H3, H5 and so on. It seems that most Armbian builds have a 4.19 Kernel, likely because Debian Stable (Buster) uses this kernel. But a as I understand it, these SoCs are running "mainline" kernels. So in theory, a 4.21 Kernel could probably be compiled for these boards without breaking anything? The alternative is waiting for Debian 11, which could take a very long time (at least 1-2 years) Kernel config tip (Source https://www.reddit.com/r/crypto/comments/b3we04/aesadiantum_new_mode_in_linux_kernel_5/ ) Apparently there are ARM kernel options equivalent to the X86 options CONFIG_CRYPTO_CHACHA20_X86_64 CONFIG_CRYPTO_NHPOLY1305_AVX2 That should be enabled for best performance. I see in https://github.com/torvalds/linux/blob/master/arch/arm/crypto/Kconfig There are options like CRYPTO_CHACHA20_NEON CRYPTO_NHPOLY1305_NEON which should definitely be enabled. Bottom line So I'm just mentioning this stuff incase maintainers are interested It would be cool to have a >=4.21 Kernel, and cryptsetup > 2.0.0 to take advantage of XChaCha20 aka Adiantum
  3. Hi, here is logs. root@aml:~# dmesg | grep -i mmc [ 2.775643] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq [ 3.007723] mmc0: new HS200 MMC card at address 0001 [ 3.008767] mmcblk0: mmc0:0001 NCard 14.5 GiB [ 3.012294] mmcblk0boot0: mmc0:0001 NCard partition 1 4.00 MiB [ 3.018144] mmcblk0boot1: mmc0:0001 NCard partition 2 4.00 MiB [ 3.023397] mmcblk0rpmb: mmc0:0001 NCard partition 3 4.00 MiB, chardev (241: 0) [ 3.472070] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq [ 3.503587] meson-gx-mmc d0072000.mmc: Got CD GPIO [ 3.538682] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 3.542690] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.551184] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.587637] mmc2: new high speed SDHC card at address aaaa [ 3.589965] mmcblk2: mmc2:aaaa SC32G 29.7 GiB [ 3.595310] mmcblk2: p1 p2 [ 3.643104] mmc1: new high speed SDIO card at address 0001 [ 4.920761] EXT4-fs (mmcblk2p2): mounted filesystem with writeback data mode. Opts: data=writeback [ 7.012116] EXT4-fs (mmcblk2p2): re-mounted. Opts: commit=600,errors=remount- ro root@aml:~# dmesg | grep -i sdio [ 3.643104] mmc1: new high speed SDIO card at address 0001 The last one do nothing.
  4. Today
  5. @jernej - nice to have the tx6 dtb in tree now i'll have a look at your patch during the next days - you mean i should apply it to plain u-boot mainline?
  6. Please help me how to install the mainline kernel.. I have found instructions but all i have found is not complete for armbian & rockpro64. I have downloaded 5.2.9 from kernel.org and compiled with rockpro64 armbian 4.4.18X .config after that make modules_install / make headers_install / update-initramfs -c -k 5.2.9 and copy dtb-5.2.9-rockchip64 vmlinuz-5.2.9-rockchip64 to /boot and make symlinks /boot/dtb -> /boot/dtb-5.2.9-rockchip64 /boot/Image -> vmlinuz-5.2.9-rockchip64 System does not boot I don't know what else to do The problem 99% is at uboot. The uboot is the most confusing thing that i have meet in linux i had no prob years with lilo and after grub but this uboot i cannot understand it how it is work... PLEASE HELP ME
  7. Perfect. Everything is snug. I'm a little worried about the power cable being damaged and me losing data.
  8. Panfrost instructions Armbian This tutorial explains how to build an Armbian image with panfrost. And what else you need to make it work. These are early drivers. Many things don't work yet. Only OpenGL 2.1 works now. You need to build an image with kernel 5.2 or later. For this you need an x86 pc with Ubuntu 18.04 or a virtual Ubuntu 18.04 x86 image. First install git, then clone the build folder from Armbian, and enter the build directory. apt-get -y -qq install git git clone --depth 1 https://github.com/armbian/build cd build Now run the script with EXPERT=yes so you can choose to build a dev image. sudo ./compile EXPERT=yes Choose "Full OS image for flashing" Then "Show a kernel configuration menu before compilation" Choose your board. If it's not in the regular list, look in "Show SCS/WIP/EOS/TVB". Choose Development version kernel configuration -> device drivers -> graphic drivers -> panfrost Let it run until it's finished. The image will be in the /build/output/images Burn it to an SD-card/eMMC/... Now we need to install all the needed software sudo apt install flex bison python3-mako libwayland-egl-backend-dev libxcb-dri3-dev libxcb-dri2-0-dev libxcb-glx0-dev libx11-xcb-dev libxcb-present-dev libxcb-sync-dev libxxf86vm-dev libxshmfence-dev libxrandr-dev libwayland-dev libxdamage-dev libxext-dev libxfixes-dev x11proto-dri2-dev x11proto-dri3-dev x11proto-present-dev x11proto-gl-dev x11proto-xf86vidmode-dev libexpat1-dev libudev-dev gettext glmark2 glmark2-es2 mesa-utils xutils-dev libpthread-stubs0-dev ninja-build bc python-pip flex bison cmake git valgrind llvm llvm-8-dev python3-pip pkg-config zlib1g-dev wayland-protocols Download and install meson wget http://ftp.de.debian.org/debian/pool/main/m/meson/meson_0.51.1-1_all.deb sudo dpkg -i meson_0.51.1-1_all.deb Download and install mesa DRM git clone git://anongit.freedesktop.org/mesa/drm cd drm meson build --prefix=/usr ninja -C build sudo -E ninja -C build install cd .. Download and install mesa graphics git clone git://anongit.freedesktop.org/mesa/mesa cd mesa meson -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false -Dprefix=/usr build/ ninja -C build/ sudo ninja -C build/ install REBOOT Optionally, update sdl (recommended) git clone https://github.com/SDL-mirror/SDL.git cd SDL mkdir build cd build cmake ../ make -j6 sudo make install REBOOT Only thing that works ok with it is supertuxkart, to install it. sudo apt install supertuxkart Panfrost - Linux games working from repo SuperTuxKart - Works well ExtremeTuxRacer - lots of glitches AssaultCube - lots of glitches Instructions by Salvador Liébana & NicoD
  9. I am convinced that so many people will be very grateful to you if you make a successful guide on how to run Cedrus + ffmpeg + MPV + Kodi on an ordinary distribution with the Mainline kernel like Armbian, even if it requires some hacks.
  10. @hexdump can you test this patch for DRAM issue? http://ix.io/1SRE Please remove all workarounds before test.
  11. I've almost all my boards hooked up with either FDTI, PL2x0x but mostly CH340 and work well with all my boards, including RockPro64, RockPi, OPi-RK3399. The only one that bother me is the NanoPCT4, where USB-TTL RX works Ok but not TX, so I can't stop U-boot for example. This NanoPCT4 issue is probably due to a protective resistor R252 which is a 2K2, I will probably try one day to short that one to see if is it the cause ...
  12. I am using a few of those. I am sure some cheap from Ebay must work as well (in specs its written Baud rates: 300 bps to 1.5 Mbps).
  13. (1st you need sha256sum tool on your computer) Example: Compare numbers in output of: sha256sum -b Armbian_5.89_Teres-a64_Debian_buster_dev_5.1.7_desktop.img with the content of cat Armbian_5.89_Teres-a64_Debian_buster_dev_5.1.7_desktop.img.sha
  14. NanoPi M4 uses 64-bit (aarch64). Raspberry Pi uses 32-bit (armhf). You need to obtain and compile a version of Qemu for aarch64. I cannot provide instructions for that.
  15. https://forum.armbian.com/topic/9277-proccpuinfo-show-only-litlle-cores-on-odroid-hc1-hints-appreciated
  16. Thanks. I see the "text" file for the sha256. What do I compare that against? I tried following the info in the link, but did not have any success. If not in the text file itself, where is the "images hash"? Thx.
  17. Can anyone provide a link to a currently available and confirmed working USB to 3.3V TTL converter that works at 1500000 bps? The PL2303 I have technically supports up to 3 Mbps but only in certain discrete steps, and 1500000 is not one of those steps. The MCP2221A only supports up to 460800 bps. The FTDI FT232 data sheet claims support up to 3 Mbps but is unclear about whether arbitrary baud rates are supported, or only discrete steps like the PL2303. Searching for a compatible USB-TTL cable to work with the RK3399 has been futile so far. A link to a confirmed working cable would be much appreciated. Confirmed working cables only. No theoretical devices, please.
  18. And after update to latest Armbian I noticed that it is not there. Update was done from Ubuntu 16.04... And before I can get AC Power supply status via: cat /sys/class/power_supply/ac/present Now I could not find anything AC Power supply related... Where is all this gone? ls -la /sys/class/power_supply total 0 drwxr-xr-x 2 root root 0 Aug 20 10:26 . drwxr-xr-x 61 root root 0 Aug 20 10:26 .. lrwxrwxrwx 1 root root 0 Aug 20 10:26 axp20x-battery -> ../../devices/platform/soc@1c00000/1c2ac00.i2c/i2c-1/1-0034/axp20x-battery-power-supply/power_supply/axp20x-battery lrwxrwxrwx 1 root root 0 Aug 20 10:26 axp20x-usb -> ../../devices/platform/soc@1c00000/1c2ac00.i2c/i2c-1/1-0034/axp20x-usb-power-supply/power_supply/axp20x-usb UPDATE: I found it, thanks to this tread: ls -la /sys/power/axp_pmu/ac total 0 drwxr-xr-x 2 root root 0 Aug 20 10:33 . drwxr-xr-x 17 root root 0 Aug 20 10:33 .. -r--r--r-- 1 root root 4096 Aug 20 10:43 amperage -r--r--r-- 1 root root 4096 Aug 20 10:43 connected -r--r--r-- 1 root root 4096 Aug 20 10:43 used -r--r--r-- 1 root root 4096 Aug 20 10:43 voltage
  19. Hallo, i want install "Qemu" on my Nanopi M4 (on Armbian Bionic). I follow these Instruction: If i eintipe tfe Command "./configure --target-list="i386-softmmu" --enable-sdl --prefix=/usr" in the Terminal, the message appears "Unsupported CPU= aarch64". I would be grateful for help. Thanks.
  20. Those driver are from Legacy ... Mainline is using "brcmfmac", and no needs for "modprobe", it is the DT that will load it if DTB is properly done. Check "dmesg | grep -i mmc", then "dmesg | grep -i sdio" and finally "dmesg | grep -i brcm" and report back those logs ...
  21. Have a look at this post. It may be the firmware between android and Linux (/lib/firmware/brcm) is different and android may work better. You'll have to do some work in android working out which one is in use and which files (usually at least 2 files) and if they differ. Don't mix DTB's between distros (Android to Linux or Linux to Linux with a bit less caution).
  22. @balbes150 Hi and thanks for Your work. Please which images without desktop have working wifi? I have A95x with S905 2/16GB (really not S905X) and with meson-gxbb-nexbox-a95x.dtb is working. But modprobe dhd, wifi_dummy etc almost says not found in the directory. Identification from android is BCM4335. I have copied DTB.img from android, but it is not working with Armbian Disco. Please is any way how to enable wifi? Thank You
  23. Igor's odroid N2 image works... Here are dmesg red lines that require investigation from somebody more expert than me: clkmsr ffd18004.meson_clk_msr: failed to get msr ring reg0 cvbs_out: chrdev devno 263192576 for disp dmi: Firmware registration failed. perf_event: read sys_cpu_status0_offset failed, ret = -22 meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl meson-pwm ffd1b000.pwm: pwm pinmux : can't get pinctrl mtdoops: mtd device (mtddev=name/number) must be supplied drivers/amlogic/efuse/efuse_hw64.c:_efuse_read:196: read error!!! meson_cpufreq_probe: Registered platform drive [ 2.063911] ff803000.serial: clock gate not found gpio-keypad ff800000.gpio_keypad: failed to get gpio index from dts efuse efuse: open efuse clk gate error!! di_get_vpu_clkb: get clk vpu error. PPMGRDRV: err: ppmgr_driver_probe called [ 2.199532] Reserved memory: failed to init DMA memory pool at 0x00000000e3000000, size 0 MiB [ 2.202554] meson-mmc: mmc driver version: 3.02, 2017-05-15: New Emmc Host Controller [ 2.203254] meson-mmc: >>>>>>>>hostbase ffffff8008629000, dmode [ 2.242335] meson-mmc: meson_mmc_probe() : success! [ 2.249480] meson-mmc: >>>>>>>>hostbase ffffff8008632000, dmode [ 2.249515] meson-mmc: gpio_cd = 1ca [ 2.252739] meson-mmc: emmc: resp_timeout,vstat:0xa1ff2800,virqc:3fff [ 2.252742] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8 [ 2.252759] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1 [ 2.252761] meson-mmc: meson_mmc_irq_thread_v3() 567: set 1st retry! [ 2.252763] meson-mmc: retry cmd 1 the 3-th time(s) [ 2.253757] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff [ 2.253759] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7 [ 2.253765] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1 [ 2.253766] meson-mmc: retry cmd 1 the 2-th time(s) [ 2.254757] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff [ 2.254759] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7 [ 2.254765] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1 [ 2.254766] meson-mmc: retry cmd 1 the 1-th time(s) [ 2.255757] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff [ 2.255759] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7 [ 2.255764] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1 [ 2.255767] meson-mmc: Command retried failed line:585, cmd:1 [ 2.286325] meson-mmc: meson_mmc_probe() : success! [ 2.286490] amlogic mtd driver init [ 2.287074] cectx ff80023c.aocec: cec driver date:Ver 2019/1/7 [ 2.287548] cectx ff80023c.aocec: not find 'port_num' [ 2.287551] cectx ff80023c.aocec: using cec:1 [ 2.287580] cectx ff80023c.aocec: no hdmirx regs [ 2.287582] cectx ff80023c.aocec: no hhi regs [ 2.287586] cectx ff80023c.aocec: not find 'output' [ 2.287591] cec: wake up flag:0 [ 2.289030] cectx ff80023c.aocec: irq cnt:2 [ 2.289243] cectx ff80023c.aocec: wakeup_reason:0x0 [ 2.289289] cectx ff80023c.aocec: cev val1: 0x0;val2: 0x0 [ 2.289292] cectx ff80023c.aocec: aml_cec_probe success end defendkey ff630218.defendkey: Reserved memory is not enough! aml_card_probe error ret:-517 cgroup: cgroup2: unknown option "nsdelegate" meson-mmc: Tuning transfer error: nmatch=0 tuning_err:0xffffffac Error: Driver 'spdif-dit' is already registered, aborting... [ 2.323264] asoc debug: aml_audio_controller_probe-115 [ 2.324305] aml_card_probe error ret:-517 Proof of work and complete dmesg is attached below dmesg
  24. What is the connection like between your power cable and the power brick? I found mine was a little loose there.
  25. I try not to aim at the total noobs with my videos. I expect people who watch my videos to know what an SBC is, and how to write an image to an SD-card. I think ETA-Prime is better for you. He's a noob explaining to other noobs Try to learn from him Then later on maybe again watch one of my videos again No hard feelings, just messing a bit.
  1. Load more activity