Search the Community
Showing results for 'panfrost'.
-
Hello, i am new here, an experienced back-end developer from Hungary, and my hobby is mostly doing some IOT stuff in my free-time. I'm big fun of the Armbian project a long time and checking its progress time to time cos its seems perfect for IOT usage and the NanoPi R3S was specially chosen by me for my ongoing project because of the Platinum support of the product as it seemed to be perfect fit with good enough video support to make IOT server with remote app for admin functions. Sadly as it seems the hardware acceleration is not supported i guess because there is no HDMI port on the product but with Panfrost + VirtualGL it could be a capable remote desktop solution and i have checked that on "BigTreeTech CB2" its already there so that could be added for that as well. For me it would be enough if i get some help to add that to the build script for only me for now! But maybe there are other people who could have good use of some kind of remote desktop solution for an app or a whole desktop. I almost got it working with the official driver but it is not possible sadly without forking VirtualGL to make it compatible with the gl4es faker, and also that limits to OpenGL 2.X apps only so with Panfrost (3.1) could much better and it won't need the faker either. Update: I have the non LTS version cos that's the only one i was able to buy but i just checked the LTS version which is the Platinum support for and it has HDMI so it could be useful even more.
-
May I know how do you enable Panrost support Ubuntu 24.04 on Khadas Edge2? By Khadas SDK, I have built image which failed with followings: 1. Enabled Panfrost in defconfig. 2. Add kisak-mesa ppa, apt update and upgrade. 3. Replace mali_csffw.bin by Armbian mali firmware. After these, the gnome-settings shows the GPU is software vendoring. Hope to get your help~ Thanks!
-
I have been trying to research this and have come up a bit blank. I am trying to figure out if I need to do anything special to enable panfrost. I have built a jammy and bookworm image using the stable kernel. Both boot fine, but are both using llvmpipe. It does look like its trying to use panfrost. Inside of dmesg: [ 20.098662] panfrost fde60000.gpu: clock rate = 594000000 [ 20.098685] panfrost fde60000.gpu: bus_clock rate = 500000000 [ 20.098820] panfrost fde60000.gpu: Looking up mali-supply from device tree [ 20.099041] panfrost fde60000.gpu: _of_add_opp_table_v2: no supported OPPs [ 20.099287] panfrost fde60000.gpu: devfreq init failed -2 [ 20.099301] panfrost fde60000.gpu: Fatal error during GPU init [ 20.099458] panfrost: probe of fde60000.gpu failed with error -2 I tried building with a newer kernel, but was having issues on boot. I haven't dug into that further yet. Anyone have any thoughts or advise? Thanks
-
Version 20230401 with kernel 6.2 (pancsf-midstream). With HDMI USB support. https://disk.yandex.ru/d/W8pOOhizVjq91A To enable HW acceleration, install the mesa package with the forced overwrite option or an archive to enable acceleration for wayland. To enable wayland acceleration, you need to replace the files in the /usr/lib/aarch64-linux-gnu directory with the contents of the archive (with file replacement). After that, acceleration will work with wayland. X11 and wayland acceleration works the same way on Debian Sid (the images are the same as Ubuntu). After starting the system and initial configuration, replace the files from the archive in the same way and acceleration will work. The results of running in Debian Sid Gnome for x11 and wayland. dpkg -i --force-overwrite mesa_23.0.0-dev-2_arm64.deb After installation and reboot, HW acceleration will work in x11 and wayland. Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs. With x11, the system works more stably, but the test results are lower than in gnome+wayland. deb\archive https://disk.yandex.ru/d/h8c-Y2FfAvx76g
-
Hello all, I noticed that since recently (TM) I got loads of spam from panfrost in my dmesg output: I understand that this has something todo with graphics. The only "graphic" thing I'm doing is running standard Klipper-Screen through HDMI and this seems to be working as always... It definately wasn't there like half a year ago. can I get rid of it? Is it something to worry about? my armbian is running on a Banana-Pi CM4 module of of the eMMC. It's a rather standard installation with Klipper installed via KIAUH. sincerely - cad435
-
Description This is a follow-up of: https://github.com/armbian/build/pull/5901 It resolves a conflict between the SimpleDRM and Panfrost graphic drivers by blacklisting simpledrm. Other boards of the same family are assumed to have the same issue and will probably benefit from this fix as well. However, the fix has been actually tested only on the Khadas VIM3. I cannot test this change for other boards, as I do not own them. The Banana Pi M5 was also included for this change, because the driver conflict has also been mentioned in another Jira ticket. Note that this board is of the meson-sm1 family! How Has This Been Tested? Perhaps someone else has these boards available for testing? Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Some high-resolution monitors (QHD/4K) will not output the desktop, and will enter sleep mode, directly after booting up an Armbian 23.8.1 desktop image and completing the initial setup questions. When such a monitor is attached, the kernel will auto-detect the SimpleDRM graphics driver, which is then prioritized over the Panfrost graphics driver. However, SimpleDRM outputs to a virtual output, while Panfrost outputs to the actual HDMI port. This causes the monitor to not receive any data. By blacklisting the simpledrm kernel module, Panfrost will take care of accelerated graphics (for any monitor) by default. Advanced users can still access simpledrm if required. Jira reference number [AR-1908] How Has This Been Tested? An Armbian image with a Cinnamon desktop has been build using the default options. That image has been written to a SD-card and tested on both a QHD monitor (that had the initial problem) and an older Full HD monitor (that worked fine before as well). In both test cases, the simpledrm kernel module was not loaded. The desktop was visible on the HDMI output both on initial boot and after subsequent reboots. Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article
-
Collabora continues to relentlessly shift the needle to make high-quality open-source software not just an aspiration, but an expectation. We're pleased to announce an extension of our collaboration with Arm, providing more surety and capability for Panfrost. View the full article
-
I have been running Armbian on a Pinebook Pro without issues. I use the stable distribution, but after an update about a week ago (I think) the Panfrost driver has stopped working. When logging into the desktop environment (Cinnamon) the symptom is a black screen with a cursor visible but nothing else. Checking the logs I see a bunch of lines like: > Mar 20 09:29:05 pine kernel: [ 534.502108] panfrost ff9a0000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0xb9f2b40, tail=0xb9f2b40 If I log in by disabling hardware rendering (choosing "Cinnamon (Software Rendering)") then the desktop does display and work (albeit very slowly). After things broke I enabled the unstable updates, but this didn't seem to fix the problem. Unfortunately I can't remember exactly which software I updated but I assume it was either the kernel or a user space program that works with Panfrost. Has anyone else seen this issue? I'm happy to provide any more details or try other steps if it would help debug the issue. Thanks!
-
Description Jira reference number [AR-1641](https://armbian.atlassian.net/browse/AR-1641) How Has This Been Tested? I run the segment of the bash script into test.sh to check it locally cp /boot/armbianEnv.txt armbianEnv2.txt BLACKLIST_SIMPLEDRM="module_blacklist=simpledrm" if grep -q "meson64" /etc/armbian-release; then echo "extraargs=${BLACKLIST_SIMPLEDRM}" >> armbianEnv2.txt fi #Line extraargs should appear cat armbianEnv2.txt bash test.sh outputs: verbosity=1 console=both overlay_prefix=meson bootlogo=true rootdev=UUID=f9f9535f-bd89-4be4-9ef4-1f1e312cc20a rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x1058:0x0730:u extraargs=module_blacklist=simpledrm In the practice instead of having with lsmod | grep drm_shmem drm_shmem_helper 24576 1 panfrost simpledrm we have now with lsmod | grep drm_shmem drm_shmem_helper 24576 1 panfrost and the warning without hardware acceleration dissapeared. thus glxinfo -B | grep Device was no more llvmpipe but the wished Device: Mali-G31 (Panfrost) (0xffffffff) View the full article
-
I installed panfrost but glxinfo still lists the device as llvmpipe. I'm using Armbian_23.02.2_Rockpi-4cplus_jammy_current_5.15.93_gnome_desktop running wayland. This is how I built panfrost meson . build/ -Dvulkan-drivers= -Dgallium-drivers=panfrost -Dllvm=disabled ninja -C build/ ninja -C build/ install i have no idea what to do next because there is no errors that I can find and I was under the impression that with a kernel 5.1> it is supposed to work. Any help is appreciated
-
Hi, community! I wish you have a nice day! Started investigating why do I have problems trying to hear something from headphones. So, I believe there is something about HDMI audio codec related to panfrost, attached you will find info about. I guess this will be useful to catch bugs. I'm 73 years old, started on computers on NCR Century 100 as field engineer. From those years to now, a long development has brought to life.... Cheers, and many thanks to you! dmesg112222.txt armbianmonitor112122.txt