Na última vez que postei aqui, consegui renderizar dois triângulos como um quadrado.

Bem, agora ele consegue rodar o GLXGEARS 💀

Isso está rodando no PowerVR SGX535 do meu Dell Inspiron Mini 12 de 2008, com um Atom Z520 e 1GB de RAM.

Está renderizando continuamente em 1280x800, a resolução máxima suportada pela tela embutida do laptop.

Ainda estou trabalhando na performance e corrigindo alguns problemas de renderização, mas fomos de um único triângulo para o GLXGEARS em algumas semanas lol. E sim, ainda estou desenvolvendo isso em um Galaxy Tab S7. O Mini 12 é só para testar no GPU real.

Edit1: I'm looking for people with Intel GMA600 or Sony Vaio P with Z520 or Z530 processors to test resolutions and drivers! And I'm looking for people to help me with optimization sugestions (this is very necessary)

Vídeo do Youtube: https://youtu.be/QRpV8xq82_g?is=SErZhPAOYDTcGnim Github: https://github.com/gabrieelgama/SGX535-reMESA

Source: https://github.com/gregkh/kernel-development/blob/master/graphs%2Fpatches_per_release%2Fcves_fixed_per_release.png

This seems to be the impact of AI tools. In my experience AI is very good at finding bugs(not particularly great at good fixes though)

(*) Terms and conditions apply. See post for details.

Specifically:

• x86_64. Sorry ARM enthusiasts!
• Uses apt, which is probably true for ~every Debian-derivative.
• Currently the Debian-derivative must be using SystemD. I know ZFS includes scripts that work in sysvinit, but I'm not familiar with how Debian-derivatives add those scripts to rc directories; help from a Devuan native wanted.
• The Live ISO MUST use a specific layout and install technique. Most Live ISOs use Casper to create an in-memory Live filesystem overlay, and then use Calamares to install the distro.
  • Most Casper uses have a directory casper/ in the Live ISO, containing filesystem.squashfs as the root filesystem, and optionally filesystem.manifest-remove for packages to remove after installation.
  • Most Calamares uses will just copy the root filesystem underneath the Casper overlay into the new root partition on the persistent storage, then uninstall Live packages (sometimes listed in the filesystem.manifest-remove file). Usually the distro only changes the Calamares branding.
  • Live ISOs which use the above pattern, which is nearly all Debian- and Ubuntu-derivatives, can be used with the ...FromISO option.
  • SlimbookOS and especially TUXEDO-OS (Ubuntu-derived version) have a variant of the above technique; the script detects when those variants are in use and will adapt to their Live ISOs automatically.
  • Ironically, neither Debian nor Ubuntu use this technique for their Live ISOs; instead they debootstrap into the new rootfs, indicating the on-USB apt cache as a (temporary) repository. Some Debian installers even forget to remove the temporary repository after installing.
  • You can just select Ubuntu26.04 or Debian13 on the directly-supported distro list if you want those; they use the classic debootstrap technique.
• The script automatically detects the ZFS situation of your distro:
  • ZFS in kernel package --- does not separately install ZFS, only its utility tools.
  • ZFS in zfs-dkms package in distro repo
  • No ZFS in distro repo --- compile OpenZFS from source.
