• Content Count

  • Joined

  • Last visited

About OPUser

  • Rank

Recent Profile Visitors

868 profile views
  1. So, was it a bad idea to decompile "sun7i-a20-orangepi.dtb" into "sun7i-a20-orangepi.dts", then edit and compile back to "sun7i-a20-orangepi.dtb"? Would it be more correct to edit/patch the kernel sources instead?
  2. Ok, thank you. My understanding was there are more changes required than just phy-mode = "rgmii"; -> phy-mode = "rgmii-id"; (for HDMI and USB)
  3. I tried to merge with bananapi dts, but something still wrong. Could you please share you new sun7i-a20-orangepi.dts file?
  4. Have you seen problems with HDMI and USB in 5.10.y kernel?
  5. Is it more correct to build Armbian from the official branch v21.02 (if talking about the self build). Does a particular kernel and u-boot snapshots are linked to the official releases? I tried to merge dtb of BananaPi and OrangePi, enabled some devices, but, unfortunately, I didn't get the desired result yet - not enough knowledge on this subject. Perhaps, v5.4 will be a good choice for now
  6. I enabled OrangePi config and built two focal desktop images. Image with kernel v5.10 has the same problem with dtb config (no USB, no HDMI) while image with v5.4 works good. WiFi is connected to USB so that explains issue with WiFi on kernel v5.10 The only confusing thing is the mismatch between web site and Armbian console Got it! However, both BananaPi and OrangePi have few changes per year. But, perhaps, something was broken between v5.4 and later version like v5.10 Will try to check this, thank you. But it is not worki
  7. I have compared dts files and found that some devices were disabled I switched them to "okay" but it didn't help to enable HDMI monitor output with OrangePi dtb file zador.blood.stained, I saw you had a great contribution to Armbian on such subjects, can you comment please what could be wrong with stock OrangePi dtb file?
  8. Hello After a couple of years, I took my "ancient" OrangePi board and found it working well with Ubuntu 18.04 (kernel 3.14.113). And I even did distr update to 20.04. So HW is ok. I found that Armibian support status of OrangiPi is changed to "Supported" and decided to try the latest image with modern kernel "Armbian_21.02.1_Bananapi_focal_current_5.10.12_desktop.img.xz" (shared image between OrangePi and BananaPi). XFCE desktop was loaded but USB was not working. And that was the known mismatch between OrangePi and BananaPi HW conguration. So I updated "/boot/armbianEnv.
  9. I compiled jessie desktop image without use of FORCE_CHECKOUT but u-boot can't load kernel - it stops at "Starting Kernel..." message. kernel only compilation gave the same result. I decided to check if Ubuntu image from site works - it works but average load is too high, over 1.2. armbianmonitor -m shows 70% CPU load. But htop shows /sbin/init at 6% as a heaviest task. How can I check the rootcause?
  10. Hello I have built Armbian new desktop image and SATA PMP patched kernel debs for OrangePi from the master branch on Ubuntu Xenial VBox host ./compile.sh PROGRESS_DISPLAY=plain FORCE_CHECKOUT="no" CREATE_PATCHES=yes\ BRANCH=default BOARD=orangepi KERNEL_ONLY=no RELEASE=jessie\ USE_GITHUB_UBOOT_MIRROR="yes" BUILD_DESKTOP=yes EXTERNAL_NEW=prebuilt and got this messages during kernel compilation HEAD detached at FETCH_HEAD nothing to commit, working directory clean [ warn ] Make your changes in this directory: [ /root/my_orangepi_kernel/sources/linux
  11. RagnerBG mpv has sound sync issue on my jessie, I will try to comple mplayer myself. Thanks Is it better to use mplayer2? I have consern that mplayer2 have incomatibility with the latest libavcodec. And that's the root cause. Previous libavcodec versions (e.g. libavcodec53, libavcodec54) worked fine with mplayer2 BTW. This says that udev rules for /dev/ion is only for H3; while A10/A20, A13, requires udev rules for /dev/g2d (it's missing in Armbian now)
  12. mplayer was working with HW acceleration on wheezy and trusty, but today I loaded jessie image and I got that: Cannot find codec 'h264_vdpau' in libavcodec... Video decoder init failed for codecs.conf entry "ffh264vdpau". I'm puzzled, what's wrong with it? Outdated libs in jessie?
  13. tkaiser, Thank you for pointing the direction. Hello Igor. BTW. Is it possible to have different sources for kernel update for those who is using custom kernel? E.g. My system with SATA multiplier will not boot if I will miss kernel update, so I had to disable source in armbian.list. Proposing something like: deb http://apt.armbian.com/all jessie main deb http://apt.armbian.com/sw_only jessie main deb http://apt.armbian.com/kernel jessie main Thank you.
  14. Hello I'm investigating update from wheezy to trusty on my OrangePI (A20) based home media server. I'm using custom kernel 3.4.110 with SATA multiplier support. System is on HDD. I had few remarks and issues (part of them were solved but some are not): - Video acceleration was not working out of the box on trusty desktop image but it was solved it by installing "Desktop-extras for Jessie-desktop (sunxi)" - it looks it could be added as default for trusty. But mvp package can't be installed due to depedencies to libs which I did not found in ubuntu reps?! - compositing if OFF in xfce but
  15. @Igor Thank you. I have recently upgraded my Debian wheezy v3.5 to the latest Debian wheezy desktop v4.5 following lib scripts. And I have also manage to complile legacy kernel with PMP and all external tools. I have notice the following - apt-get install didn't install all required packages (PAKETKI) from main.sh and from deboostrap.sh and desktop.sh so I had to install them by myself - BOOTLOADER="http://git.denx.de/u-boot.git" works faster then BOOTLOADER="git://git.denx.de/u-boot.git" in Russia. I had no big delay using http. Previously I was pushed by timeout. My Agestar DAS is