-
Notifications
You must be signed in to change notification settings - Fork 54
Getting error trying to install built kernel module for Fedora 28 on Pine64 A64 #52
Comments
@HeatfanJohn Here is how I build mali r6p2. As soon as it is a out-of-tree module you need to specify your kernel source tree.
|
@HeatfanJohn like @sergey-suloev pointed above you need to export KDIR pointing to your kernel sources. Best regards. |
Ugh! I feel so stupid! I was running the The following appears to have worked for me and placed
Another question, what's the difference between the three different versions of the driver? Which one should I use? The latest (r8p1)? |
Latest should be the better. |
@giuliobenetti Is this patch the same patch to get the Mali node into the DTB for the A64 chip (sun50i-a64.dtsi)? |
@HeatfanJohn that patch is ok. |
Ah, by the way, can you try testing with frequency@576Mhz instead of 384? Thank you |
The latest is usually the best. Please note that the R8 Blob is only available in the framebuffer version.
For use with X11 or Wayland you have to compile the R6 driver because only R6 Blob are available.
Kai
…________________________________
From: John P Masseria. <notifications@github.com>
Sent: Tuesday, September 25, 2018 3:09 PM
To: mripard/sunxi-mali
Cc: Subscribed
Subject: Re: [mripard/sunxi-mali] Getting error trying to install built kernel module for Fedora 28 on Pine64 A64 (#52)
Ugh! I feel so stupid!
I was running the ./build.sh command using sudo therefore the build script didn't inherit my environment and the KDIR environment variable. I need to add the -E option to sudo to inherit my environment!
The following appears to have worked for me and placed mali.ko into the extra directory of /lib/modules/:
sudo -E ./build.sh -r r8p1 -i
Another question, what's the difference between the three different versions of the driver? Which one should I use? The latest (r8p1)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#52 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APbi3f_7otgLjAvUD2XsXDt08UB5wZQoks5uekczgaJpZM4W3khm>.
|
@hor63 Hi Kay, thank you for the information. I see now that the driver versions are from ARM - Open Source Mali Utgard GPU Kernel Drivers. Can I find out more about each of the available releases by looking at the driver source code provided by ARM? Or do you need the Mali DDK to fully understand the driver? |
Success!
However, I had a lot of trouble trying to get a
But writing this now shows me that I neglected to checkout the branch that corresponded to my Kernel version. This must explain why my first attempts to insert the Here's the patch for
I initially tried to say I guess before submitting this upstream we should define the A64 Mali literal. Question: What is the |
@HeatfanJohn here is my dts for mali
|
FYI @sergey-suloev, @giuliobenetti asked me to try 576MHz for the clock. I need to try to run a test now. |
@HeatfanJohn sure, but look at the compatible as your issue was related to it. |
@HeatfanJohn I point you the patch I've submitted for H3 as an example: Then you have to submit it to ML, check this out: |
Thank you for all your assistance so far. My goal is to get desktop running under Fedora 28 on a Pine A64+ SBC. I have successfully built and loaded the Mali r8p1 Kernel Module:
Should I worry that it says I have also copied the
I copied them to I was getting some SELINUX AVC denied errors that I addresses using However,
I haven't been able to figure out how to eliminate these remaining AVC DENIED SELINUX errors. I turned off SELINUX enforcement and Do I need to turn off
Here's the log with
|
You shouldn't use the fbdev variant but the Wayland's if you want to use
GBM.
Le lun. 8 oct. 2018 à 18:03, John P Masseria. <notifications@github.com> a
écrit :
… Thank you for all your assistance so far. My goal is to get desktop
running under Fedora 28 on a Pine A64+ SBC. I have successfully built and
loaded the Mali r8p1 Kernel Module:
[ 15.433268] Allwinner sunXi mali glue initialized
[ 15.439773] Mali:
[ 15.439783] Found Mali GPU Mali-400 MP r1p1
[ 15.466114] Mali:
[ 15.466139] 2+0 PP cores initialized
[ 15.488204] Mali:
[ 15.488214] Mali device driver loaded
Should I worry that it says r1p1?
I have also copied the r8p1 Mali OpenGL ES userspace libraries:
sudo cp -a mali-blobs/r8p1/arm64/fbdev/lib* /usr/lib64
I copied them to /usr/lib64 because this is a 64-bit ARM platform.
Initially copying them to /usr/lib had no effect. This copy overwrote
some links that were already present in lib64 directory.
I was getting some SELINUX AVC denied errors that I addresses using
audit2allow.
However, gdm keeps erroring on me saying:
Oct 05 15:25:06 mypine64 systemd[1]: Started Session c87 of user gdm.
Oct 05 15:25:06 mypine64 gdm-launch-environment][11771]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Oct 05 15:25:06 mypine64 audit[11771]: USER_START pid=11771 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="gdm" exe="/usr/libexec/gdm-session-worker" hostna>
Oct 05 15:25:06 mypine64 systemd[10990]: selinux: avc: denied { status } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfine>
Oct 05 15:25:06 mypine64 systemd[10990]: selinux: avc: denied { reload } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.>
Oct 05 15:25:06 mypine64 systemd[10990]: selinux: avc: denied { reload } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.>
Oct 05 15:25:06 mypine64 systemd[10990]: selinux: avc: denied { reload } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.>
Oct 05 15:25:06 mypine64 systemd[10990]: selinux: avc: denied { reload } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.>
Oct 05 15:25:06 mypine64 systemd[10990]: selinux: avc: denied { reload } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.>
Oct 05 15:25:06 mypine64 gnome-session[11778]: _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
Oct 05 15:25:07 mypine64 systemd[10990]: selinux: avc: denied { reload } for auid=n/a uid=42 gid=42 cmdline="/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.>
Oct 05 15:25:07 mypine64 gnome-shell[11786]: Failed to create backend: Could not find a primary drm kms device
Oct 05 15:25:07 mypine64 gnome-session[11778]: gnome-session-binary[11778]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct 05 15:25:07 mypine64 gnome-session-binary[11778]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct 05 15:25:07 mypine64 gnome-session-binary[11778]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 05 15:25:07 mypine64 gdm-launch-environment][11771]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Oct 05 15:25:07 mypine64 audit[11771]: USER_END pid=11771 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="gdm" exe="/usr/libexec/gdm-session-worker" hostnam>
Oct 05 15:25:07 mypine64 audit[11771]: CRED_DISP pid=11771 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=mypine64 addr=? terminal=/dev/tty1 res=success'
Oct 05 15:25:07 mypine64 gdm[11767]: GdmDisplay: display lasted 1.225508 seconds
Oct 05 15:25:07 mypine64 systemd-logind[457]: Removed session c87.
Oct 05 15:25:07 mypine64 gdm[11767]: Child process -11775 was already dead.
Oct 05 15:25:07 mypine64 gdm[11767]: Child process 11771 was already dead.
Oct 05 15:25:07 mypine64 gdm[11767]: Unable to kill session worker process
I haven't been able to figure out how to eliminate these remaining AVC
DENIED SELINUX errors. I turned off SELINUX enforcement and gdm still
wouldn't initialize.
Do I need to turn off drm and/or kms? I've seen a posting on that for an
NVIDIA GPU, but I don't know the equivalent setting for Mali. Again, sorry
for the newbie questions.
Oct 05 15:25:07 mypine64 gnome-shell[11786]: Failed to create backend: Could not find a primary drm kms device
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWenwldp4zaI00xO9I_s0ZSkBkCNwpCks5ui3dqgaJpZM4W3khm>
.
|
@mripard Thank you ... I'll switch to r6p2 which has wayland support. I'm also reading: https://events.static.linuxfound.org/sites/events/files/slides/brezillon-drm-kms.pdf To learn more about all of this terminology. |
@mripard I have switched to using the r6p2 kernel module and copied the wayland r6p2 libs into /usr/lib64/, but I'm still getting I don't see how to tell |
Do you have the KMS driver running? |
@mripard Thank you, can you point me to instructions on how to do that? Whoops, do you mean that I
Then is this what I need to do, from #45 (/dev/dri/card0 not created):
However, that issue said that he didn't need to get |
Hi @mripard Should I be trying to load sunxi-mali/r8p1/src/egl/x11/drm_module/mali_drm/ ?? If yes, I get the following when I try to make it:
Sorry for being a pest, but I really lost with all of this new terminology ... DRM / KMS. Am I correct that for the sun4i-drm driver to work I need to add the HDMI and backend items to my DTB for my A64 device? |
Chating with people on #Linux-sunxi I now understand that support for HDMI on the A64 chip is planned for Linux Kernel 4.20 which should now be actively being worked on since 4.19 just got released. Hopefully I'll be able to get a fairly stable release to test out soon ... |
To update this with my most recent results, I've been successfully getting display output on the HDMI output port of my PineA64+ device, getting GDM to start and also been able to run remote windows using the "X" windowing system using this patched 4.19 kernel from @anarsoul and this kernel config. The steps to reproduce this are basically to clone @anarsoul's repository, checkout branch sunxi64-4.19, copy @anasoul's config to .config, perform make oldconfig, make -j5 Image, make modules, sudo make modules_install, sudo make install, make dtbs, make dtbs_install, copy the dtb for the Pine64+ board to the /boot directory, reboot and select this new kernel in GRUB. |
I'm following the build instructions for the kernel module and the
./build.sh -r r8p1 -b
completed without error. However, when I go to install the kernel module using the command./build.sh -r r8p1 -i
I receive the following error:This is what I've done:
Looking at the Makefile I can see that I need to specify
MALI_PLATFORM
andTARGET_PLATFORM
. I not sure what to set for them. I initially didn't have anything set. I most recently tried:The text was updated successfully, but these errors were encountered: