Kali Linux
Python hash generator and music files. Kali linux
https://gordol.github.io/n810-revival/posts/2026-11-02-gpu-command-stream/
When mainline Linux marked the OMAP2420 for removal, I pulled out my Nokia N810 to see what I could still get running. It has 128 MB of RAM and a slide-out keyboard I still like. I got Debian 12 booting on a patched Linux 5.15 kernel and just kept going.
Nokia shipped the N810 without a Maemo driver for its PowerVR MBX GPU. We studied a Nokia N95 firmware image for the same OMAP2420, reconstructed the GPU’s command stream, and wrote a Linux driver and Mesa support without the vendor SDK.
At one point the command FIFO stalled after the first polygon. Fixing vertex setup got the GPU to write triangle parameters, but the coordinates came back infinite until we supplied the clipping constants. An early rasterizer test drew four squares of color into a 32 × 32 buffer. Later we got the GPU doing the transforms, lighting, and rasterization for glxgears. In a 400 × 400 rotating terrain benchmark, it completed over 70 GPU frames per second with the CPU at 480 MHz. The display controller recorded about 26 transfers per second in that run.
The tablet boots from two Debian slots on the SD card. They share one flashed kernel and a persistent data partition, and there’s a small recovery system on internal storage. AI coding agents helped dig through board files and boot logs. One of the better fixes was swapping the SD adapter. The same card that kept timing out booted right away.
The GPU now draws Pocket, the graphical desktop I built for the tablet. There’s also a windowed TUI over SSH. Pocket can plot APRS stations from a Bluetooth handheld radio and use offline elevation data to check whether a ridge blocks the radio path. And ChessGenius runs its original Symbian ARM code directly on the N810, with the MBX drawing the chessboard. That got us looking at a similar runtime for ARM Windows CE apps.
The driver, Mesa changes, kernel build inputs, and Pocket source are in gordol/n810-revival. To try the terminal desktop on Linux or macOS, run make -C pocket n810 from the checkout with Python 3.11+ and Make.
Anyone else still working on OMAP2 hardware? I’d be especially curious to hear from anyone who tried getting the MBX going back in the Maemo days.
r/kernel • u/Beneficial-Sock-5130 • 3d ago
r/kernel • u/Apart_Case4994 • 3d ago
Hey everyone! I built **SysArmor**, a zero-dependency system hardening and security tool written entirely in pure C and Assembly.
It uses POSIX system calls (like `open` with `O_NOFOLLOW` and `fstat`) to protect critical system paths against symlink attacks, race conditions, and unauthorized modifications across all standard Linux distros (Ubuntu, Debian, Fedora, Arch, etc.).
If you're into low-level systems programming or terminal utilities, the repository is here:
👉 **https://github.com/error0941/sysarmor**
I’d love to hear your feedback, code reviews, or suggestions!
NOT:Başlıkta Assembly yazmışım ama şu anki sürüm tamamen saf C ve POSIX sistem çağrıları ile çalışıyor. İlerleyen sürümlerde kritik syscall'lar için inline assembly ekleyeceğim.
r/kernel • u/oksylisten • 4d ago
Sardina Systems is an OpenInfra software platform company based on OpenStack and Kubernetes and is looking for a Linux Kernel Live Patching Engineer to join our team.
Position summary
Build and operate a live kernel patching feed for AlmaLinux 10. You own the full technical chain, from CVE triage to signed, tested RPMs published in a public repository. This is a hands-on kernel engineering role, not a management or release-coordination position.
Core responsibilities
Patch engineering
- Track AlmaLinux security advisories (ALSA) and upstream kernel CVEs.
- Triage CVEs against the published scope: critical, remotely exploitable or actively exploited vulnerabilities.
- Backport security fixes to the supported AlmaLinux 10 kernels, resolving conflicts across version differences.
- Generate live patch modules with klp-build. Initially, publish individual CVE patches; evaluate cumulative/atomic replace strategies as the pipeline matures.
- Identify CVEs that cannot be live patched (e.g. __init changes, data structure layout changes) and record them in the coverage-gap log.
Build and distribution pipeline
- Reproduce AlmaLinux kernel builds exactly (same source, config and compiler), e.g. in mock with the AlmaLinux buildroot, so modules match the running kernel.
- Maintain the automated pipeline: CVE scan, build plan, klp-build, RPM packaging, signing, test gate, createrepo_c publication.
- Plan and execute the move of support to new AlmaLinux kernel releases as they ship.
- Verify the exact client-side commands work on stock AlmaLinux 10 (dnf kpatch auto plus kpatch-patch-* packages).
Testing and release gate
- Run the mandatory pre-publication gate on every patch:
- load and unload on the target kernel in QEMU;
- run kernel livepatch selftests;
- for high-severity CVEs: apply and revert under load on a FishOS test cluster with running VMs and Ceph I/O.
- Document which tests were passed for each release.
- A patch that passes the gate is cleared for publication. Do not publish a patch that has failed the gate.
Release and withdrawal
- Publish approved patches with release notes listing the CVEs covered.
- Publish the source for every released patch alongside its RPM.
- If a published patch misbehaves: pull it from the repository, publish an advisory, and give users revert instructions.
- Maintain the runbook and coverage-gap log.
Secure Boot
- Manage the Sardina module-signing key and RPM signing key.
- Document and verify mokutil key enrolment for AlmaLinux users.
- Work with the Ops team to automate key enrolment on FishOS.
Required skills
- Linux kernel development: strong C, with hands-on experience backporting kernel patches or debugging kernel modules. Screening will test this directly.
- Live patching: practical experience with klp-build or kpatch, or demonstrated ability to learn them quickly from source.
- RPM and the RHEL/AlmaLinux ecosystem: kernel packaging (RPM/SRPM), mock, dnf, createrepo_c and repository metadata.
- Automation: Python or shell; building and maintaining CI-style pipelines.
- Signing: GPG key management and RPM signing; kernel module signature verification and MOK enrolment.
- English: working proficiency.
Preferred skills
- Spoken Russian and/or Mandarin, in addition to English. This is to work closely with Russian- and Mandarin-speaking team members.
- QEMU-based VM validation or canary testing.
- Upstream kernel contributions or involvement in the live patching community.
- Koji or similar build orchestration systems.
- Ceph I/O testing or storage-heavy workloads.
Key traits
- Boundary awareness: Willing to say plainly "this CVE needs a reboot" and "this kernel is out of scope" rather than forcing a risky patch
- Release discipline: Understands that a bad patch is the main reputational risk and will not skip the test gate under pressure
- Self-directed: Comfortable owning an end-to-end pipeline with minimal supervision
- Confidentiality: handles embargoed vulnerabilities and unreleased plans with discretion.
Working context
- Scope: AlmaLinux 10 only, starting with one kernel version.
- Infrastructure: runs separately from the existing Koji-based OpenStack build infrastructure, but follows the same automation approach.
- Primary tooling: klp-build, kpatch/kpatch-dnf, mock, createrepo_c, GPG, systemd timers, QEMU and a FishOS test cluster.
- Release authority: Routine patches are approved by the automated gate; no per-patch sign-off is required. A named release authority reviews weekly summaries, approves exceptions (e.g., a patch that cannot pass the full gate for a documented reason), and handles emergency withdrawals.
- Backup: one Ops team member is cross-trained on the test gate, publication and withdrawal steps early in the project.
Success Criteria
First milestone
- klp-build confirmed working on a real Alma 10 kernel
- End-to-end pipeline producing a signed, tested patch for one CVE class on one kernel version
- Test gate passed on at least two consecutive builds
- Coverage-gap log and runbook exist
Second milestone
- Pipeline operating reliably with the test gate on every build
- Secure Boot enrollment automated on FishOS
- Sources and tooling published under the appropriate license
- Runbook and coverage-gap log maintained and current
r/kernel • u/Head-Leek6151 • 6d ago
r/kernel • u/PanthomAditya • 7d ago
r/kernel • u/Mundane_Educator8466 • 9d ago
I'm currently using Red Hat Enterprise Linux (RHEL), and I need to improve the timing precision and reduce jitter for periodic events.
I'm interested in using a PREEMPT_RT kernel, but I don't currently have access to a Red Hat subscription.
Since I need to keep RHEL as my operating system, I'd like to know what options are available.
Is it possible to build and install a PREEMPT_RT kernel from source on RHEL? Are there any officially supported or community-supported alternatives?
I'd appreciate any guidance or documentation.
Thanks!
r/kernel • u/Mindless-Attempt4187 • 11d ago
Some time ago I published a post about a project I was working on, previous post.
The purpose of this project was to make working with .dts files easier. For that I starting developing an IDE with some integrated tools:
There is a lot of knowledge about kernel condensed on this IDE, in order to make device tree development easier and faster.
Thanks to the database, you can start typing and use auto-completion for a compatible, the IDE checks each binding information and shows which nodes are available to use and which ones are mandatory for a proper operation.
That way, if some compatible or property it's not recognized, you can early detect it, without waiting for a fail on boot, or worse, a silence bug on kernel.
The project is now open source, and all the code and beta releases are available on GitHub and Official website. It's still a beta, but I think it is already useful enough, that's way every suggestion it's well received.
This project was developed with the help of AI, which made it possible for a single person to develop it.
r/kernel • u/TechHavenStudios • 11d ago
r/kernel • u/Tausif23456 • 11d ago
Hey everyone, I am a 13-year-old student from Bangladesh building my own OS (PoragOS) from scratch.
Today I finally got the PS/2 mouse working! I set up IRQ12 interrupt handling, decoded the 3-byte mouse packets, and wrote a routine to draw a cursor directly to my VESA framebuffer. Seeing the cursor move smoothly on a screen I built myself is amazing.
My next steps are fixing the cursor trails (backbuffer) and implementing User Space (Ring 3). I would love some feedback!
r/kernel • u/Creepy-Credit2369 • 12d ago
Hello Everyone,
I have a custom RTL code for 1G/10G ethernet( this will be an IP core in my vivado design).
I want to write a kernel driver or LKM to use this from my application code in Linux OS ( boot image will be generated from Petalinux)
The goal is to configure and use this core to bring up ethernet connection from application code (user space I/O).
Devices & Tools : KRIA , Petalinux 24.2
Any user guides/blogs/working examples on this would help me a lot :)
r/kernel • u/noboruma • 13d ago
r/kernel • u/Dangerous-Hamster272 • 18d ago
r/kernel • u/Silent-Degree-6072 • 19d ago
Is there a way to offload zram compression & decompression to the GPU?
I have a compilation server with 36 logical cores but only 16GB of RAM (I am unable to upgrade due to the global RAM crisis; DDR4 registered ECC costs a ton). In an effort to squeeze more "RAM" out of my RAM, I decided to start using zram compressed with zstd.
I managed to get 48GB of zram to work (3:1 compression), however it resulted in one of my cores being pinned at 100%, desperately trying to compress the increasing amount of ram being used by 36 compile jobs. Is there a way to offload this to the GPU? I think it would greatly speed up compilation if possible, and would perhaps allow for a greater compression rate (zstd ultra maybe???)
EDIT: The GPU is a GTX 1660 Super with the open-source kernel modules from NVIDIA. It basically never gets used and usage is at a constant 0-1%
r/kernel • u/AccomplishedAir8352 • 21d ago
Hello, I'm a CS undergraduate studying about linux kernel development.
I'm currently on LDD3 book, emphasizing about importance of cleaning up allocated resources on exit.
I assume that this is not likely to be handled properly in some linux modules as removal of modules is not something that is performed on a daily basis.
I have been looking for places to start my contributions and was wondering whether this, identification of memory leaks and applying fixes, could be a valid entry point.
The questions I want to ask is,
Thank you for your time. Any comments are welcome!
*EDIT Thank you all for your kind responses. They have been very helpful !
r/kernel • u/Totallynotnormalguy • 21d ago
I'm building a monolithic kernel called sonix (Son I'm crine + Unix) and I just found out about encrypted filesystems and I don't know what to put in these directories