Slackware - ARM This forum is for the discussion of Slackware ARM. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
08-08-2020, 01:16 AM
|
#91
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
try using fbturbo driver
|
|
|
08-08-2020, 11:34 AM
|
#92
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
i tested on H3 (no difference there too mali 400) the problem is the same.
when using modesettings, the interface slows down more than with fbturbo over also check armsoc.
|
|
|
08-08-2020, 11:39 AM
|
#93
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Original Poster
Rep:
|
Quote:
Originally Posted by sndwvs
try using fbturbo driver
|
Okay, I will try that next. Here is what I just found out after a few days of testing:
Your image with the legacy kernel does not boot past u-boot for some reason. Just black screen. I will try again to see if there is anything happening past u-boot on disk.
So, I built a fresh image with the next-kernel. This one boots fine, and when I make it to Xfce, I am getting a new error in Xorg.0.log (the previous error is now gone):
Code:
[ 127.083] (II) AIGLX: Screen 0 is not DRI2 capable
[ 127.083] (EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/swrast_dri.so failed (libLLVMCoroutines.so.10: cannot open shared object file: No such file or directory)
[ 127.083] (EE) AIGLX error: unable to load driver swrast
[ 127.083] (EE) GLX: could not load software renderer
[ 127.083] (II) GLX: no usable GL providers found for screen 0
The end result is the same, sluggish X desktop environment. I will try loading the fbturbo driver next to see if that makes a difference.
|
|
|
08-08-2020, 11:58 AM
|
#94
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
you need to install the d/llvm package.
Quote:
Your image with the legacy kernel does not boot past u-boot for some reason. Just black screen. I will try again to see if there is anything happening past u-boot on disk.
|
yes this was the case and for the A20 I changed the configuration for it.
|
|
|
08-08-2020, 12:42 PM
|
#95
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Original Poster
Rep:
|
Quote:
Originally Posted by sndwvs
you need to install the d/llvm package.
|
Ah, good call. That is what I get for not doing a full install!
I installed d/llvm and that error went away, but the previous error is now back again:
Code:
[ 131.080] (II) Initializing extension GLX
[ 131.080] (EE) AIGLX error: sun4i-drm does not export required DRI extension
[ 131.412] (II) IGLX: Loaded and initialized swrast
[ 131.413] (II) GLX: Initialized DRISWRAST GL provider for screen 0
Ah, I see you added the new drivers. I will grab those now, appreciated....
Last edited by shelldweller; 08-08-2020 at 12:45 PM.
|
|
|
08-08-2020, 12:56 PM
|
#96
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
so far fbturbo is better but still very slow
|
|
|
08-08-2020, 06:38 PM
|
#97
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
it seems so far this is the only way to get acceleration
|
|
|
08-08-2020, 07:11 PM
|
#98
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
that's a little better
/etc/X11/xorg.conf.d/20-lima.conf
Code:
Section "ServerFlags"
Option "AutoAddGPU" "off"
Option "Debug" "dmabuf_capable"
EndSection
Section "OutputClass"
Identifier "Lima"
MatchDriver "sun4i-drm"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
here's another tweak
Code:
echo -e '#!/bin/sh\n\nexport vblank_mode=0\n > /etc/profile.d/vblank.sh
echo -e '#!/bin/csh\n\nsetenv vblank_mode "0"\n > /etc/profile.d/vblank.csh
chmod +x /etc/profile.d/vblank.{csh,sh}
after that restart Xorg
glxgears before changing ~56fps after ~200-400fps
Last edited by sndwvs; 08-08-2020 at 07:52 PM.
|
|
|
08-10-2020, 02:16 PM
|
#99
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Original Poster
Rep:
|
Hmmm, well... I have run out of things to try.
The next kernel with the tweaks you provided works somewhat, but the sluggish desktop is still an issue. Compared to my working image from a few months ago, it is a serious degradation of performance. Can we just turn off the 3D acceleration? I am used to not having it, and would not miss it if turned off. Besides, it is not fully developed yet for A64, is it? I am still getting the sun4i-drm error, and I have no clue how to try the fbturbo driver... how are you installing it? I see it in the git tree, is it an extras package or something? I know how to activate a driver in /etc/X11/xorg.conf.d/, but where do I get the driver from? Build from source, or is there a package somewhere?
I still cannot build the legacy kernel image. The build.log ends here, with no error messages at all:
Code:
AR drivers/video/built-in.a
AR drivers/built-in.a
The solution here is to use "make bzImage" instead of "make kernel". Would that apply here?
If I try switching the kernel version, the patches no longer apply correctly. I am guessing that the patches are version-specific, yeah? Hmmm...
Okay, back to *real* work... more later. thanks.
|
|
|
08-10-2020, 02:31 PM
|
#100
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
driver xf86-video-fbturbo-r199.f9a6ed7-aarch64-1mara.txz in /etc/X11/xorg.conf.d/ configuration.
Quote:
Can we just turn off the 3D acceleration?
|
it is possible, but as for me it gets worse.
Quote:
The solution here is to use "make bzImage" instead of "make kernel". Would that apply here?
|
see errors much higher or install /config/environment/00-environment.conf CTHREADS=" -j1 "
|
|
|
08-10-2020, 02:50 PM
|
#101
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Original Poster
Rep:
|
Quote:
Originally Posted by sndwvs
|
Ah, there it is... maybe I just missed it. Thanks.
Quote:
Originally Posted by sndwvs
see errors much higher or install /config/environment/00-environment.conf CTHREADS=" -j1 "
|
Ah HA! I was looking for this. THANKS! This helps. Okay, more later...
|
|
|
08-11-2020, 02:53 PM
|
#102
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Original Poster
Rep:
|
Well, I got fbturbo installed (thanks again), but my first attempt at launching Xfce was a disaster.
Black screen, could not switch to another terminal, had to do a hard reset. Xorg.0.log spit out a bunch of scary stuff about FBTURBO when I looked at it from another OS:
Code:
[ 154.219] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 154.268] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 154.268] (II) no primary bus or device found
[ 154.268] falling back to /sys/devices/platform/display-engine/drm/card1
[ 154.268] (II) LoadModule: "glx"
[ 154.270] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 155.008] (II) Module glx: vendor="X.Org Foundation"
[ 155.008] compiled for 1.20.8, module version = 1.0.0
[ 155.008] ABI class: X.Org Server Extension, version 10.0
[ 155.011] (II) LoadModule: "fbturbo"
[ 155.021] (II) Loading /usr/lib64/xorg/modules/drivers/fbturbo_drv.so
[ 155.025] (II) Module fbturbo: vendor="X.Org Foundation"
[ 155.026] compiled for 1.20.8, module version = 0.5.1
[ 155.026] Module class: X.Org Video Driver
[ 155.026] ABI class: X.Org Video Driver, version 24.1
[ 155.026] (II) FBTURBO: driver for framebuffer: fbturbo
[ 155.026] (--) using VT number 7
[ 155.112] (WW) Falling back to old probe method for fbturbo
[ 155.112] (II) Loading sub module "fbdevhw"
[ 155.113] (II) LoadModule: "fbdevhw"
[ 155.114] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 155.117] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 155.117] compiled for 1.20.8, module version = 0.0.2
[ 155.117] ABI class: X.Org Video Driver, version 24.1
[ 155.118] (II) FBTURBO(0): using /dev/fb0
[ 155.118] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 155.118] (II) FBTURBO(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 155.118] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[ 155.118] (==) FBTURBO(0): RGB weight 888
[ 155.118] (==) FBTURBO(0): Default visual is TrueColor
[ 155.118] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ 155.118] (II) FBTURBO(0): hardware: sun4i-drmdrmfb (video memory: 8100kB)
[ 155.118] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 155.118] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[ 155.118] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[ 155.118] (II) FBTURBO(0): processor: Unknown
[ 155.118] (II) FBTURBO(0): checking modes against framebuffer device...
[ 155.118] (II) FBTURBO(0): checking modes against monitor...
[ 155.118] (II) FBTURBO(0): Virtual size is 1920x1080 (pitch 1920)
[ 155.118] (**) FBTURBO(0): Built-in mode "current"
[ 155.118] (==) FBTURBO(0): DPI set to (96, 96)
[ 155.118] (II) Loading sub module "fb"
[ 155.118] (II) LoadModule: "fb"
[ 155.119] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 155.173] (II) Module fb: vendor="X.Org Foundation"
[ 155.173] compiled for 1.20.8, module version = 1.0.0
[ 155.173] ABI class: X.Org ANSI C Emulation, version 0.4
[ 155.173] (**) FBTURBO(0): using shadow framebuffer
[ 155.173] (II) Loading sub module "shadow"
[ 155.174] (II) LoadModule: "shadow"
[ 155.185] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[ 155.188] (II) Module shadow: vendor="X.Org Foundation"
[ 155.189] compiled for 1.20.8, module version = 1.1.0
[ 155.189] ABI class: X.Org ANSI C Emulation, version 0.4
[ 157.355] (II) FBTURBO(0): can't load 'g2d_23' kernel module
[ 157.355] (II) FBTURBO(0): failed to enable the use of sunxi display controller
[ 157.356] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[ 157.360] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
[ 157.370] (==) FBTURBO(0): Backing store enabled
[ 157.371] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[... this line repeats about 240 times ...]
[ 157.377] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[ 157.377] (==) FBTURBO(0): DPMS enabled
[ 157.377] (II) FBTURBO(0): failed to enable hardware cursor
[ 157.377] (II) FBTURBO(0): no 3D acceleration because the driver has been compiled without libUMP
[ 157.377] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log
[ 157.427] (II) Initializing extension Generic Event Extension
[ 157.428] (II) Initializing extension SHAPE
So, it seems to have tried to load the driver, but never made it to the desktop. Any idea what might have gone wrong?
|
|
|
08-11-2020, 03:00 PM
|
#103
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
Quote:
Originally Posted by shelldweller
So, it seems to have tried to load the driver, but never made it to the desktop. Any idea what might have gone wrong?
|
I only tried it on H3 and it worked.
see section == Troubleshooting ==
|
|
|
08-12-2020, 01:13 PM
|
#104
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Original Poster
Rep:
|
quick update, then I have to get back to work...
I am now able to build a legacy kernel 5.4.x., thanks for that. However, the same slow Xorg issue persists. So, does this rule out the kernel, since my image from June with the 5.5.x kernel does not have the same problem? If so, then this would be related to ATF or maybe u-boot? Just curious...
I have tried a few different things to get Lima/fbturbo working, and most of them result in a black screen of death. Looking around the web, it seems like a few have gotten this to work on A64, but most are having similar issues to this. I have not found anything conclusive or partially working yet, but I will continue.
fbturbo is not specifically for A64, but some have reported success. I will keep investigating when I have the time.
thanks as always.
|
|
|
08-12-2020, 01:37 PM
|
#105
|
Senior Member
Registered: Aug 2014
Posts: 2,065
Rep:
|
Quote:
Originally Posted by shelldweller
I am now able to build a legacy kernel 5.4.x., thanks for that. However, the same slow Xorg issue persists. So, does this rule out the kernel, since my image from June with the 5.5.x kernel does not have the same problem? If so, then this would be related to ATF or maybe u-boot? Just curious...
|
it is only a kernel and user environment driver.
|
|
|
All times are GMT -5. The time now is 05:19 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|