Jump to content

hal8k

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by hal8k

  1. Hi Werner, Yes I'd like to try and help out. I have OPi zero Ver1.5 and can cross compile from my linux mint 64bit desktop. Have also got a git account. Is it just a matter of: git clone https://github.com/armbian/build cd build ./compile.sh After the kernel is built is it just a matter of copying the kernel into the Orange Pi and rebooting. Or will I have to build the modules? Thanks for further advice.
  2. Using Orange Pi zero Revision 1.5 loaded with Armbian Buster 21.08 ArmbianMonitor Logs: http://ix.io/3UXu The board is reporting very low temperatures, with htop and when I ssh on the login banner. Temperatures range from 3 or 4 C but also seen -3404C screenshot https://imgur.com/a/SCLVMYl Previously with Armbian 19.11 and kernel 5.4 temperatures were reported normal 33 or 37C I dont overclock and run my SoC from 480 to 960MHz (keeps current and power down). Screenshot of Armbian 19.11 kernel 5.4 and kernel 5.10.4.sunxi temperatures were normal (30 - 37C) Screenshot below: https://imgur.com/a/cFoXG8H Not sure what has changed in kernel 5.10.60, will it be safe to download to kernel 5.4.88 or will it break my installation? Everything else is working fine. Thanks in advance
  3. I have exactly the same but on OrangePiZero I did a manual sudo apt-get update sudo apt-get upgrade Just before I rebooted, I tried a lsmod and no modules were found with kernel 5.15.25 I tried to run modinfo and it told me could not get module info "exec format error" I posted a screenshot: https://imgur.com/a/7VBkrnt Is this a common problem with a kernel upgrade, to 5.15.25 ? This is three different boards but same kernel. I'm going to have to reload my image as I cannot access my orage pi zero now.
  4. Hi Guidol, Apologies for a late reply. First, my mistake H2+ is a 32bit instruction set , the "stockfish 9 64" is the name of the engine in xboard. I just ran another benchmark on my OPi Zero and got similar results: Total time (ms) : 57136 Nodes searched : 5023629 Nodes/second : 87924 I then checked results on my laptop running linux Mint 19.3LTS. I have both stockfish 8 and stockfish 13 installed on the laptop. A similar benchmark results: Stockfish 8 Total time (ms) : 6211 Nodes searched : 5926706 Nodes/second : 954227 Stockfish 13 Total time (ms) : 6935 Nodes searched : 3766422 Nodes/second : 543103 Which indeed gives an apparent poorer benchmark ?? However dont pay too much attention to the benchmark. You can try this on your Orange Pi Install the armbian build of Stockfish 9, then load xboard. Set the time limit to 1 minute, then load first engine as stockfish14 and second engine as stockfish 9. Make sure there is a tick so they dont use the opening book. Set mode to two machines then new game. After two blitz games of 1 minute, stockfish 13 beat stockfish 8 in 64 moves and second game in 72 moves, even though higher nodes/sec were displayed by stockfish 8. I then set the time limit to 2 minutes and played engines against each other, this time it was a draw after 96 moves by 3fold repetition. I would say that stockfish14 will beat the earlier versions, I've not had chance to increase time limit to say 5 minutes but expect stockfish14 to be dominant.
  5. For simple benchmark just run stockfish bench My Orange Pi Zero on Armbian is underclocked to 400MHz with maximum of 648MHz core speed Results from Stockfish 9 64 bit: =========================== Total time (ms) : 57264 Nodes searched : 5023629 Nodes/second : 87727 The Stockfish 9 results are from the Armbian repo, sudo apt install stockfish. Faster than Pi Zero and drawing less than 200mA with underclocking I've not compiled Stockfish 14 but would expect a higher nodes/second on a later verion
  6. Hi Dolf, See this link on github, in particular the paragraphs "read this" and "issues". When i was using the internal wifi, pings to the OPi from network resulted in dropouts and lags, but from OPi to network were better. https://github.com/fifteenhex/xradio/blob/master/README.md So as a workaround I have a USB wifi N dongle from Ali Express (very cheap) https://www.aliexpress.com/item/1005002626370066.html?spm=a2g0o.productlist.0.0.5eda3ec9E8E9W2&algo_pvid=c6007224-e8da-49fd-a509-c30ed26bc42f&algo_exp_id=c6007224-e8da-49fd-a509-c30ed26bc42f-11 This is recognised by the kernel in current Armbian buster and works better. Although it doesnt answer your question, these dongles are very good and you can use an external antenna of greater gain if you wish.
  7. Armbian Monitor http://ix.io/3qFr Im using Orange Pi Zero with Armbian Buster and have ir-keytable installed. The problem I'm facing is the the kernel is repeating the keycodes too fast. See this useful link , half way down section 2 https://www.sigmdel.ca/michel/ha/opi/ir_03_en.html#ir_keytable My remote control is using rc5 protocol and I have set delay and repeat delay with ir-keytable: sudo ir-keytable -D 500 -P 500 -d /dev/input/event0 Testing with evtest (event 0 on the Orange Pi 0) displays key events in the consol, and ignores delays set by ir-keytable, keys are repeated about 5 times a second. If anyone wants to test a remote after installing ir-keytable then a quick way to check a remote is to install all protocols with: sudo ir-keytable -p all ir-keytable -t Thanks in advance to anyone who can help I may go back to using lirc if there is no way around this problem.
  8. I use the same gpio library and all pins are working on my OPi Zero. It may be worth re-soldering pin 9 on the IDC header and see if the soldered connection is at fault. Below is a very quick bash script to set all pins as outputs, activate them, then turn off all pins you can use as a check. There's probably more efficient ways of doing the same thing #!/bin/bash gpio reset; sleep 1; for n in {0..30}; do gpio mode $n out; gpio write $n on; done gpio readall sleep 3 for n in {0..30}; do gpio write $n off; done gpio readall; sleep 3; gpio reset
  9. You cant use two different network connections at the same time as packets can only be routed to one gateway (usually your router or whatever device is acting as your default gateway). If you have both WLAN and Ethernet connected simultaneously then the metric with lowest value will be used: The Metric field indicates the cost of a route. If multiple routes exist to a given destination network ID, the metric is used to decide which route is to be taken. The route with the lowest metric is the preferred route.
  10. Hello, you did not state what you lowered your clock speed to, but on my Orange Pi Zero I set the clock to 400MHz and maximum clock speed to 648MHz using conservative governor. This draws around 180-210mA and runs cool at 31C without a heat sink. For IoT you don't need GHz of processing power and 4 cores at 400MHz beats my RPi 2 in terms of both performance and power consumption. The link from Werner is excellent however and you may be able to reduce consumption more.
  11. I'm running my Orange Pi Zero headless on Armbian Buster 20.11.6 Last check uptime was 6 days, but now I find its rebooted and I think this is due to unattended security packe upgrades. The package is installed unattended-upgrades/stable,now 1.11.2 all [installed] automatic installation of security upgrades Looking in /etc/apt/apt.conf.d 01autoremove 20auto-upgrades 70debconf 01autoremove-kernels 50apt-file.conf 71-armbian-no-recommends 02-armbian-compress-indexes 50command-not-found 81-armbian-no-languages 02-armbian-periodic 50unattended-upgrades Is it safe to just remove unattended-upgrades or is there a better method to prevent unattended-upgrades from running? Thanks in advance.
  12. Hi Igor, Thanks I solved it. Turns out the pcm.read error occurs when you try to record (read) from an input that is disabled in alsamixer. I cant find the post I followed, but solution was alsamixer F4 for capture and then space var on Microphone to enable input. For some reason I am limited to one post/day sorry for delay. Will try and append solved to title
  13. I'm running Armbian Bionic on OPizero. I have a problem using arecord on the mic input. Audio codecs have been enabled but when I run following command to record I get a pcm read error arecord -D plughw:0,0 -d5 -f cd test.wav Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo arecord: pcm_read:2103: read error: Input/output error There is no recording and file is just 44 bytes. pi@orangepizero:~$ ls -l test.wav -rw-r--r-- 1 pi pi 44 Jan 6 20:44 test.wav The output from this command never finishes after 3 seconds and I have to use ctrl+c to breakout: arecord -vvvv -d 3 /dev/null Recording WAVE '/dev/null' : Unsigned 8 bit, Rate 8000 Hz, Mono Plug PCM: Linear conversion PCM (S16_LE) Its setup is: stream : CAPTURE access : RW_INTERLEAVED format : U8 subformat : STD channels : 1 rate : 8000 exact rate : 8000 (8000/1) msbits : 8 buffer_size : 4000 period_size : 1000 period_time : 125000 tstamp_mode : NONE tstamp_type : MONOTONIC period_step : 1 avail_min : 1000 period_event : 0 start_threshold : 1 stop_threshold : 4000 silence_threshold: 0 silence_size : 0 boundary : 2097152000 Slave: Hardware PCM card 0 'H3 Audio Codec' device 0 subdevice 0 Its setup is: stream : CAPTURE access : MMAP_INTERLEAVED format : S16_LE subformat : STD channels : 1 rate : 8000 exact rate : 8000 (8000/1) msbits : 16 buffer_size : 4000 period_size : 1000 period_time : 125000 tstamp_mode : NONE tstamp_type : MONOTONIC period_step : 1 avail_min : 1000 period_event : 0 start_threshold : 1 stop_threshold : 4000 silence_threshold: 0 silence_size : 0 boundary : 2097152000 appl_ptr : 0 hw_ptr : 0 ^CAborted by signal Interrupt... arecord: pcm_read:2103: read error: Interrupted system call The commands work fine on Linux <Mint 19.3 (built on Ubuntu bionic). I first installed Armbian Buster but had same problem, which is why I tried Armbian Bionic After some digging I came up with this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=472469 I'm out of ideas now,. I'm using OPiZero headless, no desktop and login via SSH. ArmbianMonitor logs uploaded at: https://bugzilla.redhat.com/show_bug.cgi?id=472469 Thanks in advance for any help with this.
  14. Just had a look at your log: ALSA No soundcard found. I don't think you've enabled Audio codecs. Run: sudo armbian-config Go To system, Hardware Enable Analog-Codec save and reboot.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines