Issue Restart command also will get stuck with at basically “Shutdown” with LED light ON and will proceed to restart at times. Need to physically turn off and on again to get it to reboot. Minor issue.
Successfully upgraded to the latest Testing Updates in linux-kernel 5.9.9-2. Still no sound.
Enabled “layers.acceleration.force-enabled” on Firefox 83 to check whether there is any performance improvement. Does not crash but no visible performance improvement as far as i can tell.
Edit: When “layers.acceleration.force.enabled” = True. YouTube Video Freeze and Dmesg report Panfrost gpu fault:
“[ 803.476975] panfrost ffe40000.gpu: js fault, js=0, status=UNKNOWN, head=0x49e5bc0, tail=0x49e5bc0”
Interesting you seem to have precursor/indication when Freeze is going to happen. In my case on GT King Pro kernel panic/freeze usually occur during heavy disk writing (like large system updates or copying files) and in other cases no telling sign can be just opening a new tab or start up and application or in the middle to typing text. But with kernel 5.9.0 and above it seems to be more usable.
I think I might be on to something… If I change the cpu speed scaling governor from “ondemand” to “performance” there are no more glitches on the screen and so far (after 18h) no freezes either on my Ugoos.
In both my Armbian and Khadas images (which run stably) the setting for the governor has been “performance” (by default/install or by my choice, I don’t remember).
To be continued…
@JFL Yeah, I think we have come to understand now that every type of box needs a specific set of tweaks to get it to run well. Somewhat disappointing but also makes it more interesting, I guess.
@JFL The governor is a built in feature of modern kernels and it can be accessed via various tools/programs, on Manjaro via cpupower (pacman -S cpupower). The options (some might not be available on your platform) can be seen (as root) by just doing cpupower or cpupower frequency-info. To set a governor, do like cpupower frequency-set -g performance. You can also edit a config file /etc/default/cpupower but I don’t know yet if this is sufficient to make settings persist over reboots. @TheMojoMan Sorry, I just missed your reply (which made part of mine redundant).
Edit: To make the changes to /etc/default/cpupower persistent (and to have them applied at boot) you must set up the associated systemd service with systemctl enable cpupower --now
Edit2: The governor and its current setting can be read directly like so cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
and it can be set directly like so echo performance >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
@TheMojoMan@JFL I’m not using Panfrost right now (I think; I’m using a vanilla install and haven’t added any mesa-git stuff or the like). I’m just going to watch how your endeavor progresses and then jump in later. I can watch all movies (720p, h265) smoothly without avg. CPU load going above, say 35%, so I’m good for now.
A comment on the apparent fix for my Ugoos by setting governor to performance:
It is perhaps not surprising that there would be problems on Amlogic chips when the CPU frequency is allowed to vary (i.e. when using using the kernel DVFS functionality) since the hardware does not (at least for some chips) report back the correct frequency values to the kernel, as can be seen from e.g. these threads Armbian, Khadas and Khadas. (When using a fixed frequency it is trivial for the kernel to figure out which one it is, and quickly adjust accordingly, even if it would be reported incorrectly by hardware. If the frequency is switched this is harder, I guess.)
For now the tentaive fix/workaround seems to be working but I will run it for a few more days before actually calling it a fix. (I have run it on my hybrid Khadas-boot/Manjaro-root image for 24h without problems and have now switched to a very vanilla recent 100% Manjaro image which I will continue to use for my testing.)
Edit2: @JFL I have seen that error too, and I don’t know what it means (I would like to know also).
@dante6913 Hi, I think that the link you posted goes to an image of mine, which is unofficial (so use at your own risk). I have put up also a newer image that I’m running now, see this post (with the same disclaimer).
Hi tripole
The issue that I have is that I couldn’t try it because I always get
" Temporarily Unavailable
The file you are looking for is temporarily unavailable due to maintenance!
Don’t worry! Check back later and it will be available again!"
I never used any Arch based distribution so every thing is a little confusing, but at same time I think that will be fun to get out from debian based distributions
Yes, they are different; the one you are downloading now (the one labeled …-3pole.img.xz, I hope) is a newer version. Both images are built with the official Manjaro ARM build environment (manjaro-arm-tools) according to this post (but, of course, by some random guy on the internet; me).
OK first impressions with my X96 air s905x3
Installed and booted with the toothstick with meson-sm1-sei610.dtb. No ethernet and no sound. I enabled sound and network manager following tripole instructions.
Ethernet didn’t work so I tried with meson-g12a-sei510.dtb as said by TheMojoMan, but again after reboot still didn’t work. I remembered that with Balbes images we had to change meson-sm1-sei610.dtb to be able to use ethernet so I used the changed dtb “meson-sm1-sei610-ethfix.dtb”, the I was able to boot and the Ethernet worked.
The sound from the box didn’t work but I didn’t lose anytime with it, I used my fiio usb dac, that worked.
I enable ssh and I did a uname -a I got 5.9.0-2-MANJARO-ARM kernel. So for now I’m looking to update the kernel. So is possible to update the kernel?
Sorry for my English, is not my first language.