Active threads

nope, just checked.

I've got an Pine64 a that was one of the Kickstarter models. For a couple of years I've been running OctoPrint on it to run my Qidi i-mates 3d printer. Recently I decided to update from jammy to noble, before I did that I made a backup of my OctoPrint settings and files through the OctoPrint GUI in case of problems. I got a really messed inconsistent with all sorts of dependencies errors because the apt dist-upgrade seemed to freeze and after several hours of no movement I rebooted. As expected it was the mess. I spent about an hour on fixing dependencies but decided it just wasn't worth it as the only thing running is OctoPrint. When I went to restore OctoPrint, I got an error message about not enough space. When I did a df -m , I had plenty of space on the main partition, I posted on the OctoPrint forum and it was pointed out that my /tmp was tiny. Would anyone have any ideas of what is going on and what I can do to fix it? Here's the OctoPrint Error: Uploading backup, this can take a while. Please wait... Restoring from backup... Unpacking backup to /tmp/tmpf_d22xwu...Removing temporary unpacked folderError while running restoreTraceback (most recent call last): File "/home/ageoffri/OctoPrint/lib/python3.12/site-packages/octoprint/plugins/backup/__init__.py", line 1243, in _restore_backup zip.extract(member, temp) File "/usr/lib/python3.12/zipfile/__init__.py", line 1726, in extract return self._extract_member(member, path, pwd) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/zipfile/__init__.py", line 1802, in _extract_member shutil.copyfileobj(source, target) File "/usr/lib/python3.12/shutil.py", line 204, in copyfileobj fdst_write(buf)OSError: [Errno 28] No space left on device Restore failed! Chec And here's the df -m : Filesystem 1M-blocks Used Available Use% Mounted on tmpfs 198 4 195 2% /run /dev/mmcblk0p1 59861 3078 56137 6% / tmpfs 988 1 988 1% /dev/shm tmpfs 5 0 5 0% /run/lock tmpfs 988 0 988 0% /tmp /dev/zram1 47 3 41 6% /var/log tmpfs 198 1 198 1% /run/user/1000

Im currently trying to implement gpu support, but ive been stuck on the same error since a few days. Heres my armbianmonitor -u output: https://paste.armbian.com/uforekotuw root@radxa-cubie-a5e:~# cat /sys/kernel/debug/pm_genpd/pm_genpd_summary domain status children performance /device runtime status managed by ------------------------------------------------------------------------------ pd1_gpu off-0 0 pd1_pcie off-0 0 pd1_nand off-0 0 pd1_de off-0 0 pd1_vo1 off-0 0 4510000.ethernet suspended 0 SW pd1_vo0 off-0 0 pd1_vi off-0 0 pd1_ve off-0 0 pd_riscv off-0 0 pd_sram off-0 0 pd_npu off-0 0 pd_dsp off-0 0 dmesg | grep -i "gpu\|mali" [ 1.836128] panfrost 1800000.gpu: clock rate = 432000000 [ 1.848131] panfrost 1800000.gpu: gpu soft reset timed out, attempting hard reset [ 1.858262] panfrost 1800000.gpu: gpu hard reset timed out [ 1.858486] panfrost 1800000.gpu: Fatal error during GPU init [ 1.858674] panfrost 1800000.gpu: probe with driver panfrost failed with error -110

You need to check the disk space, apparently you are out of space and the daemon is not logging.

Not yet, i'll try to contact him ! Thank you very muych

Success story: https://forums.raspberrypi.com/viewtopic.php?p=2322591#p2322591 with the 3.5 inch ili9488, graphics (wayland) and touch in raspberry pi 3b I hope this helps with making it work in orange pi zero 3 and 2w (only touch missing)

@rockamal Write the image to the SD card using whichever method you prefer—Balena Etcher, Rufus, dd, etc. I installed it on Manjaro using gnome-disk-utility. Just insert it and power on the TV box, and it should boot from the microSD.

If this worked for you, I propose to open a PR, so there is a GitHub record of your work. Add it here https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 Here you also need to pay attention to add to series* files.

All good now?

as I've not been running X11, I can't really help with this, but among the things, check the logs during X startup (normally /var/log/*), that could lead to the cause. note also that more recently, the display systems are running wayland rather than X11. that could cause xfce etc to fail if it is expecting an X11 based setup it is also recommended to bootup in the uart console (debug) port using a usb-uart dongle. - the benefits are numerous, the boot messages are mostly presented - it provides you with a console to login and check things while the system is running e.g. to login and check dmesg and other logs - essential especially when re-wiring network configuration

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

And how to compile openvfd with this patch? How to apply this patch to openvfd?

Added instructions for joining your home lab: https://docs.armbian.com/WifiPerformance/#adding-a-new-device

That should make it. You can always try to see if it works and search online if not.

FYI. HDMI out is broken on those board at the moment. Try to access the board remotely. We don't have people to maintain those old boards.

Thank you for that information. From a cursory look, it seems as if that is only binary images, no source (violating GPL).

I will try to make that easier and more automatic with APA, eventually.

Thank you for letting us know as it allows an interested party to more easily bisect the regression.

download all files attenmented . sudo cp *.dtbo /boot/dtb/allwinner/overlay open /boot/armbianEnv.txt , add this line: overlays=spi-spidev spidev1_1 and reboot, you should find and use /dev/spidev1.1 sun50i-h616-spidev1_0.dtbo sun50i-h616-spidev1_0.dtso sun50i-h616-spidev1_1.dtbo sun50i-h616-spidev1_1.dtso

Moved to Community supported forum as this isn't a standard support board.

True. Also on most computers we have eth0 Not just eth Devices naming is a cosmetic thing from the outside / user perspection, while it has consistency issue from the inside and currently breaks initial (default netplan) configuration. Our job is not to tell user how to configure his network, but that network devices gets up at first boot. Now they do. Job done.

From the picture - I can only guess that kernel package was somehow not upgraded properly as kernel image files are missing. Perhaps they were removed by accident or there was some disk / file system troubles involved. @Chris007 Try hints from here: https://docs.armbian.com/User-Guide_Troubleshooting/

This is being worked on https://lore.kernel.org/linux-sunxi/20250526002924.2567843-1-james.hilliard1@gmail.com/T/#t There is a version of this that was ported over from a vendor kernel to Armbian. https://github.com/armbian/build/pull/6617

Okay, then you have to adjust the source to mitigate the issue. Also log excerpts are often useless. My random guess is that uboot is some old outdated version depending on python2 which has been deprecated years ago.

Last month in Nice, active media developers came together for the annual Linux Media Summit to exchange insights and tackle ongoing challenges in the media subsystem. Here’s a brief summary of the key discussions and upcoming areas of focus. View the full article