-
Notifications
You must be signed in to change notification settings - Fork 49
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
rpi4 media-libs/mesa failed to enable V3D renderer #17
Comments
@yrzr - I've just released v1.5.0 of the If so, we should be able to triangulate the issue pretty quickly, given that you are using my overlay. Best, sakaki |
OK - good. So to start with then, are there any significant differences between the |
Here is the
|
You shouldn't need that I note you aren't specifying a |
As you adviced, I updated all the firmware, copy the kernel image and kernel modules, and modified
|
OK, last thing on this would be to comment out your overclocking options from If the problem is still there, then since we now have identical boot firmware and kernel, the only remaining thing really is mesa. Did you use my binary package for that, or build it yourself? |
I have checked that the overclocking options are not the cause. I build the mesa by my own
|
OK you have a number of different USE flags in there compared to me (like root@pi4 # PORTAGE_BINHOST="https://isshoni.org/pi64pie" emerge -av --oneshot --getbinpkgonly --binpkg-respect-use=n media-libs/mesa It'll hopefully prompt that you're going to be installing from binary (purple output on screen). If so, accept the install. If you try again once done, any luck? |
Hi, I tried to install the binary package, but it turned out to be a big mess to me.
Could this relate to the problem? |
Finally, problem fixed. I upgraded to mesa-19.2.0_rc1 (just add to portage today) with your patch, and add my user to the video group. Everything works fine now. Thanks for your help! |
Hi, I'm actually having the same issue. I installed my 64bit Gentoo following the guides in the wiki and with your image on a mounted USB stick as orientation (very nice work btw! would be awesome if you could publish a guide or whatsoever with what you did to make it work). Now everything seems to be working except for Firmware, kernel and bootstub are up to date (from the official repos),
Any ideas what else the issue could be? |
Hi @Jarodiv, It's likely to be either the kernel (some versions randomly don't work with V3D, even recent ones), the kernel config, or |
Ok, back from testing (thanks for the very quick response). The first test, replacing the kernel, didn't change a thing (after all, my kernel is using almost the same config as yours does). The second test, replacing my mesa with your binary, worked, so I revisited everything I did and noticed, that I had a typo in my mesa ebuild that did exactly prevent it from enabling V3D. Fixing the ebuild and recompiling mesa did solve the issue. Thanks a lot! Would it be ok for you if I contact you via mail with a Bluetooth issue I discovered in the meantime and haven't been able to pin down so far? I'm going to try a little more but if I don't succeed some help would be welcome :) |
Glad you got it fixed! Yes, feel free to drop me an email. |
I have already used the ebuild of media-libs/mesa from this overlay and enabled video_cards_vc4.
Meanwhile, I have apply this patch in the kernel. However,
glxgears -info
still showsllvmpipe
instead ofV3D
. Would you please help to identify the problem?PS:
eselect opengl list
shows onlyxorg-x11
The text was updated successfully, but these errors were encountered: