• Content Count

  • Joined

  • Last visited


About guidol

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

5826 profile views
  1. via SSH? when I try this I do get there "Loading keyboard submodule ..." and then it will fall back to the personal menu - but it works when Iam directly connected via TTL-serial
  2. This image does boot for me and I can use it after generating locales. This does also work for the newer image Armbian_21.02.0-trunk_Orangepizero_buster_current_5.8.16 and Armbian_21.02.0-trunk_Orangepizero_buster_current_5.9.11 @Igor BTW: Is there a chance to change the following behavior? (why is armbian - like many webpages on the world- thinking I want a TR locales only because Iam in turkey? ) - I want to select a de_DE.UTF-8 or a en_US.UTF-8 - I want a german keyboard - and why we cant change the locale keyboard in armbian-config via a ssh-ses
  3. it seems to be only for a memory-remap function and not for the whole system
  4. looks like a problem with the DHCP-Server - so your sbc isnt getting an DHCP-IP but also get a timeout from the DHCP-transaction.
  5. seems to tbe a problem on devices with A64-CPU We got the "same" problem with Pine64 and the NanoPi A64 Maybe you could get a idea for a solution by checking the attached .dts for the NanoPi A64 in this message?:
  6. Tested SAM again and here some infos for compile and usage ( if you have a "late switching" amplifier on your SBC) : If you want to use direct output via sdl instead of generating .wav / using aplay the .wav ( libsdl2-2.0-0 libsdl2-dev doenst work with SAM ): ------------------------------------------------------------------------------------------ apt install libsdl1.2-dev libsdl1.2debian wget -O unzip cd SAM-master edit flags in Makefile if you want to use of Non-SDL (and save 30MB downlo
  7. @j___r on the page for the hc1 is written that it is a down-stripped version of the Odroid xu4, so you can check the download-directory of the xu4: but I think you cant upgrade this via armbian-config from 4.1.4 to Kernel 5.4.x
  8. Which serial ouput do you need/mean? From the boot-process while using eth0?
  9. Also got the problem with the official download-image Armbian_20.08.1_Orangepi-r1_buster_current_5.8.5.img eth0 orange/green led does lit , orange stays, green blink for some seconds, both goes off: like last year: [ 33.780717] vcc3v0: disabling [ 33.780731] vcc5v0: disabling [ 33.877210] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 34.901031] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [ 37.973216] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 38.996979] dwmac-sun8i 1c30000.etherne
  10. Yes- the A40i is only another pin-compatible temperature version of the R40. And the R40 (quadcore-A7-cpu) seems to be a NON-pin-compatible version of the "old" A20-CPU (duacore-A7-CPU) which was on the Banana Pi M1 (Pro)
  11. I tested my OPi R1 these days with kernel 5.10.0-rc2 and got problems with eth0 like on some versions in the past. You could see this issue in dmesg showing the eth0-device-link going down/up serveral times (eth0 ist the ethernet-port near the serial-ttl-port, the other enx-ethernet is connectec via usb) My enx-ethernet device is working here fine, but now my eth0 device has stopped working completly I use /etc/network/interfaces for setting the IP. armbian does set the IP but eth0 cant use the net ___ ____ _ ____ _ / _ \| _ \(_) | _ \/ | | |
  12. Check for R40-CPU, because A40i and A40pro are variants that differ in applicable temperatures range (industrial and military) against the R40: Allwinner R40 (sun8i) SoC features a Quad-Core Cortex-A7 ARM CPU, and a Mali400 MP2 GPU from ARM. It is a not-pin-compatible quad core sucessor of the A20. It's also known as the Allwinner T3 for In-Car Entertainment usage. Allwinner V40 (sun8i) SoC features a Quad-Core Cortex-A7 ARM CPU, and a Mali400 MP2 GPU from ARM. It is the automotive version of R40. and
  13. @5kft I will take the Samba-version which armbian does deliver me for Ubuntu Focal: 2:4.11.6+dfsg-0ubuntu1.6 and for debian buster: 2:4.9.5+dfsg-5+deb10u1 its interesting - for me - that the newer version 4.11.6 does crash with kernel 5.10.0-rc2 on ubuntu focal but the older 4.9.5 has no problems using kernel 5.10.0-rc2 under debain buster... Thanks for the informations/links - so I would stay with kernel 5.9.1 on ubuntu focal for now
  14. @Levent Erenler did you try to adress card 0 ( sun50ia64audio [sun50i-a64-audio] ) directly? Internet-Radio-stream: mpg123 -v -b 1024 -a hw:0,0 -@ or use a /etc/asound.conf: root@npi-a64-116( more /etc/asound.conf pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 }