View previous topic :: View next topic |
Author |
Message |
sbbg n00b
Joined: 02 Feb 2013 Posts: 23
|
Posted: Thu Feb 13, 2020 9:01 am Post subject: ROC-rk3328-PC X11 acceleration. |
|
|
Hello, Gentoo gurus,
I'm running Gentoo at http://en.t-firefly.com/product/rocrk3328pc.html?theme=pc
But after successfully emerge x11, some problem arises.
Does anyone tweak the >5.2 kernel to fit into this board before?
Especially with panfrost driver enabled?
If not, I'm stucked with no acceleration of X11, because I built X11 with VIDEO_CARDS="panfrost"
If I want an accelerated X11 to run Kodi. Do you have any better idea?
Thank you.
=================================================================
What I learned so far:
1. There is no mainstream support in Linux kernel. While there are dts of rock64, evb, rk3328-roc-cc. I don't know which rk3328 dts can work for this board.
And I have hard time testing the image
2. I cannot find defconfig in upstream u-boot for this board.
With above problems, even I generated a compiled kernel and boot image. I cannot boot and test.
Please let me know any suggestion if you have more experience with this board. |
|
Back to top |
|
|
guitou Guru
Joined: 02 Oct 2003 Posts: 534 Location: France
|
Posted: Thu Feb 13, 2020 11:52 am Post subject: |
|
|
Hello.
Looking at specs, you got ARM Mali-450 MP2 GPU.
And searching for drivers, it looks like you should use lima driver, not panfrost.
++
Gi) |
|
Back to top |
|
|
sbbg n00b
Joined: 02 Feb 2013 Posts: 23
|
Posted: Fri Feb 14, 2020 6:57 am Post subject: |
|
|
guitou wrote: | Hello.
Looking at specs, you got ARM Mali-450 MP2 GPU.
And searching for drivers, it looks like you should use lima driver, not panfrost.
++
Gi) |
Thank you first.
okay... but does that require kernel tuning? Or can I use their default 4.4 kernel with current mesa 19?
===============================================
Their configuration selected following in DRM:
Code: | <*> Mali-300/400/450 support │ │
│ │ [*] Enable Mali-450 support │ │
│ │ [ ] Enable Mali-470 support │ │
│ │ [ ] Enable debug in Mali driver │ │
│ │ [ ] Enable Mali profiling │ │
│ │ [ ] Enable UMP support │ │
│ │ [*] Map dma-buf attachments on attach │ │
│ │ [*] Support for shared interrupts │ │
│ │ [ ] Power up Mali PMU domains in parallel │ │
│ │ [*] Using device tree to initialize module │ │
│ │ [*] Using devfreq to tuning frequency │ │
│ │ [ ] Make Mali driver very quiet |
[Moderator edit: added [code] tags to preserve output layout. -Hu] |
|
Back to top |
|
|
sbbg n00b
Joined: 02 Feb 2013 Posts: 23
|
Posted: Fri Feb 14, 2020 8:50 am Post subject: |
|
|
After I enable VIDEO_CARDS="lima" and recompile mesa.
I did find a /usr/lib64/dri/lima_dri.so in rootfs.
But I wonder how to enable this?
I tried glmark2-es2 and glmark2 to test it.
They all display:
GL_VENDOR: VMWare, Inc.
GL_RENDERER: llvmpipe
And what's more, I can't find another option in result of "eselect opengl list"
It only display xorg-x11 as only implementation.
The only thing mentioned failed in Xorg.0.log is:
"modeset(0): glamor initlization failed."
How can I enable LIMA properly? Thank you. |
|
Back to top |
|
|
erm67 l33t
Joined: 01 Nov 2005 Posts: 653 Location: EU
|
Posted: Fri Feb 14, 2020 3:56 pm Post subject: |
|
|
It is not so easy, but first question, are you satisfied with their 4.4 kernel or you want mainline?
To fully enable opengl you need a kernel driver and a userspace library, if you use their kernel with the proprietary kernel drivers you will need to use their userspace library, if instead you are going to use mainline you will need to enable kernel config option DRM_LIMA that will work fine with mesa. I am a bit busy to search the links for the mesa part ATM, maybe during the weekend
To use mainline you only need mainline, this of course involves finding a functional dtb ...
Lima's kernel driver has been merged, and will be in Linux kernel v5.2, the mesa part has been merged already.
link to the proprietary off-tree drivers:
https://developer.arm.com/tools-and-software/graphics-and-gaming/mali-drivers/utgard-kernel
this drivers requires a binary blob that probably is already in the ubuntu image you downloaded from vendor and will probably let you use the dtb you already have.
Another option to use the old dtb is to download the off-tree utgard (lima) off-tree driver for kernel 4.4 and use it together with a recent mesa. _________________ Ok boomer
True ignorance is not the absence of knowledge, but the refusal to acquire it.
Ab esse ad posse valet, a posse ad esse non valet consequentia
My fediverse account: @erm67@erm67.dynu.net |
|
Back to top |
|
|
erm67 l33t
Joined: 01 Nov 2005 Posts: 653 Location: EU
|
Posted: Sat Feb 15, 2020 9:04 am Post subject: |
|
|
https://patchwork.kernel.org/patch/10147745/
It looks like a dtb has been added to mainline for your board in 2018 _________________ Ok boomer
True ignorance is not the absence of knowledge, but the refusal to acquire it.
Ab esse ad posse valet, a posse ad esse non valet consequentia
My fediverse account: @erm67@erm67.dynu.net |
|
Back to top |
|
|
sbbg n00b
Joined: 02 Feb 2013 Posts: 23
|
Posted: Mon Feb 17, 2020 2:05 am Post subject: |
|
|
erm67 wrote: | https://patchwork.kernel.org/patch/10147745/
It looks like a dtb has been added to mainline for your board in 2018 |
Kind sir, thank you for spending time doing some searches for me.
But I'm afraid that I need some extra experience sharing from you.
The dts is for ROC-RK3328-"CC", while I own a ROC-RK3328- "PC" .
Here arises a question for me:
"How can I tell the dts is compatible or not?"
I certainly wish I can adopt a newer kernel to eliminate binary blob requirement.
So I actually configured a 5.4 kernel with lima support for this board along with this rk3328-roc-cc.dts within boot.img.
But somehow it just does not boot.
Does that tell the dts is not compatible? |
|
Back to top |
|
|
erm67 l33t
Joined: 01 Nov 2005 Posts: 653 Location: EU
|
Posted: Tue Feb 18, 2020 7:57 am Post subject: |
|
|
sbbg wrote: |
But somehow it just does not boot.
Does that tell the dts is not compatible? |
hard to tell without a serial ...... there might be a million of other reasons .... faulty sdcard, old initramfs, missing modules
http://wiki.t-firefly.com/en/ROC-RK3399-PC/debug.html
get a 2$ srial converter on ebay
The two boards are really similar probably the dtb should boot at least in part. Despite what a lot of people thinks it is not automatic that if a board doesn't boot the dtb is at fault. _________________ Ok boomer
True ignorance is not the absence of knowledge, but the refusal to acquire it.
Ab esse ad posse valet, a posse ad esse non valet consequentia
My fediverse account: @erm67@erm67.dynu.net |
|
Back to top |
|
|
erm67 l33t
Joined: 01 Nov 2005 Posts: 653 Location: EU
|
Posted: Tue Feb 18, 2020 7:24 pm Post subject: |
|
|
I should not say that here but, if you can, try the kernel+initrd from fedora32, they are really supporting tons of aarch64 SBC in their kernel and is good (even if obviously bloated to support all the board). Their ISO boots only on the raspi ATM so you will have to grab kernel+initrd+kernel modures from the rootfs and create your own boot media. Try all the rockchip dtbs, maybe one will work. _________________ Ok boomer
True ignorance is not the absence of knowledge, but the refusal to acquire it.
Ab esse ad posse valet, a posse ad esse non valet consequentia
My fediverse account: @erm67@erm67.dynu.net |
|
Back to top |
|
|
|