• The script automatically handles signing of installed kernels and DKMS kernel modules for Secure Boot.
  • You need to install a Machine Owner Key once, on first reboot. Just "Enrol MOK" when prompted and select "Continue" then enter your password.

 __ ___ _  __        .    ,
 '/ |_ (_' |_)    |_ |\  /| _ _    -INSTALLER
 /_ |  ._) |_)()()|_ | \/ |(=| ||_|

The script is intended to be used primarily for daily-driver laptops and personal / family desktops.

You might think "isn't ZFS for big servers and won't I need tons of ECC memory and at least three disk bays?" But you get SNAPSHOTS, and for a typical modern daily-driver system with an SSD, you can get away with a small zfs_arc_max of 10% of your memory or less (1Gb ARC max is fine for a typical SSD daily-driver).

The script provides direct support for:

• Ubuntu26.04 / KUbuntu26.04 (Resolute)
• Debian13 (Trixie)
• SlimbookOS26
• Pop!_OS24.04
• TUXEDO-OS 2026/09 (Ubuntu version)
• PureOS11
• elementaryOS8

For everything other than Ubuntu / KUbuntu and Debian13, the script actually just downloads and validates the .iso file and then uses the "install from ISO file" path internally.

In addition, it has been tested (in a virtual machine) to be able to install from the following Live .iso files:

• Zorin-OS-18.1-Core-64-bit.iso
• linuxmint-22.3-cinnamon-64bit.iso

Note that the script makes an effort to remove grub and os-prober, both of which will annoy you with warnings when they can't find a Grub bootloader in the ESP every time you apt upgrade the kernel. Unfortunately, some distros make them a strong dependency of their distro-specific packages:

• tuxedo-base-files
• zorin-os-desktop

If the distro has such strong package dependencies on grub and/or os-prober, the script does not remove them as this can lead to broken installs. You'll just have to tolerate the nagging.

Pop!_OS24.04 Cosmic has a known issue where auto-login will disable screen locking until you log out and log in again. Please ask System76 to fix it.

The script automatically installs zfs-auto-snapshot, because automatically-managed snapshots are AWESOME. If you want to disable it completely:

• On distros where ZFS is available either in-kernel or in zfs-dkms, just sudo apt remove zfs-auto-snapshot.
• On distros without ZFS, zfsbootmenu-installer will install zfs-auto-snapshot-activate and zfs-auto-snapshot-deactivate scripts to completely activate or deactivate zfs-auto-snapshot. Run those as root.

None of the substantive code was written by AI.

I used AI to help with the mechanical parts of porting (e.g. translating autotools to CMake, replacing ioctl calls with tcgetwinsize, translating the C structs into Rust), as well as to write some of the smoke tests (e.g. cairo-test, mesa-test).

Where Claude really shines though is in reviewing your own commits. You give it a hash, and it tells you about the silly memory leak or deadlock that you left in, before you can make a fool of yourself.

Faith Ekstrand's write-up on Kraid, the new shader compiler for the open source Panfrost/PanVK drivers:

https://www.collabora.com/news-and-blog/news-and-events/panfrost-is-now-using-kraid.html

Starting with Mesa 27.0, all Mali GPUs with Valhall (v9) or newer will use it by default. Mesa 26.3 is the last release with the old compiler.

Highlights compared with the old compiler:

- ~18-20% fewer shader instructions across OpenGL and Vulkan shader sets

- Over 80% less register spilling

- Proper 64-bit integer support

- Much faster shader compilation with lower memory use

It went from start to default in under six months!

Saw this post on Bluesky and having had casually followed the trashing of X for about 20 years, the whole Canonical/Mir fiasco, and finally the extremely slow adoption of Wayland, this was cool to see! 😁

👀💃

Hey everyone,

I'm developing Linux Subsystem on Android (LSA), an experimental project that runs a native Linux userspace on rooted Android devices while keeping Android as the host operating system.

The goal isn't just to run a Linux desktop. I'm trying to make Android's hardware and services usable through normal Linux interfaces, without requiring applications to be rewritten for Android.

LSA uses the Android kernel directly. It's not PRoot, emulation, or a VM.

What's currently working in development testing on a Blackview N6000:

Debian ARM64 with a graphical desktop and native Linux applications

Hardware-accelerated OpenGL through Mesa/VirGL and Android's GPU stack

Audio playback and microphone capture

USB storage integration, including automatic NTFS mounting

Applications including Firefox, OpenArena, and SuperTuxKart

This is still pre-alpha. Some applications require workarounds, graphics compatibility is incomplete, and hardware support varies. Some of the results above are from a private development preview and may not be present in the current public release.

I'm looking for people who have spare rooted Android phones and are willing to help test LSA on different hardware.

Useful experience includes Android rooting, ADB, Linux debugging, shell scripting, Mesa/VirGL, graphics drivers, audio, and embedded Linux. You don't need to be an expert.

There are two ways to help:

Independent testing: Try LSA on a spare device, collect logs, report bugs, and share hardware compatibility results. No remote access required.

Direct development collaboration: For volunteers who want more involved help, I'm open to supervised SSH debugging on a dedicated test device. Any access would be optional, explicitly authorized, and governed by a written agreement restricting my activity to the agreed testing and development work.

Please don't run this on your primary phone or anything you can't recover. This is experimental rooted system software, and things can break.

GitHub: https://github.com/Phsphorus/LinuxSubsystemOnAndroid

If you're interested, let me know your phone model, chipset, Android version, and rooting method.

I'm also looking for feedback from people familiar with Linux systems programming or Android internals.

Thanks!

Disclaimer:

This project has been developed with the assistance of AI. I'm not an expert in every field this project covers, and I don't claim to be. LSA is an experimental learning project, and I welcome technical feedback, corrections, and contributions.

A dream can only be achieved if you try.

---

Example of the experimental UI.

I wanted to share a project that's been making some interesting progress in PC-based home theatre.

CroqueMr (u/Croque_Mr) is developing native Dolby Vision support for Kodi through a custom LibreELEC build, including Profile 7 FEL reconstruction. Development has moved quickly, with regular releases bringing performance improvements, new rendering modes and broader hardware support.

What's currently available?

• Native Dolby Vision playback, including Profile 7 FEL reconstruction.
• Intel and AMD support, with NVIDIA support also being developed.
• Dolby Vision rendering modes, including Master Reference and Adaptive HDR Mapping.
• Dolby Vision-to-HDR10 conversion and experimental AI-assisted HDR10-to-Dolby Vision conversion.
• Blu-ray 3D support on compatible AMD hardware.
• Performance optimisations targeting lower-power mini PCs, including Intel N100/N150 systems.

The latest Beta 5 release includes further improvements to playback stability, FEL handling, scaling and display detection. Results and compatibility can vary depending on the hardware, TV, source material and rendering mode.

What's coming next?

The developer has outlined plans for a GPLv2-or-later licensing rebuild, further AMD improvements, HDR10+ support and Dolby Vision-to-HDR10+ metadata reinterpretation, alongside expanded compatibility with older Intel graphics and additional NVIDIA hardware.

The longer-term goal is to make PC-based Dolby Vision playback more capable and accessible, including on affordable mini PCs.

Project links

• Main development thread: https://forum.libreelec.tv/thread/30362-dolby-vision-w-fel-3d-for-pc-amd-intel-nvidia/
• GitHub — source code and releases: https://github.com/CroqueMr/libreelec-x86-DV/
• Original Reddit thread: https://www.reddit.com/r/libreeLEC/comments/1wq20eu/wip_native_dolby_vision_support_on_x86_intel_cpu/

Full credit to u/Croque_Mr for the development, along with the community members contributing testing, feedback and improvements.

It's been impressive to see how much the project has evolved in such a short time. If you're interested in the technical details, supported hardware or latest builds, the links above have all the information.