• Content Count

  • Joined

  • Last visited

About Lope

  • Rank
    Advanced Member

Recent Profile Visitors

1163 profile views
  1. @Igor Interesting thanks, I've never used iozone before. I see in your command you have not specified a specific device it will test? Is your command safe? does it only perform reads? I must say I've gotten useful information about the max device (and bus) read speed using (the command reads raw from the device as fast as possible, bypassing cache) It has been very useful for me, for quick tests. hdparm -t /dev/sda @data I saw in another thread you mentioned that you're using USB3 gigabit ethernet with your H6... I would be very interested in seeing iperf test results Setu
  2. @data Brilliant, thanks for letting us know. Can you please test max throughput with a SSD connected via USB3? hdparm -t /dev/sda
  3. AES has some major weaknesses, keys are breakable through timing attacks (dependent on implementation) due to it's design flaws http://citeseerx.ist.psu.edu/viewdoc/download?doi= I'm not sure if hardware accelerated AES-NI is vulnerable to timing attacks. But the bottom line is that AES is very complicated and easy to screw up in the implementation such that it's vulnerable to various attacks. ChaCha20 on the other hand (XChaCha20 in newer kernels) is simple to implement, (much faster than AES when implemented purely in software) and easy to re
  4. I ran the poweroff command on Orange Pi Zero 1.4 with latest mainline Armbian image and kernel updated etc. On the OrangePi Zero 1.4 5.75 Ubuntu 18.04.2 LTS 4.19.20-sunxi, poweroff should be renamed to ignite-inferno It got so hot that it burned the OEM label that was stuck to the back of the board. (little white sticker with barcode and Orange Pi Zero 256MB written on it) Then I found that halt didn't create the same inferno. Curious behavior. I need to do more testing. I found that my Orange Pi Zero idled at about 80mA, maybe that was with the powersave governor. Normal operation it
  5. Hi @guidol Thank you I just did some more searching and found your very useful forum posts about audio issues you had with orange pi zero I did try making /etc/asound.conf as per examples on the orange pi forums, which didn't help. I'm going to see if I've got all the modules loaded. I've edited my first post with more commands and outputs. I added sun4i_codec sun8i_codec_analog to /etc/modules YES, progress!!! $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1
  6. I just installed the latest Ubuntu Bionic Image with 4.x kernel, fully updated and upgraded. On Orange Pi Zero 1.4 512MB + IO expansion kit board Armbian 5.75 Ubuntu 18.04.2 LTS Linux orangepizero 4.19.20-sunxi #5.75 SMP Sat Feb 9 19:02:47 CET 2019 armv7l armv7l armv7l GNU/Linux `cat /proc/asound/cards` "No sound cards" In armbian-config, I enabled analog-codec, `update-initramfs, rebooted, but there's still no sound card. mocp complains there is no driver. speaker-test (starts like this) Playback device is default Stream paramet
  7. My (directly) above post got moved here from the Armbian H5 forum Please note: 1. I experienced the issue on a NanoPi Neo2 v1.0 (H5) board. 2. I did not experience the issue on a Rockchip SoC. Nowhere does this thread mention Neo2 or H5, so I'm mentioning this here so it can at least come up in a search. Maybe my above post got moved here in error?
  8. To reproduce issue git clone --depth 1 https://github.com/gordboy/rtl8812au.git cd rtl8812au make -j 4 #you'll see that it fails to do modpost with the stock 4.19.20 kernel. # #Previously I had compiled a custom kernel for 4.19.13. #I downgraded to my 4.19.13 custom kernel and was able to complete the above without any issue. #Kernel headers seem to be broken. #If you're going to run the next step, you should backup your armbian 8812au.ko kernel module. #next step I couldn't get to sudo make install
  9. Strange how they connected the ADC to 3.3v. Seems so unnecessary? I wonder why they bothered running a trace at all? Is it to prevent issues if it's left floating? Yes, I just thought of that, thanks.
  10. @martinayotte when you say R63 do you mean it's possible to modify the board to use AA5? Thanks for the recommendations of ADC's. What about using one of the audio inputs for measuring my analog voltage? The Audio connector has these 2 pins: 1 MICIN1P Microphone Positive Input 2 MICIN1N Microphone Negative Input Do you know if anyone has used a microphone successfully with this SoC or Neo2 kernel?
  11. Thanks @martinayotte friendly arm WiringNP ref: http://wiki.friendlyarm.com/wiki/index.php/WiringNP:_NanoPi_NEO/NEO2/Air_GPIO_Programming_with_C#Shell_Script I debugged WiringNP. Either my kernel is showing wrong info, or WiringNP code doesn't work. When I `cat /proc/cpuinfo` I get this processor : 0 Processor : AArch64 Processor rev 4 (aarch64) Hardware : sun50iw1p1 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision :
  12. I'm not sure I even want BakeBit. I'm trying to use the GPIO in my NanoPi Neo2. Specifically I want to read a digital I/O pin on/off state. And if possible I'd like to read an analog voltage from the H5's built in ADC. Now that I've looked deeper into BakeBit, it seems like the entire purpose of BakeBit is to do GPIO with an Arduino, and read the information remotely on a RbPi/NanoPi or whatever ON the Arduino's GPIO pins. If that is really what BakeBit is, then BakeBit doesn't interest me. The H5 already has GPIO and an ADC. We just need to get that working. For interest's sake
  13. Hi all, Running Armbian Ubuntu 18.04 with stock neo2 4.19.20 kernel I tried installing https://github.com/friendlyarm/WiringNP but after installation `gpio readall` says : "This NanoPi model is currently not supported." However all the wiki's and the Github page says it's supported.......? I can see GPIO in the sys fs at /sys/class/gpio/ but I was hoping to have an easier time with it than manually exporting each pin and calculating offsets for pins with scraps of info online etc. Objective 1: Read a high/low 3.3v/0v status from a GPIO Objective 2: R