-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arm64: dts: rockchip: Add Orange Pi 3B v2.1 #234
Conversation
It's strange that workflow build did not produce |
Interesting. Could it be because dtb filename contains 2 periods? I see |
Issue found: Armbian build's |
As mentioned on the downstream bug.... maybe don't use DTs with periods? I don't think any mainline (or vendor, before that DT) had dots in it. |
Mainline u-boot requires these specific DTB filenames in order to match the DTB to the board version.
They exist though.
|
Big Thanks to @dust-7 @amazingfate for Per my experience if the output of
If this is the output you get 3.5mm do not work
|
Gi-0n I cannot create v2.1 v1.1 |
I was also not able to get audio via 3.5mm jack to work. I have not been able to fix it so far. |
@dust-7 in this mainline release |
@amazingfate Am still not able to generate these x2
But still no dtb files |
|
Commits squashed. |
Workflow of this pr doesn't have this issue. Make sure you have the latest code of armbian. |
@amazingfate Generally speaking lets suppose I have a new
So I placed the new |
You have to put the dts file at dt dir. |
@amazingfate my 0000.patching_config.yaml
then file locations
contents of Makefile in overlay folder
Per the progress overlay files are added to correct location but |
Compiled from sources, vendor kernel, v2.1.dtb generated, OK, but system hangs on boot anyway. |
You may try my commit to update uboot: armbian/build@7612219 |
@lopirata for vendor kernel for v2.1 board, you'll have to manually update the board config file for now. See step 1 of Testing steps taken in the first comment. For edge kernel, you'll have to wait for kernel v6.11 to drop. @amazingfate v2.1 board works with or without the uboot patch from Kwiboo. |
I'm going to use mainline uboot, not Kwiboo's branch. |
I generated Note to @dust-7 I have to manually add After this my BT started working... |
I just did a test and it works for me:
@defencedog I suspect you did not update your u-boot. Suggest you build and flash a complete image. |
@dust-7 did that, booted, but no ethernet. So I did what @defencedog done editing fdt-file parameter in armbianEnv.txt For all there, I have two boards, one just to test stuff. If I can help with testing, just send me what to do. PS: Thank you ALL, since end of june trying to make armbian work in this board and FINALLY! EDIT: MAC address changes every reboot. |
@lopirata I have an |
Thank You! For the main board I need Armbian in Debian flavour to install OMV and Jellyfin. Will test HW acceleration too. |
@lopirata I believe for such stuff DietPi is OK ... Also I am waiting for ethernet speeds |
I know Armbian or Debian OMV solution is better - no proprietary script bloatware, its pure, no additional security issues. As soon as you install OMV, "minimalism" and "optimisations" are gone as OMV is pretty bulky software bundle. BTW. Dietpi main self promo article is just a bundle of lies to support their believes. I see they expanded their illusions with another fat lie: "We maintain own kernel sources", "and otherwise rely on and benefit from kernel development done by other projects". And they don't name other projects and they don't show how they maintain kernel sources ... |
@defencedog I've tried to install OMV and the things gone wrong, so, maybe tomorrow I'll do everything again, use Iperf and show some stuff here. @igorpecovnik I'm usinge Armbian since 2017 on an Orange Pi Plus 2E, and I remember you in the forum teaching how to compile Armbian with OMV. Love the way OMV is easy to configure in Armbian and the interface itself, so easy to me to share files and media with my family. |
@lopirata how are your ethernet results? |
root@orangepi3b:~# iperf3 -c 192.168.88.101 [ ID] Interval Transfer Bitrate Retr OMV still kill ethernet and MAC address keeps changing every reboot. Still trying to realize how to apply this to opi3b. |
As I said early, the random MAC is a SPI issue as I'm booting from NVMe. The solution is very simple, but not so fast: 1-Flash a microSD card with the IMG, edit armbianEnv.txt properly to boot your specific board (in my case, v2.1); After that, reinstalled OMV and everything is fine. Next steps: |
@lopirata kindly do me a favour. Please run |
|
Changes
[drm:vop2_plane_atomic_check] *ERROR* Unsupported linear format at Cluster0-win0
). This fixes Wayland Cursor Invisible [drm:vop2_plane_atomic_check] *ERROR* #229.Testing steps taken
Update board config file to the following:
Expand
Build image with following:
./compile.sh build BOARD=orangepi3b BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=jammy
Features tested working: